There is no su binary installed? - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

My note was/is rooted. SuperSU used to work and now it doesnt (along with busybox) it says there is no su binary installed, superSU cannot install it. There is a problem!
I have tried uninstalling busybox and supersu, rebooting, reinstalling, rebooting (about 5 times) with no success. I have no recovery installed and am running the stock os. The device status says custom. Ran root check pro (see attached). Any advice or insight into whats going on?

Looks like you lost root. Just root it again using CF Autoroot.
Sent from my GT-N5120 using Tapatalk 4

Related

[Q] N7 LTE root won't stick

I've unlocked the bootloader, installed TWRP and have been trying to install SuperSU v1.65 (and 1.55 previously) but when I tell TWRP to reboot into Android it tells me I don't have root and asks if I want to root. No matter my answer, I cannot get the tablet to boot with root access. Any ideas? I've even tried Wugs Toolkit and SkipSoft's toolkit and neither does the trick. Help!
Hmmmmm.... I skipped the install superSU after I had TWRP because from there I just flashed AOKP.
What are the exact steps you've done?
Sent from my Nexus 7 using Tapatalk 4
jova33 said:
Hmmmmm.... I skipped the install superSU after I had TWRP because from there I just flashed AOKP.
What are the exact steps you've done?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, I thought about just going for a ROM with SuperSU baked in but am still not sure as I'm testing out Paranoid Android on my N10 still. Normally, I just flash a ROM immediately, I've never tried to root and run a stock Google ROM before.
Anyways, I unlocked the tablet immediately as to not lose information once I decided to root and ROM. I had the tablet for about a week before deciding to root it, so of course all the USB Debugging, USB drivers, etc. stuff was already done. Then I:
downloaded CWM recovery to PC
copied SuperSU 1.55 to the root of the sdcard (later on I switched to SuperSU 1.65)
fastboot oem unlock'd it
fastboot flash recovery'd latest CWM
rebooted into recovery
flashed SuperSU
rebooted into Android (this is when I get the "you're device is not rooted..." dialog)
Once booted, root access is not allowed, so I flashed TWRP via fastboot and still couldn't get root. I tried both recoveries several times each. As mentioned before, I have tried both telling CWM/TWRP to root the device and not doing so, but neither way allows me to keep root. This is when I tried SkipSoft and Wugs Toolkits. Both said they rooted the device but I got nothing.
Did you update the su binaries once you booted?
Sent from my SCH-I545 using Tapatalk 4
jova33 said:
Did you update the su binaries once you booted?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Well, SuperSU is nowhere to be found on the device once it boots, so no. I did try installing SuperSU from the Play store and it warns me that the binaries are not updated but then immediately closes and doesn't let me update them (I'm guessing its because I have no root access).
That is odd indeed. Try downloading superSU zip again. If TWRP says you don't have root and asks to fix, say no.
Sent from my SCH-I545 using Tapatalk 4

[Q] Root problems - Titanium Backup is granted root but fails to use it

I installed Philz touch recovery earlier, went to reboot and it told me I wasn't rooted. So i let it root me, and nothing happened (it rebooted but no superuser or anyhing, and no root apps worked). I used Dr Ketan's tool, and let it root, install busybox and remove knox.
I updated superSU (it force closed by default), and then titanium backup asked for root and I granted it. But it says root access - failed."The attempt was made using the "/system/xbin/su" command."
I tried to uninstall gmail through ES file explorer, but it says "unfortunately, ES file explorer has stopped" if you try and do it. Adfree android worked though, and so did rootchecker ("success"), as well as busybox updating and an app that reboots you straight to recovery.
I'm really confused and could do with this root working :S Thanks!
Try flashing this zip
https://www.dropbox.com/s/ylh5ckorv089e4h/UPDATE-SuperSU-v1.93.zip
It solved my similar prob.
Regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Tamen said:
I installed Philz touch recovery earlier, went to reboot and it told me I wasn't rooted. So i let it root me, and nothing happened (it rebooted but no superuser or anyhing, and no root apps worked). I used Dr Ketan's tool, and let it root, install busybox and remove knox.
I updated superSU (it force closed by default), and then titanium backup asked for root and I granted it. But it says root access - failed."The attempt was made using the "/system/xbin/su" command."
I tried to uninstall gmail through ES file explorer, but it says "unfortunately, ES file explorer has stopped" if you try and do it. Adfree android worked though, and so did rootchecker ("success"), as well as busybox updating and an app that reboots you straight to recovery.
I'm really confused and could do with this root working :S Thanks!
Click to expand...
Click to collapse
Download ROM manager from Play Store and run Fix Permisison, After RM done reboot your phone and then try.
Maybe you have to update su.
Sent from galaxy n7105

