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] Another Possibly Bricked Kindle Fire 1st Gen.

Okay, so I've searched this entire day, literally like the past 13 hours has been spent searching xda kindle fire forums, and googling the hell out of the internet searching for a fix to a situation like mine but have gotten no where! So, if I have somehow missed another thread that has this figured out I am apologizing now, but like I stated before I have tried and tried searching before deciding to post this. Now, moving on to the issue.
My Kindle Fire is stuck at the boot logo. It seems to be in fastboot mode, (4002), but will not go any further. If it is hooked up to the pc, which I'm running Windows 7 64 it will sound as though it connects, the screen will show the kindle fire logo (orange) really brightly btw, then go black with a disconnect sound on the pc then quickly show the logo again, this time dimmer and the reconnect sound on the pc sounds again.
What I did to cause this. I had a Custom CM7 rom on this (I don't remember which), and had this rooted and customized since last January. I remember that TWRP never would come up right (I don't know which version again) unless I reinstalled TWRP everytime I wanted to install a new rom on it using KFU. This time was no different, except I made a stupid mistake. I was trying to reinstall the stock rom 6.3.1 which I downloaded directly from Amazon, put it in the sdcard directory using TWRP and didn't rename it completely, instead only chaning the end to .zip, and not renaming the whole thing as update.zip (not sure if that makes a dif). Anyway, I did a delvik/cache wipe (not a factory reset) and attempted to run the install of the factory rom. Everything seemed fine until it came to the boot logo, and nothing else.
What I've tried so far. I have tried all of this on two seperate pc's using windows 7 64. I have tried the unbrick utility making sure I had the latest and greatest, making sure I tried every which way it has to unbrick it to no avail. I have tried the KFU, again the latest and greatest trying everything IT has to see if any of it would make a difference to no avail, even chaning the bootmode but no matter which mode I try, the Kindle will reboot but stay stuck regardless of whatever I tried after the reboot. I have tried using command prompts to bring up ADB Shell but again, when I run ADB devices it will show up, and the drivers hardware ID's are correct according to all the forums with the drivers listing the Kindle as an ADB android device but when I try to run a shell command it says that no such directory is found or something of the sort. If it doesn't say that than it will simply state that it is waiting for the device, and I do try to disconnect then reconnect the cable at this time, even rebooting the Kindle but it never moves past "waiting for the device". I have tried shorting it by opening the case and putting something metal to the one point and the metal border but the most that did was turn the device off! When I try to turn it on again it simply stays on the boot logo. I have tried the factory cable, and still nothing works! I have changed the script for the driver to make sure it recognized the Kindle but that didn't work either.
I am at the end of my rope here, and I am begging for someone to simply help me who may know exactly what I am going through that knows what to do! I am sorry for the lenghty post, but I figure certain questions will be asked if not for my detailed accounts of what's happened and what I have done to this point. Thank you to anyone reading this and thanks to anyone who replies, you have my gratitude!

Try Soupkit http://forum.xda-developers.com/showthread.php?t=1850038 it will rule out all the formalities of drivers. My guess is that your shell is missing or broken so that factory cable will come in handy. If you want to do without the whole setup try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358 if you desire assistance I would be happy to help.

So friendly!!!
Thepooch said:
Try Soupkit http://forum.xda-developers.com/showthread.php?t=1850038 it will rule out all the formalities of drivers. My guess is that your shell is missing or broken so that factory cable will come in handy. If you want to do without the whole setup try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358 if you desire assistance I would be happy to help.
Click to expand...
Click to collapse
Thank you so much for replying so quickly! I have seen you reply to others, and I was actually dreading posting due to some unruly replies I have witnessed to people like me. But you are always helpful and I appreciate that! I'll try setting up ubuntu (I'm assuming that soupkit only works with that, correct?) and I'll read your post and let you know what happens. Thanks again!

