Related
I have just bought Kindle. So i try to root and install TWRP recovery for my Kindle. After installing TWRP, because don't look Super User icon in Kindle; I took hard-reset my device in Settings. And Now My Kindle boot Logo Kinder Fire stuck on here.
What problem ???? Please help me....... i don't know i had just done nothing. Thanks guys !
I try to text in command dos: "add shell" but it show may Laptop Screen:
- exec '/system/bin/sh' failed: No such file or directory (2) -
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
I'm having this same problem. It's apparently stuck in fastboot. I can't even figure out how to type in adb commands or fastboot commands (meaning I could before and now when I tried it says command not found, but I didn't change anything. It won't recognize my device and when I try installing the android-winusb.inf it says it won't let me. I don't know what else to do. Any help would be appreciated. My Kindle is listed as unspecified device.
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
g1no23 said:
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But Boot Status show: Unknow, so when i type this text comandos show: waiting device
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
lovejoy777 said:
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
thanks guy much. But i tried all, i used KFU to try installing Recovery ( CMW, or TWRP), try to plug in USB Kinlde, press power button, etc. But It'S seem not working, all show: " exec- system/bin/sh failed ; not such file orr folder "
i also use tool KF Unbrick on XDA, but it's too. Reply show: " -exec- "system/bin/sh"...
Can U know that what problem in "system/bin/sh" of Kindle Fire ???????
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
works perfectly for me too! awesome!
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
thanks but my kindle don't have TWPR recovery after i've just flashing office room 6.2.1 from Amazon. Now it stuck in my logo Kindle
tunglx1988 said:
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Serinety said:
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for repl. But My Kindle Logo is Stuck in here. open KFU then show : Boolloader: UnKnow. So i don't know it bootmod ??? ( recovery, Normal, or fastboot).
b63 said:
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
he is absolutely right, this happened to me and nothing would work until I got a factory cable
This is a typical problem with KFU.
You need to go to your device manager and uninstall both the adb and android drivers then reinstall them manually. Sometimes it helps to restart your computer and Kindle afterwards. Make sure your device manager says both "Android Phone" and "Android ADB Interface" NOT "Other Device" and "Kindle".
When you are stuck at the boot screen it means you are in fastboot mode. In fastboot mode your device will only recognize fastboot commands. If your device doesn't recognize fastboot commands (KFU uses fastboot commands to change boot modes), 99 times out of 100, it's a driver issue.
A factory programming cable, while nice to have, is not usually necessary. A factory programming cable does two things. It provides power directly to the device instead of the battery AND forces the device into fastboot mode (stuck at boot logo). Since most of you with this problem are ALREADY in fastboot mode, a factory cable would be pointless.
Make sure you are 100% certain that you have the correct drivers installed and configured properly and then use the command prompt to change your bootmode to 4000.
In command prompt, navigate to the folder that contains fastboot.exe and enter the following commands...
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Sent from my Amazon Kindle Fire using xda premium
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
soupmagnet said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Click to expand...
Click to collapse
jingcleovil said:
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
Click to expand...
Click to collapse
i have the same problem as you it fills good to not be the only one
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.
I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.
im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage
do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?
2.2.0
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.
This is what I get in the command line
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds
digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.
soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.
Also, thanks for your help everyone, I'm learning a lot as I go here!
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
This is my gf's kindle fire and she wanted it rooted to have the google play store. This is completely untouched Kindle and on windows 7 pc. So I downloaded the KFU latest release 0.9.6 and proceeded w/ option 2 to install permanent root. Let it sit for about an hour with the please wait and waiting for device messages at the bottom of the screen. I wasnt sure how much longer this would be so i just let it sit. Couple minutes later my gf comes and let me know that she unplugged it accidentally while vacuuming. Im now stuck on the TWRP screen and will not reboot at all. If it try to reboot i get a message saying " E: System in not installed - preventing reboot! " which makes me think that the OS got wiped somehow. All I can do is let it run out of battery. Now in the KFU abd status: Offline and boot status: Unknown. Although that Windows will recognize the device as its showing up in device manager under Adroid Phone: Android ADB interface. What can I do?
not showing up.
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
soupmagnet said:
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
Click to expand...
Click to collapse
Mount function not working either. I hit the button and never shows up on my comp as a storage device.
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
soupmagnet said:
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
Click to expand...
Click to collapse
Could I just remove and reinstall the driver? Weird thing is that its still showing up on the device manager Adroid ADB interface.
In a perfect world, yes, that would work every single time.
soupmagnet said:
In a perfect world, yes, that would work every single time.
Click to expand...
Click to collapse
Well i managed to get the driver working and got to flash the latest update from amazon on and renamed it update.zip to get it to flash. Now it seems like its in a bootloop just showing kindle fire in the orange letters. Connecting it to KFU it shows ADB status: online , but still showing bootstatus as unknown.
You need to fix your drivers again.
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
neemo6 said:
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668159
kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
Thanks kinfauns great info!
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
neemo6 said:
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
Click to expand...
Click to collapse
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
soupmagnet said:
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
Click to expand...
Click to collapse
Awesome thanks for the help Soupmangnet!! I got it in twrp recovery now. I would like to just have it back to stock at this point and have the latest update downloaded from amazon on the sd card. Im just worried that this will put me back into the same problem as before. Do need to download or fix something else?
Make sure you change the file's extension to .zip as before, and above all else, wipe System and "Factory Reset". Everything should go well for you.
You sir are awesome! Everything works great! Now to get play store.
You could have simply just flashed modaco instead of going through all he hassle of flashing update.zip and wiping out fff and twrp...
I read the guide and have been browsing the forums for similar situations.
First of all, many months ago I tried to root my KF with something named "doomlord"? I basically googled how to root, picked one, went at it. It ran fine, though I don't recall trying to do anything with the root. Most recently every time I powered it on, I was in the CWMR menu. I tried to install the latest kindle update from amazon (changed it to .zip, placed it in the folder, tried to install from cwmr menu), to get it back to stock. Didn't work, and the only way I was able to use my kindle was wiping everything and rebooting. I became frustrated and started to try anything I hadn't, I clicked fastboot mode. Now it's been stuck at the yellow triangle, does nothing when power is pressed, isn't recognized by my mac.
Many users had my similar situation but I truly am a newbie and went at this with no knowledge, though I do know some terms through the guide. It seems I'm stuck in a bootloop, and my kindle isn't truly broken for good.
What I want to know, in basic terms:
What do I need to download?
To send commands.. do I use terminal? Seems like I need to get 'fastboot' and 'adb'
I've also seen references to getting kindle fire utility- can I use this even though I used some random doomlord program and it's using CWMR?
How to 'flash' something?
Simple, step by step instructions would be SO APPRECIATED! I apologize for having a question everyone else has asked, but I feel so frustrated at this point.
Anybody?
So far, I have downloaded KFU, adb, fastboot, and FFF 1.2.
I've tried many commands to see if my kindle is in fastboot, it does not seem to be. All commands come back with "-bash: fastboot: command not found". I also am going into the directory of "android" where I put adb and fastboot. I think that is correct.
Not sure what to do with KFU, or FFF that I've downloaded.
Should I wait for the battery to drain? Though I don't think that will fix the problem at all.
Kindle still not being recognized by my mac.
At this point I will just pay somebody to help me successfully fix this or send it out. But if it's as easy as the solutions make it seem, I'd love to just do it myself. I think I'm just confused about what exact steps I need to make, whether that is flashing FFF or TWRP?
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
soupmagnet said:
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
Click to expand...
Click to collapse
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
2hellwu said:
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
Click to expand...
Click to collapse
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
soupmagnet said:
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
Click to expand...
Click to collapse
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
2hellwu said:
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
Click to expand...
Click to collapse
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
soupmagnet said:
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
Click to expand...
Click to collapse
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
2hellwu said:
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
Click to expand...
Click to collapse
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
soupmagnet said:
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
Click to expand...
Click to collapse
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
2hellwu said:
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
Click to expand...
Click to collapse
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
soupmagnet said:
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
Click to expand...
Click to collapse
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
2hellwu said:
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
Click to expand...
Click to collapse
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
soupmagnet said:
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
Click to expand...
Click to collapse
ah yes. so, that worked. now at:
Code:
< waiting for device >
~/Desktop/fastboot reboot
at this point KF is still off. power on or no?
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
2hellwu said:
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
Click to expand...
Click to collapse
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
soupmagnet said:
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
Click to expand...
Click to collapse
Before I start this- I should have clarified my main goal is to get my kindle back to stock. I don't have a need for anything extra, I really just use it to read books. From other guides, maybe it seems that my next steps should be to download the kindle update from amazon, and flash that?
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
2hellwu said:
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
Click to expand...
Click to collapse
Yes, the mounted volume "Kindle" is your sdcard. Just drag and drop everything into that folder. Be sure to eject the volume from your computer (right-click on it and select eject) before you unmount it in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."