Develop Bugs

[Q] Kindle Fire Boot Question

I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.

Luppertazzi said:
I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.
Click to expand...
Click to collapse
Red triangle? Blimp?
Read this...
http://forum.xda-developers.com/showthread.php?t=1623244

Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
I gave you a link to a guide that fully explains what's going on and why "nothing happens." It also gives you a suggestions on what usually works and if it doesn't, the next thing you should attempt in order to fix your problem. If you don't want to try that, you can crack your case open, pull out the battery, find a charger that will charge it offline and stick it back in there.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
Never let your battery complety drain with the new kernel.
Try this:
1. Overnight charge with an iPhone charger (even the Kindle show yellow triangle).
2. If above method won't work,
Extract the kernel from stock firmware (get it from amazon)
Flash the kernel in fastboot (yellow triangle)
Reboot
Charge with wall charger at least 4 hours.
If you're lucky then you can flash Hascode #8 kernel, wipe cache/dalvik and boot normally.

Is it charging even when the yellow blip is on from a wall outlet?

Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.

Luppertazzi said:
Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.
Click to expand...
Click to collapse
Unzip the archive and extract the .bin file inside it.
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on post #3 to learn how to use fastboot.
Then you'll want to get the device into fastboot mode by issuing a command like...
Code:
fastboot getvar product
and then rebooting the KF. The post above will tell you what to look for when you manage to get it into fastboot mode. It will also tell you how to flash the .bin file you extracted from the .zip file and tell you how to change bootmodes if necessary. Also read the OP for FFF 1.4 for details on how to use your new bootloader.

http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html

soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
Click to expand...
Click to collapse
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
Type or paste the command, fastboot flash bootloader fff-u-boot_v1.4a.bin, when you see <waiting for device>, turn the KF on.
Click to expand...
Click to collapse
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?

Luppertazzi said:
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?
Click to expand...
Click to collapse
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.

soupmagnet said:
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.
Click to expand...
Click to collapse
And after reading all that information, which i did, carefully, and trying to understand all of this, the only option i might have is a factory cable to get it into fastboot mode? What about the temporary fastboot, can i profit from that or try to at least?
My main issue is the ADB is offline and i can't get it into fastboot via KFU, shouldn't it be recognized as online nonetheless?
Everybody keeps mentioning the original AC charger, flashing to stock, flashing FFF 1.4a, but i can't even get it to fastboot, recovery is a longshot. How am i supposed to fix this if all the solutions given reffer to fastboot or TWRP, both of which i cannot access?

You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.

soupmagnet said:
You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.
Click to expand...
Click to collapse
Okay, thank you, that's all i wanted to know. I thought my situation was different because ADB kept showing OFFLINE and i couldn't speculate the temporary fastboot or the normal fastboot. If you're saying this is normal when the battery's dead then okay.
I guess i'm buying a factory cable. One last question. When that cable does get in my hands, all i have to do is plug it in my laptop USB port, then into my kindle, gaining automatic fastboot, and then write:
fastboot flash bootloader fff-u-boot_v1.4a.bin
Click to expand...
Click to collapse
and
fastboot reboot
Click to expand...
Click to collapse
and it should have flashed to the newest 1.4a that bypasses this problem, correct?

Yes, assuming your drivers are in good working order.

When I try to troubleshoot someone else's problem, I do my best to understand what it is that they don't understand. Now, I finally see the reason why you are so resistant to trying my suggestions... When the bootloader says "press power button for recovery" it's not URGING you to do anything. It's SUGGESTING and providing a reminder of how to get to recovery. It's like a road sign that says "exit here for rest stop." Whether or not you pass that point with a full bladder, that reminder is ALWAYS there. It has nothing to do with your present situation.
I think you've been convinced that you need to get into fastboot mode. You can follow my previous instructions and send that command during temporary fastboot. If you are successful, it will stop the temporary fastboot countdown and stay in fastboot mode. You can get the factory cable and that will automatically put you in fastboot mode, but you are still going to have to be able to send it fastboot commands anyway. In either case, you'll have to fix whatever is keeping your computer from sending fastboot commands to the device and that's almost always the device drivers. The only difference between my suggestion and soupmagnet's is the factory cable's ability to automatically keep you in fastboot mode so you have more of an opportunity to diagnose the problem.

