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 just got a notification for an update from HTC. I dont have a data plan with Sprint, and I couldnt find any information on here regarding this update. has anyone else recieved this?
Do you know what the update did?
I see the update too, really curious what it is. HC?
I'm going to wait though, I'm rooted and don't want to do a OTA update
Seems like it was an update to fix a tracking security issue?
http://community.sprint.com/baw/message/358639#358639
I was really hoping for an update that would let us install Hulu
Still no luck with that LOL
http://www.goodandevo.net/2011/10/a...es-are-now-receiving-ota-security-update.html
I saw it and I was like YEAH!!!!!! And then I downloaded it and installed and then...........awwwwwww no hc
Sent from my Evo View 4g
Nice update that wrecked the stock htc contacts app... This happen to anyone else?
Sent from my PG41200 using xda premium
Did the update break your root status?
I am rooted, however the update fails to install. Anyone else have this issue?
I also cannot update. It downloads, and reboots the device. After the reboot, there's an android bot, and a triangle encased exclamation point.
Evo View
quickquest88 said:
I also cannot update. It downloads, and reboots the device. After the reboot, there's an android bot, and a triangle encased exclamation point.
Click to expand...
Click to collapse
Need to revert to Stock RUU and then do the update(s) once done the do root process again
In case you need the zip 1.22.651.1
OTA_Express_Sprint_WWE_1.22.651.1-1.18.651.1_release_198260xikterg48lc0snx1.zip
New Update-Security Patch 1.22.651.2
OTA_Express_Sprint_WWE_1.22.651.2-1.22.651.1_release_220183oqo49zm8mw3kfeuv.zip
Odd it shows 2.1 not 3.0
Couple of quick questions here. Is the first files you linked an update and then the second one is a patch to that one? Also reverting to the ruu won't undo to the s-off setting? Is this correct?
ElAguila said:
Couple of quick questions here. Is the first files you linked an update and then the second one is a patch to that one? Also reverting to the ruu won't undo to the s-off setting? Is this correct?
Click to expand...
Click to collapse
Correct first 1 is Update then patch and you will need to do root process again.. But 1st you need to use RUU to get into stock to allow updates to occur.
You can also try to flash VIA recovery, been told it works that way to without having to go stock then reroot. The bookmarkwidget3D was the only glitch that I found, its not in the update.
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
So I was reading on Droid-Life that there might be an OTA to ICS on 5/9. My question is if I rooted now, installing Amon Ra, backed up, and removed some bloat.
How would the OTA effect me? If I didn't want to bother with roms atm but just wanted to remove bloat. Would accepting the OTA mess anything up?
Be patient. Once the RUU hits the streets. One of the device will post a rooted, deodexed, deflated version. That's what I'm waiting on.
Masx said:
So I was reading on Droid-Life that there might be an OTA to ICS on 5/9. My question is if I rooted now, installing Amon Ra, backed up, and removed some bloat.
How would the OTA effect me? If I didn't want to bother with roms atm but just wanted to remove bloat. Would accepting the OTA mess anything up?
Click to expand...
Click to collapse
I doubt it they said an update was coming for the Xoom LTE too and so far like all android devices.... nothing. Go Google Go..
leoingle said:
Be patient. Once the RUU hits the streets. One of the device will post a rooted, deodexed, deflated version. That's what I'm waiting on.
Click to expand...
Click to collapse
So I shouldn't bother rooting for now?
Root and remove your bloat. If an OTA is released I say within a day you will see someone post a zip version you can place on your SD card and place right on your phone. Have some fun and let yourself go.
Jimi Mack said:
Root and remove your bloat. If an OTA is released I say within a day you will see someone post a zip version you can place on your SD card and place right on your phone. Have some fun and let yourself go.
Click to expand...
Click to collapse
I just didn't know if there was some crazy unrooting process or error that would happen if the OTA popped up on me or was forced to install it.
Considering I don't plan on installing a rom for a little bit till I'm more comfortable with using the phone.
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
tuningmode said:
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
Click to expand...
Click to collapse
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
k1mu said:
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
Click to expand...
Click to collapse
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
tuningmode said:
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
Click to expand...
Click to collapse
Very likely the tether - it changes the framework, doesn't it? That's very likely to be updated by the OTA.
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Mz8691 said:
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Click to expand...
Click to collapse
Flash the MJ7 no-wipe ROM that you'll find in the Android Development forum. That will restore all of the stock files that you should need (and also cause you to lose root.)Then, update to MK2 and re-root.