Database Users

- exec '/system/bin/sh' failed: No such file or directory (2) -

I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.

rydinsmoothx said:
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
Click to expand...
Click to collapse
Not gonna happen unless you can get into recovery or have the special usb cable to throw your device into fastboot (search the unbricking thread for more information on that). If you get lucky and can fix it + revert to stock, I would not install cm7 again until doing so is more noob friendly and forgiving.
The issues people are having with installing cm7 and severely screwing up their kindle are pretty epidemic due to the issues with recovery for those that don't prepare ahead of time for the possibility of disaster. The maintainer should really either close it out for now to the public or make the disclaimer much larger.

I have the same error. This is end. Only Factory Cable can help you but even with this cable I'm not sure what you can restore it.

i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?

rydinsmoothx said:
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
Click to expand...
Click to collapse
Operate how? Also, please don't double post in 2 threads.

My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.

rydinsmoothx said:
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
Click to expand...
Click to collapse
Could be a bit more explicit. Boots as in "yay, i see a logo and can't use my device beyond a paperweight that displays the cm7 logo" or boots as in "yay, i can use my device like normal and it's not bricked or malfunctioning"
Anyways, if you actually have root privileges and can mount system in read/write, get the sh binary out of the CM7 download by unzipping it or whatever and copy it over, making sure to match the owner/group and permissions that the other things in the /system/bin directory have. Since I'm guessing you're not command line savvy, I recommend doing this in root explorer or buying it if you do not have it.
Also, many of us do not own kindles and a larger % are also not running cm7 on their kindle so saying "i ran some random script that I won't say what it does and where I found it" does not help your situation either as far as getting a helpful answer.

Can you type ADB DEVICES at your command line and get a device? What about fastboot? Can you get devices to show there while at the command line?If yes, I am sure you can flash the CWM recovery to get ADB, then follow the steps to get back to stock...Dont blame me though if it doesnt work

I got the script script from someone in the cm7 thread, its supposed to opitimize the ram usage thus making the rom more smooth. He said it worked for him so I gave it a shot. I think it unrooted my kindle because I can't gain root access with root explorer. My devices shows up in adb devices but since I can't use adb shell I can't enable the fast boot.

[Q] How to backup Nexus 4 using adb?

Hi,
Thanks in advance for reading this.
Details:
Phone: Google Nexus 4
OS: Android 4.4.2
Android SDK OS: Windows 7x64 SP1
adb version: 1.0.31
Eventually I hope to unlock the bootloader and then root my phone, but right now I'm struggling with making a backup and until I get that accomplished I don't feel comfortable going any further. I hope that someone here more knowledgeable can point out what I'm doing wrong.
Long story short, I fully charged the Nexus 4, updated the existing Android SDK so I'm using the latest version of adb and installed the Google USB drivers by choosing to install "legacy" devices and selecting all three drivers (one at a time). I then removed the fake legacy devices and chose to leave the drivers installed.
I then connected the Nexus 4 in USB debugging mode and it was detected via
Code:
adb devices
. I read here about using
Code:
adb pull /sdcard/ /sdcard/
and translated that to:
Code:
adb pull /sdcard/ .\sdcard
since I am on a Windows box. That worked fine until a subfolder within /sdcard/Android for the Amazon Kindle app was encountered. The copy attempt was aborted due to a filename that I'm guessing the NTFS filesystem didn't care for.
I figured I would just move past that and come back to it later; maybe use ES File Explorer to create a zip file or copy/paste specific folders via Windows Explorer interface.
I then moved on to running adb backup and ran:
Code:
adb backup -apk -shared -all -f .\nexus4-backup-010114.ab
After a long while the command appeared to complete and control was returned to the command prompt. The resulting file was about 1 GB in size and no errors were shown on the phone or on the command prompt by adb.
Not one to trust just one run, I tried it a second time and the process hung. I cancelled the adb call and ran
Code:
adb reboot
to reboot the phone. I tried again and the process hung yet again.
I've tried all of the following and the process seem to hang (waited several hours one time):
*
Code:
adb backup -apk -shared -all -f .\nexus4-backup-010114.ab
*
Code:
adb backup -apk -shared -all -nosystem -f .\nexus4-backup-010114.ab
*
Code:
adb backup -apk -noshared -all -nosystem -f .\nexus4-backup-010114.ab
and based on the suggestion here I tried with and without an encryption password. The first attempt was without a password and later attempts was with providing a password at the time of the backup (when prompted on the phone).
Before posting this, I tried setting a password within the Developer options on the phone and had the same luck with running:
Code:
adb backup -apk -shared -all -nosystem -f .\nexus4-backup-010214.ab
By this point I'm ready to throw the phone against the wall (even if it doesn't deserve it). Any help would be appreciated.
Thanks!

I ended up giving up on this as I've spent three days and didn't want to wait any longer. I backed up the contents of /sdcard/ into a zip file (using ES File Explorer) and will restore contents manually as necessary.

