Bricked Kindle Fire (Stuck at Splash Screen) - Kindle Fire Q&A, Help & Troubleshooting

Today I tried loading 4.1 Jellybean on my fire, but it wasn't opening applications properly and being annoying so I unloaded it. I used KFU to root it, and had TWRP recovery on it. I then figured I'd revert it back to the default OS, so I grabbed a copy of the kindle fire 6.2.1 software from Amazon's page and renamed it to update.zip (it converted to a .zip with identical contents to the one directly from KFU).When I had TWRP, KFU recognized my device as online, but didn't have a version, so there was no help there. I wiped the entire thing using the recovery tool and then I hit "Install --> Update.zip". Everything seemed fine after this worked, so I rebooted the device. I thought it worked, but now it's stuck at the Kindle Fire default splash screen. When I plug iit into my computer, Windows doesn't recognize it, nor does KFU. I haven't tried letting the battery drain (since that would take awhile), but it seems like it's bricked. Please help!
EDIT: My main problem right now is that it can't even be recognized at windows. I feel like it's stuck in the wrong fastboot mode right now, but I can't even get windows to recognize it. Also, it's not running Fire fire fire, the splash screen shows the basic unanimated Kindle Fire logo. It's likely stuck on fastboot 4002 instead of 4000. I'm currently letting the battery drain so I can plug it in and see if windows will recognize it. My guess is that I can get it to work as long as windows will recognize it.

I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!

soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!
Click to expand...
Click to collapse
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?

shnish said:
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
Click to expand...
Click to collapse
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.

soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
I know that you know more about this than me, but I feel like if it's stuck on the wrong fastboot type, preventing the battery from draining would be a bad idea (or at least slow down the "fixing" processor). Sorry, but why does that seem so wrong?

Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963

soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.

soupmagnet said:
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!

shnish said:
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
Click to expand...
Click to collapse
umm...
soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
Click to expand...
Click to collapse

soupmagnet said:
umm...
Click to expand...
Click to collapse
Alright. Looks like I might need a factory cable?

shnish said:
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
Click to expand...
Click to collapse
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.

kinfauns said:
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
Click to expand...
Click to collapse
The device ended up losing power, but it still powers on properly when I plug it in (stuck on the kindle fire logo, of course).
I suppose it's not in fastboot mode, it's just stuck on the stock loader. I'm not quite positive, but it seems like I'll need a factory cable to get this thing working again. I really don't want to have to blow any money on this, if I can revert it back to stock settings easily, I'll never mess with it again. Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?

shnish said:
Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605

soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
So if I install Ubuntu, I should be good to go? Ubuntu will recognize the kindle fire?

Read the post I gave you.

soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
Yes. He has the exact same problem as me! I did the same thing as him, and I'm really hoping I'll be able to solve this issue. All I want is the stock kindle back so I can stop worrying. I've read through tons of these posts (I have 13 xda posts open in my browser), but none of them seem too helpful as to how I can get my computer to recognize the Kindle. My guess is that Ubuntu won't recognize the Kindle either, though. In that case, would a factory cable solve all my problems? I stupidly removed root access by simply updating my kindle fire without thinking of the problems that could have come with that. I figured it would just remove root access and start booting up normally. I was very wrong.

soupmagnet said:
Read the post I gave you.
Click to expand...
Click to collapse
I'm going to try it in Ubuntu, but assuming that doesn't work, I'll need to get a factory cable. What do I do to revert to stock settings once I have a factory cable?

I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.

soupmagnet said:
I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
Click to expand...
Click to collapse
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?

shnish said:
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
Click to expand...
Click to collapse
:good:

Related

[Q] Another Bricked Kindle