[Q] How to Delete su-binary ? (lost root)

I root my phone using vroot and got a chinese kinguser, the problem is that I used a method to replace the kinguser and push
a new su-binary and busybox i think and after reboot the kinguser is gone and no supersu was replaced, I have tried installing a new
Supersu kinguser supersu but nothing works just got a message that D su-binary must be updated. Also tried flashing zips for rooting in stock
Recovery and tried many methods for unrooting but nothing works. I just want a suggestion how to delete the su in /system/xbin. TIA
Benamin0318 said:
I root my phone using vroot and got a chinese kinguser, the problem is that I used a method to replace the kinguser and push
a new su-binary and busybox i think and after reboot the kinguser is gone and no supersu was replaced, I have tried installing a new
Supersu kinguser supersu but nothing works just got a message that D su-binary must be updated. Also tried flashing zips for rooting in stock
Recovery and tried many methods for unrooting but nothing works. I just want a suggestion how to delete the su in /system/xbin. TIA
Click to expand...
Click to collapse
you dont need to push superSU just install and update the SU binary and uninstall the king user
Ive tried that constantly and it fails to update the su binaries. Almost like I'm stuck with KingUser. Not that I mind since it seems to work, but it would be nice to be able to switch to superSU if I wanted.
2
Same Problem
Still searching ?
If yes:
http://forum.xda-developers.com/showthread.php?p=61203253
Sent from my GT-I8160P using XDA Free mobile app

[Q] Super SU binary update issues

I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods

[Q] losing root when restarting/powering on

I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I have to restart and try it again 5-6 times anyone know why im losing root
laniclamoore said:
I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I
have to restart and try it again 5-6 times anyone know why im losing root
Click to expand...
Click to collapse
Please reply if need more info let me know what ya need im realy hoping for some suggestions
I had this happened to me a while ago it actually ended up either being an app or an xposed module. Do you use xposed?
I had this problem with Cyanogen mod 11 and running exposed framework.
I switched ROMs and now I have no problems.
losing root
I don't use xposed im just using the root66 stock 4.3 rom I have tried different super user apps no help. Im currently using superSU 2.0 (not the one from market) so far its no longer losing root. I uninstalled the superSU app from the market and used the one I found on a different thread in the Q&A forum. thanks for asking about it I will post if it stops working or anything else goes skiddy wumpus.
Thanks guys.
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Philosuffer said:
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Click to expand...
Click to collapse
Yes I agree I set the SU request during boot to grant superSU root access so the superSU app would protect SU binary from being deleted during boot.
well crap
Crap im once again losing root on restart/boot I've tried using different root methods to no avail. Could it be the SE for Android still says enforcing maybe my bootloader is locked but I don't know how to check if it is. I have not tried custom roms because I don't know which ones work for the t999l lte.
All of the roms are safe to try. They work fine for most people, but if you have problems you can always flash back to what you have now. (Don't forget to make a nandroid backup).
And the bootloader is not locked btw.
Might also help to flash your stock firmware Via Odin. Have you tried the root66 firmware?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
su binary present in xbin but on reboot not executing
Ok im still having the same problem.
I have the su binary installed in the /system/xbin folder but when rebooting from recovery su binary is not detected by superSU but its still in the xbin folder.
This jpeg is when I have full root access is the setuid not present a problem? See errors on second jpeg.
I don't know what info is needed to find problem will someone tell me what info I should gather to help solve problem with su binary (like logcat/busybox version,) thanks
Did you try v1.94 or 2.00? I guess 2.13 didn't solve the problem.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
thread closed use thread "keep losing root access"
There are 2 threads on the same issue. Please use Keep losing root access.

Categories

Resources