Cant manually update to 2.3.1 - Nexus S General

Hi ive been trying to update my phone from 2.3 to 2.3.1 using the manual update and everytime i try i get this error:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
ive done a master reset wiped everything off mmy partition and it wont work. can someone help me out with that?

anybody out there that can help?

Update 2.3.1 issue
Hi everyone I have the same issue on my phone as well:
Model number: Nexus S
Android version: 2.3
Baseband version: I9020XXJK8
Kernel version: 2.6.35.7-g119403d [email protected]#1
Build number: soju-userdebug 2.3 GRH55 79397 test-keys
This is the error that occurs:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I even tried *#*#checkin#*#* and phone says it's up-to-date.
Please help me out with it in order to upgrade my phone to Gingerbread 2.3.1
Thanks in advance.

do you guys have CWM?

It will only install with stock recovery if ur using cwm
Sent from my Nexus S

It will install on CWM, just need to disable signature verification.

I have not changed to boot loader, or rooted the phone in any way. Only trying to get the 2.3.1 GRH78 fixes and Maps 5.0. I have done the OTA manually many times over the last 2 years on my G1 without having this issue.
Model number: Nexus S
Android version: 2.3
Baseband version: I9020XXJK8
Kernel version: 2.6.35.7-g119403d [email protected]#1
Build number: soju-userdebug 2.3 GRH55 79397 test-keys
FASTBOOT MODE
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - 3738F****
LOCK STATE - LOCKED
I downloaded;
a71a2082d553.signed-soju-GRH78-from-GRH55.a71a2082.zip
from android.clients.google.com
with md5sum = a35798d84104c7cb1d26d7946ce843fc
and renamed to update.zip and placed in root of SD card on NS.
The error I get is;
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
At first I though it was just me, but it sounds like others have the same issue.

SpookyTunes said:
I have not changed to boot loader, or rooted the phone in any way. Only trying to get the 2.3.1 GRH78 fixes and Maps 5.0. I have done the OTA manually many times over the last 2 years on my G1 without having this issue.
Model number: Nexus S
Android version: 2.3
Baseband version: I9020XXJK8
Kernel version: 2.6.35.7-g119403d [email protected]#1
Build number: soju-userdebug 2.3 GRH55 79397 test-keys
FASTBOOT MODE
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - 3738F****
LOCK STATE - LOCKED
I downloaded;
a71a2082d553.signed-soju-GRH78-from-GRH55.a71a2082.zip
from android.clients.google.com
with md5sum = a35798d84104c7cb1d26d7946ce843fc
and renamed to update.zip and placed in root of SD card on NS.
The error I get is;
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
At first I though it was just me, but it sounds like others have the same issue.
Click to expand...
Click to collapse
you tried redownloading and verifying the MD5

Should your build be mentioning test keys?
I would think that is the reason you can't upgrade.

Each time I download it using wget in bash, I get the same md5sum. I have re-copied it to the SDCard several times as well. I was concerned with the "userdebug" and "test-keys" in the Build number, and wounder if someone at BestBuy had rooted the phone before I got it, but if others are having the same issue without modifying their phones?

It's not a root thing, it's a pre-release thing.
I would try flashing it via CWM with verification turned off personally, should skip that check then.

I got a bnib phone with a Dec 18 build date that came with the test signed release. The Ota would not flash as a result. I had a nandroid from a release grh55 that I flashed over it and it then received the OTA and flashed no problem. It seems that there are definitely some devices other than the one I got being sent out with what appears to not be the final release.
Sent from my Nexus S using XDA App

Rusty! said:
It's not a root thing, it's a pre-release thing.
I would try flashing it via CWM with verification turned off personally, should skip that check then.
Click to expand...
Click to collapse
This won't work. The update script will complain because the build fingerprint isn't grh55 (I tried that with my test keys phone). You could unlock, flash the su binary, edit build.prop and try it then.
Sent from my Nexus S using XDA App

Samsung site: (Manufactured: 12/18/2010)
Just took the phone back to BestBuy and did an exchange.
This one had
Build number: GRH55
I got the 2.3.1 update less than 5 minutes after I powered it on.
Build number: GRH78
Glad I took it back. This one with 2.3.1 resolved most of the issues I had.
Thanks for the help ;-)

