I root my device (samsung galaxy s4), and install the super SU before, unfortunately my friend get my phone and made some changes, he UNINSTALL the SUPER SU improperly, and download/install it again, now I am opening my super SU and it says "THERE IS NO SU BINARY INSTALLED,AND SUPER SU CANNOT INSTALL IT. THIS IS A PROBLEM!", what should I do now?...please help.thank you.
Related
I am using stock rom, i installed busybox properly but in terminal emulator it showing 'applet not found' whts the problem.
Are you rooted? If so, download SuperSU and update the su binary. Reinstall busybox after that (just to be sure). Then see if you get the same error.
yes it is rooted, and how to update su binary?
Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?
Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.
I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.
new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...
*Since this problem can happen to other LG devices, I'm writing here.
-Summarized Question for Busy XDAers-
1.Installed su binary and busybox through Android System Recovery 3e.
2.Can get root access from LG Recovery mode, half access on ordinary boot+adb shell, Permission denied on terminal emulator app. SuperSu not working, and 'root' is granting permission every 5 minutes.
3.HELP PLEASE!
-Full Question-
Maybe it can be a real noobish question, but I need help rooting my G Pro.
LG started Kitkat update a week ago, and G Pro also got Kitkat update.
I tried to root my device using old methods, and new methods for other G devices, but none of them worked.
So! I tried making one for me, using Android System Recovery 3e(maybe it could be a problem?)
I booted my device to recovery using
Code:
'adb reboot recovery'
and sideloaded zip file containing su binary and busybox.
Of course I signed it with testkey, so I could get SuperSu, su binary, and busybox installed on my system.
But, after rebooting my device, I felt something went wrong.
I typed
Code:
'su'
command on terminal enulator, and got
Code:
'Permission Denied'
error.
Assuming it's related to permission and owner of su binary, I tried
Code:
ls -al /system/bin/su
.
Here's the result:
Code:
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $ ls -al /system/bin/su
-rwsr-sr-x root root 85096 2008-08-01 21:00 su
It seems...nothing's wrong!
So I tried with adb, and got # without asking Superuser app.
But I couldn't mount system, as well as other commands require root access.
I removed SuperSu and downloaded Superuser by ChainsDD, but that didn't work.
Instead, I could see on log that 'root' was granting permission every 5 minutes.
Not knowing what the problem is, I rebooted device to LG recovery(diffrent from Android Recovery 3e).
I could access adb from there, and got root access and removed some garbage apps.
Then, it means su binary and busybox is working.
What is the problem??? Please help!
EDIT:It was binary version problem lol
hi guys. i root my lava356 but when i open
super su it says
There is no Su Binary installed and Super Su
cannot install it.This is a problem!
could you help me please??
Hello world,
I try to make something useful out of my Samsung Galaxy Note 10.1 (GT-n8020), so I've started with reinitializing the device with kies, which got me a fresh android kitkat 4.4.2 rom (build: KOT49H.N8020XXUDNI2). After that, I wanted to flash supersu, of course - I've used chainfires cf-autoroot (CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.zip - cant post links, sorry)
I've also flashed philz recovery which works quite well, over odin.
The problem for now is, I cant use the super user binary:
1. The binary was successfully flashed via odin on the device, like the supersu apk. Opening the app just displays a missing su binary, any other app which requires root cant locate or call the file...
2. The following permissions are set on the su file
[email protected]:/ $ ls -la /system/xbin/su
-rwsr-sr-x root root 96144 2015-09-15 14:44 su
3. I've enabled usb debugging because people like to use magic even if this has nothing to do with the main problem
4. I've tried to execute su via adb shell, but it just hangs.
So if anyone could help, I'd be pretty happy - if not, I'm going to throw this f*ck!ng piece of plastic into the woods.
Alright, using N8020-CWM-6.0.2.8-Darkman.tar.md5 as recovery and CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.tar.md5 as root finally worked.