Develop Bugs

[Question] Kindle Fire is possibly dead.

Guys,
Details: Using Windows 7 64 bits, on a notebook.
Here is the full history of my brand new brick... call me stupid.
Second day with my Kindle Fire, I tryed to root my kindle fire.
Downloaded the KFU 0.9.5, instaled the drivers.
But the KFU wasn't workig... I only was getting the ADB offline status and the "waiting for device" message.
When I realized that the drivers I had were from my Motorola Milestone.
Next step: Uninstall the wrong drivers, and reinstall the new ones.
Only with this i could get the device to work with KFU.
Open the Run application at KFU folder.
Choosed option 2: Install Permanent Root with Superuser.
All worked fine until i get the message "with great powers come great responsabilityies" press any key to continue...
[EDIT: Tried to install Gapps extras... I don't remember if Kindle was dead before this or after]
The Kindle rebooted, got to the screen with the "kindle" word, and died.
Since that I'm getting no power on, no led lights, no response when connected to usb... nothing.
What should I do?
Go to Motorola Tech Support (here in my city) and try to use a factory cable?
or
I can only put my hopes on USB Boot Mode?
Guys, thanks in advance and sorry for my english, I certainly made some msitakes.
Or I can try Firekit?

That's strange, installing the wrong device drivers on your computer shouldn't affect your Kindle.
What it really sounds like is your battery died in the process of installing the FFF bootloader. How was your battery before you started? Have you tried holding the power button for 20 seconds for a hard shutdown?
As far as I know, the only thing that will cause power on issues is a broken bootloader. In which case, USB boot with firekit is your only option.

I guess I had at least 50% o battery charge, or more... I can't remember...
If I push the power button now, the Kindle will get warm, as if it was in use. And if I hold for 20s, will shut down...
I don't even started to install de fire fire fire bootloader, I installed the permanent root with super user and then went to install GApps. I guess my kindle was shutdown before Gapps install.
What should I do? Test the factory cable first?
When you say that I have to use Firekit, you are saying that I have to open my Kindle?

Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
EDIT:
Reading the FIREKIT Topic, this post: http://forum.xda-developers.com/showpost.php?p=25814062&postcount=26
My issue is kind of different from his... I'm guessing I'll have to open my Kindle anyway... Started yesterday, but I was messing with the case, gonna find some proper tools

VMs will not work. You have to create a bootable Linux LiveUSB thumb drive.

DuendePaladino said:
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
Click to expand...
Click to collapse
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.

kinfauns said:
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
Click to expand...
Click to collapse
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.

soupmagnet said:
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
Click to expand...
Click to collapse
I guess it might depend on the VM, but I disagree with the generalization that VMs are too slow and have issues with USB.
The only thing I've seen is that Oracle's VirtualBox USB implementation breaks adb. I've never tried VMWare, but Parallels Desktop for both my Ubuntu and Windows setups work perfectly. Never had an issue.

DuendePaladino said:
What should I do? Test the factory cable first?
Click to expand...
Click to collapse
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)

aarons510 said:
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
Click to expand...
Click to collapse
Without a working bootloader, a factory cable is useless.

soupmagnet said:
Without a working bootloader, a factory cable is useless.
Click to expand...
Click to collapse
All the scene leads to this... USB Boot.
About the USB stick, I was making some confusion about it.
But, I´ll gonna make one stick right now.

Guys,
I made the usb stick... just figuring how to open the kindle fire, without ruining the case.
But I guess today I'll made the short trick.
Question: I'll keep the 6.3 stock room that i tried to root? Or I'll have to download another ROM?

Is there any know issues about firekit compatibility with ubuntu 12.04?
Like this here? http://forum.xda-developers.com/showpost.php?p=25918331&postcount=10

I WON!!!!
I'M BEOWULF!!!!
Serious now...
Firekit method, with short trick... keep trying... until you find the right spot for the shor... and will work
EDIT:
THANK YOU GUYS!!!
I wouldnt be that happy without your help and your knowledge... You're the real Beowulf!

Possibly bricked Kindle Fire....help needed, and appreciated!

A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!

Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.

soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.

soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.

soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?

soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.

Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.

kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.

Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail

I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.

You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?

Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.

soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.

soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?

Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.

soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....

I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.

That will work. Download Ubuntu 10.4

[Q] Bricked Kindle Fire- Stuck on FFF, device not recognized by anything.

