Trying to Update S3 : Signature Verification Failed - T-Mobile, Samsung Galaxy SIII

My girlfriend recently acquired a used SGH-T99, running 4.0.4, stock everything, not rooted.
Every time I try to update the phone (using the settings, about device, etc. method), it downloads the package fine but when trying to install it I receive this message:
CWM-based Recovery v5.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.
I was going to attempt to update the phone using Kies, but the phone will not connect to my PC, or her MAC. I've tried multiple cables that I know work, but the phone doesn't even react like its plugged into something.
I'm unsure what my next step should be, any ideas?

If it has CWM, the OTA isn't going to work. You will need to try another rout. MobileOdin may be an option if you don't want root. I'm not sure if that updates the recovery though. Do a search and you should be able to find the thread.

Download Odin on your PC and check if it detects it, if so you can download the new firmware and flash it in Odin

You have to be 100% stock for the Ota to work. I do not recommend updating with mobile Odin though. Highly recommend flashing full firmware via Odin as suggested above.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
---------- Post added at 04:16 PM ---------- Previous post was at 04:15 PM ----------
Don't forget to unlock before you update BTW.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Same Problem on my SGH T999
Facing the same problem for my SGH T999; couldn't upgrade myself to the custom ROM, Despite I rooted the device.
Earlier I got
E: failed to verify whole-file signature
E: signature verification failed
Where as the 1st error message is no more observed; after I removed the Assert line in "updater-script" file of META-INF folders of new ROM.
But continue to get the same 2nd message.
When I go to recovery mode of TWRP recovery; my device is not getting deducted ID: COM field, eventually end up getting the message as processed the file (0 Successed/0 Failed).
So I have to live with the Old 4.3 version; where majority of the Apps these days not supporting this version of android.

Related

need help

