• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Boot_Buddy - Run Boot Scripts from SDcard (root users)

@Tokenpoke
The following lines leads me to think that you do not have busybox installed-
Error resolving interpreter:/system/xbin/sh does not exist
Using default shell
/mnt/sdcard/Download/bb_install.sh[7]: sed: not found

You should have busybox installed at the location
/system/xbin/busybox

Hopefully that resolves it for you. I will look over the OP and script and update them to indicate this information if necessary. Thanks
 
Sepero said:
@Tokenpoke
The following lines leads me to think that you do not have busybox installed-
Error resolving interpreter:/system/xbin/sh does not exist
Using default shell
/mnt/sdcard/Download/bb_install.sh[7]: sed: not found

You should have busybox installed at the location
/system/xbin/busybox

Hopefully that resolves it for you. I will look over the OP and script and update them to indicate this information if necessary. Thanks
Click to expand...


Was installed but reinstalled and it works now o.O
 
This worked perfectly, but then I updated busy box (using Stericson's updater), & now it won't work at all. I put busybox back in system/xbin, deleted & reinstalled Boot Buddy, now I get "unexpected <" error.

Edit: (I meant the linked guide to mount your Real SDcard worked perfectly.)
 
unicyclist said:
This worked perfectly, but then I updated busy box (using Stericson's updater), & now it won't work at all. I put busybox back in system/xbin, deleted & reinstalled Boot Buddy, now I get "unexpected <" error.
Click to expand...

You need to install busybox correctly... Theres many apps on the play store... Once you find the correct one it should work


Thats how I solved my error thing
 
Sepero said:
@unicyclist
Are you saying that installing Boot Buddy gives you this error?
"unexpected <" error
Click to expand...

I (stupidly) updated BusyBox. Boot Buddy no longer mounted my SD card "as God intended". It was reset to external_sd. So I tried uninstalling & reinstalling, and I got the "unexpected <" error. I reinstalled an older version of BusyBox to system/xbin and now I get "sh: applet not found"

orangejuicebox said:
You need to install busybox correctly... Theres many apps on the play store... Once you find the correct one it should work


Thats how I solved my error thing
Click to expand...

Which installer did you use?
 
pfft Umm IDK I forgot there's two APpS busy box and busy box installer.... You have to let it install automatically and yes the versions do matter this would be easier if I wasn't buzzedter
 
orangejuicebox said:
pfft Umm IDK I forgot there's two APpS busy box and busy box installer.... You have to let it install automatically and yes the versions do matter
Click to expand...

Edit: Busybox Installer worked. I used version 1.14.3 and installed to system/xbin, not system/bin. Then redownloaded the bb_install script using Opera Mini.
 
A new update has been released- BootBuddy version 1.3

Also, the source is now available on github
https://github.com/Sepero/bootbuddy
https://github.com/Sepero/bootbuddy/archive/master.zip

Updates include:

  • Smarter recognition of busybox location (bin and xbin)
  • Smarter recognition of shell location (bin and xbin)
  • All scripts are now logged, and their output. Log file /data/boot_buddy.log
  • Now supporting a wider range of limited shells by replacing a 'here document' with an echo for file creation of the boot_buddy.sh script.
Running the v1.3 installer will automatically update your current install of BootBuddy.
 
@adanmex
I'm glad you ask. I really like that idea, but unfortunately I do not plan to do that for two primary reasons.

  • Having more than one way to install BootBuddy means a greater possibility for software bugs to occur. (and debugging scripts can be a real pain :(, especially running it on multiple types of devices in a pre-boot environment)
  • If I have to choose one install method, I must currently choose installing it as a script, because CWM cannot be installed to all devices. Keeping the installer as a script provides the greatest compatibility with all devices.
Hopefully that answers your question satisfactorily. Thanks for the suggestion.
 
@Malebolgia
The latest release of BootBuddy should now work with any busybox. If it doesn't, please let me know! :D
 
How can i put the lte2 2nd init app in my boot buddy scripts so it can run at boot in case I have a bootloop. On my spare sd card?
 
@MotoTriumphant
That's a good question. Unfortunately, I don't really know how it would be done. If it's possible, the files to do this are in the location
/data/data/com.eclipse.android.razr.bootstrap/files/

Hopefully you are able to figure it out. I'd be interested in knowing the answer also
 
Is there away to get an individual script loaded by bootbuddy to stall or delay?
Say i am trying to change a system setting but system overwrites what my bootbuddy script did.
 
You must log in or register to reply here.
Back
Top Bottom