Database Info

signature verification failed during OTA update for JB

Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks

d960 said:
Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks
Click to expand...
Click to collapse
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.

You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.

jayjay3333 said:
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.
Click to expand...
Click to collapse
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?

albundy2010 said:
You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.
Click to expand...
Click to collapse
Thanks for education. Still pretty new on this...

d960 said:
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?
Click to expand...
Click to collapse
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:

jayjay3333 said:
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:
Click to expand...
Click to collapse
Thanks. I managed to update to JB following the guide you are refering to and also the steps you took (i.e., doing OTA update). In general it went smooth but I do encounter some issues that I want to ask the OP of that thread.

[Q] Stock w/root 4.1.2 Update question

Greetings, all!
A friend of mine has a VZW GS3, which I rooted for him a few months ago using this method: http://forum.xda-developers.com/showthread.php?t=2046439
Last week he got the 4.1.2 OTA. When he allows it to install, this what he gets:
Install Untrusted Package? THIS CANNOT BE UNDONE.
-No
-Yes - Install untrusted zip
_ +++++Go Back+++++
ClockworkMod Recover v6.0.2.3
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed.
Click to expand...
Click to collapse
I've looked through that thread a bit, but I can't seem to find anyone having the same issue. So my question is can he just install the update this way and be alright? Also, will it need to be rooted again?
Thank you so much for any help!

evergamer said:
So my question is can he just install the update this way and be alright? Also, will it need to be rooted again?
Click to expand...
Click to collapse
After reading about people having problems losing root after the OTA update, I decided to not to take it, and instead flashed a stock rooted 4.1.2 image, per this thread: http://forum.xda-developers.com/showthread.php?t=2178482
Since I had no plans to do any theme mods, I used the Odex version. Scroll down to post #3 and grab the 4.1.2 modem and rpm as well (which are part of the OTA). These can be flashed in the same recovery session as the update.
Also, since I was only going from 4.1.1 to 4.1.2, I dirty flashed without wiping anything, and had no problems.

SempaiMatt said:
After reading about people having problems losing root after the OTA update, I decided to not to take it, and instead flashed a stock rooted 4.1.2 image, per this thread: http://forum.xda-developers.com/showthread.php?t=2178482
Since I had no plans to do any theme mods, I used the Odex version. Scroll down to post #3 and grab the 4.1.2 modem and rpm as well (which are part of the OTA). These can be flashed in the same recovery session as the update.
Also, since I was only going from 4.1.1 to 4.1.2, I dirty flashed without wiping anything, and had no problems.
Click to expand...
Click to collapse
Thanks for the info. I haven't dirty flashed my phone in ages. Do you have to clear the cache or anything? Also, will settings/appdata be lost?

evergamer said:
Thanks for the info. I haven't dirty flashed my phone in ages. Do you have to clear the cache or anything? Also, will settings/appdata be lost?
Click to expand...
Click to collapse
Dirty flash is just clear cache and dalvik cache, you will not loose app/system settings.