mikeydjs said:
Thank you so much for replying so quickly! I have seen you reply to others, and I was actually dreading posting due to some unruly replies I have witnessed to people like me. But you are always helpful and I appreciate that! I'll try setting up ubuntu (I'm assuming that soupkit only works with that, correct?) and I'll read your post and let you know what happens. Thanks again!
Click to expand...
Click to collapse
If you use my iso Soupkit has already been ran just follow my instructions for creating it . If you choose to do the setup on your own use linux mint mate 13 32 bit or precise pangolin ubuntu 12.04 or 12.10 32 bit. 32 bit works on both 32 and 64 bit machines.

Trying Ubuntu 11.10
Thepooch said:
If you use my iso Soupkit has already been ran just follow my instructions for creating it . If you choose to do the setup on your own use linux mint mate 13 32 bit or precise pangolin ubuntu 12.04 or 12.10 32 bit. 32 bit works on both 32 and 64 bit machines.
Click to expand...
Click to collapse
I tried using ubuntu 12.04, but the live usb application wouldn't recognize the .iso I got from pbay. It did see the 11.10 version so I went with that instead. Man! Why did I ever not use Ubuntu before!!! Really nice os. Anyway, with that being said, I downloaded SoupKit while on ubuntu like you instruct in your post, but when I click on install.sh I am seeing that it says Soupkit is already installed. So I don't see the prompt to run in terminal. Do I have to uninstall or delete the current occurrence of soupkit on this ubuntu install? Or do I continue on with the setup.sh file located in the soupkit folder? Also, I plugged my fire in while on ubuntu and I don't see a prompt for it to install any drivers, nor do i know how to located usb connected devices (Too used to Windows I guess, lol). Thanks again for you help, and hopefully I'm not sounding like a total noob!

Yeah sorry 11.10 is funky with soupkit during testing I really had to cheat to get a proper install try going with my prefab iso its far more simple and stable enough. I know the download is large that is because of it's own prepacked casper r/w. Drivers do not install on linux rather it is setup as udev rules that configure for a specific device lets just say it's different to avoid going into to much detail. Yes setup.sh is the next run if it doesnt run in terminal but that's not the proper way to run soupkit stick with the distros I recommend. If it doesn't find the distro in the dropdown try unlisted iso if you can`t find the iso when attaching start to fill the name of the iso in it will begin to auto complete.

Ubuntu 12.10?
Thepooch said:
Yeah sorry 11.10 is funky with soupkit during testing I really had to cheat to get a proper install try going with my prefab iso its far more simple and stable enough. I know the download is large that is because of it's own prepacked casper r/w. Drivers do not install on linux rather it is setup as udev rules that configure for a specific device lets just say it's different to avoid going into to much detail. Yes setup.sh is the next run if it doesnt run in terminal but that's not the proper way to run soupkit stick with the distros I recommend. If it doesn't find the distro in the dropdown try unlisted iso if you can`t find the iso when attaching start to fill the name of the iso in it will begin to auto complete.
Click to expand...
Click to collapse
I'm downloading ubuntu 12.10. Not sure if this will make a difference, but I will try anything at this point! Will this make a difference?

mikeydjs said:
I'm downloading ubuntu 12.10. Not sure if this will make a difference, but I will try anything at this point! Will this make a difference?
Click to expand...
Click to collapse
It will make a difference in how soupkit setup runs if it doesn`t run correctly it causes issues you want it to be as stable as possible. Make sure you drag the slider to add at least 1300 mgs of persistent for saving data between reboots. Once you get this done I can assure you its one of the finest tools to ever grace your kindle Soupmagnet went all out on its creation make sure you stroke his thanks button.

ubuntu 12.10
Thepooch said:
It will make a difference in how soupkit setup runs if it doesn`t run correctly it causes issues you want it to be as stable as possible. Make sure you drag the slider to add at least 1300 mgs of persistent for saving data between reboots. Once you get this done I can assure you its one of the finest tools to ever grace your kindle Soupmagnet went all out on its creation make sure you stroke his thanks button.
Click to expand...
Click to collapse
Ok, so I'm currently running ubuntu 12.10 from the usb stick and I tried double clicking on the install.sh again with the same result! Do I have to install ubuntu in order for it to run properly? I keep getting the message when I open install.sh that soupkit is already installed and that I have no need to install it again. Am I doing something wrong here?

