Related
Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...
b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.
updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7
dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.
I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"
I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.
You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.
Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..
I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )
A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..
I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*
Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.
u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick
If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk
In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#
1) Yes I checked search results.
2) Yes I've googled.
3) Yes I've tried the Kindle Fire Utility, the http://forum.xda-developers.com/showthread.php?t=1356257... links options.
With that being said, here's my issue;
Got a KF a couple days ago...
Yesterday, followed some online instructions to put GO Launcher EX on there to replace the carousel deal.
Followed instructions to the T.
Restarted. Got to "Choose your OS" screen (or whatever it precisely says...)
Picked GO... then it froze.
Now, when it restarts (yes, its the 30 second hard restart), it gets stuck on the Kindle Fire splash screen.
I have tried the above utilities.
I have hard restarted.
I have fully charged and ran the battery dry and tried again.
When I use the utilities, the problem is, my PC will not recognize the Kindle (it see's it as a removable storage device, but it doesn't click over to 'Kindle', and thus the utilities can't interact with the device itself, I suppose).
I've tried different USB ports and connecters (I have 2 regular kindles in the house, too). But I know all the peripherals work through cross-testing.
Essentially, what else can I do? (I got it from WalMart, and they're currently out of stock, so I can't return it till next week, but I'd like it fixed before then if possible)
I've tried several different methods from these forums too, but I *always* hit the same snag... whenever any utility is 'waiting for device', it simply will not find it, because the PC doesn't see it properly. It sees *something* (removable storage) but not as a kindle, and thus won't allow the utilities to interface with it.
Are there any physical things I can do to hard reset it without destroying any warrantys?
Any help appreciated!
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
first i need to know if you have fff (custom bootloader - yellow triangle) on it ?
then do you have a recovery (twrp) on it ?
what os/bit of computer ?
In kindle utility go to bootmodes and enter normal (4000). Just had that problem last night.
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
b63 - I hope your right!
no - I do not have the yellow triangle.
no - I do not have TWRP on it, i have tried, but cannot get anything onto the kindle.
my PC is window7, 64bit
Euryon said:
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
Click to expand...
Click to collapse
Do you have all the kf drivers installed on your computer? I know that when I unbricked mine I had all the drivers installed but I had to reinstall them for some reason. If you do not have them I can post them later on tonight when I'm at home. However, I have TWRP installed on mine, and Cyanogenmod 7.2, so hopefully yours is able to connect to your computer.
---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------
b63 said:
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
Click to expand...
Click to collapse
In order to remove the bad launcher, you need to have your device connected to your computer to remove it using adb.
ok so b63 helped me out big time here....
about 2 hours ago we got on a teamviewer session (download this if you want these guys to help you with serious issues!)
took me a minute to figure out how to allow him/her proper access to my screen
anyway
i don't understand the technical stuff
but
what i had done wrong is that i didnt root the KF before trying to install the GO... software (i think)
b63 had a heck of a time trying to discern the problem with me being about as useful as a dead fish, but get there he/she did
after much fanangaling, b63 managed to install the TWRP and ADP on my KF, allowing it to fastboot, and basically allowing it to be read by my PC, and so fixed.
im sure it would have taken b63 all of 5 minutes in real time, but using the quirky teamview and my slow net speed didn't help
still, thanks VERY MUCH to b63 for fixing the **** out of my KF, and being very helpful and patient all along!
thanks
Just wanted to drop b63 a note here that I "thanks"ed their post above - not necessarily for the post but for going above and beyond. The people on these forums are (for the most part) really great. (Too bad there have to be a few who are demanding of the developers to get this feature or that fix done faster without taking into account that the devs do this all in their free time.)
YES, search finally led me here!
Euryon, I have the exact same thing happening with my KF right now.
Do you remember any specifics of how b63 carried out the steps you listed?
b63, any chance you could help me with mine? My issue is identical with Euryon's down to the letter.
Same Problem
Could someone please help me i have the same problem
same problem here! please can someone give a step by step? My fire is unrooted and I did nothing to it except try to install the go launcher and after I selected it as the default launcher it got stuck at the kindke fire logo.
I tried the Kindle unbricking utility but it cannot find the device even after I installed the adb composite interface
also, my fire is not showing up as a kindle - it is showing up as an android device.
rollno88 said:
also, my fire is not showing up as a kindle - it is showing up as an android device.
Click to expand...
Click to collapse
Have you added the fires usb ID to your system?
Sent from my Amazon Kindle Fire using Tapatalk 2
thanks for replying, and I have no clue how to do that. I'll search and get back .
---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------
okay, I already did that by editing the android sdk(as a prerequisite to rooting, which I planned to do eventually) - so when I connect my fire it first shows up as a kindle, and after updating the software through windows and installing drivers through KFU, it comes up as an android device and the interface is adb composite. Now if I try to install TWRP through KFU it keeps switching between adb composite interface and plain adb. And both KFU and KUFU keep waiting but are unable to find my device.
also, my fire alternately shows up as a usb composite device and an android device. PLEASE help
okay I solved it with KFU (finally!) although I have no clue how I did it as I didn'tdo anything I hadn't tried earlier so, managed to install TWRP and then wiped everything and finally my fire could be read - then I deleted go launcher and now my fire is back from the grave
A big thank you to all the helpful posts at this forum - u guys are the best
Same issue
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
edit: when rerunning KFU, i kept getting the message that many execs failed because "/system/bin/sh" directory does not exist.
I don't know if that helps narrow down what might be happening, but I saw that coming up a lot in the cmd prompt.
zeissbickham said:
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with an emphasis on post #2. You need to know what mode your device is in by looking at the device manager and make sure your drivers are loading correctly for that mode. If you can get to TWRP, you can mount your USB mass storage device, copy a new zip file of either the stock software or a custom ROM and flash it.
Thank you. I will be trying this shortly.
fully bricked
I followed the guide and got to a point where the Kindle Fire animation was playing. It loaded up to the unlock screen and then automatically shut itself down - would not stay on when either connected or disconnected. Tried installing a ROM but still shut down. Started the recovery and hit factory reset, still auto shutdown. Tried clearing a partition as described in the tutorial and now it's fully bricked. Will not turn on when connected to computer, to outlet, to another cable.
Thanks for trying to help.
I was given a "bricked" kindle to take a look at last week. Here is the story I was given.
User installed a custom rom, but it was for a lower version (didnt fully understand this)
Afterwards it locks on the kindle fire logo during boot.
User made a factory cable to restore the unit, and now anytime ANY usb is plugged into the device it shuts off immediately.
I tried opening the device and shorting the required pins, but plugging in the usb doesnt do anything. It appears to be charged, but I have no way of knowing.
It doesnt show as anything in device manager (it looks to be fully off)
Pressing the power button still gets it to start and hang at the kindle logo.
My guess is the factory cable was made incorrectly and shorted the usb board but I figured I would see what others thought.
Thanks
Any opinions?
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
narume said:
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
Click to expand...
Click to collapse
Thanks for the thought, but nothing shows in device manager. I believe this is due to the kindle shutting off the second you plug any usb into it.
bump?
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Thepooch said:
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Click to expand...
Click to collapse
I'll definitely try the factory cable again (the user tried this, but who knows)
But as far as the device not being recognized... Like I said, the second you plug it into usb (either computer, or power plug) it shuts off.
Its not that I get a windows notification for "not recognized" windows doesnt see it period.
it should not turn your device off it should appear stuck at the logo like I said sounds like a bad build guess you misunderstood
---------- Post added at 06:45 PM ---------- Previous post was at 06:38 PM ----------
only use a 2.0 usb port and try it from the device in an off position
If this is the wrong forum, please move as needed and I apologize.
I recently purchased (2) refurb'd 1st-gen Fire's with the intent of loading CM10.1 on them. I don't know what version was on the first one, but the second has 6.3.1 on it.
I downloaded KFU 0.9.9, the CM zip, the gapps zip, and after some playing around, was able to make it all work on the first Kindle, via a Win7 laptop.
When I plugged the second Kindle in (same laptop, same USB cable,) it was not recognized. I then plugged the first, now-flashed one back in, and it wasn't recognized, either (within KFU.) I checked the device manager, and the Kindle had the yellow triangle of doom attached to it, but it at least showed up. I again plugged the second unit in, and not only is it not recognized by KFU, it's not being recognized as a connected device within the device manager at all. I can't view files on it, nothing.
I then tried installing KFU on a second laptop, and got the same scenario again. I tried downloading a different KFU utility, no luck in either case.
Am I doing something completely wrong here? I just want to get CM on this second Kindle, and nothing at all seems to be working now, after the first one seemed to go pretty smoothly.
Thanks
SlightlyOpaque said:
If this is the wrong forum, please move as needed and I apologize.
I recently purchased (2) refurb'd 1st-gen Fire's with the intent of loading CM10.1 on them. I don't know what version was on the first one, but the second has 6.3.1 on it.
I downloaded KFU 0.9.9, the CM zip, the gapps zip, and after some playing around, was able to make it all work on the first Kindle, via a Win7 laptop.
When I plugged the second Kindle in (same laptop, same USB cable,) it was not recognized. I then plugged the first, now-flashed one back in, and it wasn't recognized, either (within KFU.) I checked the device manager, and the Kindle had the yellow triangle of doom attached to it, but it at least showed up. I again plugged the second unit in, and not only is it not recognized by KFU, it's not being recognized as a connected device within the device manager at all. I can't view files on it, nothing.
I then tried installing KFU on a second laptop, and got the same scenario again. I tried downloading a different KFU utility, no luck in either case.
Am I doing something completely wrong here? I just want to get CM on this second Kindle, and nothing at all seems to be working now, after the first one seemed to go pretty smoothly.
Thanks
Click to expand...
Click to collapse
Try re-installing the driver
Guitarman2010 said:
Try re-installing the driver
Click to expand...
Click to collapse
Sorry, forgot that in the OP.
I reinstalled the drivers using install_drivers.bat several times (each time it says successful.) I also uninstalled the "working" device (Kindle 1) from Device Manager and then installed the drivers afterward. No change.
I called Amazon support earlier this evening, and (but of course) the device is out of warranty. They recommended that I called the company that I purchased them from (Best Buy,) but the 15-day return window has passed so I'm assuming they'll tell me to pound sand.
On the call, I did ask whether or not there was a newer system version available (this is on 6.3.1_user_4107920) and was told that there is a newer version, and to let it sleep for 2 hours without interruption and it would find it. Several hours later, it's listing as no updates available. I thought that maybe if there were a system issue, an update would overwrite the problem and I'd actually be able to see the device in some way. So, with no cable and no auto-update, I manually installed the .bin (via Amazon's updates page, but I don't have enough posts for external links) and ran it successfully. The device was updated to 6.3.2_user_4110520, but is still not recognized in any way, beyond the fact that it charges, as indicated by the battery icon.
I'm going to stop by Best Buy tomorrow, but I don't imagine they're going to try and help me out.
The idea of the USB port being bad crossed my mind, but because it was charging I disregarded it. After running out of realistic ideas, I finally compared the two USB ports. The flashed, working unit has a pristine-looking port, while the problematic one looks mangled. I tried to ever so gently straighten and isolate the pins, but the connection may be severed at the base where I can't see it.
I'm fairly sure this is the problem. After doing this, and holding the cable just so, I was able to get the device manager to update, although not what I wanted. When it updated, and recognized the Kindle to some degree, it actually dropped connection to my mouse. When I let the cable go from where I was holding it, the device manager recognized my mouse again.
So, yea, I guess a trip to Best Buy is in order.
SlightlyOpaque said:
The idea of the USB port being bad crossed my mind, but because it was charging I disregarded it. After running out of realistic ideas, I finally compared the two USB ports. The flashed, working unit has a pristine-looking port, while the problematic one looks mangled. I tried to ever so gently straighten and isolate the pins, but the connection may be severed at the base where I can't see it.
I'm fairly sure this is the problem. After doing this, and holding the cable just so, I was able to get the device manager to update, although not what I wanted. When it updated, and recognized the Kindle to some degree, it actually dropped connection to my mouse. When I let the cable go from where I was holding it, the device manager recognized my mouse again.
So, yea, I guess a trip to Best Buy is in order.
Click to expand...
Click to collapse
So... you think the USB port on the tablet is bad? Or you think the USB port on the PC is bad?
I'm having a very similar problem with trying to root a second KF. First one rooted just fine. Installled CM10, gapps, the works. Go to try and do the same thing, and it won't work.
I also tried it on another PC, and it didn't work on that one either. That other PC however is an old server PC that I forced Windows 7 on, and it has some major issues, so not really a reliable PC.
Now the PC I'm on is too old, I'm gonna need to take Windows 7 off of it. A recent update rendered my PS/2 ports obsolete, and I'm not PC-literate enough to know how to roll back a KB file. Linux it is.
...speaking of; have you tried connecting the KF/rooting it via Linux? I have a bookmark for that somewhere. Lemme see if I can find it... or link you to it:
http://forum.xda-developers.com/showthread.php?t=1568340
Have you seen that thread?
The drivers that come with KFU always caused me problems to no end. I would suggest you uninstall them and install the Windows 8 drivers I supplied
http://forum.xda-developers.com/showthread.php?t=2185402
Sometimes (don't know why), you need to mount your Kindle for it to be detected. If you've booted in recovery, mount the usb drive. If you're loaded inside the ROM, turn on debugging.
need these drivers, site doesnt redirect properly
Socially Uncensored said:
The drivers that come with KFU always caused me problems to no end. I would suggest you uninstall them and install the Windows 8 drivers I supplied
http://forum.xda-developers.com/showthread.php?t=2185402
Sometimes (don't know why), you need to mount your Kindle for it to be detected. If you've booted in recovery, mount the usb drive. If you're loaded inside the ROM, turn on debugging.
Click to expand...
Click to collapse
ok guys I have a unmodded 1st generation kindle fire here
it works fine except it does not recognize on my pc at all.
the usb charges the battery and all but I can not load files to or off my kindle via usb
it does not show up at all in my
windows 7 64 bit OS
any help would be great
The same thing happened with to me. I just switched the usb port on my pc that the cable was plugged into, and it worked.
Sent from my Amazon Kindle Fire using xda app-developers app
if only..............
BillBill17 said:
The same thing happened with to me. I just switched the usb port on my pc that the cable was plugged into, and it worked.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
wish that it was that simple
but alas I have tried different cables, pc's ports it even cuts off when its on the charger
and according to amazon, on the charger it should power on and it won't
so thanks for the input
am stuck side loading for now, amazon has offered a trade in amount for it, but honestly
this close to Christmas, there is no money for it, hope they honor it after the new year
kindlefire not seen by computer FIX
I have 8 different Kindle Fire devices for my family. I tried to hook my daughter's best friend's Kindle to my computer so I could books on hers through Calibre. My computer couldn't see her Kindle. I tried different ports. Nothing. It could see all the other Kindle devices just fine (HD and non-HD alike) - just not hers (a second generation Kindle). I dug for hours trying to figure it out. At last I stumbled upon a post that helped. This is what I did and my computer sees it fine and Calibre is working beautifully with it.
Systems I used:
Windows 7 Home Premium SP 1
KindleFire Gen 2 System Version: 10.5.0_user_5060020
DISCLAIMER: Messing with device drivers is NOT for the unexperienced user, and can much mess up your computer beyond the point that the same user can repair it. I cannot take responsibility nor offer help if things go wrong beyond your capability to repair it.
Connect your kindle (as normal- you don't need to slide to unlock or anything... just connect it)
Open your Device Manager: Click Start -> (search) Device Manager
If your device was not recognized, a device with a yellow exclamation mark will be listed under Other devices. Mine was just listed as "mtp".
It stated that there were driver issues including an MTP issue.
To set your Kindle as a Kindle portable device, do this:
Right-click the device in the Device Manager and select Uninstall. This removes the current driver, and provided you disabled automatic driver installation, will leave it as a unrecognized device with the yellow exclamation mark icon under Other devices. You may have to unplug and replug the Kindle after you uninstall it in order to see it listed under the "Other devices".
Right-click the device again and select Update Driver Software ->Browse my computer for driver software -> Let me pick from a list of device drivers on my computer.
You should now have a large list of common hardware types. Here, scroll down and select portable devices -> Standard mtp device -> mtp USB device under the Disk drive.
You will be prompted to confirm this selection, click Yes. The Kindle will now be recognized as a portable device listed as "Kindle" by your computer.
Calibre sees it fine. It is now listed under my "My Computer" as a portable device sublisted as a Kindle.
Doing this did NOT change how my computer saw my KindleFire HD 8.9. It did not change anything EXCEPT the particular Kindle that would not be seen previously. I hope this helps some others who are lost figure out theirs as well.
cougarkittyn said:
I have 8 different Kindle Fire devices for my family. I tried to hook my daughter's best friend's Kindle to my computer so I could books on hers through Calibre. My computer couldn't see her Kindle. I tried different ports. Nothing. It could see all the other Kindle devices just fine (HD and non-HD alike) - just not hers (a second generation Kindle). I dug for hours trying to figure it out. At last I stumbled upon a post that helped. This is what I did and my computer sees it fine and Calibre is working beautifully with it.
Systems I used:
Windows 7 Home Premium SP 1
KindleFire Gen 2 System Version: 10.5.0_user_5060020
DISCLAIMER: Messing with device drivers is NOT for the unexperienced user, and can much mess up your computer beyond the point that the same user can repair it. I cannot take responsibility nor offer help if things go wrong beyond your capability to repair it.
Connect your kindle (as normal- you don't need to slide to unlock or anything... just connect it)
Open your Device Manager: Click Start -> (search) Device Manager
If your device was not recognized, a device with a yellow exclamation mark will be listed under Other devices. Mine was just listed as "mtp".
It stated that there were driver issues including an MTP issue.
To set your Kindle as a Kindle portable device, do this:
Right-click the device in the Device Manager and select Uninstall. This removes the current driver, and provided you disabled automatic driver installation, will leave it as a unrecognized device with the yellow exclamation mark icon under Other devices. You may have to unplug and replug the Kindle after you uninstall it in order to see it listed under the "Other devices".
Right-click the device again and select Update Driver Software ->Browse my computer for driver software -> Let me pick from a list of device drivers on my computer.
You should now have a large list of common hardware types. Here, scroll down and select portable devices -> Standard mtp device -> mtp USB device under the Disk drive.
You will be prompted to confirm this selection, click Yes. The Kindle will now be recognized as a portable device listed as "Kindle" by your computer.
Calibre sees it fine. It is now listed under my "My Computer" as a portable device sublisted as a Kindle.
Doing this did NOT change how my computer saw my KindleFire HD 8.9. It did not change anything EXCEPT the particular Kindle that would not be seen previously. I hope this helps some others who are lost figure out theirs as well.
Click to expand...
Click to collapse
This is a thread for the first gen kindle fire, you may get better help in the 2nd gen Q and A section
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Start here http://forum.xda-developers.com/showthread.php?t=2228539
Frequently Asked Questions - 2nd Generation Kindle Fires
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'.