Related
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Hi - Would really appreciate your help here. Thanks for the tip on turning debugging off to get to the phone so I could install the USB drivers. Problem now is that ADB just refuses to connect to it. It shows up asa disk drive in Devices, but when I do a kill-server then start-server then adb devices, it doesn't list any devices, and an adb shell just says device not found.
Do I need to reboot Windows, or the phone? Seems unlikely. I can open a window to the phone, but can't get access to install the Gingerbreak and su files I need to root it. Going crazy!
Thanks,
Eric
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Black-Falcon said:
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
ClarkSt said:
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Click to expand...
Click to collapse
Try downloading busybox from the market, or downloading titanium backup and hit the "problems" button when you open it and select get busy box
Black-Falcon said:
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Tried GingerBreak. No good. "permission denied".
Good idea - I got Busybox installed this way, but still no joy from Gingerbreak.
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
DroidXcon said:
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
ClarkSt said:
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
Click to expand...
Click to collapse
Check the development thread for the Charge. There's a thread on how to rollback to ED1 with root using Odin.
Edit: Direct link: http://forum.xda-developers.com/showthread.php?t=1085190
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Dude - THANK YOU!!!! I could not get those drivers to install!!!
Please - Stickie!!!
If you want the drivers and don't trust the sources posted anywhere (we're not trustworth ?) you can get them from the phone itself. They are located in the file /system/etc/autorun.iso and you can extract them from it.
For those of you who have had trouble with getting the drivers for the Infuse, download this:
[Im new so cant post a link, but goto softpedia.com and search kies. The only kies program available will appear, and download and install that]
It wont recognize your phone, but after you install the program, the appropriate drivers will be present, and the root with SuperOneClick will work immediately.
*remember, the program wont recognize your phone if its plugged in, but that doesn't matter. It will just install the appropriate Samsung_Android drivers your PC needs to recognize the phone in SuperOneClick.
Hope this helps!
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
pvillasuso said:
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found.
http://forum.xda-developers.com/showpost.php?p=13895587&postcount=7
posted here.
Phone doesn't exist on my PC.
Nope. Bought the infuse on day one. Installed Kies 2.0.0.11044_11_3. Phone not recognized, installed drivers, learned the truth about Kies. Phone would not be recognized but at least installing Kies made the phone visible to the PC, so I knew I could root if I so desired, read up about rooting and thought I was ready. The phone had other plans.
Decided the other day that I was ready to root. Plugged in the phone but it no longer showed up in Windows. Something about the phones compatibility with my system changed. Tried to install this Kies 2.2.1.11053_99_3 yesterday, reinstalled drivers, activated USB debugging, plugged the phone in started up SuperOneClick and . . . still nothing happened. So I deactivated USB debugging and started over. Followed all the directions in the root posts and and SuperOneClick threads . . .
But somehow between day one and today my Windows 7 64 bit system does not know that the phone is plugged into it.
When I plug the phone into USB the phone asks me how I want to interact with the computer, Kies (Firmware Update); Media player: Mass storage. But the computer shows nothing. Device Manager doesn't list the phone, Windows Explorer doesn't show the phone, Devices and Printers window shows everything that's connected but NOT the phone, it's as if I plugged nothing into the computer. The phone is charging so I know that it's plugged in, but it doesn't seem to be communicating with the PC. I've re-booted, re-installed, reviewed, rewired and re-alized that I have no clue what happened. (Tried different cables, different USB ports different times of the day)
It worked once upon a time, I tried rolling back restore points and disabling my kaspersky 2011, I've followed all rooting instructions in these threads to no avail.
I am now ready to hurl my phone out into traffic to see if that will help, but before I do I'm hoping someone here may have the answer I need.
. . . please . . .
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
For me, one of the SuperOneClick packages included Windows drivers.
Which is great since SOC is the only reason I needed Windows drivers. (SOC never works in Linux for me for whatever reason...)
All android phones are supported in linux natively.......jus t saying
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Well yeah - I've never had to install any drivers for ADB or anything else.
However, for whatever reason, superoneclick and Linux don't get along for me. So the only time I ever have to install drivers is when SOC rooting from Windows.
superweapons said:
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
Click to expand...
Click to collapse
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
menzoom said:
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
Click to expand...
Click to collapse
I've tried just about everything too, and nothing works to get my 64 bit Windows 7 PC to recognize the Infuse. Finally resorted to AndroidSync for file transfers, which worked fine, but it just makes me angry that I can't make the darn thing connect via USB.
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
And select SOFTWARE
Tried that last week. Didn't work for me. The PC does see the device, but never finds any files on it.
Drivers in that link
I was having the same issue mentioned yesterday after loading the Samsung Infuse drivers, where my PC still couldn't see the data on my phone. (I'm also running 64-bit Windows 7 OS.)
Once I loaded the drivers and plugged in my phone, I got the happy little "device drivers installed properly" message and thought I was good to go. Nope. No drives mounted and visible in Explorer.
Under Devices and Printers, I could see SAMSUNG_Android with the unhappy yellow exclamation point. The troubleshooting report just says "Problems with PnP devices."
So I dug into into Device Manager. Under Portable Devices, there were 2 new WPD FileSystem Volume Drivers. Both had the same yellow exclamation points and showed a Device Status of "This device cannot start. (Code 10)."
It turns out Windows 7 wasn't assigning drive letters to the new Android volumes. It creates two disk drives (one with pictures, videos, and ringtones and the other with music, external SD, and media). If you right-click on the drives and choose "Change Drive Letter and Paths," click Add, and assign it an unused drive mapping, it will then appear in Explorer.
Incidentally, the SAMSUNG_Android still shows up with its unhappy yellow exclamation point in Devices and Printers. So I imagine there's supposed to be a more user-friendly way that doesn't expose the true internal file structure when it's all working properly. But in the meantime, I can at least access my phone data via USB.
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Dude look at the date
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Hey there..
View attachment 876861
thanks
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Yep...
Ubuntu / Linux FTW!
Hmmm, native on Linux you say? Don't have to battle with windows composite USB hub bullcrap you say? I shall try this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Help, i just got my replacement phone and now superoneclick wont work to root my phone. any suggestions??
also my comp keeps trying to add the Same hardware over and over and if i kept plugging in the phone. does it on the other unit also
Windows PC?
Go into Device Manager and delete the Samsung device.
Reboot your computer
Download the USB drivers and install
Reboot again
plug in phone and see if it detects.
Uncle Irish said:
Windows PC?
Go into Device Manager and delete the Samsung device.
Reboot your computer
Download the USB drivers and install
Reboot again
plug in phone and see if it detects.
Click to expand...
Click to collapse
window xp,
do you have a link to the drivers?
bignate78 said:
window xp,
do you have a link to the drivers?
Click to expand...
Click to collapse
Do you have Samsung Kies?
(That's probably a dumb question now that I think about it..but that's where I got my drivers when I rooted it)
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
One of the superoneclick packages has drivers included, that's what I used.
Entropy512 said:
One of the superoneclick packages has drivers included, that's what I used.
Click to expand...
Click to collapse
None of the superoneclicks are working on my end
what exactly is happening?
does the one click program run through the process and fail or does it just fail to run.
infuse drivers
infuse drivers(windows):
http://org.downloadcenter.samsung.c...ATT_SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip
You may need to powen off and power on phone for driver installation.
to root :
disable anti-virus
also put your phone in usb debugging mode.
download again superone click or lost1's zip file(there is root script file inside zip)
bignate78 said:
None of the superoneclicks are working on my end
Click to expand...
Click to collapse
That's most likely because you haven't uninstalled and reinstalled your drivers. That's why I suggested a package with known working drivers.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
Please take your time to read this.I will keep it quite short, but try to understand my problem.
Ok so I am trying to enable USB debugging for my Nexus 5.But everytime I try to install the ADB driver, it says parameter is incorrect (I'm using windows vista).
At first, I didn't have the SDK installed, so I downloaded the 70 MB SDK Manager, and from there I downloaded the platform tools & google drivers, then I tried installing the drivers manually using the Device manager using both methods of locating the file manually using the have disk method and the locate the directory and include sub folders method..but both have failed to install the driver and it keeps saying the parameter is incorrect.
Suggestions?
Use a different driver from the one included in the SDK. Either use the USB driver package provided by lg(I did this and it went flawlessly) or use the "naked adb driver" which is a simple adb driver that should just work.(I used the former because the naked driver is third party and not properly signed, so it's a pain to install on windows 8)
Find either through a Google search.
Edit: nvm this guide includes the links required: http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
biro2200 said:
Please take your time to read this.I will keep it quite short, but try to understand my problem.
Ok so I am trying to enable USB debugging for my Nexus 5.But everytime I try to install the ADB driver, it says parameter is incorrect (I'm using windows vista).
At first, I didn't have the SDK installed, so I downloaded the 70 MB SDK Manager, and from there I downloaded the platform tools & google drivers, then I tried installing the drivers manually using the Device manager using both methods of locating the file manually using the have disk method and the locate the directory and include sub folders method..but both have failed to install the driver and it keeps saying the parameter is incorrect.
Suggestions?
Click to expand...
Click to collapse
uninstall driver and use this tool.
samersh72 said:
uninstall driver and use this tool.
Click to expand...
Click to collapse
Tried it, still doesn't recognise my nexus 5 as ADB device, and windows still wants to install the driver for it & fails as well
biro2200 said:
Tried it, still doesn't recognise my nexus 5 as ADB device, and windows still wants to install the driver for it & fails as well
Click to expand...
Click to collapse
i am sorry to ask this but are you having problem enabling usb debugging? did you activate developer option by tapping build number seven times?
Man this stuff gave me such a headache same issue here. But with fastboot. I had to manually update the drivers while the phone was plugged in. That's what messed me up.
First uninstall all drivers
While phone is on.
Update drivers with USB debugging enabled
While phone is in boatloader
Update again.
Adb and fastboot should work fine after that. Use one of the exe type drivers. Like LGS driver .exe than go into the device manager and update. Let the computer find the drivers.
Sent from my Nexus 5 using xda app-developers app