I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Twolazyg said:
I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Click to expand...
Click to collapse
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
poashll said:
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Twolazyg said:
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Click to expand...
Click to collapse
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
poashll said:
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
Click to expand...
Click to collapse
Reboot recovery and go back to your last nand, then reboot into whatever rom you were running. Uninstall SU, reinstall from the market, you should be fine then. But I would make a nandroid just to be safe
I attempted to uninstall and reinstall, but it didn't help.
Now that I have updated to 0.1.5, I can upgrade the binary and everything is working as it should.
Sent from my HERO200 using XDA App
I am on 2.3.3 and just updated SU Binary. Haven't noticed a problem yet. All previously installed root apps still work, newly installed root apps work as well.
disregard. I am retarded and didn't read what forum this was in.
My phone's still rooted, I used the same method as you.
Related
Anyone else having problems with titanium backup, i just updated it to the newest version, and now its telling me im not rooted no more? but the phone is rooted.
Are you running a custom Kernel? I just had this same issue yesterday. Let us know if you get it working and if you're able to restore backups. I got it working, but could not restore backups. I keep getting a parsing error.
Coodaddy
Using stock kernal
No im using the stock rom and kernal. all i have done with this phone is root it and now once i updated the backup program now its saying that it cant get root rights.
tomfubarr said:
No im using the stock rom and kernal. all i have done with this phone is root it and now once i updated the backup program now its saying that it cant get root rights.
Click to expand...
Click to collapse
Running superuser.apk?
Can you still get root from a terminal session (su)?
Are you using the latest busybox?
Have you tried letting it install its own app-only busybox?
All my problems I've had with TiB have been with superuser.apk and busybox.
Might not be permanent root then, check other root apps like rom manager or something. Parse error is prob the version of busybox you have, clic problems in tb, then download busybox from within app.
On stock rom/flash a rooted kernel, search the dev section and check again, the joeykrim root is janky
Sent from my SPH-D700 using Tapatalk
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
randomvector said:
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
Click to expand...
Click to collapse
All I can tell you is Voodoo OTA Rootkeeper has worked great for me. Restored root with no problems after 4.2 update.
On my system - however - root causes lag on multi-user that makes it unusable, even with updated SuperSU.
So I am back to being temporarily unrooted because multi-user is more important to me than root.
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
Hmm I didn't experience anything like that, but I only played with multi-user for a few minutes then I deleted the secondary user.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
randomvector said:
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
Click to expand...
Click to collapse
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
I'm using SuperSU and had no issyes with setting up a secondary user.
steevp said:
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
Click to expand...
Click to collapse
Really, can you have a custom recovery like Clockwork manager or TWRP and still receive OTA updates?
GldRush98 said:
I'm using SuperSU and had no issyes with setting up a secondary user.
Click to expand...
Click to collapse
When I get brave - and bored - I will try uninstalling / reinstalling SuperSU again.
For right now, I am just a happy tablet user.
It has been a long time since I have ever done an OTA update.
On most devices I'm typically running a custom ROM and do updates by flashing a new zip from a custom recovery.
I am currently running 4.2 that I got from here:
https://developers.google.com/android/nexus/images#nakasi
I flashed a custom recovery, flashed SuperSU via recovery, and installed BusyBox from the Play Store.
Now my Nexus 7 says it has an update.
Questions:
Will I be able to use OTA Rootkeeper and do this update?
Does OTA Rootkeeper also keep busybox?
Will I have to re-install my programs?
If there is an update to 4.2 why is 4.2 the latest thing I see on the google website I linked to above?
Will I be able to use OTA Rootkeeper and do this update?
Click to expand...
Click to collapse
Root keeper should work fine since of is only a minor update.
Does OTA Rootkeeper also keep busybox?
Click to expand...
Click to collapse
Busybox won't be removed with an OTA update.
Will I have to re-install my programs?
Click to expand...
Click to collapse
No, all your programs will still be there after the upgrade.
[/QUOTIf there is an update to 4.2 why is 4.2 the latest thing I see on the google website I linked to above?
Click to expand...
Click to collapse
Google hasn't built the new factory images for 4.2.1 yet.
EvanA said:
Busybox won't be removed with an OTA update.
Click to expand...
Click to collapse
How is it that su gets removed during an OTA but not but not the busybox executables?
How are the busybox executables different?
Does an OTA explicitly go after su?
I have a notification for an android update as well. I'm rooted and unlocked, running stock. So, I just want to install an app from the market called root keeper before installing the update and all is well?
OTA rootkeeper is the app.
It worked for me, and app usage is fairly simple.
The SU app doesn't get removed, it's still there, it just doesn't have access, but OTA rootkeeper restores it.
I updated yesterday I think, the update mostly fixes that December issue, nothing major, it's a <1,5MB update.
issak42 said:
The SU app doesn't get removed, it's still there, it just doesn't have access, but OTA rootkeeper restores it.
Click to expand...
Click to collapse
Technically, what is going on here under the hood?
What do you mean by "doesn't have access"?
I don't fully understand how root works on Android between the binary su and the SuperSU Android app.
Does the OTA mess with setuid bits or something?
Does it lose access during the "Android is upgrading... Optimizing Apps" after it reboots?
I will do the update using OTA rootkeeper, right now I'm just trying to gain a higher understanding of what is going on.
Edit: Update successful. I have TWRP installed and this is what it looked like. Gave me a scare for a second.
http://i.imgur.com/gAcnt.jpg
FunkyELF said:
Technically, what is going on here under the hood?
What do you mean by "doesn't have access"?
I don't fully understand how root works on Android between the binary su and the SuperSU Android app.
Does the OTA mess with setuid bits or something?
Does it lose access during the "Android is upgrading... Optimizing Apps" after it reboots?
I will do the update using OTA rootkeeper, right now I'm just trying to gain a higher understanding of what is going on.
Edit: Update successful. I have TWRP installed and this is what it looked like. Gave me a scare for a second.
http://i.imgur.com/gAcnt.jpg
Click to expand...
Click to collapse
I honestly don't know what is it that OTA rootkeeper does, I had doubts too. I'm not a developer of said app, so the questions you have should really be addressed towards the dev.
I know the feeling, I have TWRP too, and it gave me a mini heart attack
I'm glad everything worked out!
issak42 said:
I honestly don't know what is it that OTA rootkeeper does, I had doubts too. I'm not a developer of said app, so the questions you have should really be addressed towards the dev.
I know the feeling, I have TWRP too, and it gave me a mini heart attack
I'm glad everything worked out!
Click to expand...
Click to collapse
OTA rootkeeper makes a backup of the such binary and restores it after the upgrade. It works quite well, actually.
Sent from my Nexus 7 w/ PA and m-kernel
EvanA said:
OTA rootkeeper makes a backup of the such binary and restores it after the upgrade. It works quite well, actually.
Sent from my Nexus 7 w/ PA and m-kernel
Click to expand...
Click to collapse
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access
issak42 said:
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access
Click to expand...
Click to collapse
I'm running a rooted stock nexus with twrp. I screwed up with the first 4.2 OTA and had to reroot with fastboot, supersu, etc. When this new one came up last night I installed OTA RootKeeper from the playstore and backed up su with it. I ran the update this morning and had root back in seconds with rootkeeper. Works well, just as described above. The googling involved in my last screwup saved some headaches this time.
Thanks to ALL on this forum.
issak42 said:
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access
Click to expand...
Click to collapse
It doesn't need root access to restore root because BusyBox remains installed. Basically what the app does to restore su is remount the system as read and write then use BusyBox to copy the su binary back to where it should be.
Sent from my Nexus 7 w/ PA and m-kernel
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.
BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)
Just rooted again and its still the same...
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?
Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.
I've been rooted and running Sacs ROM for a while now, but somehow I've lost root access. When I try Supersu it tells me "There is not SU binary installed, and SuperSU cannot install it..."
I have been trying different ROMS and restored from a nandroid backup using TWRP. What do I need to do to get back root access?
Can you not just reroot with CF Auto Root?
Yes, I can, but I wasn't sure if that was advisable or not given that I had root access before and somehow lost it. In any event, I re-rooted using CF auto root and all is well. What I don't understand is how I lost root access in the first place.
joelshort said:
Yes, I can, but I wasn't sure if that was advisable or not given that I had root access before and somehow lost it. In any event, I re-rooted using CF auto root and all is well. What I don't understand is how I lost root access in the first place.
Click to expand...
Click to collapse
No telling why you lost it. Did you take an update?
I know I updated to NC6, lost root, but re-rooting was not an issue.