Related
Anyone know how to get permanent root?What i mean by permanent is when i reboot the phone i still have it.
I usually update to D107 then root phone using one click root method,install magic aosp rom,go to SuperUser(which i placed in /system/app folder) it ask me to update to newest version,i click ok and it works,i get root access in Estrong File Manager and other root apps,i can delete and modify /system folder from Estrong file manager.
After reboot i go to Estrong file manager and it doesnt work any more,SuperUser looses its update and any root app i install after reeboot dont get SuperUser prompt for root access anymore.And if i try to update SuperUser it says that update was successful but at the bottom i don't see new version.I still get root if i adb shell su,but on android i don't get asked for su anymore and i dont think i have root on the phone.Can anyone post step by step instruction for getting "permanent root",Thanx in advance.
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
jokarak said:
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
Click to expand...
Click to collapse
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
lviv73 said:
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
Click to expand...
Click to collapse
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
mykenyc said:
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
Click to expand...
Click to collapse
Thanx man,that fixed my root,you saved me alot of trouble,i guess it was the kernel.Oh and the fluff kernel is probably the smoothest kernel i used so far,now my root is there all the time,thanx again.
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
lockback said:
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
Click to expand...
Click to collapse
if you have temp rooted w/ s=off you do not need to permaroot. The Security Protocol is going to remove any SU access. So you are good to go.
do this, turn off the phone. and pull the battery. put it back it and turn on the phone go to Term Emulator and type "su". do not even worry about the VISIONary program. if the $ changes to a # you are good to go.
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
lockback said:
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
Click to expand...
Click to collapse
Try this.
uninstall Visionary, reboot the phone to clear up any unwanted cache, and reboot into bootloader and clean the cache and the Dalvik cache then re download VISIONary direct from the site via a computer with a Landline connection, or strong wi-fi connection then push the visionary.apk via a USB cable and install it that way.
just to make sure you do not have a faulty visionary program.
I had the same problem, on three phones. I did get it to run one time after uninstalling, rebooting and installing again.
I didn't plan on staying stock though, so I didn't need to run permroot. I just ran temp root with r/w access to system then downloaded ROM manager from the market and used it to flash clockwork recovery. (it defaults to flashing 3.0, but if you want to use Iced Glacier ROM flash clockwork 2.5.1.2) After that I just rebooted into recovery and nandroid'ed my stock ROM then flashed a new one. Iced Glacier is practically stock, so try it first.
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
lockback said:
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
Click to expand...
Click to collapse
Iced glacier is practically stock, you can try that out. All they did on that ROM is remove the bloat and add a overclock kernel.
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
the only 2.3 ROM out for the MyTouchHD is CM7.
EVERYTHING else is 2.2 or 2.2.1.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
Iced glacier is 2.2, cm7 and gingerbaked are the only 2.3 roms out that i know of
Sent from my HTC Glacier using XDA App
While the changes in gingerbread are nice, many are cosmetic and will be wasted in a sense ROM. Sure there are some optimizations and some new API's, but really the difference isn't so great that I would say its a must have update. If you like sense, waiting until we have an official 2.3 based ROM to customize is not a big deal. If you want sense, go for Iced Glacier for the time being.
I like it, though currently I am running CM7... I could take either or really.
I actually quite dislike sense. I swapped out the launcher in the first 30 minutes, and booting Sense is a pretty big plus for me.
I think I'll wait until CM7 gets a proper release and go with that.
Something strange has happened with my Desire HD
I've had CM7 installed and fine for a while, I tried to install the latest Nightlies i got an error about scripts not being able to run. Thought it was just a problem with the nightly and ignored it.
But since then i've noticed problems with other apps that require root privileges.
it seems like i've lost root access some how. it must have happen recently but I can't remember having problems with any apps, but the backup i made before I tried to install the nightly has the same problem.
Anyone had something like this happen before?
I've tried a factory reset but problem remains.
I'm going back to a backup I made 4 weeks ago and see if that fixes it!
Hope I don't have to go through the process of rooting my phone again!!
s0litaire said:
Something strange has happened with my Desire HD
I've had CM7 installed and fine for a while, I tried to install the latest Nightlies i got an error about scripts not being able to run. Thought it was just a problem with the nightly and ignored it.
But since then i've noticed problems with other apps that require root privileges.
it seems like i've lost root access some how. it must have happen recently but I can't remember having problems with any apps, but the backup i made before I tried to install the nightly has the same problem.
Anyone had something like this happen before?
I've tried a factory reset but problem remains.
I'm going back to a backup I made 4 weeks ago and see if that fixes it!
Hope I don't have to go through the process of rooting my phone again!!
Click to expand...
Click to collapse
Have you updated your Recovery to one of the 5 releases? Seems to be reports of losing root when restoring backups on the Thunderbolt
check this link about the recovery issues
https://plus.google.com/103583939320326217147/posts/VSdhDWoA59Z
Thanks I was on recovery 5.0.1.0
Could not update to 5.0.2.0
But my older backup had an earlier version of recovery. Managed to update to 5.0.2.0
Things seem to be fine now...
*Whew* ^_^
s0litaire said:
Thanks I was on recovery 5.0.1.0
Could not update to 5.0.2.0
But my older backup had an earlier version of recovery. Managed to update to 5.0.2.0
Things seem to be fine now...
*Whew* ^_^
Click to expand...
Click to collapse
Pleased to hear you are sorted.
I think you can check if you have root by opening terminal (or adb shell ):
" ls -l /system/xbin/su "
If 'su' command have suid bit "-rwsr-sr-x) (4755) - then you still have root
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<
I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up
Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.
I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.
If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on
No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.
Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser
If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.
Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up
The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium
MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later
hey all, I could use a little help on my phone. I tried to root it and I am stuck I have been using my old evo3d since it came out, and just picked up an HTC 10, so I am rusty on rooting and other things.
Anyway, I unlocked the bootloader on the HTC10 via htcdev,
installed twrp
flashed supersu (this where where the issue started)
so basically I thought I was rooted, did a root checker app and it said I wasn't.
I went to reflash supersu.zip and wiped everything again, but actually wiped EVERYTHING, no OS on my phone now.
Anyway, I am now asking for help. I am S-on right now, can get in to recovery, but just don't want to screw it up more. So could use a few tips. I am thinking about flashing the bad boy rom, but am wondering if I need to be s-off or anything like that? or can I just put the zip on my sd card and flash?
Thanks,
did you flash the modified su
https://tapatalk.com/shareLink?url=...perSU 2.74-2 With ForceEncrypt Set to Default
Sent from my 2PS64 using XDA-Developers mobile app
I did use that one when I did it. It didn't seem to work, (a couple apps said that there wasn't root) so in the process of trying again, I am pretty sure I wiped EVERYTHING on the phone. Literally no android on it at all I think. I can get in to htc download and in to twrp recovery, but nothing else. So at this point, I need to figure out how to flash either a custom rom, or a stock, or what ever just to get my phone back. Thanks for any help
I do know that it does require you to format data because of encryption.
Sent from my 2PS64 using XDA-Developers mobile app
tsbrewers said:
hey all, I could use a little help on my phone. I tried to root it and I am stuck I have been using my old evo3d since it came out, and just picked up an HTC 10, so I am rusty on rooting and other things.
Anyway, I unlocked the bootloader on the HTC10 via htcdev,
installed twrp
flashed supersu (this where where the issue started)
so basically I thought I was rooted, did a root checker app and it said I wasn't.
I went to reflash supersu.zip and wiped everything again, but actually wiped EVERYTHING, no OS on my phone now.
Anyway, I am now asking for help. I am S-on right now, can get in to recovery, but just don't want to screw it up more. So could use a few tips. I am thinking about flashing the bad boy rom, but am wondering if I need to be s-off or anything like that? or can I just put the zip on my sd card and flash?
Thanks,
Click to expand...
Click to collapse
Just put the ROM.zip on the sdcard and flash, ROM is already rooted, no S-off required
Thanks for the help, I think I got it figured out. Reinstalled supersu and then flashed the badboyz rom, seems to be working as we speak, so hopefully got it all worked out.
tsbrewers said:
Thanks for the help, I think I got it figured out. Reinstalled supersu and then flashed the badboyz rom, seems to be working as we speak, so hopefully got it all worked out.
Click to expand...
Click to collapse
Remember that pretty much all your custom ROMs come rooted. No need to root the stock ROM unless you plan to stay stock.
Way too many times I see people having trouble or run into problems trying to root, when all they want to do is install a custom ROM.