Hello,
My device Orange Rise 31 Special Edition is running on android 6.0. Bootloader Unlocked, Rooted.
I want to install busybox Pro 1.26.2 but i always have this message: It looks like the installation of BusyBox was not successful.I already change the installation path but same error! In the folder system/xbin or /bin i can't find any busybox file. All my app that requires root permission works fine. So please i need your help
Regards
Related
On my newly compiled Android 2.2.2 build, whenever i type "su" in the terminal it says:
link_image[2033]: failed to link su
CANNOT LINK EXECUTABLE
I tried everything possible, I have busybox working, but not su. I have the su binary in the /bin folder and correctly symlinked to the /xbin folder and the permissions correctly applied in the update-script but it still will not execute. Any solutions?
Anyone.. (bumped because of massive amount of threads created each day in this section..)
Having recently bought an ePad V2, it was my first introduction to Android. Therefore having rooted, upgraded firmware, etc I've hit the same issue in trying to get Root Explorer working.
I've found a potential fix at h**p://zenpad.doubtechdotcom/?p=50 but haven't had chance to give it a go yet. You'll have to fill in the gaps of the URL as this is my first post and won't let me give external links.
Ignore my last post as I sorted my problem (originally being unable to mount R/W in RootExplorer). Here's what I did:
1. Uninstalled RootExplorer and Superuser.
2. Unrooted using Universal AndRoot.
3. Rooted NOT installing SuperUser.
4. Installed Busybox Installer from Market (noob fail as I never installed it before!).
5. Installed Busybox.
6. Installed latest version of RootExplorer.
Now I can mount R/W in RootExplorer and therefore I'm guessing my SU problem has gone away.
I am fairly new with using android phones, and I am encountering that error when I am attempting to update Superuser. I'm using a Samsung Admire SCH-R720 Android 2.3.4 and I rooted it with the One Click root. I've downloaded titanium backup, Root Checker, and terminal emulator to make sure I am really rooted. I've tried uninstall/reinstalling superuser, installing the superuser update fixer(which said signatures matched), and clicking on automatic update. Current version of SU Binary is 2.3.1-ef and everything in the update is fine until it gets to "Copying su to /system... fail!". Superuser does request for rights when it asks to gain root access which I click on Allow. I am also not sure if busybox installed correctly or not, but the Root Checker program I installed said busybox was installed.
Code:
Downloading manifest... okay!
Parsing manifest... okay!
Latest Version = 3.0
Checking installed version = 2.3.1-ef
Fixing Database... okay!
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... fail!
I got the same problem with my Galaxy S. Then I opened BusyBox Installer and it said that I have multiple busybox installed. I found busybox in /system/xbin and /sbin but the file size of the one in /sbin seemed abnormal, just 402 bytes. So I reinstalled busybox to /sbin. And rerun the superuser update after that. The fail has gone.
What program did you use to explore your system files?
Astro file manager
I only have busybox in system/xbin. I tried reinstalling busybox and i still get the same error when trying to update Super user. How can I uninstall Busybox? Please give a step by step if possible since I have no clue what the hell I am doing lol.
Edit 2: Er... I tried installing it also in system/bin, and it SEEMS like its working. Seems it's installed in 3 places, on my sd, bin, and xbin. It works now, so I won't touch it lol. Thanks for the help.
Hi everyone,
Same problem for me too.
after installed busybox in system/xbin using busybox installer downloaded from android market, the problem with superuser update was fixed.
I used in samsung galaxy s2..
Thank u
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
goister said:
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
Click to expand...
Click to collapse
Same problem, I am using a polaroid tablet, I installed busybox by doing the following
busybox --install /system/bin
I believe it overwrote some files and cant find the fix
[Q] Re: "Busybox Uninstaller v1.0 - Removes busybox and its +600 symlink files"
I'm trying to use the script provided in the thread Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]. Would've asked this question there, but not allowed, being new to the forum. (Hello. First post.)
New to android in general, actually, but familiar with linux.
Anyhow, I tried using the script both using Flash from recovery method and running the script from terminal, but both fail.
Flash from recovery method fails with an error regarding package verification.
Not running CWM but the stock-thingy. Hardware is Samsung n8010 tablet. Factory-ROM (4.1.2) loaded through ODIN. Rooted.
Run script in terminal fails with a long row of "readling: applet not found".
Script was run in terminal, having su:ed and permitting root-rights. Also remounted system as RW.
Looking at bb-uninstall.log, I see a lot of
/system/bin/COMMAND is not linked to busybox but to ---> file not deleted
Click to expand...
Click to collapse
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