[Q] Kindle 2nd gen issue - Kindle Fire 2 Q&A, Help and Troubleshooting

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

Related

Kindle Fire is stuck at boot screen, (no animation). Help!

Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...
b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.
updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7
dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.
I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"
I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.
You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.
Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..
I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )
A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..
I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*
Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.
u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick
If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk
In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#

!!!(Q) Help bricked kindle fire 6.3

okay so i was trying to root my kindle fire and i didnt get su any where so then i tryed to install cwm and now its stuck at the yellow triangle and it wont go into recovery and it also will not connect to adb i need hellp ASAP
Install drivers as ADB composite with the Android SDK and then use this to change the bootmode
The link you posted is not working due to the period in the URL at the end.
Do not afraid. I have got the same experience Let God bless the search button
http://forum.xda-developers.com/showthread.php?t=1568340
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Click to expand...
Click to collapse
My kindle got the 6.3 update -solved!!
This has got to be one of the fastest ways I have rooted 6.3 kindle update
i went on line here http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html
downloaded the new kindle fire utility and ckick on Install permanent root with super user. got rooted in about 2 minutes with no trouble at all
thanks everyone for your help but i solved it what i was doing was unsing the kindle fire utility trying to instal latest firefirefire but it just sat there and so i just went into the utility and reinstaled the twrp and it booted normal!!
Bricked Kindle
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
ChrisKenison said:
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
Click to expand...
Click to collapse
If you get the yellow triangle logo to come up, then it's probably in fastboot mode. If you reboot it while it's connected to your computer and you get some device detection beeps from Windows, it's likely to be a driver issue. Look here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You might want to read the first post in that thread too.
Watch carefully as the device boots up and you get the yellow triangle logo. If that boot logo comes up and stays there, it's in fastboot. If the boot logo comes up, the screens blacks out, and then the boot logo comes back up (dimmer) then it's either trying to get into recovery or booting into the OS and failing.
I would try setting the bootmode to normal in KFU and when it says "<waiting for device>" reboot the Kindle Fire. Since you have FFF, the fastboot program on your computer will wait for the Kindle Fire's FFF bootloader to get into temporary fastboot and reset the bootmode when the KF is ready.
But, the computer won't even recognize there is a device connected to it
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
And because its not recognized in the device manger, kfu isn't picking it up
Sent from my Galaxy Nexus using xda premium
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
If you can't get the drivers working with the KFU distribution, you'll have a harder time with the SDK. They are the same drivers, but KFU has an updated, Kindle Fire specific .inf file for the driver and also installs the .ini file in the .android folder that you'll need. I don't know what you see in the device manager, but if you don't get one of the devices shown in the post I referred to earlier, I would try another Windows machine. You won't be able to do anything without getting it to detect your KF and load the proper drivers. If you are more adventurous, you could try pokey9000's Firekit (search for it) and try using linux to send it fastboot commands.
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
yea mine is stuck on the firefirefire boot screen
ChrisKenison said:
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
Click to expand...
Click to collapse
Well, if you can't get any of those scenarios to work out, maybe it's a hardware issue. It might be something as simple as a bad USB cable or something more serious within the KF itself. I've never had a problem with Windows or Linux not seeing the KF, so my hands on experience in this regard is limited... my KF has never been broken to that degree. I'm always curious to see what's going on with people's KF when they say nothing works, but my KF has never given me that opportunity.
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
Sometimes in order to install the correct driver you need to delete the original from your computer because it will continue to attempt to revert to the default but beforehand try rebooting your computer and the kindle
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
mistaanime said:
yea mine is stuck on the firefirefire boot screen
Click to expand...
Click to collapse
Run the kf utility again install twrp and fff again

[SOLVED!] Kindle Fire Bricked on Logo Startup - KFU v0.9.9