ok I have done the manual root method, (by zikronix ) was getting radio_pu errors but i had root access and s-off, could not use a rom it would error out, i had to use the stock 3.30 pc36img.zip from (aegiswa
http://www.morninglion.com/tp2martin...209_signed.zip from ) to make my phone work. So phone is working and I tried flashing (fresh, calkulins) rom, every time i load into recovery it says (E: invalid command argument), i have a hw 003, im glad i have root. but i cannot use a custom rom and when this new update keeps asking me to install it fails, and when i tried to dl the one provided and apply through recovery it failed and i had to reload the pc36img
this is becoming a hassle. can anyone help!! also when i make a recovery point just 30 min ago after reinstall and removing base apps, my phone restarted failed and i had to reload again.
i get this when loading a rom
assert failed: write_raw_image("/tmp/boot.img". "boot")
E:error in /sdcard/fresh-evo-3.4.0.1.zip
status 7
install aborted
you need to post in the right forum...
kc_sheets said:
i get this when loading a rom
assert failed: write_raw_image("/tmp/boot.img". "boot")
E:error in /sdcard/fresh-evo-3.4.0.1.zip
status 7
install aborted
Click to expand...
Click to collapse
Try downloading the file again; it may be corrupted. Did it give you the same exact error when you tried Caulkin's rom?
i tried to delet this post and i did a new one in the right area,
to the last question no the calkulins did this
e: symlink /system/bin/lsmod
e: failure at line 10: aymlink toolbox system:bin/lsmod
i was told i may have bad blocks and to get a new phone!! how can this be determined and how do i get it replaced??

1.28.401.9 OTA problem with unlock/root?

I'm unable to install the 1.28.401.9 OTA update and was wondering if anyone else has the same issue - or whether I'm missing something obvious.
My 1X is unlocked and rooted but still running stock.
On completion of the OTA download I select to install and it boots into CWM Recovery with "Installation Aborted" at the bottom and
"E: Unknown volume for path [PATH] E: Can't mount INTERNALSDCARDownload..." etc.
So I select 'Install from SD card'>'choose zip...'> then go to Downloads and select the update file and get:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
So I disable signature verification, try again and get:
assert failed: check_cid(getprop("ro.cid")...
Then a string of 8 digit numbers and alphanumeric codes and finally
E: Error in /sdcard/Download...[PATH]
(Status 7)
Installation aborted
Anyone have any ideas why it's not working?
same problem......
Me too
Kevin & Orel - just to be sure, can you confirm that you are rooted and running stock as well please?
Yep unlocked and rooted, but running stock. Once in CWM Recovery I see the same errors as you.
yes before I was sfr version and my htc is root & recovery & stock htc .....
Reinstall stock recovery
Sent from my HTC One X using XDA
tested stock recovery, but nothing happens ....
if I try to flash the uptade I receive an error message.
Appears when I have the stock recovery, I can not access the recovery to flash, I have a black page with a phone 3 green arrow and then a red box ...
And people told me I was silly to tell people NOT TO TRY AND RUN AN OTA ON A ROOTED PHONE!!!
Seriously, guys. Historically it's been nothing but problematic trying to apply an OTA to a rooted phone. If you want it THAT bad go custom
orel28 said:
tested stock recovery, but nothing happens ....
if I try to flash the uptade I receive an error message.
Appears when I have the stock recovery, I can not access the recovery to flash, I have a black page with a phone 3 green arrow and then a red box ...
Click to expand...
Click to collapse
Did you relock?
http://forum.xda-developers.com/showpost.php?p=25002854&postcount=736
You need stock recovery to apply OTA...
You dont flash it yourself from recovery!!!
The update program does that
i just flash .zip stock ...
---------- Post added at 07:02 PM ---------- Previous post was at 06:54 PM ----------
how to get back to a stock rom compatible?
Where can I find the .zip file to install stock recovery?
Squidinker said:
I'm unable to install the 1.28.401.9 OTA update and was wondering if anyone else has the same issue - or whether I'm missing something obvious.
My 1X is unlocked and rooted but still running stock.
On completion of the OTA download I select to install and it boots into CWM Recovery with "Installation Aborted" at the bottom and
"E: Unknown volume for path [PATH] E: Can't mount INTERNALSDCARDownload..." etc.
So I select 'Install from SD card'>'choose zip...'> then go to Downloads and select the update file and get:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
So I disable signature verification, try again and get:
assert failed: check_cid(getprop("ro.cid")...
Then a string of 8 digit numbers and alphanumeric codes and finally
E: Error in /sdcard/Download...[PATH]
(Status 7)
Installation aborted
Anyone have any ideas why it's not working?
Click to expand...
Click to collapse
I have the same problem....
After i restore the first rom my phone comes i dont get the error.....
1.28
kevin_d said:
Yep unlocked and rooted, but running stock. Once in CWM Recovery I see the same errors as you.
Click to expand...
Click to collapse
Same problem over here!!!
broncogr said:
You need stock recovery to apply OTA...
You dont flash it yourself from recovery!!!
The update program does that
Click to expand...
Click to collapse
+1 that
1. Download the OTA using the handset
2. Flash stock recovery (there's a download link in the CWM thread iirc)
3. Reboot
4. Go to Settings -> About -> Software Updates -> Check now
Assuming you already downloaded it, you'll be prompted to install it
5. Once the OTA update runs (it reboots twice) reboot into fastboot mode and reflash CWM
CWM can't flash the OTA and I personally didn't have to relock my device (It's not an RUU update)
Flash RUU DONT root and try again...
Once updated root again
amacrobie said:
2. Flash stock recovery (there's a download link in the CWM thread iirc)
Click to expand...
Click to collapse
Where can I find this download?
http://loadbalancing.modaco.com/download.php?file=endeavoru_recovery_signed.img
Squidinker said:
endeavoru_recovery_signed.img
Click to expand...
Click to collapse
Sorry, but how do I load this file?

Samsung Galaxy Ace 2 x Updating, Signature verification failed

Hello all. First off I'm sort of new to the Android rooting scene as I have only rooted my phone and nothing else.
I've recently had my phone prompt me to update. So naturally I hit "install" and let it restart and boot into download mode but, after it goes into CWM it says this;
Code:
CWM-based Recovery v5.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
I can provide the file it's trying to update from if needed, XDA doesn't like me posting links as a new user.
Naturally I thought I should boot up my phone on Odin and just put the Update.zip into the PDA slot. But I'm worried I may brick my phone as I really have no certain idea of what I am doing here.
If anyone could please offer me some support on updating my phone, it would be greatly appreciated. The 3 hour postpone messages are really starting to piss me off.
Please excuse my ignorance and thank you in advance.
if you have CWM you cant install an OTA software update. you must use the original (stock) recovery. also you will use root when you do an OTA update. you could try OTA rootkeeper to keep the root but ive never tried it.
use odin + later firmware.

[Q] Signature Verification Failed

I can't figure this out for the life of me. I'm trying to flash the regular old stock firmware on my SM-P600 through Odin 3.09. I'm using "P600UEUCOB1", the Cellular South version (from sammobile.com).
Problem
It flashes great in the Download screen but once it reboots to finish the update, I get this error:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Afterwards, if I reboot the system anyway, it still works...mostly. I get a ton of force closes, and every fifteen minutes or so, the tablet crashes and restarts.
What I've Tried:
Using the stock USB cable that came with the tablet
Using a couple other USB cables
Using multiple USB ports
Reinstalling Samsung drivers
Wiping data before flashing
Unrooting and wiping data before flashing
Flashing older firmwares (NK2 and ND2)
Using Odin 3.07 instead of Odin 3.09
I get the same results each time: "signature verfication failed" and a half-usable tablet.
I'm out of ideas. Anyone have any suggestions?
Btw, if it helps, I'm comfortable with doing heavy stuff like Terminal commands or coding.
GreenRaccoon said:
I can't figure this out for the life of me. I'm trying to flash the regular old stock firmware on my SM-P600 through Odin 3.09. I'm using "P600UEUCOB1", the Cellular South version (from sammobile.com).
Problem
It flashes great in the Download screen but once it reboots to finish the update, I get this error:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Afterwards, if I reboot the system anyway, it still works...mostly. I get a ton of force closes, and every fifteen minutes or so, the tablet crashes and restarts.
What I've Tried:
Using the stock USB cable that came with the tablet
Using a couple other USB cables
Using multiple USB ports
Reinstalling Samsung drivers
Wiping data before flashing
Unrooting and wiping data before flashing
Flashing older firmwares (NK2 and ND2)
Using Odin 3.07 instead of Odin 3.09
I get the same results each time: "signature verfication failed" and a half-usable tablet.
I'm out of ideas. Anyone have any suggestions?
Btw, if it helps, I'm comfortable with doing heavy stuff like Terminal commands or coding.
Click to expand...
Click to collapse
Hmm.. It seems to try and flash stock but fails. Like an update package. Is reactivation lock off first shown here. If that doesn't work, then the only thing I can think of is installing twrp and flash a zip based Rom. Like this http://forum.xda-developers.com/showthread.php?p=52058286 I hardly use Odin so yeah. Hope this helps!
DUHAsianSKILLZ said:
Hmm.. It seems to try and flash stock but fails. Like an update package. Is reactivation lock off first shown here. If that doesn't work, then the only thing I can think of is installing twrp and flash a zip based Rom. Like this http://forum.xda-developers.com/showthread.php?p=53202351. I hardly use Odin so yeah. Hope this helps!
Click to expand...
Click to collapse
Thanks for replying! I don't have anything like that on my Odin screen. I've attached what mine looks like.
Do you mean you use something besides Odin? If so, what do you use? I'd love to be able to do something under Linux. I've tried Heimdall but can't figure out how to fix the weird udev errors.
GreenRaccoon said:
Thanks for replying! I don't have anything like that on my Odin screen. I've attached what mine looks like.
Do you mean you use something besides Odin? If so, what do you use? I'd love to be able to do something under Linux. I've tried Heimdall but can't figure out how to fix the weird udev errors.
Click to expand...
Click to collapse
I've only used Odin to root my device. That's about it. If I ever need to restore, I just make a custom stock rom to flash in twrp since Odin seems to give me problems. Looks like some devices doesn't have reactivation lock. Have you tried factory resting after flashing in Odin and before also? The last thing I can think of is using Samsung kies to restore

Phone getting stuck while booting with micromax logo

My micromax android one phone is stuck during boot with micromax boot logo. It has 5.1.1 android version with build number LMY47V.
To recover this, I am trying to flsah rhe ROM with this OTA - d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7.zip
But I am getting below error:
Can't install this package over newer build
E:Error in /sideload/package.zip
However, in file ..\d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7\META-INF\com\google\android\updater-script, I removed the line which checks for newer build. But with that I am getting now following error:
E:Failed to verify whole-file signature
E: signature verification failed
IS there any way to avoid this signature problem.
Please help find OTA which could be flashed on my phone or any other suggestion.
I tried putting twrp recovery which requires device to be in debugging mode. Since my device is not booting to that stage, I skipped that part and tried if via other fastboot commands, it will be done or not. But this also fails as the device remains in default recovery.
I tried flashing through SP Flash tool also, but there it is not able to detect the device.
Please let me know if something else can be tried. Appreciate any help on this.

Categories

Resources