Hello,i get a problem exec '/system/bin/sh' failed: No such file or directory (2) when i root and unlock bootloader i try to upgrade rom from 2.3.7 to ics when i try. EDIT: The script ( I didn't write it so don't /bin/bash me over it. Unable to execute./test.sh: No such file or directory $ sudo bash./test.sh bar. No such file or directory error when trying to execute startup script. Etc/init.d/testsam: No such file or directory. Is actually called /bin/bash^M.

I have a china tablet named Quest. I have accidentally repeated pattern lock more than 5 times. Call Of Duty Modern Warfare 3 Aimbot Hack Pc Remote. Now I have also forgotten the email address. So for a factory-reset of my tablet I simply booted it into recovery mode.

But it shows an Android bot lying with red exclamation mark. After a spending hours I found a shortcut i.e, vol + and power to access recovery menu. But my tablet doesn't go to recovery menu even when I pressed the keys. So I simply connected my tablet to my pc via USB and installed drivers. In adb command prompt I typed adb devices. Now my tablet is listed as 20110301 recovery.

I can simply use only adb pull, adb push, and reboot commands. But I cant access adb shell to unlock my tablet: it simply says exec '/system/bin/sh' failed: No such file or directory (2). What can I do? On stock recveries the adb utility only registers that the device is connected when you invoke the sideload utility which gives an error when you try applying adb shell or any other thing.it only accepts push commands to the device. Adb also works when your phone is on which is a problem when you have boot issues and can only get to recovery. Best Case Scenario: Requisites 1.Flash a Custom recovery via ODIN: the stock will prevent certain commands; TWRP or CWM are the Industries (Root) finest and give a provision to initialise the sideload utility or even better yet, Backup to an external SD Card. Press Home+Power+Volume_UP to get to recovery:voila, your adb commands will work as required not to mention factory resets and wipes.

I was using aufs. Looking at the tree it failed at around 42 layers, but I could have been overfitting (as I read about the 42 layer limit being fixed).