Database Users

[help] cant get fastboot driver working

I just got a dell streak and I am trying to install the fastboot drivers in windows xp. I boot the phone into fastboot and select the fastboot option. Then I wait 10 seconds and plug in the usb cable into the streak. The computer tried to install the driver and I go to device manager, right click, update driver and try to manually install the driver, but when I select google, inc the only drive that i have available is android composite adb interface. I dont get the option for android boot loader interface. I must be doing something wrong.
On my dell streak screen it says wait for usb fastboot detect. after 10 seconds it still says this. is it suppose to say fastboot or is that after you install the drivers?
Ive spent all night and cant seem to get windows to recognize my streak in fastboot. Now when I plug the streak in on the wait for usb fastboot detect my streak shows up in windows as 'usb device'. it doenst even show up as android device, just usb device.
I really hope someone can help me.

I think it has to do with my android_winusb.inf. Can someone open their android_winusb.inf and copy/paste it here? I have this string in mine:
; Dell Mini5
%SingleAdbInterface% = USB_Install, USB\VID_413C&PID_B007
%CompositeAdbInterface% = USB_Install, USB\VID_413C&PID_B007&MI_01
I am guessing there should be a %SingleBootLoaderInterface% string in there also that would allow the bootloader driver to show up when i try to manually select the drivers.

Looks like you have not got the drivers installed download the dell suite from dell look around the forum their is a way to tell u how to find the drivers on ur PC. If u cannot do it or no one has posted how to do it when I am at the PC later I will tell u
Sent from my Dell Streak using XDA App

Yes the dell pc suite is installed. I installed the one that was on my streaks internal card and I also tried one from dells site. I also followed the guide to manually install the drivers but shipping will the boot loader driver wont show up. Ive tried pointing windows to the dell programs folder to look for the driver as well.
Sent from my Dell Streak using XDA App

Can someone who has fastboot working please paste the text inside their android_winusb.inf so I can get the correct codes.for the streak?
Sent from my Dell Streak using XDA App

I could never get mine to work in fast boot either. I was not able to send commands through fast boot. It took me days to figure out how to get my Streak running 2.2 but I did and without FB.
Now I am having constant problems with my Streak rebooting and was advised to go back to 1.6 and start all over

Well no luck so far and nobody has posted what I believe will solve my problem. I just had to exchange my streak because of a dead pixel. I would like to get this working hopefully someone can help.
Sent from my Dell Streak using XDA App

Another solution if you still cant find the drivers Go to device manager Right click Android 1.0 Select Update Driver Software Select Browse my computer.... Select Let me pick Select All Hardware Scroll down to Google INC Select Bootloader and you should be good to go

I did that already. Doesnt show the bootloader driver. That is the problem. Only shows the composite adb driver.
Sent from my Dell Streak using XDA App

When I tried searching, Google never showed anywhere and that was after waiting for a few minutes for it to appear.
It was/is so frustrating! The instructions are easy to follow but when a pc doesn't give the optioons listed in the instructions, its irritating. I would still like to be able to do it the way everyone one does but I cannot get it to work that way.
Sent from my Dell Streak using XDA App

ok here is what worked for me..... Make sure you have the dell software installed - Then go to fastboot on the streak wait 10 seconds plug it in - don't worry about installing the drivers when the popup stuff comes up - go to device manager - there should be that caution crap next to the android device - right click on it to update the driver - chose pick from list - you will see android something and android phone (click on android phone) something will popup saying it ain't right blah blah blah - push continue and ok and let it install - look at your phone it should be in fastboot mode and Flash till your heart's Happy

Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf

Laaf2005 said:
Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf
Click to expand...
Click to collapse
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?

"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.

rnj79 said:
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?
Click to expand...
Click to collapse
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.

rnj79 said:
"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.
Click to expand...
Click to collapse
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.

Laaf2005 said:
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.
Click to expand...
Click to collapse
I'm just like you! I cannot find the bootloader driver. Surely it can't be just the two of us with this stupid issue?

Laaf2005 said:
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.
Click to expand...
Click to collapse
I have no .inf files in the DRV folder. The only folder in that is i386 otherwise, the DRV folder is empty. Obviously I'm not going to be of any help to you but at least I know I am not alone and am not crazy- thats the part that helps

Well I dont know why its empty, but I have a .inf in my folder. its for basically telling your computer which streak drivers you have available and in the file it only lists adb composite driver with the id for the driver. All I need is for someone to post the device id of the bootloader driver so i can try adding it. Or if someone can post the drivers here.

I beleive i have the same priblem, there is no way i can install android fastboot, ive tried the pc suite, manual random drivers from the internet and nothing, so annoying
Arya
Sent from my Dell Streak using XDA App

Can't install Windows Driver

I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.

ks-man said:
I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.
Click to expand...
Click to collapse
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk

YoungCorruptionV2.0 said:
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk
Click to expand...
Click to collapse
No, I've been trying to point it to the USB Drivers folder from the Android SDK. I can't seem to find the driver from HTC (or know which is the right one).
I didn't think it was HTC Sync but maybe it is...

If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.

Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.

sparksco said:
If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.
Click to expand...
Click to collapse
That makes sense, I never ran the program, just had it search the folder. I think I got it working though as mentioned in my post right above this one. Thanks.

You need HTC Sync and you need admin rights to install drivers on windows.

ks-man said:
Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.
Click to expand...
Click to collapse
Yeah your all good man, when you do adb devices and get your serial # back all is well, I had sync on my Vista pc and it wouldn't let me use HTC sync, it would just say not found, but I always just used the unrevoked EVO drivers and they hold true to this day, I've done G2s inspire and MT4GS all without new drivers
Sent from my Bulletproof_Doubleshot using Tapatalk

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk

Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben

Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2

What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000

METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.

I'm going to test in my desktop this weekend to check if it works with it.

I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.

I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA

Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf

I got my i9000 recognized using the latest drives from the Google sdk

That‘s great

http://ics.samsung-updates.com/addons/usb_driver.zip

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)

USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me

The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !

these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.

I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

[Q] Help with USB Drivers for Nook Simple Touch

The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.

Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.

Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB Interface​The system cannot find the file specified​I have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.

The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll

Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?

I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.

Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse

I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.

Oneplus 5 ADB

Can someone guide me how to get ADB working on OnePlus 5?

stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'

What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options

colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers

stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.

I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers

Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!

What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.

ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using

shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.

stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.

shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow

stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:

shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed

Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html