Develop Bugs

[Q] Bricked Kindle

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

"Hardware ID doesn't match" error when plugging phone in

Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.

You may not want to try this either but try a system restore
Sent from my SPH-L710...if some one helps you press the thanks button

Volknochi said:
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
Click to expand...
Click to collapse
I had the same issue what ended up fixing it for me was watching when I plugged the phone in after a clean driver install and stopping Windows from downloading and installing an updated driver. Dont know if its the same for you but that fixed it for me. I was really frustrated by it and found no help either.

probably an easy fix
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.

I won't do a system restore, that won't do anything. Not to mention it would erase some programs that were installed (not related to phone). So, not doing that. Also, my computer will not automatically update any drivers or any thing else, as I have it set to manual mode.
And, I do not have Kies installed. It never worked for me properly, when it came to driver installation. I've done the "go into device manager" bit many times before, it still likes to play the "Hardware ID doesn't match" card. Drivers won't install either. I don't know what it is, but damn this is the most stubborn thing I've ever encountered.

i've post this in other forums today. what i do to get it working is i toggle USB debugging and try it out, then start toggling the ptp and mtp until it works. the combo that works for me is turn on debug, plug in computer, unplug, turn off debug, plug in. if it doesnt work then i toggle back and forth MTP and PTP. 5 tries at most, for me. Also, i did a nandroid back to my oem ICS that was 2 weeks old and just rooted. the problem is worse there. i'm using freegsmr6 with trinity kernel on Tmo. hope it helps.

Ditto
Yeah that whole "Hardware ID missing" was an irritating situation. This is what I recommend as far as making it work.
1. Plug in.
2. When you get the error message, I think its because of a conflict with the ADB interface. Go to Settings, Developer Options, and check off USB Debugging.
3. Plug in once again and it should work. If not, try toggling between Camera and MTP.
I have Windows 7 Ultimate and it works fine for me

I always get that error as well with my SGS 3. I have to reinstall Kies everytime it does that which is annoying.. ANyone has a permanent solution about this?

Fix for me was...
1-plug in phone. Get the hardware ID message. Leave phone plugged in.
2- open device manager. Click on. Android Phone and Uninstall Samsung Android ADB Interface. Also check the "delete software driver" when the dialog box shows.
3-still in device manager. Scroll down to Universal Serial Bus Controllers. Uninstall Samsung Mobile USB Composite Device.
4-unplug phone.
5-reboot pc.
6-install SAMSUNG USB drivers from their site or from here
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
7-reboot or not. Plug in phone.
This worked for me and no issues for the last 6 days. YMMV..

this works!
stevounit said:
yeah that whole "hardware id missing" was an irritating situation. This is what i recommend as far as making it work.
1. Plug in.
2. When you get the error message, i think its because of a conflict with the adb interface. Go to settings, developer options, and check off usb debugging.
3. Plug in once again and it should work. If not, try toggling between camera and mtp.
I have windows 7 ultimate and it works fine for me :d
Click to expand...
Click to collapse

But why this problem now out of nowhere when everything worked fine before.
Sent from my SPH-L710 using xda app-developers app

