I am running FR007 on my aria. I am getting a su binary outdated message when launching titanium backup. The message says my su binary installed version is 2.3-ef and that the latest version is 3.0.3. When I try to update the su binary it fails and my aria reboots. My currently installed superuser version is 3.0.7.
I would appreciate instructions on how to fix this issue.
That is outdated. Just flash the attached file via CWM Recovery.
I appreciate your help Theonew. That seems to have fixed the problem.
Hi,
I lost root access under CronosX by trying to install superuser update.
How to recover root access (I have again openrecovery)
Thank you
Go to su in app management & un install updates. Grab the su update.zip from androidsu.com & apply in recovery
Sent from my Galaxy Nexus using xda premium
I succeed to restore su but I have again a problem with update : it fails to update to 3.1 binary from app : error at testing new su work.
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 ...
Hi today I tell you how to fix super su problem
To fix we need to install the latest version of busybox
Next we need to install vroot and root the device..
Notice: we have to open busybox befor root the device
And your device now rooted!
Hey everyone,
I'll be showing you the easiest way to replace Kinguser/KingoSuperUser or any other superuser app with SuperSU.
Procedure:
1. Download & Install ES File Explorer
2. In ES File Explorer menu ☰ , scroll down and enable the Root Explorer option
3. Now click on Homepage > Device > System > app
4. Once you're in the system/app folder, look for Kinguser.apk or KingoSuperUser.apk or any other Superuser apk that you have.
5. Delete that Superuser.apk, and go to Playstore and install that same Superuser app. Once installed, uninstall it from Playstore.
6. Now download and install SuperSU and update binaries via normal mode.
7. After 2 to 5 minutes, your binary will be updated, SuperSU will be installed correctly and now reboot your phone.
Note: Do not worry, deleting the SuperUser .apk will not unroot your phone. And this is also a fix for binary update issue.
MSalmanKhan17 said:
5. Delete that Superuser.apk, and go to Playstore and install that same Superuser app. Once installed, uninstall it from Playstore.
Click to expand...
Click to collapse
I don't understand that step. I rooted with KingRoot but this App isn't on playstore.
So I deleted the .apk, installed new from my downloaded apk and uninstalled with Titanium Backup.
The SuperSU still complains that it cannot replace the su-binary.
Any idea?
My phone is a Honor 4X Che2-L11 with an ARM Cortex-A53 Processor.
tosho1 said:
I don't understand that step. I rooted with KingRoot but this App isn't on playstore.
So I deleted the .apk, installed new from my downloaded apk and uninstalled with Titanium Backup.
The SuperSU still complains that it cannot replace the su-binary.
Any idea?
My phone is a Honor 4X Che2-L11 with an ARM Cortex-A53 Processor.
Click to expand...
Click to collapse
I followed the manual steps that Supersu says when installing the app (redirects to a web). It says there are 2 options, the other is installing Supersu-Me, but I haven't tried that (there seems to be issues for Lollipop). Also, in my device there was only one Kingo Superuser app and a Kingo Link app (I have seen webs where Kingo installs up to 3 things).
You need root (Kingo), su binary file, busybox, terminal emulator, ES explorer, supersu app.
Step 1: Install ES explorer with root.
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize .Su. For that, open terminal and type:
system/bin/su
mount -o rw,remount -t rootfs rootfs /system
chmod 777 /system/xbin/.su
Step 5: delete the other SU files, such as ksu, etc.
# check attributes
busybox lsattr /system/xbin/su
# remove a and i
busybox chattr -a /system/xbin/su
busybox chattr -i /system/xbin/su
# remove su
rm /system/xbin/su
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps, uninstall KingoRoot,
open SuperSU, it should ask to update binaries, choose yes, choose NORMAL, and reboot.
Hope it helps!
where is file ,
pzl upload the su file here,
and ur procedure is not understanding
properly ,
plz give procedure how to do this ,
or upload video,
@tosho1 its because huawei protect system partition on locked bootloader devices.
reflash stock rom, root with kingroot, flash twrp with rashr, unroot inside of kingroot and flash supersu with twrp
(you will be able to unroot because system is still mounted after rooting but after reboot you wont be able to touch it, thats why you have to use kingroot only to flash twrp and then remove it when you are still able to)
(method tested and working on my own che2-l11)
Thanks for your reply MarcoPLs.
Meanwhile I managed to get root working flawlessly. Don't ask me, how It's too long ago.
hijackerdev said:
where is file ,
pzl upload the su file here,
and ur procedure is not understanding
properly ,
plz give procedure how to do this ,
or upload video,
Click to expand...
Click to collapse
What worked for me was finding older version of kingroot app and rooting with that then using super SU me.apk
Replace kingroot with supersu
Here you will learn how to replace kingroot with supersu
Replace Kingroot With SuperSU