Database Info

[Q] adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"

Hey,
Ok so a little backstory before my problem: So I was in the middle of putting a new ROM on my captivate. I had one before but i wanted to change so I put the rom in update.zip and installed it will clockworkmod recovery. It installed fine I think but then when I tried to boot it gets stuck on the boot screen. So i tried to boot in recovery mode. I geld down both the volume buttons and the power button until it reboots twice, then I let go of the power button. but it still gets stuck on the boot screen and does not go into recovery mode. So i plugged it into my computer and using
Code:
adb devices
it shows up under recovery mode. So far so good. I can use the
Code:
adb reboot
and
Code:
adb push
commands fine. but when i try to use
Code:
adb shell
it says
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
So i can not reflash the recovery image. I read that I just needed to mount the /system file. But i do not know how to do this. the "mount" command does not work with adb. I would appreciate anything to help me to either reflash the rom or restore to factory or anything where i can work off of. thanks

I have exactly the same problem.
Did you get to a solution to this?
Good luck, dude.

Is there a solution to this without using a Motorola Factory cable? I don't have the resources to make one and I don't have money to buy one.

I'm not sure putting the rom into "update.zip" was the right choice.
adb shell could fail because the partition is not mounted, the sh binary is not installed, or not at the correct location
If you can still get the captivate into download mode, you could use odin/heimdall to flash a working ROM.

First of all...thanks to everyone that has EVER posted in the XDA forums! I've spent days reading them and I came across one that had a suggested solution for my problem. So let's start...
1) Bricked
2) ADB is finally working again...so..not a problem any longer
(Don't ask me how I got it to work again....I have no idea. System was wiped while using TWRP from a bootloop)
3) Now...with system wiped I have no '/system/bin/sh'
4)adb shell will not work because of this. adb root does not work because of production model. adb remount is not permitted.
Now....I came across a thread that suggest using r2.6.2.kindlefire.boot.insecure.img and zergRush. I have the zergRush file, but I need the r2.6.2.kindlefire.boot.insecure.img to push with adb.
Does anyone know where I can get the r2.6.2 at? Filesonic is disabled and Multiupload will not return page.
Link I came across: addictivetips /mobile/gain-root-adb-access-with-insecure-boot-image-for-kindle-fire/

[Q] Simple adb question (or perhaps not?) Permission Denied

Hi all--in need of some help here--have been crusing the forums for three days and still hitting a brick wall...
Have a rooted (and minimally modded) Atrix 4g in serious need of a hard reset and all the pain that comes with as nearly every app force closes on startup.
Hoping to backup some of my data (contacts, SMS, etc), but unable to do so my usual way (an app, root explorer, or the like), so I'm attempting to use ADB pull to grab the .db files. I'm relatively comfortable with linux, but running into a problem with ro/rw permissions (I think).
have tried the following:
adb pull /data/...../mmssms.db (yields Permission Denied)
# cp /data/....mmssms.db (appears to copy, but no file in destination, and can't copy out of shell)
have been able to remount /system as rw, but not /data where the files are located.
Anybody have suggestions? I'd be most apprecative!

Copy the the files as superuser to your sdcard first and adb pull them from there.

Unfortunately, the whole reason I'm needing to reset is that every app (incl superuser accesses) force closes on start--no chance to move through the phone itself. Since the .db files are not in the usb-accessible file structure I'm thinking that ADB is the only way to access.
Does that make sense?

Hi, OP here--anybody else have a suggestion? Getting a little desperate here... Any thoughts would really be appreciated!

im assuming your accessing ADB via recovery?
You should be able to use su without superuser.apk's permission in that case - however, theoretically, you should not need to use su in recovery anyway.
you can try running
Code:
adb shell ls -l /data/data/*tele*/databases/mmssms.db
and see what you get permissions wise, maybe a chmod could fix it?
Otherwise you could try
Code:
adb shell mount -o remount,rw /data
Another alternative to cp and adb pull is cat
Code:
adb shell cat /path/to/mmssms.db > /path/to/destination-file.db
might copy remote mmssms.db to a local file, while
Code:
adb shell
cat /path/to/mmssms.db > /path/to/destination-file.db
exit
would copy remote to remote
Is /data mounted at all?
This is strange, you should have read access to everything, especially in recovery.
What phone and what recovery?
Its not something as simple as geting the URIs the wrong war round ('cmd local remote' vs 'cmd remote local')?

