My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen OS ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could use all adb commands on this device even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason? I encountered a similar thread on OnePlus 5/5T but unsolved.
Download tool and enjoy again
ashish_jha said:
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen OS ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could use all adb commands on this device even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason? I encountered a similar thread on OnePlus 5/5T but unsolved.
Click to expand...
Click to collapse
Probably test on another computer and check. If so, then reinstall ADB drivers and retry. i am sure it should work.
mm_rajesh said:
Probably test on another computer and check. If so, then reinstall ADB drivers and retry. i am sure it should work.
Click to expand...
Click to collapse
Thanks buddy. I re-installed sab driver and it worked !
Related
Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?
Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?
I went into USBDeview and uninstalled everything that was android related
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
How do i enable usb debugging without any os?
dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??
good to know
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue
Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?
If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.
Hello,
Had the phone for 2 years, and I was using a Google Pixel UI. I had some problem with phone auto rebooting while not in use. So I decided to install MUI, but I forgot its only in Chinese without google play.
So I have tried to install the TWRP recovery, but the fastboot is not recognized by the computer.
I have tried Xiaomi Poco X3, and fastboot its working fine on it. So its not issue with the cable.
I have installed some drivers, but it didnt help. I have tried most of the options, so not sure what I'm missing. Will try tomorrow, a different PC at work. MiFlash also cant see it.
Thanks for any help.
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Any leads on the above problem guys?
Disable driver signature enforcement and download mi flash tool. It will prompt you to install all the drivers. Install them and check if it works. For me this was the solution. Another solution is to download the latest drivers from android at https://dl.google.com/android/repository/platform-tools-latest-windows.zip for windows and install it manually by using device manager. This fixes are of course only for windows
On my PC, I didn't try other devices in fast boot mode but I know that my redmi note 7 pro wasn't displaying even after installing those Google/phone drivers.
It eventually worked when I opened Device Manager and saw that my phone was showing as Unknown Device; I clicked on the option to update the driver from a folder on my PC, so I selected the folder containing the android_winusb.inf file and it worked
sumitsky33 said:
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Click to expand...
Click to collapse
If you get solutions then please tell us
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP