Basically, I have unlocked the bootloader and flashed the Cwm recovery touch.
When I choose to reboot from recovery mode, it says I don't have root access and do I want to make it. I selected yes.
After the reboot, I downloaded root checker and the result is successful. However, it seems that every app has root access, even after I installed Superuser app. Is there anyway to control which app to have root access?
Thanks in advance
Related
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
So far so good? Am I missing anything?
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Didn't miss anything.
You can go several ways: since your bootloader is unlocked, to save yourself the pain with ADB loop method, which is completely unneeded, you can just use the regular method, skipping the "unlock bootloader" part, which leaves you with "flash custom recovery" part (totally independent) and then just flash whatever ROM you like, pre-rooted. You don't need to flash a rooting file over your ROM, you just can change your ROM to pre-rooted one.
So you are saying that I can flash a custom recovery, then load a custom rom that is pre-rooted?
How do I flash a custom recovery if I am not rooted? I thought that in order to get the recovery you needed to root via superboot?
And I must have a custom recovery in order to have a pre-rooted rom, otherwise the phone will reject the package, right?
So the only thing that prevents root on the Android is the rom and recovery partition's own integrity check for whatever you are flashing? In other words, people can lose root by flashing a stock rom, and you can get root by flashing a pre-rooted rom. I seem to remember seeing some pre-rooted packages saying that you must have previously had root in order for it to work. Is that not correct, then?
Thanks.
hgcrpd said:
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
Click to expand...
Click to collapse
Not exactly - root access simply indicates having the su and superuser.apk binaries installed, and the suid bit set on su. But you are close enough. If you are running FroYo, Cyanogen and Lox have published flashable rooters.
You will already need a custom recovery to flash either of these - but since your bootloader is unlocked, a custom recovery does not pose any problem - see below...
hgcrpd said:
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
Click to expand...
Click to collapse
Yes.
hgcrpd said:
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
Click to expand...
Click to collapse
Couple of points here:
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
2. Recovery does not use the same shell and variables as /system. Busybox is usually installed in recovery to allow you to run things via ADB or scripts when in recovery mode without manually calling them off of system (something that would be a problem if you were formatting and rewriting system, for example).
hgcrpd said:
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Click to expand...
Click to collapse
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you? In any case, I would just install the SDK - it's free, fast and gives you access to fastboot and adb. You need fastboot to install a custom recovery, and adb is useful for lots of things.
And there are plenty flashable root zips for FRF91. You need to first install a custom recovery!
http://forum.xda-developers.com/showthread.php?t=715799
http://forum.xda-developers.com/showthread.php?t=686627
So, if I were you:
1. Install the Android SDK on your computer to get ADB, fastboot and the necessary drivers.
2. Download and flash a custom recovery using fastboot.
3. Reboot into recovery.
4. Copy Lox or Cyan's rooter to your SD card using adb push.
5. On the phone, in recovery, do a nandroid backup!
6. Flash the zip from step 4.
7. Reboot your phone and confirm that you have root - the easiest way is to start up a terminal session and type "su". The Superuser authorization program should pop up and ask you to approve the application's request for root access. Grant it. If the prompt turns from "$" to "#", you have root.
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
Click to expand...
Click to collapse
I see. So the post on modaco is not quite correct when it says that root is a pre-req for Amon_RA's recovery. I'm guessing that's only a pre-req if you flash via a terminal session on the phone? (By the way, is there an official terminal app? The only one I could find was Terminal Emulator.)
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you?
Click to expand...
Click to collapse
Bootloader was unlocked when I bought it. The phone is a grey-market item that I purchased here in China, and every grey-market phone that comes in gets modified by the importers in order to add Chinese language support and such. I think that's all they did, since I've been able to do updates and get OTA without a problem.
Thanks! I will give the SDK route a try, if I get time before the superboot for FRF91 comes out.
Hello guys,
I want to share a pain reliever for many trying to upgrade Superuser with SuperSU without loosing root and successfully installing it's binary.
First you need a recovery for your Atrix HD which I recommend CWM Touch or a working up to date CWM recovery for other devices.
Download SuperSU-v1.43.zip file
Go to recovery and flash SuperSU-v1.43.zip
Go to any app that require root access to make sure is working. Once you see the prompt and hit ok or accepted it, go to Play Store and update SuperSU.
Once done, open it and when it ask you to install tje binary Normal install or by Recovery choose recovery and it should reboot to it. It will flash the binary (dont freak out if all you see is the loading bar)
Once flashed is done it will reboot the phone normally.
Confirm if SuperSU is working by opening back again SuperSU app and if you see everything as it should then job is accomplished and followed to the T.
Eventhough Superuser works great right now, SuperSU is few step ahead.
Ok, i am in the soak test for ATT Kitkat 4.4.2 (XT1058). I reverted back to stock, and took the OTA update.
I have an unlocked bootloader, so i mfastboot flashed TWRP recovery 2.6.3.1 with success
i've tried unofficial TWRP 2.7.0.0, and philz_recovery w/ no luck
I flashed supersu (via zip) v 1.89 and v 1.93, recovery reported success
Reboot, Supersu is not in my app drawer. I installed Supersu via playstore with success, installed "binary" with reported success.
Tried Superuser from Clockword Mod, no luck
Supersu crashed upon launching Titanium Backup w/ TB hanging.
It appears Supersu is not installed correctly.
What am i missing? Installing Supersu should be the easiest thing on an unlocked bootloader.
cpetersen2791 said:
Ok, i am in the soak test for ATT Kitkat 4.4.2 (XT1058). I reverted back to stock, and took the OTA update.
I have an unlocked bootloader, so i mfastboot flashed TWRP recovery 2.6.3.1 with success
i've tried unofficial TWRP 2.7.0.0, and philz_recovery w/ no luck
I flashed supersu (via zip) v 1.89 and v 1.93, recovery reported success
Reboot, Supersu is not in my app drawer. I installed Supersu via playstore with success, installed "binary" with reported success.
Tried Superuser from Clockword Mod, no luck
Supersu crashed upon launching Titanium Backup w/ TB hanging.
It appears Supersu is not installed correctly.
What am i missing? Installing Supersu should be the easiest thing on an unlocked bootloader.
Click to expand...
Click to collapse
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store
asuhoops8628 said:
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store
Click to expand...
Click to collapse
just rebooted into TWRP, was not prompted to root.
Follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 it works and has the latest versions you need.
asuhoops8628 said:
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store
Click to expand...
Click to collapse
KidJoe said:
Follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 it works and has the latest versions you need.
Click to expand...
Click to collapse
Followed them, still nothing. Basic Root Checker confirms no root. I used Terminal Emulator, and tried the su command, and it hangs up. Does SuperSU need an update??
Confirmed via ES File Explorer that Superuser.apk is in the /system/app folder.
Any other suggestions?
cpetersen2791 said:
Followed them, still nothing. Basic Root Checker confirms no root. I used Terminal Emulator, and tried the su command, and it hangs up. Does SuperSU need an update??
Confirmed via ES File Explorer that Superuser.apk is in the /system/app folder.
Any other suggestions?
Click to expand...
Click to collapse
would a factory reset help!
That thread has the exact versions of TWRP and SuperSU that I used to root, and countless others have rooted theirs on 4.4.2 as well using that process.
So I'm not sure what to say other than make sure you are using those versions from that thread (down load them again if you have to). And go into SuperSU, under settings, make sure default access is set to PROMPT, and remove anything that might be listed under Apps, reboot the phone, and try the root checker or other app that needs root again.
Another option is to un-install SuperSU via android's App Manager, reboot into TWRP, and try installing SuperSU again
KidJoe said:
Another option is to un-install SuperSU via android's App Manager, reboot into TWRP, and try installing SuperSU again
Click to expand...
Click to collapse
That did it, apparently i have 2 versions installed, and uninstalled one of them, then it fired right up. Thanks for the tip!
I wonder why I am losing root no matter which rom I flash.
I am with S-ON. I have checked that the rom I flash will work on S-ON.
They all root the device with SuperSU.
I have done a Full wipe every time I flash a rom.
The superSU works perfectly when newly flashed. But after I install applications and use the phone for a period of time, the SuperSU stops working.
I sometimes perform a temporary unroot to run some applications that requires no root.
It is usually able to recover from temporary unroot. But, sometimes after temporary unroot. When I root it again with superSU, it will restart without doing anything. Then when I go to superSU after restart, it will require me to Update the SU Binary. But if I click update, it will turn black screen and restart AGAIN.
And I try to flash the SU Binary with TWRP, TWRP just turn black and restart the phone after I choose the zip. I have repeated these a couple of times with a couple of ROMS. They are all Android 4.4.2 with Sense.
I cannot even see any error message updating the SU Binary, the phone just turn black screen and restart. This is really annoying...
I have tried to flash a CWM for updating the SU Binary, but it works exactly the same as TWRP. However, when I quit CWM it will prompt a message about losing root and ask if I fix it or not.
I have pressed "fix it" once before, and it brick my device...
Does anyone have the same problem here? I think it happens more likely with S-ON.
Hi I have a HTC One Dual Sim (m7) 5.0.2 android. I have unlocked the bootloader using htcdev.com, but cannot root the phone. I have used Kingroot, Kingo root and iRoot. Kingo and King both say rooted sometimes but it goes away quickly (dont even need to restart). Is it impossible to root the phone using these apps? thanks!
Do not use any of those apps to root.
You have already unlocked bootloader so next step is flashing custom recovery. You can find twrp recovery here. Do a fastboot install method. After you flashed recovery download supersu zip file from here and save it on your phone. Reboot phone to recovery and tap install. Find supersu and install it. After that reboot phone (your phone will restart itself a couple times during boot) and your phone should be successfully rooted.
The phone comes with the bootloader unlocked? interesting. Any toolboxes I should use?