Basic Unrevoked Forever question. - EVO 4G Q&A, Help & Troubleshooting

I have been reading threads non stop for about 4 days now. Great forum.
Quick question about Unrevoked Forever.
Q: If I apply Unrevoked Forever to my Evo and then apply some future Stock, non-rooted OTA (which may have radios, etc) and I loose root because of it, does having the low-level S-OFF from Forever allow me to run Unrevoked32 again and get root back no matter what the stock OTA did?
I am trying to figure out a best practice for myself so that I can apply stock OTA's and then easily re-root WITHOUT having to wipe everything and redo my settings or even use a backup/restore. I like that the stock OTAs don't require that I clear off everything.
Thanks for any help.

mbwesner said:
I have been reading threads non stop for about 4 days now. Great forum.
Quick question about Unrevoked Forever.
Q: If I apply Unrevoked Forever to my Evo and then apply some future Stock, non-rooted OTA (which may have radios, etc) and I loose root because of it, does having the low-level S-OFF from Forever allow me to run Unrevoked32 again and get root back no matter what the stock OTA did?
I am trying to figure out a best practice for myself so that I can apply stock OTA's and then easily re-root WITHOUT having to wipe everything and redo my settings or even use a backup/restore. I like that the stock OTAs don't require that I clear off everything.
Thanks for any help.
Click to expand...
Click to collapse
There is one thing I dont understand and that is if you root your phone why would you run OTA updates. Someone in XDA will have that update and put it in a form that you can use on your rooted phone. People updating after they root really baffles me... <-----Sorry bout that
Now to answer your question - I believe your best route would be to root your phone with this method here and this way you lose nothing and can just get an update.zip file after an update comes out. The problem is you never know what will change in future updates and a OTA may unroot your phone. Since none of us know for sure thats a risk you will have to take although unrevoked forever is suppose to get around that.

Related

Want to upgrade to 2.2, but not sure how to proceed

Greetings all,
My Evo is still at 1.47 after foolishly taking the OTA update, and I haven't yet re-rooted it after the exploit was discovered. I want to upgrade to 2.2, but I am hesitant to do so after all the warnings from last time about taking OTA updates.
I really am not interested in a custom ROMs all that much, as I prefer stability and I want my 4G to work correctly.
With that said, I do want to keep my future options open. So, with that in mind, how should I first proceed?
I don't care about losing my apps and data, etc. I will reload.
- Should I follow the tutorials to first fully unlock the NAND?
- If so, can I then apply the official 2.2 update over the air?
- If I do that, and I have unlocked the NAND, can I revert to rock stock later?
- Is there a way (kitchen?) to keep the stock ROM and just remove some apps?
Thanks for the guidance, just want to proceed cautiously.
-Rob
robroy90 said:
Greetings all,
My Evo is still at 1.47 after foolishly taking the OTA update, and I haven't yet re-rooted it after the exploit was discovered. I want to upgrade to 2.2, but I am hesitant to do so after all the warnings from last time about taking OTA updates.
I really am not interested in a custom ROMs all that much, as I prefer stability and I want my 4G to work correctly.
With that said, I do want to keep my future options open. So, with that in mind, how should I first proceed?
I don't care about losing my apps and data, etc. I will reload.
- Should I follow the tutorials to first fully unlock the NAND?
- If so, can I then apply the official 2.2 update over the air?
- If I do that, and I have unlocked the NAND, can I revert to rock stock later?
- Is there a way (kitchen?) to keep the stock ROM and just remove some apps?
Thanks for the guidance, just want to proceed cautiously.
-Rob
Click to expand...
Click to collapse
DO NOT UPGRADE/UPDATE, do a full root then flash any of the Froyo/2.2 ROM's already rooted
most of the release roms have 4g working as well as are very stable. I bet if you tried any of the custom roms you would be suprised. I have very few issues with the custom roms i have used (mainly fresh and dc). As i need my phone everyday for work and am a very heavy user because of it i can tell you hat you will probably be fine with any of the big custom roms (cm6 excluded if you need 4g)
Now on to the question if you root and then take the OTA you are basically jsut wasting time as it will unroot your phone. Your best bet is to root the phone and then if you dont want a custom rom find the stock rooted 2.2 rom in the dev section and flash that. it is the stock room except it doesnt override your root. nothing else is done to it.
This would allow you to have froyo on as close to the ota as possible while not killing your ability to root or taking away your root.
This. I'm lost along with all of the other users who applied the OTA to 2.2 (I have the leaked version). Once I get root again I will never unroot, ever. Flash this ROM (Post ID: 740520, can't post links yet), it's the rooted OTA ROM for 2.2. Keep your NAND, keep your root... having official software means you're stuck with terrible "official" support from HTC and Sprint.
Best of luck.