SpookyTunes said:
Samsung site: (Manufactured: 12/18/2010)
Just took the phone back to BestBuy and did an exchange.
This one had
Build number: GRH55
I got the 2.3.1 update less than 5 minutes after I powered it on.
Build number: GRH78
Glad I took it back. This one with 2.3.1 resolved most of the issues I had.
Thanks for the help ;-)
Click to expand...
Click to collapse
yep did the same thing had to make up some stuff like google maps wouldnt update and stuff
as soon as i turned on the new one bam it was there
mine had the test key thing too
thanks for the help guy

Ok now I'm having the same problem as my stupid Nexus has that debug OS in it. Since the phone shipped to Turkey, I have no chance to replace it. My previous Nexus One had also problems, so this is the last time I'm buying a Google Phone.
Anyway, can you help me what to do? Should I root the phone?

You should install ClockworkMod recovery, and restore this NANDroid backup to get back on track.

Which means I have to root right?

Technically no, unlocking the bootloader doesn't automatically root the phone.

Can I install Clockwork recovery without rooting the phone?

Related

[Q] Rom Manager- Not able to verify whole-file signature

Hey guys,
I am pretty new with the android OS but I am trying my hardest to read up on it and wrap my head around it. so please bear with me.
I have a verizon fascinate that was purchased a week ago and I rooted it.
I have the Rom Manager installed and the OS is running smoothly. I was going to install a custom Rom on my phone but when I tried to back up the current Rom using the Rom manager. it will boot into the Android system recover (2e) and this is what shows up on my phone:
-- Install from Package...
Finding update package...
Opening update package...
verifying update package...
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
with that massage I dont think that I have my current Rom backed up any where...
does any one know how I can get passed this step?
I dont have much knowledge about the android operating system so if some one can help me out with this it would be freaking awesome!
---
I have not installed anything crazy, Rooted with the One click root. and Used the Titanium back up software.
You have to flash the Clockwork kernel/recovery onto it to run the update.zip that activates the backup stuff. See here.
MAKE SURE YOU FLASH INTO THE "PDA" SECTION OF ODIN AND NOT THE "PHONE" PART. "Phone" will brick your device.
Works perfect now!
Thank you very much!
i'm having the same problem, but i've already flashed clockwork? did i miss something?
fail fail
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
Runing pt Litening_Rom_v1-5.rar tried Litening_Rom_v3-2.rar same isue .
Rom Manager (pro) fails to backup every time. When useing CWM (comeing with Litening_Rom no probelem at all)
And today I tried Litening_Rom_v4.1 same problem
jesterdallas said:
i'm having the same problem, but i've already flashed clockwork? did i miss something?
Click to expand...
Click to collapse
Which version of cwm are you using, and what are you trying to flash?

(Problem) OTA Update via Galaxy Tab 2 10.1