So, still tinkering... Will give it one last try before I call it quits and just wipe the bloody thing. So, your thoughts were spot on--its probably me missing something.
Quick data dump on progress to data:
Phone: Rooted Motorola Atrix running 2.2
no trouble accessing shell or via ADB
/data is mounted, though only in Read Only mode--can't seem to change, have tried several ways in various modes (shell, su, etc)
Permissions for mmssms.db are: -rw-rw---- radio radio
chmod 777 of the file yields: "Read-only file system," which makes sense since I can't seem to change /data... to rw
Tried to remount rw:
adb shell mount -o remount,rw /data
and
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p11 /system (for systeem
but get "Operation not permitted" in both cases.... UGH!
Hadn't thought of cat--great idea. Still no real joy however.
I seem to have managed a copy to /system, but can't seem to get it off the device or onto the SD card.
Thanks much for your help so far. Any final thoughts?

SO CLOSE!!!! (and yet...)
crags said:
Hadn't thought of cat--great idea. Still no real joy however.
I seem to have managed a copy to /system, but can't seem to get it off the device or onto the SD card.
Click to expand...
Click to collapse
SO FRUSTRATING!!!! so close, but not quite there--HELP!!!
As noted at the end above, have been able to copy the mmssms.db file to /system/ after remounting as RW
Can't seem to copy or pull off the device--still getting "Permission Denied" no matter which course I try!?!?!

It sounds as if your doing this while booted into the ROM, and (maybe) without su (root)?
su-ing might help, just type su and hit return to enter a root shell
alternatively, going in through recovery ('adb shell reboot recovery') might help as most recoveries ignore permission rules - make sure to mount the partitions your using though.
It almost sounds like the sdcard has no write permissions - you can get the NAND partitions to mount rw, but cant copy to the sdcard.
On my Desire, there is (at least) two mount points: /sdcard and /mnt/sdcard - maybe on your phone only one of your mount points has write permissions?
Otherwise i suggest going in via recovery. You can still use adb (will have to manually mount - 'mount /system' 'mount /date' and 'mount /sdcard' usually work, otherwise use the menu item in recovery )
When in recovery, and after mounting partitions/card, try adb pull, cp /sdcard and cat > sdcard (and if possible cat > computer) plus anything else i forgot (quite tired )
if these dont work something is messed up somewhere in the ROM, or likely kernel and so without ideas a reflash would be the only real solution :/
I did have a bare-minimum+apps recovery script (attached) which might be worth a read to see if your forgetting something obvious - it works on my desire

[Q] Have I bricked the thing?

So I went to replace libaudioflinger.so in /system/lib with one I'd built myself, but unfortunately something obviously went wrong and when I rebooted the device, it just hangs on the loading screen.
The good thing is that the original file is in /sdcard named '_libaudioflinger.so_', and I can connect via adb there. If i run 'su' which gives me some sort of root access, but when I try 'mount -o remount rw /system', it shows up as "Operation not permitted". If I'm able to get that filesystem mounted, I just need to run "mv /sdcard/_libaudioflinger.so_ /system/lib/libaudioflinger.so", anybody any ideas how I might be able to recover this?

seaders said:
So I went to replace libaudioflinger.so in /system/lib with one I'd built myself, but unfortunately something obviously went wrong and when I rebooted the device, it just hangs on the loading screen.
The good thing is that the original file is in /sdcard named '_libaudioflinger.so_', and I can connect via adb there. If i run 'su' which gives me some sort of root access, but when I try 'mount -o remount rw /system', it shows up as "Operation not permitted". If I'm able to get that filesystem mounted, I just need to run "mv /sdcard/_libaudioflinger.so_ /system/lib/libaudioflinger.so", anybody any ideas how I might be able to recover this?
Click to expand...
Click to collapse
Hopped on #android-root and they got me all sorted. Basically just had some sort of a bad root/su which wasn't giving me the correct access. All back up and running 100% now, though.

If it boots into the bootloader you can always flash the factory image
Sent from my Nexus 5 using XDA Free mobile app

You can't brick a device by swapping system files.
Sent from my Nexus 5 using Tapatalk

[Completed] [Q] Can't get into recovery; very strange flickering issue

Hey everyone, I have this very strange issue
The other day I made a nandroid backup because I wanted to mess around with some stuff I wasn't sure was going to work. I then restored the backup, and tada, bootloop. I was stuck on the boot animation. Tried a deleting data/dalvik/cache from recovery (CWM 6.0.4.7), installing rom again, but nothing worked.
Now, what I did may or may not have been smart. I wiped everything using "wipe userdata" in the adb shell. Everything gone. Now I want to put on a working rom again, but I can't. Two problems:
1. My CWM recovery is doing this . Not only when I boot into it trough bootloader, but, maybe this is because I don't have a working rom, it also seems to go into it after my bootloop attempts to boot twice, as seen here.
I have no idea what's happening and why and how. It just keeps flashing like this and I can't access the menu. I tried reflashing, flashing the touch version, flashing TWRP which doesn't have default adb access, and flashing it once again but same result. So I can't choose a rom to flash. How do I fix this?
2. I can still push files to /data/media/ and /sdcard/, but after that I have no way to install them. No tutorial I found seemed to work, e.g this one from xda says I have to mount /data/ but when I do that I get
> C:\sdk\platform-tools>adb shell
~ # mount data
mount data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
And I've also done this one which states the rom should install, but it doesn't. The cd and push are successful, but I can't do anything with it. I also think my /sdcard/ got unmounted at some point, but I was able to push a file to it so not sure here.
Does anyone know how to fix this. I have no idea what to do, pretty hopeless at this point. Thanks so so much if you have any tips
-Josh

Duplicate.
http://forum.xda-developers.com/general/xda-assist/bootloop-nandroid-restore-tried-t3153174

[Solved] Stuck on boot animation Suddenly. Solved without wiping data.

Symptoms:
Phone stucks at boot animation screen (4 color balls rolling)
adb devices command shows device is represent.
adb logcat shows no fatal error, no obvious cause
kernel message shows no fatal error
Cause:
Content inside /data/system/sync is corrupted(?)
Fix:
Rename or remove folder /data/system/sync
Below is the full story and how I figure it out:
3 days ago when I woke up, i find that my phone was rebooting and the screen showing boot animation. After waiting a long time, I find that the phone was stuck on boot animation. I can use adb shell to connect the phone and adb logcat to retrieve the log. The log shows nothing special or fatal, just some minor errors.
My phone is rooted, unlooked and relocked bootloader, CWM Recovery 6.0.4.4
The apps I installed that have root access included, but not limited to:
Xposed Framework​Android Tuner aka 3C Toolbox​GravityBox​iFont​Xprivacy​Greenify​AFWall+​BusyBox​SuperSu​com.avast.android.mobilesecurity​com.avast.android.antitheft (Root install)​
After Googled a few hours, 99.9% of the result tell you factory reset your phone is the fix, and i am not satisfied with that. So I used CWM recovery to made a complete backup, and tinkering with the files and system.
At first I cleared cache and dalvik-cache in recovery as this is easiest, but no luck.
Then I suspect this might be a flash memory chip problem , so I boot into recovery, use adb shell to connect console, however, adb shows that device unauthorized, so I do a factory reset and reboot recovery, then adb shell again and success, and in recovery, restore /data backup. Then I use command
Code:
%path to android platform tools folder%> adb push adbkey.pub /data/misc adb/adb_keys
, then adb is authorized after reboots.
To check if the flash memory is okay, i used the command:
Code:
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/system
The result seems fine, and no signs of hardware failure.
After reading logcat, the system seems nearly finished the booting process, and stucked at end of System service, and never signal Boot_Completed. Using Android Device Monitor, system_process main thread is still running and doing something unknown.
At this point, i think kernel and /system should be normal.
Then I suspect that the apps i installed might be the cause, I renamed the folders like:
Code:
mv /data/data /data/data.old
mv /sdcard/Android /sdcard/Android.old
mv /data/app /data/app.old
to see if the OS can boot normally, but no luck.
I also renamed many other app folders and reboot, but none of this can solve the bootloop problem.
Then I renamed /data/system and reboot, from the logcat, i can see the system is regenerating the content inside the system, and I waited for a moment, the OS booted successfully with many "xxx process stopped" error message on the screen. So at this moment I realized that content in /data/system might be the root of all evil. As Home screen is not usable with a lot of process stopped messages, I used this command to start the apps i want.
Code:
adb shell monkey -p com.yourpackage.name -c android.intent.category.LAUNCHER 1
(Need to use some game points )
Next I used command
Code:
find /data/system -mtime -3
to find out which files were altered within last 3 days. I get a list of files and folder and then I rename the folders one by one and reboot. Finally, /data/system/sync folder is confirmed as the cause of the problem.
I restored the full backup in recovery, and renamed the /data/system/sync folder to /data/system/sync.old and reboot. Phone boots normally, everything seems fine.
I don't know what, why, how exactly causing the boot problem, but the problem is solved anyway. Hope this information can help someone.
I used 40+ hrs to figure it out, and another 2+ hrs to summarize and write this.
fxxk.

Nice work!
Sent from my Nexus 5 using Tapatalk

Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, what should I do for this, Thank you in advance for your Help.

Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help

TUPANGPUTi23 said:
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
Click to expand...
Click to collapse
Probably best to ask in your devices forums. This is for the Nexus 5, not the Samsun J2 Core.