[Q] Rooted S3 cannot update - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

My Galaxy S3 has been rooted but didn't change the rom. Tonight I downloaded the update and reboot. Then when it goes to cmw recovery it says there is some untrusted update. I think that must be the one that I just downloaded so choose "Yes keep updating" but it seems it doesn't finish well (it goes to reboot fast). After rebooting, the error message says the update couldn't be done. And I check the device information, sadly still 4.1.2
I used the same method for 4.1.2 update and that time it went well (I was also worrying about the root issue but it turns out everything is fine). But I'm not that lucky this time.
Does anyone have the same issue as mine? How can I solve this problem? Shall I do some factory reset? (I hope Titanium backup can still work after factory reset)

yixiaxian said:
My Galaxy S3 has been rooted but didn't change the rom. Tonight I downloaded the update and reboot. Then when it goes to cmw recovery it says there is some untrusted update. I think that must be the one that I just downloaded so choose "Yes keep updating" but it seems it doesn't finish well (it goes to reboot fast). After rebooting, the error message says the update couldn't be done. And I check the device information, sadly still 4.1.2
I used the same method for 4.1.2 update and that time it went well (I was also worrying about the root issue but it turns out everything is fine). But I'm not that lucky this time.
Does anyone have the same issue as mine? How can I solve this problem? Shall I do some factory reset? (I hope Titanium backup can still work after factory reset)
Click to expand...
Click to collapse
you need to have stock recovery and unroot your phone, or with stock recovery temporaly unroot using VooDoo RootKeeper and sideload with ADB.

Related

OTA 2.12.110.4, is it possible to install?

Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!

Android update!

Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.

[Q] Went back to stock, unrooted, can't update ROM

Like the title says, I went back to stock and unrooted my phone. I got a message from Tmo today that an update for my phone was available, but on trying to update, the phone just sits at the "checking for software updates" screen and nothing happens. Any suggestions on how to fix this?
JazzMac251 said:
Like the title says, I went back to stock and unrooted my phone. I got a message from Tmo today that an update for my phone was available, but on trying to update, the phone just sits at the "checking for software updates" screen and nothing happens. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Kies.
Yep use Kies to update. Worked perfectly and then just reroot.
Have your tried going into stock recovery (after unrooting) and doing a factory restore? If the option is present, you may alsi want to wipe your cache. Hope that helps.
I am having the same issue as OP. Was rooted by CF auto root plus triangle away (deleted after use). Always stock ROM/recovery. Got OTA update notice so delayed it so I could unroot first. Checked temporary unroot option in SuperSU, no luck. Chose permanent unroot, no luck. Deleted SuperSU, no luck. Ti Backup confirms not rooted. Kies doesn't show update available and selecting upgrade through Kies tools menu fails as well. Do I need to clear my cache (which I have never done). Don't want to wipe and start over. Need to learn how to do this for future updates. I thought my basic root method would allow updates with little effort. Am I missing something? Thanks in advance.
I wiped cache and still no luck. It tells me update available and when I say install it just sits on checking for updates...
Hey OP, did Kies work for you? I installed the most recent Kies and it wont even finish connecting with my phone. God I hate being a noob at this stuff. I don't have a clue why this update wont happen or Kies wont connect. Im using the OEM USB cable. Everything says official and nothing custom. Somehow, T-mobile update knows I was once rooted or something. WTF
I should of tried OTA rootkeeper but too late now.
Any advice??
Kies finally worked. No idea what was different from previous 10 attempts...
Any suggestions how to go from TWRP back to stock recovery and keep root? I can't use the Toolkit since it's missing the stock recovery Tar file...

[Q]new ota error 410