[Q] How, exactly, does an OTA update break your ability to root, forever?

By the question you can tell that i'm rather inexperienced at this, but a buddy of mine(who has a Droid on VZW) and i were debating whether or not doing an OTA update after you root would cause you to loose your ability to root forever.
I guess it's different on both devices, but he contends that he could unroot his droid, which is running a custom 2.2 ROM, install an OTA update, decide he doesn't like it, then just go back to a 2.1 RUU from VZW or Motorola, and then re-root.
Everything i have read here about the EVO indicates that if i am already rooted, and i accept an OTA update, then i will never be able to root again. Does never, really mean never? Or is it just mean that i won't be able to root using the current methods to root the phone?
What if i had never rooted and then accepted the OTA 2.2 from sprint that may be coming this week, would i then be able to root?
What exactly does the update do to remove the ability to get /root access to the phone? Something with the bootloader, HBOOT, or what?
Thanks for the information. Hopefully, this will settle this question for my friend and I.
Chris
OTA updates typically break any existing root methods, and disable any current root access.
Some OTA's also update the phone in a manner which prevents older official roms (that have working roots) from being reinstalled.
At that point, you have an updated rom with known roots removed, that can't be rolled back, so the only option is to wait until another root exploit is found and released. Which may or may not happen depending on the device and whoever is working on it.
Hope that helps.
You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files
HTC is tricksy and they dont let you roll back after the OTA. Motorolla may not have this so your friend may in fact be able to roll back to 2.1 (however he may be misinformed as well).
To root basically they find a bug to exploit that allows us to gain access as a root user. when the OTA updates come out 99% of the time they will fix this bug. HTCat least blocks roll backs so now you are on a new version of the software that you can not go backwards and the bug to root is no longer there.
While there are normally other bugs that can be exploited to get root it is possible that there isnt one or that if there is no one can find it. if they cant find it then it could remove your ability to root permanently.
snandlal said:
You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files
Click to expand...
Click to collapse
while true accepting an OTA will not give you the chance to do this for most.
ok, that explains things a little better. thanks.
I'm new to all of this as well. My EVO has already been updated OTA by a Sprint employee while I was purchasing the phone. From what I've read it looks like I'm SOL until someone cracks 2.2. One quick question though... How long did it take people to be able to root the first software on the EVO's?

[Q] Evo with Hboot 2.10 and S/W 3.70. Want to temp root to remove apps,any options?

Hello all!
First I am not new to flashing and/or hacking phones I have done many back in my WM and other phone days,just somewhat new to Android
I have looked around and I think I already know whats up but I can't say I have seen this question asked yet...I did search
Here we go,
I have an Evo with Hboot 2.10 Stock sprint flash (as in from the sprint store) and I updated to S/W 3.70 with out first checking to see what it had...(yea stupid of me )
What I want to do is Temp root into the phone,use Ti backup or whatever to make a back up of the stock apps and then remove them. I only want to remove the sprint tv,nascar,blockbuster and other apps that I don't use that don't tie into the rest of the OS.
I tried with Z4root but seeing as I have S/W 3.70 not much happens
I don't really care to flash to new rom as I am happy with the stock flash just want to get rid of apps I will never use.
So far my only option is to wait from what I have looked up,I just wanted to know if I could execute my plan with out a full system flash.
Thank you for your time and if anyone needs more info I will be glad to give it!
Yes, it seems 3.70 has patched the exploit that z4root was using to get temp root. Until the devs find a way to get a new exploit you'll have to wait.
With the rate these Devs work, I'd give it a week and you should be able to root your phone
Thanks!
I figured that was what I would have to do,but it never hurts to ask
A quick update.
It seems as if Z4root still does work even with the 3.70 OTA update...
I was searching around on Google and found people with this exact set up that had been able to temp root.
Not sure on the why yet but I had to do a reset to factory default first in order to get z4root to give me temp root(Maybe something from the update was hanging around on the phone blocking z4??). I then fired up TI backup and started to remove the Sprint stock apps I don't use and and a few other save to remove ones!
So if anyone is looking to stay on the stock sprint rom and has S/W 3.70 this might work for you as well!
And now I am fully rooted and running the sprintlovers rom. I was able to follow the guides here and get my phone flashed up.
If anyone has the same set up and needs help let me know!
How did you get permanent root on 3.70? I was going to try the'savior' adb method, but I'm afraid of bricking. I did just download unrevoked's new beta root though. I might try that when I get home
Sent from my PC36100 using XDA App
how did you get root? I'm thinking of the savior method too (same evo specs). I'm guessing you used that since you're on sprintlovers?