To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Could you post what you did or tried to do that bricked it?
99 times out of 100 rebooting will fix the "waiting for device" problem, especially if the PC drivers are installed appropriately, but I'm guessing you already tried that. I'd do it a few times, why not?
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
soupmagnet said:
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
Click to expand...
Click to collapse
Win7 64bit Ultimate
Stock
It's a clean kindle with nothing on it that got bricked while I was rooting it, some how.
My experience is really only a 1 time root when i first bought it back in January.
Very familiar with my OS.
Average with command line interface
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
nchevaux said:
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
Click to expand...
Click to collapse
it stays on the kindle fire logo until i hard reset it.
I was using KFU when this happened.
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
soupmagnet said:
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
Click to expand...
Click to collapse
how am I supposed to put it on the kindle... Did you not read my other posts?
It won't let me do ANYTHING to it.
Did you install the drivers from kfu with your kindle plugged in?
needhelpplease3 said:
how am I supposed to put it on the kindle... Did you not read my other posts?
Click to expand...
Click to collapse
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
needhelpplease3 said:
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
Click to expand...
Click to collapse
Don't make a long story short. The more information you can provide, the better.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Click to expand...
Click to collapse
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
soupmagnet said:
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
Don't make a long story short. The more information you can provide, the better.
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
Click to expand...
Click to collapse
Sorry, I've just been really agitated by this whole situation. I've asked another forum and got back with horrible answers.
To start all over again, this is what happened.
I had my kindle fire at 6.3, unrooted (only unrooted because of the update), and decided to why not root it again, just so it's updated.
I got all the necessities to root the kindle, the same things I used when I first got it, and started up the process.
At first, the drivers were giving me issues, but that got settled quite quickly.
Then when I started up KFU, I did the perm root, but it somehow got canceled in the middle of it, so I'm guessing that's what has screwed it up.
Now when I plug it into either my Wall or USB adapters, it doesn't work.
I've tried that hard reset way, where you hold down the power button for 30 seconds, and that didn't work either.
So I got fed up, and came here for answers.
Right now, it's basically a dead Kindle Fire.
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
soupmagnet said:
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
Click to expand...
Click to collapse
Great... I'll try it. I'll tell ya what happens. Thanks
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
needhelpplease3 said:
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
Click to expand...
Click to collapse
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
soupmagnet said:
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
Click to expand...
Click to collapse
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
needhelpplease3 said:
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
Click to expand...
Click to collapse
Stop! before you screw something up.
More to follow....
soupmagnet said:
Stop! before you screw something up.
More to follow....
Click to expand...
Click to collapse
You're confusing me.
More to follow?
When I asked you "What happens when you try to power the device on?", I'm looking for specifics, i.e. "When I press the power button, nothing happens and the screen doesn't come on at all", or "The screen comes on, but the boot logo flashes on and off", or "The screen comes on, but hangs steady at the boot logo".
It is very important that you make this clear from the very beginning because it will help us in not telling you do do the wrong thing and potentially causing serious harm to your device.
I'm getting conflicting symptoms from you and it is making helping you rather difficult. If your screen doesn't come on at all the only fix for that starts with the "shorting trick". When you say that your screen was turning on and off it makes me think that it was doing that all along, which would require a completely fix.
If I'm going to help you I need to know exactly what is going on with your device along with any changes it has made and when they happened.

[Q] Still having FACTORY CABLE brick problems-Video Included. Help!

Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
I remember the instructions for the skorpn factory cable says to plug it into your computer first and then your device. Make sure you hold the power button for 20 seconds to shut it down first.
I just read through more information. I don't think this factory cable is even getting me into fastboot mode. What's my screen supposed to look like if it is in fastboot? I can't find any info on what that looks like.
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Thepooch said:
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Click to expand...
Click to collapse
Is firekit the one where I need to crack open the back case? I really hope not...
jeffjoleen said:
Is firekit the one where I need to crack open the back case? I really hope not...
Click to expand...
Click to collapse
You're fine. I watched your video. The first time you plug it in, I think you hit the power button with your forefinger before you plugged it into your computer and the KF booted normally. When you turned it off, back on again, and then it got "stuck" on the "kindle fire" logo... that's what's supposed to happen with the factory cable. Your KF should now be in fastboot mode. Now you have to get your drivers working so that the computer sees the device properly and you'll be able to issue fastboot commands.
Look at this link...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
compare what you get in the device manager with the table in the middle of that post. You should be seeing "Android Phone -> Android Composite ADB Interface" in the list. Then it's a matter of opening up the Windows command prompt program and sending the KF some fastboot commands to have it boot into recovery. That's in one of the posts you already mentioned in the OP.
EDIT: My bad... that should be "Android Phone -> Android ADB Interface"... no "Composite" in there.
This is new...I now go to the Device Manager and it shows under the main "Martin-PC" I now have "Android Phone" with the "Android ADB Interface" nested underneath it. I don't think it's going into fastboot mode like the factory cable is supposed to do. What is it supposed to look like?
Unfortunately Jeff it is but I really wonder about your situation because your not getting to the fff bootloader but you may be getting to the stock one . So get it where your just looking at the kindle fire logo not the pissed of unicorn go to kfu shift+right click on the tools folder choose open command window here then type fastboot devices post the results here if any
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
I don't want to discourage you guys from trying to help people here who find themselves in trouble, but please try to understand the problem before offering guidance. How can you fix something without understanding the situation?
Hyperrunner said:
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
Click to expand...
Click to collapse
The system software on his device is broken and will not boot. Setting the bootmode to normal with KFU or otherwise doesn't fix anything. That would just put him right back into the situation he's trying to get out of in the first place. He doesn't want to get out of fastboot mode the way you're suggesting, he's trying to get into fastboot as the first step in flashing a new ROM.
xiaohewu said:
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
Click to expand...
Click to collapse
The OP and his followup posts show that he doesn't know if he's even in fastboot mode. Your question doesn't even make sense in this context.
Guys, this post isn't meant to chastise you for trying to help. Just don't throw out random things to people who are already flustered and confused as it is.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you fix your KF?

