Windows 10 automatically installed this update: Microsoft - WPD - 2/22/2016 12:00:00 AM - 5.2.5326.4762
Since then no mobile device I connect to my PC can be detected. I used a restore point and that got things working, but it auto updated again and this time a restore point did nothing, and after the restore all restore points magically disappeared.
What kind of USB driver can I install, or what do I need to do to get my PC detecting my phone again?
Update: After attempting to reinstall the Qualcomm USB drivers, which just came as loose files, it detected the phone improperly in the device manager and from there I manually chose "MTP USB Device" which I know is the default and that got the phone detected again. But now the phone is not detected in fastboot mode as an ADB device when I use the command ADB devices. I tried reinstalling the fastboot driver package but that doesn't do anything. How can I properly clear/install fastboot drivers to get this working again?
Related
I've read through so many threads on so many forums trying to fix this, and I'm about to throw this thing through the wall.
I'm running CyanogenMod 7 nightly on 2.3.7
When I connect the phone to any PC (I've tried Win7 64/32 bit, XP SP3, XP SP2) I get a charging icon in my notification bar, but the USB Storage mode never opens to enable/disable. After about 10 seconds I see "USB Device Not Recognized." Happens the same on every PC. I can still access my internal storage via FTP, just not via USB. The device shows in my device manager as "Unknown USB Device."
Not sure if it's related, but when I boot into FastBoot it runs USB Control/USB Control init and then just freezes. Even after downloading a ROM update with ROM Manager it says "NO ROM FOUND"
This is what I've tried:
USBDeview to uninstall all Android-related drivers, reinstalled Samsung and Google SDK rev 4 drivers.
USB data wipe (for the hell of it, really.)
Multiple PC's with different OS and 3 different USB data cables, including the original.
At this point I'd like to try a factory reset. When I try to unroot with SuperOneClick the program just crashes. When I try a reset from the phone it fails to boot into recovery, and using the Factory data reset produces a "null" error.
I know just enough to be dangerous. If I'm missing something please let me know, and I appreciate any help.
--------------------------------------------------------------
Tried loading a CM9 rom from the SD card that I FTP'd over via ClockworkMod Recovery. It asks for data+cache wipe, then just boots into recovery. I get "NO IMG FOUND" and USB CONTROL INIT and USB CONTROL INIT END.
Try installing pdanet on your computer. Its what I did in order for my computer to recognize my phone. Hope it helps.
Should have mentioned earlier that I also installed PDANet after I wiped my drivers. It couldn't detect the phone being connected and did not completely install.
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.
HI,
I am trying to root and installing TWRP in my device but it seems that drivers are not properly installed in My PC .
Everytime I have to restart zenfone just so that PC will detect and connect to the phone. But it is painful task as everytime for detecting and connecting process I have to restart my device. Phone should connect immediately when connected to PC.
So I am trying to uninstall all drivers from PC but again drivers are not getting fully uninstalled. ( I have tried uninstalling from Device Manager but that didn't help too, Using windows 8.1. ) .
Is there any way to uninstall all drivers of Asus zenfone 2 ze551 ml from PC manually So that next time PC will detect freshly detect new device and download and install drivers.
Also there is an observation. Whenever i reboot my phone while attaching it to the PC/Laptop drivers are getting installed/detected by PC/laptop. But when phone it switched on then no luck. Also while phone in on and you try to connect to PC/laptop then also it wont connect.
Need some help with this one.
I've got debugging enabled, have tried literally all the connection options, multiple computers, etc. I just want to back up and root my phone. I'm at the point that I'm willing to try a factory reset and pray that works. Is there anything else I can do before that?
Do you have device drivers installed on your computer? Does adb/installed properly? Is OEM unlocking ticked? If its a driver issue update them. If its adb download the minimal adb from XDA. Otherwise that's it.
Device drivers are installed and OEM unlocking is ticked. I'm working on updating adb/fastboot.
Alright, everything is updated as much as it can be, and still nothing. No recognition whatsoever.
What version of windows are you running?
I had to do this to get mine to work... go into the device manager on Windows, find the Nexus, right-click and choose update driver software. Browse to where the driver is located on your PC and select the folder.
I am trying to recover the data from my old bootlooping LGV20. My drivers are updated. When I plug my current, working LGV20 into the computer, the phone is immediately recognized and the driver is listed as LG v4.2.0, the most current in Device Manager. The phone is labled as its model number in Devices and Printers. When I plug in my old V20 (which has full access to stock recovery and download mode but does not boot) the computer recognizes something is plugged in, but in Device Manager the device doesn't show up. In Devices and Printers the phone shows up, but as "LGE Android Phone".
Summary:
When a working LGV20 is plugged in, it is recognized and the latest 4.2.0 driver is used.
When the bootlooping phone is plugged in and completely off, it is only recognized as "LGE Android Phone"
Not recognized in Recovery mode
Because of this issue, I cannot use adb on the phone to recover my data.
The phone is stock, non-rooted, android 7, LG-VS995. I have the usb debugging option in the recovery menu though the phone bootloops when this is selected.
ADB installed via 15 second installer and SDK.
"ADB Devices" returns nothing.
When in Download mode, "Fastboot devices" returns nothing.
This issue was repeated on a second computer.
USB 2.0 and 3.0 tried.
The phone is recognized in LGMobileSupportTool
In Download mode the phone is recognized as "LGE AndroidNet" in Devices and Printers and as a COM41 port (changed from 7) in Devices and printers.
What do? I'm at a loss and it feels like I've tried everything.
Edit: I've successfully dumped the phone via LGUP, tried flashed a new image, phone is still bootlooping. Is there any way I can browse the userdata dump file?