Kindle Fire HD 8.9 red triange after root. - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

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.

Related

[Q] Kindle Fire bricked, have factory cable but can't boot recovery, please help!

Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs

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!!

[Q] Kindle 8.9" stuck in Kindle Fire System Recovery

Hi,
I had my kindle rooted and a few weeks back the OS got updated automatically to a new version and my Home screen went black and I was unable to change the wallpaper. So I ran Stunts Wallpaper Fix but something must have gone wrong and I am now stuck in the:
Kindle Fire System Recovery
Your kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
The choices I have are:
Reboot your kindle
Reset to Factory Defaults
Choosing any of the two options eventually leads back to the above. So I purchased the fastboot cable but that apparently does not help either, as soon as I plug it into the kindle it will go back to the Kindle Fire System Recovery screen. I have ADB installed on my PC, however when starting the Kindle, my PC only recognizes the driver for about 2 seconds and displays it as "Jem-PVT-Prod-04" in the Device Drivers then that disappears as well.
I read many, many threads on this forum but don't seem to find anyone with this particular problem. Help very much appreciated.
Where did you get your factory cable?
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
eandjon said:
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
Click to expand...
Click to collapse
And before plugging it in, did you make sure your device was completely powered down (held the power button for 10-15 seconds)?
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
eandjon said:
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
Click to expand...
Click to collapse
You may have a bad factory cable, or the "factory cable" you have is not a factory programming cable.
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed your instructions and it seems to be working.
I am now receiving after rebooting the Kindle a dark screen saying "fastboot mode" in yellow.
In order to not screw things up again, what would be the best way forward?
I would suggest using kindle fire first aide and reflashing the stock system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed the steps mentioned for the Kindle First Aide and did a complete restore. My Kindle is now up and running!
Thank you sir for your excellent advice!
On another note if you try my wallpaper fix again, if it has some kinda error and bricks again, could u report the error to me? I always try to make it as safe as possible, and would like to know why my safeties didn't help in your case. Who knows, it might actually work this time since your os is closer to stock than before possibly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I installed your wallpaper fix and it worked without any issues at all. Thank you!
My kindle fire hd 8.9" rooted is doing the same
stunts513 said:
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My kindle is stuck in the exact same loop. What do you mean by 'install the driver...on the jem device'? ...I'm pretty green
Basically it means open the device manager on your PC, and plug you kindle in while its off, if it is indeed an 8.9" model, after it powers on you should see a device pop up briefly in the device manager called jem something, if it instead makes the noise like something connected an you don't see a jem device popup, then you probably have the drivers installed already. If you see the device pop up then quickly right click it and hit update drivers and point it to where you extracted my drivers and let them install. After that you should be able to use the fastboot command I mentioned to get I to fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It says "Windows encountered a problem...The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
Sent from my SGH-T999 using xda app-developers app
You must be on windows 8, you need to disable driver signature enforcement. Google it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It's rebooting now...fingers crossed!!!
IT WORKS!!!
Thank you so much Stunts!!! I'm now trying to do your programming, and I'm having a bit of a problem. The dos is telling me 'Could Not Find ...system32\framework-res.apk.orig doing prelim check...' followed by 'Your system partition is too low...' what am I doing wrong?
OK well the cannot find time isn't an error, its just extra output that I haven't disabled, that file it can't find is basically the cleanup process running to delete any files from a previous attempt, and if they aren't there you see that error. As for the disk space error, you should check your system partition to see how much space it has left on it, you will need around 40mb to use the wallpaper fix. You can attempt to disable the check if you are sure you have enough space, but if it doesn't have enough space you will end up with a softbrick'd device stuck in a boot loop until it has its system partition reflashed. Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app[/QUOTE]
Ok, recap...system is still rooted. I did a full system reboot, and the only other os that I had was go launcher. To try and get the script to run, I deleted Go launcher, along with widget picker, and live wallpaper. I tried to run "df/system" through COMMAND under administrator, and I tried the same command on my kindle through a terminal emulator and it said "not recognized" on pc, and "not found" on kindle. I'm sorry if this is annoying, and I appreciate the help.
---------- Post added at 05:32 AM ---------- Previous post was at 04:55 AM ----------
n/m, just found the df. on system it says 37M. What can I do for the other 3M?
---------- Post added at 05:49 AM ---------- Previous post was at 05:32 AM ----------
Ok...I realized I was asking stupid questions that I should resolve myself. For nOObs (like me) I went to this http://forum.xda-developers.com/showthread.php?t=619153 to get help with the adb shell. In doing so I was able to find my available space. I typed the command "df" and it showed all my available and used storage. I then went in to X-plore (root file management app) where I was able to change my user status to SU and go in to the systems folder and remove apps that were invaluable. Thanks for all the help stunts, if it wasn't weird I would send you some Christmas cookies lol.

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] 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.

Categories

Resources