Database Users

[Q] PC recognices Vega as USB device

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"

Nexus 7 shown as "unknown device" in bootloader mode

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.

[Q] Can't get LG G2 back to stock / unrooted

Creating a troubleshooting thread to see if might be able to get some help on a big problem I'm having with my LG G2...
I'm trying to restore my VZ LG G2 to stock so that it can be returned (audio input is malfunctioning). I am currently running TWRP + CM 11 Nightlies on it.
When I enter download mode, I see the screen "Firmware Update" and it says "B99" and "Rooted" at the bottom.
When I use the R&D Test Tool + LGMobile Support Tool to try to restore to VS98011A_01.kdz, the software update runs on my computer as if it is pushing the update to the phone, but the phone itself shows no actual status change. It just sits there with 0% on the status bar.
When it finishes on my computer it says (on my computer) that the software update was successful. Unfortunately my phone boots into CM just like it normally does with all my apps and data there.
Based on some suggestions I have seen, I have tried manually changing to COM 41 and disabling the device as a modem in device manager -- does not make a difference.
I have no idea why no actual change is happening on the phone. Any suggestions?

Man, this is brutal. I thought that maybe the issue was that I was using the 3.10 LG United drivers instead of the 3.8 drivers, so I uninstalled 3.10 and installed 3.8.
Unfortunately now the LG G2 is recognized when it is in normal mode (running CM 11.0) but Windows shows "No drivers found" when I put it in download mode:
USB Composite Device: Ready to Use
CDC Serial: No drive found
CDC ECM: No driver found
LGE Android Phone: No driver found
Network Controller: No driver found
The last four all show up under "Other devices" in device manager with an exclamation.
Previously I was at least able to see the LG Android VZW etc. etc. under COM/Ports with 3.10 drivers installed.
I am burning so much time trying to figure this out. Mayday, mayday!

For anyone that may come across this thread in the future, I want to share what ultimately worked.
I followed the TOT method instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2448960
It was just as easy as the KDZ method, but actually worked! Here are the two things that seemed to make a difference:
1. I installed the _Verizon_ LG drivers referenced in that thread
2. I manually changed to COM41
Following all instructions in that thread everything worked like a charm.

help getting out of download/firmware update screen

my phone was stuck in fastboot using the instruction here: http://androidforums.com/threads/lg-g2-stuck-in-fastboot-mode-please-help.865650/
i tried to follow this forum http://forum.xda-developers.com/showthread.php?t=2432476 i can get the program to run and ready to go but its not doing anything on my phone's end.
my computer sees my phone as "LG AndroidNet Phone" and "Unknown USB Device (Link in Compliance Mode)".

teapalm said:
my phone was stuck in fastboot using the instruction here: http://androidforums.com/threads/lg-g2-stuck-in-fastboot-mode-please-help.865650/
i tried to follow this forum http://forum.xda-developers.com/showthread.php?t=2432476 i can get the program to run and ready to go but its not doing anything on my phone's end.
my computer sees my phone as "LG AndroidNet Phone" and "Unknown USB Device (Link in Compliance Mode)".
Click to expand...
Click to collapse
You see that tutorial you followed, it says download the LG Drivers, did you do that?
Download and Install LGUnitedMobileDriver_S51MAN312AP22_ML_WHQL_Ver_3.12.3.exe.
If the problem still occurs, try downloading and installing the drivers from this ADB_USB_Drivers.rar package.
Also your title is misleading, may I perhaps suggest something like "Help with LG AndroidNet Phone, Unknown USB Device" instead of "help getting out of download/firmware update screen".

d00lz said:
You see that tutorial you followed, it says download the LG Drivers, did you do that?
Also your title is misleading, may I perhaps suggest something like "Help with LG AndroidNet Phone, Unknown USB Device" instead of "help getting out of download/firmware update screen".
Click to expand...
Click to collapse
i install both of that and nothing.
my phone is literally stuck in the firmware update screen.

Windows not detecting device in stock Recovery Mode

Hi. I am trying to sideload the Android 6.0.1 update but am having some problems detecting the device in recovery mode.
I have previously unlocked my bootloader on the day i got my phone.
I have enabled USB Debugging and have installed android USB Driver 11.0.
On my Windows 8.1 Device Manager...
When I am in normal android = Android Composite ADB Interface is present.
When I reboot to Bootloader = Android Bootloader Interface was installed.
However, when I am in the stock recovery, Android Composite ADB Interface is not found. Neither is there any unknown devices in my Device Manager (yellow question mark) that might look like the ADB Interface.
As a result, when I am in Recovery Mode, "ADB Devices" command does not work.
Help? Thanks!

Same here!
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!

I am having this same issue. I've installed HiSuite with the latest USB drivers and have the latest Android SDK Platform Tools updates. I have tried unplugging and plugging-in the device when it is in recovery to try and trigger something but nada. I've tried different USB ports too.
My behavior is exactly the same. The phone shows up in ADB devices under normal full boot and also in the bootloader. As soon as it goes to stock recovery it won't show up as a device in Windows anymore. Not as an even an unrecognized device.

Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.

Minlock said:
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Click to expand...
Click to collapse
Thanks! I realised im actually on Windows 10 too...
However, your method doesnt seem to be working for me.
In Recovery mode, "Android ADB Interface" doesnt show up. Hence, I added a legacy hardware as you suggested, but it shows up that "This device cannot start. (Code 10)".
I also tried to update the hidden "Android Composite ADB Interface". While driver installation was okay, the phone is still not detected.
I tried replugging in the phone into a different USB port but it is still the same.
Strange... seems like only some people are encountering such issues? Wonder what is the difference. Thanks.

okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....

l0nEr said:
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
Click to expand...
Click to collapse
After doing all the previous steps, doing this step really did the trick.
Thanks!!!

makeitra1n said:
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
Click to expand...
Click to collapse
i'm here too

I had same problem and after searching days it solved by installing universal ADB Drivers from the link below:
Universal ADB Drivers