Related
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?
Hi Guys,
just a quick question before breaking my Phone down ;-)
When I install the NoDo Update, do the Apps installed via XAP installer on a chevron unlocked phone stay working or will they stop working?
Is it possible to get back to the old WinPhone Version by completely resetting the device?
Thanks for your help!
Regards
FB310
Any sideloaded apps will be lost, since they're not tied to your zune/marketplace account. You will aslo not be able to load them again after updating until/unless a new hack comes along
nick109 said:
Any sideloaded apps will be lost, since they're not tied to your zune/marketplace account. You will aslo not be able to load them again after updating until/unless a new hack comes along
Click to expand...
Click to collapse
This isn't entirely correct. The applications will remain on the phone, however the phone will relock itself rendering them useless.
you're right
i keep thinking of nodo-rom flashing
And what about custom ringtones (call and SMS) installed through the Chevron tools ? Will they stay on the phone ?
Aqua-Niki said:
And what about custom ringtones (call and SMS) installed through the Chevron tools ? Will they stay on the phone ?
Click to expand...
Click to collapse
Yes, they stay. Even the Chevron Ringtone Installer still works if the phone if "officially" developer unlocked.
Great =D Thanks for the answer !
have a chevron unlocked focus and nodo. sideloaded apps work and still unlocked. make sure to prevent device relocking with samsung tools or registry edit
can confirm that sideloaded apps still working on my samsung omnia 7 with nodo
(had my device unlocked by chevron and did the prevent from unlocking hack before)
nodo update took about 15 minutes...
sideloaded apps still working after nodo on my optimus 7 too
Ditto on my Samsung Focus. Sideloaded apps still work fine. If you apply the registry change to prevent re-locking, it should persist across the upgrade and remain unlocked. You won't, however, be able to use Chevron to unlock it if you didn't do so before upgrading to NoDo.
HELP!!
It's not working for me! I just upgraded my focus to NoDo and now I can't unlock using Chevron! Help please. What can I do?
My Focus is still unlocked after NoDo. Sideloaded apps still work and I just deployed a XAP file to it and it works as well.
pdangcil said:
It's not working for me! I just upgraded my focus to NoDo and now I can't unlock using Chevron! Help please. What can I do?
Click to expand...
Click to collapse
If I'm not mistaken, you needed to check the "Prevent Device Relocking" in Samsung tools before updating to NoDO. I don't think there is a way to unlock once you've upgraded. You could always revert to the backup from Zune and try again, this time making sure to check the option I've mentioned above. Somebody correct me if I"m wrong
So, I have been searching a bit on how to root the Nexus 7 2013. The process I have found seems pretty simple, even for me, as someone who never worked with a Nexus device before.
Unlock bootloader, flash recovery and flash the root.
But the first step, unlock bootloader, has a problem: it wipes all the user data (including SD Card data!!). As the tablet isn't mine (but I was asked to root it), I can't simply just clear all of its data and do the whole process. Thinking of that, I googled a bit on how to root without unlocking bootloader, but I have found nothing (all recent Sony phones, with a few tricks and the right tool, can do that) regarding the 2013 model.
I'm not sure if there is actually no way to do that or my search skills suddenly got horribe... So, the thing is: Is there a way to do that? Root without having to unlock bootloader (and, thus, wiping all data)? Or I have to unlock it?
EDIT: I found this Toolkit, but did a search and nothing regarding that in the 22 pages of the thread...
http://forum.xda-developers.com/showthread.php?t=2389107
Another few questions that I'm lost: I still haven't quite understood why I have to flash the stock ROM back after I do the whole process... So, why?
And, also, what do I lose unlocking bootloader? I mean, the tablet isn't mine (it's from my younger brother), so the easiest, the best, so keeping OTA updates for example are essential. Do I lose it? What else?
It sounds, for me, some silly questions, but I'm still confused... Seems like doing that kind of stuff is easier with my Sony phone. I don't know if it is due me being used to it, but Nexus is sounding to be WAY more hard than everyone keeps saying it is...
Thanks in advance...
Tell them what is going to happen if they want root. Backup as much of their data as you can, then unlock it. You should be able to get most data backed up one way or another.
At the moment you cannot unlock without wiping because the bootloader enforces that. There might be a way to get around that in the future, but not right now.
When you root, use SuperSU v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Versions prior to that had an issue with preventing OTAs from completing.
1.60 may have some other issues with changes to OTA survival mode.
Not sure where you read you had to flash the stock rom, but it isn't necessary.
You don't really "lose" anything by unlocking it. Someone might bypass your lockscreen to get at your data, but there is a big inconvenience factor leaving it locked (because eventually you'll want it unlocked, at which point it become more painful to backup/restore your data), so you'll have to decide if it is worth the tradeoff.
The issues with stuff not working after unlocking don't have to do with the unlock itself. They have to do with folks rooting and then using their root power to install changes, which then start breaking things.
If you just install SuperSU 1.55 and don't install themes, APM mods, etc. etc. then everything should still work (except apps which specifically won't work, for security reasons, if they detect root)
@sfhub
Thanks for the answers. As I said, I have some Android knowledge, but still got confused with a new "kind" of device. Once again, thanks
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!
I downloaded the Verizon update yesterday and it brought a question to mind. I am just curious about this. I do not have the DE, just the retail version. I assume in order to do the update as downloaded, the update had to somehow have root access. What makes the update so special it can achieve root access and many brilliant people can't? Is there something in the update that allows root access? If there is, what is so special about it that it couldnt be somehow extracted and used for other purposes? I have no knowledge in this area and am wondering if someone knows the answer.
bdraulston said:
I downloaded the Verizon update yesterday and it brought a question to mind. I am just curious about this. I do not have the DE, just the retail version. I assume in order to do the update as downloaded, the update had to somehow have root access. What makes the update so special it can achieve root access and many brilliant people can't? Is there something in the update that allows root access? If there is, what is so special about it that it couldnt be somehow extracted and used for other purposes? I have no knowledge in this area and am wondering if someone knows the answer.
Click to expand...
Click to collapse
very elaborate signed keys. When the update comes from the phone, the phone is coded to look for specific signed authentic keys that gets created when samsung\verizon makes an update file. If the file is modified the update will fail because the keys wont match. A developer may be able to explain it in greater detail, but that's the tidbit i gathered