no os for kindle fire

Was trying to root kf . started "Install Permanent Boot, etc." all seamed to be going OK. Went as far as TWRP was installed. At that point the OS for the fire was GONE. Fire is hung at TWRP. No operating system for anything. Plz HELP
If TWRP is still functional, then you can just "mount USB," put a rom and gapps into the folder, flash them, then boom! You'll have an OS again; just basic protocol haha.
I would also wipe data/cache, dalvik, etc. just in case...
...But if you want stock Amazon Gingerbread then you're going to have to look way back in time in the forums for the stock rom.
What happens when you reboot system? Does it go right back to TWRP?
Me Too
I have no OS on my kindle fire. I wiped the memory and now I lost my roms and backups. I heard you can try ADB, but I couldn't get it to work. Mine just boots to the kindle fire logo but nothing else happens. It's basically collecting dust.
Take a breath, relax, and take comfort in the fact that there is nothing wrong with your Kindle. It is doing exactly what it was told to do. Your problem is easy to fix, but you need to know what's going on first.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it. Then read it again. And while you're at it, go ahead and read it a third time. Do this before anything else.
[Edit:] Oh yeah, and read this too.
http://forum.xda-developers.com/showthread.php?p=25730650
Ahh, what the hell, read this one as well.
http://forum.xda-developers.com/showthread.php?p=26435498
soupmagnet said:
What happens when you reboot system? Does it go right back to TWRP?
Click to expand...
Click to collapse
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
"
Click to expand...
Click to collapse
jerryhndy said:
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
Click to expand...
Click to collapse
Wow, very interesting, and welcome back.
Weird. It's almost as if you have TWRP installed to the system partition. Selecting "reset boot" on FFF1.4 changes the idme value to 4000, so your device should boot to the system partition no matter what. But you said the boot logo changes from blue to red. What's actually happening, is the bootloader finishes doing it's thing and then boots to the system. The red and white Kindle Fire logo you see then is the stock boot animation, which makes everything really strange. "Recovery" boot shouldn't show the boot animation at all. And if you have recovery installed to the system partition, you shouldn't see the boot animation there either. WTF did you do to your Kindle?
My best advice would be to get into fastboot and reinstall TWRP to the correct partition so you can reinstall your ROM. From the sounds of it, you will likely have no access to the adb shell, in which case you would need to get a factory cable.
So, boot into recovery and enter the following command to see if you even have a working shell:
Code:
adb shell idme bootmode 4002
no os
jerryhndy said:
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
Sorry, above is the correct info that I sent in. #2 is "recovery. Sorry for the confusion.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
soupmagnet said:
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
Click to expand...
Click to collapse
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
jerryhndy said:
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
Click to expand...
Click to collapse
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
soupmagnet said:
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
Click to expand...
Click to collapse
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
jerryhndy said:
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
Click to expand...
Click to collapse
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
soupmagnet said:
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
Click to expand...
Click to collapse
I found a keyboard in TWRP in the KF, however it would only let me type #'s. I think I am lost here. Do you accept KF's (sent to you), for
repair or what ever to get it to root ?? If so, I could sent it to you etc. [email protected]
Soupmagnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Thepooch said:
Soup magnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Click to expand...
Click to collapse
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
jerryhndy said:
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
Click to expand...
Click to collapse
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Thepooch said:
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Click to expand...
Click to collapse
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
to
jerryhndy said:
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
Click to expand...
Click to collapse
I sent you a pm Jerry. I would not charge you. Lets take a look and see if we can`t fix it without you even having to ship it.

Bricked Fire but need help bad!!

Well I have a bricked 1st gen Kindle Fire. It is stuck on the orange and white kindle fire screen and I have a factory cable. The screen just stays on the orange and white for forever unless I hold the power button down for almost 15 seconds. I need help getting it back to normal Kindle then rooting and such. Please help me somebody!!!!!!
http://forum.xda-developers.com/showthread.php?t=2166668
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
Click to expand...
Click to collapse
Simply plugging it in doesn't do nothing.
Simply plugging it in puts it into fastboot (static Kindle Fire logo) like it's supposed to. In fastboot you use fastboot commands to get the device in a usable state. If fastboot commands don't work, then it is a problem with your drivers.
All of this information and then some can be found at the link I gave you, so you should probably study it more carefully. Identifying and using fastboot mode on the Kindle Fire is such a basic task, you should be able to learn everything you need to know about it on your own, using the information that's available to you.
soupmagnet said:
Simply plugging it in puts it into fastboot (static Kindle Fire logo) like it's supposed to. In fastboot you use fastboot commands to get the device in a usable state. If fastboot commands don't work, then it is a problem with your drivers.
All of this information and then some can be found at the link I gave you, so you should probably study it more carefully. Identifying and using fastboot mode on the Kindle Fire is such a basic task, you should be able to learn everything you need to know about it on your own, using the information that's available to you.
Click to expand...
Click to collapse
Can you please just help me? I've been googling for days and I'm confused like there's no tomorrow. All I know is my Kindle has been stuck on the stock orange and white screen and I have a factory cable.
The information you need has already been laid out for you, and the FAQ that I linked to was written in such a way to make finding the information you're looking for that much easier.
Q2 Links to information every Kindle Fire owner needs to know if they plan to modifying their device (it even includes an explanation on "unbricking").
Q16 Explains what it means when your device is stuck at the Kindle Fire logo and clues for getting your device fixed.
Q17 Explains a simple way to fix 90% of all Kindle Fire problems.
Q18 Links to a list of fastboot commands and a short explanation for each
Q19 Is a guide regarding fastboot, which explains how to identify and/or access fastboot mode
Q26 & Q27 Has information regarding the factory cable and how it is used.
...and various other questions have answers which clue you in to what you need to do to fix your device.
If you had a complicated problem or a question, to which the answer was hard to find, I could justify spending the time to help you figure it out. But your problem is one that has happened probably thousands of times around here. It is basic knowledge, prerequisite to modifying the Kindle Fire, and you should have already known it anyway.
Don't forget that you created this problem for yourself (not me). Therefore it is your responsibility (not mine) to fix it.
I've already gone out of the way to make that process easier by providing the FAQ in the first place, so you should (at the very least) use that information to figure out why your device is behaving the way it is, and what you need to do to fix it.
It isn't that hard. You just have to put forth the effort.
soupmagnet said:
The information you need has already been laid out for you, and the FAQ that I linked to was written in such a way to make finding the information you're looking for that much easier.
Q2 Links to information every Kindle Fire owner needs to know if they plan to modifying their device (it even includes an explanation on "unbricking").
Q16 Explains what it means when your device is stuck at the Kindle Fire logo and clues for getting your device fixed.
Q17 Explains a simple way to fix 90% of all Kindle Fire problems.
Q18 Links to a list of fastboot commands and a short explanation for each
Q19 Is a guide regarding fastboot, which explains how to identify and/or access fastboot mode
Q26 & Q27 Has information regarding the factory cable and how it is used.
...and various other questions have answers which clue you in to what you need to do to fix your device.
If you had a complicated problem or a question, to which the answer was hard to find, I could justify spending the time to help you figure it out. But your problem is one that has happened probably thousands of times around here. It is basic knowledge, prerequisite to modifying the Kindle Fire, and you should have already known it anyway.
Don't not forget that you created this problem for yourself (not me). Therefore it is your responsibility (not mine) to fix it.
I've already gone out of the way to make that process easier by providing the FAQ in the first place, so you should (at the very least) use that information to figure out why your device is behaving the way it is, and what you need to do to fix it.
It isn't that hard. You just have to put forth the effort.
Click to expand...
Click to collapse
I understand, I'm very knowledgable with my Razr, so I figured I'd be able to do this easy peezy lemon squeezy. Guess not. I just keep trying things and nothing is working or else I'm just not doing it right :/
soupmagnet said:
The information you need has already been laid out for you, and the FAQ that I linked to was written in such a way to make finding the information you're looking for that much easier.
Q2 Links to information every Kindle Fire owner needs to know if they plan to modifying their device (it even includes an explanation on "unbricking").
Q16 Explains what it means when your device is stuck at the Kindle Fire logo and clues for getting your device fixed.
Q17 Explains a simple way to fix 90% of all Kindle Fire problems.
Q18 Links to a list of fastboot commands and a short explanation for each
Q19 Is a guide regarding fastboot, which explains how to identify and/or access fastboot mode
Q26 & Q27 Has information regarding the factory cable and how it is used.
...and various other questions have answers which clue you in to what you need to do to fix your device.
If you had a complicated problem or a question, to which the answer was hard to find, I could justify spending the time to help you figure it out. But your problem is one that has happened probably thousands of times around here. It is basic knowledge, prerequisite to modifying the Kindle Fire, and you should have already known it anyway.
Don't forget that you created this problem for yourself (not me). Therefore it is your responsibility (not mine) to fix it.
I've already gone out of the way to make that process easier by providing the FAQ in the first place, so you should (at the very least) use that information to figure out why your device is behaving the way it is, and what you need to do to fix it.
It isn't that hard. You just have to put forth the effort.
Click to expand...
Click to collapse
I know this has been answered but I've tried 10 million different ways on how to get the right working drivers. Can you supply me with something that is easy? I've tried installing the SDK manager, tried deleting the ADB, replugging in, and nothing still works and it still shows up as unknown device......
What commands are you using?
soupmagnet said:
What commands are you using?
Click to expand...
Click to collapse
How do I do those?
soupmagnet said:
What commands are you using?
Click to expand...
Click to collapse
I thought I had to have the right drivers for those?

Anyone know how to fix a bricked FTV

Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
hi,
I am not an expert on this matter but you should provide detail info exactly what you did to your Fire TV, the exact steps and sequence so folks can help you better.
In the meantime, check these all link out before you do anything. It seems few folks has some success see link 2 and 3 as always try it on your risk. I hope someone else can provide a better solution.
http://www.aftvnews.com/top-ways-to-brick-your-fire-tv/
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
http://forum.xda-developers.com/showthread.php?t=2799779
http://www.aftvnews.com/factory-reset-on-amazon-fire-tv-and-fire-tv-stick-explained/
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
KLit75 said:
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Click to expand...
Click to collapse
Thanks for the reply Klite, I didn't unlock the bootloader before installing the menu so that must have caused the brick.
I'm only able to see the Amazon logo, it does not reach the Fire TV Logo. I have plugged in a USB keyboard but i can't seem to get to recovery.
ashsha7877 said:
hi,
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
Click to expand...
Click to collapse
Hi Ashsha
I do mainly use my FTV for Kodi, I did previously use a Raspberry Pi but i bought this to replace it as i wanted something more powerful due to the problems i was having with stutters during play back.
Thanks for the links too, i did try them but i have had no luck so far.
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
Phill360 said:
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Click to expand...
Click to collapse
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
KLit75 said:
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
Click to expand...
Click to collapse
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
rbox said:
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
Click to expand...
Click to collapse
Thanks for the reply rbox.
So what your saying is my Fire TV is dead.
I might just move on then to a new device like the Razor Forge TV when that comes out.
daffung said:
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
Click to expand...
Click to collapse
I'd love to return my FTV under warranty but i live in Australia and can't be bothered paying for postage to get it replaced
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Phill360 said:
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Click to expand...
Click to collapse
Depending on how much of the instructions you actually followed, and if your bootloader is 51.1.0.2 or older, there is a method that @AFTVnews.com is working on a writeup for that should recover it. But if the bootloader wasn't downgraded to 51.1.0.2, then it's dead.

Categories

Resources