Related
Okay, so I haven't as of yet seen a thread that appears to spell out this process. Most of you are talking about applying developer-modified patches to get to DI01, using Clockwork recovery, and things like that. For various reasons, some of us prefer to remain a bit closer to stock, and not worry about bricking with custom recovery software and whatnot. I'm one of those people, and I've seen questions here and there on how to go back to stock, and if root can be maintained or redone afterward, etc., so I decided to document here what I did to apply the official update to my rooted and lag-fixed Fascinate. Without further ado, here's the process I followed:
Ran the unlagfixme.bat script from http://forum.xda-developers.com/showthread.php?t=779597, which automatically reboots the phone
Used Root Explorer to remove the ".old" extension I had added to all system .apk files I considered bloatware (I chose to disable them, not delete them)
Rebooted the phone again for good measure
Downloaded the update, and let it install normally, after which root access was gone as expected (Superuser.apk and other apps that required root access were still present, but they wouldn't function)
Rooted my Fascinate again per the instructions in http://forum.xda-developers.com/showthread.php?t=779238, just like I did the first time (only had to do it once, not twice like some here have said); note that I followed all instructions except for the final one, which is installing Superuser.apk, as that application was still installed, and still worked fine after applying the proper permissions to su and busybox
Opened Root Explorer, and once again added .old to all .apk files that I wanted to disable and remove from sight
Rebooted again
Ran the lagfixme.bat from http://forum.xda-developers.com/showthread.php?t=779597 to re-apply the lag fix
Rebooted one final time to make sure everything was in still good working order
So there it is. I'm still running stock ROM, stock recovery, etc. I should be able to easily repeat this process any time there's a new OTA update, with minimal risk of bricking.
Helpful thanks, but I think I screwed up.
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
propylene22 said:
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
Click to expand...
Click to collapse
Just re-root, either through adb or there was a one-click out there.
Yeah, just re-root using the original procedure you used (except no need to reinstall superuser.apk), and you should be good to go.
Sent from my SCH-I500 using XDA App
Thanks for taking the time to write that up Ivorycruncher!
How would this process differ when the Froyo update is released, also having ClockworkMod Recovery installed instead of stock recovery?
I, like you, would like to have legitimate updates installed while keeping root.
I've never installed Clockwork, so I can't comment on that. When Froyo comes out, I imagine the process will be much the same, though at this point there's no way to know if the original rooting method will still work or not after the upgrade. Also, depending on what they do with Froyo, the lag fix may not be necessary anymore, and might not work without some tweaking even if it is still needed.
Sent from my SCH-I500 using XDA App
I just got a CLNR Rezound with the 1.xxx software--if I temp-root to debloat will the OTA still take, or will it fail? Is there a reason to want the 2.xxx software over the 1.xxx? I'm sure this has been discussed, but I'm still trying to figure the Rezound out. Seems awesome, so far.
1/2
I can confirm that I had removed QUITE a bit of bloat, but the OTA still self-installed on my phone. I was not temp rooted at that moment.
jdmba said:
I can confirm that I had removed QUITE a bit of bloat, but the OTA still self-installed on my phone. I was not temp rooted at that moment.
Click to expand...
Click to collapse
Did it reinstall all the garbage? I'm basically just going to strip everything out.
Seems Ok
tekhna said:
Did it reinstall all the garbage? I'm basically just going to strip everything out.
Click to expand...
Click to collapse
I don't recall 100% of what I removed, but I remember NFL something was one thing, and its still gone. So is VZW Navigator. Seems it did not reinstall those items; but I suspect if it was going to update something you removed, that would come back.
New bloat was installed (e.g., Verizon Location), per other threads.
Rezound OTA
I had used CleanTOOL to debloat and the OTA update would download ok but would not load. I tried it several times. I went back into CleanTOOL and rebloated, and the update loaded just fine the first time, though I had to wait overnight until I could download it again.
Now, of course, I can't temp boot and CleanTOOL no longer works. I hope this OTA update is worth it.
For me the OTA keeps downloading but it doesn't seem to want to install. I have frozen some of the bloated apps using the temp root method. This is the 2nd day in a row where I have caught the phone downloading the firmware update. I'm unsure what I can do to start it because it looks like it just retrys over and over without any success.
Why not just perma root? You can download cons otarom, completely debloat, dont have to worry about the turning off and having to re root? Heck, use TI and you can save all the bloat, and put them back on at anytime if you so desire.
Mitalis said:
For me the OTA keeps downloading but it doesn't seem to want to install. I have frozen some of the bloated apps using the temp root method. This is the 2nd day in a row where I have caught the phone downloading the firmware update. I'm unsure what I can do to start it because it looks like it just retrys over and over without any success.
Click to expand...
Click to collapse
You can do a factory reset and accept the OTA but iirc you cannot temp root again afterwards though, but I believe you can perm root afterwards. But while you are temp rooted you might want to back up your settings and apps with Titanium backup or MyBackup first.
Don't take my word on perm rooting though, search first if you want to perm root. But I believe that since you can unlock the bootloader you can perm root by flashing Amon Ra recovery then installing su with that, but the one-click perm root won't work any more.
I think I had used CleanTool as well, I love my Rezound and really wanted the bloat off. The update downloaded 3 times and then didn't install. I gave up and did the factory reset. Although I hate bloat, really I am happy with Sense and the way the phone itself functions so I didn't feel the need to do a full root.
Hey guys,
Alright, so I was on my stock rooted ROM and saw an OTA come in. I download and apply the update, but it freezes and stops the update. So I unrooted, and tried again. Still failed. So then I remember I didn't disable SafeStrap, and I go and re-root, disable SafeStrap, unroot again, and THEN try the update. Still failed.
I did delete some of the games that came with the phone (while unrooted; I didn't remove system files to my knowledge). What do you guys think the problem could be? I'd really like improved signal connectivity and eventually ICS. And Fastbooting didn't work for me the last time I used it for some reason (although I wasn't on stock ROM at the time - could that have done it?)
Thanks!
Edit: Tried factory reset, did NOT work. Looks like SBF/Fastboot is my only option. What happens if it doesn't work? I'm on stock and unrooted and everything. Maybe I just need to install the missing files? I think I only deleted thinks like NFL 12 and the similar games that were ALLOWED to be deleted. SO blown right now...ugh.
It probably was the bloatware you removed. Before the update came down, I fastbooted back to make sure there weren't any issues with the update. Several people have said that with bloatware removed, the update will fail.
How did you unroot? The only way I've done it is to fastboot it (just to be on the safe side).
I used some app called Ginger Unroot from the market. Surprisingly, it actually worked - SU operations (including SafeStrap apk tasks, SetCPU, etc) ceased function due to a lack of root. I almost feel like VZW could just reset the phone because it is TECHNICALLY not rooted and is still not accepting the OTA. Also, I have a Mac, so it's a hassle to have to borrow a friend's PC every week and try again. But I'll see. There's absolutely NO WAY to fastboot via a Mac, right?
(Also - would a factory reset put the missing apps back and allow, then, for an OTA?)
Thanks!
Things like Safestrap can prevent OTA update.
Safestrap changes the boot structure.
I removed SafeStrap though. Like, it is NO LONGER on my phone, either in bootup OR in apk form. So it shouldn't be affecting the process anymore, right?
Sorry for double post - I found a FastBoot utility for Mac that MIGHT work. Not 100% on it though, but everyone who's used it has indicated it has worked for them.
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
See, that's my problem...I got rid of apps like the blockbuster app and Madden 12...you're telling me, essentially, that I'm screwed because VZW was stupid enough to make "vital" apps deletable? Also, I deleted those apps while non-rooted. How's that for ironic...
ViaCapita13 said:
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
Click to expand...
Click to collapse
How did you reload the pre install files? Where did you get the files?
I'm having same issue on xt926.
Thank you very much for the help!
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2
UPDATE: Ignore this. I gave up for a fix and just let OF1 update run. Phone is fine.
TL;DR Is there a way to ABORT the OF1 update if it's already set to install on boot?
From these forums I learned that we want to prevent OF1 if we want to root. I had tried Kingroot app once and it failed so I was waiting until I could figure it out. Meanwhile, I was getting the stupid nag screen over and over. For days I avoided it but last night somehow I must have touched the screen while the phone was in my pocket. I pulled it out at one point and saw, to my horror, that it was in the recovery/install screen. It says "initializing system update" with the little green android robot. So, I pulled the battery and the phone has been off since.
I"m not an advanced hack-user, but I've been a IT guy so if there is a method, I MIGHT be able to execute instructions. But, I think I know enough to know that it's pretty unlikely I can fix this easily. I don't really under how phone boot, but I assume this is a pretty deep system level thing, like the boot sector on a Windows PC. I ignorantly guess maybe it can be done through the ADB interface? Somehow UNset the "boot into recovery" and then remove or otherwise disable the update package? When I say that, I might sound like I know what I am ttalking about but really I have no idea what that would really involve, it might be over my head.
I really only want root (for now) so that I can use Titanium Backup, and other root-dependent apps. SOMEday I might want to ROM this, but that's not key.
I guess if I can't find a solution soon, and I really need my phone, I'll have to let the install finish and I'll have OF1. Then I'll wait to see if/when a root comes. *sigh*
I wish I could have figured out how to disable to the OTA before this happened. But, doesn't freesing apps require Titanium which requires root? Yeah, carriage and horse problem.
Thanks in advance.
Abort? If you had root, you could have hid the notification and delete the OTA.
Yes Please.
How do you delete the notification? I believe I found the update the in the FOTA file and have deleted it, but still get that update
deleting the file in /cache/fota is the only thing you can do without root. Once you're rooted, you can disable the application with something like Titanium Backup, or just delete the OTA updater.
macravin said:
deleting the file in /cache/fota is the only thing you can do without root. Once you're rooted, you can disable the application with something like Titanium Backup, or just delete the OTA updater.
Click to expand...
Click to collapse
So, which APK in /system/app is the actual OTA updater?
I can't seem to figure out what's supposed to be disabled, and no threads in the entire Verizon S4 forum give a clue when I'm searching for 'Disable OTA'