Hi
Just connected my OPT to my Windows 10 machine and I got the message like in the picture >> USB device not recognized.
I tried uninstalling and reinstalling drivers but it is still not recognized ("malfunctioned").
When in device manager in device status I get: "This device cannot start. (Code 10). A device which does not exist was specified."
Any ideas of what should I do
Try to disable usb debugging. And then try again
Thanks for Your suggestion, but I didn't mention that it was the first thing I tried... I did uninstall the drivers and reinstall them... and yesterday I eventually gave up... this morning it just started working on its own again, so right about now it works perfectly fine -.-'
Conclusion: give up more easily xD
Related
Hello all,
A bit strange problem. I was trying to adapt MoDaCo custom rom to my Vega from 1,09 FW. Everything was ok until ticking the USB debug mode. Until that time, the device was normal APX mode, but as I switched to USB debug mode, my PC (with Win7 x64) reconized it as "NVidia Tegra 2 USB Device" under disk drivers. So, I cannot go further steps, since windows doesn't recognise device as "android phone"
Anyway, to overcome this I tried to uninstall-reinstall but it didn't work. After every re-install, win7 recognised as same. No change.
Then I tried to change the drivers to right one but this was not possible since when I attempted to do so, the msg I got "You have already the most updated driver"... Then close.
Finally I tried to erase some "tegra2" entries from regedit. Some I could, some not but this was also dead end. Everytime the tabled was recognised as "usb device"
The important thing is I cannot go back to "APX mode" again.
Any advises about this issue?
Many thanks in advance.
The usb switcher is currently not compatible with v1.09. You can try going to software tool in settings and selecting "erase all content and settings"
I got a nexus 7 2012 wifi 32gb today, updated to 4.3, and I have had nothing but problems trying to root the thing. I have been unable to unlock the bootloader, currently whenever I'm in bootloader mode windows 7 64 bit just shows it as an "unkown device" when I look at the properties it says "Windows has stopped this device because it has reported problems. (Code 43)" I have tried "update drivers" and had it look at C:\PROGRAM FILES (X86)\WUGFRESH DEVELOPMENT\DATA\DRIVERS but it just says the drivers are up to date for my unkown device. There was actually a point where in bootloader mode windows had device manager say bootloader something instead of unkown device however it says drivers were not installed and I think the error code was 10 or something, basically it was still useless and would not recognise my device and install drivers. I have tried on my laptop which has windows 8 64 bit but it is far worse there, the computer keeps giving malfunction usb message or something over and over again as if the device is constantly connecting and disconnecting. Despite this however MTP works fine and I have transferred a music album over as a test and it was fine and the device charges fine too. Would really appreciate help as I'm desperate at this point.
Uninstall whatever out of date drivers that came with the toolkit then install the latest Android Composite ADB Interface Driver 8.0.0.0.
You also need to install this in order to use ADB while in recovery.
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Short of going back in and deleting (not just uninstalling) every USB driver, might be easier to borrow another computer?
lightlink7 said:
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Click to expand...
Click to collapse
The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for bootloader and when booted into ROM. Naked Driver 0.72 is only for when in recovery or else your computer would show "Nexus 7" under Unknown Devices in the Device Manager.
So, I cant seem to be able to connect my G2 to the PC via USB cable. I get "usb device not recognized" error, and when looking for the device via LGPC Suite, it says driver not installed and attempts to re-install the driver to no avail. Im using Win 7 64 bit. Here's what Ive done to attempt to fix it:
Tried uninstalling and reinstalling both the driver and LGPC Suite in my normal user account and in admin admin account.
Redownloaded both driver and LGPC Suite and doing the above.
Tried 3 different USB cables.
Tried 2 different USB ports.
Yes, Im changing the connection options on the phone from MTP and LG Software.
Phone charges normally over USB.
I *can* however connect to LGPC Suite via wifi successfully.
Any ideas? Im stumped.
blackangst said:
So, I cant seem to be able to connect my G2 to the PC via USB cable. I get "usb device not recognized" error, and when looking for the device via LGPC Suite, it says driver not installed and attempts to re-install the driver to no avail. Im using Win 7 64 bit. Here's what Ive done to attempt to fix it:
Tried uninstalling and reinstalling both the driver and LGPC Suite in my normal user account and in admin admin account.
Redownloaded both driver and LGPC Suite and doing the above.
Tried 3 different USB cables.
Tried 2 different USB ports.
Yes, Im changing the connection options on the phone from MTP and LG Software.
Phone charges normally over USB.
I *can* however connect to LGPC Suite via wifi successfully.
Any ideas? Im stumped.
Click to expand...
Click to collapse
Sorry for bumping old thread, but have you found a solution? I found my self in exactly same situation as you describe.
Phone is in LG Software mode
LG Suite can find the phone over Wi-fi, other modes work through USB.
Tried on two different computers, with win7/win8 respectively.
Stock EU ROM, just bought it.
Tried different USB ports.
Yet PC doesn't recognize it :/
EDIT: Never mind, solved it by following the following instructions in another thread:
cmahendra said:
You must be on 64 bit windows. Not even on 64bit, Still try this...
1) Uninstall LG Drivers, LG PC Suite and anything you see named LG. Restart PC.
2) Install latest LG Driver from this post (step 4)
3) Install Optional MTP Driver from this post (step 4)
4) Open Windows Device Manager (just to watch whats happening.)
5) Disconnect Internet (To avoid stupid online WDM drivers)
6) Connect phone with Usb and let drivers install automatically. Give it some time to install drivers keeping watch on Device Manager window.
7) Keep changing USB connect modes to all modes one-by-one on Phone and let drivers install.
You should see MTP drivers installed now. If this does not help, cant think of anything else. If this works, press THANKS button
EDIT: Connect USB at backside of pc, directly to USB on pc motherboard.
Click to expand...
Click to collapse
Hello,
today I tried to root my phone with Nexus Root Toolkit. The first step was to unlock the phone so I could root it. After I unlocked it I can't get the phone to connect to the PC. I've tried uninstalling the drivers(with USBDeview also), restarting the computer, different cables, different ports, USB debugging on/off, MPT/Camera, restoring to factory settings. Nothing works. The only time the phone registers in the Device Manager is when I put MPT with USB debugging, and I get an exclamation mark next the Nexus 4 device. Trying to update the drivers results in no drivers found. Downloading the drivers manually doesn't work either. What I find especially troubling is that when I connect the phone without USB debugging the phone doesn't even react to the connection. There is nothing in the status bar. The phone is charging tho.
edit: I've now tried 2 different computers (running Win 8.1, and 7), and it's the same problem, so I'm pretty sure the phone is the problem. Is there anything I can do from here?
Since I can't connect to the PC is there a way I can do something 'OTA' to fix it? Will I be eligible to update to 5.0 OTA since my phone is unlocked(stock ROM tho)?
edit2: I've now locked the bootloader, but the issue persists.
edit3: Uninstalled NRT, and the drivers it provides, and installed Google USB Drivers over the SDK Manager. I now have two devices: one Nexus 4, one Unknown Device, both with exclamation marks next to them. I think this double entry could be due to some remaining driver somewhere. Gonna try to remove every Nexus driver I can find, and then try with Google USB Drivers again. Fingers crossed.
edit4: Tried naked drivers. No luck...
Appreciate the input!
I just upgraded to Android Oreo via OTA. When I go to plug in the phone to my computer, it doesn't show up. In the Device Manager is has "Unknown USB Device (Device Descriptor Request Failed)".
When i swipe down, I don't even get the option to change it from Charging to PTP
Is there an updated driver that I need for the new update?
I'm running Windows 10
StormChaser83 said:
I just upgraded to Android Oreo via OTA. When I go to plug in the phone to my computer, it doesn't show up. In the Device Manager is has "Unknown USB Device (Device Descriptor Request Failed)".
When i swipe down, I don't even get the option to change it from Charging to PTP
Is there an updated driver that I need for the new update?
I'm running Windows 10
Click to expand...
Click to collapse
You can try to reset and setup the USB debugging settings and configuration in the developer options.
StormChaser83 said:
I just upgraded to Android Oreo via OTA. When I go to plug in the phone to my computer, it doesn't show up. In the Device Manager is has "Unknown USB Device (Device Descriptor Request Failed)". When i swipe down, I don't even get the option to change it from Charging to PTP Is there an updated driver that I need for the new update? I'm running Windows 10
Click to expand...
Click to collapse
No there are no new drivers to install. Try a different cable/port. If you are using USB-C to USB-C, try a USB-A cable. As mentioned revoking/enabling USB debugging might help. If you are unlocked you can install TWRP and use MTP to take off any files you need before factory resetting.
None of this worked. I've reset the phone twice.
I had this problem. Try plugging it on a different computer and see if it shows your files and reads the phone. If that happens. The drivers in your pc is the problem. I would try to uninstall and re install google drivers.
StormChaser83 said:
None of this worked. I've reset the phone twice.
Click to expand...
Click to collapse
Okay, but resetting the phone is not addressing the different PC/port/cable possibilities. It could also be the USB port on your device but it sounds like a PC driver issue or cable. Try a different PC and see what happens.