Develop Bugs

[Q] Boot stuck at Pink Unicorn (Team Kang) Help!

OK...I'm a first time poster to the Kindle Fire forum and I'm having issues. I'm a little above average with my Android knowledge. I've flashed CM9 onto three Toucpads and have been fooling with my phones for a few years. HOWEVER, I'm completely stumped. Here's what's happening and what I've done.
1) I downloaded Kindle Fire Utility to root. It all went fine, as far as I could tell.
2) I downloaded the aokp_otter_build-M5>0xD34D build for CM9
3) I downloaded the gapps-ics-20120429-signed zip
4) Booted into the TWRP recovery
5) Made a backup of the stock Kindle
6) Flashed the CM9 zip and the Gapps zip. Everything seemed fine with the TWRP. Never used it before. Very familiar with CWM and seemed similar
7 Rebooted.
The Kindle Fire logo came up and then went to a blank screen. It boot-looped (is that a verb?) five or six times. While I went surfing to find answers it looped once more and came up to this screen with a pissed off looking unicorn and the Team Kang logo. It's stuck there and won't go past. The screen is still animated. The battery is not dead. I've read dozens of posts where the first suggestion is to charge the Kindle. That's not the problem. I've restarted the Kindle a hundred times and nothing.
Here's what I've tried:
1) Every combination of holding down the power button/pressing the power button combination. Nothing.
2) Downloaded the Kindle Unbrick Utility. The computer isn't recognizing the Kindle, so this isn't doing any good. I've tried all of the six different UI buttons. Nothing.
3) I went back to the Kindle Fire Utility and reinstalled the drivers and then opened the CMD window. As I expected, it's telling me "waiting for device" and doing nothing.
I have no idea where to go from here. There's got to be a way for me to get this thing to be recognized on my computer. Please help. Any advice would be greatly appreciated. Thanks! -Jeff

It's like deja vu...
http://forum.xda-developers.com/showthread.php?t=1658205
Even the description of the bootanimation is eerily the same.
I think my assessment of his problem would apply to you as well. If you want to skip most of the discussion, my post is at (or very near) the end.

Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?

jeffjoleen said:
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999
Probably wouldn't hurt for you to look this over either...
http://forum.xda-developers.com/showthread.php?t=1552547

I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.

You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?

Thepooch said:
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
Click to expand...
Click to collapse
Honestly...don't remember if I did a full wipe of dalvik. I assumed I would have, but really don't remember. No...I don't get the yellow triangle and my kindle fire logo color is white "kindle" with a yellow "fire". I used the kindle fire utility and I think that installs the twrp by default. I don't have CWM installed. Wish I did. I'm comfortable with it. I just can't get to any kind of a recovery screen.

soupmagnet said:
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Click to expand...
Click to collapse
Yes...the KFU went fine, I think. I was able to access twrp and created my backup before I flashed the ICS. The Kindle logo has the white "kindle" and yellow "fire". Pauses for a few seconds or two...screen goes black...then that damned pink unicorn shows up and stays there. The unicorn screen is animated. I can power it down from there and start over without any problem. Any ideas?

without a bootloader you wont have access to recovery regardless of twrp/cwm

One other thing that I'm not sure matters, but when I do power it off and back on, I head the little "bong" on my computer telling me that a new device has been plugged in. I go to the device manager and under the "Other" category it shows "Amazon" with the yellow triangle the black exclamation point symbol.

Reinstall your drivers

Thepooch said:
without a bootloader you wont have access to recovery regardless of twrp/cwm
Click to expand...
Click to collapse
I guess that's where I am a little confused with definitions. I understand about the twrp and cmw recovery set ups. What exactly is a bootloader? Thanks for not laughing...

Thepooch said:
Reinstall your drivers
Click to expand...
Click to collapse
Through the Kindle Fire Utility? If so, I've done that several times. Would trying a different computer and installing them there make any difference?

the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device

First, read this...
http://forum.xda-developers.com/showpost.php?p=23747567
You need to make sure your drivers are in order so you can change the bootmode to 5001 and reboot. A custom bootloader will let you do this easily but considering you don't have one you need to use adb instead.
Code:
adb shell
idme bootmode 5001
adb reboot