I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
.................FIGURED IT OUT!..............................
Much thanks to the pooch who spent hours helping me troubleshoot.
What we (he) did, as far as I remember, hopefully this can be of some service to someone else out there.
1) Figured out that trying all of this on a Virtual Machine is not a good idea!
2) I somehow broke the bootloader in my first attempt, so none of my computers were recognizing the KF.
3) Created a Pendrive to run Linux (ubuntu). Here Requires a USB drive formatted Fat16/Fat32/NTFS, minimum of 2 gb.
4) Once I got Linux running, installed SoupKit.
5) Went through a few tries of booting, rebooting, into recovery mode until the Kindle flickered back to life!
6) Followed prompts on SoupKit to install TWRP, updated TWRP, install FireFireFire, install Android 4.2.
Good luck, I am happy to answer any questions - though I am no means an expert now.
What I have tried...more info
More Information:
I am running Windows7 in a VirtualBox on an iMac.
I bricked the Kindle a few weeks ago, after messing with it then, I bought a factory fastboot cable. Still no dice.
I have tried all turning on and off computer, on and off Kindle with it disconnected, connected, going through the KFU 4 seconds after starting the Kindle. Letting the Kindle's battery die, recharging.
I have deleted .android folder, reinstalled drivers, re-downloaded KFU.
I have tried on a different computer (Windows XP) The Kindle is also not recognized there.
I have tried booting into Ubuntu (however in the directions there, it said the FireKit is for more "serious" issues than my soft brick.
I am sure there is some small detail I am missing, but I have not been able to find it - and I am not knowledgeable enough to properly diagnose the problem. Again thanks for any help.
kyleboyd said:
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
Click to expand...
Click to collapse
Sometimes KFU will show as Unknown even though it's really fine. I had the same issue as you. Try switching boot mode to Normal and see if that fixes it, it worked for me.
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
hemmulde 1st
zastava750 said:
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
kyleboyd said:
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
Click to expand...
Click to collapse
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.
I've tried that as well...
Just so I am totally clear, this is what I did in relation to those instructions:
Opened Command Prompt - set the directory to C:/kfu/tools
Typed "fastboot -i 0x1949 getvar product" (with out the quotations, obviously)
<waiting for devices>
I plugged Kindle in, it powers on and the frozen logo pops up.
I also tried "fastboot -i 0x1949 oem idme bootmode 4000" and "fastboot -i 0x1949 oem idme bootmode 4002"
According to the guide it often takes multiple tries, I have done it over and over again.
I have also tried different orders of code, plugging in Kindle, and powering on and off.
Am I doing something wrong? Is there a specific code for my Kindle? (Not -i 0x1949)
Thanks!
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1660636
Reinstall the driver then use kfu to reset the boot mode to normal.
Drivers?
I did try this: http://forum.xda-developers.com/show....php?t=1660636
When I get to the part about the Device Manager, I am stuck, as nothing shows up (I suspect something do with drivers)
Thepooch said:
Reinstall the driver then use kfu to reset the boot mode to normal.
Click to expand...
Click to collapse
By reinstall drivers do you mean clicking on "install_drivers" in the KFU folder? I have tried that.
Is there another method of uninstalling and installing drivers? Sorry if that is a dumb question!
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Still not working
Thepooch said:
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Click to expand...
Click to collapse
Thanks for the quick reply.
So I am on a Win7 and/or a Windows XP. Currently on both systems, when I plug it into the computer, with the Device Manager open, nothing happens other than the Kindle turning itself on.
Before it froze up, I saw it in device manager as Android ADB interface, and before doing anything at all, saw it as the default Kindle Fire.
On the Win7 system, I have rerun the driver installation bat over and over and over again, with absolutely no results.
On the WinXP, I have tried it, and for the life of me can't get it to install (it says install failed (Unsigned)). I never connected the Kindle up to this computer before it froze up, so I wonder if that is somehow causing the problem (it is trying to update drivers that don't exist?)
Am I doing something wrong with this? Can I uninstall or delete drivers, and totally start over?
If you are using a WinXP you must install driver manually.
Drivers?
zastava750 said:
If you are using a WinXP you must install driver manually.
Click to expand...
Click to collapse
How do I do that, when the Kindle does not show up as being connected? All the guides I have found start off with accessing from the Device Manager. My Kindle does not show up in the Device Manager...
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Windows 7 - No Dice
Thepooch said:
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Click to expand...
Click to collapse
Yeah so I have a Windows7. I have reinstalled the drivers (by clicking on the install_drivers.bat file in the KFU) over and over again, and I still do not get any recognition on the computer, or in the Device Manager when I plug in the Kindle.
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Thepooch said:
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Click to expand...
Click to collapse
Thanks! I would be willing to give it a shot (teamview I mean) if you are willing.
I tried the Firekit before I began this thread, but I kept getting stuck trying to run the tool after booting into ubuntu. Perhaps that is a different thread topic, but I am more than willing to put more work into figuring that out, if it could be the key to unlocking this stupid thing.
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Nixnaegie said:
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Click to expand...
Click to collapse
Glad to know I'm not alone - misery loves company! Solidarity my friend.
I wish I could tell you I'd solved it, but alas, I have not. I'm still working on it, I'll keep you updated if I have any breakthroughs!

[Q] Non-rooted Kindle HD 8.9 not found in device manager

Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
ray8888888 said:
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
Click to expand...
Click to collapse
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
stunts513 said:
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
Click to expand...
Click to collapse
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
ray8888888 said:
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
Click to expand...
Click to collapse
it should be fine to use now, that's just stock rooted, you might wanna consider disabling ota's or flashing another rom onto it but its fine how it is.

Kindle Fire HD 7 bootloop and no ADB

Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Maric98 said:
Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Click to expand...
Click to collapse
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
stunts513 said:
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
Click to expand...
Click to collapse
Thanks for your reply!
I have actually tried to holding down the volume button when it turns on but it doesn't do anything. It's like the device is ignoring me and just keeps looping.
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
That actually sounds really difficult.
Just to be clear there is no way to do this on just Windows 7 or OSX? Instead of installing Ubuntu ( which I am not familiar with ). Also could you explain a bit more about the functions of those fastboot cables / adapters because I don't really understand what they do and are you sure those will work with the status of my device? I assume as soon as I get that cable / adapter I Need to plug my device in to the computer and have to get it working via some commands? But anyway is there a way I can stick to windows or mac OSX ( Which I did not use before in the rooting process )
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks I hope my mac will get the job done. It would make it a lot more easier than going linux I think.
Ok. Ill try it on my mac. I will now download Android SDK and place the extracted file on my desktop. I guess I install all tools and all that. And keep you up-to-date.
I downloaded the SDK and placed the folder to my desktop and opened the SDK manager by going to sdk / tools / android and installed SKD tools and SDK platform Tools. Although when i downloaded it it gave me a log that told me something like '' Stopping ADB server failed (code -1). '' And now I get a red checkmark. I don't know if getting a red checkmark is actually good. And i don't know if it's installed now and if the error message matters.

Categories

Resources