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
Related
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
nacef_l said:
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
Click to expand...
Click to collapse
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
LetMeKnow said:
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
Click to expand...
Click to collapse
I just tried that but it did not work, windows is still displaying USB device not recognized.
nacef_l said:
I just tried that but it did not work, windows is still displaying USB device not recognized.
Click to expand...
Click to collapse
What Windows version are you running?
You may have to uninstall the drivers for your MTP device before installing new ones as well as disabling Windows to automatically install drivers for a new device, then manually point it to the Universal Naked Drivers folder.
Or downlaod Android SDK tool ad through it the Platform Tools and USB drivers.
BTW: When you flashed the stock firmware you lost your custom recovery. That's why you see the dead Droid - it's the stock recovery.
If you can't get fastboot to work you can use Motochopper to root your JB 4.1 stock firmware and then GooManager to install the latest TWRP recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
nacef_l said:
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
Click to expand...
Click to collapse
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
berndblb said:
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Yes checked and double checked that
nacef_l said:
Yes checked and double checked that
Click to expand...
Click to collapse
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
nacef_l said:
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
Click to expand...
Click to collapse
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
berndblb said:
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I don't have a dock and I am connecting directly with the cable. I have just reflashed it to stock rom again hoping it resolves itself but nothing.
It's driving me crazy. The stock rom is really sluggish and I want to flash it to CM
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
sbdags said:
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
Click to expand...
Click to collapse
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Sent from my iPhone using Tapatalk - now Free
Had the same problem.I fixed it by uninstalling the faulty usb device. Then disconnected the usb cable. Reconnected. And the drivers installed.
nacef_l said:
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Click to expand...
Click to collapse
Im having the same problem and after one day of research I could not find a solution. I bought a use TF700 with a standard andriod on it, no mod, not unlocked, no root. When I connect it to the pc I get the same error, meaning just a USB Device showing up. Tried different PC's with different types of OS, no success.
Did you manage to fix the problem ? I would really appreciate some help because now I can't use that tablet in debug mode to test my android applications and that's all I bought it for. By the way, is there a adb tool that works wireless and doesn't neet root access or can I get root access without connecting my pad to my pc ?
Thanks for the help !
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
berndblb said:
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
Click to expand...
Click to collapse
First of all thanks a lot for your response, didn't think anyone would still react on that post because it's quite old. Yes I did install adb fastboot drivers, the device only shows up in the usb section saying usb device not recognized. I tried nearly every driver I found, installed the Andriod SDK, the Asus Sync Tool, the naked drivers... then removed them all (including the hidden ones) and installed just the adb fastboot -> no success. I have not tried it on linux, but on windows 7, 8 and 10. Android version is 4.2.1 and Build is 10.6.1.14.10. I now unlocked it using the apk provided by asus (version 7 , 8 did not work). Still for rooting I need pc connection, so I ordered a new cable today (cable is original Asus though).
I installed the Rom Manager and that tells me the ClockworkMod Recovery and TWRP are already installed. I also tried that recovery (power + vol) and got the same result as nacef meaning " I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign." Thing is, I don't know what the previews owner did, so it might be the reason he sold the Tablet. Can I get anywhere form that Bootloader ? Maybe boot as a Superuser and then use wireless adb to root the device ?
Thanks a lot for your help, Im feeling that I have wasted the money and the only way to get rid of that feeling is to fix the problem
Grab the Puppy Linux live CD from here: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It has adb fastboot already installed. If you don't get a connection with that one the problem would be tablet side, not Windows related.
I booted using that Puppy Linux and followed the Guide but no success. After entering "adb devices" I get the output "list of adb devices attached" and than a blank space. So I tried booting in fastboot like you described in your guide and entered "fastboot devices" but that also gives me nothing. Fastboot works though (as it's already included in that image) so I tried a bunch of other fastboot commands but that just results in "waiting for the device".
I don't know what to do now, it has something to do with the tablet itself. Im waiting for the new cable but don't think thats gonna change anything.
You are not trying to do this through the dock port, right? You are connecting the tablet directly to the PC?
The only answer I have left is either a broken cable or one of the pins in the port is bent or broken. Get a magnifying glass and check them out.
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.
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.
Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly
Hello, did you try typing in `fastboot devices` while in fastboot ?
-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
triteshy said:
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
Click to expand...
Click to collapse
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
niteStalker09 said:
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
Click to expand...
Click to collapse
Thank you for the response. Did both of those things already.
triteshy said:
Thank you for the response. Did both of those things already.
Click to expand...
Click to collapse
Just making sure but you do have the latest platform-tools?
I've never actually experienced it not being detected in fastboot before so that's really the only solution I can think of.
So just for some one in the future trying to figure out what happened. I managed to get it fixed.
The problem I was running into was that my computer recognized the driver (the regular oneplus driver that you can install when you plug in your phone) only when my phone was using adb (or in other words, my phone was on, in a usable state, in the regular OS, not fastboot or anything).
However when I launched into fastboot, my computer would no longer recognize my phone as the same device.
To fix:
I had to open file explorer on my pc (running windows), then right click "my pc", then manage devices.
There was my phone, right there, but under "unknown device". I right clicked it, and installed a driver for it, however I didn't use the oneplus driver, I used the Samsung phone drivers. It then worked perfectly.
I know that's not good directions but it still may help someone in the future and save them from a horrible headache that I experienced, at least pointing them in the right direction.
GLHF.
I had this happen to me as well. Was driving me nuts. I had to use a different cable. The wrong cable solution usually never works, but for some reason, my older USB-C anker cable would work in ADB but not fastboot. Newer Anker cable worked. I'm sure the OEM cable would work too.