Develop Bugs

Red Screen + no fastboot

Hello all
I realize the one post below me is almost the exact same problem, but I am stuck. I just got my kindle hd 89 and I already have a red screen. Every option I try to use to get fastboot does not work, whether I'm using cmd and typing in the command, using KFFA, or KFHD 2.1. I think I ended up with a red screen by using FireFlash but without checking the right options. If it matters, I started with 8.4.6. I really want to unred-screen this, so any help would be appreciated! Thanks.

hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL

GermanJPL said:
hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL
Click to expand...
Click to collapse
I used KFHD_SRTv2.1- 8.1.4 and I am going to try KFHD_SRTv2.0- 8.1.3 , but the link to KFHD_SRTv1.3-8.1.2 in this thread appears to be dead. Anyone have a mirror?
And yes, the issue I'm having with KFFA, the SRT, and even when I am just trying to boot into fastboot via cmd, is that it says "waiting for device" and then when I plug it in it says "KindleFire" (in orange) for a second or two before switching over to the red screen.
I was able to do fastboot before the red screen showed up, so I doubt it has anything to do with drivers.

hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL

GermanJPL said:
hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL
Click to expand...
Click to collapse
I do not understand what you are saying.

I will say that when I plug the Kindle in, my laptop makes the "device connected" noise followed quickly by the "device disconnected" noise and it even shows up in the device manager for the split second before it turns red.

What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
At first it showed up under "portable devices" as an "unknown device" and I managed to uninstall the drivers in the hopes of re-installing them, and then the next time it showed up under "portable devices" as "jem-004..." etc. or whatever the code name for this type of kindle is. I think it just shows up as the category "other devices" now, but I do not have the kindle handy.

Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Your drivers just saved my life dude. Thank you so much. Gotta figure out the next step now.

stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
oh but seriously dude running CM10.1 now and could not be happier thank you so much.

Your solution to fastboot and redscreen issue
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers

Hello I am very sorry to ask for help, I have this same problem and can help stunts513 beatmastermcfly, my kindle has a red screen and make everything after root, and the worst part is that my laptop recognizes it as unknown device which driver you downloaded work for you
:crying:

Dead Kindle Fire HD 8.9
Okay, due to my own errors while using fastboot on my KF, it no longer does *anything* when I try to turn it on. I can't reenter fastboot, since ADB no longer recognizes the device (which of course, it can't, since the device doesn't start). I mean, it does *nothing* (although the hardware is in great shape).
Am I, as I suspect, just dead in the water here? I have the recovery files, but without ADB or fastboot, I no longer have a way to load them.
Should I just start using the KF as a doorstop now? Or is there some obscure solution to this mess?
rogerlig

Someone correct me but figuring concludes that the red screen is because amazon blocks tablet when it comes to a stolen board or losses , my I get a tablet I did not say much , so that the repaired but through the serial number of a personal contact amazon and they said it was lost and I imagine blocked the operating system so I could not use the tablet

Please Help!
Meeperman said:
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers
Click to expand...
Click to collapse
Did you ever find a solution? Thanks!

On a win7 x64 box you need adb (there is a quick version) installed. The kfhd drivers. USC disabled. AND MOST IMPORTANTLY YOU MUST RUN ADB FROM A COMMAND PROMPT ORIGINATED FROM THE ADB FOLDER. (shift+right click and select "run command prompt from here)

Did you ever get your kfhd 8.9" to work. Everything youve said so far is the exact replica of my kindle. I know its like 7 years later but this is still a problem for people

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

Kindle Fire HD 8.9 red triange after root.

Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?

Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.

OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.

In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.

Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.

Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.

Please help to unbrick---stuck in red Screen and can't get into fastboot

Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)

z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?

I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.

Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?

Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.

Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？

stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？

It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk

Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app

[Q] Why does my KF2 not display fastboot mode?

Hey all, I have a kindle fire 2 that I have been trying to restore and reset using kindle first aide, http://forum.xda-developers.com/showthread.php?t=2096888
I purchased a factory cable from skorp and when I plug my KF2 in with it, it simply says "kindle fire" on the screen. It is listed in device manager as Android Phone, and it says the Android ADB Interface is working properly. Yet when i type "abd devices" in cmd prompt nothing shows up, and when I try to use the first aide tool it says its waiting for a device.
Does anyone have any ideas on what may be wrong with it?

Can you verify that pin 1 and four are shorted on the micro USB side?
Sent from my XT907 using xda app-developers app

mrkhigh said:
Can you verify that pin 1 and four are shorted on the micro USB side?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes they are, I tried the cable on my mom's kindle as well and the screen said kindle fire fastboot on hers. Device manager recognizes hers the same way it recognizes mine though.

If it was in fastboot mode then "adb devices" wouldn't show anything. When in fastboot mode, use fastboot commands, try this out:
Code:
fastboot -i 0x1949 getvar product
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

try..
Marinski94 said:
Yes they are, I tried the cable on my mom's kindle as well and the screen said kindle fire fastboot on hers. Device manager recognizes hers the same way it recognizes mine though.
Click to expand...
Click to collapse
Try upgrading the factory amazon firmware first to repair fastboot on the device. I've had this happen before on a customers kindle. I was able to just grab a rootable amazon firmware update, update it, then continue to root, twrp and flash with a new rom.

[Q] [Help] Red Screen Bricked KF2 [Have Fastboot Cable]

So I managed to brick my rooted Kindle Fire 2nd Generation after trying to install a rom with TWRP app. Anyways, I have a fastboot cable, and the correct drivers and Android SDK, but when I plug in my cable, turn off the device (holding button for 20 seconds), then turn back on, it still goes to red screen immediately after the brief kindle fire logo, exactly the same without fastboot cable. What am I dong wrong?
Would really appreciate any help .
-Thanks,
Jacoobyman

You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
No it does not detect it at all in device manager. not even briefly. :/

That sounds bad, I don't trust windows too much for debugging but I'm guessing Linux would say the same thing, what were you trying to flash that caused this?
Sent from my Amazon Kindle Fire HD using Tapatalk