hey guys been having a recent problem.. in terminal emulator after inputing su, reboot i get back a reboot: no such tool??
is there something up with my busybox or applets?
MotoTurbo said:
hey guys been having a recent problem.. in terminal emulator after inputing su, reboot i get back a reboot: no such tool??
is there something up with my busybox or applets?
Click to expand...
Click to collapse
I don't know what rom you are on and it usually depends. Check the super su app to make sure that you have the binaries installed (it only tells you if you don't). Also check with Root checker. I find the issue you have pretty odd.
I was on nusensesix and SuperSU did update the binaries when it updated from playstore but I guess something went wrong with that department or when I changed to stephs busy box. Thanks for the reply tho. Thread can be closed
Sent from my One M8 using XDA Free mobile app
Related
For some reason even after using each subsequent one click root method, including the latest andromeda flasher, I cannot install Busybox. It says that the phone is either not nand unlocked or isn't rooted. I also cannot use remount in adb as it says it is not found. Any ideas as to why?
sporkisfaster said:
For some reason even after using each subsequent one click root method, including the latest andromeda flasher, I cannot install Busybox. It says that the phone is either not nand unlocked or isn't rooted. I also cannot use remount in adb as it says it is not found. Any ideas as to why?
Click to expand...
Click to collapse
The only way I have found around this myself is to go back to stock kernel. Then install the Joey 2.2.4 root exploit install not the noobl kernel and then install the latest busy box .... and superuser
Try installing titanium backup, open it, hit problems and install busy box from there.
Aridon said:
Try installing titanium backup, open it, hit problems and install busy box from there.
Click to expand...
Click to collapse
This seemed to install busybox inside of TiB so thats good. Also I already have superuser. Everything about the root seems to work ok however trying to remount in adb still is a no go.
Copy and paste your console here so we can take a look at it
Aridon said:
Copy and paste your console here so we can take a look at it
Click to expand...
Click to collapse
How do I console? Sorry a bit of a nub when it comes to stuff like that.
That is to say, what exactly do you want to see? My cmd prompt or something on my phone?
I downloaded terminal from market and ran su and said permission denied? any ideas?
I ran odin and rooted altered beast rom as well
Sent from my SCH-I510 using XDA Premium App
Do you have the Superuser app installed? The su binary requires this to work properly.
imnuts said:
Do you have the Superuser app installed? The su binary requires this to work properly.
Click to expand...
Click to collapse
when i read this i realized it wasnt but even after i installed it it still gave me the same problem on terminal, idk if it the actual rom that i installed or what?
first of all, did you root your phone? by any method? if you did, download titanium backup from the market, and when you open it, it will tell you that you dont have root access, press the problems? button, and it will prompt you with a box that has the option to get busybox, just press that button and most of the times this will fix this root permission issue
I updated SU last night and used the app to push the file and now I can't get root access.
Anyone gotta fix?
Did you set the permissions correctly on the binary?
You need to give more detail otherwise.
Sent from my HTC Desire using Tapatalk
How about you tutor me on how to set the permissions correctly ... if you don't mind.
I used the app to try and update. It would not update successfully through the app so it put a .zip file in /sdcard so I moved to external, to flash and I get a bad file error from CWR
Which app are you trying to update from and which zip are you trying to flash with cwm?
Sent from my HTC Desire using Tapatalk
SuperUser ChainsDD
When trying to update binary I get a error msg that state unable to update. There is a .zip file placed on your sdcard flash thru recovery to update. That is not word for word but close enuff
Brenardo said:
SuperUser ChainsDD
When trying to update binary I get a error msg that state unable to update. There is a .zip file placed on your sdcard flash thru recovery to update. That is not word for word but close enuff
Click to expand...
Click to collapse
Well, assuming you didn't replace the boot image, you should be able to remount with "adb remount", I suggest you follow my rooting guide from that line, which will also help you with permissions etc.
Sent from my HTC Desire using Tapatalk
just to be clear I am already rooted and have no problems with root until I try to update SU.
Uninstall update and restore nandroid back to root with no problems ..
Brenardo said:
just to be clear I am already rooted and have no problems with root until I try to update SU.
Uninstall update and restore nandroid back to root with no problems ..
Click to expand...
Click to collapse
Well, either don't update su, or follow my guide as suggested but replace my superuser files with your updated ones.
Sent from my HTC Desire using Tapatalk
I just wonder why the update will not work
i have this exact same problem. it wasnt working so i updated through the market and it worked for one app and then it wouldnt at all. i tried updating the binary like Brenardo but i get the same error and in CWM it says its a bad file
Same here really annoying.
Sent from my MB860 using XDA Premium App
The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:
$
type "su" and hit the enter key and it should give you back:
#
If it doesn't, and you get the following:
reloc_library[1315]: 2756 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.
See post #340 in the following thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1117004
This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
So the zip file that is put on the SD card is the file that we need to push?
Almighty1 said:
The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:
$
type "su" and hit the enter key and it should give you back:
#
If it doesn't, and you get the following:
reloc_library[1315]: 2756 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.
See post #340 in the following thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1117004
This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
Click to expand...
Click to collapse
But it has been working up until yesterday when it asked to update
Sent from my MB860 using XDA Premium App
Seadub2 said:
But it has been working up until yesterday when it asked to update
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Consider that some updates are incompatible or just bad. I am not allowing the update. I have disabled auto update. My current superuser is just fine, thank you.
Brenardo said:
So the zip file that is put on the SD card is the file that we need to push?
Click to expand...
Click to collapse
No, unzip the zipfile and you will get a file called su which is what you need to push. The zipfile is only for convenience and also so you will know if the file is corrupted or not when you download.
Seadub2 said:
But it has been working up until yesterday when it asked to update
Click to expand...
Click to collapse
The only reason it worked is because Superuser app (the graphical program in the GUI) and su binary which resides in /system/bin are two different things altogether. Previously, the newest su binary was version 2.3.1-ef so Superuser app will not prompt you to update the su binary as it's the same version as what you already have on your device. When the new Superuser came out, after you open Superuser the first time after the new version it's installed, it prompted and told you that a new version of the su binary is available and if you declined it, you wouldn't have the problem. If you accepted it, it basically replaced the existing su binary and replaced it with the new one which is version 2.3.1-efg. No different than if you had Honeycomb 3.1 installed, it would not update unless the number is greater than 3.1.
The latest superuser 2.3.6.3 update can update the su binary to 2.3.2-efgh now which does update automatically and work correctly on the Xoom.
Almighty1 said:
The only reason it worked is because Superuser app (the graphical program in the GUI) and su binary which resides in /system/bin are two different things altogether. Previously, the newest su binary was version 2.3.1-ef so Superuser app will not prompt you to update the su binary as it's the same version as what you already have on your device. When the new Superuser came out, after you open Superuser the first time after the new version it's installed, it prompted and told you that a new version of the su binary is available and if you declined it, you wouldn't have the problem. If you accepted it, it basically replaced the existing su binary and replaced it with the new one which is version 2.3.1-efg. No different than if you had Honeycomb 3.1 installed, it would not update unless the number is greater than 3.1.
Click to expand...
Click to collapse
Thanks for info
tutech said:
The latest superuser 2.3.6.3 update can update the su binary to 2.3.2-efgh now which does update automatically and work correctly on the Xoom.
Click to expand...
Click to collapse
Thanks for the pointer. When 2.3.6.3 came out and I installed it, it did prompt with the su binary update but I cancelled it while I updated the su binary on my Motorola Droid. So when I saw your post, I went into the SuperUser app and went to settings and clicked on check for Su binary update, it said checking failed so I basically copied the updated su from my Motorola Droid and it works.
If I try to use the terminal for anything it returns "<command>: permission denied". This occurs with any terninal emulator I use. Will I have to make a call to busybox for everything?
Sent from my Cyanogen R800x using the XDA app.
seems that your root method doesnt work properly.Just try another one
Did you not see that I'm using cm? the ROM comes rooted.
Sent from my Cyanogen R800x using the XDA app.
hm two ideas.
- root permission is not being granted correctly
- busybox not installed correctly
Should I reinstall bb then?
Sent from my Cyanogen R800x using the XDA app.
brainard52 said:
Should I reinstall bb then?
Sent from my Cyanogen R800x using the XDA app.
Click to expand...
Click to collapse
If you type busybox in your terminal do you get an error?
Reinstall busybox and root you device again!
DroidVPN said:
If you type busybox in your terminal do you get an error?
Click to expand...
Click to collapse
No error.
-bfar97- said:
Reinstall busybox and root you device again!
Click to expand...
Click to collapse
This was addressed earlier. My rom COMES rooted, so I don't need to root it.
Also, When I try installing BB (using one of the BB installers) it says that the same version was already installed. Does this mean that I need to UNinstall it first? Wait for the next version of BB? :/
Try rebooting into clockworkmod recovery and going to advanced>fix permissions. Then reboot and go back to terminal and type su. If you still get permission denied, uninstall busybox the push it back to the phone via adb. Let me know how it goes.
Sent from my HTC Vision using xda premium
Why do I have to use adb? Wouldn't I just be able to use the installer?
Sent from my Cyanogen R800x using the XDA app.
Do you get permission denied when type su in the terminal? Then superuser from the market since the rom is already rooted
Sent from my GT-I9000 using Tapatalk
You could do it from the market/installer . Sorry I use adb for everything.
Sent from my HTC Vision ILWT CM7
have u devices is rooted?
if not its impossible to doing command
should you start command with "SU" (without quote)
mr.snax said:
have u devices is rooted?
if not its impossible to doing command
should you start command with "SU" (without quote)
Click to expand...
Click to collapse
Thanks. I didn't realize I was supposed to use SU :x
Please someone help me .
I've got an update from chainfire, then after reboot my phone lost the su binary. When open the chainfire apps, it said the su binary is not installed and the super su cannot install it. What should I do?
tyha said:
Please someone help me .
I've got an update from chainfire, then after reboot my phone lost the su binary. When open the chainfire apps, it said the su binary is not installed and the super su cannot install it. What should I do?
Click to expand...
Click to collapse
I wrote on this threat that Chainfire has problems with some roms... You could try the solution i provide there (but i do not know if it will fix your problems). If i where you, i would first try the solution from the above topic, then uninstall Chainfire and then install/reinstall busybox (with this app), then check if super su is fine. Else, make a titanium back app and flash a rom...
First of all make a backup...
What is the function of Busybox? It okay to use it?
tyha said:
What is the function of Busybox? It okay to use it?
Click to expand...
Click to collapse
yea...demanding the same answer...
tyha said:
What is the function of Busybox? It okay to use it?
Click to expand...
Click to collapse
The "function" of Busybox? If that means: "What is Busybox?", here we are...
Busybox is something that you install to give you some additional LINUX / UNIX based commands. You need Busybox installed in order to run apps that demand these commands which are not available to you and you made need them for some root level tasks.
If you need it, install it with this app.