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.
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.
Back story: I purchased a used Kindle Fire on Ebay about a week ago, not knowing that it had been rooted. I was looking for a standard Kindle fire for my son so he would stop using my tablet (lol) and the parental controls are better and more books and so on... none the less when I got it I noticed that it booted differently (I had a kindle fire prior) and it booted into Android. I have had problems with trying to be able to get my computer to recognize it. It looks for missing drivers and I have been all frustrated, but figured that we would just have to download off of it, well, we went on a trip this past weekend (11 hours) and my son wanted to watch a movie, turned it on and it wont boot past the yellow triangle now. I have tried a hard reboot, I have tried to turn it on and hold it and watch for the orange light to no avail. The light is either green or its powered off.
I don know what to do at this point? I cant hook it to my computer (wont even recognize as an F drive or mass media) and I cant boot past the orange triangle. Yes, I am a newb (apologies) but a very frustrated one if that counts?
Sadly I think the thing is bricked and I will take a $150 hit (ugh)
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Yes, you would be correct in that I just want it stock, sure Android is great but my son is 4 and he just needs the basics for his books and angry birds lol. So, I attempted what you said, powered off all of the way and turned back on, as soon as I see the yellow triangle I hold the button and it wont turn orange, it will just power back off. I used to be able to touch the screen when the yellow triangle came up and it would take me into some menu (TWRP?) but it wont do that anymore either, its just remains either off or on the yellow triangle.
soupmagnet said:
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Click to expand...
Click to collapse
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
soupmagnet said:
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
Click to expand...
Click to collapse
Save yourself the trouble mail it to me I will fix it then you reimburse me the return postage or better yet I can show you how to fix it without even mailing it . 150 for a first gen kindle is pretty high you kinda already got taken.
[email protected] said:
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
Click to expand...
Click to collapse
Pay attention to what I said previously...
soupmagnet said:
Extract the KFU and run the install_drivers.bat
Click to expand...
Click to collapse
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
I think I am officially over this thing... I downloaded the drivers and went to plug in the kindle fire to the computer and now its just looping the triangle... it turns on for a second and then off and on and off and so on... UGHHHHHH....
soupmagnet said:
Pay attention to what I said previously...
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
Click to expand...
Click to collapse
You let the battery die. I won't go into how it happened but to get it to charge, you need to...
With the device turned off, Plug the device into USB and hold the power button until it shuts off again. If you can get it to stay off, leave it plugged in for about half a day and turn it on again.
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
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
you need a usb keyboard and then you need to press a combination shown on youtube: , Don't be afraid it is very hard to do it but i can confirm it works 100% for sure!! The timing for holding the key press is all that matters to be successfully...
Try different timings if it's not working on the first run but you need then to hold the buttons for very long time until your fingers feel dead....
..im not sure if adb is working in "safe mode" you need to test that. If yes - you could use "adb reboot recovery".
2. you need to reflash Magisk in core mode.
Aq
dougie175 said:
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
Click to expand...
Click to collapse
You haven't killed your stick, install fastboot drivers and app.
Connect your stick to your pc via usb.
Enter
Code:
fastboot devices
when you see black screen with amazon logo, it should be inside fastboot mode
(If somehow you flashed update to boot.img as written in the guide)
If you see the stick in fastboot mode,
Pull twrp from kamakiri.zip
Place it in fastboot folder
Enter
Code:
fastboot flash boot boot.img
(boot.img or whatever the name of your twrp image)
Code:
fastboot reboot recovery
It should work, if not you can use shorting method again.
Thanks very much both, I will have a play around this evening when I get home from work and the kids are in bed, hopefully with the info above I can get back to recovery again.
Thanks for the help gents, in the end I had to do the shorting method to get the stick to do anything. It took about 6 attempts before kamakiri script even registered it as anything being plugged in, it just kept saying wait for boot.
Once it realised the stick was present and shorted I was away though, I have ended up having to factory reset and wipe everything so will need to start again with it but I am just pleased I don’t need to shell out again for a new stick.
Thanks again for your help