Try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358.

mikeydjs said:
Ok, so I'm currently running ubuntu 12.10 from the usb stick and I tried double clicking on the install.sh again with the same result! Do I have to install ubuntu in order for it to run properly? I keep getting the message when I open install.sh that soupkit is already installed and that I have no need to install it again. Am I doing something wrong here?
Click to expand...
Click to collapse
Yeah, I need to fix that...delete your /bin/SoupKit folder and try again.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
Yeah, I need to fix that...delete your /bin/SoupKit folder and try again.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Lemme know when your ready for more testing .

Rooted KF not recognized (?) by PC

Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:

KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
When I flashed CM10.1 I needed to download "google android usb drivers" or something...

sghsmorgan said:
When I flashed CM10.1 I needed to download "google android usb drivers" or something...
Click to expand...
Click to collapse
Yup, I've tried every possible solution out there and nothing has helped.

kindle fire not found after cm10
KindleTrish said:
Yup, I've tried every possible solution out there and nothing has helped.
Click to expand...
Click to collapse
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.

galearned said:
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.
Click to expand...
Click to collapse
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.

KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.

KindleTrish said:
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.
Click to expand...
Click to collapse
zerbey said:
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.
Click to expand...
Click to collapse
This has been talked about several times, but for some reason no one ever seems to catch on.
You have to check the hardware IDs reported by your device in the Device Manager for every ROM you install, and make sure the information matches whatever is listed in your 'adb_usb.inf'.

Trying ti fix a bricked Kindle Fire HD 8.9 for a friend

Hey Guys,
OK, so I have spent about 5 hours scouring this forum and google and am in need of some help. I am trying to fix a kindle for someone and I really dont have much experience with Kindle at all but have rooted most of my android phones with no problem and flashed different roms etc... Well this thing seems a little hosed. When I turn it on, it shows the kindle splash screen then goes directly to the red screen. I wanted to use fastboot but device manager doesnt even show the device. When I power on the kindle, it will flash the jem device (Jem-PVT PROD-04) and then it goes right away so I dont really have any opportunity to install the drivers. WIth that being said, I cant use fastboot (just is stuck at waiting for device) or adbdriver.
My buddy attempted to root the kindle and was able to using yeymasterroot or something like that then proceeded to use fireflash and using freedom boot and twrp.
Has anyone gone through this and fixed it? How can I get fastboot to work (I tried installing the USB drivers and also installed the Android sdk). Is this thing just hosed and I should give up? I really dont want to and look at it as a challenge and was hoping maybe someone has had the same thing and figured it out? Oh, and I asked what version it was on before and he said 8.5.1.
Thanks in advance.

The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.

macman005 said:
The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.
Click to expand...
Click to collapse
Thank you.
Just an FYI for anyone that runs into the same issue. I absolutely tried every method I could find (I must have spent probably 15 hours or so researching) to use WIndows and finally gave up. I tried the most recent version of Ubunto live and this did not work as well. Soupkit would not install, I had to use Ubunto 12.04. Once I loaded this, I installed soupkit then tested fastboot and was good to go. Once in fastboot, I used the followink step by step wiki (follow every step to a T):
wiki.cyanogenmod.org/w/Install_CM_for_jem
Now, I have it working and it is fast and nice (albeit a bit heavy).
I hope this helps someone avoid wasting all of the time that I did for this but I am glad it is finally working. Next I will install Lollipop.

Trick how to fix this
maybe it is too late but it will help someone else probably if they face the same issue, first you will need to reboot windows with drivers signature disabled and then install these drivers who was made compatible with the jem model (the only one that worked for me) you can install them by just right clicking the .inf file after extracting the archive, or by going to the device manager and then make it show the hidden devices and you will see the Jem-PVT PROD-04 fadded in the devices list, you can right click on it and access to properties and from there you can install drivers via update (I guess you have the minimal windows knowledge to do this)...