Related
Just got a new KF today and tried loading Go Launcher EX. Got to the point where I rebooted the KF and told it to always boot to GO Launcher..... BIG MISTAKE... something had gone wrong in the go launcher install and Not I have a pretty Kindle Fire Logo on my screen that will not go away.
I have downloaded KFU and Installed the drivers. With my KF on and plugged into usb my device manager shows. "Android ADB Device" which if i read correctly is what it should show.
But inside KFU it does not seem to connect to the device.
Is there something i have missed or is it truly a brick ...
I tried that ... Uninstalled device (made sure to remove driver) refresh device manager.. update drivers on kindle device... Then tried KFU
All I keep getting is waiting on device...
On the main screen it says:
ADB Status: Offline
Boot Status: Unknown
When I go into the Bootmode Menu and select 1 it sits on a screen saying waiting on device.
This is pretty much where i have been stuck at all day ...
Power your kindle off by holding the power button for like 30 seconds its very likey that adb will not detect your kindle it cannot while its in fastboot But first try this shift plus right click on the tools folder in kindle fire utility select open command window here power your kindle off and enter the command Fastboot getvar product (hit enter)Plug your kindle in it will power on in fastboot If you get the response product: kindle then we can move on.
if you get the response product: kindle Type fastboot oem idme bootmode 4000 (hit enter)fastboot reboot (hit enter)
Nothing.?then Then next time try fastboot -i 0x1949 getvar product (hit enter) when it says <waiting for device> plug in your powered off device if it says product: kindle type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)fastboot -i 0x1949 reboot(hit enter)
Fastboot getvar product
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I tried both of these. Each time i unplugged the KF, held power for 30 secs(using a timer),typed command then hit enter, then plugged in KF.
both times it powered on and went to the Kindle Fire logo and the command window just said waiting on device. A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Don't unplug it.
I've found with mine, whenever I'm stuck in fastboot I do the following:
1. LEAVE THE KF PLUGGED INTO THE COMPUTER AT ALL TIMES!
2. Uninstall all instances of the Android Device in Device Manager.
3. Power off KF by holding the power button for NO LESS than 30 seconds. Even when it looks off, keep holding it and count to 30. (keep plugged in)
4. Power on the KF by simply clicking the power button once. (still plugged in)
5. Once the KF is back at fastboot, the computer should automatically install the drivers from the KFU folder, if not then manually point it there.
6. Open KFU and start run.bat
7. At the menu, regardless of device status (mine says offline/unknown when in fastboot mode), press 1, enter, 1, enter.
so are you suggesting i do the command line stuff?
EDIT.... any way i cut it im getting the same Kindle Fire screen ...
one I used this -i 0x1949 one I didnt because sometimes it doesnt matter but lelandfried is suggesting to try to use kfu to reset your bootmode which is logical and keep working with your drivers which also makes 100% sense keep trying you could get lucky and something will work its windows darn drivers that are killing you another option is this http://forum.xda-developers.com/showthread.php?t=1670405 then you wont be messing with the drivers anymore add sudo to the front of all your fastboot commands.
If I have ubuntu running on a VM can I do this through there? I have mixed success using usb devices
whoops sorry soupmagnet will know if it will run on a vm ask him he can give you the best advice
No problem. Im going to give it a shot... I have done everything i can think of to get the right drivers on here in windows. As best as I can tell from the chart on this thread http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
I have the ADB driver loaded for Recovery,Stock SW or ROM (USB Debog On)
I think I will try the ubuntu thing for a bit .... Frustrating .. very frustrating
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
did you use sudo before all your commands and plug in your prepowered off kindle in when it says waiting for device?
Deslyxia said:
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
Click to expand...
Click to collapse
Soupmagnet said he had problems getting the KF to work with VMWare in fastboot mode. YMMV. I use Parallels Desktop and have no problems with it.
The most telling thing you said in this thread...
Deslyxia said:
A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Click to expand...
Click to collapse
If the logo "blinked" a few times, then it's not in fastboot mode. It is most likely past the bootloader stage, loaded the boot partition and trying to start up the system. At this point, your best hope is to send it some adb commands to get the KF into fastboot or recovery, but it might not be far enough along in the process to accept adb commands either.
Read the following post about fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
Most people in your situation end up buying a factory cable.
Okay. thank you to everyone for the help so far. From within Ubuntu I was able to use this guide http://forum.xda-developers.com/showthread.php?t=1414832 to get into fast boot mode. From there I installed TWRP Recovery then rebooted into recovery mode. Then I installed FFF, Rebooted into recovery mode and reset to factory.
When I rebooted I got the FFF boot screen and let it boot like normal to a factory reset KF.
Again thank you all for your help .
I'm glad you got it going just make sure you do all the right things if you start flashing roms don't be afraid to ask questions its better than getting messed up again always make backups and do proper wipes just don't wipe your SD card or let your battery die good luck
I dunno how to do adb thru Ubuntu, even though I have it on my desktop. I do all my adb stuff through my Windows laptop.
Glad to hear you got it going. I'm bookmarking this thread for the Ubuntu links and info, Thanks!
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
arthur. said:
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
Click to expand...
Click to collapse
So you have followed Steps 3 and 4?
Just below that is a method to flash back to stock, have you tried that, as the stock files are there as well?
arthur. said:
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
Click to expand...
Click to collapse
I was having the same problem, i just booted and suddenly turned off. It was on the stock rom , so I used a factory cable and installed fff 1.4 then installed the twrp 2.5 from their site but I'm not able to get it into recovery, just an amber light and it turns off!! I'm wondering if is not compatible, I tried the otter and blaze twrp just to make sure...
What do you think? Did you managed to fix it?
Sent from my SPH-D710 using xda premium
chronicfathead said:
So you have followed Steps 3 and 4?
Just below that is a method to flash back to stock, have you tried that, as the stock files are there as well?
Click to expand...
Click to collapse
i wanted to get the restoration tool from here, but the file is not availible anymore. anyway, the device didn't received the adb commands.
i tried to flash the original stock rom back, just by using files from amazon. i don't know what happend, but after "fastboot bootloader" command the Kindle is dead. No more LED light while charging, no reaction on fastboot cable
first i thought, the battery is empty, but after one night on the charger, nothing changed. the device stays complete black.
Any chances left (even at amazon?) or is the garbage the only place this kindle belongs now?
Well Arthur, if you have not opened it should not be dead, it seems like you are on a boot loop and maybe the battery is fully discharged.
Please explain how did you tried to install the Amazon stock ROM
Sent from my SPH-D710 using xda premium
well, my first thoughts were also, that the battery is discharged. but i used next to my computer already an ipad charger and my phone-charger (both over 1A out) over night. but still no lightning of the LED.
last thing i remember, was a (afterwards clearly) stupid hint from a ebay page. [fastboot -i 0x1949 flash bootloader u-boot.bin] i used the u-boot.bin from the amazon homepage.
afterwards the kindle shut down and the lightning LED has never been seen again
Your KF will not charge if bricked, you could try a factory cable to get it into fastboot mode but if it is discharged maybe you must try another method to charge the battery... First try the factory cable!!
Sent from my SPH-D710 using xda premium
i tried with a factory cable, but again, no response from the device. As I mentioned, I tried already several charger.
And what do you mean by another charging method? Is there something i don't know yet ?
Hi all,
First off, this is my first post :victory: and I need some help.
Last night I used this thread to successfully get root access on my Kindle Fire HD 8.9".
Then, wanting to install CyanogenMod 10.1 on the Kindle, I tried to install the second bootloader and TWRP Recovery. At this point, the Kindle began to reboot. When it turned on, the Kindle Fire logo appeared, shined a few times, then blank red covered the screen.
I can turn on/turn off the Kindle, but all I see is this red screen. Anything I can do?
I've looked at factory cables, hopefully there are some things I can try before I buy that...?
A factory cable won't work on the 8.9
Disconnect the USB cable
Turn the device completely off (hold power button for 10 seconds)
Enter: fastboot -i 0x1949 getvar product
Reconnect the USB cable
As the device powers up, if your fastboot drivers are working properly, the device should boot into fastboot mode. Use it to restore your saved partition images.
Thanks for reply
Hi soupmagnet,
Where do I enter the command "fastboot -i 0x1949 getvar product"?
In command prompt on the computer?
EDIT: Self-explanatory It worked perfectly - thanks!
HAVING SAME PROBLEM KFHD 8.9 2nd Gen RED BOOT.
I have the same problem. Can boot into fast mode with KFFA, but restoring stock settings seem to be Impossible. I have tried to restore with ADB, ADB (Fastboot), KFFA, and KF SRT. No matter what red boot screen will not go away and device can only fastboot. Any help?
JonnyLawless said:
I have the same problem. Can boot into fast mode with KFFA, but restoring stock settings seem to be Impossible. I have tried to restore with ADB, ADB (Fastboot), KFFA, and KF SRT. No matter what red boot screen will not go away and device can only fastboot. Any help?
Click to expand...
Click to collapse
Red screen is also considered a hard brick. Sometimes restore does not work.
Same happened here
Today I rooted my kindle fire 2nd gen10.4.8 using vroot I also installed a boot loader that as soon as I tried downloading shut my kindle fire down and when I tried unsuccessfully to turn it back on the red kindle fire symbol came for a second and then the careen was red
http://forum.xda-developers.com/showthread.php?p=46154263 follow this and you should all be away from that red screen
Sent from my Amazon Jem using XDA Premium 4 mobile app
same here but worse
My kindle is rooted and when i flahsed a recovery it asked if i wanted to boot into recovery after i said yes then when it booted the kindle fire logo appeared for about 1 second then a red screen slid in from the side now it wont boot into recovery fastboot or normal mode and i have reinstalled kindle drivers several times as well as fastboot.exe and also adb.exe and nothing works the computer sees it for 3 seconds if i hold power volume down but then it goes to red screen
You need to run this on the computer: fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in while it is off, if the bootloader isn't too damaged it should kick into fastboot. Hopefully you also installed the fastboot drivers previously or your best bet might be a Linux live distro like Ubuntu.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You need to run this on the computer: fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in while it is off, if the bootloader isn't too damaged it should kick into fastboot. Hopefully you also installed the fastboot drivers previously or your best bet might be a Linux live distro like Ubuntu.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
fastboot doesn't recognize if there is a way to fix this or a way to keep the kindle connected for more then 3 seconds i would appreciate it
What does the kindle show up as for those 3 seconds? Because usually it shows up as a jem device (without the driver installed) or a adb device (with fastboot drivers installed) and in those 3 seconds that command gets it to go into fastboot mode so you can fix it. All that needs doing is the bootimg needs to be flashed or erased and fastboot should be more cooperative.
Sent from my Amazon Tate using Tapatalk
I ran the fastboot command like you said, and got my kindle to go into fastboot but i have no idea what to do next.
should i run certain files?if so please tell me where and how?
Use kindle fire first aid or system restore tool for the rest once it is in fastboot mode or flash a backup of your boot image with "fastboot -i 0x949 flash boot boot.img", that should fix a red screen/bad loop scenario where fastboot is not working well, etc.
thats the problem
stunts513 said:
What does the kindle show up as for those 3 seconds? Because usually it shows up as a jem device (without the driver installed) or a adb device (with fastboot drivers installed) and in those 3 seconds that command gets it to go into fastboot mode so you can fix it. All that needs doing is the bootimg needs to be flashed or erased and fastboot should be more cooperative.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
i cant tell what it shows up as because by the time it shows up in the device manager the kindle disconnects
how do i flash a boot.img if the kindle is only connected for 3 seconds and fastboot isn't working
A ubuntu live os probably would do the trick
May I give up kindle fire hd 8.9 ?
LinearEquation said:
Red screen is also considered a hard brick. Sometimes restore does not work.
Click to expand...
Click to collapse
As you told. I try use fastboot by KFFirst Aide or KF SRT 2.1 but not thing chance. My screen still blank red. So Sad .
My Kindle Fire HD 8.9 Use stock rom from amazon 8.5.1.
Have we have another way to fix it ?
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.
hello. i was trying to install cm11 but way before that u used a program called flash fire. and now its stuck on boot logo and a dark screen. my computer recognize my device for 3 seconds then it disconnects. i have install the drivers necessary, and i have tried the fastboot -i 0x1949 ..... methond on my cmd but it just stay at <serching for device> or something like that please help :crying:
mcdell111 said:
hello. i was trying to install cm11 but way before that u used a program called flash fire. and now its stuck on boot logo and a dark screen. my computer recognize my device for 3 seconds then it disconnects. i have install the drivers necessary, and i have tried the fastboot -i 0x1949 ..... methond on my cmd but it just stay at <serching for device> or something like that please help :crying:
Click to expand...
Click to collapse
When you used Fireflash, did you get TWRP and second bootloader installed? If you did, power your device off, then power back on. When you see the gold Kindle Fire logo, hold the volume up button until the logo turns blue, keep holding for 3 more seconds, then release and you should boot into TWRP. From there should be able to connect to computer and transfer files using ADB if needed.
I belive i did not. Everytime i do your method it just show the screen on but just black.
I even have a factory cable to fastboot it and it also dosent work /:
USB Drivers
You just need to change the drivers on windows to get it detected properly and access to fastboot
I posted a quick how to here : http://forum.xda-developers.com/showpost.php?p=59900685&postcount=4
Install Android SDK, if you have not already.
Put the kindle in fastboot mode.
Download The Twrp files for kindle fire hd.
Flash The Files
Reboot Into Recovery
Try to see if you can boot into your os
If not, use adb to push a rom into your kindle.
Flash it
You should be good.
Detailed Tutorial:
http://forum.xda-developers.com/kin...help/kindle-fire-hd-8-9-bootloop-fix-t3137732
i have this same problem i type in fastboot -i 0x1949 getvar product once i plug in the turned off kindle it just turns on and starts the bootloop once again i've tried holding the volume up button as well but the screen just turns black like you said. if you figured out how to fix it please tell thanks.