[q] usb boot only

Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.

thequietone said:
Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
Click to expand...
Click to collapse
Are you opening up the case each time you use usbboot?
What Firekit script are you using to boot the device?
What happens when it fails to fully boot in to the system?
Is your battery charged?
usbboot only loads a bootloader into memory temporarily. Once you've got the device booted, you need to flash a new bootloader permanently onto the device. I suggest FFF 1.4a...
http://forum.xda-developers.com/showthread.php?t=1632375

usb boot only
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.

Get it booted temporarily disconnect the battery then reconnect it let it continue to charge via usb maybe it will correct your problem. Or replace your system with something stock like without going fully stock paul has a new release http://forum.xda-developers.com/showthread.php?t=1439916 good luck

usb boot only
So unplugging the battery while plugged in via USB doesn't work, however I am able to get it to boot into ICS I just have to unplug the USB right after the script says Flash FFF... That would lead me to believe it's a problem with the boot loader, but I have tried several times to flash it with fff-u-boot_v1.4a.zip with no luck.

thequietone said:
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Click to expand...
Click to collapse
The fact that you are able to use those scripts indicates you are in usbboot mode (4003) or the hardware is defaulting to usbboot on its own which probably indicates that something about your bootloaders is a little off...
Try using the "fix all" script (I don't recall the exact name). This will return your partition table back to stock and then flash both the 1st and 2nd stage bootloaders.
Also try flashing FFF 1.4a again with TWRP and take note of the output it gives you if it fails.

usb boot only
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB

thequietone said:
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
Click to expand...
Click to collapse
See if you can set the bootmode back to normal and reboot it. Running as root...
Code:
usbboot /root/firekit/aboot.bin /root/firekit/u-boot.bin; fastboot oem idme bootmode 4000; fastboot reboot

usb boot only
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)

thequietone said:
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
Click to expand...
Click to collapse
Did you ever have Hashcode's CWM recovery installed on your device or have you always used TWRP?
Have you run those Firekit scripts again after you installed FFF 1.4a?
The only other thing I can think of is that your device's bootmode is set to USB boot and that's why it doesn't load up the bootloader already installed on your Kindle Fire. It's seems to be waiting for you to use usbboot to send it a bootloader. Get to TWRP again, flash FFF 1.4a and run these adb command to set the bootmode to 4000 and reboot...
Code:
adb shell idme bootmode 4000
adb reboot

The problem is I can't get FFF 1.4a installed. When I try to do it via TWRP which is the only utility I have tried it appears to load successfully, but when I do the reboot, the screen won't come on and there is no power light. So I hold down the power button for the 20 seconds then run the FireKit commands hook up the USB and it boots back up, but won't boot on it's own.

Have you found a fix yet? I may have a solution from my experience with mine, which was bricked beyond imaginable (don't ask how ). I was able to install FFF+TWRP and restore to stock perfectly fine.

It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.

thequietone said:
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
Click to expand...
Click to collapse
You didn't answer the question of whether or not you've used Hashcode's CWMR.
From TWRP, run these commands...
Code:
adb shell idme ?
adb shell parted /dev/block/mmcblk0 unit b print
and paste the output here.
Also, if you can load ICS, download/install smirkit...
http://forum.xda-developers.com/showthread.php?t=1500935
and try to install FFF 1.4a that way. Using smirkit will raw write the bootloader image directly onto the partition.

Here is the screen shot. Couldn't get smirkit installed.

Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!

Still Unresolved
Nope I am still having the same issue. Right now, I just try to keep it charged hoping it won't die, because if it does then I have to USB boot to get it back up and running
dmp2007 said:
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Click to expand...
Click to collapse

shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.

I haven't heard of it responding to touch. Mine works perfectly except for always having to USB Boot if it dies or if someone holds down the power button too long.
QUOTE=dmp2007;28967427]shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.[/QUOTE]

