Related
Hey guys, I followed one of the tutorials on how to unroot your EVO 3D and bring it back to stock. Before I unrooted my phone, I kept getting a notification that an OTA update was available, specifically version 2.08.651.2 (August 18, 2011). Right now, my software number is 1.11.651.2. I want to update to the newer version, but when I go to Settings > System updates > HTC software update > Check now, it shows no updates are available. I've tried rebooting the phone and checking repeatedly. I'm kinda lost here and not sure what to do. I was wondering if the PG86IMG I downloaded to return to stock disabled OTA updates, but I highly doubt that since it's just a stock image. If I could find a download link to the updates, I could apply them manually through the bootloader. If not, I might suck it up and take my phone into Sprint and get them to see what's up and update my phone there. Either way, what do you think I should do? I want it updated though. Thanks in advance.
so u unrooted using the approved method and then tried to update to 2.3.4 via HTC but it would'nt find the update? Just wanna make sure u know that if u take this update ur only option is to root via HTC's unlocked bootloader which isn't a true unlock... secondly if that is ur desire and the stock image won't find the update then i would check ur source and make sure it's not missing something. I turned off my update check cuz once it checks and finds an update that little icon stays in ur taskbar unless u factory reset and i was waiting to root with teamwin's method so i didn't take the update. if i knew how to pull the image without updating id post it for ya...
Yes sir! I understand that updating my software to version 2.8.651.2 will prevent my phone from being rootable until somebody figures out a method to make it rootable. I have no need for rooting my phone actually. I tried out a few roms, and I would rather stick with a stock unrooted rom in case I ever need to take my phone into Sprint for service. The Sprint store where I live won't do any service to a rooted phone, so I need to be on the safe side. I went to the store today, and unfortunately the only people available at the time were sales representatives, so they were of no help. They just told me to wait and keep trying to update the phone periodically. If it doesn't show any updates within the next month, my only choices will be to either call Sprint and see if they can push the update to my phone or find an update image, transfer it to my phone, and manually update it through the bootloader. I also read on an EVO 4G thread that the phone won't update if it's missing SprintUpdater.apk. I doubt a stock rom would be missing that app though. I had the update notification when I was rooted, but I didn't download it because it would break my root, and now that I'm completely back to stock, I should get the notification. What gives? I wish Sprint would send out the updates all at once instead of in waves. Anybody wanna chime in?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Having the same problem. But i havent tried unrooting the phone.
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.
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
When the Samsung Galaxy Note 2 came out on Verizon I got it immediately and obtained root with odin, I think, it's been a while... Anyhow, a few months back the handset began downloading the OTA from Verizon, but it would never install, it would just fail every time. But now, because the OTA is trying to install, that stupid reminder pops up every single day (I always reset the time for the middle of the night so I dont have to deal with it during the day). That doesn't fix the problem, it just prolongs what really needs to be done, To get rid of it I think, I'm not 100% tho, but I think I would have to unroot, go back to stock, except the OTA, and then root again.
I am running with:
Android version 4.1.1
Build number JRO03C.I605VRALJB
Baseband version is I605VRALJB
I never unlocked the bootloader...
Based on that information, what would you say I should do 1st?
I read a lot of guides on this forum but it seems like everyone is rooted on newer versions than me. I don't want to screw things up so I thought I would ask the pros first.
Thanks for whatever help you can offer...
I would unlock, then Judy flash one of the zips of the new ota. Or if you're happy where you're at freeze the sdm app and the popup will go away
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
I would unlock, then Judy flash one of the zips of the new ota. Or if you're happy where you're at freeze the sdm app and the popup will go away
Click to expand...
Click to collapse
Sounds easy but it fails when I try and install the pit and bootloader...
If I am already rooted can I skip to casual?
It's because of these type of issues that I thought that going back to stock and re-rooting would be best, but to do that seems confusing and I don't know where to begin
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
hondaboi20002 said:
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
Click to expand...
Click to collapse
From what I have read the answer is NO. I think you are SOL until a new root method is found.
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
I believe that is your only option, yes. To my knowledge, there is no way to revert back and you're stuck. Unless you'd like to just keep your current phone and wait until someone roots the new update, but your only other option would be to exchange it.
In your opinion, do you think the devs will find a way to crack this update and obtain root?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
Correct. That is *IF* the new phone doesn't already have the update installed, or the sales rep doesn't install the update while activating it and getting it ready for you.
Rumor has it that they already have root, but aren't releasing how until they can find a way to also unlock/patch the boot loader. They are said to be afraid of having Samsung/Verizon block this root method before they can use it to unlock the boot loader. Will they ever get it? Will they ever release the root method? That is anyone's guess.
So for now, it looks like the 16gig DEV edition direct from Samsung, without warranty, is the only option if you definitely want to root and flash custom roms now and "forever". But is it still available? or did they sell out yet?
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
You can block the OTA updater with titanium backup. I'm not on a stock ROM, so I don't remember the updater app name.
Sent from my SCH-I545 using Tapatalk 4 Beta
SDM
That sucks. You gotta keep your eye on those reps :cyclops:
i never let any sales person set up, activate or even power up any phone i buy. if they chose to do so i cancel the order and buy on line where it comes sealed. i always tell them i'm in a rush and i'll take care of activating it afterwards. only one has ever refused and i told him to cancel the sale since he decided to open a product i purchase without my consent. he did get me a new one after that.
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
That is assuming the new phone you get isn't updated b4 u turn it on...
Sent from my SCH-I545 using xda app-developers app
Ok, got a new S4 and this worked !!
Ok, everyone I got a new S4 and activated at Verizon which it immediately started download pretty much as soon as it was turned on. I immediately disabled mobile data, turned it off and then took out the sim card. Once I got home, I hooked this baby up to my PC and rooted...success, finally! I used the I545 all-in-one-root tool which includes OUDS clockwork. http://www.droid-life.com/2013/05/30/all-in-one-root-tool-released-for-verizon-galaxy-s4/
My questions is I have installed ROM Manager so that I could do a backup, but when I first open ROM manager, it says I need to install a custom recovery even though I have OUDS clockwork built in. Do I need to install clockwork from within the ROM manager app? I can reboot into recovery, but its the OUDS "generic" recovery, for lack of a better word. Is that recovery good to go for backing up, flashing another ROM or do I need to use the ROM manager to install CWM from with the app itself? Hope this makes sense. Thanks everyone!!
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
dopediculous said:
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Since I have been doing smartphones, I have NEVER updated, I wait until someone has tried it. and even then, I wait for a dev to cook it up. And everyone better hope you do not have to do any replacements thru the carrier, you WILL get a bootloader locked device with the newest release, NO bootloader fix.
Need to find alternatives.
k1mu said:
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Click to expand...
Click to collapse
That's great news to hear! Unfortunately my location was dead yesterday and I didn't sell any S4's. Just stupid idonts to bubblegum chewing pop tarts and grandparents. Ugh *face palm
Sent from my SCH-I545 using xda premium
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
Yeah, I ordered my S4 online, and it let me defer the update. It downloaded, then said ready to install would you like to install now or later? I set the timer to 12 hours, rooted, installed recovery, flashed AOKP, and bam, no worrying about OTA updates.
Sent from my SCH-I545 using Tapatalk 4 Beta
hondaboi20002 said:
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
Click to expand...
Click to collapse
What I suggest is what I did.
Do not place the sim into the phone.
My phone came from Wirefly.com without the sim card installed.
Power up without sim card, boot directly to download mode, connect to pc usb port, run Odin, follow rooting procedure.
Only after you freeze SDM using titanium backup, should you consider inserting the sim card.
Also while on wifi samsung will ask to install update, say no.
P. S. I installed samsung drivers, and Odin. I did not install kies which I have read also tries to install the update.