Develop Bugs

Stuck at KindleFire white/orange logo. Unresponsive to ADB commands.

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

Replacement cannot "fastboot"

Hell. I've received my KF's (1st gen) replacement today and I've tried to get into fastboot using a factory cable.
My KF would enter FB mode but upon doing so my system (both Linux and Windows) would "lose connection" with my KF.
So I'd reboot instead. When it'd boot into stock ADB worked so I changed bootmodes hoping that this time around Fastboot will work.
Again both my Linux and my Windows systems refuse to make any "contact" with my KF, only this time around my KF is also incapable to get out of fastboot as well (given that I changed the bootmode via ADB).
So what is this? (while in Windows I'm getting "unknown drivers", in Linux nothing happens as if the device is not connected at all)
Also would the USB method work, or should I -merely- again replace my KF since as it seems there's some problem in a Hardware level...
Thanks.

Stevethegreat said:
Hell. I've received my KF's (1st gen) replacement today and I've tried to get into fastboot using a factory cable.
My KF would enter FB mode but upon doing so my system (both Linux and Windows) would "lose connection" with my KF.
So I'd reboot instead. When it'd boot into stock ADB worked so I changed bootmodes hoping that this time around Fastboot will work.
Again both my Linux and my Windows systems refuse to make any "contact" with my KF, only this time around my KF is also incapable to get out of fastboot as well (given that I changed the bootmode via ADB).
So what is this? (while in Windows I'm getting "unknown drivers", in Linux nothing happens as if the device is not connected at all)
Also would the USB method work, or should I -merely- again replace my KF since as it seems there's some problem in a Hardware level...
Thanks.
Click to expand...
Click to collapse
In Linux, can you see the device in fastboot with lsusb?
You know, they may have given you the proverbial shaft and replaced your 1st gen with a 2nd gen.

soupmagnet said:
In Linux, can you see the device in fastboot with lsusb?
You know, they may have given you the proverbial shaft and replaced your 1st gen with a 2nd gen.
Click to expand...
Click to collapse
Yep I can (as "Lab126"), but trying to issue any command and I get the proverbial "waiting for device"... How can I even check it's 2nd gen? IIRC it had bluetooth support for one and I don't, also Windows gave me the Hardware ID of KF 1st gen (unless they somehow share the same Hardware ID).
In other news I managed to change the bootmode back to normal (for a split second FB worked enought to change the bootmode, but not enough to do anything else). So yeah I have adb support (when I boot into the rom), but nothing much else. What can I do with adb (w/t fastboot my hands are tied aren't they?).

What does the following command return? (in Linux)
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'

soupmagnet said:
What does the following command return?
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
Click to expand...
Click to collapse
Hmm for the time being I'm back into Windows restoring my KF apparently adding the flag "-i 0x1949" after fastboot did the trick even though "bare" fastboot commands don't work ("fastboot devices" gives me nil). Anyhow I've managed to install FFF, TWRP and as I mentioned earlier I'm currently restoring from my backups.
However if you wish I can try run the command when all this is finished (it's still a mystery to me why "regular" fastboot doesn't work).

Stevethegreat said:
Hmm for the time being I'm back into Windows restoring my KF apparently adding the flag "-i 0x1949" after fastboot did the trick even though "bare" fastboot commands don't work ("fastboot devices" gives me nil). Anyhow I've managed to install FFF, TWRP and as I mentioned earlier I'm currently restoring from my backups.
However if you wish I can try run the command when all this is finished (it's still a mystery to me why "regular" fastboot doesn't work).
Click to expand...
Click to collapse
It's because of the stock bootloader. The stock bootloader requires the -i switch, FFF does not.

soupmagnet said:
It's because of the stock bootloader. The stock bootloader requires the -i switch, FFF does not.
Click to expand...
Click to collapse
Gotcha! Thanks

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

[Q] KFHD Boot Logo Problem

Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!

Maximus300 said:
Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!
Click to expand...
Click to collapse
Thats a kindle fire hd 8.9" model, fastboot cables don't work on them. A easy way to fix this is to boot a ubuntu live cd and install the fastboot command from the repos and run it. Latest ubuntu is 14.04 lts and i haven't checked the package names yet, but if it has the same name as on 13.10 then these instructions should work. Boot a ubuntu live usb/cd and open the settings and look for something like software updates and check off all the download form internet boxes. Hit reload if it asks, and if it asks ignore the first command in the next part of the instructions.
Now open a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
fastboot -i 0x1949 getvar product
Now that it says waiting for device, plug the kindle in while its off and you should be in fastboot mode. From there you can reflash it from windows with kffa or srt, or just do it manually while in ubuntu.

So I used the Linux command to put my Kindle in fastboot mode, but now it says it cannot connect with MTP device, so I still cannot flash any type of recovery. Even though it is in fastboot mode, and the drivers are installed, ADB is still not working on Windows.... and I'm not sure how to do it manually on Linux...

MTP is irrelevant with fastboot, as is adb, you don't use adb commands with fastboot, you use fastboot commands. You can use kffa or SRT to restore it from windows once it is in fastboot, or restore it manually in Linux using SRT's images. You probably will have to use SRT, I have heard a report that kffa's downloads for the images are offline again, though I'm not positive on that.
Sent from my Amazon Tate using Tapatalk

Fire HD 8.9" Stuck at Boot Screen, cannot connect fastboot or ADB

Hello all,
Recently recieved a Fire HD 8.9" (OS 8.5.1) from a family member that upgraded to a newer Fire HDX. I decided to convert the tablet to Pure Android to give it another lease on life, I followed the instructions here https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286 and I goofed. I forgot to "apply stack override" when flashing and when rebooting to go into TWRP it froze at the boot animation and will not connect to my PC (you can watch on device manager and it appears for less than 2 seconds before disconnecting). I have been out of the rooting and installing custom ROMs for a few years and I am lost as to what to do next. Fastboot and ADB commands are something I have not used before (I do have the latest Android SDK installed) using the command prompt doesn't scare me and I am used to fixing Windows OS issues using it. I have read a couple of threads saying to flash the factory system image to the device using fastboot but haven't found a step-by-step on exactly how to do so. I also have installed the driver for Kindle Fire HD 8.9" JEM found on XDA if that helps. TWRP is/was installed prior to rebooting, would just like to get back to where I can try again. This community has helped me a lot in the past when it has come to my Android devices.
Thank you,
Coop

I have the exact problem and and have been trying to find the solution for a week but nothing works. If I by chance find something I will come back and post it.

NecroWolf said:
I have the exact problem and and have been trying to find the solution for a week but nothing works. If I by chance find something I will come back and post it.
Click to expand...
Click to collapse
To go to fastboot - Shutdown your device.. and then make sure you have adb and fastboot installed in your pc/windows then type in
HTML:
fastboot devices
and hit enter. This should say <waiting for devices>
Then, connect your kindle hd to PC. It should show... fastboot mode
First make sure you have the correct device.. type the following... it should say ...jem
HTML:
fastboot -i 0x1949 getvar product
If you are able to get to fastboot mode.. if you have the stock image for boot, recovery, and system backups.. do the following
1.
HTML:
fastboot -i 0x1949 flash boot [your boot image file]
2.
HTML:
fastboot -i 0x1949 flash recovery [your recovery file]
3.
HTML:
fastboot -i 0x1949 flash system [your system/os file]
you should be able to restore to factory os.. Also, this worked for me in Mac.. had some issues using PC

I have the same situation and my Fire HD 8.9 is not detected by fastboot or adb.

this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!

just make sure you do
fastboot -i 0x1949 getvar product
in the CMD before you boot your device.
I made mistake of booting device then entering command prompt and couldn't get anywhere.
I also tried different usb ports.
also updated drivers on usb ports.
I used iobit driver booster 5 today and scan/installed outdated drivers. Maybe that helped.
plugging usb I noticed windows recognize something with word jem in it when I turned on device.
turned off tablet and retried and I got into fastboot.
again make sure fastboot -i 0x1949 getvar product is active in CMD before turning on tablet