Hello everyone,
I have read several forums regarding the new update and decided to attempt OTA with VooDoo's rootkeeper running (and backups made of course!)
I have dowloaded the update seveal times and everytime I get the error "verification signature failed"
Any suggestions to move past this?
BigJRules said:
Hello everyone,
I have read several forums regarding the new update and decided to attempt OTA with VooDoo's rootkeeper running (and backups made of course!)
I have dowloaded the update seveal times and everytime I get the error "verification signature failed"
Any suggestions to move past this?
Click to expand...
Click to collapse
Don't do it, you will lose root regardless of having Rootkeeper and you will not be able to re root until a workaround is found for the new update. The reason its failing is because you have a custom recovery. Which you will no longer be able to have if you accept the update. freeze sdm 1.0 using titanium backup to stop the ota process and feel lucky that the update failed.
Sent from a Shaftamle Galaxy S4
"Thanks" are always appreciated!
http://mycolorscreen.com/Shaftamle/
Related
Hello friends,
Yesterday i rooted my phone following this link
http://forum.xda-developers.com/showthread.php?t=1457622
Every step i have followed is successful .i.e. my phone is rooted.
However i am not able to install the OTA update after using the OTA rootkeeper and unrooting it temporarily. After the installation package gets downloaded, the OTA does not install..
Is there any way to get the OTA
manish.sanil said:
Hello friends,
Yesterday i rooted my phone following this link
http://forum.xda-developers.com/showthread.php?t=1457622
Every step i have followed is successful .i.e. my phone is rooted.
However i am not able to install the OTA update after using the OTA rootkeeper and unrooting it temporarily. After the installation package gets downloaded, the OTA does not install..
Is there any way to get the OTA
Click to expand...
Click to collapse
I can assure you OTA rootkeeper is not at fault. You must have modified files on there that are making the update fail. Please share a log of what went wrong on the update, seeing as that would make your problem much easier to fix.
mattlgroff said:
I can assure you OTA rootkeeper is not at fault. You must have modified files on there that are making the update fail. Please share a log of what went wrong on the update, seeing as that would make your problem much easier to fix.
Click to expand...
Click to collapse
before shutting down after the download, the msg which it showed was that the phone is unable to move the update to the sd card and then sd card unmounted..However in cwm it shows that my sd card is mounted
could someone please give me some advice.
i had to get the asia rom through the method above but i can't update any OTA!
i have downloaded the asia ota and put it on my sd.
i boot into recovery and update from zip/sd card.
all goes well until half way and i get an error.
something along the lines of "assert failed: apply_patch_check("MTD:boot:8388608:c3d17a6e41533c 813209ed51dfef327df8e1f76")
E:error in /tmp/sideload/package.zip
(status7 )
Installation Aborted
Hey all,
apologize in advance if this was asked before. i have performed a search and could not locate a definite answer.
i have SG3 ATT1747ucalem rooted using the guide on this forum.
since 2 days ago i have a notification for an OTA from ATT.
i have read the thread here and from users instructions installed voodoo OTA keeper.
i then tried to perform the OTA,
it keep going into recovery and then fail on "e: signature verification failed"
i have tried to temp unroot the device and try again - fail.
tried to toggle the verification off and apply the OTA - fail.
my question is this:
is there any way (or a thread to read) where there are instructions on how to apply the OTA update without loosing your root?
please let me know, thank you.
Questions go in the Q&A forum. Not Dev.
my apologies, i will ask there.
Hey guys I woke up this morning with a update from at&t so i tried to install it, the phone reboots and then says Signature verification failed installation aborted. My Galaxy S 3 is currently rooted. Anyone else have this problem?
It's much easier to flash a rooted stock ROM containing the OTA. There is at least one in the development section with more to follow.
THE HARDER (BUT NOT HARD) WAY:If installing the latest OTA update, you need the latest version of cwm for AT&T phones for the OTA to install. It's in the development section. You may also need voodoo OTA root keeper app to backup your root. The OTA WILL break your root.
Sent from my SAMSUNG-SGH-I747 using xda premium
Sweet thanks for the help, I flashed back to stock rom, got the update and rooted back to what I had before. It only took 10 mins to do
Hi,
I was previously current with the stock firmware, but rooted. I have OTA Rootkeeper. SU was backed up and did a temp unroot before the update.
After installing the OTA 2012.11.07 Update, every app at startup threw "Unfortunately, ... was closed" errors. I could not even launch any apps without them closing. Subsequent reboots ran through the "Updating Applications" cycle, but kept the same error result, basically creating an error loop.
I was able to "fix" it by manually installing the firmware update (now running 10.4.4.20-20121026 without error), but have lost root. OTA rootkeeper has no listing to restore root. So 2 questions (1 is very obvious, at this point):
1. Did I lose/overwrite the rooted SU binary or can this be relocated/replaced somehow?
2. What the root options (if any) for the TF700T Android 4.1.1 version?
Any other suggestions?
Thanks!
acraigl said:
Hi,
I was previously current with the stock firmware, but rooted. I have OTA Rootkeeper. SU was backed up and did a temp unroot before the update.
After installing the OTA 2012.11.07 Update, every app at startup threw "Unfortunately, ... was closed" errors. I could not even launch any apps without them closing. Subsequent reboots ran through the "Updating Applications" cycle, but kept the same error result, basically creating an error loop.
I was able to "fix" it by manually installing the firmware update (now running 10.4.4.20-20121026 without error), but have lost root. OTA rootkeeper has no listing to restore root. So 2 questions (1 is very obvious, at this point):
1. Did I lose/overwrite the rooted SU binary or can this be relocated/replaced somehow?
2. What the root options (if any) for the TF700T Android 4.1.1 version?
Any other suggestions?
Thanks!
Click to expand...
Click to collapse
There was another OTA update? my crappy tablet hasn't received any update since the original JB update. It says no update available. ASUS website doesn't show any new firmware update files.
I (painfully) solved my problem. I flashed back to Gingerbread, got root, then upgraded to the latest Jelly Bean. This time OTA rootkeeper did it's thing. No idea why it was so broken before. Unfortunately, it removed all my apps and settings so I'm busy restoring for the night
My rooted SCH-i605 got an update a week or two ago, and whenever I try to update it, it restarts and says the update failed. I keep postponing it by the maximum it allows, 5 days. From reading what people have been saying here, the same update has bricked some people's phones.
Should I flash back the vanilla ROM, update, then re-root? Is it possible to root this new update? Also, if I can't root after the update, can I restore applications with saved data from Titanium Backup (or similar) without rooting?
I'd appreciate advice on what to do. Thank you.