Develop Bugs

[Q] Stuck on Kindle Fire Logo Screen with no ADB

OK, folks. Hopefully somebody can help me out of this mess I've caused. I'm currently stuck on the Kindle Fire Screen with no access to ADB to get into fastboot or anything else.
Here's how I got there:
Fire was rooted and had CWM recovery installed using KFU
Downloaded Pure AOKP ICS ROM with 3.0 kernel
Flashed with CWM like an idiot, instead of using TWRP like the instructions called for
Here I am -- My Kindle shows up in Windows 7 Device Manager, but can not be found via ADB; it just hangs on the Kindle Fire boot screen.
I've done a lot of reading on the subject and I'm really hoping I won't have to resort to getting a factory cable.
Any help would be greatly appreciated, folks!

The only thing I can think of atm is either the KFU or the kindle fire unbrick utility. Try both.. good luck..

Sounds like you are not bricked and fast boot is possible.
I would recommend trying to fast boot twrp onto it and get into recovery.

Stuck at "kindlefire" bootlogo

Hi,
currently I am stuck at the non flashing "kindlefire" bootlogo.
I cant access TWRP anymore and my computer also does not recognize the kindle fire.. what options do I have to get a bootable kindle fire again?
What I have done in the last 4 hours to end up in that state:
follow this thread: http://forum.xda-developers.com/showthread.php?t=2105077
IMPORTANT: WHEN COMING FROM STOCK AMAZON OS
-Make sure you wipe everything while in TWRP before you flash anything!
Click to expand...
Click to collapse
I did like statet and ended up without OS because I wiped everything like statet.
Then, after booting into fastboot I tried that tool:
http://forum.xda-developers.com/showthread.php?t=2096888
It said that I recovered my kindle to stick firmware but In fact I am stuck now with the bootscreen.
Can anyone help me please?
after following this thread

Do you have a KF1 or KF2?

As soup said, are you sure you have a Kindle Fire 2?
Did you buy it new, and did it come in a brown or black box?
You might be OK to flash TWRP again, then use ADB push command to get a 10.1 ROM onto your Kindle. I would talk with Soup a bit in case there is an issue with his tool.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

[Q] Kindle Fire 1st gen Stuck at Boot Logo

Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.

jaredahuey said:
Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.
Click to expand...
Click to collapse
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.

Thepooch said:
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.
Click to expand...
Click to collapse
I am aware of that however, I cannot boot to cm10. If i could boot to cm10, I would know what to do but right now I am still stuck at the kindle fire logo.

[Q] Kindle Fire 8.9 Stuck on static boot screen.

Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?

