Does anyone use Supercharger v6 on AOKP? I tried using it, but I got an awk error, so I installed the modified busybox from their site, but it doesn't persist after reboot (reverts back to 20-cm9).
I guess my question is does anyone know if I can get these two to play nicely?
For people having this issue, please refer to zepplinrox's Supercharger v6 thread where you can find a script that will reinstall busybox 1.19.4 on boot.
Did you completelyremove all busybox information from your phone before installing the new version?
If so, try doing a cache and dalvik wrote in between (can't hurt) for kicks. If you get out working but can't get the minfrees to stick, run 99SuperCharger.sh as root and at boot.
Lemme know.
Clay
Sent from my SGH-I777 using XDA
use script manager, and have it set to run at startup
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
use script manager, and have it set to run at startup
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
just the 99SuperCharger.sh file, not the entire script.
Oh, and for sure use sm, haven't used terminal emulator but sm is easy to navigate and get used to.
Clay
Sent from my SGH-I777 using XDA
Last I checked, completely removing busybox is dangerous business. I can't seem to do it anyways . But I removed about as much as I can using the BusyBox app, but it still reverts back to 1.20.0-cm9 after a reboot.
Then I tried manually deleting /system/bin and /sbin, but as expected that caused very bad things to happen .-.
lol, nvm, deleting /system/bin and /sbin just f-ed up my su binary. After replacing that, BusyBox (app) is still reporting that I have 1.20.0-cm9 installed.
When you open busy box what does it tell you at the top? 1.20 or whatever?
Do you then have the option to choose what version you wish to install? If so, what happens if you choose 1.19.4?
I originally chose version 1 of the version 1.20's then reverted back to 1.19.4. I'm SuperCharged fine. I'm running a different Rom and Kernel, but that seems to working for me
Clay
Sent from my SGH-I777 using XDA
It tells me 1.20.0-cm9 installed if I use the free version. If I use the paid version, I get "multiple busybox installed" (possibly from TB?)
I'll give 1.19.4 a shot.
1.19.4 still reverts back to 1.20.0-cm9 on reboot.
use the boot reinstaller version from the supercharger OP.
It reinstalls wraithdu's v1.19.4 busybox build on every boot for situations like yours.
zeppelinrox said:
use the boot reinstaller version from the supercharger OP.
It reinstalls wraithdu's v1.19.4 busybox build on every boot for situations like yours.
Click to expand...
Click to collapse
Lol, I was just reallllyyy hoping to find a way around that lol.
I created that tool because there is no way around that - except for fight fire with fire
lol, thanks zeppelinrox. Should I set that up with sm? Or somehow put that in init.d? Does SS99Supercharger work then?
Yeah just run it like you do all my other scripts...
After rebooting, check to see which busybox build is active
Problem is that it always defaults to 1.20.0-cm9, lol. Whatever, I've just put your busybox installer script in init.d and having it run right before SS99Supercharger, and all seems to work well. Thanks a lot for you help and the awesome script
heh... well that's what the boot reinstaller script does - it converts the normal installer script to a proper init.d script (renames it to 96busybox and removes sleep commands and other stuff)
Oh my bad, you had a script for that? o.0 I assumed you meant "just copy it into init.d xD"
Looking now...lol
ya... it's called boot reinstaller or something like that... lol
Related
DROID X2 init.d hack
This is an alternative to a certain 2nd init functionality, because with 2nd init you could do this just as easily if you know how. This is not an init. This is for the folks running stock 2.3.3 for the Droid X2, who want to "performance tune" their phone while working with what they have. This will allow you to use any init.d performance scripts on your phone. If you don't know, an "init.d" script is special in the sense that they are run when the phone is booting up. This way, when you are using your phone, you can enjoy performance benefits.
The "hack" runs the BusyBox "run-parts" binary and searches the /system/etc/init.d directory for scripts. Additionally, if for whatever reason you don't have BusyBox, it will fall back to a for loop and run that instead! This functionality is added through "install-recovery.sh" script in /system/etc which is run every time the phone boots by default. Normally this script tries to install the default recovery every time you boot your phone, so that you can't install any other recovery. I've hijacked that script for the init.d task instead. As is common practice, any script actions can be viewed in your logcat upon boot if you have USB debugging enabled.
This hack includes default enhancement scripts (outlined below). You can choose to use these scripts, or delete them and replace them with whatever you want. I would advise against running the default scripts with other tweak scripts!
Requirements:
Root - follow the guides
Bootstrap Recovery - follow the guides
Knowledge of CWMR/Bootstrap Recovery use, and how to install a zip with it
Default Enhancements:
sysctl tweaks - try to speed up OS/virtual machine/kernel
lowmem tweaks - try to limit low memory so as to keep more memory available
sd read ahead - increase KB read ahead on SD reads
cpu/governor tweaks - set scaling_min/max_freq and governor
disk scheduler - optimize disk scheduler for flash memory across all blocks
---
Changelog
0.1
Initial release to public
0.2
Tweaked scheduler and send errors to null
0.3
Fixed scheduler bug
Added additional scheduler tweaks
Changed min_free_kbytes to 32mb
Changed bdi read_ahead_kb to 2048kb
Added system r/w mount
Added sync
0.4
Added quantum to scheduler tweak
Switch to noop scheduler
Added conditionals
Change CPU tweak to support cpu1
Change scaling_min to proper freq
0.5
Split script into 3 versions
Battery - most power savings
Midrange - balanced power savings/performance
Performance - all out speed
0.6
Combined script back into one generic version
Includes separate scripts for all purposes
Enhances prior scripts functionality
Rewrote init.d hook to work in all scenarios
Included BusyBox 1.19 with installation
0.6b
Updated script to fix unique error
---
Version 0.6b FINAL
Download: http://www.multiupload.com/FI1D93TV6Y
Mirror: http://www.mediafire.com/?71geufr3754j6be
amazing! should usher in a ton more dev for the X2
Great to hear from you again navenedrob! Loved your work on the fascinate.
Sent from my DROID X2 using XDA Premium App
Will this have any ill effects with the eclipse rom?
Sent from my DROID X2 using XDA App
Its for stock roms as stated in the 1st post
Sent from my DROID X2 using XDA App
Getting ready to run this but just want to clarify:
Install like any other. zip?
Use script manager to tweak values?
How to revert, if necessary?
Remove v6 supercharger before installing?
Thanks again.
Sent from my DROID X2 using XDA Premium App
garywojdan81 said:
Getting ready to run this but just want to clarify:
Install like any other. zip?
Use script manager to tweak values?
How to revert, if necessary?
Remove v6 supercharger before installing?
Thanks again.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Yes
Yes
Delete scripts from /system/etc/init.d, that's it
Optional
Kanibull said:
Its for stock roms as stated in the 1st post
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
You can use this on Eclipse ROM. That is a stock ROM. A non-stock ROM would be a stock ROM with this or 2nd init already included, CM7, or MIUI.
Thanks man. Gonna load it as soon as I get back home.
Sent from my DROID X2 using XDA Premium App
Would using this allow zepplelinrox's 98kickasskernel to work as it should?
So are these scripts already optimized or are they stock values waiting to be tweaked? Is there some kind of guide as to exactly what the numbers mean or could you recommend some? Thanks!
Sent from my DROID X2 using XDA App
ashclepdia said:
Would using this allow zepplelinrox's 98kickasskernel to work as it should?
Click to expand...
Click to collapse
Wow, yeah it should indeed.
This should be posted at droidforums and droidxforums!
I have a few questions.
Using Script Manager I had to modify/change most of my scripts because Script Manager would try to run them and simply state there were syntax errors, which was simply not the case because on my oringial droid I could verify they would run using init.d and they would work.
So my question there is what's with the syntax error in script manager, and will my original scripts work? Second, are these automatically run as root...or?
zeppelinrox said:
Wow, yeah it should indeed.
This should be posted at droidforums and droidxforums!
Click to expand...
Click to collapse
If it hasn't already been done by the time im done eating ill get to linking up to share the goodness. Thanks for quick reply zepp.
Good stuff...
I know for a fact that they will be all over this like brown on poo at droidx...
0vermind said:
I have a few questions.
Using Script Manager I had to modify/change most of my scripts because Script Manager would try to run them and simply state there were syntax errors, which was simply not the case because on my oringial droid I could verify they would run using init.d and they would work.
So my question there is what's with the syntax error in script manager, and will my original scripts work? Second, are these automatically run as root...or?
Click to expand...
Click to collapse
Which busybox version?
That Rom you where talking about
What kind of Rom would it be, would be an aosp?
zeppelinrox said:
Which busybox version?
Click to expand...
Click to collapse
v1.19.0.git.adrynalyne
Installed in /system/xbin
0vermind said:
I have a few questions.
Using Script Manager I had to modify/change most of my scripts because Script Manager would try to run them and simply state there were syntax errors, which was simply not the case because on my oringial droid I could verify they would run using init.d and they would work.
So my question there is what's with the syntax error in script manager, and will my original scripts work? Second, are these automatically run as root...or?
Click to expand...
Click to collapse
I'm not sure what Script Manager is, so I can't really answer. All I can say is that I write all my scripts by hand, and they are all common shell scripts using bash language. As long as your shell scripts are written according to those specs, then I don't think you'd have any problems.
Anyone else, remember that you can use whatever init.d scripts you want, it shouldn't really matter as long as they somewhat pertain to the phone. Feel free to delete the included scripts.
Okay I set it all up and none of the scripts ran, so I did
Code:
/system/xbin/run-parts /system/etc/init.d > /data/initd.log
in adb and got back
run-parts: applet not found
Click to expand...
Click to collapse
What am I doing wrong?
After many hours of screwing around, I figured out how to get around your busybox run-parts thing which doesn't seem to be working on my phone. In it's place I put:
Code:
if [ -e /system/etc/init.d ]
list=`ls /system/etc/init.d/*`
for script in $list
do
sh $script
done
fi
Everything is working awesome now!! They really do seem to be running at start up!
This is something I realized when the init.d hack by naven was posted, it plain didn't work for me, and after some investigation i discovered that not all busybox versions had the run-parts applet.
It has come to my attention to that many users may not have the proper hack installed, at least the ones using my scripts, I had them check in /data for the zipaplign log and it was in fact not there.
I got it working by modding navens hack. Credit goes to him for his discovery.
Here is a link to the flashable zip. If you are using my scripts, check in /data for the zipalign log, if you don't have one, just flash this zip, reboot, and check again.
http://www.sendspace.com/file/9g6ngz
Thanks!
Edit (8/31/2011): Just so there is no confusion, this is not my new Speedy script, this is just a re-hack for init.d originally discovered by naven. This will just help those of you having problems with his hack. Obviously you need to be rooted and have recovery bootstrap.
Just flashed your zip. Log file in /data
Welcome back! Thanks for your work on the X2.
Sent from my DROID X2 using xda premium
Grapejelly!!
Sent from my DROID X2 using xda premium
Worked perfectly
Sent from my DROID X2 using XDA App
Is this a new version of your script then?
Do we have to flash this the same way with recovery (aka renaming it to update.zip) like i had to go with the manual gb update?
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
SuBDivisions said:
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
Click to expand...
Click to collapse
There is an option under advanced I think, in recovery, to enable/disable that.....
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You need to use the modified boot -strap recovery available on this forum. D/L it & install it like any other app. When you open it, just read & follow the directions on the screen & you will get to the custom recovery where all good things flash from.
Sent from my DROID X2 using xda premium
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You should be flashing this thru the Bootstrap Recovery, not the default Android Recovery.
Sent from my DROID X2 using Tapatalk
Ahh HA.. See i know i was missing something.. Thanks have been given.
Zip-align logs were not showing in /data/ for me, so I flashed this, and now they do.
I'm assuming that means the rest of the scripts weren't working either?
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
BusyBox with run-parts binary, installed in /system/xbin - If you don't have BusyBox, you can download it from the market here.
Click to expand...
Click to collapse
hapyman said:
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
Click to expand...
Click to collapse
You should be okay on 1.19.0 now, but busybox should always always be installed in xbin.
So which init is better or the working one?
gkitab said:
So which init is better or the working one?
Click to expand...
Click to collapse
Some people find that the re-hack (this thread) works (and the original does not), others find that the original hack works just fine. A way to test is to install my Speedy Gonzales scripts, reboot the phone, and then check in /data for a zipalign log. If not, then flash this re-hack.
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing. I also noticed when I flashed speedy navens old oo got left behind. So I deleted al scripts in init folder and reflashed yours and all yours are now correct.
With his init and your script. Yours scripts are in there but no zipalign in data.
Should I start over by deleting unit folder flash your unit then speedy would that be the safe bet?
Thanks for staying.
gkitab said:
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing.
Thanks for staying.
Click to expand...
Click to collapse
They are two separate things entirely. I posted the re-hack for those having troubles getting scripts to run with naven's original hack. The re-hack posted in this thread doesn't contain any init.d scripts, it's purely the hack. Like I said above, a good way to test his hack is to install my scripts (which it looks like you have), and then use a file manager like Root Explorer and navigate to /data, there should be a zipalign log, if there isn't then his hack isn't working.
Edit: Well, the biggest question is if the init hack you have installed is even working. I'm assuming you have naven's... try the above, let me know if the log is there or not.
I edited my post can you please check it and let me know what you think.
I do have his with your script.
I think I should I should delete init completely and start fresh with yours and your scripts. That sounds like safest bet. Or does naven init need to be there first then yours on top then your scripts. Thanks.
Hi, I just installed NottachTrix on my Atrix.
Now all I need to know is which installation option of V6 Supercharger script is best for this device. Ideally, a small explanation with each option to help me learn.
Thanks.
BPinard said:
Hi, I just installed NottachTrix on my Atrix.
Now all I need to know is which installation option of V6 Supercharger script is best for this device. Ideally, a small explanation with each option to help me learn.
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1334834.
Busybox/Supercharger V6 Advice for Nottachtrix v.1.3.1
I would like to try the V6 Supercharger script. I'm running Nottachtrix v1.3.1. Having read through the main Supercharger thread, it appears Nottachtrix contains a version of busybox that is known to cause problems, 1.18.4. It seems prudent to update busybox before attempting to run the script. But I need to know which busybox to install and how to do that.
I have downloaded the CWM-flashable version recommended in the Supercharger thread, which is by wraithdu and installs version 1.19.4. Having looked inside the zip it appears it only install to system/xbin and exploring Nottachtrix file tree shows busybox is in both system/xbin and system/bin.
Does anyone know the best way to "properly" (i.e. both locations) update busybox in Nottachtrix? And which version I should install for full busybox implementation and trouble-free Supercharger scripting?
Also, is there a particular version of the script I should be using for my Atrix?
gandalf_grey91 said:
I would like to try the V6 Supercharger script. I'm running Nottachtrix v1.3.1. Having read through the main Supercharger thread, it appears Nottachtrix contains a version of busybox that is known to cause problems, 1.18.4. It seems prudent to update busybox before attempting to run the script. But I need to know which busybox to install and how to do that.
I have downloaded the CWM-flashable version recommended in the Supercharger thread, which is by wraithdu and installs version 1.19.4. Having looked inside the zip it appears it only install to system/xbin and exploring Nottachtrix file tree shows busybox is in both system/xbin and system/bin.
Does anyone know the best way to "properly" (i.e. both locations) update busybox in Nottachtrix? And which version I should install for full busybox implementation and trouble-free Supercharger scripting?
Also, is there a particular version of the script I should be using for my Atrix?
Click to expand...
Click to collapse
The BusyBox installer available on the V6 Supercharger thread is the one you want to use.
upndwn4par said:
The BusyBox installer available on the V6 Supercharger thread is the one you want to use.
Click to expand...
Click to collapse
Do you mean the installer script? Will it update both locations in Nottachtrix? Because it appears to be the same as the CWM-flashable one just with a script to install it?
gandalf_grey91 said:
Do you mean the installer script? Will it update both locations in Nottachtrix? Because it appears to be the same as the CWM-flashable one just with a script to install it?
Click to expand...
Click to collapse
At the bottom of the post there is a CWM flashable busybox installer zip. It will install a fully compatible version of busybox in the place it needs to be.
Stop fretting over install locations and just do it.
upndwn4par said:
At the bottom of the post there is a CWM flashable busybox installer zip. It will install a fully compatible version of busybox in the place it needs to be.
Stop fretting over install locations and just do it.
Click to expand...
Click to collapse
It is amazing how a small piece of "advice" can cause a crisis. Thanks for the response. The CWM version will not install, CWM aborts install and says zip file is corrupt (downloaded multiple times). Tried script install and it installed to system/bin and not system/xbin and now I have lost root!!!
Tried the 2 "big name" busybox installers and neither will install any version of busybox because I no longer have root.
This is exactly why I asked for advice.
Edit: Restored from nandroid backup (many times!) and tried 4 different version of busybox installed to both locations via JRummy and Stericson busybox installers, none will install on Nottachtrix with or without root. WTF?
Is there an Atrix-specific CWM-flashable version of Busybox newer than version 1.18.4?
Is busyBox built into CWM recovery kernals? is this common practice?
if so, and "I believe it is" How can I update my busyBox Version?
The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again.
So I geuse what Im asking for is verification basicly.
Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab?
By the way to all comers who would like to bash my noobness Bring it!
I say this because I can learn more from the bashing than from no response/answer at all.
That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Pirateghost said:
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
Click to expand...
Click to collapse
Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed.
I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot)
I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings.
However on the skyRocket I do not seem to have this problem I believe this is why.
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
While Great for My "I727" that doesnt help me on my "I777"
rdannar said:
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks but not at all what I was talking about.
Phatboyj420 said:
Thanks but not at all what I was talking about.
Click to expand...
Click to collapse
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
rdannar said:
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks again but your still off please re-read O.P.
Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot.
The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to
"/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread.
Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin).
Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot).
To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.
Im running ICS SlimROM 1.6 and (was) loving it. But:
Titanium Backup Pro prompted for an update, which I ran, then it barfed and told me to install BusyBox from the market
Installed BusyBox, which got TB to run
uninstalled WiFi tether ( not working, another issue.....)
Next full reboot of phone, its stuck at the Google Gears
Then:
I went into recovery, wiped cache, Dalvik and ran fix permissions
Reboot, stuck at Google Gears
Mounted SD in Recovery, copied my PH98img file to SD, fastboot and ran update
Still stuck at Google Gears
I need to get the file off of SD to get into Recovery again, but when I do, what next ? Full wipe ? Reflash ROM ?
Only thing I can think of is BusyBox broke the ROM......am I wrong ?
I was stuck doing a full reflash of the rom, fixes, updates etc.......only thing I can figure is that the supersu was gorked...... Superuser (chainsdd) from the market ended up on my phone after the busy box install and didn't want to work or be removed until reflash.
Sent from my ADR6425LVW using xda app-developers app
archalon said:
Im running ICS SlimROM 1.6 and (was) loving it. But:
Titanium Backup Pro prompted for an update, which I ran, then it barfed and told me to install BusyBox from the market
Installed BusyBox, which got TB to run
uninstalled WiFi tether ( not working, another issue.....)
Next full reboot of phone, its stuck at the Google Gears
Then:
I went into recovery, wiped cache, Dalvik and ran fix permissions
Reboot, stuck at Google Gears
Mounted SD in Recovery, copied my PH98img file to SD, fastboot and ran update
Still stuck at Google Gears
I need to get the file off of SD to get into Recovery again, but when I do, what next ? Full wipe ? Reflash ROM ?
Only thing I can think of is BusyBox broke the ROM......am I wrong ?
Click to expand...
Click to collapse
Most likely, you installed busybox to the /system/bin/ directory.
Uninstall it, restart your phone, then re-run the busybox installer, except this time make sure you select /system/xbin/ as the install path.
a.mcdear said:
Most likely, you installed busybox to the /system/bin/ directory.
Uninstall it, restart your phone, then re-run the busybox installer, except this time make sure you select /system/xbin/ as the install path.
Click to expand...
Click to collapse
I'm on CleanRom 4.4 and it runs fine. I have the BusyBox install app from the market. I currently have BusyBox 1.20.2 installed and it's installed in /system/bin. That's where it wanted to install it, so i let it. I have had no problems with it being there. Should I move it? What is the pros and cons of it being in /system/bin vs /system/xbin??
Thanks.
derek4484 said:
I'm on CleanRom 4.4 and it runs fine. I have the BusyBox install app from the market. I currently have BusyBox 1.20.2 installed and it's installed in /system/bin. That's where it wanted to install it, so i let it. I have had no problems with it being there. Should I move it? What is the pros and cons of it being in /system/bin vs /system/xbin??
Thanks.
Click to expand...
Click to collapse
If its working at /system/bin/ then its probably not an issue for you.
I have init.d scripts, and my init.rc calls for busybox to be located at /system/xbin/. If I accidentally installed busybox to /system/bin/, busybox and thus also my init.d scripts fail to load because the init.rc file still tries to load it all from /system/xbin/.
but, since its likely you didn't build your ROM yourself, you may not know exactly where its supposed to be installed. You could look at the original update script in the zip file that installed your ROM, because usually there will be an install path and associated symlinks in that script which you can then use to determine where busybox is supposed to be installed on your particular device. Or, if your ROM has init.d support, you can look in the /init.rc file for the lines where busybox is called to enable init.d support. Your install path for busybox should mimic whatever path is called in this file, meaning if its attempting to load busybox from /system/xbin/, then that is where you need to have busybox installed, and not /system/bin/.
a.mcdear said:
If its working at /system/bin/ then its probably not an issue for you.
I have init.d scripts, and my init.rc calls for busybox to be located at /system/xbin/. If I accidentally installed busybox to /system/bin/, busybox and thus also my init.d scripts fail to load because the init.rc file still tries to load it all from /system/xbin/.
but, since its likely you didn't build your ROM yourself, you may not know exactly where its supposed to be installed. You could look at the original update script in the zip file that installed your ROM, because usually there will be an install path and associated symlinks in that script which you can then use to determine where busybox is supposed to be installed on your particular device. Or, if your ROM has init.d support, you can look in the /init.rc file for the lines where busybox is called to enable init.d support. Your install path for busybox should mimic whatever path is called in this file, meaning if its attempting to load busybox from /system/xbin/, then that is where you need to have busybox installed, and not /system/bin/.
Click to expand...
Click to collapse
I'm running Scott's CleanRom 4.4. I've looked in the updater-script file inside the zip.
I see the line: symlink("/system/xbin/busybox","/system/bin/busybox");
So, I am assuming that it can be installed in either location. When I installed busybox using the busybox install app from the market, it has "Smart Install", it scans system memory and then recommends where to install everything so I just let it do that.
derek4484 said:
I'm running Scott's CleanRom 4.4. I've looked in the updater-script file inside the zip.
I see the line: symlink("/system/xbin/busybox","/system/bin/busybox");
So, I am assuming that it can be installed in either location. When I installed busybox using the busybox install app from the market, it has "Smart Install", it scans system memory and then recommends where to install everything so I just let it do that.
Click to expand...
Click to collapse
So, according to that symlink, the actual location of busybox should be in /system/xbin/, but has created a symbolic link to /system/bin/ because some applications look for it in that location as well.
on a linux system, the physical location is the first listed path, the symbolic link is created by the second path, which essentially allows you to run busybox from either location even though it is actually located in /system/xbin/ and not /system/bin/
make sense?