Alright folks, I would like to start off with a little introduction:
I'm extremely new to the rooting scene, i've been jailbreaking iphones and ipods since day one. That being said, I probably should have spent more time researching this technique before I went through with it.
Fast forward to today:
I tried rooting my device awhile back, wasn't a 100% successful and I really didn't have the time to work it out. I did have FFF installed and the next window (which i'm not exactly sure what it's called, which allowed me to boot in various moods and such)
Earlier today I got stuck in a boot loop, where my kindle would turn off as soon as i restarted it, and after i selected normal boot mode. I decided it would be a good idea to try a different boot option, so i tried the FF boot, which completely ruined my day.
My current situation is as follows:
I'm currently stuck on the first FFF screen (yellow triangle, with the green light on), i can do nothing else from that screen except hard (cold) reboots. When i plug my kindle in (Mac, windows 7, windows XP), the device is not recognized and i get zero response. I've tried a decent amount of suggestions on this forum, including Kindle fire unbrick (Which can somehow see that there adb is installed, but the bootmode is unknown)
Help out of this current situation would be wonderful. I'm really in a jam here.

Sounds like you are stuck in fastboot and you might have a dead battery too.
You should read this...
http://forum.xda-developers.com/showthread.php?t=1552547
1st post for background information, 2nd post for making sure your device drivers are loading/working, and the 3rd post for fastboot and adb commands. You'll probably need to use fastboot to change the bootmode back to normal.
This one...
http://forum.xda-developers.com/showthread.php?t=1623244
address dead battery problems. You might be affect this by this one as well.

Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?

B4CKlash said:
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
Click to expand...
Click to collapse
What do you mean by recovery screen? Because your first post said FFF and that's your bootloader. If the yellow triangle boot logo comes up and that's all that the display does (doesn't go black and redisplay the boot logo), then it's in fastboot mode. Windows should give you an indication that it's connecting with a series of 2 connection beeps (low->high tone) without a following set of disconnect beeps (high->low tone). The device manager will show something new in the list (this is covered in post #2 in the first URL I pasted for you).
Yes, you need to get something to get recognized by your computer then you need to install the proper drivers for it. Look at post #2 again, and see if you can figure out what device is appearing in the list and get the drivers loaded for it. If you get absolutely nothing, there's something wrong with the bootloader, your USB cable, USB port, or computer in general and it's a bigger problem.
If nothing happens on your computer, find another one and hook it up there. You might also look at this...
http://forum.xda-developers.com/showthread.php?t=1430038
and see if Linux can help you.

I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?

B4CKlash said:
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
Click to expand...
Click to collapse
Windows will be the only one that of the three that will beep at you. There's a better chance of you getting something done with Linux, but it's starting to sound like a bootloader problem to me. There's another user with a similar problem to yours and he's basically where you are now. Both of you might have to open up the case and get it to USB boot mode where you can upload a bootloader to it through USB. Try Firekit and see if it gets anywhere.

[Q] KF2 Empty and not recognized on windows

So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.

Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?

xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen

mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.

Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?

So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?

One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...

This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.

That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!

OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.

He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.

[Q] USB Boot Short Trick

I have a KF 1 which is bricked, can't power on, no led. Win recognizes it as OMAP4430 temporally.
After some research, seems Firekit is a good try. Everything is documented amazing, only part I am not quite sure is "USB Short"
I understand it is about using a wire to connect that particular pin in the picture, but what the other end should touch? If there is a picture would be great.

june12 said:
I have a KF 1 which is bricked, can't power on, no led. Win recognizes it as OMAP4430 temporally.
After some research, seems Firekit is a good try. Everything is documented amazing, only part I am not quite sure is "USB Short"
I understand it is about using a wire to connect that particular pin in the picture, but what the other end should touch? If there is a picture would be great.
Click to expand...
Click to collapse
Short pin to metal frame of the Kindle

I tried that, but always blocked at step two, Fix partition, wait for device.
Any suggestion? The Firekit, fix partition command. Does that mean my kindle is brick completely?
Thanks

june12 said:
I tried that, but always blocked at step two, Fix partition, wait for device.
Any suggestion? The Firekit, fix partition command. Does that mean my kindle is brick completely?
Thanks
Click to expand...
Click to collapse
Did FFF and Twrp flash? can you get to TWRP now?