Windows 10 driver installation issue on my Oneplus 3 - OnePlus 3 Questions & Answers

I have a Oneplus 3, and after I updated my laptop's Windows 10 to the new Anniversary Update (I'm not sure what's the reason, so I mentioned this, just in case), it fails to recognize the MTP option when I connect the phone to my laptop. Although, it is able to recognize the phone in P2P (Photo Transfer) mode and wholly recognizable on my Ubuntu on the same laptop and other Windows laptops/PCs apart from mine.
I tried updating the driver software from the Device Manager but it shows the following error:
Code:
Windows found driver software for your device but encountered an error while attempting
to install it.
[MTP Device Symbol]
A service installation section in this INF is invalid.
Thank You

When clicking on the "Driver update" find Android device, and MTP. There should be 2 options. Select an option, and if it isn't working, select the other. Hope i helped

Related

Windows unable to recognize the HTC evo device

Hello,
Android phone: HTC Sprint EVO 4g
Connected to PC by USB cable
PC OS :Win XP
Last update of android sdk : very recent (today). up to date updates
On command line if I type adb devices:
adb devices
it shows "List of devices empty".
Did the following resolutions but nothing worked.
Cleared the windows registers under devices/controls
Cleared driver from system32
Tried to reinstall the driver again, It shows the following message on
the screen
"Cannot Install the hardware because wizard cannot find the necessary
software"
I specified the windows USB driver directory manually..It shows the
same message again.
Checked the contents of the <sdk> usb directory..i can see one. inf
file and two .cat files
So, please suggest me what to do to fix this. I have spent my whole
day and frustrated.
Why simple things are so complex on android.
Please help me with suggestions.
Thanks,
Arjun.

How to regain mtp access for usb file transfers

Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
This guide can be helpful. It clears out 'ghosts' of past device connections.
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
Also Wugs toolkit has a really good guide to cleaning out drivers. Then stop short of installing drivers. Then Windows should auto configure MTP drivers when You plug in the device.
I also make sure that I have deleted any drivers in uninstall programs in the Windows control panel.
Its a lot of steps, but it can save time over try this, try that. It returns your computer to like an Android device had never been plugged in before. Now any routine to install drivers (after the device is recognized as an MTP device) should go smoothly.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
My Device Manager shows NO Nexus devices of ADB interfaces, so I'm stumped at step 1.

Unknown USB device (failed request for device descriptor)

I have a problem.
My screen is broken. Now I want to send him to OnePlus.
But before that I want unroot it. Or at least reset to factory defaults. But both things fails.
I have the latest FreedomOS Rom. Since then I can no longer use TWRP. When I start my phone to the recovery the screen goes black and nothing happens anymore.
The same happens when I put it back to factory settings through the settings menu .
I've read there is a modified version of TWRP.
From here begins the real problem. Windows doesn't recognizes my phone.
In Device Manager it appear as "unknown USB device (failed request for device descriptor)"
What I've tried:
Boot in to Bootloader
Original (Dash) USB cable
Other USB cable
WIndows 10
Windows 7
USB debugging on
USB debugging off
OEM unlocking on
OEM unlocking off
USB configuration: File transfer
USB configuration: MTP
USB Configuration: Charge
Anyone have an idea?
Maybe it's the ROM. But I cannot flash another ROM because I can not get into TWRP.
Maybe it's an option to flash the modified TWRP without a computer. So right from the bootloader. But I do not know if this is possible. And how it should be done
I'm having the exact same problem. Did you find a solution?
In windows 10 -> i get Device Descriptor Request Failed
In windows 7 -> Unknown Usb Device (Installed Correctly)
whenever i try to update device driver with ANY driver (oneplus... or generic sdk driver) I get a message saying "doesn't contain a suitable driver for your device.....)
I went to device manager > right click mtp (unknown device) > update driver software > browse my computer > let me pick > mtp USB device > happy me
Windows it's the problem. I reinstalled drivers, adb, nothing. At work i try it & it works. I reinstalled windows. Now works.
I'm on windows 10 x64.
Damn it, I don't think windows is my problem.. i tried Windows 10 / Windows 7(2 diff computers)
i can't even see the phone as MTP..
Found any solution to this? Having a similar issue
THREAD CLOSED! If interestend in this subject, please continue here: https://forum.xda-developers.com/oneplus-3/help/usb-device-recognized-t3722279

USB Device Not Recognized - Win10

tl;dr: Boot your Moto in Fastboot mode with USB connected to PC for it to recognize the device, then reboot normally.
For those with issues with their PC recognizing the device, in my case Verizon's Droid variant. I racked my brain all weekend and tried multiple different cables and PCs in order to push some ADB commands and transfer files with nothing seeming to get the PCs to recognize the phone. I just now rebooted into Fastboot mode and the PC now recognizes the phone, both in Fastboot and under normal boot. Hope this helps anyone with a similar problem. Cheers!
I have tried this method and still the PC does not see the Phone in File Transfer mode but will see it in Photo transfer.
Help, I have the Moto 6.4 drivers installed, when I check device Manger on the PC i see "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"
If I try to force a driver update I am told the "INF" is invalid. Any suggestions are welcome, this has me scratching me head and is driving me nuts.
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
BOOM, Thank you worked like a charm... after trying every other way I could think of was driving me nuts.
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
-- snip --
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
Thanks so much! Was having same issue as OP but with Win 7 and Moto Z2 Force. Even with the Motorola Device Manager app installed, I the device kept showing up as "unknown" in Windows Device Manager.
I've updated your steps to include one you left out (in bold):
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select Mobile Device
Then select MTP USB Device
THen NEXT NEXT BOOM​

Question LE2125 Driver issue

I'm trying to restore my Oneplus 9 Pro to factory defaults. I downloaded the latest stock OOS Img from the oneplus site and then followed the direction in this thread (https://forum.xda-developers.com/t/restore-oneplus-9-to-stock-via-fastboot-commands.4265153/) to extract the payload.bin file.
I have all the img files and I tried using the powershell script in the link posted above to flash all the imgs. It seems to get through everything, up to the point where it tries to flash the flashbootd partition. When it gets to that part, I get a bunch of errors stating that it can't write to it.
When I look at device manager in Windows, I see the "LE2125" device with a exclamation mark. The hardware ID for that device is:
USB\VID_18D1&PID_4EE0&REV_0504
USB\VID_18D1&PID_4EE0
I can't seem to find any compatible drivers that work for this. It works fine when I'm plugged in and at the booloader, and also in Windows, but when I go into fastbootd, it doesn't seem to recognize. I tried connecting to USB and USB-C connectors (I have an adapter that allows me to also plug into USB)
Anyway, I'm posting this because I can't seem to find much information about the driver or hardware ID, and I'm sure I'm not the first person with this issue. Any assistance is appreciated. Maybe I'm doing something wrong.
I had the issue in fastboot mode yesterday (with win11), I solved it by installing the Oneplus driver, loading windows "disabling driver signature enforcement" mode.
Thank you that did work for me, although I have to add that simpy installing the oneplus driver wasn't enough for me. I had to manually go into device manager right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.

Categories

Resources