I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )
Related
Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!
mooshubob said:
Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!
Click to expand...
Click to collapse
Same thing here, except I also had a overclocked kernel. What I did was use ODIN, there is a thread here. I downloaded the stock files full install.
1) Download full recovery image and Pit file
2) Open Odin and point to the PIT file downloaded and in PDA section point to the full firmware.
3) Check only Reboot and Debug in ODIN
4) Power on phone while holding 1 on the keyboard (it will go into download mode)
5) in ODIN press START and flash image
6) Then update to to the new image
7) Re root phone using 1 click
8) Install Clockwork Mod again 1 Click
9) update superuser
Have fun
mooshubob said:
Hey guys, quick question:
I'm fully rooted/one-click CWM'd (stock everything, however), and I just got the OTA DI18 update notification. When I tried to install it, it booted to the stock recovery (blue text) and said something about verification of the signature failing...installation aborted.
Now, how would I go about either uninstalling CWM, or reflashing the stock recovery? I can't find anything that really goes into detail about any of this.
Any help would be most appreciated!
Click to expand...
Click to collapse
well what i did is i download this file http://forum.xda-developers.com/showthread.php?t=786266 the i went to cwr and wipe data/factory reset thats only if u deleted any sprint apps... then flash it and u are good to go!!!
Whew. Worked with the full release (the zImage.tar failed and near-bricked my phone haha). Getting the DI07 update now, should hopefully see the new one soon-ish. Then I'll re-root and restore my backup.
I've been in and out of these forms for hours now, and I still can't figure this out. I have an I9020a from Fido (Canadian). I flashed the stock ROM & modem from this post (http://forum.xda-developers.com/showthread.php?t=1056062&page=68). When I try to flash the 2.3.6 update through CWM 5.0.2.3 I get the following
-- Installing: /sdcard/7d11404284c0.signed-soju-
GRK39F-from-GRJ22.7d114042.zip
Finding update package...
Opening update package...
Installing update...
assert failed: file_getprop("/system/build.prop"
. "ro.build.fingerprint") == "google/soju/crespo
:2.3.4/GRJ22/121341:user/release-keys" ||
file_getprop(/system/build.prop". "ro.build.fin
gerprint") == "google/soju/crespo:2.3.6/GRK39F/1
89904:user/release-keys"
E:Error in /sdcard/7d11404284c0.signed-soju-GRK3
9F-from-GRJ22.7d114042.zip
(Status 7)
Installation aborted.
Now I know that some people say I need to use the stock recovery, however there doesn't seem to be any way to get that back. The post (http://forum.xda-developers.com/showthread.php?t=1033269) that everyone mentions has dead links in it, so I cannot download the stock recovery from it.
Can anyone help?
Wolfgar2k
Have you renamed the file to update.zip. placed it on the root of the sd ard and flashed it by selecting the install update.zip option in clockwork. You cannot use the flash zip from sdcard option.
Sent from my Nexus S 4G using xda premium
I tried renaming it to update.zip, but got the same results. I tried with Clockwork 4.0.0.2 and 5.0.2.3. Both of these are missing the install from update.zip option for some reason. I also tried to flash a recovery.img file that was supposed to be stock recovery from post (http://forum.xda-developers.com/showthread.php?t=1033269&page=4) but all it did was make the phone go to the screen with the ! in a triangle with the android logo beside it.
Have you been on stock the whole time? These errors usually mean that there is some different configuration than expected on your phone when using an update package. It could be your radio or your recovery and I have read that even different versions of google apps can cause this. I have seen this myself. Your best bet is to flash the full rom package for your I9020A with clockwork recovery to get you to 2.3.6 you can download here. http://android.clients.google.com/p...8148de0d.signed-sojua-ota-189904.0b9c8148.zip You won't receive any errors because it's a full rom package. You will however have to re flash clockwork recovery aftewards.
Had same issue coming from 2.3.4 I was rooted . Flash the full ROM 2.3.6 you shouldn't have to wipe. after flashing you lose cwr and root
Sent from my Nexus S using XDA Premium App
I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.
Wolfgar2k said:
I tried flashing that ROM with CWM. It made my phone go into a boot loop. I even tried using the NAND 2.3.1 backup. That didn't work, nor did it replace my recovery with the stock one. I did manage to flash to a full 2.3.6 ROM that was pre-rooted, though that's not quite what I was going for. I was trying to get back to pure stock with the 2.3.6 update.
Click to expand...
Click to collapse
2.3.1 was never designed for the i9020a the first release was 2.3.3. A nand backup will never get you to stock recovery. when making a backup it doesnt save a recovery.img because you make the nand using the fastboot flashed clockwork recovery.img.
The link I provided for you is the full rom which is pure stock 2.3.6 for the i9020a Nexus S straight from Google. This is the update presented to me when going from 2.3.3 up to 2.3.6. If you flashed that you are completly stock including radio, kernel and recovery.
After if you want cwm and root back you have to fastboot flash cwm again and then from cwm I flash su.
I am in the same boat as Wolfgar2k. I am also in Canada and have a Nexus S I9020A with Fido. I wanted to ditch CyanogenMod and go back to the stock 2.3.6 version.
I tried installing the build that blowtorch provided (copy to SD card, rename to Update.zip, select "Install from SDCard"). The install completed without error but when I boot the phone, it gets to the loading animation (colourful X-shaped particle system), the animation then freezes and restarts, over and over.
Anyone know what could be going wrong here?
I have (finally) solved my problem. It turns out all I had to do was use fastboot to erase the cache (fastboot -w) and the phone no longer crashed on boot. Tons of thanks to blowtorch for posting that 2.3.6 build, which does in fact work just fine. I have my phone back!
So happy.
Cooper39,
can you guide me how can i do "use fastboot to erase the cache (fastboot -w)" on my nexus .. I am having the same problem
Ahmed
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Ran it again to get the exact error messages.
On install it takes me to CWM Recovery and asks if I want to install the untrusted zip, (Shows failed to verify whole file signature, then signature verification failed.)
If I tell it to install the untrusted zip I get the following:
file_getprop: Failed to stat "/system/build.prop" : No such file or directory
E: Error in /cache/fumo/OTAPkg.zip (Status 7)
Installation aborted
YELLOW_STL_MACH said:
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Click to expand...
Click to collapse
If you have a custom recovery installed it won't update.
Sent from my SCH-I535 using Tapatalk
re install the stock recovery or wait a few hours for the devs to put flashable versions.
YELLOW_STL_MACH said:
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Click to expand...
Click to collapse
I would recommend this: http://forum.xda-developers.com/showthread.php?t=2723159
It's always best to wait for someone to release the version(s) of Firmware that will work for S-Off/Rooted/Custom ROMs. Since I'm running ViperOneM8, I flashed the No Boot firmware and have no issues. BTW, my battery life is absolutely AMAZING.
FWIW, here's the patch download on Verizon's own servers: https://pvzwmdmcdn.vzw.motive.com/firmware/HTC6525LVW_1.55.605.2-1.12.605.11_R3.bin
@YELLOW_STL_MACH curious: what did you end up doing? I'm in the same boat (Orig Factory stock ROM, rooted, S-Off, etc.) but never bothered taking the OTA (although it keeps bugging me). just wondering what you did and if it was worth the trouble.
Sorry if this topic has been discussed, I tried searching a bunch before posting, but didn't really find anything.
I have a P3113 that I thought I rooted and installed CWM a very long time ago, but never installed any custom roms or anything. Since then I've updated to JB with OTA updates.
Last night I tried installing CWM 6.0.4.8 with this guide http://forum.xda-developers.com/showthread.php?t=2642005 so I can install a rom of KitKat. Everything in Odin says it was successful, but when I try booting into the recovery mode, it is not CWM, its stock Advanced Boot Loader 3e. Also when the stock recovery loads, it says "No Command" upon starting, and also I tried a cache wipe, and that gave an error.
I'm too afraid to wipe the data partition or factory reset. Did the OTA ICS or JB updates unroot my device? do I need to do it again? My flash counter was at 0 so I know I didn't try anything in the past that I don't remember, but now count is at 4 since I tried CWM multiple times. Do I need to downgrade the stock rom to something before JB?
Thanks for any help!
Carini33 said:
Sorry if this topic has been discussed, I tried searching a bunch before posting, but didn't really find anything.
I have a P3113 that I thought I rooted and installed CWM a very long time ago, but never installed any custom roms or anything. Since then I've updated to JB with OTA updates.
Last night I tried installing CWM 6.0.4.8 with this guide http://forum.xda-developers.com/showthread.php?t=2642005 so I can install a rom of KitKat. Everything in Odin says it was successful, but when I try booting into the recovery mode, it is not CWM, its stock Advanced Boot Loader 3e. Also when the stock recovery loads, it says "No Command" upon starting, and also I tried a cache wipe, and that gave an error.
I'm too afraid to wipe the data partition or factory reset. Did the OTA ICS or JB updates unroot my device? do I need to do it again? My flash counter was at 0 so I know I didn't try anything in the past that I don't remember, but now count is at 4 since I tried CWM multiple times. Do I need to downgrade the stock rom to something before JB?
Thanks for any help!
Click to expand...
Click to collapse
First of all check if your device is rooted I would say use root checker in google play store if not re root your device
Secondly you can also try to flash any recovery in zip file from your phone's stock recovery check the thread given below for flashable zip file of CWM after flashing reboot into recovery and you should be in CWM recovery....
http://forum.xda-developers.com/showthread.php?t=2548257
Carini33 said:
Sorry if this topic has been discussed, I tried searching a bunch before posting, but didn't really find anything.
I have a P3113 that I thought I rooted and installed CWM a very long time ago, but never installed any custom roms or anything. Since then I've updated to JB with OTA updates.
Last night I tried installing CWM 6.0.4.8 with this guide http://forum.xda-developers.com/showthread.php?t=2642005 so I can install a rom of KitKat. Everything in Odin says it was successful, but when I try booting into the recovery mode, it is not CWM, its stock Advanced Boot Loader 3e. Also when the stock recovery loads, it says "No Command" upon starting, and also I tried a cache wipe, and that gave an error.
I'm too afraid to wipe the data partition or factory reset. Did the OTA ICS or JB updates unroot my device? do I need to do it again? My flash counter was at 0 so I know I didn't try anything in the past that I don't remember, but now count is at 4 since I tried CWM multiple times. Do I need to downgrade the stock rom to something before JB?
Thanks for any help!
Click to expand...
Click to collapse
Reroot...and try newer recovery from here:http://forum.xda-developers.com/showthread.php?t=2548257
Great thanks guys! I'll try tonight when I get home
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
KomradeNikolai said:
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
Click to expand...
Click to collapse
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Yaz75 said:
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Click to expand...
Click to collapse
Thanks. I don't spend much time on here and I didn't see a post that gave me something concrete.
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
-- Installing: /sdcard/0/Download/***.zip
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys or google/hammerhead/hammerhead:5.0.1/LRX22C/1602158:user/release-keys; this device has google/hammerhead/hammerhead:4.4/KRT16M/893803:user/release-keys
E:Error in /data/media/0/Download/***.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
I am getting the same error.
KomradeNikolai said:
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
Click to expand...
Click to collapse
I actually tried reverting to stock recovery using Flashify. Though it shows success but when I try to run the update, it doesn't get past the recovery mode, android with the red exclamation mark. Not sure where I am going wrong with it specially when I have been flashing since last 3 years.