Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I am trying to install BusyBox on panda board which has an ICS Android kernel.

I used the steps below:

  1. Download binary file which supports the panda board
  2. Push it into /system/busybox folder
  3. Install the BusyBox command line tools on the target by executing the following commands on booted filesystem:
    pc ./adb shell
    target$ cd /system/busybox
    target$ ./busybox --install .
    target$ ./sh  #here i am getting error like ./sh: precmd: not found
  4. Save the original sh executable by renaming it, and then create a soft-link to BusyBox sh:
    target$ cd /system/bin
    target$ mv sh sh.android
    target$ ln -s /system/busybox/sh sh
  5. Export
    export PATH=$PATH:/system/busybox:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

Step 3 is to install BusyBox, and step 4 is to make BusyBox shell as default shell. But I am getting an error in the 3rd step. I want to make BusyBox shell as default shell, so I can run scripts on panda board.

I appreciate any type of suggestions or solutions. Thanks in advance.

share|improve this question
add comment

2 Answers

If you are using Connectbot: according to an article at XDA-Developers, this is nothing but a cosmetical error:

Connectbot seems to set shell variable 'PS1' to "$(precmd)$USER@$HOSTNAME:${PWD:-?} $ ".
It means your shell (the busybox's ash applet) will try to use output from 'precmd' as a part of a command prompt. So when 'precmd' was not provided, error messages will be generated wenever a prompt was to be shown.

To fix this, mentioned post says you can use PS1="> " (or simply unset PS1) to work around that error.

share|improve this answer
    
Looking for further references, I found you already cross-posted this to stackoverflow and got an answer there. It would have been fair to update your question here accordingly, as you obviously got a solution there (the same, it seems) which solved your issue. –  Izzy Mar 15 '13 at 16:04
add comment

Try this :-

adb remount

adb push busybox /system/xbin

enter adb shell and issue below commands

cd /system/xbin

chmod 777 busybox

busybox --install -s /system/xbin

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.