Apologies up front... I'm sure this has been discussed ad nauseum, but my searches can't turn up the answer I'm looking for.
I'm not ready to grab the new update, kernel, or radios. I'm running perfectly the way I want with Nils GingerSense 1.5 (GB).
The first OTA nag, I was able to reject. This morning, the OTA downloaded (found the OTAPkg.zip in /cache/fumo), but I was only able to defer several days, no reject option.
Question: Is there anything I can do to prevent future Verizon OTA attempts and forget about this until I'M ready to move forward?
I used to have fotakill.apk in my cm7 rom for the incredible . Maybe you can download any cm7 rom and extract that file. Might work?
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
I see a otacerts.zip in /etc/security , so I'll try renaming that, thanks.
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Resigned
DIncLover said:
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Click to expand...
Click to collapse
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
I simply deleted every apk in the /system/app folder that said either Verizon or VZW.... I have not gotten any prompts about the OTA and it definitely has not installed or attempted to.
htcdm showed up as "hogging data" in one of my data trackign apps when i got my update message, hope that helps.
Would be nice to reject this OTA.
It don't even ask before trying to apply it!
I'm suprised that people on custom roms are getting the update attempt. Usually on a custom ROM, that kills the OTA updates. This is usually only a problem on those that are on a stock rooted type rom.
Very weird
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
jdmba said:
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
Click to expand...
Click to collapse
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
brettokok said:
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
Click to expand...
Click to collapse
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
solo_xda said:
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
Click to expand...
Click to collapse
Yeah, happens to me once or twice a day, and if you don't notice it as it happens, it ends up just rebooted sitting in twrp. So I don't get calls or texts or alarms.
Anyone out there have any idea how to block the OTA's? Or can anyone answer if the following is possible.... I have never used titanium backup for actually doing any backups. I have just used it for removing stupid verizon apps. Could I do a backup of setting/apps and then flash the newest stock ICS ruu or whatever, re-use the root tool, and then restore my stuff from my backup?
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
brettokok said:
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
Click to expand...
Click to collapse
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
ckupsco said:
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
Click to expand...
Click to collapse
I'm stock and rooted.
Last night, I froze the updater app in Titanium Backup. I rebooted for good measure. This morning I woke up to my phone booted in recovery.
I rejected the update and booted back up. So this is still an issue...
Just chiming in that I'm also affected, but havne'tthat on Sunday this push broke my GB image, so bad that I had to RUU it to ICS. Now I've been finding my phone at TWRP every morning with an OTA.zip failing to flash.
Additionally, I got a message that offered me to defer my update and I chose 3/10 at 7pm. But it still tried overnight.
Use tibu to freeze the ota updater package.
Or flash a custom recovery like amon ra for rezound. Or even a custom rom, say simplistic if you want to stay on an ics/sense based rom
To get the ota, one must have: a relatively unmodified stock rom (key system apps can't be frozen or missing) and the stock recovery tool. If you change either of those, you won't get prompted to do the OTA.
Sent from my Infected Rezound using Tapatalk 2
---------- Post added at 01:55 AM ---------- Previous post was at 01:49 AM ----------
AndroidGraphix said:
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
Click to expand...
Click to collapse
If you're s-on, you can't rewind the firmware on your phone. The mainver fix is just to get certain roms installed.
While it's possible they could patch the current s-off method, I doubt they care much at this point. Verizon has depleted their stock of replacement rezounds and HTC has moved onto new devices.
Sent from my Infected Rezound using Tapatalk 2
Related
Ok, so apparently you cant just click reject on the verizon update and expect it to never come again. Every single day, sometimes twice per day they try and push their stupid update to my phone. Is there anyway to permanently disable OS updates? Getting tired of this.
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.
Sent from my HTC Thunderbolt
Not rooted, there is no other way?
Sure. You root your phone and follow the steps in post 2.
Just messing with you. Looks likes there's no other way.
Sent from my ThunderBolt using XDA Premium App
Sorry to bump an old post, but FYI this worked. For anyone who might be wanting to do the same without adding custom roms. Root process took a little while but EasyRoot eventually nailed it.
Actually, this did NOT work. Verizon is still trying to update my phone! And I hear doing an OTA update after root can seriously mess stuff up. I renamed the file, rebooted, twice even, and I still catch my phone auto-downloading this goddamn update without even asking for permission anymore!!!!!
Do I have to just flash a new rom or something to finally get rid of this trash? I really like the stock rom without the bloat. I de-bloated it myself since all of the debloat links for other roms are dead and the authors refuse to allow mirroring so they can make money on their links. :thumbsup:
Yea, just have to bite the bullet and flash a new rom. I had the same issue with my Galaxy Tab when I went back to stock, except it wouldn't apply the update, just reboot and pester me again. Of course you know the benefits and pitfalls of rooting, might i suggest trying a clean 2.3 rom with Sense 3.0? You will practically have a new device.
Also, of you never had a Vanilla device try pur3a05p. They have a great offering.
Cast by the Odinson's mighty Mjolnir!
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.
After some fighting I managed to convince my phone to redownload the ota(had to delete old zip and clear data on the htcdm service, then the "check new" option started working again). I accepted the update, it downloaded. There was a loud ding and then nothing, phone still on, no prompts, no reboot, no nothing. Ideas? Could it be something that was frozen by the cleantool?
I'm sure the reason why nobody has replied is because you didnt use the search at all..go to the front page and look for OTA and you will be on the right track....
Are you stock or rooted? If your rooted then this problem is normal..even if you did get a prompt and somehow managed to get into recovery then you would get an error..if your stock then I'm not sure what's wrong..either way there is a stock rooted Rom with the update out already and I'm sure other rims will incorporate the update also.
I've used the search and so far have yet to see anyone with the exact same problem. Have you seen something I haven't?
I'm stock (no rom at all), rooted, default recovery
esheesle said:
I've used the search and so far have yet to see anyone with the exact same problem. Have you seen something I haven't?
I'm stock (no rom at all), rooted, default recovery
Click to expand...
Click to collapse
lock your bootloader my friend.
fastboot oem relock
then you can unlock it again after..
So if the bootloader is unlocked it won't even reboot to try the update?
It's weird cause read postings here saying people are rooted and unlocked and still install just fine. So what's the actual truth?
In fact right in this thread someone says they didn't lose lock(as in never relocked seemingly):
http://forum.xda-developers.com/showthread.php?t=1466474&page=10
My theory is that some service disabled by Cleantool may be required for this update to get started, but just a theory. Has anyone who completely debloated run this successfully yet?
Love to hear other theories though.
Question
I know the original unlock was a hard reset to the phone.
Do subsequent RELOCK and UNLOCK do the same thing?
andybones said:
lock your bootloader my friend.
fastboot oem relock
then you can unlock it again after..
Click to expand...
Click to collapse
That would be a great fix IF it worked for all Rezounds....
Unfortunately, it doesn't. My buddies phone was also unlocked thru HTCDEV and rooted and the update sailed right thru for him.....not for me though
xbxjunkie said:
That would be a great fix IF it worked for all Rezounds....
Unfortunately, it doesn't. My buddies phone was also unlocked thru HTCDEV and rooted and the update sailed right thru for him.....not for me though
Click to expand...
Click to collapse
What happened with yours? I just tried unfreezing some stuff and going to try installing after work. What was the difference between you and your friends phones? Bloat removal, etc?
esheesle said:
What happened with yours? I just tried unfreezing some stuff and going to try installing after work.
Click to expand...
Click to collapse
I can download the update, but during the attempted install I get the red triangle and I gotta pull the battery. I unfroze all my bloatware from rom toolbox and tried again....nope. I did a backup, and tried a factory reset....nope again.
xbxjunkie said:
I can download the update, but during the attempted install I get the red triangle and I gotta pull the battery. I unfroze all my bloatware from rom toolbox and tried again....nope. I did a backup, and tried a factory reset....nope again.
Click to expand...
Click to collapse
At least you are getting to the reboot. Mine doesn't even reboot, just downloads and then beeps at me, then nothing.
jdmba said:
I know the original unlock was a hard reset to the phone.
Do subsequent RELOCK and UNLOCK do the same thing?
Click to expand...
Click to collapse
I was messing with this earlier today. I reengaged the lock and then my phone would only load hboot. I eventually gave up and reran the unlock process, which unfortunately did wipe out all of my data. Thank goodness for AM and my nandroid from last night!
I have the same problem as well. I am stock, no root but I have used CleanTool to get rid of bloat. I have downloaded the update atleast 10 times and it has never done anything. Just dings at me, I click OK and no reboot, nothing. Not sure what is up.
EDIT: I used the CleanTool again and temp rooted and restored all the bloat, option 5 I believe and now it is taking the update.
Radiman said:
I have downloaded the update at least 10 times and it has never done anything. I click OK and no reboot, nothing. Not sure what is up.
Click to expand...
Click to collapse
X2 no luck
RustyNailz said:
I was messing with this earlier today. I reengaged the lock and then my phone would only load hboot. I eventually gave up and reran the unlock process, which unfortunately did wipe out all of my data. Thank goodness for AM and my nandroid from last night!
Click to expand...
Click to collapse
I had the same issue , drove me batty, i thought maybe i left a ph98zip on my card. Took the card out and still wouldn't reboot. I just said screw it and tried the RUU through fastboot and it worked ! Then I just downloaded the update and unlocked again and rerooted. I did lose data on internal SD also lol.. I am a noob to Titanium backup and when I redownloaded it couldn't figure out why all my apps were gone..
Or you guys could just download cons rom with the updates in it...
Someone will extract it soon and make a flashable zip
Did any one figure out how to get the OTA to Re-download?
Did any one figure out how to get the OTA to Re-download? Mine downloaded, gave the option to install, said battery to low and try with charged battery. Didn't realize that it was downloading or I would have made sure the battery was fully charged. It has not given me another prompt to install. How do you get to download again? Just deleting the OTApkg.zip will not do it. What other file needs deleting or?
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
paulhoop said:
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
SquireSCA said:
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
Click to expand...
Click to collapse
You have many paths in front of you my friend, depends on where you want to go.
It appears that you are original stock still, rooted with recovery.
Not sure what went wrong. You might want to check for a PH98IMG.zip file on root. Delete it, causes issues with HTBOOT and bootloader.
SquireSCA said:
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
Click to expand...
Click to collapse
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
mjh68 said:
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
Click to expand...
Click to collapse
Yeah, seems like the best way to do it is to just grab the latest RUU and install that and call it a day. No having to worry about it taking, it already includes the latest radio and stuff.
How do you tell what radio your phone is running??
jmorton10 said:
How do you tell what radio your phone is running??
Click to expand...
Click to collapse
Settings->Phone->Software Information->More->
Baseband version is radio
paulhoop said:
Settings->Phone->Software Information->More->
Baseband version is radio
Click to expand...
Click to collapse
Lol, I realize that but what is it supposed to say??
Edit: NVM, I found the info
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