Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
smoke1 said:
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
Click to expand...
Click to collapse
It's normal you can't flash OTA because you have a custom recovery. You need stock recovery for that. You can download a factory image from Google, extract it and flash the recovery inside using fastboot.
https://developers.google.com/android/nexus/images#soju
ALSO, stop using Odin. There's no need to use Odin or nearly on Nexus S. This thing is nearly unbreakable and you have more chances of breaking stuff with Odin than anything else.
thanx for quick replay
flashed factory GB 2.3.6 straight away using sdk tools
now will root it and install custom clockwork recovery to prevent from automatic OTA updating to lagy ICS
Use FOTAKill instead,
http://forum.xda-developers.com/showthread.php?t=1579154
Thanx for good advice. Installed it allready.
Sent from my Nexus S using xda premium
Related
I dont know if any similar stuffs are around...
so
I went from GRI40 to FRG33 using PASSIMG, rooted with z4, and then I tried to use the original recovery to flash update.zip of a pre-rooted GRI40
it says:
-- Install from sdcard...
Finding update package...
Verifying update package...
E:signature verification failed
Installation aborted.
why does this happen?
I saw some others talking about custom recovery, but how to install/flash them
I don't prefer cmd but pls, post solutions
another thing is, I saw another developer mentioning using su.zip to root stock GRI40
how does that work? how to do that?
hope some of you can help me
so my phone is rooted and have downloaded the darkey Rom and next Rom manager but when i go to recovery mode and try to update the zip file its giving error saying "signature verification failed" so what's the reason and how to solve it my galaxy s is running on 2.3.3 firmware xxjvk
Hey this is my first time posting - I have a rooted Rogers Samsung Captivate i897 that I upgraded to Gingerbread 2.3.4 in November (with an AT&T based ROM). I am trying to upgrade the firmware to the new ICS 4.0.3 that is now available for this model as I am looking for something new.
So, I did some research and followed the directions that were posted (got ROM Manager, downloaded nightly .zip files & GApps). I then tried to back up my ROM using ROM manager (didn't work but thats OK I have the ROM file on my PC). And did the factory restore/cache wipe and tried to flash the .zip files from my SD and it didn't work.
Here is what it says when I try to flash:
"E: failed to verify whole-file signature"
"E: signature verification failed"
Question 1) What could be causing this error?
Question 2) Should I try to flash a stock ROM first before attempting to flash ICS?
Question 3) do I really need to use ROM Manager?? Is there another method available (flashing from PC from Odin)?
I am hesitant about doing this on the fly because when I updated to Gingerbread in November I had a good scare with my phone - soft bricked it, fixed that, and then got it stuck in a boot loop, then had issues with boot logo conflict between Rogers a AT&T. I was out of a phone for about a day working madly to fix it. I would like to avoid it again at all cost.
Phone Information:
Firmware Version: 2.3.4
Baseband Version: I897UCKH3
Kernel Version: 2.6.35.7-I897UCKH3-CL461307
Build Number: GINGERBREAD.UCKH3
Please help I appreciate it!!
Hi Guys,
I have a Motorola Xoom 32Gb
Android ver. : 4.0.4
Kernel ver : 2.6.39.4-g42a0480
[email protected]
I receive lately a message to upgrade but when i chose yes i got this error message after some minues :
Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8)
Finding update package
opening update package
verifying update package
E: failed to verify whole file signature
E:signature verification failed
Installation aborted
What shall i do ?
Thanks in advance for your help.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
if it's an official update and you're running stock, you must run a stock recovery to update
matt4321 said:
if it's an official update and you're running stock, you must run a stock recovery to update
Click to expand...
Click to collapse
Thanks.
How shall i proceed ?
Trying to install a new rom (cm-12-20150113-unofficial-n8013.zip) But I get this message:
"
Finding update package...
Opening update package...
Installing update...
Warning: No_filecontextsThis package is for device: c0, p4notewifi, p4notewifiww, n8014, GT-N8013; this device is p4noterf.
E:/Erron in /external_sd/cm-12-20150113-unofficial-n8013.zip
(Status 7)
Installation aborted."
I can assure you, my tablet is the n8013... Why am I having this error? How can I fix it? This error also occurred while trying to install the BlissPop rom as well... I don't understand WHAT I'm doing wrong?
Thanks,
Kris.
Make sure you're using the latest custom recovery. Try redownloading the ROM.
I also get a STATUS7 trying to flash CM12.1 with CWM 6.0.1.1
I have yet to try TWRP but I need a TAR.MD5 packaged image, which I'm having trouble finding.
I'd run into this problem as well, and it actually has to do with your version of TWRP (at least to my knowledge). I was actually trying to flash a custom rom, knowing fully well that my device was GT-N013, when it gave me the error. Turns out, I flashed the recovery for the Gt-N8000 model.
As far as I know, GT-N8013 and p4notewifi are the same device, but considering your error said that "this device is p4noterf," flash the latest version of TWRP for either GT-N8013 or p4notewifi (specifically). Then try reflashing the ROM.