I'm in a bit of a fix. I correctly rooted my nexus 6p. I could originally run it in fastboot mode. But I wanted to install a ROM, and I foolishly cleared off my /system files as well. I nearly can get it fixed, but the one problem is that I can't get my PC to get my phone to get detected in fastboot AFTER this. But the phone is detected in recovery mode.
I searched everywhere and didn't get a good result. Anyone?
The rom is https://forum.xda-developers.com/nexus-6p/development/rom-t3488519
and I have flashed the vendor img, and the Rom. System files are now back, but I cant flash the radio image as I cant get my PC to detect it in fastboot.
This fastboot problem is bothering me a lot. Please, if you know how to fix it then please explain it in detail as I'm a bit new to this.
IMP: Although I haven't flashed the radio img, Wifi and things still seem to work. What could be the reason?
Hi... What OS do you run on your computer? How is your phone detected in device manager when you're in bootloader?
Do you have adb/fastboot up to date? If not download that zip here and try again, just in case...:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
5.1 said:
Hi... What OS do you run on your computer? How is your phone detected in device manager when you're in bootloader?
Do you have adb/fastboot up to date? If not download that zip here and try again, just in case...:
Thank you for replying. I am running Windows 8. My Phone isnt detected at all when I'm in bootloader. But it would work fine....until I accidentally cleared the system files in TWRP.
Yes, my files are all up to date.
Click to expand...
Click to collapse
Maybe try to reinstall USB driver when device is booted in bootloader:
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
5.1 said:
Maybe try to reinstall USB driver when device is booted in bootloader:
Click to expand...
Click to collapse
I already did that. Any other ideas?
UPDATE: I reinstalled gapps, now the phone boots up and works fine. But the PC still doesn't recognize it when my phone is in bootloader mode It was working fine before I accidentally wiped the system. Can you please help me out with that? Or could you please refer this topic to someone who knows a good deal about this? I appreciate your help.
Unplug the phone from your computer. Reboot into bootloader... Now plug the phone back.
Is your phone detected as an unknown device in device manager? Or not recognized at all?
5.1 said:
Unplug the phone from your computer. Reboot into bootloader... Now plug the phone back.
Is your phone detected as an unknown device in device manager? Or not recognized at all?
Click to expand...
Click to collapse
There is an unknown device called Android. But no files open up on my PC like it's supposed to. My device would read as Nexus 6P before the accident. Now, the PC reads it and I can view the files but that is only when it's in recovery or when it's booted up.
Is it caused by me accidentally wiping out the system files? I am not sure why exactly this is happening.
PS- After flashing the ROM, I lost root access. Would re-rooting fix it?
Change driver on windows via manual select driver and selecting from list.
to adb single sooner interface.
My device: 701->703 B212 KangVIP AJ Xposed
So... When in bootloader with "unknown device" in device manager... Right click on the unknown device and choose update driver...
Choose the option where you can select a driver on your computer and use the "USB driver" from the link I gave you before. (If you haven't done it yet )
audioralf said:
Change driver on windows via manual select driver and selecting from list.
to adb single sooner interface.
My device: 701->703 B212 KangVIP AJ Xposed
Click to expand...
Click to collapse
Change driver? I didn't exactly understand that. Could you please elaborate the steps? I have recently taken interest into android tweaking and I'm not very familar with how to do this. Thanks for your help.
@5.1 Thanks for the reply, but it doesn't work. I tried and the options I get are either troubleshoot or remove or properties. The update option isn't there. It is an unspecified driver.
If you don't understand. Well just google how to manually update drivers on Windows 8 and use the driver from the google USB driver link.
5.1 said:
If you don't understand. Well just google how to manually update drivers on Windows 8 and use the driver from the google USB driver link.
Click to expand...
Click to collapse
I understand your post, but unfortunately that didn't work, as the option to update didn't appear. But I didn't understand what @audioralf said
EDIT: I'll try it out and let you know soon. I think I nearly got it.
Googlenerd19 said:
There is an unknown device called Android.
Click to expand...
Click to collapse
And when you right click on that "Android" you have no option saying "Update driver software" ?
I'm out of thought then sorry...
I got this zip from http://www.wugfresh.com/faq/8/ :
1.) WinKey+C > Settings (Gear icon)
2.) Change PC Settings
3.) General > Advanced Startup > Restart now
4.) Troubleshoot > Advanced Options
5.) Windows Startup Settings > Restart
6.) Wait for computer to restart…
7.) Select ‘Disable driver signature enforcement’.
8.) Now you can proceed to install the drivers ^_^
http://www.thewindowsclub.com/change-pc-settings-does-not-open-windows
My device: 701->703 B212 KangVIP AJ Xposed
audioralf said:
I got this zip from http://www.wugfresh.com/faq/8/ :
1.) WinKey+C > Settings (Gear icon)
2.) Change PC Settings
3.) General > Advanced Startup > Restart now
4.) Troubleshoot > Advanced Options
5.) Windows Startup Settings > Restart
6.) Wait for computer to restart…
7.) Select ‘Disable driver signature enforcement’.
8.) Now you can proceed to install the drivers ^_^
http://www.thewindowsclub.com/change-pc-settings-does-not-open-windows
My device: 701->703 B212 KangVIP AJ Xposed
Click to expand...
Click to collapse
Okay, but I didn't find the zip on that page. Could you specify which driver exactly am I supposed to install? Because the Nexus 6P driver is already there.
audioralf said:
I got this zip from http://www.wugfresh.com/faq/8/ :
1.) WinKey+C > Settings (Gear icon)
2.) Change PC Settings
3.) General > Advanced Startup > Restart now
4.) Troubleshoot > Advanced Options
5.) Windows Startup Settings > Restart
6.) Wait for computer to restart…
7.) Select ‘Disable driver signature enforcement’.
8.) Now you can proceed to install the drivers ^_^
http://www.thewindowsclub.com/change-pc-settings-does-not-open-windows
My device: 701->703 B212 KangVIP AJ Xposed
Click to expand...
Click to collapse
BUMP: Device is detected perfectly when it's on and it is also detected when it is in recovery mode. Only the bootloader doesn't seem to be detected. Could this be because of faulty drivers or is it because of some mess up of my phone files when I accidentally wiped system before?
I don't see any reason why wiping system could have caused such issue. (I could be wrong though...)
Have you tried to update the driver while in bootloader?
Here is a how-to in case you're not sure how to proceed:
https://www.drivereasy.com/knowledge/how-to-manually-install-a-driver-in-windows-8-8-1/
Use the zip from the link I provided yesterday...
Try Wugfresh Nexus Root Tool kit http://www.wugfresh.com/nrt/
5.1 said:
I don't see any reason why wiping system could have caused such issue. (I could be wrong though...)
Have you tried to update the driver while in bootloader?
Here is a how-to in case you're not sure how to proceed:
https://www.drivereasy.com/knowledge/how-to-manually-install-a-driver-in-windows-8-8-1/
Use the zip from the link I provided yesterday...
Click to expand...
Click to collapse
Thanks, but do you mean the ADB driver shown under "Android Devices" in Device Manager? Because I updated it with the zip file and windows said it's up to date. Weird :/
@arifqur I have installed it, and it seems to control my phone well. But the problem is, how will I be able to use it to flash images to flashboot if the PC can't detect my phone in bootloader mode?
I'm really hoping this isn't a phone issue and it's a driver one. I even went to SDK Manager and re installed Google USB drivers thrice. I'm really wondering as to what could cause this. I think too that it's faulty drivers, for some reason.
Googlenerd19 said:
Thanks, but do you mean the ADB driver shown under "Android Devices" in Device Manager? Because I updated it with the zip file and windows said it's up to date. Weird :/
Click to expand...
Click to collapse
You said when in bootloader there's an unknown device recognized as "Android" in device manager... Upload the driver for that device...
Related
[*] shutdown the phone
[*]hold down volume up + power
[*]Now you are in the standard recovery mode
[*]assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows
or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB
[*]assuming you device is seen via fastboot devices, now type "fastboot oem unlock"
[*]accept...and new bootloader is unlocked...
[*]now we need a custom recovery from clockworkmod or amon_ra, and we'll be good to go
Credit goes to gandalf44
Seems like a lot of people are having issues with the amd64 driver from the 2.3 SDK. Here's a workaround:
Go to the PdaNet homepage and download the Windows 7 x64 version of the PC software Download PdaNet
Make sure your phone is not connected to the computer. Install the app from PdaNet. Ignore the warning about HTC sync if you get it, that doesn't matter for what we're doing.
At the end of the PdaNet install, you'll be prompted to connect your phone. Make sure USB debugging is on, and connect to a high speed (as in not through a hub) USB port.
Follow the prompts and accept the unverified driver warning. Let it finish, then reboot your phone into fastboot mode -- power off, then hold volume UP and power.
Open the device manager in Windows (right click My Computer, properties, choose Device Manager from the list on the left.
Find the Android 1.0 entry, with the yellow exclamation mark beside it. Right click and choose to update the driver.
Select to search your computer for the driver manually, and point it at C:\Program Files (x86)\PdaNet for Android\. You will see a warning about an unknown/unsigned driver for sure this time, accept it.
When it finishes, at the command prompt (in the sdk\tools\ directory) type
Code:
fastboot devices
you should now see your Nexus S listed.
Credit to Gbhil
Thank you for this information
So easy??? Lol!!! The only reason i asume somebody could take that phone is this...
The really OPEN SOURCE ....
That was easy and fast.
We can't flash files through the stock recovery?
I dont understand..I did everything you stated but I dont get the option to type anything.
just a fyi. fastboot oem lock will relock the bootloader!!
pimpkogan69 said:
I dont understand..I did everything you stated but I dont get the option to type anything.
Click to expand...
Click to collapse
You need to type it into the command prompt on the computer, not on your phone.
Any way to root without doing this?
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Jr33 said:
just a fyi. fastboot oem lock will relock the bootloader!!
Click to expand...
Click to collapse
Can anyone confirm this? This would be freakin awesome!
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Technically, it's not rooted, but in essence, we all know that once the bootloader is unlocked, we can fastboot flash a custom recovery. And from there, we can flash custom roms or just the su and superuser.apk into the stock rom from recovery. So yea, it is kind of rooted.
DOHCtor said:
Can anyone confirm this? This would be freakin awesome!
Click to expand...
Click to collapse
I can confirm that fastboot oem lock does re-lock it.
crazifyngers said:
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Click to expand...
Click to collapse
yea just found it thanks
Seems I can't update my Android 1.0 device driver.... I've updated everything in my SDK 2.3 but keep getting this ... Hmmmm
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
had same problem use this link
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
Yes you need to force the driver install
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Well once a custom recovery is available then the puzzle is complete.
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
TENlll423 said:
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
Click to expand...
Click to collapse
What device? which oos version? What steps did you take exactly? Did you tried switching firewalls off? Did you tried other pc? Did you follow this guide https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and use the drivers provided there? Can you reboot your device to fastboot mode? Is your bootloader unlocked already or never?
OnePlus 5... Nougat custom rom... Encrypted.... Rooted.... ADB fastboot from Snoop on windows 10... I'm going to disable firewall and uninstall ADB and reinstall. Then see if that helps.
ADB recognizes device... Fastboot does not.. my phone is unlocked and I can get it into fastboot by doing the power and volume up..
I reset my computer last night so I work nights when I get home this morning I'm going to give it another whirl .....thanks for the help.
TENlll423 said:
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
Click to expand...
Click to collapse
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Chamaka said:
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Click to expand...
Click to collapse
thanks. I'm going to give it a try.
Chamaka said:
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Click to expand...
Click to collapse
Thank you so much... Your instructions solved my issue..
Short history: I wanted to flash a Stock ROM. In normal mode, Windows knew the device properly. But when the device was in Download Mode, in device manager the icon of the LG phone had an exclamation mark (apparently something was wrong). Despite that, I started flashing using LG Flash Tool 2014. It failed after very slight initial progress. This was my first time doing flashing.
Current state: Whenever I hit the power button, it starts in Download Mode (i.e. the screen with "Firmware Update" title appears). I'm able to start a hard reset, but it fails. When I connect the device to my PC, I have the same device driver problem. I tried to reinstall LG drivers on Windows but wasn't successful.
Is there any solution?
Here is a picture of what I get whenever I try to reinstall the drivers: pasteboard.co/IxfmSgd.png
arham86 said:
Here is a picture of what I get whenever I try to reinstall the drivers: pasteboard.co/IxfmSgd.png
Click to expand...
Click to collapse
what driver version are you trying to install? (afaik - the latest one is "LGMobileDriver_WHQL_Ver_4.2.0.exe" )
did you try to completely uninstall and delete any LG related driver and let it install again when you connect the device?
- go to device manager
- find all LG phone drivers there and uninstall each one > on the uninstall prompt/popup > check "delete the driver software for this device" > then click "uninstall"
now you can try to install the drivers again from scratch...
do you use back usb ports on your computer? (if no - try to use them instead)
60nine said:
what driver version are you trying to install? (afaik - the latest one is "LGMobileDriver_WHQL_Ver_4.2.0.exe" )
did you try to completely uninstall and delete any LG related driver and let it install again when you connect the device?
- go to device manager
- find all LG phone drivers there and uninstall each one > on the uninstall prompt/popup > check "delete the driver software for this device" > then click "uninstall"
now you can try to install the drivers again from scratch...
do you use back usb ports on your computer? (if no - try to use them instead)
Click to expand...
Click to collapse
Thanks for your reply.
I installed LGMobileDriver_WHQL_Ver_4.4.2
Several times I uninstalled and reinstalled it.
I even tried the device on another PC (both PCs having Windows 7).
Interestingly, all LG drivers worked properly on normal mode.
But the MTP driver doesn't work for Download Mode.
I'm not even sure if this behavior should not be expected.
yes, but did you uninstall the drivers completely like i said (with removing all the previous driver files) ?
i recently did a kdz flash from download mode to get back to stock lollipop but i didn't see that 4.4 driver that u have used (the most recent version i've found was the one i've mentioned in my previous post)
btw try to find some universal adb drivers as well...
also try installing the drivers before pluging the device to PC