Related
I rooted my Kindle Fire about a month ago with KFU. Everything was fine until I turned it on one day and I got stuck at the Triangle screen. None of the reboot tricks work. The interesting thing which I think is what is stopping me from being able to successfully use other methods is that when I plug my Kindle Fire into my computer via usb, it connects, and then disconnects (the USB) about 2 seconds later. I've tried different ports, etc. Any help on this issue would be greatly appreciated. I've read over multiple things, but don't see a mention to the kindle being disconnected via usb so quickly, thus stopping me from being able to do anything.
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
soupmagnet said:
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
Click to expand...
Click to collapse
I've tried the rebooting the Kindle while trying to reset the kindle to booting "normally" within the KFU. I've tried holding down the power button on a reset, then pushing it again until it is orange, none seem to work. I'm confident I could get it to work again if the kindle did not disconnect from my computer so quickly. By this I mean I hear the "usb chime" when I plug it in, then within seconds the disconnect chime plays. During the brief few seconds it is connected, it shows up on my devices list, but obviously when the usb disconnect chime plays, it disappears off of the device list.
edit: I'm using windows 7 Ultimate.
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
ErikV55 said:
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
Click to expand...
Click to collapse
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
kinfauns said:
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
Click to expand...
Click to collapse
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
ErikV55 said:
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
Click to expand...
Click to collapse
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
kinfauns said:
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
Click to expand...
Click to collapse
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
ErikV55 said:
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
Click to expand...
Click to collapse
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
kinfauns said:
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
Click to expand...
Click to collapse
I've tried to reset the bootmode via the KFU method recommended in the guide posted here (normal, 4000 and trying to reset when it says waiting for device) The device pops up in the device manager as an "unknown device" which may be a problem with the version of the drivers im DLing. I'm using KFU version 0.9.6
When I first DLed them it seemed as if the drivers were installing correctly, when I plugged in the Kindle is said drivers were being installed but it failed because the device disconnected after the 2 seconds.
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
hunterhk said:
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
Click to expand...
Click to collapse
Thanks for your response, I will go through these and report back when I get back home from class.
ok, now I have my kindle being recognized by my computer as "android phone" with the sub of "android adb interface." If I have read the guide correctly that means it is in fastboot mode. However when I open kfu it says the kindle is offline.
If someone would be willing to help me out through Skype I would gladly appreciate it. I'm really at a lose as to what to do at this point.
and no stupidly I do not have FFF or TWRP loaded, since I first rooted it when I was a super noob. The usb driver seems like it should be able to work according the the Kindle fire beginners guide, but KFU does not recognize the kindle even though my computer does.
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.
i live in australia, and got a kindle fire for my b'day, and wanted to access the features that arnt allowed outside the US. my first search i came across rooting it, and it seemed straight forward, the instructions, which was for kindle fire utility. i installed the drivers, then did run.bat, that worked and detected the kindle. then it said to go to bootmode menu, then install permanent root with superuser. it lasted about 2 seconds then it rebooted the kindle. thats it. unless i misread something. it looked exactly the same as before, i didnt know what to expect, but some hint that something had changed, so i figured it didnt work. then i saw the bootmode menu, and selected normal, and that just reset it, then chose fastboot, not knowing what it did. so i tried that. now my kindle isnt detected by the pc at all, it just says kindlefire on the screen, and the power light is orange.
most of the fixes i have come across all start with "we assume you have this or this installed on the kindle, and that it is detected in some way by the computer". but it isnt being detected at all. i saw the fireusb thing, with ubuntu, i attempted that, but it didnt seem to recognise the fk file, which was only 9mb, it was the only file the instructions said to take, and that its supposed to unpack to more tools to manage it and get it to register that the device is plugged in.
then the only thing else i could try was opening the back of it, and doing the shorting out thing, then plugging it in, but KFU didnt detect it and not sure what else to try. i am a complete noob at this i know, so i dont know where to go from here.
edit: turns out the kindle doesnt like being detected in 3.0 usb, or usb hubs. so if you are trying to get it to detect, use the ones in the back of the pc lol... soo much wasted time on this over such a simple thing, but im glad it was a simple mistake, and not a major problem. though now i have the issue of having small sratched and stuff on the side when i opened the case, but oh well, learn from my mistakes!
have you tryed holding the power button for like 20 seconds and completely powering it off then powering it back on? Chances are your stuck in fastboot many people lately have had this happen so your not alone. Some say to power it off have the kindle fire utility window open plug your kindle in it should power back on then recheck status. Look in device manager and see how it appears there windows is terrible with drivers when this happens it will try to install what it thinks best even if the device is unknown rendering adb useless until the driver is reinstalled correctly. Most the time this is not enough to set the bootmode back to normal because it cannot detect your device correctly. http://forum.xda-developers.com/showthread.php?t=1670405 this may help but its not the only thing that can be done. If some of the files actually did get pushed to your device such as fff the bootmode can be changed via the bootloader. Try the power down thing see what you get and post back.
---------- Post added at 01:03 AM ---------- Previous post was at 12:12 AM ----------
also look at this thread http://forum.xda-developers.com/showthread.php?t=1670300
Another thing simply just rooting your device does not change how it appears its not until you install twrp and fff that it changes there are simple ways to do that first we need to get your boot mode corrected and ensure you are rooted then the rest can get sorted out. Check how your device is listed in device manager first.
sorry for the delay. spent all day just trying to install ubuntu, then connecting to the internet wirelessly, seems to have a lot of issues. anyway, in the end i got it all set up, followed that guide, then ran firekit, but still not detected. in windows and ubuntu, when its plugged in by usb, nothing at all shows up in device manager, or lsusb. ive tried doing the short trick, then plugging it in, still doesnt get detected. and honestly i think when i thought i rooted it, i may have misclicked and instead of selecting instant permanent root or whatever that command was, i just did a normal boot, so im pretty sure i selected fastboot for a stock kindle. i know the usb cord works cause i use it for my phone.
adb devices doesnt detect it either. i got all the doesnloads from the link you posted, would they all be up to date? also the adb_usb.ini file, had to get online, but not sure if that matters.
In Linux, type
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
...and make sure you have the following:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Reboot to save any changes you've made and check "lsusb" again.
i added both those rules, one of which was already in there, but it still isnt being detected. typing lsusb, then up and enter repeatedly as i plug it in doesnt show any changes at all, its not being detected.
While unplugged, type
Code:
udevadm monitor --environment
Plug it back in and see if you get a result.
sadly not. tried plugging other things in, they all appeared, also my phone with the same cord. but nothing at all when i tried the kindle, with it powered off when plugging it in, and with the shorting out thing, nothing at all. i dont understand how booting in fastboot by accident, with a stock kindle, could make it not be detected at all, ive read people causing worse things getting it to at least be picked up. im pretty sure thats all i did, i cant think of how i could of done anything worse.
That's interesting...I'm having the same problem with mine but I was led to believe it was my VM causing the problem.
So, just to make sure...
Are you using a VM Linux install or USB or other?
Have you tried multiple usb ports?
Do you have FireFireFire installed and if so, what version are you using? (If you're not sure, what does your boot logo look like?)
What Linux distro/version are you using?
this is the first time ive ventured outside windows, so not sure what you mean by vm, but i installed ubuntu with a disc, to a second hard drive that i had in my comp.
and nope, dont have firefirefire installed, im pretty sure its just a stock kindle still, just stuck in fastboot by mistake, and not being detected by any usb port.
also, would a factory cable work? if its makes it boot differently, you would think it would? i really suck at making things, but http://forum.xda-developers.com/showpost.php?p=23049902&postcount=254 is selling them. sure it would probably take 2 -3 weeks, but if it works then thats better then not using it forever lol. and if i get it fixed before it even arrives, well, cant complain about that.
A factory cable will only help if you can get Linux to detect your device. Considering you can't get Linux to detect any USB event when plugging your Kindle in, it most likely points to a problem with your Linux install.
It would be very helpful to know what version of Ubuntu you are using.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
though there is a few updates in theupdate manager. but last time i installed them, it completely disabled my wireless adapter and ened up reinstalling ubuntu to get it to work again cause i couldnt figure out how to get it detected again. but redownloading it all now to see if its any different. i hope it is just a problem with the install, at least thats something i can work on.
at soupmagnets suggestion, i made a liveUSB, which i had tried to do earlier, but didnt succeed, where as now it does work, im pretty sure i have the drivers now installed, but not sure where to go from here, with it still not being detected at all.
haaa... im an idiot. just putting that out there. ok, so i got the kindle detected. turns out it was the usb ports. one was usb 3.0, and the others were in a hub, which apparently the kindle doesnt like. i got frustrated and plugged it into the back of the pc, and it is now unknown device in device manager. thinking i should go back into ubuntu, see if its also detected there, and go from there
oh yeah the usb is a problem and use 2.0 and go back to ubuntu you will see its detected in a couple hours Im gonna retest soups script for udev rules but I think you will have success now
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
in fact I think using 3.0 usb is quite dangerous
i didnt go back to ubuntu, i just used KFU again, and just tried doing normal boot. and it worked. its back up and working. ill try rooting it again now, being more careful this time, sorry for the waste of time, but thanks to soupmagnet for helping. now that its back to stock, i do stil lwant to root it, and now with ubuntu installed, what is the best noob friendly guide to use to just get the basic things up and running.
yayyy Im glad you got it goin check allow installation from unknown sources under device and install twrp first then fff bootloader no need to root flash a rom and gapps once your familiar all roms are rooted
You can select these options in kfu watch the dialogue on the screen you can see the files downloading and getting pushed to your kindle just make sure your connected to the net I suggest running one of the options without your device plugged in first do a reboot on your computer plug your kindle in check for adb online boot status normal and go for it
---------- Post added at 11:38 PM ---------- Previous post was at 11:23 PM ----------
or go this route http://forum.xda-developers.com/showthread.php?p=24129239
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
So lately I've been having more and more issues with my Lumia 640, such as random reboots, data switching, and slow downs. I decided that since I haven't preformed a hard reset since about 2 builds ago, it was time for it. I went ahead and reset, and everything appeared to be working better. It was when I plugged my phone into the laptop to dev unlock and deploy tools that I ran into trouble. As soon as I plug it in, I get the device connected sound followed by USB Device Not Recognized error, a Phone charging slowly message on the phone, and then a device unplugged sound from the laptop. I tried it on my desktop and get the exact same results. Both my computers are running Windows 10, and my 640 is on latest 10586 build.
I've tried everything I could think of/find online including
-Soft reset the device while plugged
-Using different Usb cable
-Uninstalling the device (read below)
-Rebooting the PC and letting it turn the phone on with it
-Uninstall all Usb Root Hubs
Unplug PC power cord/battery and Usb devices and wait 10-15min
-Developer Mode on/off
-Hard Reset phone again
I really don't know what else to do. When I plug it in and get the not recognized error, it's a Descriptor Request Failed, and then the device disconnects. In Device Manager it shows under Universal Serial Bus (as an Unknown device with the Descriptor Request Failed next to it) until it disconnects itself, then it disappears. Using Show Hidden Devices and a command to enable showing every device ever connected (plugged in or not), I see it show but it's greyed out and it's properties page says it's disconnected. While showing all hidden devices, I uninstalled the phone under Portable Devices as it used to work, along with my wife's phone.
Nothing I've done has gotten me anywhere. It just connects with the error and immediately disconnects. It used to work with both the laptop and desktop before I hard reset. The only thing i believe could be causing it was the fact that before the reset my phone was being faked as a Lumia 1520. But I've uninstalled that in the hidden devices of Device Manger.
Any help would be greatly appreciated. As it stands, I can't developer unlock, deploy tools, or even copy my pictures!
Edit- just tried plugging it into 2 other computers with WinXP (. I know it's not supported), and also get the device not recognized and charging slowly. So... Either the firmware/os git messed up, or the Usb jack is messed up.
I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/
Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.
OP, you have interopunlocked phone with FS acces?
augustinionut said:
OP, you have interopunlocked phone with FS acces?
Click to expand...
Click to collapse
as a matter of fact yes, to both!
anubis23 said:
Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.
Click to expand...
Click to collapse
charging is perfectly fine. I also suspected the Usb port, but after an online chat with Cricket Support, they assured me it was a software issue.
animesh_shah said:
I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/
Click to expand...
Click to collapse
the thing is, I couldn't even restore to 8.1 with my issue. The phone would not stay connected long enough to be identified by the OS let alone the Recovery Tool.
However, I have good news. I did finally solve the problem. When I had realized that connecting the phone while in the boot loader got it to detect and install as Lumia BootMgr, I opened up the Recovery Tool and sure enough it was detected. I let it start downloading the ROM, and about 1/2 way through I heard the device disconnected sound and thought oh great this isn't going to work either. However, the download kept going, and when it finished I clicked the start install button, but it gave an error saying the device was not detected. So with the phone still plugged in, I preformed a soft reset and continued holding Volume down to boot back into the boot loader. When I came to the ! screen and the phone was detected again as Lumia BootMgr, I clicked Retry in the Recovery Tool and it actually copied over the ROM, which thankfully is a very quick process.
Once 8.1 had finished setting up the phone was detected and installed perfectly on the computer. Last night I updated back to W10 and it's still detecting without an issue. I'm for sure not enabling the Full Filesystem Access hack again. Before this problem started I was already tired of waiting up to 30 minutes at a time for it to connect. Only reason I did it was to copy the custom HOSTS mod file to block ads, which I'd love to do again, but it's just not worth it.
So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila
augustinionut said:
So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila
Click to expand...
Click to collapse
Are you referring to the problem I was having? If you are, then reread my OP. You'll see that Device Manager would not even display the phone because the phone would immediately disconnect after the USB Device Not Recognized error popped up. There was simply nothing to disable, or enable for that matter.
If your saying to disable and enable AFTER applying the FS access hack to affect the detection time, then please, elaborate on that.
Erase driver, reinstall driver, try with another pc, sell the phone....
@x_orange90_x
http://forum.xda-developers.com/win...de-filesystem-access-sftp-windows-10-t3185766
augustinionut said:
Erase driver, reinstall driver, try with another pc, sell the phone....
Click to expand...
Click to collapse
you obviously did not reread the OP.. I tried all of those with the exception of the last with no sucess.
And I think you've missed my point entirely.. I solved the issue already. Hopefully the other member that posted in here with the same problem can fix it by following what I did.
You right.. disable full fs access....
You still active Mr. Orange