[Q]Going from 4.22 to 4.24 OTA if you kept it stock and rooted will keep the root?

Going from 4.22 to 4.24 OTA if you kept it stock and rooted will keep the root?
Going from 4.22 to 4.24 was just bug fixing and does not touch any part of the phone other than those bugs?
okay, so is this true? I have yet to see a real answer of yes or no. I saw people with 2-3 posts saying it. but need an expert opinion on this? It takes a long ass time to put my phone back to how it was when I do a full wipe/flash. just trying to save some time. Don't have time to sit and wait 2-3 hours for my phone to recover. so the OTA doesn't in any form or way touch bootloader or root or anything that would cause damage to the OS? of course talking about the 6M one. lol
runcool said:
Going from 4.22 to 4.24 OTA if you kept it stock and rooted will keep the root?
Going from 4.22 to 4.24 was just bug fixing and does not touch any part of the phone other than those bugs?
okay, so is this true? I have yet to see a real answer of yes or no. I saw people with 2-3 posts saying it. but need an expert opinion on this? It takes a long ass time to put my phone back to how it was when I do a full wipe/flash. just trying to save some time. Don't have time to sit and wait 2-3 hours for my phone to recover. so the OTA doesn't in any form or way touch bootloader or root or anything that would cause damage to the OS? of course talking about the 6M one. lol
Click to expand...
Click to collapse
I wouldn't chance it. There were a couple of OTA's back in the day that didn't touch the bootloader (that I was aware of) that caused people to lose root. In particular this affected me because one of the updates didn't have a root exploit and I needed to wait a week or two to root my phone (so...awful...haha)
I mainly want to know if someone has done it on this exact update and if it worked or didn't work. :-D
runcool said:
I mainly want to know if someone has done it on this exact update and if it worked or didn't work. :-D
Click to expand...
Click to collapse
The only people who would have done it are people who don't read in the first place. If they did read, they'd know that nobody recommends accepting an OTA when you're rooted. So since anyone who's tried what you're asking doesn't read, they won't have read your post either.
You will lose root access when you accept the OTA. Normally you can get it back if you're S-OFF, though there's always some level of risk if they really wanted to get serious about locking people out. But there's no reason to try, since you can go here and just flash a rooted version of the ROM. You'll end up doing that anyway if you want to have root access, so you're wasting time and taking a risk by accepting the OTA.
You should be able to flash the updated rooted rom without wiping data -- just wipe cache and dalvik cache and then flash it.
I'll try it next weekend. lol. just didn't want to spend time doing it. haha
runcool said:
I'll try it next weekend. lol. just didn't want to spend time doing it. haha
Click to expand...
Click to collapse
Use recovery to do a nandroid (include android_secure and ext3 in the backup if you use them), and then there's really no risk of losing your setup. You can always restore back to where you are. A Titanium Backup run is also quite useful. But like I said, you should be able to flash the rooted 4.24 ROM over the rooted 4.22 you're running with only a wipe of cache and dalvik. That's basically how the OTA does the upgrade for non-rooted users.
Yes you can update without losing root as long as you have used either the newest unrevoked method for evo's OR unrevoked forever. Just do not update over the air, as in just download it but do not install it. Follow this link step by step:
http://forum.xda-developers.com/showthread.php?t=1109272
It's never a good idea to accept an ota update if you are rooted.
mizzouse said:
Yes you can update without losing root as long as you have used either the newest unrevoked method for evo's OR unrevoked forever. Just do not update over the air, as in just download it but do not install it. Follow this link step by step:
http://forum.xda-developers.com/showthread.php?t=1109272
Click to expand...
Click to collapse
But that's if you're going from the old one to the completely new one. I'm going from 4.22 to 4.24
The instructions given are flat out wrong and don't even work. the OTA isn't in the cache folder. I've checked. errrrrrrrr. sounds like it needs to be updated. that thread is clearly upgrading to 22, not 24.
Well, I'm just going to use clockworkmod to install it. lmao Will this work?
Flash one of the roms in the development section. Wipe cache and dalvik like stated and go on about your way without risking your root status.
Besides that, if you did first flash a deodexed 4.22 from here and try to apply the sprint 4.24 patch you will have a system conflict between the odex and deodex files
To help answer your question, if you're currently rooted and accept the OTA, you will loose root access, BUT as long as you don't flash the S-On tool you will still be able to flash after downloading a custom recovery such as Amon_Ra and then continue flashing whatever you want. I have done this to many phones since the update and haven't had a single problem yet. But if you flash S-On, you're screwed until they are able to hack the new Bootloader.
Even after accepting the OTA and having S-Off, your hBoot will update but you Can go back to Froyo if desired and hBoot will change back to Froyo compatible 2.10 not 2.16. So I hope my answer helps and will let you know what you're looking for!
I installed the 22 odex version. and I am now at this second doing the 24 odex version. so hope everything goes well. haha. if not. made a backup. so hope the backup works. :-D Just trying to avoid spending hours on getting my phone back in order because downage means money and time lost.
EDIT= so CONFIRMING that going from 22 to 24 with going through clockworkmod completely works without any issues. I was just afraid to do it. hahahaha just as long as you don't wipe data and cache