I too get this, I've been through what feels like every thread on here about this, only a few of these show up as the 'usb boot only' though and they all end in no answer. I have tried all forms of partitioning up to and including dd'n the p1.img over top of xloader and p2.img on top of bootloader.
With usb, i can go back fully stock (however, even fully stock wont boot without usb boot.. so its got to be busted xloader or bootloader), i can get TWRP installed, any ROM and its all usable.. until as OP said.. power out or reboot needed. It's bothering me enough just wanting to fix it I keep rebreaking perfectly good installs thinking some nugget I found/missed re-reading endless posts is the one.. just in case someone else comes through with this, here are my findings:
happened to me as originally I bricked to the point had to crack it open and short it to get it to boot via usb, finally working well using liveUSB firekit. However, from that point on, would NEVER boot on its own, and would NEVER shutdown/reboot without needing 20-30s of power button molestation. perhaps this is left over issue of the pin short... dunno
Once i figured out I could usbboot, basically went on with everything as normal. recovery, roms, back to stock, back to rom, etc etc. What seemingly never works, or simply oui can never get to, is the bootloader. All indications that I have known/been able to check seem to think its iinstalling, perhaps we are just never making it to it (xloader death)
So then I went crazy and tried everything from adb/fastboot raw on Mac, windows and linux, setting bootmode to 4000 every way with every tool listed on this site possible.. no joy.. usbboot is a must. Tried zeroing the mmcblk0p1/p2 and writing good versions on top, nothing.
Current state.. if I, via adb/fastboot/twrp/recovery do a reboot or shutdown.. the kindle shuts down screen and led's only (sometimes even leaving the green power light on, but almost ALWAYS just all black, but not off) .. dmesg notes that its stuck in a usb connect/disconnect loop, with an error:
new high-speed USB device number 33 using ehci_hcd
unable to get BOS descriptor
New USB device found, idVendor=0451, idProduct=d00f
New USB device strings: Mfr=33, Product=37, SerialNumber=0
Product: OMAP4430
Manufacturer: Texas Instruments
USB disconnect, device number 33
rinse, repeat, about every 3 seconds.
As you can see, BOS descriptor can't be found.. which is just a little stupid because the port its plugged into is 2.0
bcdUSB 2.00
but maybe there is still something there? not changing any port though, usbboot has no problem.
I sniffed the traffic of the usb bus while plugging in the USB cable after shutting down via 30 second hold, and its pretty much the same thing, just bouncing the connection before it has time to get started.. so it seems to be hitting this "issue" both on shutdown/reboot and startup. As I can't really tell, with usb being the only way for me to talk to the KF, I can only assume after a hard shutdown when I push the button again its probably doing the same thing (no lights, no screen), but I can confirm once I plug in the usb and it tries to boot itself.
Only sort of difference is sometimes it can go down into the dark reboot and I am able to run usbboot and it comes back up (usb never unplugged) but its been sporadic so I haven't chased it.
At this point I just want to figure out exactly what bit needs flipped in the front somewhere so I can reboot my KF like all the cool kids so I'll probably keep hacking on this issue until I really really brick it or hopefully help comes along or I figure it out myself. One good sign is I know have completely working dev/hack environments on OSX, win7, liveusb ubuntu AND linux mint debian so, I guess that is something.
YOU ARE NOT ALONE USBBOOT ONLY PEOPLE!! one love. =P

[Q] Need Help - Bricked Kindle Fire

I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.

gwmadrigal said:
I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.
Click to expand...
Click to collapse
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.

Thepooch said:
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.
Click to expand...
Click to collapse
I have done a lot of experiments with my SGS2 about installing ROMS using ODIN or CWR, backing up my own images and making backups. Most of the work I do though is in CWR. I haven't dealt with TWR yet. I also installed ICS on my HP Touchpad. So, even though this is the first time I deal with the KF, I already some experience working with ROMS and images.
Back to the process. I installed the FFF using the Kindle Fire Utility. The KF was forced to fastboot mode via the factory cable. At first I could see on the KF splash screen with the black and orange logo, and now the KF is booting using a Black and Blue kindle fire logo with 1.4a on top. At the bottom of the splash I see instructions of the bootloader selector indicating to press the power button and select the mode that I want to boot. Either Normal Mode or Recovery Mode.
I flashed the TWRP 2.2.2.1 in fastboot mode using my command prompt by putting this code:
Code:
fastboot -i 0x1949 flash recovery [path]\openrecovery-twrp-2.2.2.1-blaze.img
I was following the instructions on this guide.
http://forum.xda-developers.com/showthread.php?t=1638452
I got stuck on step 3 after attempting to boot into recovery mode.
I can select which boot mode I want to go, but none of them work. I only get on the bottom of the screen saying Booting... and then the KF shuts down.
I suspect the battery had a good level of charge, but I can't tell for sure.
Thanks for everything.

Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot

