Forgive me if I am not describing this in the best terms.
My fire was stuck at the kindle fire logo, it would load for 2 seconds to the kindle fire logo then turn off and boot to the logo once again, non-stop.
I plugged in my fastboot cable and it immediately booted into fastboot. While connected to fastboot I opened the Kindle Fire utility and under one option was the option to boot into recovery. My thought was, if I could force it to boot into TWRP I could fix permissions/wipe cache or something like that to get it working.
It immediately disconnected from my computer (the noise the computer makes when a USB is disconnected) then it went on connecting and disconnecting non-stop. The screen turned on to kindle fire logo, then to fast boot logo then went black, the entire time it is connecting and disconnected to my computer, making the connection tone then disconnection tone every other second.
I unplugged the kindle then held the power button for 60 seconds, this seemed to turn it off. I hit the power button again, while still unplugged and it shows the kindle fire logo, immediately followed by the fastboot mode logo, then the screen goes off. If i plug it into the computer it is making the connect/disconnect noise.
I feel like if I could get it to stay in fastboot I could use the recovery tool to fix it, but at the moment it is just cycling non-stop and cannot be connected to the computer.
Any ideas?
Thank you for any help you can give me.
FIXED
Okay, great news, I fixed it. After trying a combination of EVERYTHING I could find on the internet, a dozen programs and images. So, here is how I did it.
At the windows command prompt I entered the command: fastboot -i 0x1949 getvar product
this was while my device was constantly connecting and disconnecting, launching straight into fastboot. So the command did not execute right away, it would say < waiting for device >
While plugged into the computer, I held the power button for 20 seconds to shut off the device, then hit the power button to restart the device. The moment the device turned on, before it would power cycle, the command processed and the device would stay on, at the fastboot screen.
Downloading KFHD_SRTv1.3.5 I opened that program. Giving me options to restore the device. I did an ERASE CACHE AND USERDATA (Options 4), once that completed I did the RESTORE-FACTORY RECOVERY (Option 3).
I tried to reboot right here but it would AGAIN begin power cycling through fast boot.
I went back to my command prompt and issued the command: fastboot -i 0x1949 reboot
The device rebooted to the kindle fire screen and DIDN'T go to fastboot, it DIDN'T power cycle. It took a few minutes to load, but when completed it loaded the stock amazon application.
This took me a couple hours, I tried a lot of different methods and a LOT of different boot.img, recovery.img, system.img. I downloaded 15gb of files trying different thing. This worked for me.
Good luck all.
Related
Environment: OS X 10.7.3; started with stock KF 6.3.1. Added 0x1949 key to ~/.android/adb_usb.ini, confirmed adb working with adb logcat. Plan was to root stock ROM first, get comfortable with the KF's behavior in that state, then eventually get over to CM9, as my Droid Incredible runs CM7 quite beautifully.
Started with procedure at http://forum.xda-developers.com/showthread.php?p=24129239 . Pushed fbmode successfully, chmodded and ran it, adb reboot successful. Continued with the following
Code:
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash bootloader u-boot-firefirefire-1.2/u-boot.bin
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)...
...and everything stopped. Waited there for about 10 minutes before giving up. Eventually powered down by holding power button and then pushed it again to start up; got yellow firefirefire triangle. That screen suggested pushing power to go into recovery; no dice.
I thrashed a little with fastboot oem idme bootmode commands until I got it to successfully reboot. Current boot sequence displays firefirefire triangle for a few seconds, then goes to the 'kindle fire' logo screen, then boots to working stock OS. The first time this happened and several reboot cycles thereafter, it would not charge via stock charger or Mac USB and LED would not light; after another few reboot cycles, it suddenly decided to charge with stock charger and LED lit orange. I'm not inclined to experiment any more until I get (a) some knowledge and (b) better than 36% charge. ;-)
I assume I've got a borked recovery. Question is how to fix and continue on my happy rooting way. Help much appreciated.
VT_hawkeye said:
Environment: OS X 10.7.3; started with stock KF 6.3.1. Added 0x1949 key to ~/.android/adb_usb.ini, confirmed adb working with adb logcat. Plan was to root stock ROM first, get comfortable with the KF's behavior in that state, then eventually get over to CM9, as my Droid Incredible runs CM7 quite beautifully.
Started with procedure at http://forum.xda-developers.com/showthread.php?p=24129239 . Pushed fbmode successfully, chmodded and ran it, adb reboot successful. Continued with the following
Code:
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash bootloader u-boot-firefirefire-1.2/u-boot.bin
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)...
...and everything stopped. Waited there for about 10 minutes before giving up. Eventually powered down by holding power button and then pushed it again to start up; got yellow firefirefire triangle. That screen suggested pushing power to go into recovery; no dice.
I thrashed a little with fastboot oem idme bootmode commands until I got it to successfully reboot. Current boot sequence displays firefirefire triangle for a few seconds, then goes to the 'kindle fire' logo screen, then boots to working stock OS. The first time this happened and several reboot cycles thereafter, it would not charge via stock charger or Mac USB and LED would not light; after another few reboot cycles, it suddenly decided to charge with stock charger and LED lit orange. I'm not inclined to experiment any more until I get (a) some knowledge and (b) better than 36% charge. ;-)
I assume I've got a borked recovery. Question is how to fix and continue on my happy rooting way. Help much appreciated.
Click to expand...
Click to collapse
What a relief it is to see such a detailed description of someone's problem. Thank you.
When you turn the device on and see the yellow triangle, hold the power button until it turns orange and release. Does it boot into recovery?
I'm sorry if that sounds like a stupid question but you can never assume anything here.
soupmagnet said:
What a relief it is to see such a detailed description of someone's problem. Thank you.
When you turn the device on and see the yellow triangle, hold the power button until it turns orange and release. Does it boot into recovery?
I'm sorry if that sounds like a stupid question but you can never assume anything here.
Click to expand...
Click to collapse
No, good question, and thanks very much for the help. I tried that several times and was not able to even get the power LED to turn orange, which seemed odd to me. Should have put that in my initial post. Thinking about it, I may not have unplugged the USB cable during those cycles; perhaps that caused it not to respond to the power button.
So I just tried it again. Rebooted by issuing 'adb reboot' and, this time, unplugged as soon as screen went dark. At FFF triangle, held power button until LED went from green to orange. At this point, LED stayed orange and the backlight changed intensity two or three times while still on FFF graphics. The kf logo then came up briefly, then the KF rebooted entirely. On that boot cycle, I touched no buttons and it appeared to go normally (FFF triangle, then kf logo static, then kf logo with shimmering animation, then stock lockscreen). Charging from AC continues to work.
Download twrp 2.1 again and check the md5 before reinstalling with:
fastboot flash recovery /path/to/recovery.img
...and see if that gives you a better result.
soupmagnet said:
Download twrp 2.1 again and check the md5 before reinstalling with:
fastboot flash recovery /path/to/recovery.img
...and see if that gives you a better result.
Click to expand...
Click to collapse
Reinstall worked this time -- I issued the command immediately following adb reboot and it flashed successfully as soon as FFF started up. This time the 'fastboot oem idme bootmode 5002' command just yielded '...' though, and 'fastboot reboot' just yielded 'rebooting...'. It's as if the fastboot USB connection just dies for some reason if you don't keep feeding it data.
So I shut down with held power button, pushed power button to boot to FFF screen, held power button to orange LED, held my breath, and TWRP popped up. Steps after that all went perfectly, I Dropboxed Superuser.apk and Root Explorer over from my Inc after the reboot, and we're in business with hot hot root action.
Thanks very much for your help -- it's nice to have somebody who's seen all the weird failure modes around in case I bork something.
VT_hawkeye said:
Reinstall worked this time -- I issued the command immediately following adb reboot and it flashed successfully as soon as FFF started up. This time the 'fastboot oem idme bootmode 5002' command just yielded '...' though, and 'fastboot reboot' just yielded 'rebooting...'. It's as if the fastboot USB connection just dies for some reason if you don't keep feeding it data.
So I shut down with held power button, pushed power button to boot to FFF screen, held power button to orange LED, held my breath, and TWRP popped up. Steps after that all went perfectly, I Dropboxed Superuser.apk and Root Explorer over from my Inc after the reboot, and we're in business with hot hot root action.
Thanks very much for your help -- it's nice to have somebody who's seen all the weird failure modes around in case I bork something.
Click to expand...
Click to collapse
Yeah, after changing the bootmode in fastboot, "fastboot reboot" doesn't work.
I'm glad to see you worked it out though.
Hey guys,
After trying for the past two days and a lot of hours to get a good enough grasp to undo a hasty attempt at rooting my kindle, I've decided to come to you with a request for help!
It all started when I installed the amazon usb drivers for kindle fire and then loaded up KFU. It read that my kindle was in boot mode 4000 (normal boot mode) and I told it to root my device. It seemed to be working fine, until all the sudden, it froze as it was trying to load TWRP onto my kindle. AFter waiting some amount of time, I finally just cancelled the job and tried to reset my kindle.
Ever since my kindle is stuck at the stock loading screen. No FFF, just the regular kindle fire logo and it never dims in light, which is a clear indication that it is in fastboot, and isn't going anywhere. Well at that point, my windows drivers failed me and ceased to recognize my kindle. Well, I tried everything to get windows to recognize the device but it failed. I even tried creating a bootable ubuntu partition and using the linux drivers with firekit. It didn't really work as well as I'd have liked.
Recently, I used my roommate's macbook and fastboot to try and see if there was any hope for communicating with my kindle.
The "./fastboot -i 0x1949 getvar products" command returned "product:kindle" suggesting that the macbook recognized my kindle.
YAYY!
but when i tried to reset the bootmode to 4000, it just sat there with three dots and did nothing. i tried to flash TWRP again, same thing. Each time i would cancel the job and then when i went back to try and recognize my kindle, even the macbook had lost it.
Ideas?
Hold your power button to shut it off, then start it up again. Does the display stay brightly lit?
Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.
sabres032 said:
Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.
Click to expand...
Click to collapse
with OtterX bootloader v2.05, every time kindle is booting, fastboot commands can be used, but the window is short.
with kindle off, enter command
Code:
fastboot devices
then power on kindle, if you get a response like 123456789 fastboot
then you could try flashing bootloader again, but likely LCD is bad
unzip OtterX bootloader v2.05.zip, copy otterx-u-boot_v2.05.bin from cache folder, paste to your adb folder
verify md5:241A3FD1EDAD0A0D95886DDEB4693E1C
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
I'll give it another go. One thing I forgot to mention, when I rebooted the device to recovery I pressed the power button and the TWRP screen briefly displayed. Then the screen went blank again.
EDIT: I try the fastboot>devices command, power on the device and Windows comes up with device not recognized and the device booted into ROM. I have confirmed this is also happening with my Kindle Fire so looks like I'm missing a driver. Both devices connect successfully within the ROM and Recovery so is it just a bootloader driver issue????
Screen shot of the error and code number.
Windows 7 or 8?
Sent from my XT894 using Tapatalk
sd_shadow said:
Windows 7 or 8?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Windows 7 32bit. I did a search of the forums and found a thread with a link for signed Kindle Fire drivers from Amazon. Downloaded, installed and rebooted system. Plugged in and powered up my Kindle Fire into SlimKat and Windows recognizes device and I'm able to transfer files no problems. I'll have to try the adb and fastboot commands later, I have to get my son to a college entrance exam soon. I'll let you know the results when I return home.
Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.
sabres032 said:
Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.
Click to expand...
Click to collapse
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode
sd_shadow said:
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode
Click to expand...
Click to collapse
I'm on the OtterX partition, will the drivers still work or do I have to revert back to Amazon partition?
shouldn't need to revert, just use the install drivers.bat, then reboot pc
sd_shadow said:
shouldn't need to revert, just use the install drivers.bat, then reboot pc
Click to expand...
Click to collapse
Sweeeeet!!!!! Thank you. I've just been tasked with a project from the captain at my fire department so once again I have to put this on hold for a few hours. Once I'm done there I'll give it a go and report back.
I can not get my wife's fire HD 8.9 to boot. When I turn it on the Kindle Fire screen appears for about 5 seconds, then the Kindle Fire goes out, but the screen is still backlit.
This device is completely stock with no modifications. It did this when I turned it on one day, no previous problems.
I tried holding the power button down for up to 2 min. After I hold the button for 10 seconds the backlight goes out and the kindle is completely off. I tried letting the battery go completely dead, then charging it for several hours with no change. I tried running fastboot, but it is stuck at <waiting for device>. My computer does not see it at all. I do hear the chime that something was plugged into the computer immediately followed by the chime that it was disconnected, but nothing shows up in my computer at all.
Is there any hope for this Kindle, or is it bricked for good?
So I assume you're on windows. That beeb you hear is the fastboot mode you need to load drivers really quickly during that beeb. At that point fastboot shoukd work and you can issue a command to get into the factory restore.
I got it working again.
The problem was simple, I did not have any drivers installed on my computer for the kindle (I have never plugged it into this computer before it would not boot). I found the drivers to download here: http://forum.xda-developers.com/showthread.php?t=1890413
I was then able to get it into fastboot and recover it with instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2011126
Ok so really need some help as I’m on the verge of giving up!! I don’t know anything about what you guys are doing!! My kindle fire 8.9 just decided to go ‘red screen’ on me when I turned it on one day. I hadn’t done anything to it to try to mod it or anything- it just turned on and went straight to the red screen and that’s all it’s done since. I’ve tried disconnecting the battery for a while and then reconnecting - no joy. I’ve followed tutorials here to try to reset it via fastboot but have got stuck where it says ‘waiting for device’ - I plug it in and turn it on but it doesn’t find it and nothing happens. I don’t know how to get it into fast boot mode any other way and don’t have any other ideas for things to try so any help would be really great or I’m just going to have to chuck it out?.
I got it into fastboot earlier without the special fastboot cable. I had lubutu running on a memory stick. I installed the adb and fastboot stuff. The first time it wouldn't say "waiting on device" or whatever but the second time before installing the adb and fastboot stuff I changed the settings so it was normal releases and unsupported sources or whatever so it'd draw from a bigger pool. Then the waiting on device part showed up. I plugged a normal cable in and was turning it on and off and all that. But what made it go into fastboot mode was having it plugged in then holding power button to turn it off then I pressed and held down the power button and I think it's the volume down button (the one closest to power) then it loaded into fastboot ^_^. I'm gonna try to actually fix it now.