Develop Bugs

[Q] Kindle Fire Bricked: exec "system/bin/sh": No such file or directory

I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory

i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7

b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.

adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot

b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.

your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times

b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.

Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery

qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery

osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery

qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >

just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img

b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >

the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works

b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.

would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry

I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.

You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.

@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm

When it says waiting for device, what happens when you unplug and plug in the device?

[Q] KF Stuck on FireFireFire 1.3 - Not Recognized by ADB

Edited OP to be shorter to the point:
I am stuck in fastboot but can not establish an adb connection to set the boot mode back to 4000.

Xplorer4x4 said:
I was tired and trying to update my KF to FFF1.3 and TWRP 2.1.0. I am now stuck at the new FFF boot logo(green android guy with KF text under neath). The update to FFF1.3 went smooth. Then I moved on to TWRP. So I tried flashing the img file via terminal emulator rather then using ADB over my computer. So first I set the boot mode to 4002. Success! Then I tried to flash the img file, but was getting errors(I think it was because I forgot to cd in to the downloads folder so Terminal Emulator knew where the file was). Well Due to not being able to flash I had to set up my PC again for the KF to use ADB as I had a system crash since then. So I got hung up with not being bale to use ADB and decided to reboot the KF, thinking it needed a reboot before the PC would recognize it. After rebooting I for stuck on the FFF 1.3 logo. I know ADB is fully functional now(forgot to install an API) but the KF Utility will not recognize the device to be able to reset the boot mode to 4000.
Any suggestions?
Click to expand...
Click to collapse
can't use term to flash like adb, gotta use the dd if= method.
might be I'm fastboot if its stuck at the startup logo.
Sent from my HTC Glacier using xda premium

Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D

DeadChex said:
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
Click to expand...
Click to collapse
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.

Xplorer4x4 said:
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Click to expand...
Click to collapse
opps, I lied... you cant issue idme from fastboot.... nor can you issue fastboot shell...
so, no adb at the very beginning of the KF boot? Does fastboot notice it
Try "Fastboot Reboot" if fast boot works... or 'Fastboot continue"

DeadChex said:
so, no adb at the very beginning of the KF boot?
Click to expand...
Click to collapse
Nope, not at all.
Does fastboot notice it?
Click to expand...
Click to collapse
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?

