Database Info

[Q] DI18 OTA failed. How to remove CWM Recovery?

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.

Can't install OTA update

Hi guys,
I received today OTA update, but cant install it. My phone is rooted and has got Clockworkmod recovery. I tired move update zip file in sd card root and install zip from sdcard, i get following error > assert failed: check_cid(getprop("ro.cid"),etc
Is it any way to install update? I remember last time I received OTA update after root, i did same method, moved update file to sd card root and applied update with CWM and everything worked but now i get cid error.
My phone is previously on O2, it was S-off, rooted and unlocked, at the moment it running all stock soft 1.45.206.2

Or you could just flash stock recovery, and then install the OTA.

I have recovery manager but cant find stock recovery for 1.45.206.2
Do you know which one to use?

bakili said:
I have recovery manager but cant find stock recovery for 1.45.206.2
Do you know which one to use?
Click to expand...
Click to collapse
I didn't use recovery manager, I used the manual way, by using ADB. So I have no idea.

Can someone help please? I dont understand why I cant get second O2 update. I have clockworkmod recovery back up, and I restored very first back up 1.45.206.1. After restoring back up, I got straight away notification for system update 1.45.206.2, which I managed update through sd root (by moving update file to sd card root), after 1.45.206.2 update I received another notification 1.50.206.1 which won't install, giving me cid error.
I even changed super cid 11111111, to original O2___001 cid, still no success.
I dont wont loose S-OFF.

I had little progress, by enabling signature verification in CWM recovery,
Now installation starts, progress bar reaches to quarter and then fails with signature verification again!

same problem with me, still can't solve, I have read and installed a lot of drivers,
debugging mode is all fine when device is on but when turned off debugging goes off detected by flashtool. SE wt19i user.

Superwipe and Flash ARHD.. its almost stock but runs better than stock. Be sure u have latest firmware.
Sensationaly sent from my Sensation.

bakili said:
Can someone help please? I dont understand why I cant get second O2 update. I have clockworkmod recovery back up, and I restored very first back up 1.45.206.1. After restoring back up, I got straight away notification for system update 1.45.206.2, which I managed update through sd root (by moving update file to sd card root), after 1.45.206.2 update I received another notification 1.50.206.1 which won't install, giving me cid error.
I even changed super cid 11111111, to original O2___001 cid, still no success.
I dont wont loose S-OFF.
Click to expand...
Click to collapse
Double check your CID. O2___001 doesn't make sense.
It should have 8 digits (lettters and/or numbers) including underscores (e.g., HTC__001).
Also, you won't lose S-Off with OTA update.

bakili said:
Hi guys,
I received today OTA update, but cant install it. My phone is rooted and has got Clockworkmod recovery. I tired move update zip file in sd card root and install zip from sdcard, i get following error > assert failed: check_cid(getprop("ro.cid"),etc
Is it any way to install update? I remember last time I received OTA update after root, i did same method, moved update file to sd card root and applied update with CWM and everything worked but now i get cid error.
My phone is previously on O2, it was S-off, rooted and unlocked, at the moment it running all stock soft 1.45.206.2
Click to expand...
Click to collapse
my best suggestion is to just remove CWM for a while and replace it with stock recovery, and then put it back again once you installed ICS. Refer this thread : http://forum.xda-developers.com/showthread.php?p=17830737

You CANNOT flash an official OTA without the stock recovery. You need to replace CWM with the stock recovery, AND remove root, to get the new OTA...

[Q] Updating to 4.1.1 OTA

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 )

[Q] Soft Bricked for the past 3 hours... need phone. Help this N00B

Last week I successfully rooted, unlocked my bootloaded and loaded the touchwiz 4.1 ROM. Because the GPS wasn't working and some other fairly bothersome glitches I decided to flash a different ROM, wanted to try CM10. Unfortuneatly, I didn't "read carefully" and just jumped in, trying to replicate my past success by following similar steps. So I booted into recovery to wipe and begin anew.
I used the native recovery, which I've now seen was a bad idea and should have used CWM but I don't know how to install CWM now because I can't load the OS. I originally used Casual to root and help me install 4.1 touchwiz on my Verizon GS3. After factory reset I attempted to install CM10 from the SD card and got the below mentioned error. My phone is stuck. I can only access the native recovery or ODIN mode (I have a mac so I can't use ODIN and Heimdall doesn't seem to want to play nice. Please help!! I need my phone for... life. I'm happy going back to stock if I need to but I'd love to run CM10.
"Verifying update package...
E:failed to verify whole-file signature
E:signature verifaction failed
Installation aborted"

sirknave said:
Last week I successfully rooted, unlocked my bootloaded and loaded the touchwiz 4.1 ROM. Because the GPS wasn't working and some other fairly bothersome glitches I decided to flash a different ROM, wanted to try CM10. Unfortuneatly, I didn't "read carefully" and just jumped in, trying to replicate my past success by following similar steps. So I booted into recovery to wipe and begin anew.
I used the native recovery, which I've now seen was a bad idea and should have used CWM but I don't know how to install CWM now because I can't load the OS. I originally used Casual to root and help me install 4.1 touchwiz on my Verizon GS3. After factory reset I attempted to install CM10 from the SD card and got the below mentioned error. My phone is stuck. I can only access the native recovery or ODIN mode (I have a mac so I can't use ODIN and Heimdall doesn't seem to want to play nice. Please help!! I need my phone for... life. I'm happy going back to stock if I need to but I'd love to run CM10.
"Verifying update package...
E:failed to verify whole-file signature
E:signature verifaction failed
Installation aborted"
Click to expand...
Click to collapse
I'd say your best bet is to get all of the ODIN parts and see if a friend has a PC with windows on it you can use for a bit. I dont know of another way.

As far as I know, you will have to flash stock image back with Odin, I don't think anything is ready for the Mac yet. I will be glad when it is, I have 1 as well.
If you don't have any other options, use Boot Camp and Odin will work fine.
Sent from my SCH-I535 using xda premium

Thank you all. Using a friends pc and Odin I was able to flash 4.1 touchwiz but I wasn't able to flash a recovery and keep root.
Sent from my SCH-I535 using xda app-developers app

Now that you have a working device, reroot, install cwm from play store and then make a nandroid backup and flash away. Also,be sure to back up for imei . happy flashing
Sent from my SCH-I535 using xda app-developers app

Nexus 5 OTA Update w/ custom recovery/root

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.