Related
I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
Both can be installed. Just make sure SuperSU updates the binary so that it becomes the dominant app.
BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
There's no upside to keeping Superuser if you have SuperSU installed. I deleted it to avoid any confusion personally.
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Yes, you can postpone the update.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Also if it has pre .30 firmware you might consider unlocking it and creating the nvflash files for it if you ever plan on doing anything beyond rooting.
rightonred said:
I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?
Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.
Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.
neo1738 said:
Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.
Click to expand...
Click to collapse
What is "the binary updater"? Last OTA, I had SuperSU and Voodoo OTA and lost root, so I'm a bit concerned there may be something I should have done that I missed. I currently have SuperSU (uninstalled old Superuser) and Voodoo OTA. All the boxes are checked on my Voodoo OTA dialog including "protected su backup".
redheadplantguy said:
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?
Click to expand...
Click to collapse
I can't see what the problem is. Make sure all of the checkboxes are checked in Voodoo and you should be good to go. superuser can be uninstalled using the root uninstaller app.
das0527 said:
Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.
Click to expand...
Click to collapse
Root with debugfs seems to be iffy. Try opening the superuser app, then switch out of it. If superuser is running in the background, the apps should be granted root access.
Also, to restore, you just:
1. Run SuperSU manually once
2. Run Voodoo OTA and restore
In that order, right?
Wonder if I'm good?
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
rightonred said:
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse
droidhaxxor said:
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
Click to expand...
Click to collapse
Whichever app manages root access at the time the backup is made, it backs up the binary for that app.If that binary is the supersu binary than you're good to go. The apk and the binary are separate files though. if you loose the app, you can simply reinstall it from the market. The binary requires root access to manage.
I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app
scataldo721 said:
I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.
fatpandas said:
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.
Click to expand...
Click to collapse
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app
scataldo721 said:
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
if you want to root, i would definitely do it now. mainly because the process if very easy and MOST people have had no problems with it. We're not sure what will happen once JB comes out though.
as for unlocking, i'm not too sure. only thing to be aware of would be that you won't get the OTA after unlocked so you would have to flash it manually. though at that point, you may just go flash some custom roms. just take those into consideration and see what is more important to you.
Bump since jb is out.
Hello,
sorry, im still new to rooting and everything..i've done some basic steps and it appeared that i've rooted my nexus 4 just awhile ago..
after i've rooted my phone, busybox and superSU appeared on my app tray..i've done all the necessary steps and then i wanted to flash a custom ROM onto my phone..i flash Paranoid Android 3+ the latest release which is 3.15..i've done the required steps to flash and i've succeded in flashing the rom..
now, the problem is, i've watched one of the tutorial's on installing this custom Paranoid Android 3+ rom and i saw that man's app tray does have superSU app but mine DOES NOT.
what does this means?..did i do anything wrong?..is my phone not rooted anymore?..i'm a bit worried actually..or is it normal?
i'm a bit confused..pls help me..is there any way to fix this??
thanx!
Using the custom recovery, reflash the ROM then gapps again..
You may just need to reinstall superuser.
Try installing a root permission required app from the play store( SuperUser). If it works you still have root permission and just download a SU app from the play store. If that doesn't work or says root permission required you somehow managed to unroot yourself. You'll have to repeat the process of rooting if its the latter of the two.
Try downloading a root checker from the play store and check. If you just need the superuser files...google is your friend.
Lim Wee Huat said:
Using the custom recovery, reflash the ROM then gapps again..
Click to expand...
Click to collapse
sofyanator said:
Try installing a root permission required app from the play store( SuperUser). If it works you still have root permission and just download a SU app from the play store. If that doesn't work or says root permission required you somehow managed to unroot yourself. You'll have to repeat the process of rooting if its the latter of the two.
Click to expand...
Click to collapse
connorc0405 said:
Try downloading a root checker from the play store and check. If you just need the superuser files...google is your friend.
Click to expand...
Click to collapse
Thanx all..i did tried using the custom recovery and reflashing the ROM again.. the superSU app does not appear..so i just install the superSU app from play store..
Don't follow YouTube videos. They are normally out of date. Your issue maybe that alot of AOSP based roms no longer use a stand alot SU app but have it built into the roms itself. This would bbe why you don't have an icon. Check your system settings for super user
Wayne Tech S-III
Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.
What if you upgrade it using the "normal" method?
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?
brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards
rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.
I'm having issues with my OPO root. I unlocked my bootloader, flashed TWRP and rooted by installing SuperSU through a zip. All was good and root was working yesterday.
I haven't done any Android updates, but my root is gone! If I open the SuperSU app it does this (see screenshot in attachments)
I tried reflashing the zip through TWRP but the same happens after rebooting.
Any ideas?
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Reinstall busybox.
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Sent from N5 or OPO
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Why on earth did you uninstall Busybox in the first place?
Sent from my Evita
Same problem here.
My OpO was rooted and after uninstalling busybox i have the same issue.
Superuser says no su binaries
i tried flashing again an again. Flash works fine but always the same message no su binaries ..
Busybox was stuck on loading data, that's why i uninstall it .
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
wacky.ddw said:
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
Click to expand...
Click to collapse
Don't restore system data when switching ROMs.
Sent via Bacon
timmaaa said:
Don't restore system data when switching ROMs.
Sent via Bacon
Click to expand...
Click to collapse
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
You guys are totally out of a clue.
First: why do you uninstall busybox? Read twice, flash once. If you knew what busybox is for you probably would avoid such errors. Don't tweak your devices if you're not savvy of what you're doing or xda forum will always be cluttered by such threads.
Second: System options backed up can screw up your phone if they do not apply to the ROM just installed causing various problems if not bootloops. DO NOT RESTORE EM. NO WAY.
Hope this helps.
PS: Install busybox from play store to solve the issue.
wacky.ddw said:
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
Click to expand...
Click to collapse
Read what you just wrote and tell me again that you don't want to restore system data.
Sent via Bacon
DuckMcQUack said:
PS: Install busybox from play store to solve the issue.
Click to expand...
Click to collapse
It don't works, install ok but Busybox crash when i open it
ahytes said:
It don't works, install ok but Busybox crash when i open it
Click to expand...
Click to collapse
Personally i would just clean flash again from the start...
Inviato dal mio One utilizzando Tapatalk
Hi, I have the same problem.
I tried to reflash SuperSU, but not working.
BusyBox was uninstalled from my pocket :crying:
What should I do ?
See post right above yours.
Transmitted via Bacon
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Brigitte-Bedo said:
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Click to expand...
Click to collapse
I have this same problem as OP. Ok well since the app keeps crashing on startup, flashing a zip seems like a good idea. Where did you find this zip file?
Same Problem
I lrooted my opo and flashed Sabermods Cm Lollipop and am also getting the same notification, any root needed apps are telling me the phone isnt rooted?? I also tried installing this busybox but wont work cause the phone is coming up as unrooted?
Has anyone a straight answer for this dilemma that doesnt include a full wipe/flash rom again...?
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
mindblizzard said:
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
Click to expand...
Click to collapse
Had this problem to, try to uninstall supersu etc. Flash latest su and problem fixed, im on slimLP rom
Ok, I can't seem to get back root either. I had root and was running ParanoidAndroid. I wiped clean, flashed Cyanogen 12 nightly, flashed Gapps, wiped cache/dalvik. Everything rebooted into Lollipop fine, but I've lost root and can't seem to figure out how to re-root. I flashed the most recent SuperSU (2.46) via TWRP with no luck. Keeps saying I need to re-root first. Any ideas?
So I have watched lots of tutorial videos, used toolkits, etc. but I am unable to root my OPO!
I have unlocked the bootloader and flashed TWRP.
I have flashed SuperSU from TWRP 5-6 times, it says it is flashed successfully, but when I reboot, I don't have root.
I have also tried downloading a pre-rooted stock rom and flashed it but it had the same result!
Any ideas anyone? Btw I am on the latest stock rom (30O)
suffix642 said:
So I have watched lots of tutorial videos, used toolkits, etc. but I am unable to root my OPO!
I have unlocked the bootloader and flashed TWRP.
I have flashed SuperSU from TWRP 5-6 times, it says it is flashed successfully, but when I reboot, I don't have root.
I have also tried downloading a pre-rooted stock rom and flashed it but it had the same result!
Any ideas anyone? Btw I am on the latest stock rom (30O)
Click to expand...
Click to collapse
Here is the best root thread here. have you tried flashing Calks pre-rooted rom. Once you flash this there is no need to flash supersu. Give it a try
playya said:
Here is the best root thread here. have you tried flashing Calks pre-rooted rom. Once you flash this there is no need to flash supersu. Give it a try
Click to expand...
Click to collapse
That's the rom I flashed.. but when I rebooted the device I had no root access!
suffix642 said:
That's the rom I flashed.. but when I rebooted the device I had no root access!
Click to expand...
Click to collapse
did you try and download supersu from the play store and install it that way. also what did you to test the fact that you have no root
playya said:
did you try and download supersu from the play store and install it that way. also what did you to test the fact that you have no root
Click to expand...
Click to collapse
I have tested whether I have root with various apps. Also I cannot remove SuperSU so I tried installing Superuser app from play store but still the same..
suffix642 said:
I have tested whether I have root with various apps. Also I cannot remove SuperSU so I tried installing Superuser app from play store but still the same..
Click to expand...
Click to collapse
go into developer options and check under root access and see what it says
Are you planning to use a custom ROM or what is the goal you're trying to accomplish?
I understand that you're trying to root. But what ROM are you planning to use with ROOT?
Try a custom ROM, do the following
1. Download your ROM, Gapps (if needed), custom kernel (if you want), supersu http://download.chainfire.eu/supersu
2. Put it on your phone
3. Boot into TWRP
4. Factory reset
5. Flash ROM, Gapps, custom kernel, supersu
6. Reboot
... and you should have root.
zephiK said:
Are you planning to use a custom ROM or what is the goal you're trying to accomplish?
I understand that you're trying to root. But what ROM are you planning to use with ROOT?
Try a custom ROM, do the following
1. Download your ROM, Gapps (if needed), custom kernel (if you want), supersu http://download.chainfire.eu/supersu
2. Put it on your phone
3. Boot into TWRP
4. Factory reset
5. Flash ROM, Gapps, custom kernel, supersu
6. Reboot
... and you should have root.
Click to expand...
Click to collapse
Yea he said he did this already but still did not have root. He flashed Calks stock rooted rom
playya said:
Yea he said he did this already but still did not have root. He flashed Calks stock rooted rom
Click to expand...
Click to collapse
I read that, I was suggesting try another flashing custom ROM. I know Mahdi ROM has SuperSU built in but just incase never hurts to flash it.
zephiK said:
I read that, I was suggesting try another flashing custom ROM. I know Mahdi ROM has SuperSU built in but just incase never hurts to flash it.
Click to expand...
Click to collapse
Ok, it does not hurt to try them all if need be. Just the way your post read I am sure he would of said he tried a custom rom but trying more than 1 is something I hope he at least did prior to posting.
OP how many roms have you tried?
Also when your phone boots up, give it a good 1-2 minute before you check if you have root.
Download the SuperSU from the link I provided in the previous post.
Use https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to check. A pop up will appear asking if you want to grant or deny access, grant it.
ok so I found the solution to my problem after flashing supersu using all available recoveries several times!
I unchecked the option "Respect CM root settings" in the SuperSU app and it worked!
btw I can't find a root access setting in the Developers Options. can you guys see it?!
suffix642 said:
ok so I found the solution to my problem after flashing supersu using all available recoveries several times!
I unchecked the option "Respect CM root settings" in the SuperSU app and it worked!
btw I can't find a root access setting in the Developers Options. can you guys see it?!
Click to expand...
Click to collapse
Depending what ROM you're using, its missing built-in Superuser. Just use SuperSU