Hi, i am from the philippines. just a while ago, i received a firmware update notification via my galaxy tab 2 10.1 (running a rooted stock rom [ICS 4.0.3 EXWALE2]. I succesfully downloaded the whole package, about 259mb, and did the installation afterwards. however, got the following errors in recovery mode:
CWM-based Recovery 5.5.0.4
E: Invalid command argument
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted.
has anybody here had experienced the same problem? the fix, if there is?
Another thing: I could not find the downloaded update package in my phone or just do not know where find it.
reywal said:
Hi, i am from the philippines. just a while ago, i received a firmware update notification via my galaxy tab 2 10.1 (running a rooted stock rom [ICS 4.0.3 EXWALE2]. I succesfully downloaded the whole package, about 259mb, and did the installation afterwards. however, got the following errors in recovery mode:
CWM-based Recovery 5.5.0.4
E: Invalid command argument
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted.
has anybody here had experienced the same problem? the fix, if there is?
Another thing: I could not find the downloaded update package in my phone or just do not know where find it.
Click to expand...
Click to collapse
I suppose CWM blocks any OTA updates, I've tried download the update twice only to get those message on CWM.
Try download the update via Kies, I just successfully did it.
However the update size it's a lot bigger than 250MB and you're gonna lose your root privileges.
cliffflip said:
I suppose CWM blocks any OTA updates, I've tried download the update twice only to get those message on CWM.
Try download the update via Kies, I just successfully did it.
However the update size it's a lot bigger than 250MB and you're gonna lose your root privileges.
Click to expand...
Click to collapse
thanks, ill try out what you said.
EDIT: (fixed)
1. I updated my tab by flashing the stock firmware (JB 4.1.1) here-->> http://forum.xda-developers.com/showthread.php?t=1704668
2. Then regained my root privileges here -->> http://forum.xda-developers.com/showthread.php?t=1957165

help unable to update nexus 7 to 4.2.2

I get notification to update from 4.2.1 in to 4.2.2 but when I try i get this error
Model:
"Legal information
FCC ID: MSQMEBYUT
ICI 3568A-ME37OT
Model: ME370T
Model number
Nexus 7
Android version
4.2.1
Kernel version
3.1 .10—g22b4fcd
android—[email protected] #1
Fri Nov 2 10:55:26 PDT 2012
Build number
JOP4OD "
error:
"CleckworkMod Recovery v6.0.1.0
install Zip from sdcard
wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
ClockworkMod Recovery v6.0.1.0
E:lnvalid command argument
Finding update package...
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("/systemfapp/Phonesk
y.apk", "f5624ba46e409925fc93e0d4222c9a5bf37defb4", "
a?d39ad?438b0fb634?033a75b5d5054aae9bfa8“)
E:Error in Xcachef6ece895ecb23.signed-nakasi—JDQ39-fr
om—JOP40D.6ece895e.zip
(Status ?)
Installation aborted. "
Please read the forum guidelines about searching before posting, as it is completely evident that you did not.
Then, search for "Status 7" and read every one of those threads from start to finish.
As you have just discovered, the OTA updates are not guaranteed to work on rooted phones.
If you search and read you will find plenty of suggestions.
When you have finished that, come back here and apologize for starting yet another thread about an issue which is substantially identical to dozens of other threads.
good luck

[Q] How to install new small security patch on JB 4.3

I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.
I will appreciate any help.
I have this too
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret
rookie8155 said:
I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.
Click to expand...
Click to collapse
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page
bcw1000 said:
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret
Click to expand...
Click to collapse
Yes, I have also installed ClockworkMod Recover v6.0.2.3 and running stock ROM as well. . If this update is available as a zip file then we can install it. It should not be just two of us having this issue. Everyone who rooted phone should have same issue.
HeyyMyNameIs said:
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page
Click to expand...
Click to collapse
Thanks for pointing towards the right direction. I tried to side load the zip but it failed. I will post the question in the other thread.

[Q] I9505G OTA Upgrade Fails

I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.
Yes you'll need to flash original FireWire with Odin but before proceeding with the flash run triangle away it should be ok then
Sent from my GT-I9505 using Tapatalk
FireWire? What's that? I don't think I flashed anything like that.
ruidh said:
FireWire? What's that? I don't think I flashed anything like that.
Click to expand...
Click to collapse
I think he means "Firmware" :highfive:
ruidh said:
I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.
Click to expand...
Click to collapse
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE
Thanks. I'll give that a try.
Joku1981 said:
I think he means "Firmware" :highfive:
Click to expand...
Click to collapse
I'm not sure about Odin here. I never altered the stock recovery.
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE
Click to expand...
Click to collapse
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4
ruidh said:
I'm not sure about Odin here. I never altered the stock recovery.
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4
Click to expand...
Click to collapse
It's not my problem if you don't know read.
I followed Method 2. I see what you're saying now.
None of these upgrade methods worked. I still had assert failures. I removed SuperSU after restoring all changes I made to /etc.
Somehow this morning the phone failed to connect to data services. Several apps failed when they tried to access the network.
I eventually reflashed a 4.4.3 rooted image from here http://forum.xda-developers.com/showthread.php?t=2772043 and restored my Titanium Backup.
OTA upgrade to 4.4.4 succeeded after turning of SuperSU and reverting my change to \etc\permissions

Categories

Resources