soupmagnet said:
Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot
Click to expand...
Click to collapse
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.

gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
What happens when you change the bootmode to 5001?

soupmagnet said:
What happens when you change the bootmode to 5001?
Click to expand...
Click to collapse
It accepts the command.
The command prompt responds saying something like it took 0. something seconds to execute the command.
Thanks for reading my thread.

If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.

soupmagnet said:
1. If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
2. If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
3. If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.
Click to expand...
Click to collapse
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.

gwmadrigal said:
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.
Click to expand...
Click to collapse
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.

gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.

Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.

soupmagnet said:
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.
Click to expand...
Click to collapse
I tried reloading the u-boot using fastboot and the upload was successful. But it's doing exactly the same.I guess my only question right now, do you know of any good guide that I should start reading to get my feet wet on what the firekit is and how to get started?
Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I have nothing to lose. This KF is already bricked. I can certainly try anything. Which cable do you suggest I use? the Factory cable or the USB cable?
I think I answered my own question now. Using a regular USB cable puts the KF in the bootloop. I will use the factory cable instead. I shut down the KF, put the factory cable connected to my computer and the KF. Right now the KF is in the KindleFire splash screen waiting for fastboot commands of for me to use the button to tell it which mode to boot. I will leave it plug overnight.
Thanks for replying on my thread and trying to help me.
soupmagnet said:
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.
Click to expand...
Click to collapse
I posted a video in utube of what the KF is doing, so you can see what I'm seeing.
Link
Thanks for coming back several times to reply on my thread.