I've since unlocked my phone, restored quite a bit of content, taken two Nandroid backups (before and after rooting the phone) and loaded all currently available versions of stock Android for the Nexus 4. What follows is some of my notes that I took while going through the process.
---
After unlocking my phone I restored contents from the zip file and a surprising amount of content was restored, but unfortunately not stuff like bookmarks and other personal settings. As I read before and after unlocking my phone a lot of that content is kept in /data where only root can get to it. Thankfully not all app developers follow that recommendation and I was able to retrieve some of my content.
However after I unlocked the bootloader and rooted the phone I was able to make a backup by running:
Code:
adb backup -apk -shared -all -f nexus4-backup-010414.ab
I'm not sure if it was just unlocking the bootloader that allowed it to work or that + rooting the phone or maybe something else entirely. Whatever the case that command completed successfully. I'm going to run several more backups with differing options and then will flash the phone back to stock and try restoring from that.
Just before that I'll try making a backup via TWRP (haven't really looked into the details yet) and also follow the codemink.com/backup-or-restore-android-through-adb/ guide to try and make a backup of the entire phone (OS, Recovery, etc).
I'm hoping I don't have to spend all of my time restoring the phone from scratch if this doesn't work, but it's worth trying this to find a reliable solution.
---
I picked another tool from the tool chest and tried using the Nexus Root Toolkit (NRT) v1.8.0 since others have recommended it. I know it's not good to rely on toolkits, but I wanted to see what it was capable of. It rebooted the phone into bootloader mode and then booted a custom recovery (TWRP) so it could run a Nandroid backup. It did and ended up with a 2.30 GB backup located at /sdcard/TWRP/BACKUPS/SerialNumberOfYourPhone/. From what I can tell the NRT automates what you can do manually, only when it finished the process and attempted to copy the backup to the PC it only grabbed about 40 MB worth and reported a successful backup.
Since I had been watching the process from the phone I saw that it reported the size of the data it was backing up as 2750 MB, so I knew that the NRT was wrong. It asked if I wanted to nuke the backup since it copied it over, and I told it No since I knew it was wrong.
* If I haven't mentioned it yet, I used Windows 7x64 for all steps.
---
I followed the directions on the www .android.gs/root-google-nexus-4-on-android-4-4-kitkat-krt16o-rom-using-twrp/ page and didn't have any problems. Well, the one problem I did have was not freaking out when my Nexus wasn't seen by either
Code:
adb devices
or
Code:
fastboot devices
.
I frequently made the mistake when experimenting on my own by using one or the other when it wasn't appropriate. I ended up learning that fastboot is used when interacting with the bootloader and adb is used when the phone is booted into the full Android OS or in Recovery mode.
After I had TWRP installed, the Android 4.4.2 installation rooted (again using the www .android.gs/root-google-nexus-4-on-android-4-4-kitkat-krt16o-rom-using-twrp/ page and my phone setup the way I wanted it, I took a final Nandroid backup using TWRP and then booted the phone back into the full OS.
I proceeded to copy the /sdcard/TWRP backup files to the PC as a precaution. I ended up using the developers.google.com/android/nexus/images#occam official factory images for the Nexus 4 to flash Android 4.2.2 all the way up to Android 4.4.2 "just to do it". Restoring my TWRP backup first required me to re-flash TWRP and then copy the TWRP backup folder back to /sdcard/TWRP. I booted back into Recovery mode via adb reboot recovery and used the menu system to drill down to the backup I was interested in and restore it. I then rebooted when prompted and my phone was restored to where I last made a Nandroid backup.
I took extensive pictures using a second phone and kept all output so I could have something to refer to if (uhm, when) I try this again in the future.
What I learned at the end is that I could have flashed just the OS by modifying the flash-all.bat file to remove the -w switch from the final fastboot command in the file. Here is what it looks like by default for the file included in the Android 4.2.2 factory image tarball:
Code:
fastboot -w update image-occam-jdq39.zip
and after removing the switch:
Code:
fastboot update image-occam-jdq39.zip
Using that approach I would likely be able to safely keep the /sdcard/TWRP files on the phone during the flashing of stock roms. I hope this helps someone. Unfortunately I never did find a way to use adb to make a successful backup prior to unlocking the bootloader, so if I had it to do all over again I would have unlocked the bootloader when I first received it. Lesson learned!

Temporary Root with ADB - Note 4 N910f - 5.1.1 - it is possible ?

Hello,
is it possible temporary root with ADB commands?
I need a root in order to restore data to a folder root / data / (copy files - stored position in the games that I have previously backup in Titanium Backup)
Will this work?
1. write in command line adb root
2. the answer will be:
*deamon not running. starting it now*
*deamon started successfully
*adbd is already running as root
3. write in command line adb remount
the answer will be: remount succeeded
A temporary root should be ready ?

Hmm to be honest since the first Android phone G1 I have rooted all my phones the very same day I got them and have never looked back at the useless ****ty stock roms.
With that said I would just try and push the files to there location but do bear in mind if they don't have the right permissions to run then that could open the doors to a whole other ball game of fc and what ever.
So before you copy those files I would look into a way of giving the permissions they need to run from adb and if it's possible.
Sent from my SM-N920C using Tapatalk

Issues with adb install commands with the Nexus 10 Factory Image

Hi,
I'm having a series of issues with my Nexus 10... not sure what I am doing wrong.
I downloaded the 5.1.1 (LMY49J) factory image for the Nexus 10 from https://developers.google.com/android/nexus/images and flashed it using the flash-all.zip, it completed fine. I booted the ROM and enabled adb via settings.
As soon as I run a command such as adb install apkfile.apk or adb install -r apkfile.apk it throws up /system/bin/pm[6]: app_process: not found
I've checked the checksum of the factory image and it matches so it's not an issue with my download becoming corrupt
I installed the latest version of twrp via fastboot and tried to install the same way as above, but still it doesn't work regardless of if I mount or unmount the system directory.
I had a look in the system directory via twrp's file manager and it has a bin folder but there are no files anywhere inside the system folder...
If I do the exact same thing with my Nexus 4 there are plenty of files in the folder & the adb install function works fine.
Any ideas?

Hyflex said:
Hi,
I'm having a series of issues with my Nexus 10... not sure what I am doing wrong.
I downloaded the 5.1.1 (LMY49J) factory image for the Nexus 10 from https://developers.google.com/android/nexus/images and flashed it using the flash-all.zip, it completed fine. I booted the ROM and enabled adb via settings.
As soon as I run a command such as adb install apkfile.apk or adb install -r apkfile.apk it throws up /system/bin/pm[6]: app_process: not found
I've checked the checksum of the factory image and it matches so it's not an issue with my download becoming corrupt
I installed the latest version of twrp via fastboot and tried to install the same way as above, but still it doesn't work regardless of if I mount or unmount the system directory.
I had a look in the system directory via twrp's file manager and it has a bin folder but there are no files anywhere inside the system folder...
If I do the exact same thing with my Nexus 4 there are plenty of files in the folder & the adb install function works fine.
Any ideas?
Click to expand...
Click to collapse
it looks like you are omitting the path to the file you want to install. For example: ~/Downloads/apkfile.apk

garnet&gold said:
it looks like you are omitting the path to the file you want to install. For example: ~/Downloads/apkfile.apk
Click to expand...
Click to collapse
Nope, it's not that. the location is correct. I'm actually doing it from a python script which fills it all in automatically but even just trying to install them manually via command prompt isn't working as explained.

in the Nexus Root Toolkit is a ADB installation included ( if you go down the installation directory and find adb and fastboot)
this installation should have the correct drivers for all Nexus devices and could do a clean install of the stockv rom, unlock the device and rooting the device including installation of a different recovery like TWRP
You can find it at http://www.wugfresh.com/
Nexus Root Toolkit v2.1.9
Posted on September 19, 2016

guidol said:
in the Nexus Root Toolkit is a ADB installation included ( if you go down the installation directory and find adb and fastboot)
this installation should have the correct drivers for all Nexus devices and could do a clean install of the stockv rom, unlock the device and rooting the device including installation of a different recovery like TWRP
You can find it at http://www.wugfresh.com/
Nexus Root Toolkit v2.1.9
Posted on September 19, 2016
Click to expand...
Click to collapse
Nothing to do with ADB directly, it's something to do with the device/firmware as ADB works on my nexus 4 just fine and worked on my Nexus 10 before returning to stock. also WUG thinks my ADB is fine too.

How do I adb pull root directories (like "/" or "/system"?)

Hi there, I'm trying to pull root directories like /system and /data without any luck. My purpose it to have them on my PC as a backup, and be able to browse them to pull out apps and pieces of data as necessary if it ever becomes necessary.
Device: Nexus 6P (North American version)
ROM: Stock 6.0.1 Rooted, using Wugfresh Nexus Root Toolkit and SuperSU
PC OS: Windows 7 PC (64 bit)
Adb is working properly and I can easily pull non-root directories like "/sdcard" and so on. I'd like to be able to backup the entire root directory ("/") or at least the child directories (like "/system" and "/data", etc.) Unfortunately, when I try
Code:
adb pull -p "/system" "C:\somewhere"
it skips a bunch of files, so I need to come up with a better method.
I've tried
Code:
adb root
and it tells me it's already running in root mode.
I try
Code:
adb remount
and it does this properly, but doesn't change the effects of all the commands I've tried.
When I run
Code:
adb shell
it enters shell and gives me # by default, so seemingly it is giving me su permission by default?
*** Oddly, when I enter "su" while in shell, it tells me "/sbin/sh: su: not found" which seems odd to me. I think it's possibly that SuperSU is installed as systemless root, or there's something else screwy here, so I guess I'm not sure how to proceed. Still, if that were case, why would adb already be running as root, and why would shell automatically give me the #?
Any help is appreciated!!
Thanks!

@Heisenberg I figured I'd tag you because of your extensive experience with the Nexus 6P in particular (and rooting.) Not sure if you may be able to shed some light on the issue here?