Related
My kindle fire is stuck in a boot loop (i think) it just keeps saying "Kindle Fire" then restarts then says the same thing and does this for ever in this state the computer doesnt find the device. I have a fastboot cable and it does put the device in to fastboot. Then I switch the fastboot cable with a regular kindle cable then it finds the device as otter2-prod-04. This all happened when I was trying to put twrp on it. And I think I rooted it.
If it shows up now as otter on your PC you just need to use fastboot to reflash the system image. If you are have an exclamation mark in the device manager you need to install the adb drivers for it when its in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for the reply but another problem that i forgot to mention is that neither adb nor fastboot find the device.
Check the device manager for an an exclamation mark then also, what fastboot command are you running? If you don't run the command with -i 0x1949 it won't detect it. So for a test try running "fastboot -i 0x1949 getvar product".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when I run that command it only says <waiting for device>. And also in device manager it has a exclamation mark.
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
bootloop
stunts513 said:
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Sounds like you will need a fastboot cable to attempt fixing that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jarjacksn said:
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Click to expand...
Click to collapse
You need to get a fastboot cord. There is some great info here http://forum.xda-developers.com/showthread.php?t=2271909
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
javipas said:
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
Click to expand...
Click to collapse
The fact that you don't know what device you have is a little disturbing. If your device said "otter" anything in fastboot, then you definitely do not have a Kindle Fire HD.
If that's the case, you flashed the wrong bootloader for your device and it is very unlikely that you will ever recover it.
The device IS a Kindle Fire, maybe not an HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
javipas said:
The device IS a Kindle Fire HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
Click to expand...
Click to collapse
Oh my...
Have a seat, my friend, because you're about to learn something...
In fastboot, if you were actually successful in sending the "fastboot devices" command (not possible on the HD), the output would be something similar to the following...
Code:
1234567890ABCDEF fastboot
...however, if you had a Kindle Fire HD7 and used the "fastboot getvar product" command, the output would be something like "TATE-XXXX-XXX". Respectively, the Kindle Fire HD8.9 would be "JEM-XXXX-XXX", the Kindle Fire 2 would be "OTTER-XXXX-XXX" and the original Kindle Fire would be "kindle".
Furthermore, only the original Kindle Fire and the Kindle Fire 2 (non-HD), have the model number D01400.
Now, whether you have an original Kindle Fire or a Kindle Fire 2 is still up for debate because you are clearly confused about what device you have in the first place. If you are lucky, and in fact have an original Kindle Fire, you will be able to restore it using Firekit. Unfortunately, considering the information available, I'm willing to bet that you have a Kindle Fire 2, and thus there is no way for you to restore your device.
Thanks for the clarification, that was perfect. I'm affraid I've got a Kindle Fire 2 then, so it seems there's nothing to do. Maybe in the future some method will appear to recover this second generation, who knows.
Greetings soupmagnet!
Easy Way to tell KF&KF2 from HDs: If it has a camera its a HD. Duh.
Sent from my Amazon Kindle Fire using xda app-developers app
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.
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
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