Related
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
amancini92292 said:
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
Click to expand...
Click to collapse
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
amancini92292 said:
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
Click to expand...
Click to collapse
Just use titanium backup then and back to stock, do the update and reload ur apps. Takes all of about an hour, tops.
Droid X2 - Eclipse v1.0
yeah i have all of that done already, i might give it a try, thanks
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
im running the completely stock rom, removing the script i have isnt an issue what so ever, is there any way to remove installed zips that were installed in the recovery?
ashclepdia said:
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
Click to expand...
Click to collapse
True always better to be safe than sorry
if your on stock and you want to return your animations to stock you could possibly extract framework-res.apk from /system/framework/ of the stock gingerbread and push it via adb to your phone or you could use root explorer to do so as well. that should erase your mods to animations. and you'll most likely have to reboot after. but animations should retrun to stock after, than unroot and take the ota. but its never a bad idea just to go to bone stock via sbf as rp076 suggested
For taking off the toggles u can just flash the stock notification zip from one of those threads I think it is there somewhere. Or ask the creator of the toggle zip u flashed for the stock one...
But ur safest bet is sbf and data wipe. It's not hard to do at all and is just a good thing to know how to do
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Sent from my eclipsed DROID X2 using xda premium
rp076 said:
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
Click to expand...
Click to collapse
Steve125 said:
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Click to expand...
Click to collapse
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
masters said:
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
Click to expand...
Click to collapse
Calm down killa...just stating what I know thru past experiences & I'm not the only one who's had the problem before. When the 2.3.3 update first came out I couldn't update because my phone still was rooted, NOTHING FROZEN OR REMOVED. I read in other threads at the time that sbf'ing was the way to fix the problem. Once i did that, i was able to get the update installed successfully. Its not a wrong procedure, but a way to be sure to get a clean install. And as for flashing back, I was saying to do that if he wanted the ota
Side note...rom manager isn't or hasn't even been available yet for this phone ...surely you knew that
Hello all,
Just had a quick question. I didn't know what search terms to use to get an accurate answer, since the search seems to pick up any and everything related to any of your search terms. I was wondering what exactly prevents an OTA update from taking. Is it the recovery that is installed? Is it having root? It's been a while since I have accepted an OTA for a device, outside of the Nexus on launch day. I have my Razr Maxx rooted, no custom rom. I tried a few of the ICS leaks but they were in safestrap, my non safe partition remains only rooted. When the OTA actually hits should I be able to accept it fine or will I need to go back to completely stock unrooted?
Things that prevent an OTA: ROMS, Bloatware frozen/uninstalled, custom recoveries (safestrap, bootstrap) so yes, when you want the OTA you'll need to fastboot back to complete stock for it to work. Root won't stop an OTA but OTA's generally break root.
You can try just uninstalling safestrap but I've read cases where just uninstalling it doesn't work and you need to fastboot back to stock.
everything wrong with motorola and Android has to do with idiot upper middle management execs having endless powerpoint presentations babbling corporate gibberish so they can make the next payment on their overpriced overlarge joke of a house and BMW. we are left to sort out the steaming pile of ****. i pray google has the sense to fire every last one of them and give their salaries and bonuses to the engineers!
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
tech_head said:
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
Click to expand...
Click to collapse
What is the difference between freezing and removal, from a technical standpoint? I rooted my Razr using CASUAL and then installed Titanium Backup Pro and have been zapping the Verizon bloatware. I do want the stock ICS when it comes out. I guess I could reinstall the bloatware from backup and then freeze it rather than uninstalling. I don't care so much if the OTA doesn't install, I can troubleshoot that, but I don't want the OTA to brick my phone, that's the main concern.
The main reason I don't want the bloatware on there is that I don't want there to be any danger of clicking on anything that will make my monthly bill go up. Sometimes I let my girlfriend or other people use my Razr and if they manage to get a $10 monthly charge on my bill because they just had to see NFL Mobile or something similar, I'm gonna be pissed
I'm fairly sure it just changes the extension to .apk.bak, but I could be wrong
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Rooted, stock 2.3.6
bpingry said:
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Click to expand...
Click to collapse
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
quarky42 said:
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
Click to expand...
Click to collapse
Apps in preinstall folder are required by OTAs those are the real bloats. Any other system modification will be verified too, like build.prop, init.d CWM and so on..
Remember an OTA update is an incremental update wich will check any required system piece, especially those I've mentioned.
Cheers
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
MarkyG82 said:
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
Click to expand...
Click to collapse
Yes, it's a system modification. You'll need to flash stock rom to flash an OTA update.
When installing an OTA you can press both volume buttons at the same time to to see dialog, and if anything fails you will have filename and directory of failed checks. And it won't auto reboot until you tell it too. I found the problem files for the ics leak from early April leak and was able to install without wiping.
Sent from my DROID RAZR using xda premium
See I'm not fussed about wiping. Id quite happily have stock ICS and mod it from there. Looks like I'll be hacking some way or other to get the official anyhow as I'm on linux. Unless someone can point me to a UK suitable stock rom I can fast boot or add flash from linux. I have add setup if that helps. My system version is 167.26.
Sent from my XT910 using xda premium
cause they arent bronies, duh.
ExtraDan said:
cause they arent bronies, duh.
Click to expand...
Click to collapse
Sorry, I don't understand.
Sent from my XT910 using xda premium
and you wont...
MarkyG82 said:
Sorry, I don't understand.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I don't understand them either, just don't make a big deal about it
Thanks for all the replies. I don't have any bloatware frozen and no system mods done so I guess once the OTA hits, as long as safestrap uninstalled smoothly, I should be good to go. Ill check out ota root keeper here shortly.
Sent from my DROID RAZR using xda premium
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
DNak206 said:
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
Click to expand...
Click to collapse
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Don't take the OTA expecting to reroot!
wazup7 said:
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Click to expand...
Click to collapse
There may not be a "re-root" after you take the new hboot!!!!
YOU HAVE BEEN WARNED!!!
I've been saying this and not enough people are listening and stuck not being able to root again.
I know one person even trying to work on the hboot right now and his device will no longer boot, so think again before taking the OTA.
It's up to you and doesn't effect me either way, just a few words of advice if you will.
Maybe this will change and another miracle as big as this release will happen and an exploit will be found on a 2 year old device with less then a handful of devs even looking at it.
This could change, but right now I would not count on it.
I took the update unrooted but still had revolutionary's hboot. I can confirm that the hboot was not overwritten by the new one.
Edit
Didn't realize there was a thread about this already lol. My bad.
Sent from my HTC6435LVW using xda app-developers app
Seems there is a LOT of revert to stock and unroot threads, is there a consolidated place or simple means of doing this? I think I'm going to undo everything I did and just her activate it stock. If she *****es down the road about not having root (unlikely), I'll worry about it then.
Thanks guys.
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
CavyS said:
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
Click to expand...
Click to collapse
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
scott500 said:
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
Click to expand...
Click to collapse
Yeah that might as well have been written in Arabic. I think that might be one of the methods I tried though?.. Except when I put the Nandroid backup in TWRP/backups then rebooted my phone into recovery the backup wasnt showing in there no matter what I did, and the other way just got an error.
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
CavyS said:
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
Click to expand...
Click to collapse
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
redpoint73 said:
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
Click to expand...
Click to collapse
Lol I know, idk why I have to have to OTA either. Its just an OCD thing. I think its because I know that what I'm getting from OTA is clean and is a 100% working squeaky clean release by Android. Opposed to a ROM that someones put together themselves. I'm sure there is nothing wrong with the ROM or that there is any kind of malware or viruses in it. But its just an OCD thing were I would never stop thinking about it. And first thing my phone crashes or runs into a bug regardless of the problem I would blame it on the ROM. Lol now I sound like a sociopath
CavyS said:
now I sound like a sociopath
Click to expand...
Click to collapse
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
redpoint73 said:
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
Click to expand...
Click to collapse
Quick question. I put the Nandroid backup in the TWRP/backups/ folder. It doesnt show up in "Restore" but it shows up in "Install" in TWRP Recovery. When I click on it in "Install" it asks me "Swipe to Confirm Flash" Is it okay to flash Nandroid backup from the "Install" location or does it have to be done through "Restore"?
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
twiggums said:
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I just updated with RUU, I'll re-root again once 4.4.4 gets pushed out.