• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help? Error trying to update rooted device. How to unroot?

A new firmware update was detected by my phone, and I chose to update my rooted device this morning. After the download, I was prompted to reboot and install, and then an exclamation point came up. This scared me, but I rebooted the phone, and it's fine now. But after this scare, I want to unroot it, then update. I'm not such a big fan of ROMs, and my phone isn't under any warranty.

So I guess, how do unroot my boost mobile galaxy s2?? I can't find clear directions anywhere. Sorry if this has been asked before.
 
That update is just the OTA push to FL24, you don't have to do it if you don't want to. Otherwise follow the unrooting guide.
 
That update is just the OTA push to FL24, you don't have to do it if you don't want to. Otherwise follow the unrooting guide.

I just got the update notification a few minutes ago and dismissed it with "Later." Will it keep nagging ad naseum?
 
You will keep getting it till you update or disable it. If you do update just root again, but I use SuSuper user which helps with keeping you with ota updates.
 
I just got the update notification a few minutes ago and dismissed it with "Later." Will it keep nagging ad naseum?

There's an apk over on xda that kills OTA updates. Needs root though.
Havent tried it because I have JB and this is actually for ICS. Also there hasn't been any updates pushed to my phone to test this out to see if it works on JB.

http://forum.xda-developers.com/showthread.php?t=1832496
 
I just got the update notification a few minutes ago and dismissed it with "Later." Will it keep nagging ad naseum?

yes but you can stop it from doing so and stop the phone from even checking for an update if you are rooted. An app like autostarts will help you to disable the start up of the framework that checks for update. and you can use an app like ES file manager to remove the update file that was downloaded to the /cache folder on your phone
 
Just got this same update msg and wanted to make sure of a few things before I do anything. 1 if you update does it get rid of root? 2 can you reroot if it does? I'm rooted but on stock rom, will updating cause any problems? Thanks for any answers
 
yes but you can stop it from doing so and stop the phone from even checking for an update if you are rooted. An app like autostarts will help you to disable the start up of the framework that checks for update. and you can use an app like ES file manager to remove the update file that was downloaded to the /cache folder on your phone

I tried the autostarts method but still received the prompt to update this morning, so I've tried the method suggested by Munguse and so far nothing. Hope it works. By the way Codegerm do you have any idea if OTA Rootkeeper works with our phone? I've downloaded it, ran it, and it says I have a protected copy of root but I've read on the XDA thread that it doesn't work with the SGS2...
 
I tried the autostarts method but still received the prompt to update this morning, so I've tried the method suggested by Munguse and so far nothing. Hope it works. By the way Codegerm do you have any idea if OTA Rootkeeper works with our phone? I've downloaded it, ran it, and it says I have a protected copy of root but I've read on the XDA thread that it doesn't work with the SGS2...

Did you disable the right framework in the After Startup section? It is like the third Google services framework listed there. Also you need to delete the file in the /cache folder using a root explorer like es file manager. I have never used root keeper I disabled the auto update and make sure I am the one who decides when I am updating. I have seen far to many updates mess up things that the user actually liked.
 
Did you disable the right framework in the After Startup section? It is like the third Google services framework listed there. Also you need to delete the file in the /cache folder using a root explorer like es file manager. I have never used root keeper I disabled the auto update and make sure I am the one who decides when I am updating. I have seen far to many updates mess up things that the user actually liked.

Ahh...no I didn't disable the framework in the after startup section. I disabled system updates in screen on/screen off sections. That must be where I went wrong. Anyway I installed the other method and deleted the update file in cache, and so far so good.
 
Ahh...no I didn't disable the framework in the after startup section. I disabled system updates in screen on/screen off sections. That must be where I went wrong. Anyway I installed the other method and deleted the update file in cache, and so far so good.

heheh Okay that is why. Yeah, that framework is what checks for updates. It's kind of annoying that they list them multiple times in there but, you just look at each one until you find the one that has update in its description.
 
heheh Okay that is why. Yeah, that framework is what checks for updates. It's kind of annoying that they list them multiple times in there but, you just look at each one until you find the one that has update in its description.

Once again you're right Codegerm,it's the third one down. Disabled it. Should have that little problem licked now. Hehe..
 
I was rooted and wasn't thinking, so I'd attempted the update. It broke my camera, data, and text messages.

I ended up flashing stock through Odin. Then immediately after it did three updates. Fh29, Fl22, then the recent one that patched the exploit.

There are ways to remove root, but honestly this update wasn't anything special. If you've got Supersu, go into it and use clean up and unroot. If you've used Exynos Abuse, make sure you go in and uncheck "Disable exploit at start up" also use the clean up option there too.

Make sure you've restored any system app you may have frozen/removed. The update is likely to fail without everything being in it's original place. ^^.
 
Back
Top Bottom