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
Back story: I purchased a used Kindle Fire on Ebay about a week ago, not knowing that it had been rooted. I was looking for a standard Kindle fire for my son so he would stop using my tablet (lol) and the parental controls are better and more books and so on... none the less when I got it I noticed that it booted differently (I had a kindle fire prior) and it booted into Android. I have had problems with trying to be able to get my computer to recognize it. It looks for missing drivers and I have been all frustrated, but figured that we would just have to download off of it, well, we went on a trip this past weekend (11 hours) and my son wanted to watch a movie, turned it on and it wont boot past the yellow triangle now. I have tried a hard reboot, I have tried to turn it on and hold it and watch for the orange light to no avail. The light is either green or its powered off.
I don know what to do at this point? I cant hook it to my computer (wont even recognize as an F drive or mass media) and I cant boot past the orange triangle. Yes, I am a newb (apologies) but a very frustrated one if that counts?
Sadly I think the thing is bricked and I will take a $150 hit (ugh)
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Yes, you would be correct in that I just want it stock, sure Android is great but my son is 4 and he just needs the basics for his books and angry birds lol. So, I attempted what you said, powered off all of the way and turned back on, as soon as I see the yellow triangle I hold the button and it wont turn orange, it will just power back off. I used to be able to touch the screen when the yellow triangle came up and it would take me into some menu (TWRP?) but it wont do that anymore either, its just remains either off or on the yellow triangle.
soupmagnet said:
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Click to expand...
Click to collapse
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
soupmagnet said:
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
Click to expand...
Click to collapse
Save yourself the trouble mail it to me I will fix it then you reimburse me the return postage or better yet I can show you how to fix it without even mailing it . 150 for a first gen kindle is pretty high you kinda already got taken.
[email protected] said:
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
Click to expand...
Click to collapse
Pay attention to what I said previously...
soupmagnet said:
Extract the KFU and run the install_drivers.bat
Click to expand...
Click to collapse
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
I think I am officially over this thing... I downloaded the drivers and went to plug in the kindle fire to the computer and now its just looping the triangle... it turns on for a second and then off and on and off and so on... UGHHHHHH....
soupmagnet said:
Pay attention to what I said previously...
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
Click to expand...
Click to collapse
You let the battery die. I won't go into how it happened but to get it to charge, you need to...
With the device turned off, Plug the device into USB and hold the power button until it shuts off again. If you can get it to stay off, leave it plugged in for about half a day and turn it on again.
I had a tough time learning how to UN-brick my wife's AND my friends Kindle Fire devices. I'm going to liberally add links to things around the site because I found them extremely useful and educational, but I could not find all of the things I needed in one place. Both of the Kindle Fire devices I had to fix were Kindle Fire first generation devices, so I can only speak to these fixes. However it may help you at least get your head straight to understand what you are doing, what you have and what you need to do. My intent with both of these devices was never to root them or replace the ROM's, although I have done that to my own phones and love the Android OS, it was simply to get both working again so my wife could read and check email and my friends kids could play their games.
What I had and the issue with each device:
Kindle Fire (1) - no more space on the device, stuck at logo.
Kindle Fire (2) - originally USB connector separated from the circuit board, I had a local electronics guy solder a new one back on and upon start up it was stuck at the logo also (it worked before he fixed the board).
Utilities you need:
Kindle Fire factory cable - quality cable get one from here: http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
Minimal ADB and Fastboot Utility: http://forum.xda-developers.com/showthread.php?p=42407269
Kindle Fire Utility 0.9.9 - get it here: http://forum.xda-developers.com/showthread.php?t=2192818
Fix the Kindle Fire Utility run.bat file - It would not run on my WinXP or Win7 machine and the fix works no matter which version you are running: http://forum.xda-developers.com/showthread.php?t=1737671
Information about TWRP, it comes with the Kindle Fire Utility: http://www.teamw.in/project/twrp2
Information about FireFireFire: http://www.xda-developers.com/android/firefirefire-custom-bootloader-for-the-kindle-fire/ FireFireFire comes with the Kindle Fire Utility and allows you to get into recovery when not connected to the computer, install FireFireFire after TWRP.
Informative video on using Kindle Fire Utility: https://www.youtube.com/watch?v=CQ21pr6_SHI
The Forum recommends reading these first, do yourself a favor and READ THESE FIRST:
Kindle Fire for Beginners (very helpful): http://forum.xda-developers.com/showthread.php?t=1552547
Kindle Fire for Beginners - Supplemental How-To Guide: http://forum.xda-developers.com/showthread.php?t=1638452
The PROCESS of UN-bricking:
1, Install Minimal ADB and Fastboot:
2, Install Kindle Fire Utility - I just put it into the Minimal ADB install directory so its all in one place.
3, In the Kindle Fire Utility directory run "install_drivers.bat" without the device connected (does not matter what version of WinXP or Win7, I have no idea if these will work on Win8 I did not try it). Reboot if you need to.
4, Plug the factory cable into your device, then plug the cable into the USB port on your computer and the Kindle Fire will boot into FASTBOOT all by itself. You can tell by the White/Orange logo and the screen is brighter than normal.
NOTE: This is the part that drove me bat crazy! With a stock Kindle Fire 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, ie "fastboot -i 0x1949 devices", where 0x1949 is the stock vendor ID. Also ADB and Fastboot are mutually exclusive, meaning you can only be in and use one at a time, never both. ADB commands will not work in fastboot mode or with the factory cable, you must use a regular USB cable for that and not be in fasboot mode. Even at the logo with a standard USB cable ADB would connect, but it's READ ONLY.
5, Run the Minimal ADB shortcut to the ADB prompt or open a CMD shell, navigate to the directory and run "fastboot -i 0x1949 devices". If it returns something like "0123456789ABCDEF fastboot", the number being your device number then you are in fastboot mode.
6, In the Kindle Fire Utility directory run the "run.bat" file, a CMD window with a menu will open.
NOTE:
You will see something like the below in the CMD window, ignore it, the stock Kindle Fire always shows this. If you want to make sure you are still in fastboot Run the Minimal ADB shortcut to the ADB prompt or open a CMD shell, navigate to the directory and run "fastboot -i 0x1949 devices" again and make sure your device shows up.
ADB Status: Offline
Boot Status: Unknown
7, Once Kindle Fire Utility loads, select option 3 and install TWRP, let it finish and it will reboot the device, hit enter back to the main menu. The logo will not change yet.
8, Once Kindle Fire Utility loads, select option 5 and install FireFireFire, let it finish and it will reboot the device, hit enter back to the main menu. The logo will still be white and blue logo.
9, Once Kindle Fire Utility loads if you want to root select 2 "Install Permanent Root with Superuser", let it finish and it will reboot the device, hit enter back to the main menu. The logo will still be white and blue logo.
10, Hold the power button until the device shuts down, unplug the factory cable from the computer, then the device.
11, Tap the power button and the device should start to boot. At the bottom you will see the boot select prompt, hold power button a couple of seconds and a menu should pop up. Tap the power button to change menu item until recovery is selected "--Recovery--" and leave it until it boots into TWRP.
12, Once you boot into TWRP select WIPE,
13, On the bottom of the next screen swipe "Swipe to factory reset", let it finish and select the back button.
14, Select REBOOT and then SYSTEM (this resets Fastboot mode to 4000 if you changed it to 4002 or screwed with it otherwise).
15, At one point I was asked if I want to root it and install SU. On my wife's I did and on my friends I did not, kids have a habit of pushing the right combination of buttons and bricking them. I don't recall when it actually asked me to do the root, but it probably has to do with me doing step 9 above on one and not the other.
16, After it reboots and it takes a while the first time again, reconfigure your Factory Stock Kindle Fire as you would out of the box. All of your stuff will synch back to it, unless you used a USB cable to transfer data to it, that stuff may be gone, but I did not have any of that to worry about.
17, Since the Kindle was already registered both your Kindle books and Amazon apps should be there but you will have to reinstall the apps and lose saved game data.
Again, this is how I chose to do the repair based on my knowledge level (and frustration level) after a lot of research, reading, testing and rebooting. Like I said, all I wanted was a stock fresh Kindle Fire, so this worked for me. I might at some point wipe it and install a custom ROM and Kernel but for now they are both grateful and happy to have their devices back without buying new ones.
Also, I am grateful to all the people who posted here before me that allowed me to learn more about the Android OS devices and repair them. It was actually a fun and frustrating adventure, but the thrill of beating it into submission was well worth the learning curve on another device!!!
Jocco-
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
lob455 said:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
Click to expand...
Click to collapse
Does it show up in Device manager? as kindle, android phone, or something else...?
sd_shadow said:
Does it show up in Device manager? as kindle, android phone, or something else...?
Click to expand...
Click to collapse
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
lob455 said:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
Click to expand...
Click to collapse
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Thepooch said:
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Click to expand...
Click to collapse
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
lob455 said:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
Click to expand...
Click to collapse
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Thepooch said:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Click to expand...
Click to collapse
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
lob455 said:
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
Click to expand...
Click to collapse
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze
sd_shadow said:
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x ..................
Click to expand...
Click to collapse
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
lob455 said:
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
Click to expand...
Click to collapse
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
sd_shadow said:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
Click to expand...
Click to collapse
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Just place a Rom on your Sdcard and flash it.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Try the mount option in twrp again
sd_shadow said:
Try the mount option in twrp again
Click to expand...
Click to collapse
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.
Before I begin, trust me when I say I have scurried through dozens of Google results, forums, blogs, YouTube videos, FAQ's and other things trying to find out how to unbrick this thing. I have a Kindle Fire first gen which I rooted using Kindle Fire Utility through superuser 3 days ago. All was well, as I had google play and an innovative new launcher. After downloading a few apps, I thought that I had finally made the Kindle the fully-functional Android tablet I had desired. However, after a few hours of seamless use, the Kindle decided to freeze on me. Holding the power button still brought up the "Do you wish to power down your Kindle?" notification, and I shut it down, planning on restarting it. However, when I turned it back on, it would not get past the animated Kindle Fire logo. The weird part was, I could still hear notification tones. I was using my phone to DM on Twitter, and when I would get a message back, I could hear the twitter notification on my Kindle. (No, I was not mistaking it for the phone). After a while, I could hear that sound it makes when the battery was about to die. I plugged it in, and after two hours I unplugged it, held the power button to shut it down, and started searching google for answers. I was advised to use the Kindle Fire Utility to launch it in fastboot mode, which only restars the Kindle with no success. I have tried all options on the KF utility, even Permaroot. If I install TWRP recovery, it gets stuck on waiting for device. On most options, it gets stuck on waiting for device. (I have tried all the unplugging, unpowering options I saw). The computer makes a sound when the KF is plugged in, but it doesn't come up on the devices with removeable storage tab. I have all drivers installed, it is ADB enabled through the device manager, I have the Java Developer Kit, as well as Android SDK. The only thing I can get any utility to do (I have tried many such as Kindle Brick, SuperOneClick,etc) is restart the Kindle as if I did it myself. It still makes all the notification tones I mentioned earlier. One thing I have noticed, though, is that when the Kindle is 10 seconds from dying, the Unlock Screen will appear with no response. I have tried several times to let it get to that point, then quickly plug it in, but no sucess. It just restarts on the same boot screen. I have no idea what to do. I'm not a developer by any means, but I'm good with following directions I'm given to mess with computers and such. I don't have much knowledge of the command prompt, either. I just made this post as a last resort. Someone please help. (Running Windows 10 techncinal preview on a Windows 8, 64-bit laptop if that helps)
Do you know which system version?
Kindle Fire Utility doesn't root the latest system version.
Guessing that you rooted older version, then Kindle downloaded and installed newer system version, it would not ask for permission.
New system version may not have installed correctly.
If system was updated, Kindle lost root.
When powered off, connect to wall charger, does it charge?
Couple of options
See if you can force fastboot mode with adb commands
Or buy a fastboot cable
Then flash fff and twrp so you can reinstall stock rom
See
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Sent from my XT912 using Tapatalk