Database Users

[Q] Error 7 When installing 2.3.7 from Recovery

Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin

normankev said:
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
Click to expand...
Click to collapse
Try toggling script asserts, or re-download the file.
Also, I suggest updating your recovery to 2.5.1.8.

Thanks for the quick reply!
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
I've tried redownloading the file multiple times, even getting earlier versions of the rom to try.
How would I go about updating recovery? I don't have a functional usb cable at the moment unfortunately but if absolutely neccessary I can hack one up.

normankev said:
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
Click to expand...
Click to collapse
I think you should have the asserts disabled to get past the error. (use the extracted zip, which gave you the error 7)
If this does not help, probably best way to go forward is to get a usb cable and try flashing using fastboot

Can I do OTA if I rooter my Nexus?

I just got OTA notification, should I install it? I'm rooted and have custom recovery.

If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.

4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.

By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.

Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks

I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.

I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it

That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app

@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.

I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?

@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.

Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app

mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?

inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped

[Q] /system/etc/gps.conf issue when trying to update to KitKat

I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.

jaredmorgs said:
I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.
Click to expand...
Click to collapse
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.

racerklm said:
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.
Click to expand...
Click to collapse
I decided to install scrosler's Stock 4.4 ROM, which now has the update applied. It's working great.
Thanks for the advice either way. Would love to know why gps.conf was blocking the update.

Phone not booting after attempt to update 4.4

So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?

bankmaggot said:
So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
Click to expand...
Click to collapse
Update: I was able to get to the recovery mode hitting down+power. I'm kind of lost at this point. Just give me 4.3 anything at this point.:crying:

I am in the same boat!! Any ideas, i have tried to do a sideload but i get an error installing //sideload.zip
checking for md5 file
skipping md5 check : no md5 file found
warning no file_contexts
file_getprop: failed to stat "/system/build.prop": No such file or directory
e:error executing updater binary in zip '//sideloader.zip'

download factory image and flash it via fastboot..for instructions -->Click Me!

anto.danny said:
download factory image and flash it via fastboot..for instructions -->Click Me!
Click to expand...
Click to collapse
Brilliant, that fixed. Thank you :good:

Flashing ROM Fail HELP!!!

So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks

ST2014 said:
So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks
Click to expand...
Click to collapse
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.

Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?

b3ltazar said:
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.
Click to expand...
Click to collapse
Thanks for the help. Unfortunately I got a tad frustrated and accidentally deleted EVERYTHING!!! So I have blank tablet now. I'm trying to download the Google Factory Images from their site but it only downloads this .tgz file instead of a zip with 4 files. I even tried extracting the .tgz and it give me a single file. Anyone have any ideas as to why this is?
I'm trying to restore this tablet based on following this page (can't post outside links on this site until after 10 posts?.......really?)
But as you can imagine I'm stuck because I can't download the aforementioned zip file.
My tablet is soon becoming destined to be a rifle target.

BAM!!! Never mind got it all squared away. Now if we can get that ROM set up so that it will work properly.

Androlover98 said:
Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?
Click to expand...
Click to collapse
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.

ST2014 said:
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.
Click to expand...
Click to collapse
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.

b3ltazar said:
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.
Click to expand...
Click to collapse
Exactly. Nothing beats KitKat. PERIOD
Sent from my Nexus 7 using Tapatalk