Hey Community!
At first I'm sorry for my bad English and if I'm wrong here. I'm German
Hopefully you understand what you read here.
My system:
Phone: HTC One (M8) (root)
OS: Android 5.0.1
BusyBox Installer (Pro): latest version (28/1.23.2)
ROM: Stock-ROM
Several days ago I rooted my phone. To use some root-apps I've downloaded BusyBox -Installer. But as soon as I try to install it, I get an error message: "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue."
After I tried it a second time my phone crashed and rebooted.
So I chose another path. But it still doesn't work.
So I searched the web for possible solutions.
One of them was that I should install a fix via recovery-mode.
Another was that I should mount the installation path "/system".
But nothing helps.
Then I got the tip that I should install busybox on the recovery-mode. But I cannot find a .zip file.
I do not know what to do now.
I hope someone can help me.
PS: My Samsung Galaxy TabPro 12.2 (Android 4.4.2) is also rooted but there I could busybox install without issues.
Flash the full SELinux version from the link.
http://forum.xda-developers.com/showthread.php?t=1929852
Sent from my HTC One_M8 using Tapatalk
You might also try another Busybox installer from the Play Store.
The one called "Busybox Installer" (which it sounds like you are using) is by JRummy. There is another I've used by Stericson.
When I've had issues on my old HTC device with one BB installer, I tried the other, and it worked fine.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
creamypie said:
Another was that I should mount the installation path "/system".
Click to expand...
Click to collapse
If Busybox needs to install to the system partition, you need the kernel mod to make system writable.
This device has system write protection, even with root.
i had been suffering from same issue on stock rooted rom,for me no solution was there on here xda , finally decided for custom rom and almost all custom roms having busybox already.
so try some custom rom.
Related
I downloaded busybox from the market place and everytime it dosent install. Sometimes it reboots the phone iv tried all the versions of busybox and stilll no install. I am running android 2.2 on a htc desire any help would be greatly appreciated ! ps my phone is rooted
spikey1000 said:
I downloaded busybox from the market place and everytime it dosent install. Sometimes it reboots the phone iv tried all the versions of busybox and stilll no install. I am running android 2.2 on a htc desire any help would be greatly appreciated ! ps my phone is rooted
Click to expand...
Click to collapse
Hi spikey1000!
Try "Busybox Installer" from Market instead. Also make sure that you have root access. (sry I just saw that you're rooted)
The app I suggested works simple. You just select the busybox version you need then press Install. Is should work
Thanks for your help but ..
I have tried that aswell. Could it be that i don't have enough space left in the install directory?
spikey1000 said:
I have tried that aswell. Could it be that i don't have enough space left in the install directory?
Click to expand...
Click to collapse
Well you can check that in Settings/ SD & phone Storage.
If you have more than 20 MB (just guessing), then I think not the lack of space is the problem.
Is there any error message or something or it just simply won't install?
i have 28.11mb free on my phone memory and if i use the busyox installer by (stericson) i takes like 3 hours then it closes. If i use the one by Jrummy16 the phone restarts and does not install. What do you suggest ?
spikey1000 said:
i have 28.11mb free on my phone memory and if i use the busyox installer by (stericson) i takes like 3 hours then it closes. If i use the one by Jrummy16 the phone restarts and does not install. What do you suggest ?
Click to expand...
Click to collapse
Are you on a stock rooted Froyo? Without A2SD?
Have you tried uninstalling a few big apps just to see if the space is the probem?
Sorry I don't have any more guess
If I were you I would try it on a different ROM. Haven't you considered moving to Gingerbread Sense?
ps: Try deleting dalvik cache in recovery. It cannot do harm.
i tried deleting the dalvik cache but still no install. I am not very technical so i don't know how i would install gingerbread sense could you tell me how ? please all of my apps are on my sd but i my storage seems to have gone down to 20mb!!
Busybox is not an app, it's a linux toolset. The app itself just installs the linux toolset to the system-partition(/system/bin, /system/sbin or /system/xbin), however on desire apps won't have write access to /system if you are s-on, so the apps will be unable to install busybox.(trying to do so results in a reboot which one of the apps nicely does )
To install busybox you will need to either do it from recovery(can be flashed using a zip file) or by making your phone s-off(i'd recommend this, as it'll make everything so much easier).
To s-off go here: http://alpharev.nl/ or here: http://revolutionary.io/
thanxx
sempi601 said:
Hi spikey1000!
Try "Busybox Installer" from Market instead. Also make sure that you have root access. (sry I just saw that you're rooted)
The app I suggested works simple. You just select the busybox version you need then press Install. Is should work
Click to expand...
Click to collapse
thanks
Safe?
edit: posted in wrong thread please ignore
Hi all, first of all...sorry if I did not provide enough information...I am first time doing this whole flashing thing on my own...
My phone's CID number: HTC_044
Version main: EMPTY <<< is this normal?
Version bootloader: 3.19.0.0000
Using stock ROM i suppose...didn't flash any other third party's ROM before
My phone was rooted for sometime and lately I want to upgrade my phone to Lollipop...I thought I need to unroot first and therefore I found solution online...everything went fine and I was able to upgrade to Lollipop using the official way (update through phone).
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Can anyone help me on this? I also not quite sure what went wrong...hope you guys can enlighten me...will try to provide as much information as possible.
jkidz91 said:
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Click to expand...
Click to collapse
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
jkidz91 said:
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Click to expand...
Click to collapse
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
redpoint73 said:
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
Click to expand...
Click to collapse
Noted bro! You r really helpful!
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app
angvil said:
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app
Click to expand...
Click to collapse
Yes
Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?
ChrisJ951 said:
Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?
Click to expand...
Click to collapse
Yes, it's deodexed, zipaligned, SELinux in permissive mode, RIC disabled, busybox installed, write-enabled external SD card, adb insecure. I'll probably add some other things soon - Xposed is top of the list.
Does you think this can fix the over heating problem with some Z3+ devices? I hope so
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Got my Z3+ last night and about to unlock the bootloader so happy to give it a test and report back. I've seen the command line twrp link but might need some additional guidance on flashing your ROM, if you wouldn't mind.
lilloscar said:
Does you think this can fix the over heating problem with some Z3+ devices? I hope so
Click to expand...
Click to collapse
I doubt it. I've made no bug fixes. If there's a problem in the base ROM, the problem will exist in this ROM.
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.
My first initial thoughts are perfect. I haven't had any issue whatsoever. No problem with root, works with every app. Appreciate the work.
Skickat från min E6553 via Tapatalk
rjhellel said:
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.
Click to expand...
Click to collapse
Which version of Xposed did you use? All the ones I tried only resulted in bootloops.
I used official xposed v73 sdk21 arm64.
Little note: You have to wipe dalvik cache before or after installing Xposed to prevent bootloop.
Latest Xposed has auto-wipe feature, but to make sure...
Could I test, just unlocked my bl last night
hello all this rom have lte band 38/2600 ? Or can be added? thx
Having a e6533 Dual. 266 firmware with unlocked bootloader. Would like to downgrade and test this rooted 251 ROM. Thank you.
I used to use xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip as from some post. Facing random reboot from time to time.
Last week, I need to reflash, I tried official xposed-v79-sdk21-arm64.zip. It works ... and the phone stay "no reboot" for one day. Then it starts again. I wipe cache and seems back to be more stable. My own feeling is thsi v79-sdk21 has less reboot issue, but still does.
---------- Post added at 16:35 ---------- Previous post was at 16:29 ----------
BTW, Sony has new update in Asia ...
28.0.A.8.272 Release: 1/9/2016 Still 5.0.2
I could not find anywhere to download full rom. Also not sure existing root/xposed will work or not.
I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.
Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...
Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.
This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.
Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.
Hey all,
I realize this might need a wipe, but honestly if there is a fix it will save me a few hours headache of reloading and re-configuring everything.
Currently my phone will not root properly. I'm using the latest release MTC19V. I used the Nexus Root Toolkit to upgrade without wipe from the previous version like I normally do. After upgrading, I used the root function. There were no errors, however some applications are stating SU is not present.
SuperSU thinks everything is fine. Root requests are popping up normally.
BusyBox states "the su binary was not found on your phone", even after SuperSU pops up and I grant it permission. I assume BusyBox is no longer installed.
AdAway states "su binary could not be found" after I grant permission.
Greenify gets root access fine.
Xposed is working.
Also, after it is rooted, I no longer have access to DATA services over the 2G/3G/LTE networks, there is a "!" icon by the signal bars. WiFi works fine. If I flash back to stock without wipe, everything works normally.
I have tried:
- Unroot, flash back to stock MTC19T
- Removing all apps and installs of Xposed, SuperSU, BusyBox
- Using the uninstall and clean options in SuperSU
Going to keep messing around, but if anyone can point me in the right direction to avoid a full wipe, that would be fantastic.
Thanks.
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Tarv said:
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Click to expand...
Click to collapse
Ok, the regular ole busybox and adaway don't work with systemless root. There are additional things that need to be flashed. When I get to my computer I'll post a link to the files.
Sent from my SM-G930V using Tapatalk
---------- Post added at 05:00 PM ---------- Previous post was at 04:51 PM ----------
Flash the systemless hosts file from THIS link to get adaway working.
Try THIS busybox. If it doesnt work try THIS one.
Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?
Sent from my Nexus 6P using XDA Labs
Spikedude said:
I think the problem might be a corruption of the Busybox installation
Click to expand...
Click to collapse
Spikedude,
I think I was in the same boat. Before it stopped working, I too was seeing BusyBox 1.24.1 and not able to upgrade to 1.24.2. I also did an uninstall.
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
I used the other method of installing BusyBox as PiousInquisitor mentioned, and it installed properly, although it's using 1.24.1. BusyBox by Stericson still does not show it's installed.
I also think the installer from Stericson is busted and what caused this whole mess.
Tarv said:
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
Click to expand...
Click to collapse
Hey Tarv,
Thanks for the update. When you wiped the phone, what method did you use? Factory reset from within settings, or using NRT to flash stock and unroot with the "no wipe" option to preserve user data disabled?
Also, you might be right about the broken Stericson Busybox installer. Busybox on Rails looks like a good alternative. I've disabled the NRT option to install Busybox by Stericson when rooting, so I'll just install Busybox on Rails after the fact.
Sent from my Nexus 6P using XDA Labs
Spikedude said:
When you wiped the phone, what method did you use?
Click to expand...
Click to collapse
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Tarv said:
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Click to expand...
Click to collapse
Thanks Tarv,
Followed your procedure and am once again rooted and have data connectivity.
Unfortunately, installation of Busybox was not successful. Tried the BB on Rails version, but it only installs to /system/xbin, not /su/bin. As a result, the same root apps that didn't work previously still don't work. BB by Stericson pops up the success message, but then indicates BB is not installed.
So almost back to square one. I'll try going back to stock and rerooting using NRT again, but this time enable BB installation as part of the rooting process. Maybe...
UPDATE:
First, I may have spoken too soon about BB on Rails not working. I based that on root mode of ES File Explorer not working properly, but that might be an ES problem. Play Store reviews are also complaining about the ES root problem. So maybe installation of BB to /system on systemless root is ok?
I wiped and rebooted with NRT, and allowed it to install BB by Stericson. This worked fine, allowing installation of 1.24.2 of BB to the /su/xbin directory. Originally it indicated /su/bin, and that the "cat" file was missing (whatever), but after reinstalling to xbin a couple times and some restarts it all looks normal. Adaway works, full data connectivity works, etc. Trying to flip the root mode switch in ES pops up an error, but I can still explore root, so no big deal (I'm using Solid Explorer more anyway).