I put back stock recovery and locked when i try to update it starts then reboots the phone once i did get a congrats message but checked still on 4.2.2 when i check status it says failed error 410 and ive been searching but not finding any info on error anyone know?
bregga said:
I put back stock recovery and locked when i try to update it starts then reboots the phone once i did get a congrats message but checked still on 4.2.2 when i check status it says failed error 410 and ive been searching but not finding any info on error anyone know?
Click to expand...
Click to collapse
Ive also gotten this problem. Ive looked into it and it occurs when you delete a system app. I believe the update wont be applied unless all stock apps are installed
weird
I have not deleted any running stock just s off and unlocked Ill have to look for a stock rom then thank you I will give it a shot
eXperianceHD said:
Ive also gotten this problem. Ive looked into it and it occurs when you delete a system app. I believe the update wont be applied unless all stock apps are installed
Click to expand...
Click to collapse
you were rigtht
I nandroided back to my original backup and it is doing the updates thank you.
bregga said:
I have not deleted any running stock just s off and unlocked Ill have to look for a stock rom then thank you I will give it a shot
Click to expand...
Click to collapse
I have S-OFF and 1.10.605.15, and had deleted a bunch of the Verizon bloatware. After reverting to stock recovery, I tried to apply the OTA; it got stuck with a red triangle. I pressed volume-up + power, which showed me a bootloader menu and an error message that it couldn't find Kidzone (one of the apps that I had removed). I selected reboot in the bootloader to reboot the phone and, obviously, it was still in 4.2.2 and the software status had error 410.
I don't have any backups with the bloatware apps on them, can you think of any way to apply the OTA without wiping my phone? I'm a little annoyed that Verizon made the OTA check for those apps to be installed on the phone; I find it hard to believe this is necessary...
neutrino37 said:
I have S-OFF and 1.10.605.15, and had deleted a bunch of the Verizon bloatware. After reverting to stock recovery, I tried to apply the OTA; it got stuck with a red triangle. I pressed volume-up + power, which showed me a bootloader menu and an error message that it couldn't find Kidzone (one of the apps that I had removed). I selected reboot in the bootloader to reboot the phone and, obviously, it was still in 4.2.2 and the software status had error 410.
I don't have any backups with the bloatware apps on them, can you think of any way to apply the OTA without wiping my phone? I'm a little annoyed that Verizon made the OTA check for those apps to be installed on the phone; I find it hard to believe this is necessary...
Click to expand...
Click to collapse
You have to have all apps present or else it fails to patch them.
It can't guarantee a full clean install if some files patch and some don't.
(This is why we root, so we can flash already rooted roms and remove things as we want. Not so we can take OTA's)
Install the stock rooted rom and firmware in the dev section.
OR install the previous stock rooted rom in the same thread in the dev section and stock recovery and then ota update.
You will wipe your phone by flashing stock recovery though.
If you just flash the firmware and then the stock rooted rom, you won't have to wipe.
Just be sure to do an odex version, since yours is still stock odex.

can't update to 4.4.2 OTA

Hello, my phone recently notified me that a 4.4.2 android OTA update is available (i have a AT&T SGH-i747) however once it reboots, it will get to about 29% complete, then i get the "Update failed" message, and it reboots back into android (4.3) and i was wondering how i could get it to work?
(i'm using stock rom, i've NEVER flashed anything on it before, only thing i've done is root it to use titanium backup, however i used the saferoot thing so as to not flip the knox security stuff)
You need to unroot.
audit13 said:
You need to unroot.
Click to expand...
Click to collapse
do i have to do something special to do that? or can i just click the "Full unroot" button in the SuperSU settings tab to unroot my phone
You also need stock recovery and, preferably, all of the ATT apps on your phone. I have read that removing too many ATT apps will prevent the OTA update from completing.
I have never tried removing root that way so I cannot comment.
You should also make note of the fact that it is possible to have something go wrong during the OTA process which may result in the loss of your data. I recommend at least backing everything up to your external SD card and removing the SD card during the OTA update process.
like i said, i only rooted to use titanium backup to restore a backup for a game save, that's all i've ever done (so if that undid stock recovery, or removed AT&T apps without me telling it to, then how would i fix that)
In that case, just unroot and then run the OTA update. Titanium backup would not alter the recovery or remove apps.
well, i have 5 hours to wait before doing so, after unrooting (using the saferoot unroot.bat file, then using supersu's unroot after that to finish the process as the saferoot program said to do) i went to click check for updates, and instead got "Your device is running the latest version" and "you may check again in 5 Hours 0 Minuties" which i'm assuming is because it failed last night when i tried to update it?
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
audit13 said:
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
Click to expand...
Click to collapse
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
logoster said:
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
Click to expand...
Click to collapse
sorry for double post, just checked download mode, says i'm completely stock and official
also thought i'd mention that the check again later timer is going down, it's at 4 hrs and 3 minutes
You could also try booting into recovery and wiping cache and Dalvik. Don't wipe data.
nope, still has a timer, but it's fine as it is going down, i have about 2hrs and 47 Mins left according to it
Sorry for double post again, but timer finished, and update worked flawlessly, so unrooting did work, thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Categories

Resources