Develop Bugs

[Q] What problem my Kindle Fire stopping Kindle Logo ?????

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

[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] 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

[HOW TO] my kindle fire is stuck on the original boot screen

my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.

jbQsad said:
my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.
Click to expand...
Click to collapse
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.

kinfauns said:
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.
Click to expand...
Click to collapse
i was rooting and ran out of battery. and i would fast boot it but my kfu wont recognize my kindle even when its in adbinterface

Is it charging?

im not sure
Thepooch said:
Is it charging?
Click to expand...
Click to collapse
its plugged into the computer but since its at the boot logo i cant tell. the light is green on the bottom if that means anything

Maybe try another machine and attempt to reset the bootmode

[Q] Please don't hate me... fastboot "brick" on VM

So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!

escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2

soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!

escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?

Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.

Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.

Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".

soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet

Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.

Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?

Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?