This is where my Kindle fire is at:
-Boots up using power button
-Displays Kindle Fire(orange) logo for about 5 secs
-Display goes blank for about 3 secs
-Loops in this manner indefinitely.
-Pressing Power & Volume Up during boot up puts into a specific mode where screen is blank and
PC would detect Kindle at Amazon Tate (In portable devices) and another device as ADB composite.
- When I run adb, it shows the device name and says unauthorized.
I have tried various methods, like plugging in HDMI cable, OTG mouse but there is no way to enable ADB on the tablet as there is no display.
-BTW, bootloader is locked on this tablet, I made fastboot cable but it doesnt work. I was never able to put tablet in fastboot
I basically bricked tablet by installing 7" ROM on 8.9" tablet. I dont know how it would break the tablet but it did. My tablet was rooted before I bricked it.
Tablet is worthless even if I fixed it but I am just curious if there is a way to fix it. Any help is much appreciated.
harshil22 said:
This is where my Kindle fire is at:
-Boots up using power button
-Displays Kindle Fire(orange) logo for about 5 secs
-Display goes blank for about 3 secs
-Loops in this manner indefinitely.
-Pressing Power & Volume Up during boot up puts into a specific mode where screen is blank and
PC would detect Kindle at Amazon Tate (In portable devices) and another device as ADB composite.
- When I run adb, it shows the device name and says unauthorized.
I have tried various methods, like plugging in HDMI cable, OTG mouse but there is no way to enable ADB on the tablet as there is no display.
-BTW, bootloader is locked on this tablet, I made fastboot cable but it doesnt work. I was never able to put tablet in fastboot
I basically bricked tablet by installing 7" ROM on 8.9" tablet. I dont know how it would break the tablet but it did. My tablet was rooted before I bricked it.
Tablet is worthless even if I fixed it but I am just curious if there is a way to fix it. Any help is much appreciated.
Click to expand...
Click to collapse
You installed a Tate Rom on a Jem and you don't know why it's bricked?
Sent from my ali using XDA Labs
I got so excited once I was able to finally root the tablet that I completely missed in the tutorial video that the ROM was for different tablet. Damage was done!
harshil22 said:
I got so excited once I was able to finally root the tablet that I completely missed in the tutorial video that the ROM was for different tablet. Damage was done!
Click to expand...
Click to collapse
Hello !!! I have the same issue. Could you fix it?
Related
Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544
ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.
your welcome I`m quite pleased its fixed myself
same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs
I can get around in both windows and linux. I have rooted, flashed and modded a smartphone before (Samsung Galaxy Express) successfully.
This should be an easy one for some of you to diagnose. A fresh stock Kindle Fire (6.3.2). Trying to install KFU v0.9.6 from a Win7 (also have various flavors of linux, ubuntu, arch, debian, etc available to use if need be). ran install_drivers.bat without any problems, device showed up and was recognized. Ran run.bat. put it in fastboot mode. Kindle Fire rebooted into the "Kindle Fire" White/Orange static logo and is stuck. No animation, no powerbutton response, can't turn it off, unknown device in Win7, adb and fastboot commands return no devices.
From reading the many beginner guides and unbricking posts, I was lead to believe that I needed to put this unit in fastbootmode to do any custom work with the device, and seeing that it's #1 on the menu list of the KFU I thought this was a pre-requisite before installing anything else. Apparently this is not the case. The device comes up as a USB Unknown Device (Code 43) now, and KFU can not find the device and is waiting for the device. Can't do anything. The only clue I was able to read was possibly letting the power drain. It was full charged so I will have to wait for a while. In the meantime, I figured I would hit up the forum to see if anyone has a better suggestion.
How do I get my Kindle Fire out of FastBoot Mode?
I am right there too...
BlushNine said:
I can get around in both windows and linux. I have rooted, flashed and modded a smartphone before (Samsung Galaxy Express) successfully.
This should be an easy one for some of you to diagnose. A fresh stock Kindle Fire (6.3.2). Trying to install KFU v0.9.6 from a Win7 (also have various flavors of linux, ubuntu, arch, debian, etc available to use if need be). ran install_drivers.bat without any problems, device showed up and was recognized. Ran run.bat. put it in fastboot mode. Kindle Fire rebooted into the "Kindle Fire" White/Orange static logo and is stuck. No animation, no powerbutton response, can't turn it off, unknown device in Win7, adb and fastboot commands return no devices.
From reading the many beginner guides and unbricking posts, I was lead to believe that I needed to put this unit in fastbootmode to do any custom work with the device, and seeing that it's #1 on the menu list of the KFU I thought this was a pre-requisite before installing anything else. Apparently this is not the case. The device comes up as a USB Unknown Device (Code 43) now, and KFU can not find the device and is waiting for the device. Can't do anything. The only clue I was able to read was possibly letting the power drain. It was full charged so I will have to wait for a while. In the meantime, I figured I would hit up the forum to see if anyone has a better suggestion.
How do I get my Kindle Fire out of FastBoot Mode?
Click to expand...
Click to collapse
I am right there too...
I ordered a Factory Cable and it should be in any day now. . . .
That is what I am doing and crossing my fingers . . .
serendipityguy said:
I am right there too...
I ordered a Factory Cable and it should be in any day now. . . .
That is what I am doing and crossing my fingers . . .
Click to expand...
Click to collapse
For anyone who has run into the same problem, this is how I fixed my problem
[1] Power off the Kindle Fire and unplug. Hold down the power button for more than 10seconds. There seems to be some variance with how long you have to hold the button down.
[2] Use the Kindle Fire Utility "run.bat" in Windows. Without the Kindle Fire device plugged in, the ADB Status will be Offline and Boot Status unknown, obviously. Go into boot menu [1] and select Normal Boot [1]. It will tell you <waiting for device>.
[3] Plug in Kindle Fire device.
[4] It should reset the Kindle Fire to normal working status.
PS. I tried the power drain, but it as soon as I supplied power back to the unit it resumed its stuck boot loop condition, so nothing changed. The reason it took so long to figure out this problem was (a) I didn't know you had to hold down the power button so long. 3-5 seconds is typical for most devices to perform a hard shutdown. (b) You have to set the Kindle Fire Utility waiting to catch the Kindle Fire device booting, if it's stuck in this condition. You can't just plug it in and run the KFU while its stuck on that screen.
Also, DO NOT SELECT [1] and FastBoot Mode on a fresh stock unmodified Kindle Fire. The other install menu selections in KFU will automatically Fastboot in order to perform what they need to do.
Hope this helps others.
Hi there,
All was going well with my Fire HD 8.9, I rooted it, had the 2nd bootloader installed and was trying to install CM 11 before I got an error message saying that the jem version was the one I needed. I couldn't get my computer to recognise the the Kindle whilst in TWRP, so thought that I'd have to restore from the backup I made (of the stock Kindle OS and settings) to be able to transfer the version of CM that I needed. The backup seemed to work, but it hasn't in fact.
I turn on the Kindle and it gets stuck at the very first image of the logo, with NO animation
I'm unable to get back into TWRP
I can turn the kindle on and off but that's it
I can't use any recovery programs because my PC doesn't recognise the Kindle
I uninstalled and reinstalled the adb drivers, but when I connect the Kindle, my PC plays the 'Device Connected' then 'Device disconnected' sounds in quick succession, making the installation of any drivers fail
It's as though there's a brief second or two when USB works on the Kindle in terms of my PC knowing something is there, but then the USB disconnect noise plays
I only got it a day ago (managed to mess it up very quickly somehow!), so I could always try returning it if needs be, but hopefully that won't be necessary. Any ideas? Thanks in advance
EDIT - I can get the device to come up with fastboot mode and then the computer recognises it as an Adb device, but don't know where to go from there.
I would try to fix it from recovery if possible, it is way easier than having to do the process over again. You do know how to get it back into recovery right? Hold down volume up right after you power it on, just keep holding it even after kindle logo turns blue until you see the twrp logo. If that doesn't work, I would use kindle fire first aid to restore it and start over, but if you can get it into recovery then you can simply push a ROM onto it via adb.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I would try to fix it from recovery if possible, it is way easier than having to do the process over again. You do know how to get it back into recovery right? Hold down volume up right after you power it on, just keep holding it even after kindle logo turns blue until you see the twrp logo. If that doesn't work, I would use kindle fire first aid to restore it and start over, but if you can get it into recovery then you can simply push a ROM onto it via adb.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I actually managed to fix it in the end by using the fast boot command and then connecting the Kindle, then using the SR tool to erase user data and cache, before flashing the boot and recovery imgs (just saying in case anyone googles and this comes up and it might help).
I can not get my wife's fire HD 8.9 to boot. When I turn it on the Kindle Fire screen appears for about 5 seconds, then the Kindle Fire goes out, but the screen is still backlit.
This device is completely stock with no modifications. It did this when I turned it on one day, no previous problems.
I tried holding the power button down for up to 2 min. After I hold the button for 10 seconds the backlight goes out and the kindle is completely off. I tried letting the battery go completely dead, then charging it for several hours with no change. I tried running fastboot, but it is stuck at <waiting for device>. My computer does not see it at all. I do hear the chime that something was plugged into the computer immediately followed by the chime that it was disconnected, but nothing shows up in my computer at all.
Is there any hope for this Kindle, or is it bricked for good?
So I assume you're on windows. That beeb you hear is the fastboot mode you need to load drivers really quickly during that beeb. At that point fastboot shoukd work and you can issue a command to get into the factory restore.
I got it working again.
The problem was simple, I did not have any drivers installed on my computer for the kindle (I have never plugged it into this computer before it would not boot). I found the drivers to download here: http://forum.xda-developers.com/showthread.php?t=1890413
I was then able to get it into fastboot and recover it with instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2011126
Hi,
My stock fire tv is stuck in boot process. When I turn it on loads the b/w amazon logo and, about 30 seconds after, the colorful amazon fire tv logo comes up. And that's it, nothing else ever happens. No reboot, noloop, nothing else.
I have tried to factory reset it by pressing alt+i+print-screen hundred of times while booting with no success. I have tried with 4 different keyboard (including a logitech k400).
I have tried to connect a USB-A to USB-A cable from the fire tv and the PC and installed adb drivers (all devices are recognized by windows and display and device manager) but I can't detect the device with adb devices at any stage of the boot process at all.
Does anyone have any other possible way to un-brick it? O any other suggestion to revive it?
btw, It "bricked" itself. One day I turned on tv and I saw empty menus and nothing happened if I tried to navigate on it... So decided to reboot it and... there you go, the way it is now.
Thanks in advance.
Anybody can help please? I've got a precious brick os plastic and circuits on top my desk right now....