Related
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
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
SenorSmartyPants said:
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
Click to expand...
Click to collapse
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging and no check in protect usb storage
Click to expand...
Click to collapse
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Many thanks.
I think I will do a full wipe (was just doing the cache/dalvik after the first install) to make sure nothing else is screwy
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Click to expand...
Click to collapse
no prob
SenorSmartyPants said:
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Click to expand...
Click to collapse
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
SenorSmartyPants said:
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
Click to expand...
Click to collapse
i have the same issue on mine, using twa builds
also, sometimes when i plug in the usb cable it makes the kindle run extremely slow and laggish, requiring a reboot.
*Bump*
Does only detecting usb connected once per reboot only happen to the two of us in this thread? CM10 works pretty well for me, but this is a bit of an annoyance. I have a work around, reboot, but still...
I have the same issue. In fact, I can't get USB storage to work after installing CM10 8/24.
But I think the issue has to do with multiple Android USB drives being installed in Win7. I have a TF201 and Xoom and when I plug in the KF, USB reports the TF201 being connected. Of course Win7 does not show KF in Desktop Explorer. The only way I can download a new ROM to my KF is via my NAS which I connect via ES File Manager....
Can anyone confirm that having multiple Android devices causes this USB confusion?
You have to specifically enable USB storage before it will mount.
Unable to root! Stucked on TWRPP 2.2.0 Screen with several options
Hello!
I've tried to root my Kindle Fire, following the same steps that most of the users have followed (Using KFU 0.9.6).
Unfortunately, while installing the root (I guess) once it installs TWRPP, it inmediately boots up to the TWRPP screen with several options ( Install, Backup, Restore...) and the KFU software keeps a message that says Please wait.
Does anyone know how to fix this and finish the rooting of the device?
Thanks in advanced.
jjosue17
soupmagnet said:
You have to specifically enable USB storage before it will mount.
Click to expand...
Click to collapse
I have enabled but it still will not mount for some reason. I had a forced reboot issue appear as well.
try the previous build see if that doesnt solve your problem you must have usb debugging enabled and then tap on the icon in your status bar to transfer files...
I've been limping along just using the work around of rebooting while plugged in to get usb mounting to work.
But today I had KF mount to my PC, deleted the ADB drivers in windows from the device manager. Did a factory wipe on the tablet (even wiped the SD card), I'm running the latest TWA rom 8/28. I still can only get usb to detect if I reboot while connected to a pc. A couple little differences; after the wipe ADB was turned off on the ROM, I left it that way to see what happens. It does still mount (only after reboot, did I mention that ) but now it shows up under "Portable Devices" in device manager and the Device ID string is different in some apps (on PC) "Amazon Kindle Fire" instead of "Kindle Fire" which is what it was before today.
What else can I try? Do I need to do a super duper wipe? Factory, reinstall ROM, cache/dalvik? Do I need to purge even usb android driver on my system? (And how would I do that?)
Thanks for any help. I would love to get rid of this issue and just be able to plug in the KF and not worry about rebooting all the time.
Funny thing is I worked with someone the other day and when he mounted nothing would come up..... Reinstalled his adb drivers from kfu and it worked like a champ... Dont really know why... This is what I would try instead of messing with windows try creating a live usb as a formidable test to see if its simply just windows stupid drivers that are killing you... Create it with persistent and use this script to set up the drivers http://forum.xda-developers.com/showthread.php?t=1850038 very good chance it will work then you will know its a driver problem...
I'll see if I can give the Live USB thing a try if KFU driver reinstall doesn't help.
But I have a laptop that I never messed with the drivers on. With stock usb was always detected, after rooting and rom installed, had the same usb detection problems as my desktop.
Well I never did give the Live linux USB thing a try. I just keep going with my work around of rebooting with the usb connected and then doing my file transfers. I would only do this about once a week. I even noticed that with a couple of the more recent builds if I would plug KF in several times it would detect usb and I would not have to reboot.
But now with the last build (or two?) not exactly sure when it changed even that isn't working. Plugging in several times never detects usb now (95%+ detects usb charging though). And now it also won't detect usb after reboot while the cable is plugged in during the reboot. So I've had to do my file transfers in recovery mode. Recovery mode always works. What is different about what recovery mode "says" to the computer compared to what the full ROM "says"
Oh, and I only get USB 1.1 transfer speeds. But I think I read that this is a kernel driver issue that is well known, or has that been fixed somewhere?
Thanks
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
Okay so before anyone says this has been solved before it hasn't, I have scoured the internet left and right and I have not found any way to fix this problem. Also just as a pre FYI it's not just the LG G3, it's also happening with my work provided Samsung Galaxy S5 and my girlfriend's S7.
So here we go, no matter what I have tried or pulled off, I cannot get my new (old) laptop to recognize any device I plug into any of its 5 USB ports (3 USB 3.0, 2 USB 2.0, 1 USB 3.0 enabled with Super Charger), now as for the details, the laptop has windows 10 installed and to be more specific it's an msi gt70 0nc, so it's a higher end gaming laptop and I have tried everything and it just won't connect to any phone I plug into it.
And before anyone says if I've tried another laptop I have, to be specific I've plugged both phones into my lady's HP Envy with Windows 10 and both were recognized just fine.
If anyone is wondering here are the measures I've taken:
Installed LG United Mobile Driver (almost every version available)
Installed LG Mobile Driver (once again, every version available)
Installed LG PC Suite (Doesn't detect phone)
Tried switching phone between USB debugging and MTP PTP And Charge Only and every combination in between.
Have tried uninstalling and reinstalling Windows Media Player as it carries the MTP protocols.
Have tried installing the Media Feature Pack for windows 10 N and KN off of the Microsoft website
Have tried uninstalling the drivers manually and forcing an update on the drivers with no avail.
Have tried messing with the BIOS USB Settings on the laptop.
Disabled driver signature enforcement
Tried Safe Mode on both Laptop and Phones
Installed the Universal Google Driver
Installed ADB and fastboot (ADB doesn't detect the phone)
Installed KIES to try the Samsung (Doesn't detect phone)
Tried forcing generic MTP inf files
I'm honestly insanely frustrated and all I want is for this device to show up in my computer so I can install some roms and tinker. I've been trying all I could for the past 24 hours (Lost sleep) with no avail. Nothing seems to be wrong with the USB Ports as I have a Logitech unifying receiver plugged in for a mouse and it works, it just seems like this laptop doesn't like Android devices.
Going to device manager and forcing an update does nothing, the device sometimes shows up as "Unknown Device", sometimes shows up as "LGE Android Net MTP Device" and sometimes as "LGE Android Mtp Device", forcing the update yields the result "The driver installation file for this device is missing a necessary entry, This may be because the INF was written for Windows 95 or later. Contact your hardware vendor" This happens with both the LG and the Samsung. Any help would be appreciated. If anyone needs any more information or logs don't hesitate to ask.
Sure hope you find a solution and post it. I have EXACTLY the same issue. The last paragraph of your description is identical to the error message I am getting.
---------- Post added at 10:41 PM ---------- Previous post was at 09:52 PM ----------
Wow. All I did was uninstall and reinstall Media Player 11 and it started working. No driver error and computer detects phone now.
USB cable only charges the phone when connected to computer. Tried the following
1. Using 2 different cables which previously worked for data but phone only shows charging.
2. Using pc and Mac and both does not see phone. Looked in device manager of windows but it nothing shows up. Both computer previously used for data transfer on this phone
3. Looking inside usb-c port but no lint or dirt. Although just before update to September security patch my phone has some water on the screen which I wiped off. And the phone does not show sign of problem other than no data transfer to computer
4. Factory reset phone and same thing
5. No notification shown for changing charging only to file transfer
6. Computer doesn't Bing when connected.
What else can I try? Anyone can help or confirm if their usb-c works after September update so I can narrow down to hard ware problem.
Anyone diagnosed this hardware problem before?
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
jd1639 said:
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
Click to expand...
Click to collapse
I tried changing the options to MTP, PTP, midi, charge only, etc but non of them make any difference to the computer, nothing pops up and does not show as new item connected in device manager
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
jd1639 said:
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
Click to expand...
Click to collapse
Tried changing when USB connected and when not. Doesn't seem to make a difference.
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
jd1639 said:
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
Click to expand...
Click to collapse
I don't know how I can flash a previous firmware if I don't have USB access.. it's really frustrating. Looking from ifixit. It does not seem there is any chip near usb-c other than voltage control.
Can't seem to find how I can look at logs to know if USB has been engaged or if there is any error message. It's all dead end and my phone seem to be the unique case.
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
jd1639 said:
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Click to expand...
Click to collapse
USB worked fine, I am using it for Android studio, and transfered music across as well. Looked at the post and it seemed that has to do with device manager. Problem is mine does not show up any changes to device manager. I.e . No ADB or other device. Seemed like no data is exchanged and windows treating it like a battery or something
Any fix for this?
I've hit the same issue and wondering if anybody has a fix for this yet?
I'm using linux and seeing no usb activity at all from my nexus 5x after sep 17 update.
I've tried multiple cables. Cleaned the usb port on the phone. Multiple PCs.
I've connected to the phone using adb over tcpip and seeing nothing in logcat except battery logs when the usb cable is plugged in and out.
Turned usb debugging off and on.
I've set usb mode in developer options to mtp (it was on 'charging') and restarted the phone. Then find the option is forced back to 'charging.'
Logcat entries during boot show no failures in regards to usb connectivity.
Charging works fine but no data connectivity via usb at all.
Anyone got any other ideas?
Hello world.
I had the same issue.
To solve the problem :
- unlock developer mode
- switch on debug usb
regards
J.
I had this problem too- did not have to enable USB debugging though, just enabling the developer options fixed it for me. Which is odd because I definitely had them enabled previously... I guess a recent update reset that and for some reason all the USB data options are tied to developer mode now.
I've got 790 (american, as i know). The same issue, no response from service, guarantee, doesn't help, pc shows it as unknown device. some other bugs, mobile data fails, no sim detected after a few seconds, violet camera with no focus, but nice when the distance ia ok, so matrix works ok, but no stabilisation.
Then, bad battery, it seems that the bank ia ok, but controller works bad. it charges enough time to think that the capacity is not degraded. I suppose that usb controller (pc connection and fsat discharging) are nearby problems.
None of the above posts worked for me on my N5x (8.1.0 March), but searched some more and found this to work for me:
https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY
Hello everyone. I'm just resurrecting this old thread so I can provide the solutions I have found to this problem. It appears this symptom has multiple causes, and there are different solutions depending on the cause. I have seen this problem twice now on my Nexus 5x (stock, no custom ROM) and solved it both times.
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
2. SOLUTION #2 - ClockworldMod USB Driver was installed. Replace with Google driver
The second time I encountered this issue, the Solution #1 above did not work. Surprisingly, the adb devices command successfully detected the Nexus 5x. It's just that the phone wasn't showing up in the Windows 10 File Explorer interface.
The root cause of this problem was that I had installed the ClockWorldMod USB Driver because I was playing around with their Vysor App (on a different phone.)
BTW, I think the Vysor tool is really nifty for screen mirroring purposes!
To resolve the problem, I replaced the ClockWorldMod driver with the regular Google USB Driver.
(Sorry, XDA is not letting me post links because of my low post count. The link is:
h++ps://developer.android.com/studio/run/oem-usb.html )
The procedure is:
- Download the Google USB Driver from the link above and extract the ZIP.
- Enter the Windows Device manager
- Find 'Android ADB Composite Interface'
- Open the properties of 'Android ADB Composite Interface' and you will see it is from ClockWorldMod.
- Right click on this Interface and Select 'Update Driver'
- Click on 'Browse My Computer for Driver Software'
- Click on 'Let me pick from a list of available drivers on my computer'
- Click on 'Have Disk'
- Browse to the Google USB Driver you downloaded.
- Select that driver and load it on top of the ClockWorldMod driver. (Windows may claim that you've got the best driver already installed, but ignore that.)
After re-installing the Google driver, the Nexus 5x appeared immediately in the Windows 10 interface for file transfers.
Cheers, I hope this helps someone out!
I have the same problem with LineageOS 15.1, I am not sure since when, because I don't use USB that often, but I it must have been after the second update for 15.1. ADB and FASTBOOT don't work.
None of the suggested methods work. I am on Linux, but I also tested the USB driver solution on a windows PC.
The problem is, my phone does not trigger any response from the system I connect it to.
On Linux an lsusb/dmesg shows nothing, and on windows it doesn't make the classic "ding" when I connect something to the USB port.
It is like my phone isn't even there.
In the developer options under networking and USB, USB was set to charging only. I changed that to MTP, but it didn't help.
Now I can't change it back (not that I want to, but just saying). No matter what I press on this menu, it always stays on MTP.
I am here because of adb not connecting tho, MTP is not my concern anyways.
I am not sure what to do, format data, and wipe system etc. and go for a clean install? The problem is, when I boot into recovery, ADB and FASTBOOT don't work either, i.e. my computers don't see an USB connection. So will a wipe even help? I am scared I wipe my phone, and then I can't connect via ADB in TWRP.
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
tantalfr said:
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
Click to expand...
Click to collapse
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
ufopaper said:
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
Click to expand...
Click to collapse
Never underestimate the power of a toothbrush
Bamboo-Toolkit said:
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
Click to expand...
Click to collapse
Amazing, this solved my problem. Thanks!