Kindle Fire stuck in fastboot but unable to connect through fastboot - Kindle Fire Q&A, Help & Troubleshooting

Pushed the fbmode file to it and got it into fastboot, but the device doesn't show up in device manager even as unknown or other. In USB View it shows up as Android ADB Device and it did recognize that a kindle was connected in Virtual box but was unable to connect it to my linux VM.
Edit: After hours of looking for a solution it ended up being solved from this post, my KFU being in my download directory and not in the root of C.

Related

Help! Bricked my Kindle Fire

I attempted to root my Kindle Fire (which was running 6.2.2) using the Kindle Fire Utility v0.9.5. KFU appeared to run successfully and my Kindle was fine (started up OK). But, when I ran Root Check Pro, it showed KFU didn't succeed with rooting. I thought maybe KFU was unsuccessful because KFU v0.9.5 works on Fire firmware 6.3 and up (and not on 6.2.2).
Then, I tried to update the Fire firmware to 6.3.1 from the Amazon site, thinking I'd run KFU v0.9.5 again after the firmware update. I didn't think to uninstall any of the KFU installed rooting software (like superuser or TWRP) before trying the update because the root was unsuccessful.
My Fire started the update but stopped almost immediately and got stuck at the TWRP yellow-triangle logo. Also, my laptop (running Window 7) won't recognize the Fire when I plug it in with a USB cable.
When I set my laptop Device Manager to show hidden devices, "Android Phone" appears as a device. When I expand it, I see "Android ABD Interface". The Android Phone device displays for a few seconds and then disappears. If I shutdown my Kindle Fire and power it on again, the device manager does the same thing.
[FYI - I successfully rooted another Fire (though it was running 6.3) using KFU v9.0.5 on this same laptop so the Kindle Fire drivers for Windows were installed.]
Because of this behavior, none of the unbricking, KFU, or ABD utilities/commands are getting through to the my Fire. The Kindle Fire Unbricking utility, for example, will start but almost immediatley close the Windows Command window.
I don't know what to do when your laptop won't recoginize the Fire as a connected device. Is there any thing else I can try? I'd appreciate any help with this I can get!!
Go here
...and download FFF1.4
Mount your sdcard in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
If you get things working and decide you want to root again I would highly suggest side loading the superuser.apk. Root Check Pro might have discovered no root because the su.apk was missing (just a thought). This is an issue with KFU. I've rooted 4 kindles and not once has it installed the su.apk.
I also had to side load superuser and Google Play. Here is a great link on this forum to help with that:
http://forum.xda-developers.com/showpost.php?p=24312196&postcount=17
Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.
morgan4k said:
Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.
Click to expand...
Click to collapse
This is a tricky situation because you need to replace your device drivers, but you can't replace your drivers if you don't have access to them. I haven't come across a situation like this before last night so I wouldn't know how to fix your device manager issues.
You could however, try a different computer (easiest), OR create a bootable Linux LiveUSB thumb drive to boot from your laptop and set up the environment for issuing adb/fastboot commands. IMO, that would probably be the best route considering Linux's overall stability but it would definitely be the trickiest.
There are tutorials here for setting up Linux to use adb and fastboot and I'll add them as soon as I find them.
Setting Linux up for adb and fastboot can be tricky but there are plenty of Linux users here that can help with that.
Once you get everything set up, (re)install TWRP and continue wth the previously posted tutorial.
[Edit:] Actually, I have a better idea if you're using the LiveUSB and you wouldn't need to set up adb and fastboot.
Thanks for a great summary! Unfortunately even after sideloading superuser.apk, I still have read-only rights on / and the system directories under it that (would) allow me to copy over vending.apk. Yes, I am superuser when I try.
I have no problems becoming superuser, and OTA Rootkeeper works to switch back and forth.
The three things that do not work are write access to /system/app in order to switch out vendor.apk, mounting a drive as read/write, and from my PC am unable to use the adb remount command. All see outcomes of the same permissions issues.
Anyone seen this, and found the cause?
Thanks.
Are you positive your rooted download root checker verify root if you get red writing your not rooted

[Q] KFU can't see kindle

I'm currently trying to root my kindle with 6.2.2 with my windows XP Computer.
I've downloaded the most recent KFU and the 2 other files listed in the KFU post
KFU is currently located at c:\KFU
When I run the instal drivers.bat file It yells at me and tells me that the Google driver is unsigned. No problem, Plugged in the kindle and when the "install drivers" box came up I selected the C:\KFU\Drivers folder
Everything installed fine, When plugged in I get the USB Storage under USB devices and Anroid ADB Device under phones
when I run KFU it shows that ADB is offline
I've tried with the Mass storage stopped, still shows ADB offline.
Does anyone have experience getting KFU to work in XP?
Should I give up on the simple utility and do it from the CMD line with ADB? (I just feel safer having a script run becuase it gives less chance for error / skipped steps)
I've also tried on my mac, but sadly my older mac doesn't support KindleWater or ADB for that matter
PS as a background I have rooted 2 phones in the past and Custom ROM"d 1 of them.

Stuck on boot logo, want to unbrick

Hello,
So I have a kindle fire original and I tried rooting it with the KFU, but my computer froze I unplugged the device which caused it to be stuck on the logo. I have gotten Windows to recognize the device with the google usb driver, but adb does not list it as a device. I have altered both the android_winusb.inf file and the adb_usb.ini file to include the proper lines. I need help getting adb to recognize it so that I can unbrick it hopefully.
Open kfu, plug your kindle in, select option 1, then 1 again. If nothing happens within a few minutes power it off with a long press, then on again hopefully it will detect the kindle and set the bootmode to normal. http://forum.xda-developers.com/showthread.php?t=1850038 All else fails try Soupkit.

[Q] Kindle 2nd gen issue

Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.
Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk

cant connect to device via PC in CMD or ADB fire

i already installed kodi via the non PC es explorer method
im now trying to connect fire stick to PC
it shows up on device manager
in CMD adb devices lists the stick but adb connect then IP says it can not connect
In ADB fire device shows up as device, but when i try LLama options it says device not connect.
i have kodi set up with all the streams but need llama to get a shortcut on the home page and i cant connect
thanks for any help
Anyone any ideas ,says I have latest Google.USB driver installed
Can a mod lock this please ,all sorted

Categories

Resources