Related
I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
jdswain said:
I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
Click to expand...
Click to collapse
I think you have a dead battery....
http://forum.xda-developers.com/showthread.php?t=1623244
FWIW, I've noticed a number of Mac fastboot problems being posted here lately. I tried this for myself to see what was going on. Although it will respond to 'fastboot devices' and 'fastboot getvar product' commands, it stalls while trying to send the image to the KF. I've tried several different copies of fastboot and they all do the exact same thing for me. No "fastboot flash" or "fastboot boot" commands will get past the sending stage.
VMWare might also have issues with fastboot as I've heard some rumblings about that as well. I'm a Parallels Desktop user and I've never really encountered any problems along these lines in my Windows or Linux VMs.
I think your next best bet is to build a Ubuntu Live USB system on a thumb drive and try using that on your Mac.
I've been speaking with kinfauns about this fastboot/Mac problem that's come up recently. I've been using Mac since I rooted my Kindle Fire and I've never had a problem with it in regards to adb or fastboot.
Have you installed any OSX software updates lately?
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
.................FIGURED IT OUT!..............................
Much thanks to the pooch who spent hours helping me troubleshoot.
What we (he) did, as far as I remember, hopefully this can be of some service to someone else out there.
1) Figured out that trying all of this on a Virtual Machine is not a good idea!
2) I somehow broke the bootloader in my first attempt, so none of my computers were recognizing the KF.
3) Created a Pendrive to run Linux (ubuntu). Here Requires a USB drive formatted Fat16/Fat32/NTFS, minimum of 2 gb.
4) Once I got Linux running, installed SoupKit.
5) Went through a few tries of booting, rebooting, into recovery mode until the Kindle flickered back to life!
6) Followed prompts on SoupKit to install TWRP, updated TWRP, install FireFireFire, install Android 4.2.
Good luck, I am happy to answer any questions - though I am no means an expert now.
What I have tried...more info
More Information:
I am running Windows7 in a VirtualBox on an iMac.
I bricked the Kindle a few weeks ago, after messing with it then, I bought a factory fastboot cable. Still no dice.
I have tried all turning on and off computer, on and off Kindle with it disconnected, connected, going through the KFU 4 seconds after starting the Kindle. Letting the Kindle's battery die, recharging.
I have deleted .android folder, reinstalled drivers, re-downloaded KFU.
I have tried on a different computer (Windows XP) The Kindle is also not recognized there.
I have tried booting into Ubuntu (however in the directions there, it said the FireKit is for more "serious" issues than my soft brick.
I am sure there is some small detail I am missing, but I have not been able to find it - and I am not knowledgeable enough to properly diagnose the problem. Again thanks for any help.
kyleboyd said:
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
Click to expand...
Click to collapse
Sometimes KFU will show as Unknown even though it's really fine. I had the same issue as you. Try switching boot mode to Normal and see if that fixes it, it worked for me.
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
hemmulde 1st
zastava750 said:
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
kyleboyd said:
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
Click to expand...
Click to collapse
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.
I've tried that as well...
Just so I am totally clear, this is what I did in relation to those instructions:
Opened Command Prompt - set the directory to C:/kfu/tools
Typed "fastboot -i 0x1949 getvar product" (with out the quotations, obviously)
<waiting for devices>
I plugged Kindle in, it powers on and the frozen logo pops up.
I also tried "fastboot -i 0x1949 oem idme bootmode 4000" and "fastboot -i 0x1949 oem idme bootmode 4002"
According to the guide it often takes multiple tries, I have done it over and over again.
I have also tried different orders of code, plugging in Kindle, and powering on and off.
Am I doing something wrong? Is there a specific code for my Kindle? (Not -i 0x1949)
Thanks!
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1660636
Reinstall the driver then use kfu to reset the boot mode to normal.
Drivers?
I did try this: http://forum.xda-developers.com/show....php?t=1660636
When I get to the part about the Device Manager, I am stuck, as nothing shows up (I suspect something do with drivers)
Thepooch said:
Reinstall the driver then use kfu to reset the boot mode to normal.
Click to expand...
Click to collapse
By reinstall drivers do you mean clicking on "install_drivers" in the KFU folder? I have tried that.
Is there another method of uninstalling and installing drivers? Sorry if that is a dumb question!
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Still not working
Thepooch said:
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Click to expand...
Click to collapse
Thanks for the quick reply.
So I am on a Win7 and/or a Windows XP. Currently on both systems, when I plug it into the computer, with the Device Manager open, nothing happens other than the Kindle turning itself on.
Before it froze up, I saw it in device manager as Android ADB interface, and before doing anything at all, saw it as the default Kindle Fire.
On the Win7 system, I have rerun the driver installation bat over and over and over again, with absolutely no results.
On the WinXP, I have tried it, and for the life of me can't get it to install (it says install failed (Unsigned)). I never connected the Kindle up to this computer before it froze up, so I wonder if that is somehow causing the problem (it is trying to update drivers that don't exist?)
Am I doing something wrong with this? Can I uninstall or delete drivers, and totally start over?
If you are using a WinXP you must install driver manually.
Drivers?
zastava750 said:
If you are using a WinXP you must install driver manually.
Click to expand...
Click to collapse
How do I do that, when the Kindle does not show up as being connected? All the guides I have found start off with accessing from the Device Manager. My Kindle does not show up in the Device Manager...
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Windows 7 - No Dice
Thepooch said:
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Click to expand...
Click to collapse
Yeah so I have a Windows7. I have reinstalled the drivers (by clicking on the install_drivers.bat file in the KFU) over and over again, and I still do not get any recognition on the computer, or in the Device Manager when I plug in the Kindle.
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Thepooch said:
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Click to expand...
Click to collapse
Thanks! I would be willing to give it a shot (teamview I mean) if you are willing.
I tried the Firekit before I began this thread, but I kept getting stuck trying to run the tool after booting into ubuntu. Perhaps that is a different thread topic, but I am more than willing to put more work into figuring that out, if it could be the key to unlocking this stupid thing.
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Nixnaegie said:
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Click to expand...
Click to collapse
Glad to know I'm not alone - misery loves company! Solidarity my friend.
I wish I could tell you I'd solved it, but alas, I have not. I'm still working on it, I'll keep you updated if I have any breakthroughs!
Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.
chickeninferno said:
Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.
Click to expand...
Click to collapse
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.
soupmagnet said:
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.
Click to expand...
Click to collapse
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
I've run into relatively the same problem with my HD8.9 several times while testing scripts but I've always been able to enable fastboot after rebooting using 'getvar product'. The difference in my case, is that I was always using Linux. You may want to set up a LiveUSB and install the SoupKit from the Dev section and try again to see if it makes a difference. SoupKit is not required, of course, but it is definitely recommended if you're not very familiar with Linux.
chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.
chickeninferno said:
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.
Click to expand...
Click to collapse
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!
Glorious Success!
So I ended up doing a combination of the two solutions and since I know how frustrating this was here's how I did it just in case someone stumbles upon this.
How it magically worked:
1.) Inside of Linux Mint, I installed Soupkit
2.) In terminal i typed "fastboot -i 0x1949 getvar product"
-----The kindle reacted for the first time in a long time and went into fasboot mode. Since I had no idea where to put the boot.img or recovery.img in linux to send them but the fastboot or adb commands, I decided to risk it and move to windows.
3.) I unplugged the kindle
4.) Booted into Win 7 x64
5.) The fastboot wasn't working in windows but I checked device manager and the exclamation mark was lingering. I manually picked the driver of amazon.com/kindle and it installed the adb composite device. Fastboot now works in windows.
5.) ran SR Tool.bat in the KFHD_SRT_2.1 folder and chose option 1 (Enable Fastboot)
-----Success
6.)in SR Tool i chose option 4 (erase cache and userdata)
----Took ~4 minutes but success
7.) in cmd I navigated to my sdk platform tools folder by typing "cd C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools"
8.) I downloaded the boot.img and recovery.img linked here (http://forum.xda-developers.com/showthread.php?t=2011126) and placed them into C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\
9.) in the cmd from step 7 I sent the following commands "fastboot -i 0x1949 flash boot boot.img" and "fastboot -i 0x1949 flash recovery recovery.img"
----Great Success
10.) In SR Tool I chose option 6 (reboot normally)
-----It looped for ~2 minutes but eventually booted like normal but the SR_Tool asked me to make sure that adb was enabled before clicking enter. I enabled it on the device but SR Tool still didn't seem to see that I had done it. Since it rebooted normally, I didn't really care.
11.) The kindle upgraded itself after I set it down to type this response to 8.4.3
I probably could have easily done this is linux, but I didn't know where to put the boot.img and recovery.img. Also, I'm guessing that the system.img is put back on the device when I used the KFHD SRT but I'm not sure.
Now I'm going for round two to get CM 10.1 put on this thing!
Thanks for all of the help. I really thought that I had actually managed to brick the nearly unbrickable kindle fire 8.9"
Congrats on your success and thanks for sharing the experience!
I think one problem with Windows is that, "fastboot -i 0x1949 getvar product" does not work very well on putting the kindle to fastboot if the device driver is not properly installed, kindle will simply bypass the fastboot step and continue(and hang), the whole situation is a dead loop on Windows if the fastboot driver is having problem and the kindle can't boot into the ROM, and to make things even worse, there is no factory cable for HD8.9
So the SoupKit is a real life saver here.
I had the same sort of driver problem after I installed the second bootloader. For me the simple fix was to go into device manager (In Windows 7), uninstall whatever driver was there with the yellow triangle and then reinstall the official kindle adb driver. Congrats on getting it fixed though. It's a great feeling, I know.
Worked form me too!
Brandonrz said:
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!
Click to expand...
Click to collapse
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.
DBMmn said:
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.
Click to expand...
Click to collapse
I'm so glad I could help, it was so frustrating for me.
Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.
Tyler9097 said:
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.
Click to expand...
Click to collapse
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk
Brandonrz said:
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!
Tyler9097 said:
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!
Click to expand...
Click to collapse
Power off the Kindle, type fastboot -i 0x1949 getvar product , plug in the Kindle when you get <waiting for device>, and flash the 2nd bootloader, recovery, and freedom-boot images as directed in Hashcode's thread. Skip to step 5 after downloading the files, as we're already in fastboot mode at this point.
Also, Windows 10 enforces driver signatures, so you'll need to disable that before proceeding with the Kindle driver installation.
Sent from my Amazon Jem using XDA Labs
Hey everyone
I think I've just bricked brand new Kindle Fire HD 8.9 :/
So, I'm new in rooting and I tried to install custom rom Cyanogen Mod 10.1 following the instructions from there: http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/ .
After rooting Kindle, installing 2nd bootloader and TWRP my Kindle rebooted. It showed up Kindle Fire logo, first yellow then blue one. But after that nothing happened, it stucked at booting. So I entered to recovery mode by holding down volume up button and because of my stupidity I thought backing up system and restoring it will get me able to enter to original Amazon's system. After restoring system and rebooting worse thing happened. Logo while booting didn't turn from yellow to blue, it just stucked in yellow logo like it freezed. Now I can't enter anywhere in my Kindle, even in recovery mode and after plugging Kindle to PC through USB cable PC doesn't see Kindle. I think maybe using fastboot cable will help but I'm not sure about that, so I'm asking You: Is there anything I can do to restore my Kindle? And the fastboot cable will work with this software: http://forum.xda-developers.com/showthread.php?t=2011126?
Thanks for any help
Sorry for my bad english
Gunter_Time said:
Hey everyone
I think I've just bricked brand new Kindle Fire HD 8.9 :/
So, I'm new in rooting and I tried to install custom rom Cyanogen Mod 10.1 following the instructions from there: http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/ .
After rooting Kindle, installing 2nd bootloader and TWRP my Kindle rebooted. It showed up Kindle Fire logo, first yellow then blue one. But after that nothing happened, it stucked at booting. So I entered to recovery mode by holding down volume up button and because of my stupidity I thought backing up system and restoring it will get me able to enter to original Amazon's system. After restoring system and rebooting worse thing happened. Logo while booting didn't turn from yellow to blue, it just stucked in yellow logo like it freezed. Now I can't enter anywhere in my Kindle, even in recovery mode and after plugging Kindle to PC through USB cable PC doesn't see Kindle. I think maybe using fastboot cable will help but I'm not sure about that, so I'm asking You: Is there anything I can do to restore my Kindle? And the fastboot cable will work with this software: http://forum.xda-developers.com/showthread.php?t=2011126?
Thanks for any help
Sorry for my bad english
Click to expand...
Click to collapse
(if you're bricked, you need fastbootcable?). that what i was told anyways
OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I did everything like you said, and voila! Kindle works fine now
Thanks for the help
stunts513 said:
OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hey i cannot kind a download for this tool anywere i screwedup my bootloader and recovery img.. now i need help my device only recognized for 3 seconds.
then loop loop and stock recovery mode which dont work.
plz help pm me a link or anything. ugh i bricked this uggh
Download kindle fire first aid or system restore tool, they come with fastboot and adb.
Sent from my Amazon Kindle Fire HD using Tapatalk
vIgGeN7 said:
hey i cannot kind a download for this tool anywere i screwedup my bootloader and recovery img.. now i need help my device only recognized for 3 seconds.
then loop loop and stock recovery mode which dont work.
plz help pm me a link or anything. ugh i bricked this uggh
Click to expand...
Click to collapse
Here is a tutorial that will show you how to install a 2nd bootloader and TWRP recovery.
2nd bootloader/TWRP install http://forum.xda-developers.com/showthread.php?t=2128175
Then choose a ROM made for the 8.9 Kindle Fire HD only and flash it.
If you wish to go stock then flashing the appropriate images in fastboot will be your plan. This requires setting up some SDK tools in your environment.
SDK setup video http://m.youtube.com/watch?v=oaNM-lt_aHw
KFFA is another option as well.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Kindle Fire HD 8.9 Bricked
Can someone please provide me with some information. I tried to update the recovery for my Kindle Fire HD 8.9 running on cm10.2 using flashify which I found out now was a very lazy and dumb thing to do. Now my device is bricked its stuck at the white and orange kindle logo, my computer only recognize it for a split second and I can't boot into recovery.
My question to the experience members is if my device is done for or can the factory cable restore it? I tried creating one but it didn't get my device into fastboot mode and I also heard that it isn't compatible with the 8.9 series, I would like to know how true this is.
Thanks a lot.
You don't use a fastboot cable with a 8.9. It should when plugged in while off show up for a brief moment as a jem device. In this brief moment you must have the device manager open and right click the jem device hit update drivers and point it to where you would have downloaded and extracted the drivers in my signature. Once you manage to get the drivers installed shut off the kindle and open a command prompt that's CD'd into the directory of the fastboot command and run
Code:
fastboot -I 0x1949 getvar product
it should say waiting for device, at this point plug the kindle in with a normal cable and it should go into fastboot. I recommend a ubuntu live CD for this procedure because you don't have to deal with the driver issue, instead you just have to install the fastboot binary from the repo but it is fairly easy.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't use a fastboot cable with a 8.9. It should when plugged in while off show up for a brief moment as a jem device. In this brief moment you must have the device manager open and right click the jem device hit update drivers and point it to where you would have downloaded and extracted the drivers in my signature. Once you manage to get the drivers installed shut off the kindle and open a command prompt that's CD'd into the directory of the fastboot command and run
Code:
fastboot -I 0x1949 getvar product
it should say waiting for device, at this point plug the kindle in with a normal cable and it should go into fastboot. I recommend a ubuntu live CD for this procedure because you don't have to deal with the driver issue, instead you just have to install the fastboot binary from the repo but it is fairly easy.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thanks a lot man I completely gave up and was ready to order the motherboard. Now my kindle fire hd is up and running cm11 :good: :laugh:
unbrick for dummy
Kemoid said:
Thanks a lot man I completely gave up and was ready to order the motherboard. Now my kindle fire hd is up and running cm11 :good: :laugh:
Click to expand...
Click to collapse
stunts513
Can you explain step by step for techno-peasants how to fix my Kindle fire HD 8.9?
It flashes the words "kindle fire" for 14 seconds then goes dark and won't to anything else. I tried holding in the power button for 20; 30;40;60 seconds and that whole thing. I tested the charge in the battery. I'm past the easy fixes.
I'm at the point Kemoid was at above, ready to throw my Kindle Fire away and buy a new one.
I need the idiot proof directions that start with words similar to "Go to ww.somemagicURLwhereIcangetwhatIneedtodiagnoseandfixmyKindefireHD8.9.com and download xxxxxxxxxxxxx.xxx to your computer, then....."
Assume downloading an app reaches the limits of my technical comfort level.
Can you help me?
JoyousM said:
stunts513
Can you explain step by step for techno-peasants how to fix my Kindle fire HD 8.9?
It flashes the words "kindle fire" for 14 seconds then goes dark and won't to anything else. I tried holding in the power button for 20; 30;40;60 seconds and that whole thing. I tested the charge in the battery. I'm past the easy fixes.
I'm at the point Kemoid was at above, ready to throw my Kindle Fire away and buy a new one.
I need the idiot proof directions that start with words similar to "Go to ww.somemagicURLwhereIcangetwhatIneedtodiagnoseandfixmyKindefireHD8.9.com and download xxxxxxxxxxxxx.xxx to your computer, then....."
Assume downloading an app reaches the limits of my technical comfort level.
Can you help me?
Click to expand...
Click to collapse
Your in a bootloop. Just use the factory restore tool for the 8.9 and your USB cord.
I'm thinkin your kernel is messed up, probably just needs reflashing, I agree with LinearEquation, you just need to use the system restore tool or kffa and it should reflash that, if you can get into fastboot though you might need to wipe your boot partition. Try the SRT first though.
My kindle still brick
mr.galaxys said:
(if you're bricked, you need fastbootcable?). that what i was told anyways
Click to expand...
Click to collapse
thank for your share, but my kinlde fire hd 8.9 still brick
Before, i rooted and install TWRP . But, I install stock rom form amazon ( 8.5.1) and after, I update superuser and restart it. red screen appear. And now, I try anything to unbrick but nothing change.
you can see my brick youtube.com/watch?v=kJzsZKF5OUk ( I dont enough post to up youtube)
so, Please help me this case.
Thank you very much !!!
Hi, I just recently got a Kindle Fire HD 8.9 and decided that I wanted to flash CM 11 onto it. Well I followed the steps of a tutorial up until the point where I have to flash a second bootloader and TWRP Recovery. I flashed and installed the script, but accidentally clicked the option to turn off and go into recovery mode or something. Now my Kindle is stuck in a boot loop where the Fire in kindle fire is red. The logo stays for a couple seconds then the kindle just restarts itself.
I've tried to go into fastboot mode using the command prompt "fastboot -i 0x1949 getvar product" but when I connect my device, the computer does not see a thing. I do not know what else I can do at this point. I've looked up and read countless forums, but nothing has worked. Is there any way for me to recover my Kindle?
If it hasn't ever been in fastboot mode before while hooked up tot hat PC and had the drivers installed then it is precisely that reason the command is not working, because the drivers ade not installed. You can try to install them if that is the case, you just have to be fast and update the driver while the device is first plugged in and showing up for a brief moment. I personally recommend using a ubuntu 13.10 CD for this kinda case because of how Linux's driver system works you Don,t have to do anything, the driver already loads up when you plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk