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.
Hello. After a few attempts I was finally able to root my kindle fire using Breakdroid found here: http://forum.xda-developers.com/showthread.php?t=1511757 .(I only have access to an OSX, no windows). I have a dell latitude running snow leopard. (hackintosh)
I can get to the black and red screen.
I downloaded the energy ics apk and tried to install the zip through the CWM-base Recovery v5.0.2.7 FULL (by DooMLorD) and it just loops through the fire screen with the triangle logo. Occasionally you can see the ICS startup screen, but very briefly(like 1 sec) but it goes back to looping through the reset.
I am not new to rooting android devices as I have rooted my phones in the past with no problems.
1. What am I doing wrong?
2. I can try install TWRP but how?(step by step on overwriting the CWM-base Recovery in OSX please, i have adb and tried but it does not see twrp in my file location.
3. is there an updated script for osx that auto installs TWRP?
If someone has time, please post a video please as there are none on installing using OSX on a fire using 6.3 on youtube or anywhere else on the web.
I cant add a new post since im new so Im editing this one:
Thanks! After waiting 15 min for the opening ICS screen, I finally rebooted and had the same problem..
Now the big question... how do you install TWRP using OSX?
tell you the steps I have done with no success...
I went to http://www.teamw.in/project/twrp2 and chose kindle fire
downloaded the .img and placed it in my platforms-tools(and yes, I downloaded the ADB package and added platform-tools)
first did adb devices and got:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
436E000600000001 recovery
then followed the websites direction and started adb shell by typing adb shell and got:
:~ drive$ adb shell
~ #
then followed the websites direction and entered su and got:
~ # su
/sbin/sh: su: not found
~ #
why was su not found?
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
matchnbpm said:
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
Click to expand...
Click to collapse
TWRP is required to run the new ICS roms. CWM usually will not work.
ok.. got su to finally work after reloading kindle fire's image that I did a backup of and let it be on USB mode
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
.. Edit.. found out that fastboot requires that you exit out of ADB..
now fastboot stuck on 'waiting for device'
matchnbpm said:
ok.. got su to finally work
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
Click to expand...
Click to collapse
You don't need "su" to enter fastboot commands.
While in recovery, enter:
adb shell idme bootmode 4002
adb reboot
That will restart your kindle in fastboot mode. Then you can enter:
fastboot flash recovery /path/to/twrp.img
Then...
fastboot oem idme bootmode 4000
...and reboot
EDIT:
6.3.1
Wow.. what a pain! Finally got TWRP to load! Here are the instructions for OSX using http://forum.xda-developers.com/showthread.php?t=1511757 (since no one seems to have it)
download breakdroid
start breakdroid (not kindlewater)
press 5 for kindle
press ok
press 1 for autoroot
now this is where you either get it or not.. my first time I got hung at waiting for device, so i simply unplugged it and replugged it and continued the autoroot. The second time after i unrooted my kindle fire and rerooted I did an exit and re rooted and it went all the way through... so your choice...
after you should be able to load kindle fires normal os after you see a triangle with a fire in it
now download TWRP
head over to: http://www.teamw.in/project/twrp2 choose kindle fire from their
'please select device'
download their .img
follow the instruction here to add adb to your MAC: http://forum.xda-developers.com/showthread.php?p=9842005
with the instructions, make sure you do it step by step including the "Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it."
if you did the instructions correctly you made a quick way to start ADB.
you can check if it works by starting a terminal(under applications/utilities(i made a quickstart and pinned it to my bar) and type ADB devices(with caps)
you should see your device there, if not, retrace your steps
move the TWRP .img file to your platform-tools folder
now start your kindle fire to normal mode and plug in your usb.. leave it on USB mode, do not exit
start a terminal and type ADB devices, your kindle fire should NOT be in recovery, should show 'device'
follow the TeamWin directions and type adb shell
type su
type idme bootmode 4002
type exit
quit terminal
restart terminal
type fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
your kindle fire will look like it is locked up after a few min, simply power off your kindle fire after installation of TWRP by pressing the power button until it turns off..
power back on and press and hold until it turns orange, release..
Welcome to TWRP!
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
I'm trying to downgrade htc incredible 2 6.01.605.05 and I'm stuck on the following step:
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue
I do not get the red exclamation mark it just boots into hboot then after I reboot the phone and try the next step it says root denied.
Can anyone tell me were I'm going wrong i'm following the steps here:
http://forum.xda-developers.com/showthread.php?t=1726134
mrkmzo said:
I'm trying to downgrade htc incredible 2 6.01.605.05 and I'm stuck on the following step:
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue
I do not get the red exclamation mark it just boots into hboot then after I reboot the phone and try the next step it says root denied.
Can anyone tell me were I'm going wrong i'm following the steps here:
http://forum.xda-developers.com/showthread.php?t=1726134
Click to expand...
Click to collapse
Check out this thread. It has been updated more frequently by Prototype:
http://forum.xda-developers.com/showthread.php?t=1751796
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.