[Q] If you are s-off w/root and custom recovery...why take OTA?

I don't get it....
I have been rooting and customizing since my Droid 1. In all that time over several devices...there was never a need to un-root and take an OTA...that was not soon made available through Dev's that could be flash via customer recovery, or pushed via ADB.
But I keep reading how all these HTC One users are doing just that.
I got my One on Thursday from VZW store, and it was still running 1.10.605.8. I figured that once s-off and rooted I could flash any new radios/modems...and the ROMs would take care of the rest...so no need to update to 1.10.605.15.
Currently running EclipticOne with the 1.10.605.15 radios.
Am I wrong? Is there something I missed?
Thanks,
I think it's the amount of people who are new to the process of how to handle taking updates when they're S-Off/Unlocked Bootloader/Rooted. The only way they've ever known to do Android updates is taking OTA's. They're new to the paradigm of manually updating radios, hboot, and /system.
It can't be stressed enough that OTA's are designed for completely stock, untouched devices. OTA's aren't made with hacks in mind, nor will they ever be, nor should they be.
If you want to go S-OFF, unlock the bootloader, install a custom recovery, and get root, you have to be willing to take on some of the extra responsibilities that come along with it. One of those is forfeiting a normal OTA process. OTA's will, at the very least, remove root. You're going to have to boot to recovery to reinstall superuser so you might as well just do all the updates manually.
Really just a matter of preference and what you are after. This is the first phone I have owned that I am content running stock, other than a few apps that require root. It's actually faster for me to take the OTA and reflash custom recovery/supersu which are already on my computer than to wait for someone to upload the goods.The end result is the same, just different ways of getting there, none better than the other.
xenakis said:
Really just a matter of preference and what you are after. This is the first phone I have owned that I am content running stock, other than a few apps that require root. It's actually faster for me to take the OTA and reflash custom recovery/supersu which are already on my computer than to wait for someone to upload the goods.The end result is the same, just different ways of getting there, none better than the other.
Click to expand...
Click to collapse
I could be wrong but if you take an ota and expect to retain root and s-off every time, you might be in for a surprise. im pretty sure certain updates have been pushed that relocked bootloaders and removed s-off.
MJL99 said:
I could be wrong but if you take an ota and expect to retain root and s-off every time, you might be in for a surprise. im pretty sure certain updates have been pushed that relocked bootloaders and removed s-off.
Click to expand...
Click to collapse
It was my understanding S-OFF stays on/off (whatever) no matter what OTA you take.
Sent from my HTC6500LVW using Tapatalk
Though folks often warn that an OTA may remove s-off, I have never seen evidence of one doing this and could not find any posts on XDA or anywhere else about this happening. And while it is technically feasible for an OTA to remove s-off, I can't imagine any phone maker or carrier doing so. More important for them is patching known exploits, which if you already have s-off is not an issue since the exploit was only needed to get you s-off, not to keep you there.
Obviously, this wouldn't be the first time that I am wrong and welcome anyone to post a link to an example of an OTA undoing s-off. I'm only here to learn and if you keep me from screwing up my phone, I'll thank you!

Categories

Resources