evergamer said:
Do you have to clear the cache or anything? Also, will settings/appdata be lost?
Click to expand...
Click to collapse
I cleared absolutely nothing, and all settings and app data were unchanged. (Actually, some bloatware that I had previously uninstalled was returned.) My thinking was that the OTA was only a small update that wouldn't screw up settings and data. Of course, I did a full nandroid backup in case things didn't work.
Also, the stock rooted 4.1.2 thread says that the vzw installer is removed. However, after flashing it, I noticed there was still an "SDM 1.0" service still on my phone, which I think has something to do with updates, and I froze it with Titanium Backup. (Since then, I've flashed CleanROM 6 R2, and the SDM 1.0 is gone.)

buhohitr said:
Dirty flash is just clear cache and dalvik cache, you will not loose app/system settings.
Click to expand...
Click to collapse
K, cool. I don't remember the last time I flashed like that. I always flash clean with AOKP.
And 724mb for a ROM? Seems huge.

evergamer said:
K, cool. I don't remember the last time I flashed like that. I always flash clean with AOKP.
And 724mb for a ROM? Seems huge.
Click to expand...
Click to collapse
Full bloated rom is about 1gb, if you debloated you should have smaller rom size, so 724mb is about OK.

(Q)How to stay up to date while rooted?

Rooted with CWM as recovery. Shield Tablet has OTA update but obviously can't install with CWM. What is the simplest way to stay up to date and keep root?
Sent from my SHIELD Tablet using xda premium

Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium

Scoobydumb said:
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Click to expand...
Click to collapse
That's not the way to go at all.
Whenever there's an update, flash the incremental OTA file HERE.
Flashing the stock recovery will not allow taking OTA's.

thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again

Scoobydumb said:
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Click to expand...
Click to collapse
Um, just flash it in TWRP or CWM, only need to flash cache and dalvik cache, but that's optional.

Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.

Singularity_iOS said:
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Click to expand...
Click to collapse
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.

FoxyDrew said:
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
Click to expand...
Click to collapse
Ok thanks. One more question. How would I go about checking the rom version? Unless I'm missing it I can only see the Android version, which is 5.0.
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.

Singularity_iOS said:
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Click to expand...
Click to collapse
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.

Wouldn't the tablet be wiped then? And if this is the case everytime can't I just keep the stock recovery and sideboard a custom one?

Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work

NaminatoR1254jaime.sier said:
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
Click to expand...
Click to collapse
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.

perky nerky said:
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
Click to expand...
Click to collapse
On my previous instructions I pointed out to (after flashing ota) to reflash custom rec and supersu.
NaminatoR1254jaime.sier said:
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Click to expand...
Click to collapse
With twrp I do it literally after flashing full ota. I leave recovery to reboot to system right when Im done flashing everything.

[Q] Install CM12S Update with TWRP recovery?

Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?

6andro said:
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
Click to expand...
Click to collapse
Just follow this...
STEPS:
1. Download http://builds.cyngn.com/cyanogen-os...263178b74/cm-12.0-YNG1TAS0YL-bacon-signed.zip
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot

Shankar9822 said:
Just follow this...
STEPS:
1. Download [lurl]
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Click to expand...
Click to collapse
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?

Update twrp first then flash. You will not loose personal data when doing the wipe.
Sent from my A0001 using XDA Free mobile app

6andro said:
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Click to expand...
Click to collapse
I think you are using the wrong version of TWRP.
http://dl.twrp.me/bacon/
Use the above link, download the latest version 2.8.6.0-bacon.img and flash it...

I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?

striker280 said:
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
Click to expand...
Click to collapse
It's normal for the stock recovery to be flashed during an OTA update. Yes you can flash it again. No it won't relock your bootloader.
Transmitted via Bacon

Can I use a flashable zip instead of updating through ota?

My phone is currently on 13.0-ZNH0EAS26M and I want to update to cm-13.0-ZNH0EAS2JK as it is the incremental update. I rooted my phone and have TWRP. Before, I had to redownload my phone's current images and flash it thru fastboot to go back to "stock" and update my phone thru OTA. Now, I plan on doing that again but I can't find the images for 13.0-ZNH0EAS26M, all I could find are cm-13.0-ZNH0EAS2JK, can I just download the flashable zip and just go from there? Will I lose any data from this? Thanks

FadedAce said:
My phone is currently on 13.0-ZNH0EAS26M and I want to update to cm-13.0-ZNH0EAS2JK as it is the incremental update. I rooted my phone and have TWRP. Before, I had to redownload my phone's current images and flash it thru fastboot to go back to "stock" and update my phone thru OTA. Now, I plan on doing that again but I can't find the images for 13.0-ZNH0EAS26M, all I could find are cm-13.0-ZNH0EAS2JK, can I just download the flashable zip and just go from there? Will I lose any data from this? Thanks
Click to expand...
Click to collapse
If you have TWRP you can just flash to the latest cm-13.1-ZNH2KAS1KN directly using the signed flashable zip found here.
Its the full ROM so there is no need to go from OTA to OTA till the latest.
Simply download, go to recovery and wipe system, dalvik and cache then flash the ROM and you're on the latest build

please close this thread as i already flashed it and everything is ok. thank you

Renosh said:
If you have TWRP you can just flash to the latest cm-13.1-ZNH2KAS1KN directly using the signed flashable zip found here.
Its the full ROM so there is no need to go from OTA to OTA till the latest.
Simply download, go to recovery and wipe system, dalvik and cache then flash the ROM and you're on the latest build
Click to expand...
Click to collapse
Thank you sir, please disregard the previous message as i thought nobody replied to my post. Thank you very much