Hmm, off flashing from fastboot should typically work, since you were attempting to flash cm 10.2 I have to ask something because I am slightly uncertain of this myself, but did you ever get twrp running at one point before all this happened, and second if so did you ever wipe any of the partitions or try to flash the ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Unfortunately no. I was never able to get into TWRP as the blue logo has never appeared. Directly after my first attempt at this I rebooted and got the red screen or wall of fire. I "fixed" that by reflashing stock boot, bootloader, recovery, and system image partitions to 8.1.4. Yet instead of a working device I now have either a boot loop or a fixed orange logo. I have gotten the device into stock recovery once (haven't been able to reproduce this result) but it shutdown while the process was underway(About half way??). I have also gotten the device to boot into a animated logo that then proceeded to a data corruption screen, but before I could even read the entire message the device shut off and began another set of boot loops. It looked like a amazon stock os prompt screen. Before this even began I had a normal Kindle fire that I had rooted. I forget what software version it was on before all of this unfortunately.

Sounds like the system image is slightly corrupted or something if the os had that kind of error about data corruption but you said the md5's march so that is weird. You try reflashing the boot partition again since reflashing system didn't work? This is frustrating, mainly because with out adb access from a decent recovery I have no Linux commands to work with, if worst comes to worst I think there's a way to reform at the system partition from fastboot but I wouldn't go for that just yet, I don't know the command offhand but if you did the wrong one I think there's a way it would clear all data on all partitions which would be very very bad. I'll ask hashcode what he thinks cause this is weird.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I have tried flashing all partitions before. Will try again soon. Also, I have another piece of information as well even if it isn't relevant. I originally bricked my Kindle at first, flashed the wrong bootloader. So I bought a for-parts Kindle (Same model) that had a busted screen and took out its motherboard and placed it into my device. Then I rooted the stock os on the new MB and the rest of the story is already in this thread. It still charges and fastboots but nothing other than a static orange boot screen so far. Thank you for helping me out on this; really hope that this can be fixed.

Thinkwithportals said:
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Click to expand...
Click to collapse
"I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick."
I have the same problem but when I try fastboot mode the computer wont even find the device

Alrighty, well. I woke up this morning and decided to re download all of the system, boot, and recovery image files. I flashed them to the device and it again boot-looped for about an hour. I set it up next to me and started reading through the forums for repair via soldering eMMC to SD card reader. I look down and what is starting back at me? A fully working Kindle waiting in initial setup for input... Yet within about a minute it is back into the old boot looping game again. Hardware problem? A short maybe???

possibly or maybe it has a bad emmc chip.
Sent from my LG-P769 using xda app-developers app

Hm, well I think I might just give up on this MB then. I am considering looking into my hard-bricked motherboard and using Kurohyou's pin-out. Even if my soldering skills are a bit rusty.
Thank you anyway for your help. I will report my progress in the other thread from here on out.

Careful not to melt the contact pads, I just ruined one of my Xbox 360 controllers today unsoldering a trigger, cheap parts.... Long story short controller falls in dogs water bowl, circuit board goes in rice, rice gets stuck under a trigger, I ruin controller unsoldering trigger... Least I have 4 more. But anyways yea careful, I suggest at least an st7 tip and not to let it get to hot, read someone else managed to melt a contact on a kf2 I think it was.
Sent from my Amazon Kindle Fire HD using Tapatalk

[Q] need help with boot loop

Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??

according to FAQ 16 Frequently Asked Questions - Amazon Kindle Fire
If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse
yes you need a fastboot cable
or
there is a [UTILITY] Kindle Fire Unbrick Utility V1.1! that you can try

kfs325 said:
Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??
Click to expand...
Click to collapse
Not sure of the state of your Kindle Fire G1 (It's not rooted? Are you sure?), but this sounds similar to what I ran into trying to install CM11.
What version of TWRP do you have installed? If it's 2.2.2.1 and you're trying to install a ROM with KitKat (CM11) you can run into this. I did. When I installed TWRP 2.7.0.1 I could install CM11 just fine without the boot loop.
To install TWRP 2.7.0.1 I found that you could only do so by:
When you turn Kindle Fire on, hold down the power button to cycle through the options when you see the Kindle Fire logo. You want to land on the Recovery option.
Mount storage from TWRP 2.2.2.1 on a PC and copy CM10.x.x and related GApps to SDCARD
Factory reset then reinstall CM10.x.x (with Gapps for that version)
Install Flashify from the PlayStore
Download the latest TWRP for otter/Kindle Fire G1 (2.7.0.1)
Install it with Flashify
Download CM11 and related ZIPs (GApps kk, Change to Nexus 7, etc) to Downloads directory
Restart into TWRP recovery (should be 2.7.0.1 now), and factory reset/reinstall CM11 and related ZIPs from Downloads directory
Should be fine now.
I found that I could only do it this way because for some reason Kindle Fire Utility Kit and ADB couldn't work with my Kindle anymore with TWRP 2.2.2.1 (don't ask, I don't know why). This way works. Just make sure you have a copy of a version of a ROM and GApps on SDCARD at all times since mounting storage might not work anymore in TWRP (again, I'm not sure why). I tried it again and again, but I couldn't get it to work and it might be the same for you. Keep in mind this is for CM11. If you're using stock, then follow sd_shadow's advice.