Hi,
Anyone have experienced this issue? My oneplus 8 is only detected as "Android" under device manager with an exclamation mark. I tried reinstalling google, oneplus and qualcomm drivers but its still the same.
Appreciate any help I can get. Thanks
This is already ok. not sure why my laptop wont detect it properly but it worked on the desktop. Thanks anyways
You will need to manually choose the fastboot driver in device manager. Right click Android, choose update, browse my computer, let me pick from a list, choose Android devices, and then choose the option for fastboot or bootloader interface. It will scream that it may break things, but it's safe to ignore. After this, your device should authenticate in fastboot. If you do not have a driver already installed, pull the latest from Google, install them, and then they should populate in Device Manager for selection.
Related
I've tried the following:
1) Installing HTC Sync Manager and HTC Sync (the older version of Sync Manager)
2) Installing the drivers included with hasoon's All-in-One Toolkit.
Neither works. Both methods result in a device labeled "E:" showing up under "Portable Devices" in Device Manager, but adb devices shows no devices, and if I choose on the phone to use it as a disk drive, it does not show up under My Computer.
I previously had a Galaxy Nexus and I had the adb usb drivers installed for that. The only thing I can think of is that the computer is somehow still defaulting to those drivers instead of using the HTC drivers, but I don't know how to solve that problem, if that is even the problem.
Any advice would be greatly appreciated!
Oh, and I also had the android-sdk installed for my Galaxy Nexus. Any chance that completely uninstalling it would help?
I had the same problem but i just figured out how to make my PC to see the HTC One S
(My Windows 7 is in Italian, so I don't know the exact translation for the links)
Start -> Right click on Computer -> Manage -> Devices -> Select the HTC Android Phone USB Device you will have in "DVD/CD-ROM", right click on it and "Deactivate" it, then you have to right click the other HTC Android Phone USB Device you will have under "Disc units" or something like that and right click it, then "Software update" (I repeat, I don't know how the buttons will be in English since I'm on Italian windows, but it'd be similar) and select the second button "Search driver software in my computer" then again the button below "Choose manually" and then just click on "Disc unit" and finally "Next" and it should work...
Hope it helped!
chrikenn said:
I've tried the following:
1) Installing HTC Sync Manager and HTC Sync (the older version of Sync Manager)
2) Installing the drivers included with hasoon's All-in-One Toolkit.
Neither works. Both methods result in a device labeled "E:" showing up under "Portable Devices" in Device Manager, but adb devices shows no devices, and if I choose on the phone to use it as a disk drive, it does not show up under My Computer.
I previously had a Galaxy Nexus and I had the adb usb drivers installed for that. The only thing I can think of is that the computer is somehow still defaulting to those drivers instead of using the HTC drivers, but I don't know how to solve that problem, if that is even the problem.
Any advice would be greatly appreciated!
Oh, and I also had the android-sdk installed for my Galaxy Nexus. Any chance that completely uninstalling it would help?
Click to expand...
Click to collapse
Try this first:
Install drivers on you PC, as you have done. Also don't forget to enable "Debugging mode" in settings. After that, when you connect phone to PC, don't select anyhing, leave it at default of "just charging".
If after the above it still won't work, then you will have to:
1) Uninstall the drivers that you installed from the toolkit.
2) You will need to change how windows handles installation of drivers, once the device is connected.
a) Right click on "Computer", then properties.
b) From the left, click on Advances System Settings
c) Click on Hardware tab.
d) Click on the second button "Device Installation Settings"
e) If you have "Yes..." selected, select "No" instead.
f) Now select "Install driver from Win Update if it is not found on my computer and save!
3) Restart you PC
4) Go to the Hasoon's All-in-One Toolkit folder and install HTC drivers again. Just make sure your phone isn't connected at this time.
5) After intallation is done, just connect you phone. Make sure "debbuging icon" is present on the phones notification bar and that is it, you don't need to enable usb storage mode.
Hope it helps.
Under Windows 8, you will likely run into the issue that you can get ADB to work properly, but cannot get Fastboot to work.
The reason is that ADB and Fastboot actually require/use two different drivers for each to work properly under Windows 8. But, only one of those, the driver that ADB will work under, will intall in a signed fashion that Windows 8 requires. You will need to enable Windows 8 to allow unsigned drivers to be installed, the steps are below.
You can install the normal HTC Sync, and the drivers/devices should be installed and work fine for ADB. You can test this by installing the SDK Tools for Windows and HTC Sync, then run "adb devices" from the command prompt, and it will find the device and work fine.
But...when you go into Fastboot mode, for example, to install a new custom recovery, the Fastboot.exe just flashes in the DOS window and nothing works.
Upon looking back into the Device Manager in Windows once in fastboot mode on the phone, it no longer recognizes the driver/device.
After some driver troubleshooting, I found that when the phone reboots into Fastboot mode, it needs another set of Generic Drivers, the typical ones you can find on the Web for HTC devices. The device while in Fastboot mode, under the Device Manager would show up with the Unknown icon instead of the My HTC device icons at the top of the list.
The issue is Windows 8 by default will not allow you to install unsigned drivers without jumping through some hoops.,
So here is what you do. You can download these generic drives, unzip them somewhere on the desktop, and have them ready.
http://androiddrivers.net/htc-android-drivers/download-htc-one-x-64-bit-windows-drivers/
(There are several other versions out there, just google "Windows 8 HTC One X Drivers" and you will find many to download, or the original HTC .exe. I like the zip file, easier to unzip, then update the driver.
Then, put your phone into Bootloader mode.
Go to Device Manager and notice that your phone is showing up as an Unknown Device in the list.
Now, in Windows 8:
1) Settings
2) Change PC Settings
3) Very bottom, Advanced Startup. Select this.
4) It brings you to another screen to select the options you want.
5) Troubleshoot
6) Advanced Options
7) Startup Settings, Select this option. You will see a list of options it gives you, included is "disable Driver signing"
Select this now and the computer will restart and provide another menu.
#7 is the option to boot the computer with driver signing disabled.
8) Once rebooted, your phone is still in bootloader mode, go back to device manager, right click the unknown android device, and update the driver manually, selecting the folder of the drivers you have downloaded previously.
It will then prompt about unsigned drivers, select Yes to install them anyway.
Now, your phone is detected in bootloader mode, and Fastboot will work properly to flash recovery etc.
this is pretty helpful but make sure you post in the right section
So I did what you did, and when i got to the screen to choose option 7, i tried with both F7 and hitting the number 7, then i went back into device management and tried to update the driver, but it didn't prompt me to install unsigned drivers.
Also, once you click settings, you have to click on general to find advanced options.
Any ideas?
---------- Post added at 12:53 PM ---------- Previous post was at 12:37 PM ----------
Ok, I got it workng, but theres a few more steps involved. Upon trying both drivers that you suggested downloading, when I run an adb devices command, it doesn't show anything under the devices attached listing.. Is that normal, or should I see my phone? I suspect this is why I'm having issues inside roms, since the boot.img isn't flashing correctly.
Hi all,
I was having a strange problem with my USB dropping out when using the NEWER recovery (TWRP and Philz). Which meant I couldn't push files via ADB or Sideload. Here is my solution....
Before starting
I am using Windows 7
Download Google USB driver
Make sure you have TWRP 2.7.1.1 loaded as your recovery
You may have slightly different devices show up maybe, but this is what mine showed...
Open device manager
Plug phone in and power up to bootloader
Device manager should show 'Android Device' or similar
Open recovery
**This is where my USB was dropping out**
Make sure TWRP 2.7.1.1 loads
Look at device manager and should show 'One Mini' with a yellow exclamation mark
I tried updating the drivers automatically and browsing to the Google USB folder that we downloaded above but just kept saying 'device driver loading failed'.
The only way I found worked was
Right click 'One Mini' and update driver
Browse my computer for driver software
Let me pick from a list of device drivers
If you have Android device listed click that, if not choose Portable device.
Click 'Have disk' and locate the Google USB Driver folder and should be able to load the .inf file.
Click from the list ADB USB device and click ok.
This should load your device and install properly.
You shoud now be able to use ADB and Sideload in Recovery now.
Let me know if this works or not as there are a couple of bits that I can't replicate as the driver is already there!
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
hahaha1659 said:
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
Click to expand...
Click to collapse
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
hahaha1659 said:
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
Click to expand...
Click to collapse
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
hahaha1659 said:
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
Click to expand...
Click to collapse
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
hahaha1659 said:
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
Click to expand...
Click to collapse
It was created by a member of this forum, you should be able to find a safe version here somewhere.
Sent from my LGL84VL using Tapatalk