Updating a rooted Galaxy S3

[evti]

I rooted my Galaxy S3, and got an update notice the other day. I tried updating it, and all was okay until it rebooted to try and install it. It booted to the Odin screen or whatever (the one where you select the Zip package when you root it), and then showed the Android robot dead with an exclamation mark over him. I tried restarting it to get it back to functionality, and fortunately this worked, but now it won't shut up about the update. Is there any way I can update it, or is it like jailbreaking an iPhone where you have to do it again (and only if there's a version of the jailbreak for your software version)?

 

[s44]

Did you change the recovery or kernel while rooting?

You could try using the OTA Rootkeeper to temporarily un-root before running the update, then run it again to re-root after.

 

[T_Yamamoto]

Download and install a ROM. Maybe bugless beast? If you get a stock ROM (like bug less) it gets rid of those OTA notifications. If you just root. They still show up

 

[PowerYoga]

You're probably on verizon, I got the update push 2 nights ago myself. You can flash the updated rom but it requires the unlocked bootloader.

http://forum.xda-developers.com/showthread.php?t=1892670

If you want to disable the notification without updating, you can disable SDM by freezing it with titanium backup or using root browser to rename the SDM.APK file to something else.

 

[evti]

Did you change the recovery or kernel while rooting?

You could try using the OTA Rootkeeper to temporarily un-root before running the update, then run it again to re-root after.

No idea, lol. If I did this, I assume the root isn't version dependent? As in it's not like the iPhone where only certain versions of the software can be jailbroken?

 

[s44]

No idea, lol. If I did this, I assume the root isn't version dependent? As in it's not like the iPhone where only certain versions of the software can be jailbroken?

Basically not, but you'd need to reroot after a successful OTA unless you use Rootkeeper. Your problem is more likely the reverse: something you changed while rooting is borking the OTA update.

Tell us what model you have and what root instructions you followed...

 

[Suspicious-Teach8788]

on a lot of phones OTA updates get screwed or updates in general because of root.

this is a path I hate taking with people who aren't interested in ROMing. Essentially root is a difficult path to go down.

 

[ponyo]

on a lot of phones OTA updates get screwed or updates in general because of root.

this is a path I hate taking with people who aren't interested in ROMing. Essentially root is a difficult path to go down.

Name one phone. Rooting itself won't effect OTA update.

 

[NikolaeVarius]

on a lot of phones OTA updates get screwed or updates in general because of root.

this is a path I hate taking with people who aren't interested in ROMing. Essentially root is a difficult path to go down.

Root does nothing in regards to updates.

 

[Suspicious-Teach8788]

Name one phone. Rooting itself won't effect OTA update.

My gf's Incredible 2? Verizon would try to push OTA updates and it'd fail.

 

[PowerYoga]

If you just root it won't affect OTAs at all. If you rooted and then flashed a custom rom the OTA might fail depending on if its a stock rom or not. For example I flashed a slimmed down stock rom and I still got the OTA prompts.

 

[evti]

I used this method to root my phone. I have a Galaxy S3 SGH-I747

 

[ponyo]

I used this method to root my phone. I have a Galaxy S3 SGH-I747

So do you have stock recovery or custom Clockworkmod recovery?

 

[s44]

So do you have stock recovery or custom Clockworkmod recovery?

From his link

does not affect your phone in any way other than install ClockworkMod Recovery and give you root

So the root method he used switched recoveries to CWM. This is what broke OTA.

This method should let you apply the OTA changes using the recovery you have. Check your Settings first to make sure you're on UCALG1 before you apply it.

Of course, I'd personally nandroid, TiBu, and start trying ROMs, but that's up to you.

 

[ponyo]

From his linkSo the root method he used switched recoveries to CWM. This is what broke OTA.

This method should let you apply the OTA changes using the recovery you have. Check your Settings first to make sure you're on UCALG1 before you apply it.

Of course, I'd personally nandroid, TiBu, and start trying ROMs, but that's up to you.

The reason I asked is that CWM won't stick unless you delete the 2 files. I don't know if this program does that for you or leaves it up to the user to do that. This is why I'm not a fan of one click root and other automated batch programs. It teaches the user nothing since the steps are usually hidden and when things go wrong or the user wants to undo the changes, they don't have any idea or clue where to start. There's no learning or understanding of the process. It's why I still do everything manually via adb and fastboot commands. It's not hard and it forces me to read and check after every step of the process. OP, I'm not trying to pick on you. I just want people to understand what they're doing.