"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.
busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...
Related
Curse these programs that won't use newer su/busybox combinations.
After installing one of the latest blur ROMs, I wasn't able to get webtop2sd to run (a very common problem), nor Cisco's Anyconnect VPN client. webtop2sd did the usual FC, while Anyconnect would complain that it couldn't start a "critical component". Going back to the one I was running before the upgrade didn't help either.
These problems are not unique to the beta, nor this ROM, but here's what I had to do:
Follow the steps in this thread starting in step 6:
http://forum.xda-developers.com/showpost.php?p=21155110&postcount=852.
Total props to dicksteele for the original post. Thought it might be better to put out here since this seems to be a recurring issue on most ROMs now.
Specifically,
6. Install Busybox installer from Market. Ran app installed busybox into /system/bin.
7. Open Root explorer Go to /system/etc mount r/w create webtop2sd directory
8. Go to /system/bin copy busybox over to /system/etc/webtop2sd
9. Still in root explorer, go to /system/bin and /system/xbin and delete su
10. Can't use quick reboot to reboot into recovery because su has been deleted. Wherever your adb is located, run adb reboot recovery.
11. Install the superuser app from the zip I have attached. Reboot.
12. Open some other app besides webtop2sd that needs root. Verify root is working.
13. Install webtop2sd.
14. Open webtop2sd, hopefully no FC's. Do the webtop2sd partitioning and copy webtop over to new partition on sdcard.
Click to expand...
Click to collapse
Yes, webtop2sd was very picky to the point of needing busybox from the installer, not the identical one installed by the ROM. Once I got webtop2sd running, I tried Anyconnect again and it started right up.
I can understand webtop2SD not working since it hasn't been updated for a long time, but a company like Cisco should be sure their tool, available on the Market, works with the latest superuser/busybox combinations.
I would go so far as to say that if you are having trouble with any programs requiring root access, try the steps above used to get webtop2SD working. Hope this helps others stuck on similar issues with these newer ROMs.
Hey guys, some of you seem to be having troubles installing busybox on the new marshmallow. Busybox claims there's only about 16 MB left on the system, but you need more before it will successfully install. Well, if you go into twrp and go to wipe, select system and hit repair, you have to option to resize. It'll set your system at 32 MB. This should be enough to install busybox. After you install it you'll be back down to 0 mb but you can do the process over again and gain another 32 MB.
A better solution would be to just use TB to remove a bunch of Google Apps, then just reinstall from the play store.
I cleared about 500mb doing that, without fussing with formatting.
or just flash this
http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip
in twrp
funny, i installed stericsons busybox app, then it installed busybox without any issue.
Busybox on Rails worked for me.
The M BusyBox wouldn't install for me so I tried Busybox on Rails. It says it can't write to /system/xbin. Is that also due to the 16MB size of /system?
LeoRex said:
A better solution would be to just use TB to remove a bunch of Google Apps, then just reinstall from the play store.
I cleared about 500mb doing that, without fussing with formatting.
Click to expand...
Click to collapse
You don't have to format, you just resize the partition. I moved some apps but it still said I had 16 MB in system.
abogrhen said:
or just flash this
http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip
in twrp
Click to expand...
Click to collapse
I installed this version but don't see the Busybox app. However, I see files under /system/xbin that look like it's installed. Does that should normal?
JimSmith94 said:
The M BusyBox wouldn't install for me so I tried Busybox on Rails. It says it can't write to /system/xbin. Is that also due to the 16MB size of /system?
Click to expand...
Click to collapse
Busybox on rails gave me the same error when I ran it using the "Normal" option. The "Recovery" option booted to TWRP to install but I noticed two red text errors. Something about Busybox not installing, but my device reboots before I can get the exact errors. Oddly, Busybox IS installed after the reboot, the app is there and I confirmed through terminal.
Worked For Me
I'm on a Nexus 6 with fresh install of latest Marshmallow build. I used NRT this morning to do a fresh install, root and install TWRP. Busybox did not install properly and using a Terminal Emulator and entering the command "busybox" would show "not found". After using donjuro's fix at the top of this thread and then flashing the Busybox-Android_M supplied by user abogrhen (also in this thread) I was able to properly install Busybox. Using the Terminal Emulator and typing "busybox" now shows me a list of commands. Thanks for your help.
donjuro said:
Hey guys, some of you seem to be having troubles installing busybox on the new marshmallow. Busybox claims there's only about 16 MB left on the system, but you need more before it will successfully install. Well, if you go into twrp and go to wipe, select system and hit repair, you have to option to resize. It'll set your system at 32 MB. This should be enough to install busybox. After you install it you'll be back down to 0 mb but you can do the process over again and gain another 32 MB.
Click to expand...
Click to collapse
Just copy the busybox binary to the data partition, something like /data/bin/
Then in your terminal program, add /data/bin/ to the PATH variable (start command).
There is no need to mess with the system partition for this.
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
I'll give it a try had nothing but issues trying to use layers, currently got busybox on rails installed but as you've mentioned can't get it working, I'll try as you've suggested thanks
Sent from my Nexus 6P using Tapatalk
Spot on
hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
Thank you so much for discovering this, I was going crazy why I couldn't create the overlay folder under vendor, this is the solution, to everyone who sees this, don't listen to whoever says busybox on rails is the way to go...
If you have supersu 2.65 and install busybox to /su/xbin then it will also work.
I have superuser 2.65 and following your instructions finally have layers working, thanks dude
Sent from my Nexus 6P using Tapatalk
Perfect, thank you
Sent from my Nexus 6P using Tapatalk
hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
For me with su 2.65 and busybox on rails, things are working. However, not as expected. Sometime even I change some overlay it won't apply. Sometime the dialer and other fonts won't be visible at all. May be I should try ur method. Thanks.
Sent from my Nexus 6P using Tapatalk
This method will defeat the purpose of systemless root though, right? So Android Pay and Good for Enterprise will cease to work because /system had been edited?
Hey people!
I just got a nexus 7 2012 and i am wanting to mount it in my car. So i wanted to do a few things before that.
I updated to official 5.1.1 via OTA. Everything is STOCK
First step was rooting which SEEMED to work (DID it via WUGS). It installed SU and busybox. Next step was to create my own bootanimation
This is where the issues have started. I can not change permissions or move any files to the system directory even with W/R option turned on
I can delete the files but can not copy files to the directories. I can no change permissions in ANY directory.
I have tried in root explorer mounting r/w ES file explorer R/W ... i tried to install a new busy box and it installs then immediately says "you installed but it seems there is an older version on the system" i can not uninstall busybox. I tried mounting in terminal and it says all partitions are EXT 4. I have tried rerooting. Root check says everything is fine. SU seems to be working fine (it elevates permissions for all the root apps).
But for the life of me it will not copy anything into / or /system. :crying:
Should i just forget it and install another rom, WIPE everything and start again? If ROM which one is the best at the moment (nexus 2012)
After 2-3 hours of messing about... I just TWRP and flashed a different SU and it starting working.
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.