Kindle Fire 5th Gen, adb lost at recovery - Kindle Fire Q&A, Help & Troubleshooting

I've installed all the necessary drivers, checked with rootjunkie's supertool and verified that adb and fastboot drivers are detected, and verified that adb is detected all the way up to the recovery. But when I select "sideload from adb," my Device Manager shows the device as "Other-KFFOWI," and typing "adb devices" returns no devices. Have I done something wrong?

ArtOfSnaila said:
I've installed all the necessary drivers, checked with rootjunkie's supertool and verified that adb and fastboot drivers are detected, and verified that adb is detected all the way up to the recovery. But when I select "sideload from adb," my Device Manager shows the device as "Other-KFFOWI," and typing "adb devices" returns no devices. Have I done something wrong?
Click to expand...
Click to collapse
This is not the 5th gen forum
ask here
http://forum.xda-developers.com/amazon-fire/help
Sent from my XT1080 using XDA Labs

Related

[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

Kindle Fire Stuck in TWRP 2.2

Hi,
My Problem:
My kindle fire is stuck in twrp. There are no backups or roms. When I do a Normal Boot, it just gets frozen at the kindle fire boot logo. When I try to mount the USB storage (cache & sd card), my computer can't find it. I do have FireFireFire on it and I have manageed to get it into fastboot mode. Still no luck
How I Tried To Fix it:
I downloaded the kindle fire driver and installed it. I have already done the Android SDK thing too, I've already edited the two files in Notepad. Then, I went on Command Prompt and did the "adb kill-server", "adb start-server", and then "adb devices" but it doesn't list my kindle fire. Under device and printers on my PC, it does list the driver for kindle, but when you click on properties it says only "Android ADB Interface".
Can anyone help me with this? Please?
I can post it again here if you can't fix it in windows try this http://forum.xda-developers.com/showthread.php?t=1882565
OK. Do you know how to get command prompt, under adb, to show my kindle? I do adb shell but it returns with "error: device not found". When it says Android ADB Interface it knows it's a Kindle Fire. But it only says "Android ADB Interface" under device & printers
This method is with Linux it will show your kindle attatched in what form is yet to be determined
Thepooch said:
This method is with Linux it will show your kindle attatched in what form is yet to be determined
Click to expand...
Click to collapse
OH MY GOD!! I got it working!
:-|
threed42 said:
Hi,
My Problem:
My kindle fire is stuck in twrp. There are no backups or roms. When I do a Normal Boot, it just gets frozen at the kindle fire boot logo. When I try to mount the USB storage (cache & sd card), my computer can't find it. I do have FireFireFire on it and I have manageed to get it into fastboot mode. Still no luck
How I Tried To Fix it:
I downloaded the kindle fire driver and installed it. I have already done the Android SDK thing too, I've already edited the two files in Notepad. Then, I went on Command Prompt and did the "adb kill-server", "adb start-server", and then "adb devices" but it doesn't list my kindle fire. Under device and printers on my PC, it does list the driver for kindle, but when you click on properties it says only "Android ADB Interface".
Can anyone help me with this? Please?
Click to expand...
Click to collapse
it did not work 4 me

[Q] fastboot drivers

I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Resolver1 said:
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Click to expand...
Click to collapse
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
Hmm that did help. I should make a noob friendly guide because all of these guides are so vague when it comes to fastboot.
fast boot commands not functioning, adb works fine
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
lgweaver said:
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
Click to expand...
Click to collapse
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
onemeila said:
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
Click to expand...
Click to collapse
Found those steps. but that driver was already installed and said it was functioning. I risked it and attempted the root and install of jellybean without the fastboot command showing devices. apparently it works. my Kindle fire 2 is running cyanogen mod without issue now.
thanks for the response.

[Q] KFHD 8.9" ADB works, fastboot doesn't

Hello,
I successfully rooted my KFHD 8.9" with Bin4ry's "root many android." I want to install Cyanogenmod on my tablet, so I installed the android adt bundle. The problem I have is that I'm unable to fastboot the Kindle. Typing "adb devices" in the command prompt looks like this:
adb devices
B0C91101319300F6 device
However, typing "fastboot devices" in the prompt returns nothing. I've also tried powering off and unplugging my Kindle, typing this:
fastboot -i 0x1949 getvar product
into the command prompt and then pluggin in the device. However, the command prompt just stays at < waiting for device > and the Kindle powers on normally (not fastboot mode).
Did anyone have this same problem? If you were able to fastboot successfully, which drivers did you use (where did you download them from)? I tried the drivers from here http://forum.xda-developers.com/showthread.php?t=1893838 and here http://forum.xda-developers.com/showthread.php?t=2337634. Niether worked.
Thanks!
If you have adb access try "adb reboot bootloader", or if rooted run
Code:
adb shell "su -c 'reboot bootloader'"
That should get you into fastboot so you can install the drivers in my signature, from there on the method you were previously trying should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If you have adb access try "adb reboot bootloader", or if rooted run
Code:
adb shell "su -c 'reboot bootloader'"
That should get you into fastboot so you can install the drivers in my signature, from there on the method you were previously trying should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Sorry, I'm a bit confused, which drivers? Also, where to install the drivers computer, Kindle?
The drivers are in my signature(my signature is only viewable when not in a tapatalk or equivalent app, like if you view this thread on your pc.), download them onto your computer and extract them somewhere, open the device manager with kindle plugged in and USB debugging enabled and you should see a device with a yellow triangle next to it. Right click it and hit update driver, and tell it to search the directory you extracted my drivers to and it should install. If you are on windows 8 you will have to disable driver signature enforcement first.
Sent from my Amazon Tate using Tapatalk
Just use fireflash Google the apk. I had the same problem. The only tutorials were for the 7 in, but find one. Don't use the files they tell you to use. Go to hashcodes goo.im and find the ones for the 8.9.
Sent from my Amazon Jem using Tapatalk
Or you can use the fireflash tutorial for 8.9", its stickied in the 8.9 dev section. http://forum.xda-developers.com/showthread.php?t=2277105
While the fireflash method is easier, you have to make sure you check the box that downgrades the bootloader or you will have a red screen brick upon reboot. The box to check has red warning text under it. somehow people miss it.
Sent from my Amazon Tate using Tapatalk

[Q] Stock 1st gen KF stuck on logo screen

Been through a bunch of threads here and elsewhere trying to figure this out. My daughter brought her 1st gen KF to me last night with it stuck on the logo screen. Here's the things I've tried so far:
Hard reset (with power button): Held down for 20 seconds to a minute. Doesn't work.
Installed adb and fastboot on my Mac OS X system. I can get adb responses, "adb devices" returns <device ID> device. The KF will also reboot with the "adb reboot" command. I followed the suggestion at noelarlante.com/kindle-fire-stuck-at-boot-logo-solved (can't post link, new user), but when I ran the "adb shell /data/local/tmp/fbmode" command, it returned "couldn't write bp1, panic!"
Also tried running "adb shell idme bootmode 4000" and "adb shell idme bootmode 4002", but get permission denied as the response
Fastboot commands don't work, I just get <waiting for device>
On the Windows 7 side, I installed the Amazon drivers and the KF is recognized without any problems.
I then tried the Kindle Unbrick Utility (v1.1). If I run the "Stuck at logo" option, I get error: device not found, even though Device Manager lists the Kindle Fire without any issues (shows up as Android Composite USB Interface). "Recovery Loop" option leaves me at <waiting for device>.
Turning now to the Kindle Fire Utility (v0.9.9), the KF is listed as ADB Status: Online, but Boot Status: Unknown. Using the options on the bootmode menu, the KF will reboot, but I get the "couldn't write bp1, panic!" message and Boot Status stays unknown. If I try to install TWRP, "couldn't write bp1, panic!" comes up again, then <waiting for device>. Nothing more happens.
Any suggestions beyond what I've tried so far? The key step seems to be getting past the "couldn't write bp1, panic!" issue.
May need a fastboot cable.
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT912 using Tapatalk
sd_shadow said:
May need a fastboot cable.
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Click to expand...
Click to collapse
Yeah, I was wondering if the cable might be necessary. I'll give that a try and check back in when I've got it.
typ993 said:
Yeah, I was wondering if the cable might be necessary. I'll give that a try and check back in when I've got it.
Click to expand...
Click to collapse
Try the fastboot commands without cable first.
I meant to add that in first post.
Sent from my XT912 using Tapatalk
sd_shadow said:
Try the fastboot commands without cable first.
I meant to add that in first post.
Click to expand...
Click to collapse
See OP, fastboot commands just give me the <waiting for device> prompt, only the adb commands work. Hoping the cable gets around that.
typ993 said:
Been through a bunch of threads here and elsewhere trying to figure this out. My daughter brought her 1st gen KF to me last night with it stuck on the logo screen. Here's the things I've tried so far:
Hard reset (with power button): Held down for 20 seconds to a minute. Doesn't work.
Installed adb and fastboot on my Mac OS X system. I can get adb responses, "adb devices" returns <device ID> device. The KF will also reboot with the "adb reboot" command. I followed the suggestion at noelarlante.com/kindle-fire-stuck-at-boot-logo-solved (can't post link, new user), but when I ran the "adb shell /data/local/tmp/fbmode" command, it returned "couldn't write bp1, panic!"
Also tried running "adb shell idme bootmode 4000" and "adb shell idme bootmode 4002", but get permission denied as the response
Fastboot commands don't work, I just get <waiting for device>
On the Windows 7 side, I installed the Amazon drivers and the KF is recognized without any problems.
I then tried the Kindle Unbrick Utility (v1.1). If I run the "Stuck at logo" option, I get error: device not found, even though Device Manager lists the Kindle Fire without any issues (shows up as Android Composite USB Interface). "Recovery Loop" option leaves me at <waiting for device>.
Turning now to the Kindle Fire Utility (v0.9.9), the KF is listed as ADB Status: Online, but Boot Status: Unknown. Using the options on the bootmode menu, the KF will reboot, but I get the "couldn't write bp1, panic!" message and Boot Status stays unknown. If I try to install TWRP, "couldn't write bp1, panic!" comes up again, then <waiting for device>. Nothing more happens.
Any suggestions beyond what I've tried so far? The key step seems to be getting past the "couldn't write bp1, panic!" issue.
Click to expand...
Click to collapse
OP says nothing about fastboot commands.
See fourth bullet point in list above.
Will the fastboot cable override whatever has failed to keep the KF stuck in the boot loop? If the KF is accepting (some) adb commands, does that imply it is in normal bootmode?
Thanks again, got the cable ordered.
typ993 said:
See fourth bullet point in list above.
Will the fastboot cable override whatever has failed to keep the KF stuck in the boot loop? If the KF is accepting (some) adb commands, does that imply it is in normal bootmode?
Thanks again, got the cable ordered.
Click to expand...
Click to collapse
Fastboot cable forces Kindle into fastboot mode.
Sent from my XT912 using Tapatalk
Problem is solved. Here's what I did:
As sd_shadow suggested, I got a fastboot cable. This worked to get the KF into fastboot mode.
Once in fastboot mode, I was able to use Kindle Fire Utility to load FireFireFire and TWRP onto the Kindle.
TWRP from KFU was kind of an old version, so I got the latest version and did a fastboot flash recovery to load up that newer version.
Also downloaded the stock Kindle ROM. For some reason, the sdcard partition wouldn't mount in my Win7 VM, but did mount on my Mac, so copied update.zip from there.
TWRP (2.8.5.0 otter) then wouldn't install the ROM. Tried loading in the 2.8.5.0 blaze version, same deal.
Some Googling on this same problem turned up the fact that TWRP 2.2.2.1 would correctly install the Amazon ROM, which in fact it did. Later builds must have some kind of bug, but if this only affects 1st gen KF's, probably not an urgent one.
Rebooted and back in business. :good:
Fastboot cable is the key ingredient in this situation.
Twrp versions 2.8.X.X have issues for some people, use 2.7.1.0 for custom Roms, 2.2.2.1 for stock.zips
Sent from my XT907 using Tapatalk

Categories

Resources