Last night I put my phone into the Clockwork Custom Recovery to install CM. However, after restarting, my phone only boots up til the HTC logo. I tried going back into custom recovery to restore to stock but whenever I get up to the "adb shell" portion in command prompt i just get this: '/system/bin/sh' failed: no such file or directory (2).
has this happened to anyone else. is there a fix or do i have to send my phone in?
thanks for any help.
any help at all would be appreciated. to clarify i can get into unrEVOked but I can't go into adb shell.
Related
Hey, my brother just got a Defy, and I managed to root using z4root and install tenfar's recovery, but when I boot into the recovery, both laptop running ubuntu and my pc running w7 with motorola's dev usb drivers just won't recognize it.
I've tried killing and starting adb as root, running cmd as admin in w7 and nothing.
When I type "adb devices" it shows a blank table.
I've also tried to enable usb-ms on tenfar's recovery, and they won't recognize the sd either when in recovery mode.
Any idea?
P.S, in normal boot, both computers recognize the defy with no problem at all
bump, no one knows?
Errrrr... why are you trying to run ADB commands to it while you're in the bootstrap recovery?
If you're trying to run ADB commands, you probably want the phone booted into Android, and (usually) with root and USB debugging enabled.
The bootstrap recovery is pretty much just for making/flashing Nandroid backups.
It's also required for running BiDi correction scripts, I need to extract framework.jar from the phone, run a correction script on it, and then push back the altered jar to the phone, and for this I must be in recovery mode.
having the same problem:there is no recovery mode
Hi,
I instaled cm9 on my defy. Now when I try to turn it on, can't. Also cant open recovery, cause there is error: "busybox was not created in footfs". And when I open recoveri, it says: "E:Error in /system/bootmenu/script/recovery.sh (result: no such file or directory) Could someone please help me?
This is a followup to this thread.
I got some help at androidcentral.com and now have Fastboot driver installed. I don't have access to ADB mode or the main Android OS. What can I do now to get my phone back to working. My phone can also enter Download mode if that's useful.
I can enter Recovery from Fastboot but then what do I do?
Edit:
Run this command in ADB.
adb backup -apk -noshared -nosystem -all -f C:\backup.ab
Your phone will ask for a password...
Don't put one in.
Once it's finished...
It will say backup complete.
Or your phone might just boot straight up.
Then navigate to recovery.
And factory reset.
Does your phone now boot?
(If not, stop here, and hit me again)
GOOD!
Now get back in fastboot and run:
adb restore C:\backup.ab
This will give you your applications back.
This MIGHT brick you again...but I doubt it.
If so...simply factory reset.
Thanks for the response.
Can I use ADB from recovery mode because I don't have access to the main OS and It was my understanding that you access ADB from the main OS?
If so, I'm using GNex TOOLKIT V5.6. Would I need to boot to CWM Recovery to use ADB or is the stock recovery ok?
I tried using the command in Fastboot and I get the error "adb: unable to connect for backup"
In GNex TOOLKIT at the top is says:
FASTBOOT MODE
List of devices attached
(the phones serial) fastboot
ADB MODE
List of devices attached
(blank space)
Click to expand...
Click to collapse
When i try "adb devices" in the command prompt, I also get "List of devices attached" with a blank line under it.
OK, I gave up on trying to access my data and attempted to do a restore with the toolkit. I had to unlock the bootloader as the first step and after that the system would boot again.
It would be nice if I could have figured out how to reflash the stock bootloader as a first step but I couldn't figure hot if you can or how.
Anyway, I should have unlocked it from day one. If i had, I would have has access to ADB from CWM recovery and would have been able to backup my stuff and access files even with it in the unbootable state it was in.
I guess not unlocking the bootloader was a mistake I need to learn from.
Jubakuba, thanks for trying to help me out.
Thank you in advance:
I attempted to flash CM10 yesterday and things went astray. I flashed the Rom as usual, then V13 Kernel, then Gapps, then rebooted. Rom didn't boot and when I go into recovery I get the following errors:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So then I attempted to re-flash back to an older stable Rom and I get the error:
E:Error in /sdcard/rom_name_here.zip
(Status 1)
Installation Aborted
When I try to wipe data/factory reset it takes about 30 minutes while hanging on formatting data and cache, but I still get the Can't mount/open errors after it's finished.
When I try to flash a new kernel I get this error:
Installing Boot Image...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/kernel.zip
(Status 7)
Installation aborted.
I am able to get my Hboot USB PLUG working and recognized by my device manager, but adb commands tell me *device not connected. Is there a way to do these commands in OSX? Windows is frustrating me.
I'm not really sure what to do, any help would be greatly appreciated. Thank you!
My phone's info:
VIVO_W XB SHIP S-OFF RL
HBOOT - 6.13.1002
RADIO - 1.09.01.0622
Can you wipe anything else? Dalvik cache
Sent from my vivow using xda premium
Kinz1980 said:
Can you wipe anything else? Dalvik cache
Sent from my vivow using xda premium
Click to expand...
Click to collapse
When I Wipe Dalvik Cache the recovery menu disappears for a few seconds, then re-appears with the same option. No dialog came up saying anything was wiped or even tried
There is a way to get rid of a brick from HBOOT by re-installing the PG32IMG and then re-rooting.
To get rid of the brick: http://www.youtube.com/watch?v=YEIVtsrqaDo&feature=plcp
Then, how to re-root: http://www.youtube.com/watch?v=Wag3W3Hq2u4&feature=plcp
EVoorhees said:
There is a way to get rid of a brick from HBOOT by re-installing the PG32IMG and then re-rooting.
To get rid of the brick: http://www.youtube.com/watch?v=YEIVtsrqaDo&feature=plcp
Then, how to re-root: http://www.youtube.com/watch?v=Wag3W3Hq2u4&feature=plcp
Click to expand...
Click to collapse
That you VERY much! I am currently updating the recovery, it seems hung up but hopefully it's just taking a while. Will keep you posted.
EDIT 1: I'm still stuck on step [2] RECOVERY - Updating, things are looking grim.
EDIT 2: So I can't get past step 2 of 9 updating via the PG32IMG.zip It is just hanging on Updating. Anyone have any other solutions?
Robinette said:
That you VERY much! I am currently updating the recovery, it seems hung up but hopefully it's just taking a while. Will keep you posted.
EDIT 1: I'm still stuck on step [2] RECOVERY - Updating, things are looking grim.
EDIT 2: So I can't get past step 2 of 9 updating via the PG32IMG.zip It is just hanging on Updating. Anyone have any other solutions?
Click to expand...
Click to collapse
I think that may be a hardware brick.
You may have to take it and get it replaced from VZW. But, they don't sell the DINC2 anymore, so I wouldn't know what they would do. If you got the phone about a year or two ago, Verizon lets you upgrade about 4 months in advance I believe.
But, I have never experienced a brick myself; so I could be wrong.
have you tried flashing a recovery via fastboot?
sjpritch25 said:
have you tried flashing a recovery via fastboot?
Click to expand...
Click to collapse
I tried on Windows 7 but couldn't get ADB to recognize my device. I got it to work ONE time where the phone had a black screen and a blue REVELUTIONARY written in the middle, but for some reason I can never get it to get there again.
So now I'm going to try and get it to work on OS X. Will keep you posted...
Edit: Finally got ADB working on OS X and I'm able to recognize my old Incredible, now going to try and get it to recognize the Incredible 2...wish me luck.
Edit 2: I was able to get ADB commands working on my Incredible 2. However when I get to the step enter the command "./adb shell /data/local/tmp/zergRush" I get the error "/sbin/sh: /data/local/tmp/zergRush: not found" even though I know the zergRush file lives in that folder. I think it may be a permissions issue with the computer I'm on at work. This is such a nightmare. I have to troubleshoot every step of trying to fix this phone. Drain.
So I have still yet to fix my phone. I'm much closer, but running into new issues. ADB works and recognizes my phone in both 'recovery' and Downgrade VivoW with hboot 0.98" guide.
While the phone is sitting at the white HTC screen and recognized as 'device' by adb, I get the following errors:
adb shell rm -r /data/local/tmp/* = failed to copy 'tacoroot.sh' to '/data/local/': Is a directory
adb push zergRush /data/local/tmp/zergRush = failed to copy 'zergRush' to '/data/local/tmp/zergRush': No such file or directory
and while the phone is in 'recovery' mode I'm able to push zergRush and misc_version, set their permissions, but then:
adb shell /data/local/tmp/zergRush = /sbin/sh: /data/local/tmp/zergRush: not found
Even though:
adb shell ls /data/local/tmp = misc_version zergRush
Does this command not work while in recovery? I'm not able to get even past the first step in 'device' mode. The /sbin/sh thing confuses me.
Please help!
Robinette said:
So I have still yet to fix my phone. I'm much closer, but running into new issues. ADB works and recognizes my phone in both 'recovery' and Downgrade VivoW with hboot 0.98" guide.
While the phone is sitting at the white HTC screen and recognized as 'device' by adb, I get the following errors:
adb shell rm -r /data/local/tmp/* = failed to copy 'tacoroot.sh' to '/data/local/': Is a directory
adb push zergRush /data/local/tmp/zergRush = failed to copy 'zergRush' to '/data/local/tmp/zergRush': No such file or directory
and while the phone is in 'recovery' mode I'm able to push zergRush and misc_version, set their permissions, but then:
adb shell /data/local/tmp/zergRush = /sbin/sh: /data/local/tmp/zergRush: not found
Even though:
adb shell ls /data/local/tmp = misc_version zergRush
Does this command not work while in recovery? I'm not able to get even past the first step in 'device' mode. The /sbin/sh thing confuses me.
Please help!
Click to expand...
Click to collapse
It won't work in recovery because the partitions aren't mounted. Try reflashing the ROM and get it to boot. If recovery won't work, flash back to stock or try reflashing the recovery.
sjpritch25 said:
have you tried flashing a recovery via fastboot?
Click to expand...
Click to collapse
prototype7 said:
It won't work in recovery because the partitions aren't mounted. Try reflashing the ROM and get it to boot. If recovery won't work, flash back to stock or try reflashing the recovery.
Click to expand...
Click to collapse
Thanks for the suggestions. I am able to get the phone recognized and responsive with fastboot, but it still doesn't want to work. When I attempted to re-flash recovery in fastboot, it completes the first step just fine and then hangs on "'writing' ..." as soon as that happens terminal freezes as does my phone, resulting in me having to battery pull and force quit terminal. I've waited and waited but it never finishes, and I think it's supposed to happen very fast anyway.
I read on another forum to extract the system.img, boot.img, and recovery.img from the PG32IMG.zip and manually install them via fastboot. I tried this as well but again I get errors and freezes immediately after "fastboot flash system system.img"
I also tried "fastboot erase cache" and again, it hangs and freezes both my phone and terminal.
I'm pretty sure my phone is a goner. If anyone has another suggestion please let me know. I don't think there are many things I haven't tried, except the alternative methods (software?) of running commands other than fastboot and recovery. I hope it's not just something dumb on my end like the usb port or permissions.
Robinette said:
Thanks for the suggestions. I am able to get the phone recognized and responsive with fastboot, but it still doesn't want to work. When I attempted to re-flash recovery in fastboot, it completes the first step just fine and then hangs on "'writing' ..." as soon as that happens terminal freezes as does my phone, resulting in me having to battery pull and force quit terminal. I've waited and waited but it never finishes, and I think it's supposed to happen very fast anyway.
I read on another forum to extract the system.img, boot.img, and recovery.img from the PG32IMG.zip and manually install them via fastboot. I tried this as well but again I get errors and freezes immediately after "fastboot flash system system.img"
I also tried "fastboot erase cache" and again, it hangs and freezes both my phone and terminal.
I'm pretty sure my phone is a goner. If anyone has another suggestion please let me know. I don't think there are many things I haven't tried, except the alternative methods (software?) of running commands other than fastboot and recovery. I hope it's not just something dumb on my end like the usb port or permissions.
Click to expand...
Click to collapse
Try an RUU or the return to stock PG32IMG.zip in development.
Sent from my Incredible 2 using Tapatalk 2
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse
When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.
My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.