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?
Related
Hey!
Lately I kept on playing with my kindle until the battery reached 0.
So I charged it but its stuck at the yellow Triangle and it turns off after a second or two.
Your problem is invaluable to the continued efforts of the developers.
Hey Im looking for a proper answer.
JoshuaLintag said:
Hey Im looking for a proper answer.
Click to expand...
Click to collapse
Maybe youll find a proper answer....in the proper forum...aka not the DEVELOPMENT forum ;D
Reported so it could be moved to the proper thread so you wont get flamed q&a
Sent from my Kindle Fire using Tapatalk 2
Help!
Anyone?
Adb does not detect it.
Sadly I am in the same boat! I am not getting anything to work.
http://forum.xda-developers.com/showthread.php?p=25400963
http://forum.xda-developers.com/showthread.php?p=25598837
THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps
JoshuaLintag said:
THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps
Click to expand...
Click to collapse
Did you happen to READ THE LINKS GIVEN TO YOU?
not sorry for caps
Your battery is near dead. You probably won't get anything to connect at this point without a factory cable. Which you would have known by READING THE LINKS GIVEN TO YOU.
I couldn't even charge mine
Okay, (even though I know this has been covered in the link I gave you) I'll be nice considering the possibility of a language barrier.
You need to get a factory programming cable (which I've said) so you can get into fastboot. Read about the factory cable and it's purpose here:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
...and here:
http://forum.xda-developers.com/showthread.php?p=20317299
Then learn how to fix your drivers in case that's also contributing to the problem:
http://forum.xda-developers.com/showthread.php?p=23747671
Pay attention. The fix for this requires installing a new bootloader which (if you aren't careful) can PERMANENTLY brick your device.
Thanks for the links, btw.
I'm 13 and I don't know about making a factory cable, the steps on the links
is quite complicated. And Maybe risky.
Your only option then, would be to get a fastboot connection to flash the new FFF 1.4
This you may need to do several times to get it to work, if it works at all.
Make sure you know how to use fastboot
With the Kindle turned off, enter the following command:
Code:
fastboot flash bootloader /path/to/FFF1.4.bin
When you see "waiting for device" turn your kindle on.
If the installation takes place, all you need to do at that point is plug it into the wall charger.
If after several tries it still doesn't work you may want to try fixing your fastboot drivers. http://forum.xda-developers.com/showthread.php?p=23747671
Otherwise, a factory cable is your only option.
oh crap.
I think it's really dead.
It doesn't work, my computer won't detect it and it won't even show up
on device manager when I turn it on.
sorry man
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".
i had rooted my kindle with firefirefire by KFU and had accidentally erased the SDCARD, so i found a new gingerbread kindle fire OS.zip online no problem and installed it, had it up and working again, all fine and dandy.
Then everytime i booted it up it would always come up with the whole blue "kindle fire" and "press power button for boot options" screen and i decided i didnt want twrp on my kindle anymore and that i wanted to return it back to factory condition. so i looked up on youtube how to de-root you kindle fire and i referenced myself with this video:
http://www.youtube.com/watch?v=AzbmxV45x10
i downloaded the update.zip and flashed my kindle with twrp (just like it said) and everything went fine. however the next time i turned it on (well when it turned itself on after the update) it just got stuck in a boot loop... it will display the factory setting "kindle fire" with the red color, not twrp's blue "kindle fire", then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo) then it will shut off. after about 5-10 seconds of being off, it will boot itself back on and repeat the same cycle again.
i have tried to hook it up to the computer, but it only shows up in "My Computer" for about a millisecond. thought maybe it was just my computer that couldnt load fast, so i tried a different computer, same thing.
i have tried holding the power button down for anywhere between 20- 60 seconds, still nothing.
i have tried opening the KFU and going to install firefirefire and letting it load to the point of <waiting for device> and then plugging in my device, still nothing.
i am extremely grateful of any ideas and solutions you guys/girls can offer and help me out. i loved my kindle fire quite dearly and used it everyday. i am willing to accept the fact that i have a $200 brick, but will do just about anything to fix. please help http://forum.xda-developers.com/images/smilies/frown.gif
Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.
James.Whaton said:
it will display the factory setting "kindle fire" with the red color...then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo).
Click to expand...
Click to collapse
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.
soupmagnet said:
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.
Click to expand...
Click to collapse
i do have a rocketfish cable that is a step up from the factory cable, always worked in the past whenever i used it for the kindle, i can get it to charge, just not stay connected to my computer... i dont quite know why this happened because all i did was install that update... not quite sure why it did this... any ideas on how to get it back to normal?
Thepooch said:
Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.
Click to expand...
Click to collapse
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?
James.Whaton said:
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?
Click to expand...
Click to collapse
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864
soupmagnet said:
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864
Click to expand...
Click to collapse
my computer will detect the device but only for a second, because it never fully loads it is only in the booting mode.my computer cant see it due to the kindle not being available. where would i purchase a foctory cable becuse by the way you guys are talking about it it sounds like the cable isnt just a cable but it can make it boot differently... the cable i have now connects it to the computer very easily and just fine, and the only reason that it isnt working now is because the kindle is in a boot loop.
http://forum.xda-developers.com/showthread.php?t=1392693 post 9 James the factory cable will force the device into fastboot so you can use kfu to resend fff and twrp to the device in order to do a full wipe and flash a new system.
forgive me for being curious, but how exactly does this factory cable work? i know that it isnt you who is making them, but i would hope that if you are suggesting to use it you would understand how it works... i have my cable here so why go buy a new one instead of just doing it myself? it seems like it is just a simple soldering job, which i could handle. after a little research it looks like i need to connect pin 1 to pin 4 which wouldnt be all that difficult to do by myself.
could anyone tell me how i could simply create on myself. yes ive read this post:
http://forum.xda-developers.com/showthread.php?t=1392693
but they never quite explain in detail what i need to do to make one. i watched a couple videos on youtube to figurre out what i had to do, but i still would like a more professional opinion as to what i need to do and as to how it works. thank you
lost OS
i have done every thing to the T to get OS back. when i down load the new OS and place it in the kindle updates folder it does not show up in TWRP when I unmount the KF.
suggestions> I have been beating my head on this since some screwball decided to pay with it.
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me. (I just installed stock Ubuntu to a flash drive with the fk file on root, I'm fairly certain that's all that needed to be done?)
Anyways, my Kindle is unresponsove, and the usbboot trick has yet to work for me. I really want to save this guy. I've heard the KF cannot be completely bricked through software/flashing. I hope it's true! Any help would be greatly appreciated. Thank you.
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
chris_m128 said:
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
Click to expand...
Click to collapse
Thanks fro replying. I'm pretty sure a factory cable only puts it into fastboot if you have a working bootloader. I don't, so I don't think it would work.
I remember an instance where a friend of mine had a broken bootloader, and we used a factory cable to restore it, this was on the kindle fire. we had to first reflash the bootloader. I hope this is possible here.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
but you'll have to ask someone with more experience than me sorry.
jophish said:
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me.
Click to expand...
Click to collapse
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
Click to expand...
Click to collapse
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
jophish said:
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
Click to expand...
Click to collapse
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
jophish said:
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
Click to expand...
Click to collapse
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
plinders said:
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
Click to expand...
Click to collapse
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Same Here..
I was thinking that all kindle fire are the same... installed fire fire fire using KFU and device got bricked....!
Hope someone here could help us get our devices up and running again...
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
jophish said:
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
Click to expand...
Click to collapse
I am sure they can figure it out. Can you boot into TWRP?
If so, you can still recover...
Dame problem
plinders said:
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
Click to expand...
Click to collapse
Same problem dude, did you fix it?
i.robert said:
Same problem dude, did you fix it?
Click to expand...
Click to collapse
Not yet I'm afraid. Everything I tried so far hasn't worked.
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
No, Absolutely nothing. I really would like to get this working.
jophish said:
No, Absolutely nothing. I really would like to get this working.
Click to expand...
Click to collapse
same here we need a new firekit for the kf2
Help..
any updates on the fix? I hope someone out there could help us revive our bricked kindle fire 2... :angel:
kindle fire 2
flashed wrong bootloader (fff)
no power
no lights
no adb
shorting trick is not working for me :crying:
The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks
nobleman221 said:
The only thing I can do is get the device status to go online. It's recognizable on my computer devices. But I can't open it. Only right click. Iv tried fast boot. Iv tried installing twrp manually. But I always get stuck at waiting for device. When the Kindle reboots reconnects and disconnects and then reconnects. But all I see is the kindle fire logo. It can sit there for hours like that. Iv tried Soupkit. But that didn't work because it said the device was offline even it actually wasn't. Iv tried everything unless someone has an idea. It has no OS to boot to. So thats the reason. It must be. I void the warranty obviously by rooting. But I'm not here for admitting I did a stupid move of actually rooting when you dont know what your doing. If someone can leave a suggestion. I'd appreciate the suggestion. thanks
Click to expand...
Click to collapse
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?
soupmagnet said:
Does your Kindle Fire logo stay brightly lit or at any point does it flash and/or go dim?
Click to expand...
Click to collapse
brightly lit
nobleman221 said:
brightly lit
Click to expand...
Click to collapse
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?
soupmagnet said:
Okay, are you using a Linux VM, LiveUSB or full normal Linux install on your PC?
Click to expand...
Click to collapse
full normal linux, Ubuntu 12.10`
nobleman221 said:
full normal linux, Ubuntu 12.10`
Click to expand...
Click to collapse
Are you using a USB 3.0 port?
soupmagnet said:
Are you using a USB 3.0 port?
Click to expand...
Click to collapse
Noob question how do you tell
nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
nobleman221 said:
Noob question how do you tell
Click to expand...
Click to collapse
If you have to ask then 99% likely you don't have one.
If you bought your computer in the last 6 months then maybe.
soupmagnet said:
How old is your computer?
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse
Acer Aspire 5742. 3 years old.
nobleman221 said:
Acer Aspire 5742. 3 years old.
Click to expand...
Click to collapse
Nope. No way to possibly have a USB 3 port on that.
TheNetwork said:
Nope. No way to possibly have a USB 3 port on that.
Click to expand...
Click to collapse
So Is my kindle gone for good?
nobleman221 said:
So Is my kindle gone for good?
Click to expand...
Click to collapse
No. Did you follow the instructions I gave you previously?
soupmagnet said:
In the SoupKit Utility, choose the option to install FireFireFire, whether it says online or not, and follow the instructions to see if that get's you anywhere.
Click to expand...
Click to collapse
Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.
nobleman221 said:
Ok, Im able to get the ADB device status to online in Soupkit. But where do I a start from exactly. do i got to bootmenu or what.
Click to expand...
Click to collapse
Install menu > install TWRP...or COTR...your choice.
Sent from my Amazon Kindle Fire using Tapatalk 2
The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Sent from my EVO using xda app-developers app
nobleman221 said:
The kindle status is online. Should the kindle be off or not. Also when I run twrp install on the terminal. Its running nothing but words. How long does this take. Also do I need WiFi while doing this.
Click to expand...
Click to collapse
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.
soupmagnet said:
"It's running nothing but words." Hmm...interesting.
You have to understand that I cannot see your device and I definitely can't see these "words" you're talking about. I have no idea what you've done and you still haven't told me whether you understood the instructions I gave you to install FFF or whether or not you succeeded in doing so. So unless you are able to provide me some usable information, we're just going to go around in circles here.
Aside from that, ADB is not going to do you any good until you get TWRP installed. You won't get TWRP installed until you follow the instructions I gave you to get FireFireFire installed. In case you missed it...for the second time...I'll try to explain it a little better.
If you had read the SoupKit thread, you would find that the stock bootloader doesn't work like it should in regards to accepting fastboot commands. The command "fastboot devices" doesn't work, so the SoupKit, will always say "Device Offline". Other fastboot commands will work, but you have to enter the command, turn the device off (hold power button for 10 seconds), then turn it back on. I also explained in the SoupKit thread (and here...twice), that if you have the stock bootloader installed and you get "Device Offline", to choose an option anyway and follow the instructions it gives you (which will be to turn the device off, then back on, etc).
Now, considering you have not given me any information regarding the success or failure of those instructions, I'll have to assume you either didn't read or you didn't understand them. That being said, let's go back and try it again.
Click to expand...
Click to collapse
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.
nobleman221 said:
i did read the instructions. But the terminal runs a bunch of commands rapidly so fast I cant read it. I have my WiFi turned on and when I enter the command to install TWRP the terminal window just runs and that's the end of it, it runs in an endless loop jumbled words. My Kindle fire connects making 3 connect/disconnect sounds when plugged in my computer. And Still is stuck at the boot logo with no signs of change.
Click to expand...
Click to collapse
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.
soupmagnet said:
You can scroll up through the terminal to get the outputs of the previous commands. Regardless, if you ran the option to install FireFireFire, it would sit at "waiting for device" until you shut the device down and turn it back on.
Click to expand...
Click to collapse
"Your shell is either missing or corrupt shell making it impossible to change from the inside of the system your \nshell must be installed properly before you can proceed any further, the only way to do this is firefirefire." Is what was being spammed in the terminal. I couldent copy and paste the the thing because everytime I clicked inside the terminal the instructions dissappeared.