Related
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.
Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU? Amazon said they would send a replacement, but I'm wondering if I'll have issues if they see it's been rooted...
Update 6.3.1 has left me on this screen, and as of yet I have not been able to get around it. The computer will only recognize it for about 5 seconds when it is plugged in, but then the LED on the KF goes Orange and it disconnects.
I'm looking at getting the factory cable.
Unfortunantly when I ran the KFU I did not install any other recovery options other than rooting the device. (Crossing over from the jailbreaking on the iPhones, you could get the device is recovery without any big deal and I assumed it was the same with the KF...oops)
Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
While in recovery, look for an option to mount your sdcard.
When it is mounted, it will show up on your computer as an external drive.
From your computer, transfer the "Flash.zip" from this link: http://forum.xda-developers.com/showthread.php?p=25598837 ...to your sdcard.
Then use recovery to flash "Flash.zip" and reboot.
When it reboots, hold the power button until it turns orange again and use the selections at the bottom to change your bootmode. To scroll through the selections hold the power button for a second and release. When you have the right option selected, leave it alone for a few moments and it will select automatically. You may need to reboot.
Avidmtbiker said:
Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU?
Click to expand...
Click to collapse
This is not the stock boot loader screen, it is an older version of FireFireFire.
soupmagnet said:
Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
Click to expand...
Click to collapse
I've done this...
But there's no response from the KF, the screen doesn't change. The LED does go Orange, but it would anyway - even without pressing the button.
The computer is unable to recognize it at this point.
As of now it seems only to turn on whenever the USB cable is plugged in, I'm guessing the battery is dead.
Any more suggestions? I'm leary of sending it back in with modded software, I imagine they're smart enough to check that...
Ah, so you don't even have recovery installed. I guess I should have seen that in the OP...I'm such a noob <hangs head in shame>
OK the first thing you need to do is educate yourself a little bit about the Kindle Fire, the different bootmodes, and the difference between adb and fastboot:
http://forum.xda-developers.com/showthread.php?p=23747567
Then you need make sure your drivers are in good working order:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
When you have a good foundation to work from, we'll get recovery installed and continue to fix any other problems you need help with.
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.
SO recently i tried to root my kindle using one of the guides unfortunately i somehow messed up during it or something, but the problem i have now is whenever i turn my kindle on it has the yellow triangle with a fire logo in it and at the bottom it says "press power button for recovery". Simple enough only the second problem is i do not have TWRP or anything like that so pressing the power button literally does nothing. Unfortunately as well when i plug it into the USB it will identify that something is connected but it won't install it to the pc because it cant find some hardware or something. So i cant get it to start up or connect it to the pc and am desperately looking for a solution. Thanks to anyone who can help.
First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
jma9454 said:
First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
Click to expand...
Click to collapse
Attached is a picture of what my kindle screen looks like. I tried resetting it, plugging it into the computer, etc. but this screen never changes. Also on my pc it doesn't recognize it as a kindle, it recognizes it as an unknown device. So I can't put any files onto my kindle at the moment because my PC keeps telling my me driver is not working or something. I attached files showing what my pc says as well. Also I apologize for the bad quality of the pictures i don't own a very nice camera at all so I apologize in advanced for that. The last 3 are readable the 1st one is basically just a yellow triangle with a fire symbol in the middle and it says "press power button for recovery" but nothing happens when i press the power button, and the 2 photo is a little bit blurry but all it says is:
Unknown Device
Device Type: Universal Serial Bus controllers
Manufacturers: (Standard USB Host Controller)
Location: Port_#0009.Hub_#0002
Device Status:
Windows has stopped this device because it has reported problems. (Code 43)
The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.
soupmagnet said:
The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.
Click to expand...
Click to collapse
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?
KindleFail said:
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1405052
http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit
Since you will need Linux anyway, you might as well download and install SoupKit. It comes with Firekit and will probably make your life easier in the long run.
What guide did you use exactly? I can see if we can update that guide to use the latest FFF because that is a very old alpha version that has had many issues with the yellow triangle in the past. I'm surprised its still floating around here.
Sent from my One V using xda app-developers app
Stuck at boot logo
Hey all,
I'm not sure if this is the correct place to post but I didn't want to make a new topic and this seems to be in the area of what is wrong with my kindle... I tried the new KFU v0.9.9 on my first gen KF running 6.3.2. I have rooted it before (not on 6.3.2), but unrooted and restored to factory settings because I thought I was going to sell it. However, the plans fell through and I am keeping it so I wanted to re-root and all that jazz....
My question is, how do I get it boot past the boot logo? I used the KFU, but firstly when it prompts it says:
'findstr' is not recognized as an internal or external command, operable program or batch file.
So none of the commands pop up, however they are still there... For example, i followed:
"Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer."
And I can get to fastboot, but it says there is no device connected to my computer. If you need more details on the problem I'll be glad to give them to you. Hopefully someone checks this thread again
Thanks
What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?
soupmagnet said:
What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?
Click to expand...
Click to collapse
I'm running a 64 bit version of Windows 7 professional.
There's nothing in the device manager when I plug it in.
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