That looks like your battery. From what I can tell, the device is just rebooting, not shutting down.
Unplug the device and hold the power button to perform a hard shutdown.
Plug the device in (it should power up on it's own) and hold the power button to shut it down again.
Leave it plugged into the computer until sometime tomorrow and try again.

Same thing I was thinking 5 second bootloop Thank you the video was very helpful to see just how its acting. Use stock cable to charge not factory.

OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.

gwmadrigal said:
OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.
Click to expand...
Click to collapse
I think you're fine let it rest.

[Q] Kindle Fire powers on, flashes and shuts down

I have come into my possession a Kindle Fire 1st generation. When I got it, the youngster said it was “hacked for the Amazon App Store”… and the battery was dead. I traded an older laptop for it. I put it on a charger for a day or so and left it. It would boot to the “Stock” logo for several seconds, then the backlight would go slightly brighter and it would shut off.
I started reading up about some of the power-on issues around the web. I found most of my answers on “xda-developers.com” for my TF101 so I gravitated here.
Here is what I’ve done so far:
1. Acquired a factory cable... SO useful.
2. Flashed FFF v1.4a and TWRP v2.4.4.0
3. Played around with fastboot.exe commands -update, flash, erase, getvar, reboot, help
4. Flashed a stock bootloader and recovery… trying to get it to charge.
5. Disassembled and tested battery voltage… 4.10VDC on a 3.7V battery. That sounds good to me.
6. Tried the firekit boot from Live-USB. Won’t stay powered on.
Right now, I’ve flashed the FFF 1.4a and TWRP v2.5. What happens is, in normal boot, the fire boots to the FFF logo (White &Blue) goes to “Booting” and the power switch LED gets slightly brighter, then the backlight goes slightly brighter and the whole thing shuts off. If I push power to go to recovery, the fire shows “Booting.” Then, the power switch goes orange, then it goes off, then the whole thing shuts down. I cannot do any ADB commands because the Fire will not stay powered on in that mode. The factory cable keeps it powered on, but I’m stuck with fastboot.exe commands in that mode.
I do not have a stock charger. I’ve been using my charger from my TF101 and a cable from my phone or the factory cable. I’ve been futzing around with this thing for a few weeks and would like some input. I haven’t found an identical issue so I’ve decided to create a thread.
I’m wondering if I have a bad gate on the memory chip… I’ve seen desktops and laptops shut down with bad memory in the past. I’m reasonably savvy with a command prompt and not afraid to crack a box.

Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.

soupmagnet said:
Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.
Click to expand...
Click to collapse
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.

pmrmx774 said:
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.
Click to expand...
Click to collapse
What command did you use to install TWRP?

soupmagnet said:
What command did you use to install TWRP?
Click to expand...
Click to collapse
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.

pmrmx774 said:
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.
Click to expand...
Click to collapse
Use fastboot to flash this to your system partition and see if you can boot normally.... http://d-h.st/NzN

Perhaps it is hardware, not software
Just had a very similar issue. Turned out to be stupid simple.
Use spudgers to gently take the back off the case (a small flathead screwdriver should do the trick). then check the connection between the battery and the motherboard. In my case, my daughter had dropped it enough times that the connection was not all the way out but not enough in. This caused the exact behavior you are describing. Took me 2 minutes to fuss with once I got motivated.
Jon

[Q]bricked kindle in usbboot mode.

I recently recieved this kindle as is from a friend and i was asked to fix it, i don't really have any information to go off of other that what i could gather. So far, it doesn't turn on/charge, in windows it's recognized as a OMAP4430 device only for a second or two, from there i tried using FireKit on ubuntu via usb. that gave me some success, after using usb_fix_parts_and_install_fff_twrp i saw the yellow triangle on the screen; however, the script seemed to stop with this:
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
and won't progress any further. i'm not really sure what to do at this point since i feel so close and it would be a shame to quit now.
I've also tried using multiple USB cables and a fastboot cable, but none seem to be making a difference. so please if you know of anything that would help, it would be greatly appreciated.

You only have a small window of time to get everything through. When the usbboot script hangs at "waiting for device", leave the script running, unplug the device, hold the power button for 15 seconds, create the short and plug the device back in.
You may have to do it a couple of times.
Once you see the yellow triangle, don't shut the device off until you install FireFireFire1.4a while in recovery. You may have to use adb to push the .zip file to your sdcard first though.

Oh, ok thanks. i didn't know i still had to preform the short, since it was already in usb boot mode. anyway trying it now.

I'm not sure if I'm doing it correctly. I followed what you said and after shorting the device, and plugging it back in, it brings up the yellow triangle again. But pressing the power button doesn't bring me into a recovery and the script still says waiting for device

I should have clarified that a bit, but oh well.
Go ahead and reboot to try to access recovery with the power button. Sometimes when you reboot, depending on how everything went, the device doesn't come on again and you have to start all over...but you should be fine though.

=/ not too much luck there...maybe i'm shorting the cpu incorrectly, not sure. once the script hangs i unplug and power off the device, and essentially just any old conductive piece of wire should do and connect it to the point and the metal bar, right? i'm using a male to male jumper cable at the moment. While doing this i've noticed a couple times the kindle would power back on and display the yellow triangle but still no other responsiveness or progess in the script itself.

When the yellow triangle is displayed, do you have access to fastboot?
Try sending 'fastboot getvar product'

i guess not. it just sits at "< waiting for device >"

Try using a safety pin to make the short....that might help.

so slight update, it turns out i have no problem booting a firefirefire from usb, but from there it just refuses to initiate fastboot and ubuntu can't seem to recognize it. i thought it might have been a possibly issue with the specific version of FFF i was booting from, but so far 1.2, 1.3 and 1.4 all give me the same issue.

dragon0010 said:
so slight update, it turns out i have no problem booting a firefirefire from usb, but from there it just refuses to initiate fastboot and ubuntu can't seem to recognize it. i thought it might have been a possibly issue with the specific version of FFF i was booting from, but so far 1.2, 1.3 and 1.4 all give me the same issue.
Click to expand...
Click to collapse
Make sure you have FFF1.4a and run your fastboot commands as root in Ubuntu.

so i just found out something interesting. i had a spare fully functional kindle that i put into usb boot mode with the shorting trick, and did all the steps, and fastboot was able to recognize it. i haven't done anything differently with the currently bricked kindle, but it just wont get past "waiting for device" when issuing any fastboot command. so at this point is there really anything i can do?