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
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 an OMAP3 board that has no internet connectivity. It has Froyo on it, and has been rooted. However, there's no busybox, which I'd like to install for a few of the commands.
Where do I get busybox from, and how do I go about installing it?
Thanks!
OK, I managed to install BusyBox 1.19.4 using stericson's Busybox Installer Free app. It seems to be the latest version of busybox according to the busybox website, however, it seems to package some older versions of the apps compared to my Incredible S with CM7.1's Busybox 1.19.3. For example, the 1.19.4 has mke2fs version 1.40.8 (13-Mar-2008) while CM's 1.19.3 has mke2fs version 1.41.12 (17-May-2010).
It seems like the older mke2fs doesn't support some filesystem options that I wish to run.
Is there a way to install newer versions? Can I extract busybox from my Incredible S and install it on the TI board? If so, how?
Thanks.
Anyone ?
I am trying to root my samsung galaxy tab 2. I tried Weltwon's guide here:
http://forum.xda-developers.com/show....php?t=1657056
But it didn't work. I redownloaded each file and attempted the process 4 times. After that, I figured maybe I was doing something wrong. I don't understand how it isn't working for me yet it works for everyone else it seems.
Using odin "passes" (goes green as if it worked) And i'm able to boot into the recovery. I chose the file on the sd card and it runs through a quick install. It then says it has completed and enjoy. I reboot my tablet and try accessing 3 different root apps. (root checker, SuperSU, and GameCih- which requires root) and I get errors telling me im not rooted.
Here is what my install looks like:
-- Installing: /sdcard/cwm-root-gtab2.zip
Finding update package...
Opening update package...
Installing update...
************************
Galaxian-Soup is Proud to present
#######################
CWM root for your galaxy tab 2 7.0
#######################
Root brough to you by Brett Richter - nycbjr - itweakit.com
######################
*************************
Mounting SYSTEM...
Deleting System:bin/su...
Deleting SYSTEM:xbin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755
Creating SYSTEM:xbin/su symbolic link...
Installing busybox
Unmounting SYSTEM...
Install complete. Enjoy!
What model tab do you have?
P p.
Delivered to you via microwave technology .
Did you download and install super user from the market? It is not included with rooting procedure (although Super su is) .
!0.1
I have the 10.1 model. there were 2 other zip files i tried. They said 10.1. The one i tried last i found on a forum for 7.1 that said was fully operable on 10.1
SU
Yes. I didn't read to do that anywhere, but I tried it on my own. SuperSU says that it cannot find SU bin. SuperUser is blank when I open it. I try to update and it says canot find su binary. :S
I am so confused. Lol. It doesn't make sense! The instructions were not difficult to follow, and others are finding success.
For what it's worth, Model # = GT-P5113
Android version = 4.0.3
Kernal version = 3.0.8-396106-user [email protected] #1
Build number: IML74K.P5113UEALD7
Why are you trying to install the galaxian soup zip, I don't think this is compatible with the 10.1, your description says Tab 2 7 inch, this may be your problem. Just follow the op instructions and work with the zip file provided by welton.
Pp.
Delivered to you via microwave technology .
re
I have tried both of the ones on weltons guide. Plus a few others. All have same results. No root.
download the app superuser from play store, then run supersu, it will request root access, give it to it, then it will update. Might need to download busybox from playstore before hand if u dont see it in your app list
Check out this thread for recovery /root on the 10.1" tab: http://forum.xda-developers.com/showthread.php?t=1686514
Do not flash the stock ROM though, it's for the 3g model.
Cheers,
C.
Ok let's see. Superuser never asks for permission. I open it and the log is empty. The whole app stays empty. I check the installed version and it says legacy. It asks if i want to update and i say yes, then it fails. Super.su opens up saying it cannot find any .su binaries and that it's a problem. Busybox installer is the only app I've ran that gave me any belief that the root worked. It tells me I'm rooted and my current Busybox version is 1.19.3 when i try to install any new versions it fails. I also downs0loaded an app called busybox. When i click install there, it says it may be unable to find the binaries and it closes.
Sent from my GT-P5113 using XDA
Oh, here's something I'd like to add. I read a different guide an in its description the rooting process took a couple minutes after selecting the zip. Mine only lasts about 3 seconds. Could my probem have been the odin process?
Sent from my GT-P5113 using XDA
re
I'm probably stacking too many responses, but here's word for word issues:
I JUST WHIPED ALL DATA on my tablet, deleted all the files on my PC, and started over. I redownloaded, reflashed (ODIN), used only the versions in the guide by weltwon - and ran the root again.
Superuser, Busybox, SuperSU - NONE of these were installed on their own. NOTHIGN was installed by the root process.
Superuser:
Opens to a grey background and a white column. On the left (in grey) "No apps in list". On the right (in white) No log information Showing 0 entries. The start icon takes me to the app store. The button that looks like a piece of paper with a list and an (X) does nothing.The wrench icon takes me to the settins.
---In settings AutoResponse is set to Prompt. no settings have been touched, all are default. Under general there is a lane saying "Superuser v3.0.7 (41)" I press it but nothing happens. next i press "Su binary vnull (tap to check for updates)".
------In su binary vnull:
{
Downloading Manifest... Okay![GREEN]
Parsing manifest... Okay![GREEN]
Latest version = 3.0.3.2[GREEN]
Checking installed version = legacy[RED].
}
At the top, "New version of su binary found. Update now?" So i click update.
{
Fixing databse... Okay![GREEN]
Checking for busybox... Okay![GREEN]
Checking current install path... fail![RED]
Failed to find currently installed su binary. Update cannot continue.
}
So I try to run busybox free.
Under the install busybox tab the first thing i notice is; "Location of Busybox could not be determined.
I try to install BusyBox 1.20.1 to /system/bin and I get a pop up that says the following; "I am unable to verify whether or not certain utilities needed for this application to run are present and functional on your device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured."
My only option is to press the X on this message box, which closes the application.
I reopen and try other versions, same message. I reopen and try the other two installation choices (/system/xbin and Custom Path) I instantly cancel the Custom Path because it says it's an advanced option and I do not want to mess up anything.
I install SuperSU and open it. I'm brought immediately to a pop up saying, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" MY only choice is to press OK which closes the app.
Next i try "Jrummy16" 's BusyBox Installer. I install it and open it. Under the installer tab:
Select busybox version [Set to: BusyBox v1.20.1]
Select install location [Set to: /system/xbin/]
Your devise is rooted
Busybox Location: /system/xbin
Busybox version: v1.19.3
System storage 200 MB
Phone Model: GT-P5113
ROM version: IML74K.P5113UEALD7
I press install and get, "Installing BusyBox v1.20.1 failed. Please try installing a different version." I press the X and am taken back to the original screen. I try the next 5 versions, plus sqlite3, zip, zipalign, and a few versions of BusyBox and I get the same failure message. I change the location to ~/bin instead of ~/xbin and try again. SAME error.
It is VERY frustrating because I have the correct model, and am following instructions that (to my knowledge) not a single person has had trouble with. And now that I whiped the data, I'm completely out of ideas. It is completely beyond me how I end up stuck in this situation where nothing seems to be doing what it should.
Hello everyone.
I have been wanting to get to grips with linux for a while now and decided linux decided to try completelinuxinstaller as i was having some problems with linux deploy.
i set up everything as the app asked. Downloaded .img files, extract, rename file and launch.. but in the android terminal i get a error which said:
chroot: can't execute '/root/init.sh': Permission denied
After days of searching and trying minor fixes i got no where until i found a list of instructions on how to fix this error.
(This error is becoming common on Samsung devices running android version 4.4.2, and can be expected to happen with some other devices, or newer versions of android. Although I haven't yet found the exact cause of the error, an effective workaround has been found:
The error seems to be coming from something in the busybox executable installed by the Complete Linux Installer app; many have reported that using other versions of busybox removed this problem, and the following version (free download on Google Play) has been confirmed to work: BusyBox
After using that app to install an updated busybox binary, simply copy the new binary over the existing busybox binary at /data/data/com.zpwebsites.linuxonandroid/files/busybox
Finally, in a rooted terminal window, type chmod 0755 /data/data/com.zpwebsites.linuxonandroid/files/busybox (see the more detailed instructions in the How do I install the most up-to-date version of bootscript.sh on my device? section of this FAQ)
Now you should be able to start linux using your Complete Linux Installer app on your device.)
But the problem is no matter what explorer i use i am not able to find the busybox config file. Where they said it would be doesnt exist. Even if i go to android/data its not there. Just the .com for all other apps. do you know where the busybox might be ?. On the busybox installer it says it is in /system/xbin but again i cant find it on my device.
And if i may chew your ear off for one more moment. How can i change the .config file ?
Thank you for your time