Hardware ID missing - SOLVED!!
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
UPDATE!! (Oct.11.2012)
After a few Kies updates and going through various ROM's:
- the procedure listed above works 100% but a few steps are just not needed (redundant) - see bellow
- the problem is mostly caused by Windows "forcefully" trying to install its own drivers, rather than allowing Samsung's suggested.
- Samsung's fault is providing "updated" drivers that don't always work (hence, use the suggested 1.4.6.0 drivers)
- Following EVERY Kies update, DISCONNECT from internet before plugging your phone (otherwise you'll have to go through this, AGAIN).
Some suggested here that plugging the phone into a different USB port (without disconnecting from internet) would be the culprit - which happens to be true, but as a mere effect, not the cause: every time an unknown device is plugged into a different USB port, Windows is trying to download/install the appropriate drivers if it doesn't recognize the hardware - and there you are again.
So, the simplified procedure becomes:
1. Not needed - leave Kies installed, as is - no harm at all
2. N/A
3. YES
4. Not (always) required
5. MUST
6. MUST
7. MUST
8. Yes
Furthermore, if still interested in connecting your I747(M) as UMS (USB mass storage) the solution presented here works. I tested it myself - read my comment on this post for the very few existing hiccups.
- while installing the USB mass storage device drivers you don't have to disconnect from the internet

Install Drivers
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.

tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
For someone experiencing the "hardware ID missing" error, just reinstalling the drivers won't do anything. Like many others, I've been banging my head trying to solve this for quite some time; the suggested steps are truly a compilation of successful ideas and trials mingled with tons of frustration, coming from my own experience as well as from many different people and forums.
If, on the other hand, you had a different type of connectivity issues - without this error, then, yes, reinstalling the drivers is Samsung's recommendation.

billard412 said:
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
Click to expand...
Click to collapse
Just wanted to say thank you. Did this and the last 2 days, works everytime. I made sure that after the first time I plugged the phone in after doing all this, and the screen pops up asking what I wanted to do, made sure to check the box for "do this everytime" and then choose the view folder option or whatever that is.
Thank you again,
Whiteice

One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.

nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thank you so much for this. This solution worked for me.

nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thanks for this i will try it tomorrow as still new to these tabs.
For moment i change to camera PTP and it pops up, so at least i can use it for now.
Will let you know how i get on.
Best wishes :good:

adamspud said:
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
Click to expand...
Click to collapse
The Android Developers toolkit DOES install the USB drivers 1.4.6.0 - which seems to be the ONLY one that works, BUT the rest of the steps suggested in my previous post are needed in order to get rid of the problem - otherwise the fix is just temporary.

Re-loading OS drivers corrected issue.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
I removed the updates to Kies on my Note and uninstalled the Kies update on the PC which is what started this issue of the OS not recognizing the device and then a fresh driver load for my phone from the Samsung site. Worked Perfectly, Thanks!
Cowoholy

[Q] Phone no longer gets recognized as USB storage on PC

I've tried this on both my work PC and my home PC. When I plug the phone in, it makes the familiar connection sound and will start to charge but the computer doesn't ask me if I want to open it up for USB browsing. This is recent and there have been no firmware changes. I've rebooted the computers and the phone but nothing seems to matter. Has anyone else encountered this issue?

do you have developer options (in settings) on or off? Has the usb cable been roughly removed from the phone lately. it may be damaged?

developer options are off, I've also tried several cables

Are you rooted and on a custom Rom?
The Thanks button is just to avoid "THANKS" posts in threads. Don't defeat the purpose of why it was introduced.

IM having the same problem.I got the phone on monday and it wont mount as ubs.

jordan2333 said:
IM having the same problem.I got the phone on monday and it wont mount as ubs.
Click to expand...
Click to collapse
It doesn't mount as a USB drive, it mounts as a media device because it uses MTP. That's not an issue with the phone, it has to do with how Samsung set it up.
The Thanks button is just to avoid "THANKS" posts in threads. Don't defeat the purpose of why it was introduced.

that makes sense now but i cant not transfer any files to the card or the phone.

jordan2333 said:
that makes sense now but i cant not transfer any files to the card or the phone.
Click to expand...
Click to collapse
Did you install the SG3 drivers? If not go here and download and install the usb drivers..

jordan2333 said:
that makes sense now but i cant not transfer any files to the card or the phone.
Click to expand...
Click to collapse
Do what the poster above me said, then make sure to unlock your phone after plugging it in or else your files won't show up
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

Its the same thing i can't transfer files to the phone or the external card.I don't get it i never had a problem with my galaxy 2.I've uninstalled the drives installed them again and used different cables.

i have the same problem too. my phone nolonger shows up as a storage device on my pc. i have developer options on and usb debugging checked. ive tried different cables , different computer , tried rebooting phone, tried reinstalling the drivers too .. nothing seems to fix this issue... earlier today it was working fine .. when i plug it in it pops up samsung modem and thats it.. please help

This is very strange, as a work around you can use Wireless Transfer. I've used this as my main method since my OG Epic.

same issue trying the fixes mentioned. after reinstalling the driver i get about 3 files transferred then it pops up with that error....WTH is goin on i have several gigs of books and music how am i supposed to get them off?
---------- Post added at 07:10 PM ---------- Previous post was at 06:50 PM ----------
THis is complete crap! why is this goin on?! I can get my pc to recognize the device i can browse directories but it suddenly tries to decide when to quit when i try to transfer files. I can only get about 5 folders moved before it thinks thats all and just stops it no longer comes up with the device not functioning error message anymore.......please somebody help. I dont have a large enough sd card to just transfer. Ive searched on google and there are not actually explanation only that you cant mount the internal storage as mass storage.....samsung is going the way of HTC for me. Stupid oversights renders the device a complete waste to me. !!!!!!!!!!!!!!!!
---------- Post added at 07:20 PM ---------- Previous post was at 07:10 PM ----------
Ok last one. I was considering getting the note 8.0, is this something that all of their devices are gonna suffer from?

I'm not going to pretend to know what's wrong with your device, as I have 2 Galaxy S3 and a Gnex and 2 Epics which all connect just fine and I can transfer any and all files from the desktop or laptop no issues.
But I will suggest maybe you set up a drop box and you can share all those files from your phone to computer or visa versa.
Sent from the future via Tapatalk 4

well after a couple deep breaths i went ahead and did that after posting those. I still cant locate a reason why it would come up with that error. There are a couple posts in another forum talking about it being win7 related and not the device it self. Ive tested other cables, rebooted pc/device, checked/reinstalled drivers, and nothing come up out of the ordinary. I hope someone locates the issues, just for having an answer to this headache. thx

An answer-
For those who are having issues insure that your device is on a Stock TouchWiz ROM.
MAKE SURE DEVICE IS UNPLUGGED THIS ENTIRE PROCESS.
1.
= Go to the Dialpad.
= Enter this code ##3424#
= Menu will pop up click Qualcomm USB Settings.
= Click the 2nd Option MTP+ADB
= Press Save
Done
2.
= On your computer go to Control Panel Click Category for the viewing style.
= You will see Uninstall A Program. Click that and go to S- Uninstall Everything Samsung.
= Plug your device back in and let default drivers install takes average 45-60 seconds.
= Device detected as MTP. You may now transfer files.
Done
Let me know if this worked for you.

Ok i tried that and when i plugged the phone back in to install the drivers,they all installed except the CDC serial it says no driver found.I need help please.

do you have any other phone drivers installed on your PC?

jordan2333 said:
Ok i tried that and when i plugged the phone back in to install the drivers,they all installed except the CDC serial it says no driver found.I need help please.
Click to expand...
Click to collapse
As you said, the CDC serial (Unknown Device) popped up. Unplug your device and install drivers.
http://www.samsung.com/us/support/owners/product/SPH-D710
Click "Download" tab at the bottom and press the "EXE" button to download.
-Plug your phone back in afterwards and keep "Device Manager" open you will see the CDC Device disappear.
-When its installing I recommend keeping the "Installing Drivers" window open to see when everything is finished.
-After that's done switch phone to PTP via the notification menu. Let it load drivers and it will install as a camera.
-Switch back and MTP should be working.
Let me know how it goes.

jaysoblitzed said:
As you said, the CDC serial (Unknown Device) popped up. Unplug your device and install drivers.
http://www.samsung.com/us/support/owners/product/SPH-D710
Click "Download" tab at the bottom and press the "EXE" button to download.
-Plug your phone back in afterwards and keep "Device Manager" open you will see the CDC Device disappear.
-When its installing I recommend keeping the "Installing Drivers" window open to see when everything is finished.
-After that's done switch phone to PTP via the notification menu. Let it load drivers and it will install as a camera.
-Switch back and MTP should be working.
Let me know how it goes.
Click to expand...
Click to collapse
Well it finally worked.Thank you so much did what you said and i can transfer files over to the card and phone.Again thanks for your help.I never had trouble with with the original epic and epic touch.

usb data not working after september update

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!

I Guess I Discovered a New Form of Hard Bricking on my Device???

I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.

jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.

Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?

Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.

Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯

I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.

have we even seen a bricked device yet?

twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.

have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image

Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury

What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.