I'm having trouble with installing Busybox. I need it to set up an SSH server on my phone to quickly, wirelessly transfer files from my phone to my computer. I have tried both BusyBox by Stephen (Stericson) and BusyBox Installer by JRummy Apps Inc. I am rooted, so that's not the problem, and neither smart install nor regular install work in BusyBox, whether trying to install to /system/bin or /system/xbin. In BusyBox Installer, neither the regular nor advanced setup work. After trying to install, BusyBox Installer crashes my phone. If I try to do a regular install in BusyBox while it is processing all the components for a smart install, my phone crashes.
Could another app be causing a conflict? Or do I need to flash dsb's kernel that allows writing to the system? Would simply installing to a directory that's not in /system work, or does it need to be in /system?
Thanks for any help.
Install the stock writeable kernel.
Do you mean dsb's kernel where writing to system is enabled, or just the stock kernel? Because I'm already using the stock kernel.
Sent from my HTC6435LVW using xda app-developers app
DSB's kernel. He has a stock one that is writeable and a modified one that is also writeable. You should use the stock writeable.
Alright, I'll install that and see how it works out.
Sent from my HTC6435LVW using xda app-developers app
Related
Hi All,
I am trying to Unlock my Samsung Vibrant phone which is updated to version 2.2.
When i try to install Busybox installer app which was downloaded from market, it is giving the error "Failed to install busybox!"
When i search in google somewhere it mention for Android v2.2 i need to install Busybox installer v1.2 but when i downloaded from maket i am getting v1.19.
how to download Busybox v1.2 (googled, but didnt get correct link) or install busybox v1.9 in Androidv2.2?
or is there any method to unlock phone with out using busybox?
Thanks in advance.
chsundar said:
Hi All,
I am trying to Unlock my Samsung Vibrant phone which is updated to version 2.2.
When i try to install Busybox installer app which was downloaded from market, it is giving the error "Failed to install busybox!"
When i search in google somewhere it mention for Android v2.2 i need to install Busybox installer v1.2 but when i downloaded from maket i am getting v1.19.
how to download Busybox v1.2 (googled, but didnt get correct link) or install busybox v1.9 in Androidv2.2?
or is there any method to unlock phone with out using busybox?
Thanks in advance.
Click to expand...
Click to collapse
Had the same issue when I tried to root my stock 2.2 Vibrant.
Busybox has to be installed somewhere in /system, I believe. The version of 2.2 that Samsung Kies installs, however, has /system packed completely full of bloatware, so there's no room for busybox.
What worked for me was to root with SuperOneClick, then reboot my phone. That got the Superuser app working, so I could use a file manager (I used Super Manager) with root privileges to go into /system and delete some of the bloat to make room for busybox.
An alternative choice is to just flash something else, instead of sticking with a rooted stock 2.2 firmware. As far as I know, all stock 2.1 builds have room in /system for whatever you might need to put there.
let me try to install file manage and clean some unwanted files and try again...
chsundar said:
let me try to install file manage and clean some unwanted files and try again...
Click to expand...
Click to collapse
I used Super Manager for the job, but I think about any file manager that can use root privileges would work.
Be sure to only delete bloat. Stuff like Sims 3, Amazon mp3, Slacker Radio, that sort of thing. Those are really just apps, and have no business being in /system. They're only put there because T-Mobile didn't want us to be able to delete the bloat they were paid to pre-load onto our phones. /system also holds all sorts of stuff your phone needs to work properly, so you can end up forced to Odin to stock if you delete stuff that's not bloat.
http://forum.xda-developers.com/showthread.php?t=925400 is the thread that I followed to get root working on my previously stock 2.2 Froyo Vibrant. It's /system/app that you need to clean up bloat from.
Thanks i could delete unwanted apps and free up some space in system folder. I could unlock my phone and use AT&T sim.
So I rooted my tblot no problem but when i rooted my manager's i keep having a problem with the superuser process force closing. I've tried rerooting and reinstalling superuser, updating su... phone is rooted and s-off. I would try and figure it out myself but i only have access to it at work when i bring my laptop in and mess with it on my lunch. So basically i was just wondering if anyone had the same problem and how they fixed it.
Sent from my HTC Mecha
sunflash72 said:
So I rooted my tblot no problem but when i rooted my manager's i keep having a problem with the superuser process force closing. I've tried rerooting and reinstalling superuser, updating su... phone is rooted and s-off. I would try and figure it out myself but i only have access to it at work when i bring my laptop in and mess with it on my lunch. So basically i was just wondering if anyone had the same problem and how they fixed it.
Sent from my HTC Mecha
Click to expand...
Click to collapse
Did you try fixing permissions? It's in Rom Manager.
Rom manager can't run because the superuser process force closes whenever you try and run anything that requires root permissions
Another weird thing is that he is able to uninstall superuser from the manage applications menu
Sent from my HTC Mecha
There are some borked versions of superuser out there. Make sure you're installing a very well-trusted ROM with a known-good superuser app.
sunflash72 said:
Rom manager can't run because the superuser process force closes whenever you try and run anything that requires root permissions
Another weird thing is that he is able to uninstall superuser from the manage applications menu
Sent from my HTC Mecha
Click to expand...
Click to collapse
You can also fix permissions by booting into recovery.
Is there a release of clockwork mod outside of rom manager for the thunderbolt? i tried finding a zip to flash in fastboot but to no avail
Sent from my HTC Mecha
I had a similar issue a while back. I had to redo the entire root process from scratch using the adb method, then I installed a rom that had the superuser fix from rmk40; most TB roms use the fix. Good luck!
Sent from my ADR6400L using XDA Premium App
Your issue may be related to how busybox is installed. A standard "busybox --install [path]" will create a link for busybox's su. If that's earlier on the path than the correct su for Android, it will cause problems. The easy fix is, after installing busybox, remove the su it created.
Everyone seems to do different things with busybox. It may be placed in different places, and may not be "installed" with the links created.
I put it in /system/sbin, and create the links there. If you followed the common instructions for root, that su should be in /system/xbin. The standard PATH is =/sbin:/system/sbin:/system/bin:/system/xbin
From adb shell, do a "busybox which su" It should say "/system/xbin/su"
I wish someone who was setup for cross-compiling would do a busybox with no su, and with "ls --color=never" the default.
Makes sense... unfortunately i don't have too much access to his phone to mess with it. Here's hoping the tbolt gets unrevoked support soon...
Sent from my HTC Mecha
Hi, i need to install busybox cause i want to give that v6 script a go. But it wont let me do it using the market apps. it says i dont have root access when i hit the install button.
can someone give me some basic steps to installing it please ?
im using miks CM7 rom.
also after failing to install it my wifi doesnt work. so ive had to reflash the rom twice now, im pretty over it !
just download busybox installer from the market. after installing u can download the busybox version of your choice through the installer app.
press the thanks button if i helped u
Every rooted ROM had Busybox built-in, so does CM7. If you simply need another version try reflashing the ROM and make sure you are using the installer that works, there's one that doesn't work on CM7 (Search the market for pname:"com.jrummy.busybox.installer").
i tried both installers on the market, they both failed with a rooting error. Im not going to try again because after it fails, it ****s my wifi up and i have to reflash the rom.
you say busybox is installed already tho? my phone doesnt think it is. i tried to run a script manager and it said i need busybox..
Unless you have a custom non-rooted CyanogenMod build, you should have Busybox 1.16.2 pre-installed. Run the busybox command from adb / terminal emulator and make sure you have allowed Script Manager Superuser permissions.
Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?
Check the Neak thread first .
And or reflash the kernel .
jje
Why dont you root with a CF-Root kernel to get root and superuser and then flash the Neak kernel to see if the root access stays.
I was a bit worried because there was no exact cf-root kernel for XXKL1. But I used the XWKL1 one and flashed back to the other kernel and yes it worked.
Thanks!
(Although I don't quite understand why...)
CF-Root kernels are basically stock root kernels by Chainfire so being stock rooted they are,I imagine,more likely to get and hold root access.They are the only kernels is use as Im not into overclocking or anything like that.Anyway once root was acheived flashing the other over top was no problem.XXKL1 is the same as XWKL1 as long as the Firmware is the same.The important part is the last 3 digits.
Hossie2k said:
Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?
Click to expand...
Click to collapse
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk
simone201 said:
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk
Click to expand...
Click to collapse
The same happens to me. Even installing the Superuser from Play Store it says I don't have root access. I'm on a n7100 with 4.1.2 stock (rom) and latest neak kernel.
Thanks.
Siyah anyone?
Sent from the little guy
what actually bussybox do to our devices.??
i havent installed this app still all the rootapps areworking great, so what really it does to our device
Sent from my Dell Streak using xda app-developers app
In a layman's lanaguage- busybox is a set of command line tools which is used by applications with root privilege to alter data on restricted partitions of system.
It's a must have for any rooted user who want to alter their device to their liking not usually allowed in stock ROMs.
Sent from my Dell Streak using Tapatalk 2
cant install it
o have dsc rom with simplesu
while installing it says device not rooted
qhat to do.?
Sent from my Dell Streak using xda app-developers app
Use SuperSU instead of SimpleSU. As I explain in the Traveller DSC thread, SimpleSU's su binary isn't seen as a valid binary by certain apps. Stericson's Busybox installer is one of those apps.
You could also switch to Traveller DSC, as it uses SuperSU and includes a comprehensive busybox binary.
cant i just use some other app for it without changing the rom
Sent from my Dell Streak using xda app-developers app
You can install SuperSU from the Play Store (not recommended due to bugs in SuperSU 1.69), but you'll need to add SuperSU's package to SimpleSU's whitelist before SimpleSU will allow SuperSU to do its thing. In the Traveller DSC thread I do make a flashable zip of SuperSU 1.65 available to plug into /system, which is the best way to go. This will replace SimpleSU's binary and allow the Busybox installer to function. If you go this route, make sure to read the post regarding SuperSU.
Regardless of which way you install SuperSU, all apps requiring root will require that permissions be granted again, since you are changing both the su binary and the Superuser app.