Hey all,
I have a rooted sprint galaxy nexus on stock ICS 4.0.4. When I rooted my phone CWM wasn't sticking and so the guide i was using said I had to change recoveryfromboot.p to recoveryfromboot.p.bak. So I did that. Now when I try to install the OTA update it boots into recovery and fails the install with the message: Failed whole package sign (or something like that). How can I update to the newest stock build without having to wipe everything?
Related
So I bought Nexus S from second hand recently mostly because it will get official ICS support from Google.
So because it's second hand buy, I really don't know if I'm using original bootloader, kernel, radio etc.
It's rooted (because I have Superuser app), I think it has stock 2.3.6 android (build number GRK39F) and kernel version 2.6.35.7-gf5f63ef, [email protected]#1.
Can someone who use stock android and original kernels confrime to me that this is right version?
I really want to update to ICS using incremental update which I found here (http://forum.xda-developers.com/showthread.php?t=1445635) but I'm affraid to don't screw something because of bad experience when I radio bricked my desire
Can I update it to ICS or I need to do unroot or something?
Just download the correct stock ICS rom for your device (if it is I9020T or I9023) ,put it on the SD root and then flash it using the stock or CWM recovery and be done with it (if you need the ICS)
most likely you won't be update by OTA because you are rooted (system file verification will fail)
just download stock ICS ROM and flash it ...
Ota will install fine if its a stock rom with just root. The update script basically checks that everything that should be there is there . If there is something else in there like su it don't matter.
flashing a new rom is the best way to go if you have cwm installed already
I succesfuly flashed ICS and first impressions are very good.
But I think I lost recovery...
jurvyx said:
I succesfuly flashed ICS and first impressions are very good.
But I think I lost recovery...
Click to expand...
Click to collapse
flash a CWM recovery via adb , or there is TWRP recovery in DEV section , which is very good .
I was running nexus s 4.0.3 on my phone i downloaded the kernel to overclock my nexus s but the kernel was of nexus s gingerbread i suppose
So my phone hanged and didnt boot up ....at that time i forgot to make bacup of my current rom so i ve downloaded a older ics(not official pre realse one) i flashed with it and it started everything worket except wifi and the problem of status 7 has begun i couldnt fix it so i went to samsung guys and they installed the 2.3.3 on my phone ... and now the main problem start
My nexus s is not able to accept any kind of update say it as a system update of i9023 2.3.6 or custom rom with status 7 error . I googled it a lot they say its a problem with the signature it download a proper signed file still it doesn't help it installs but not working properly even after doing wipe cache , dalvik cache so i googled more it says make no changes in phone and return it with stock system apps i did it again same problem while system update (screen hangs with android exclamatiory sign in a triangle) i then downloaded a stock rom of 2.3.3 for nexus s i9023 while installing it with the clockworld mod recovery 5.0.2(latest as far as i know) it starts install then says status 7 error.
To overclock my phone i have installed netarchy kernel for overclocking to 1.4 ghz....is it because of my kernel changed i am not able to install andy custom rom or system ota update from google
And theres one more thing i have changed the bootloader version accidently thinking it may work to i9020xxka3 i think which is the same for i 9023 and my baseband version is i9020xxkb3.
I have tried to install many signed versions of rom for my phone including 2.3.3 ,2.3.6 and ics 4.0.3 all stock downloaded from different websites but still not able to install any rom through clockworld mod recovery and any of the system update .
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!!
I have been trying to get my phone to update following the directions for the past year almost and have had no luck.
EDIT*: I am trying to do the OTA update that i am being prompted to do (9.16.6)
I am on:
Android Version 4.1.1
System Verison 9.1.41XT926
Bootloader: unlocked
Safestrap
I am trying to get to Android 4.3 but when I go to voodoo OTA rootkeeper and temp unroot then download and try and install the update my phone reboots like its starting the install but then shows the android the with the ! coming out of him then it restarts and upon restart it tells me that the update failed.
What am I doing wrong and how can I get these updates to work!
Thanks,
Tyler Hegamyer
There isn't an official 4.3. And if your trying to flash a custom 4.3 you need to be unlocked running a custom recovery.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
There isn't an official 4.3. And if your trying to flash a custom 4.3 you need to be unlocked running a custom recovery.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I currently have my bootloader unlocked and am running SafeStrap. What do i need to do from there, do i simpily just flash a new rom on a new rom slot in SS and ill be at 4.3?
TylerHegamyer said:
I currently have my bootloader unlocked and am running SafeStrap. What do i need to do from there, do i simpily just flash a new rom on a new rom slot in SS and ill be at 4.3?
Click to expand...
Click to collapse
i would suggest abandoning ss unless the rom you want is only supported through ss (rare but possible).
i would:
-disable ss
-use the 1.33 utility in the dev forum to update and return to the latest stock
-use the same utility to root
-use the same utility to flash a custom recovery
--boot into recovery and witpe data/cache/"data-media(cwm recovery specific)" to be sure everything is gone
-choose the rom of your chice from the dev forum and flash in recovery as directed by the rom's dev.
Don't use safe strap. Delete the partion and uninstall it. Use cwm or twrp. And might want to change the title then your not accepting a ota your flashing a custom rom.
Sent from my PACMAN MATRIX HD MAXX
I'm also having some troubles. Trying to apply the new update (rooted with stock 4.1.2) keeps resulting in "signature verification failed" in CWM. I have to then wipe the cache so it doesn't keep trying to reboot and apply the update. I've also tried unfreezing all the bloat in TitaniumBackup but got the same results.
Does anyone know a solution for this?
EDIT: I've also tried running OTA rootkeeper app and it still failed.
gf1723 said:
I'm also having some troubles. Trying to apply the new update (rooted with stock 4.1.2) keeps resulting in "signature verification failed" in CWM. I have to then wipe the cache so it doesn't keep trying to reboot and apply the update. I've also tried unfreezing all the bloat in TitaniumBackup but got the same results.
Does anyone know a solution for this?
EDIT: I've also tried running OTA rootkeeper app and it still failed.
Click to expand...
Click to collapse
the ota will not work through a custom recovery such as cwm, you need to put the stock recovery back on.
Hello! Recently purchased a used (but like new) S Relay off of Ebay. It came with 4.1.2 already installed.
Basically let me tell you a brief backstory: I started off by installing Custom Recovery (CWM PhilZ 6.07) using ODIN and backing a NANDroid Backup. Then flashed KitKat CM 11 from CWM (wanted to try it out but didn't like it more than Jellybean). So I restored my backup via custom recovery.
Then I tried unlocking the sim network from T-mobile so I can use this phone when I travel abroad (using the method in http://forum.xda-developers.com/showthread.php?t=2255892 ). But apparently I found this doesn't work except on the stock Ice Cream Sandwich rom. So I flashed the LH1 stock rom using ODIN. Then I did the unlock method and it appeared successful. (it recognized an AT&T sim I have without asking for an unlock code)
So long story short, I used the custom recovery again to restore to my stock version of 4.1.2 Jellybean. But my baseband version is still LH1. I want to update it to UVMA2. I tried using a zip to update it from LH1 to UVMA2. But it always fails and aborts. It gives me Error Status 7. Which from google apparently means the device name doesn't match the one on the zip package.
I also try installing other minor packages. Which all incur the same error 7. So I'm not really sure if I'm just a really stupid beginner. Or if I've messed something up when I went to Kitkat and back. Or perhaps when I downgraded to 4.0 to unlock the network....
I tried using this ( http://forum.xda-developers.com/showthread.php?t=2302599 ) guide to fix the packages by removing the initial device name check. Yet it still fails/aborts before trying to install.
Any help or insights for this beginner would be greatly appreciated, thank you
Edit: The device name should be "apexqtmo" apparently...
Was able to flash to UVBMC5 baseband. Is that perhaps the latest version? It appears to be one of the most recent from google.