Related
I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
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
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
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
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".
So Ive read multiple threads from this forum and tried the suggested methods and nothing has worked at all. My Kindle Fire is stuck at the Yelllow triangle logo and I have no clue how to get it back working at this point. I originally rooted using BreakDroid using Clockwork recovery and was successful running the Energy ICS Rom.
I attempted to flash the Miui ICS Rom and thats where it went all bad and has been stuck at the Yellow Triangle ever since. I've tried to use the KFU 0.9.6 but my computer only recognizes the kindle as a "android phone" but doesn't see that's it plugged in. KFU states that it's waiting for device when trying to run any of the commands and I have reboot to get it to proceed but none of the commands work and only return me back to a frozen triangle screen everytime.
So I need some serious advise on how to start over and get my kindle fire back to stock and out of this dreadful yellow triangle screen thats haunting me! Please post any instructions based on your experiences or expertise.
Please Please Please Help!
Thanks in advance.....
Are you able to access recovery?
soupmagnet said:
Are you able to access recovery?
Click to expand...
Click to collapse
Nope not at all everytime I press the button and it turns orange nothing happens and it completely freezes and I have to reboot completely.
How comfortable are you with fastboot commands?
soupmagnet said:
How comfortable are you with fastboot commands?
Click to expand...
Click to collapse
Not the best but if you have some instructions I'm sure I can figure it out lol at this point I have no choice
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I used the Kindle Fire Utility and did option #1 to boot normal mode but it didn't work but I'll these methods and post some feedback on it....thanks a lot
soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I understand all of that info but doesn't really lay out any steps to take to fix the issues I'm having. I'm not a newbie to rooting this is just the first time I've experienced this particular problem
Disregard
Thepooch said:
Disregard
Click to expand...
Click to collapse
Thanks for the positive advice
I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.
Thepooch said:
I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.
Click to expand...
Click to collapse
I actually got it fixed using breakdroid and thank god it worked but thanks for the advice I know exactly what not to do the next time
Had a similar problem brickoid sorted me
Sent from my i777 using xda
aokp on neak yo!
I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of. I've tried KFU, Kindle Fire Debricker/Unbricker, followed various tutorials, and even made my own factory cable all to no avail yet. My Kindle simply keeps rebooting itself into the stock OS 6.3.1 of amazons about every 30 seconds +/-. Nothing I do can/will change that. When it starts up it shows the kindle fire bootloader then onto the main "Home" screen where various notices come up stating that basically everything is NOT working and they've all failed miserably and horribly. Then onto the next reboot. There is no longer any sort of recovery as far as I can tell. I cant get it to respond to any sort of fastboot anythings. On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened, far as I can tell I was in TWRP recovery when I tried to flash the stock firmware from there and everything just failed. Anyhow, if anyone has any idea what so ever on what to try or where to look for an answer, I'd be eternally grateful. Or if any other info is wanted, just let me know. Thanks all for any advice given ahead of time.
http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."
24861 said:
I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of.....On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened
Click to expand...
Click to collapse
Try right clicking and select run as administrator.
Sent from my Amazon Kindle Fire using Tapatalk HD
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you
24861 said:
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you
Click to expand...
Click to collapse
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you
24861 said:
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you
Click to expand...
Click to collapse
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.
soupmagnet said:
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.
Click to expand...
Click to collapse
Okay. So far so good. Is doing just what you said, except for I evidently have no fastboot driver installed. Plus it doesnt recognize that the fire is plugged in (in fastboot mode) inside the device manager. So....? Is there a specific driver (fastboot driver) that I need to load (and do you have it?) and how do I get the fire to atleast become recognized?
Thanks again bud
That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Its white and orange. Although I believe my current issue is that it is stuck in fastboot (4002) mode. Even though it still reboots into normal mode, it remains stuck in fastboot. And I am unsure as to how to get it back as nothing will recognize it, so no drivers will ever install. So I am currently trying to let it run dry of juice in hopes it will reset when its dead. Any ideas?
Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"
Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.
soupmagnet said:
Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
okay. Waiting on you. Thanks
Thepooch said:
Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.
Click to expand...
Click to collapse
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
Agreed it`s still normal to be undetected by kfu how does it show in device manager?
24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.
soupmagnet said:
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.
Click to expand...
Click to collapse
Nothing doin' there champ......... just same old "waiting for device" followed to a tee, but nada. Anything else?
Make sure you're using a 2.0 usb port.
I assuredly am using a 2.0 USB port, but still nada. Anything else anybody? Please.................
So.... back to where I was (I had to switch PC's though). I can get adb running just fine. I can getshell even. But cant do much with as all permissions seem denied. And I have continuous access to the sd card as its always mounted it seems, even thru every restart. So...... what to do now?
Hello everyone...
I've been reading all the threads on this forum for a few months, but I couldn't find an concrete and final answer to this problem:
I have a Kindle Fire 7'' 2nd Generation, and after rooting and installing ICS ( with KF First Aide) i noticed that my wallpaper was flashing and the notification bar was disappearing. I tried to fix it but suddenly the RED TRIANGLE ( with exclamation point inside) appeared and looks like this:
( the triangle)
"Your Kindle device cannot boot.
You can reset your device to Factory defaults to fix this issue (all data will be deleted from the device).
<Menu options>
To reboot your device press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession"
None of those options work, and when I connect the USB cable to my PC nothing happens.
Is there someone who knows how can I fix it, but please... explain from the scratch because I am a total beginner. ( I rooted it only by following instructions for noobs, step by step)
I would be very thankful.
BTW I don't have a Factory Cable and if I have to buy one it would take about 40 days, and if it is possible to make one- I also don't know how.
You will need a fastboot/factory cable, here's a life o on how to make one, there's one on this forum as well but I knew where this was listed in the FAQs thread here so I used it. http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Why would buying a cable take 40 days? I bought one off ebay for £3 and had it within 2 days. It was easier than making my own, and i have a soldering iron.
Sent from my LG-D802 using Tapatalk
chronicfathead said:
Why would buying a cable take 40 days? I bought one off ebay for £3 and had it within 2 days. It was easier than making my own, and i have a soldering iron.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Only one sent from China could possibly take that long. Not sure what you're getting at...
LinearEquation said:
Only one sent from China could possibly take that long. Not sure what you're getting at...
Click to expand...
Click to collapse
Buying one should be quick and easy. You only have to look in the forum to see lots of posts of people struggling with the KF2, and how often a Factory Cable is required.
It should be a recommendation that you get the cable before doing anything.
Sent from my LG-D802 using Tapatalk
chronicfathead said:
Buying one should be quick and easy. You only have to look in the forum to see lots of posts of people struggling with the KF2, and how often a Factory Cable is required.
It should be a recommendation that you get the cable before doing anything.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Actually the tutorials for 2nd bootloader/TWRP for Kindle's of all kinds do suggest that you grt a fastboot cord. Show me one that does not. It falls on the person doing the modding to go ahead and read and maybe do a little bit of research first don't you think?
Edit: The problem is some tutorials failed to update when the firmware was patched creating many bootloops if the firmware was not downgraded to 7.2.3 or 7.3.0 first. Still warnings always exhisted to backup and get a fastboot cord.
How to root
LinearEquation said:
Actually the tutorials for 2nd bootloader/TWRP for Kindle's of all kinds do suggest that you grt a fastboot cord. Show me one that does not. It falls on the person doing the modding to go ahead and read and maybe do a little bit of research first don't you think?
Edit: The problem is some tutorials failed to update when the firmware was patched creating many bootloops if the firmware was not downgraded to 7.2.3 or 7.3.0 first. Still warnings always exhisted to backup and get a fastboot cord.
Click to expand...
Click to collapse
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
idam_cuco said:
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
Click to expand...
Click to collapse
Glad your tablet is working.
So first you want to go here http://forum.xda-developers.com/showthread.php?t=1886460 and download "Root_with_Restore_by_Bin4ry_v31: [Improved Root-Method by Ariel Berkman]" There is a of stuff in that post but v31 was an update to the OP so trust that it is correct. You will download and run the bat and root your KF2.
Now to get a custom ROM you first need to install a 2nd bootloader and TWRP (Team Win Recovery Project) The best thing you can do is read and ask if needed so you don't brick your Kindle.
Here is Hashcodes thread on how to install a 2nd bootloader and TWRP http://forum.xda-developers.com/showthread.php?t=2100963
Here is Hascodes thread on getting the custom ROM put on your KF2 using ADB commands http://forum.xda-developers.com/showthread.php?t=2100963
Here is a list of custom ROM's for KF2 http://forum.xda-developers.com/showthread.php?t=2462878
Make sure to not use anything not intended specifically for the Kindle Fire 2 (otter) or you may hard brick your Kindle.
idam_cuco said:
Hey, thanks for the advice
I recovered ( unbricked) my Kinde 2gen and it's working now.. but how can I root it now and instal ICS or JB on it?
I did it once on the same device using KF First Aide ( the one with 45 options) but now it cannot gain root access... why?
So:
1. How to gain root access?
2. How to instal android ICS or Jelly Bean on it, but with noobs description please
Thank you
Click to expand...
Click to collapse
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
crt2389 said:
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
Click to expand...
Click to collapse
Plug your fastboot cable in. Then run the KFFirstAide.
And to all you toilers, first you flash 10.2.4 bootloader, and then boot up and install the Alien Box (Tweezermod), and then you get second bootloader. Instructions to thank Hashcode or FMkilo (or whichever the guy is).
crt2389 said:
Can you post on how you got it unbricked from the screen you were talking about. I have the same problem but can't seem to fix it. Thanks if you could do that.
Click to expand...
Click to collapse
Hey, sorry for the late reply...
Well first install the KFFirstAide ( the program with 40+ options ). You can find it easy here.
Now, you need to have factory cable. Turn off your Kindle, plug the factory cable and turn the Kindle On. You should see your Kindle in Fastboot status now, showing green and red light circles.
Next, start the KFFirstAide and run option 1 or 2, and when you get to the question "would you like us to switch your Kindle into Fastboot status" you should answer NO, because you already are into fastboot.
Then, just let the program do it's magic and you'll have your Kindle in it's original version of Android ( the Amazon version).
I hope this helps, let me know what you did
Cheers!
Waiting for device
idam_cuco said:
Hey, sorry for the late reply...
Well first install the KFFirstAide ( the program with 40+ options ). You can find it easy here.
Now, you need to have factory cable. Turn off your Kindle, plug the factory cable and turn the Kindle On. You should see your Kindle in Fastboot status now, showing green and red light circles.
Next, start the KFFirstAide and run option 1 or 2, and when you get to the question "would you like us to switch your Kindle into Fastboot status" you should answer NO, because you already are into fastboot.
Then, just let the program do it's magic and you'll have your Kindle in it's original version of Android ( the Amazon version).
I hope this helps, let me know what you did
Cheers!
Click to expand...
Click to collapse
I did exactly what you said and was stuck at <waiting for device> ???????
rohanlad8 said:
I did exactly what you said and was stuck at <waiting for device> ???????
Click to expand...
Click to collapse
It's a pain in the ass sometimes...
When you connect it with the factory cable, does it show the Fastboot on the screen? If yes, make sure you answer the questions correctly from the KF First Aide program, for example if it asks you do you have the Kindle Fire 2 gen?
But if it cannot recognize the device at all and it shows "waiting for device" for the whole time, I really don't know what can you do, except disconnect and connect again...
Maybe you could send me photos of how it looks the screen after every step you make including the questions when you run the KF First Aide?
You can send it to my mail: [email protected] | no tricks, just wanna try to help |
I had that problem and I know how awful it is
Good luck!
I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.