Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.
syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Is your phone actually in fastboot mode?
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?
MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?
Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.
I have a Xperia SP model C5306 on Fido in Canada that I cannot for the life of me get into fastboot mode. The phone is carrier unlocked (by unlockthatphone) and I've verified it on another carrier. I have also rooted the phone with the doomlord exploit successfully.
When I hold the volume up button and plug the device into my Win 7 Pro 64 bit PC the LED goes red for a second then orange once the battery charging icon appears.
The phone seems to have no problem getting into flash mode but fastboot is a no-go.
To get into fastboot you need an UNLOCKED bootloader, it is not the same thing as a SIM unlocked phone.
cachanilla86 said:
To get into fastboot you need an UNLOCKED bootloader, it is not the same thing as a SIM unlocked phone.
Click to expand...
Click to collapse
Based on all of the instructions I've read fastboot is required in order TO UNLOCK the bootloader, including those from Sony. If you can't fastboot until the bootloader is unlocked how do you unlock the bootloader?
Have you a SIMLOCK? Have you became that phone from your provider?? it can be that the provider disabl the fastboot that you not can disabl the Simlock
XplayerLP said:
Have you a SIMLOCK? Have you became that phone from your provider?? it can be that the provider disabl the fastboot that you not can disabl the Simlock
Click to expand...
Click to collapse
I bought the phone from a provider but I have carrier unlocked the device through an unlock code that I bought from Unlockthatphone.com
Is that different from a Simlock?
Have you installed the drivers yet?
This phone is quite funny, it restarts after a few seconds of inactivity in Fastboot/Flash mode
Catching my breath, letting it go, turning my cheek for the sake of the show
CallMeVentus said:
Have you installed the drivers yet?
This phone is quite funny, it restarts after a few seconds of inactivity in Fastboot/Flash mode
Catching my breath, letting it go, turning my cheek for the sake of the show
Click to expand...
Click to collapse
I have the drivers on my PC, I downloaded the ones from Sony and replaced them in the SDK folder. I haven't got to the point where my computer asks me to install the drivers. I'll try this.
649 34535926
So when I hold down the volume up button and connect my phone to the PC via USB I see a green LED (fully charged) on the device and my device manager tells me that there is a Sony Ericsson seehcri Control Device connected. If I navigate to the Driver information of that device the driver is pointing at the Windows System 32\drivers\seehcri.sys driver.
When I try to update that driver to the Fastboot driver it says there are no 64-bit compatible drivers in that folder. Are there 64-bit drivers for fastboot?
cameron.laird said:
So when I hold down the volume up button and connect my phone to the PC via USB I see a green LED (fully charged) on the device and my device manager tells me that there is a Sony Ericsson seehcri Control Device connected. If I navigate to the Driver information of that device the driver is pointing at the Windows System 32\drivers\seehcri.sys driver.
When I try to update that driver to the Fastboot driver it says there are no 64-bit compatible drivers in that folder. Are there 64-bit drivers for fastboot?
Click to expand...
Click to collapse
Okay, Sony's fastboot drivers are not signed, so to install the drivers, you need to disable driver signature enforcement in Windows first.
Look here for more info: http://forum.xda-developers.com/showthread.php?t=2354721
Try this method.
Install Drivers
Fastboot Mode - Blue Light - Turn phone off>Press and Hold Volume UP button while plugging in USB Cable> Release the button (from being held) after the blue light.
Flash Mode - Green Light - Turn phone off> Press and Hold Volume DOWN button while plugging in USB Cable> Release the button (from being held) after the green light.
Common problem is it doesn't stay too long on specific mode
You will need drivers try downloading Xperia Z driver here - http://developer.sonymobile.com/downloads/drivers/xperia-z-driver/
(Optional in case you can't Install the driver correctly)
Install Driver first
1.Extract the downloaded file. (If it is in Zip file) in a place where you can easily locate it.
2.Connect your phone (turned on) to your computer
3. Assuming that you have My Computer Icon on your desktop.. Right Click it > Manage> Device Manager (Located at the left tab) > Android Phone> android ADB interface > Right click> Update Driver Software > Browse my computer for the driver software and locate where you put the XZ driver.
4.Done!.
It worked for me, hope it will work for you, too.
Guys, you can correct me if I am wrong..
jayP11 said:
Install Drivers
Fastboot Mode - Blue Light - Turn phone off>Press and Hold Volume UP button while plugging in USB Cable> Release the button (from being held) after the blue light.
Flash Mode - Green Light - Turn phone off> Press and Hold Volume DOWN button while plugging in USB Cable> Release the button (from being held) after the green light.
Common problem is it doesn't stay too long on specific mode
You will need drivers try downloading Xperia Z driver here - http://developer.sonymobile.com/downloads/drivers/xperia-z-driver/
(Optional in case you can't Install the driver correctly)
Install Driver first
1.Extract the downloaded file. (If it is in Zip file) in a place where you can easily locate it.
2.Connect your phone (turned on) to your computer
3. Assuming that you have My Computer Icon on your desktop.. Right Click it > Manage> Device Manager (Located at the left tab) > Android Phone> android ADB interface > Right click> Update Driver Software > Browse my computer for the driver software and locate where you put the XZ driver.
4.Done!.
It worked for me, hope it will work for you, too.
Guys, you can correct me if I am wrong..
Click to expand...
Click to collapse
My major problem is that i never get a blue light when I hold down the volume up and plug it in. My computer makes that sound like a uSB device had been unplugged in a couple seconds.
Also, I download the drivers, and with the device powered on, plug it into the PC. What I see in the Device manager is Sony sa0108 ADB Interface Driver. If I disable adb on the device I get nothing in the device manager.
Flashtool will not allow me to do the adb fastboot reboot either.
This is extremely frustrating!
I've been searching for quite some for the solution but I wasn't lucky to find it anywhere online.
I flashed my phone several years ago with a custom ROM and haven't touched it since then. I unlocked the bootloader, flashed kernel and installed a new ROM as was described in the guide.
However, now when I try to access the bootloader or recovery I just see a black screen and a constant blue LED. On top of that, Windows tells me to "Insert a disc into the drive" when it's connected. The phone is also not recognized by Sony PC Companion or Sony Emma when it's plugged in. Flashtool by Androxyde sits there waiting to detect my phone.
The device, however, is listed in ADB under "adb devices", but "fastboot devices" shows an empty list.
I have tried a different PC just to see if I messed up the drivers, but same thing happens there too.
CORRECTION: Flashtools actually sees the phone, my bad. It identifies it EXCEPT for fastboot drivers (of course while the phone is in fastboot mode).
Any ideas on what's happening and how can I fix this issue?
I think your drivers are not installed correctly. In Windows you need to disable driver signature verification first. Then, you can install the drivers in Flashtool, if I remember it right.
M1chiel said:
I think your drivers are not installed correctly. In Windows you need to disable driver signature verification first. Then, you can install the drivers in Flashtool, if I remember it right.
Click to expand...
Click to collapse
Is it necessary to disable that? I have never had to disable that in order to install drivers for my Android phones. Whenever I try to install the drivers, some of them fail:
http i.imgur dot com/dguUIj6.jpg
http i.imgur dot com/1mTjnp0.jpg
List of drivers I choose to install:
Flashmode Drivers
Fastboot Drivers
Xperia Z3 Compact Device Driver
Yes, at least in Windows 10 you do. It is not difficult.
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
VoltaGe86 said:
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
Click to expand...
Click to collapse
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Sony make.belive said:
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Click to expand...
Click to collapse
Sorry I think I've explained incorrectly. Those are the drivers I've installed, the problem is it only works once.
The second time I reboot the phone into Fastboot mode it doesn't display in device manager. Looking at USBDeview absolutely nothing shows up. Changing USB ports and the cable have no effect, however if I plug the phone into an old USB 2 hub I have then plug that into the computer it will display again in the device manager.