Database Users

Win7 Auto Installs Wrong Drivers

Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!

It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.

pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7

Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app

[Q] Unbrick G2 D803. TWRP.

Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.

BraydenJW said:
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
Click to expand...
Click to collapse
try these as drivers

Trying now
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
Thank you. Trying this now. I'll let you know how it goes.

datechnerd said:
try these as drivers
Click to expand...
Click to collapse
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.

BraydenJW said:
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
Click to expand...
Click to collapse
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those

datechnerd said:
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
Click to expand...
Click to collapse
I'm afraid that did not work. I get an error message saying there wasn't any drivers found in that folder.
i.imgur.com/mkLZzBe.png
The two files are directly within the extract folder on my desktop. I'm running Windows 8. I right-clicked g2 in device manager, and selected update driver software and navigated to the extract folder on my desktop.
Thank you for your help so far, do you know where I could go from here?

It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.

BraydenJW said:
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
Click to expand...
Click to collapse
go to sideload and install drivers

datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.

datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
I'm sorry. I'm not entirely sure what you mean. When I go to sideload on TWRP, it gets stuck on the loading feature part indefinitely.
cityneversleepz said:
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
Click to expand...
Click to collapse
Thank you. I've tried it from my own laptop and my work computer and both have similar results. I'll try it from one of my older computers. I'll post back with my findings.

Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?

BraydenJW said:
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver

datechnerd said:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
Click to expand...
Click to collapse
Thank you! Trying this now. I'll report back soon.

It's looking good! It showed up in my adb devices now. Just have to re-download the rom

I pushed the ROM and am installing it now. If this goes through successfully, I'll send you some money over paypal if you wish. Nothing huge, but at least a little as a token of my appreciation.

The ROM installed successfully. I'm just waiting for the first boot now. It's taking a while (about 5 minutes now) and I'm VERY nervous.

The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?

BraydenJW said:
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
Click to expand...
Click to collapse
that rom says let the first boot take as much time as needed.

datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Alright! I'll leave it for a few hours. PM me your paypal email if you'd like me to make a donation to you! You've been an extreme help!

datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Left it for over an hour. No luck. Something is wrong.

Soft brick? (No ROM installed but can sort of boot into recovery)

howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7

Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!

demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.

fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones

I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?

You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed

I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.

Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand

[Q] G2 Soft bricked no ROM on Internal Memory

SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.

The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP

Last option is lg flash tool and then reroot

Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.

Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"

Stuck on boot, can't access download mode, recovery crashes

I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".

I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.

Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.

no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0

kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.

FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.