Thepooch said:
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
Click to expand...
Click to collapse
So, without a functioning bootloader I won't even be able to get to the twrp to access my back up I made. Nice. Just bought this damn thing yesterday. I'm kinda missing the one-click jailbreak software from my old iphone a few years back!

if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547

Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
I just read through the basic instructions. I'll grab a usb thumbdrive and give it a shot. Thx

good luck hope you get through this is the not so fun side of rooting

Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks. It answered some of my questions. I guess it helped me relax a little, too. I know this is a problem that can be fixed. Just need to dig in an try each suggestion until I find one that works.

[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?

Bricked Kindle Fire (Stuck at Splash Screen)

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:

[Q] Kindle screen very weird

Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.

Kooky_Lukey said:
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Click to expand...
Click to collapse
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.

Thepooch said:
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Click to expand...
Click to collapse
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks

Kooky_Lukey said:
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Click to expand...
Click to collapse
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?

Thepooch said:
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Click to expand...
Click to collapse
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.

Kooky_Lukey said:
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Click to expand...
Click to collapse
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.

Thepooch said:
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Click to expand...
Click to collapse
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.

Kooky_Lukey said:
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Click to expand...
Click to collapse
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.

Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thepooch said:
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Click to expand...
Click to collapse
Thank you so much you do not know how much I appreciate it. If anything youre writing has anything to do with java i would love to help but if not then i wouldnt be of much help

stunts513 said:
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I wouldn`t even bother opening it let Amazon do their job. Case openers, case damage it would be pretty hard to pin the issue on them if you were to open the device.
Actually because of the present condition of the device I would go this route http://forum.xda-developers.com/showthread.php?t=2096888 . Just pick the latest version of the 8.9 to restore to you should also be prompted with an option to wipe cache and data please do so. All the partitions will be restored to stock and the device will be ready for return. Say nothing about modifying the device just leave those details out. If you want help catch me online and we will set something up. Some of this does depend on the state of your warranty. Be courteous with customer service and brief as to what caused the issue you simply just found it that way Good luck.

Good point, wasn't really thinking about "what if the problem wasn't that".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Help! - stuck in "kindlefire" boot screen

Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!

notiboy07 said:
Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!
Click to expand...
Click to collapse
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike

11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.

notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<

!
11fan said:
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<
Click to expand...
Click to collapse
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!

notiboy07 said:
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!
Click to expand...
Click to collapse
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike

11fan said:
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike
Click to expand...
Click to collapse
Thanks again @Mike. However, i wasn't able to do my factory backup images. and secondly, what did you use to restore the images? Did you use KKFA or the KFHD SRT? i'm sorry, i kinda scared now to proceed on my own.

From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!

notiboy07 said:
From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!
Click to expand...
Click to collapse
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???

11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Thank you for the prompt reply. So now i know those wouldn't work. Yes, fastboot is working - it says fastboot on the screen of the kindle fire 8.9. Ok, so i need to get that recovery image - however, i think you were not able to link that thread. I'm sorry, can you please paste the link again?
I'm on google hangouts now. [email protected]
Thanks a lot @Mike!

I have been reading XDA for years, My KFHD 8.9 recently stopped booting also
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)

Umisguy said:
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)
Click to expand...
Click to collapse
I dont think this is the same case @Umisguy as you have not tinkered with your tablet (100% stock), while mine happened while trying to install a custom ROM. Maybe the amazon guys can help you?

Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files
11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Folks,
I got in to the same trouble able to mess up the KF and get a redscreen but used KFHD SRT to reflash the 8.1.4 system image, boot image, recovery image but now I ended up in the boot loop mode where it shows reboot kindle or Reset to factory Dafaults but as I flashed every thing am unable to reset to factory. As I got the tablet recently it came with 8.5.1 so I need to try with the latest image I can get.
If there are any suggestions i can try please let me know.

Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike

11fan said:
Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike
Click to expand...
Click to collapse
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.

I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk

11fan said:
I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
That will be great Mike.
Thanks,
Krishna

krishnasanga said:
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk

krishnasanga said:
That will be great Mike.
Thanks,
Krishna
Click to expand...
Click to collapse
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike

11fan said:
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike
Click to expand...
Click to collapse
Mike,
I tried with this new boot and recovery images but still stuck in the loop , can you upload your backup files of 8.5.1 system.img,boot.img,recovery.img I think that will be my last shot to try to unbrick this device.
Thanks,
Krishna