Xplorer4x4 said:
Nope, not at all.
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Click to expand...
Click to collapse
the boot process goes... Bright LED (first turning on) > Dim LED (Fastboot and Button input) > Bright LED (Normal Boot)
Where is it stuck?
Use "fastboot devices" to see if its listed in the beggining (when bright green)
but, if its going Bright, that means its not trapped in fast boot
(Fastboot is a diffrent program from ADB completly, just throwing that out there, I've attached it if you need it)

Something very enlightening I found somewhere around this great place:
"
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
"
Edit: You do need the file in the above post when doing this over usb.
Sent from my Amazon Kindle Fire using XDA

freefaling said:
Something very enlightening I found somewhere around this great place:
Click to expand...
Click to collapse
This is great information but totally useless with out a working ADB.
DeadChex said:
(Fastboot is a diffrent program from ADB completly, just throwing that out there)
Click to expand...
Click to collapse
I am aware, but thanks anyways.
fastboot devices does give an out put after the dim. Did not test before the dim.
Good News: I tried the "fastboot -i 0×1949 oem idme bootmode 4000" command again and got an unrecognized vendor ID. So despite following the instructions to modify the 2 .ini files, and accept the install driver warning, and selecting the location for the ini manually as you should, I realized something was wrong with adb. So I used the install driver bat from the KF Utility zip,and got adb working. Issued the 4000 boot command and back in business.
Thanks for all the help guys! I think you guys managed to provide the fastest responses to help I have ever needed, and it is rare I ask for help, so that makes the experience that much better.

[Q]Bricked my Kindle during root, no custom bootloader installed, need help.

I'm stuck on the Kindle File logo boot screen.
I used this client to attempt to root my Kindle. I am rather inexperienced, and tried to apply a permanent root with superuser before installing a custom bootloader. In the process, i think it tried to install FFF, but would take an unusually long time to download and install it. So naturally, as any frustrated noob would do, i tried to X out of the window and unplug my Kindle. Bad idea. Turned it on, and it was stuck on the boot screen.
I've tried using a MOTO factory cable to start it in fastboot, but it would not work. In the Kindle Fire general section, there is a sticky that has instructions on how to unroot it, but the link to download important files just leads to some internet propaganda thing multiupload is hosting or something; I can not download the files.
Any help and instruction would be great. I must warn, I'm rather new to the whole rooting and device modding thing, so I may need some additional instruction. Thanks in advance.

Your just stuck in fastboot shift +right click on kfu tools folder select open command window here power off your device leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug it in it will power on in the terminal if you get a response product: kindle type fastboot -i 0x1949 oem idme bootmode 4000 hit enter then type fastboot -i 0x1949 reboot it should then boot normal use a standard cable for this not your moto factory cable

[Q] I've bricked my KF, no custom bootloader, Factory cable didn't work. Need help.

I'm stuck on the Kindle File logo boot screen.
I used this client to attempt to root my Kindle. I am rather inexperienced, and tried to apply a permanent root with superuser before installing a custom bootloader. In the process, i think it tried to install FFF, but would take an unusually long time to download and install it. So naturally, as any frustrated noob would do, i tried to X out of the window and unplug my Kindle. Bad idea. Turned it on, and it was stuck on the boot screen.
I've tried using a MOTO factory cable to start it in fastboot, but it would not work. There is a sticky at the top of this section that has instructions on how to unroot it, but the link to download important files just leads to some internet propaganda thing multiupload is hosting or something; I can not download the files.
SOLUTION:
shift +right click on Kindle Fire Utilities tools folder, select open command window here. power off your device leave it unplugged, type "fastboot -i 0x1949 getvar product" (no quotations). when it says waiting for device, plug it in it will power on in the terminal. if you get a response "product: kindle" type "fastboot -i 0x1949 oem idme bootmode 4000", hit enter then type "fastboot -i 0x1949 reboot" it should then boot normal use a standard cable for this, not your moto factory cable

USB_boot with pokey9000's firekit

64_hit_combo said:
I'm stuck on the Kindle File logo boot screen.
I used this client to attempt to root my Kindle. I am rather inexperienced, and tried to apply a permanent root with superuser before installing a custom bootloader. In the process, i think it tried to install FFF, but would take an unusually long time to download and install it. So naturally, as any frustrated noob would do, i tried to X out of the window and unplug my Kindle. Bad idea. Turned it on, and it was stuck on the boot screen.
I've tried using a MOTO factory cable to start it in fastboot, but it would not work. There is a sticky at the top of this section that has instructions on how to unroot it, but the link to download important files just leads to some internet propaganda thing multiupload is hosting or something; I can not download the files.
Click to expand...
Click to collapse
Sounds like your booting to fastboot mode you need to download the drivers so you can set your bootmode back to system
Sent from my Galaxy Nexus using xda premium

Your KF is OK and you need to change the boot mode to normal by following the below commands
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
from my Amazon Kindle Fire using Tapatalk 2

ammubarak said:
Your KF is OK and you need to change the boot mode to normal by following the below commands
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Okay, I'm assuming i can do this through cmd.exe, but what commands do i need to type in to get to the point where i can type these in?

I've fixed it. Thanks to someone over in the Q&A section.
Turns out i was stuck in fastboot.
For anyone who discovers this thread in the future, here was the solution:
shift +right click on kfu tools folder, select open command window here. power off your device leave it unplugged, type "fastboot -i 0x1949 getvar product" (no quotations). when it says waiting for device, plug it in it will power on in the terminal. if you get a response "product: kindle" type "fastboot -i 0x1949 oem idme bootmode 4000", hit enter then type "fastboot -i 0x1949 reboot" it should then boot normal use a standard cable for this, not your moto factory cable

This worked for me, thank you very much.

I have this same problem, but I cannot get my computer to recognize that the Kindle Fire is plugged in. I have tried installing the KFU driver but that doesn't seemed to have worked.

Try the iso I made post 7 http://forum.xda-developers.com/showthread.php?t=1413358 or just run your own http://forum.xda-developers.com/showthread.php?t=1850038

Confused and Broken

Ok, so I have very eagerly jumped on and tried to root my Kindle Fire. I read a few things, thought "This is easy and didn't read everything (shocker) and now am looking at a white / orange kindle fire logo and "unknown device" in device manager
I have uninstalled and reinstalled the drivers provided by the kfu
I have tried the unbrick kit
I have downloaded the soupkit but gave up cuz my experience with Linux is celebrating that I can SPELL U-b-u-n-t-u right.
At this point, I realized I am jumping the gun and need to focus on drivers.
I have read that I need to know 'where' it's broken (huh?) in the bootloader or boot process.
I have also read I need to run adb or kfu or skd or ffff or twrp or my kf will remain f.u.b.a.r.
I have read http://forum.xda-developers.com/showthread.php?t=1644970
http://forum.xda-developers.com/showpost.php?p=23747567&postcount=1
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
& http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
and dunno where I got lost.
Please help! Thanks in advance!

Progress!!!
ok so I got drivers installed as I now have an "android phone --> Android ADB interface" in the DM.

Id suggest flashing bootloader + recovery manually in fastboot
Something like:
fastboot -i 0x1949 flash recovery "/home/mike/twrp.img"
fastboot -i 0x1949 flash bootloader " /home/mike/fff.bin"
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 rebootot

Alright, if you have the drivers working you should be able to root and manage everything. I wrote a detailed guide on getting it working. Have you attempted to root it yet?

OH NOES! Your device manager says "Unknown Device"! From my experience, it is caused by a faulty bootloader flash, which is probably why you couldn't connect after using the SoupKit.
In Linux, with the device plugged in and powered up, enter the following command...
Code:
lsusb -v
...and print the results here. Also, it is very important to know what bootmode you are in. The easiest way to tell is by looking at the boot screen at startup. kinfauns' fastboot guide will give you an idea of what you should look for.
http://forum.xda-developers.com/showpost.php?p=26435498

powerpoint45 said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 rebootot
Click to expand...
Click to collapse
worked and was able to run the kfu to root the device and install TWRP and FFFF and I think that's it.
Now, I see the TWRP screen can't do anything from there. I tried mounting USB Storage and doing an "adb push" and get " 'adb' is not a recognized as an internal or external command, operable program or batch file."
::edit:: figured the adb issue. now getting 'device not found' when trying to push a ROM
Still confused and thinking maybe it's not too late to turn back.