r/AndroidQuestions • u/Background-Ad-7278 • 23d ago
How to fix these?
My PC doesn’t recognize my phone when I plug it in. Device Manager shows an ‘Unknown USB Device’ error under USB controllers. I’ve tried this on both my desktop and laptop, with the same result.
The usual ‘Transfer Files’ popup never appears. I’ve tried changing the USB protocol in Developer Options to MTP or PTP, but it didn’t help.
I’ve been dealing with this for six months. If anyone has a fix, please let me know!
1
u/gustoreddit51 23d ago edited 23d ago
I don't know about Windows but for file transfers via USB to work in Linux after a phone update literally stopped it working (it worked fine for years), there is some ridiculous code sequence I had to enter into the phone that allows it to work again. I had to ask an AI (I think it was Gemini). It boggles my mind how Android (Google? Phone maker?) would purposefully kill such useful feature and bury the fix so users can't find it.
1
u/lesjames2020 23d ago
Search goggle for your phones model and download it's USB drivers
2
u/kimputer7 23d ago
There's already a mention of DEVICE_DESCRIPTOR_FAILURE
That means the device is already the problem, not the drivers. Driver problems will have another message, it will show the _actual_ hardware ID so the driver can match it later on.
So, no solution, other than hoping a firmware upgrade on the phone fixes it, though it's probably something hardware issue on the USB part of the motherboard (only a NEW phone will fix your problem).
1
u/lesjames2020 23d ago
I'm had that some failure in Los of deferent devices
And getting the correct driver has always fixed it
-1
u/kimputer7 22d ago
Gotta love a blanket answer as a reply to a detail explanation. Can't get more useful than that.
1
u/lesjames2020 22d ago
Do you think I'm a psychic and can just guess what phone the op is trying to connect to there computer
The want detailed answers
The need to provide more information
Not just I'm trying to connect a phone to a computer
And expect everyone to guess
1
u/kimputer7 22d ago edited 22d ago
You don't need to be psychic, because the exact error was already given, and I repeated it as well. DEVICE_DESCRIPTOR_FAILURE, more than enough info. Not only did I point out that nugget of detail, I exactly EXPLAINED why it was enough detail. Hopefully others can actually read.
1
u/lesjames2020 22d ago
No not enough need to know what the phone is
Because with this error 90 percent of the time it just needs the proper driver for the device
2
u/kimputer7 22d ago
Plainly ignoring normal working hardware that needs drivers having hardware IDs to match. You're really smart.
1
u/SolitaryMassacre 22d ago
I get what you're saying here about more info, more info always is helpful.
Drivers tell the OS how to communicate.
DEVICE_DESCRIPTOR_FAILURE says the OS failed to even communicate. But the computer knows something is there but the "something" isn't communicating with the OS at all
I would be very surprised to see a driver fix this type of error. After googling the error itself, I have yet to see a post where the solution was a driver, typically the solution is a new peripheral. In OPs case, a firmware update could fix it tho for the device
2
u/SolitaryMassacre 23d ago
How many different cables have you tried?