I have been trying to root a Pantech Element, but after I have finished the process I get the same message from SuperSU "There is no SU binary installed, and SuperSU cannot install it. I have used several methods, but most people had luck rooting through adb following these instructions http://pastebin.com/HyEyzHJw and others used a program from Bin4ry found here http://forum.xda-developers.com/showthread.php?t=1886460 I've posted of a few sites and never got a response. Is there some way to install the SU binary manually using adb?
Related
Rencently, my phone update to the ICS4.0.4 ROM via official rom。
I tryed to root my device use a 4.0.3 root tool (which worked fine with official 4.0.3rom),but it doesnt work.(2.3.6 is doesnt work too).
BOOT:locked
Reproduce
1.Flash the signed su update pack.
2.run the root tool.
the problem seems su command cant run use "su -c"
after update su zip pack ,I try run su use "adb shell su" in bat file , the # is appeared ,but the terminal freezed,the cursor flash continued,i can't input anythiny anymore,so other commane can't be run too.
Any ideas?
I don't believe there is a way to 1 click root 4.0.4 yet. It's a brand new update so the tools may not work.
The only way I could think of to keeping your root would be to downgrade back and the download "Voodoo OTA" root keeper and "Root Check" from the android market.
Voodoo is an app that creates files in your phone that will store the su- binary and restore it when you update your phone.
Root Check will do just as it says: Check to see if your phone is rooted.
So you will either have to wait for the 1 click root to be updated. Or Downgrade an try again.
Hope this helps!
Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem
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 ...
I originally rooted my LG Vortex (2.2.1) by flashing the su-bin-3.1.1-arm-signed.zip binary within the ArmonRA recovery. Somehow my root apps are no longer gaining root so I'm trying to use the Universal AIO Flasher Tool 1.4 beta to unroot before reflashing the root.
However, the AIO Flasher Tool's unroot process is stuck at ".../adb shell rm /system/xbin/su"
How do I safely get out of this process? Thanks.
OK, I took a chance and hit the Reboot button in AIO and was taken to RA recovery where I rebooted. Superuser app icon was still present and it pointed to superuser3b4.apk, and indicated that no superuser binary was present.
I flashed the SU binary zip, rebooted and gained root. Found that both superuser3b4.apk and superuser3.1.3 were installed in /system/app.
I used the Terminal Emulator to remove superuser3b4.apk. After I rebooted, the superuser3.1.3 icon displayed in the apps menu. All seems back to normal for now.
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.