1

to day I add one daemon file to android devices, I use command:

 ./adb push XXXXX   /system/bin/sh

I say done, but when i restart the device, now it can not boot, no logo appear, just black screen, although I see the light is enabling. I can not know what can I do now, how can i fix it... plz

3
  • 2
    Instructions vary on phone brand/model, but you'll need to reflash stock firmware, which may or may not erase all your data. If you end up flashing the exact same build number, your data may still be there. Mar 28 '16 at 8:02
  • @AaronGillion Would you like to post that as an answer?
    – Dan Hulme
    Mar 28 '16 at 8:06
  • hello. My device is a board, then only connect to this by using "adb". The problem is now the device can not booted, and I can not coonect to device to, can not connect to recovery mode. Sorry if I have a silly question, but can you explain more how can i solve it
    – kemdo
    Mar 28 '16 at 8:11
1

USE FASTBOOT INSTEAD...Shell/sh has been replaced by

adb push  xxxx  /system/bin/sh

Shell controls the adb commands, So ADB is now disabled ! ... What you need to do is reboot into FASTBOOT using the device specific button code while the phone starts
(usually home and volume up together for 10 seconds) or(power and volume up )
Once inside FASTBOOT you need to replace your boot.img and system.imgSystem then boot

fastboot flash system xxxx.img

fastboot flash boot xxxx.img

XXXX represents the .img file name

7
  • Hi, can i enable fastboot through other action, because my board does not have volume, home, back... botton, only screen... :(
    – kemdo
    Mar 28 '16 at 9:44
  • What board are you using ? Mar 28 '16 at 9:48
  • the old board made by my partner, use your own SDK android, and does not have home, press, volume button... and used android 4.0 only
    – kemdo
    Mar 28 '16 at 9:56
  • 1
    Fastboot can only be accessed with adb reboot-bootloader or button combination... Replacing SH shouldn't of caused a boot error however... You should still see a boot logo and a boot loop after that !... Mar 28 '16 at 9:57
  • 1
    When making the board, did you include a pre-boot recovery.. Some devices include a recovery accessible by removing the battery fully and plugging back in ... Then it loads the device in devices on pc... You need a driver .. I think it's called something like V-COM Driver Mar 28 '16 at 10:02
0

It sounds like you pushed xxx to replace your Shell Binary in bin... Shell is not a folder but a binary file... If you have replaced this on purpose with a custom binary, then you needed to run a

adb chmod 0755 /system/bin/sh
or
adb shell  chmod 0755 /system/bin/sh

Adb Shell Might work because you have replaced the shell in system, You can run a remote shell command..
If you can still connect in any way..

IM NOT SURE ABOUT THE EXACT PERMISSION, 0775, 0755, 0777

4
  • hello, I think the problem is I can not use "ADB SHELL" command, because the device not boot , just black screen. So I can not connect to devices through " adb connect X.X.X.X"
    – kemdo
    Mar 28 '16 at 8:38
  • Hi, if I wrong, please teach me, i am new about using linux command :)
    – kemdo
    Mar 28 '16 at 8:44
  • Forget ADB and try using Fastboot ... Use Fastboot by holding the opposite button of Recovery... For example, if Volume Up is recovery, use Volume Down at boot , + the usual extra buttons - home or power ... Mar 28 '16 at 9:16
  • P.s > ADB connect is not a command...( ADB DEVICES) - (ADB REBOOT )-( ADB WAIT-FOR-DEVICE )-(ADB PUSH/PULL)........ Mar 28 '16 at 9:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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