Database Develop

Unable to get OP3T recognized in ADB/FASTBOOT( tried everything )..help!!

Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!

Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?

redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?

Easy steps/screenshots to install Windows drivers for FastBoot to work with XA2 Ultra

10/26/2019 update (also posted at the end of this thread):
I was having trouble Using NewFlasher v19 with the "H3223_Customized US_1312-1380_50.2.A.0.400_R2B" firmware I downloaded and extracted with XperiFirm. I kept getting the following:
(short version: occasionally the Sony driver doesn't work for me to flash the latest official update. On those occasions I update the driver in Device Manager to the GordonGate driver that Newflasher provides, and then it works fine, but other times if I just go straight to GordonGate, then it doesn't work either, so go figure. At least it works one way or the other, just depending on I don't know what. )
Code:
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
This was on a relatively new (almost three months old) Windows 10 build 1903 installation, so I hadn't flashed my H3223 on this Windows build yet. I had installed without trouble the same XZ2 driver (they haven't updated it) but no luck. Finally I tried NewFlasher's GordonGate option, I extracted the archive, pointed Device Manager at this folder for the Sony ADB driver and it installed just fine. After that, NewFlasher flashed this just fine. I don't recall ever needing the GordonGate driver, nor it even working when I had attempted it previously.
I was still able to use the XZ2 driver to fastboot boot TWRP.img.
Just FYI if this helps anyone.
Click to expand...
Click to collapse
The following is my original post (if the above new instructions don't get you what you need, or if you need help installing the XZ2 driver in order to boot TWRP - I have no idea if NewFlasher's GordonGate driver would make it so that you could boot TWRP.
I hope this guide with both text descriptions and screenshots for every step can help anyone who had trouble with the driver installation steps. They're not difficult steps, but on three PCs that I installed the drivers on, I found the description of the method to be just a little different than what some users experienced, so please note that you may have a slightly different experience, and this post is not meant to mean that this is the only way to get the Xperia XA2 Ultra drivers installed.
Also note that I have the H3223 model (one of the two "Discovery" types, just in case there are any differences in experiences for those with different variants, as well.
Click to expand...
Click to collapse
Please use this thread for all variants, however, as long as it is regarding the installation of drivers.
First the thanks:
Sony for making their devices bootloader unlockable and being developer-friendly.
@LuK1337 for building official TWRP for the "Pioneer" types of The XA2 Ultra, which at least for 'fastboot boot TWRP.img', works great on the "Discovery" variants as well.
@Chainfire for [BETA][2017.10.01] SuperSU v2.82 SR5, which works great on the ROM v50.1.A.5.59_R6A.
@topjohnwu for Magisk, which I know others are using and I may have to switch to when this device is updated to Android 8.1+, as I know from personal experience SuperSU doesn't work on the 2016 Pixel on Android 8.1, at least not by straight flashing the zip.
@li0nh3art3d and @AngryManMLS for leading me down the path of being able to successfully install the correct drivers, in this thread Unlocking Bootloader/Rooting
If I missed anyone, please let me know and I'll correct ASAP.
Click to expand...
Click to collapse
The steps are (also all instructions and screenshots are available here and below (click on the thumbnails to open larger copies):
1a. Go to the Sony Driver webpage and download Xperia XZ2 driver and unzip it
OR
1b. Go to Xperia XZ2 driver webpage and download the driver and unzip it
2. Put the Xperia XA2 Ultra in Fastboot mode (turn the phone off and disconnect it from any cables, press and hold the Up Volume button, and while doing so, connect the cable from the computer to the phone
3. Right-click on Start Button
4. Click 'Device Manager'
5. 'Device Manager' - 'Other devices'
6. Right-click on 'Android', choose 'Update driver'
7. Choose 'Browse my computer for driver software'
8. Browse or copy-paste path of extracted Xperia XZ2 driver, and choose 'Let me pick from a list of available drivers on my computer'
9. Choose 'Show All Devices', click 'Next'
10. Choose 'Have Disk'
11. Browse to or select in the drop-down menu the path to the extracted Xperia XZ2 driver
12. Click 'OK'
13. Select the only driver that is listed and click 'Next' (on just one of the three PCs I installed the driver to, there were more than one Sony drivers listed, and I'm pretty sure I picked the one that said 'Fastboot' in it in that case)
14. Select 'Yes' at the warning dialog
15. Click 'Close'
16. Observe that Device Manager now lists 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (again, on just one of the three PCs that I installed the driver too, it said something different in that case)

thanx

thank you for this. I couldnt get anything to work until i tried this. very useful

sonyalmarshad said:
thanx
Click to expand...
Click to collapse
Aklenz07 said:
thank you for this. I couldnt get anything to work until i tried this. very useful
Click to expand...
Click to collapse
You're welcome, glad it helps some people.

Hi, This did not work...... (error code 10) when trying to update driver as in your instructions!...... which i thought might happen as youve directed us to the XZ2 driver instead of XA2 ULTRA driver!!!
Where the hell can I find the proper XA2 ULTRA driver?????? ...cant find anywhere...its crazy!!!

jake333at333 said:
Hi, This did not work...... (error code 10) when trying to update driver as in your instructions!...... which i thought might happen as youve directed us to the XZ2 driver instead of XA2 ULTRA driver!!!
Where the hell can I find the proper XA2 ULTRA driver?????? ...cant find anywhere...its crazy!!!
Click to expand...
Click to collapse
There is no XA2 Ultra driver, that's why we have to use the XZ2 one.

First, thank you for the great guide. Now, sorry about the possibly silly question, but I am a bit of a neophyte. I am able to follow these instructions and install the adb driver for the XA2 Ultra (all works as described). However, after I eject the phone and reconnect it while in USB debugging mode to try to use an adb command (to add a permission to write_secure_settings), Windows does not recognize the phone as an adb device. Thus I cannot do anything. I have tried this on two different Windows machines and the result is the same. Please apologies again if this is silly, but I feel I am missing something important. Thank you in advance.

Flaco05 said:
First, thank you for the great guide. Now, sorry about the possibly silly question, but I am a bit of a neophyte. I am able to follow these instructions and install the adb driver for the XA2 Ultra (all works as described). However, after I eject the phone and reconnect it while in USB debugging mode to try to use an adb command (to add a permission to write_secure_settings), Windows does not recognize the phone as an adb device. Thus I cannot do anything. I have tried this on two different Windows machines and the result is the same. Please apologies again if this is silly, but I feel I am missing something important. Thank you in advance.
Click to expand...
Click to collapse
Thanks, and you're welcome! I'm afraid I haven't actually used ADB that much with this phone. Does Device Manager actually list 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (as I noted in the OP, on one or more PCs it said something different, and in a differently-named section)? You may find better help if you create a new thread in the general Q&A section since this problem doesn't deal directly with the driver installation problem that this thread is for. Good luck!

roirraW "edor" ehT said:
Does Device Manager actually list 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (as I noted in the OP, on one or more PCs it said something different, and in a differently-named section)?
Click to expand...
Click to collapse
It does! All goes exactly like your screenshots indicate. But when you eject the phone and reconnect it again in USB Debugging mode, the ADB driver is gone, and you when type 'ADB devices' on CMD, nothing shows, so Windows cannot find it and it's not possible to run any commands. Let me do some more searching prior to starting a new thread.

Flaco05 said:
It does! All goes exactly like your screenshots indicate. But when you eject the phone and reconnect it again in USB Debugging mode, the ADB driver is gone, and you when type 'ADB devices' on CMD, nothing shows, so Windows cannot find it and it's not possible to run any commands. Let me do some more searching prior to starting a new thread.
Click to expand...
Click to collapse
Did you ever have any luck?

roirraW "edor" ehT said:
Did you ever have any luck?
Click to expand...
Click to collapse
Gave up temporarily; until my phone receives the Pie update.
Thanks for checking in!

works also on xa2 standard thank you

stuccamelo said:
works also on xa2 standard thank you
Click to expand...
Click to collapse
Awesome! You're welcome. Glad to help.

Thank you thank you thank you. I was about ready to give up on unlocking bootloader for my xa2 when i found this. Your a lifesaver. Now Ive installed /e/ on 3 devices. i'm 3 for 3 Your data is your data and everyone should take a look at this and ungoogle yourself.

eeloed said:
Thank you thank you thank you.
Click to expand...
Click to collapse
You're welcome!

I was having trouble Using NewFlasher v19 with the "H3223_Customized US_1312-1380_50.2.A.0.400_R2B" firmware I downloaded and extracted with XperiFirm. I kept getting the following:
Code:
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
This was on a relatively new (almost three months old) Windows 10 build 1903 installation, so I hadn't flashed my H3223 on this Windows build yet. I had installed without trouble the same XZ2 driver (they haven't updated it) but no luck. Finally I tried NewFlasher's GordonGate option, I extracted the archive, pointed Device Manager at this folder for the Sony ADB driver and it installed just fine. After that, NewFlasher flashed this just fine. I don't recall ever needing the GordonGate driver, nor it even working when I had attempted it previously.
I was still able to use the XZ2 driver to fastboot boot TWRP.img.
Just FYI if this helps anyone.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hi if anyone can help me install twrp on my xa2 ultra, try all possible methods and it is not possible. jump that error, someone who knows how to fix it? i want root to install lineage 17. thank you very much

maximdq said:
hi if anyone can help me install twrp on my xa2 ultra, try all possible methods and it is not possible. jump that error, someone who knows how to fix it? i want root to install lineage 17. thank you very much
Click to expand...
Click to collapse
I don't think you can install TWRP, but you can:
Code:
fastboot boot twrp.img
to boot it each time you want to use it while connected to your PC where you have the TWRP image named "twrp.img", and the latest Android platform tools (available at https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the same folder as twrp.img. Obviously you have almost all the steps correct, just wanted to spell it out for anyone else with the same problem.

roirraW "edor" ehT said:
I don't think you can install TWRP, but you can:
Code:
fastboot boot twrp.img
to boot it each time you want to use it while connected to your PC where you have the TWRP image named "twrp.img", and the latest Android platform tools (available at https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the same folder as twrp.img. Obviously you have almost all the steps correct, just wanted to spell it out for anyone else with the same problem.
Click to expand...
Click to collapse
sorry I do not understand. I can't install lineone 17 then? I speak Spanish and the translator does not understand well. Thank you

maximdq said:
I don't think you can install TWRP, but you can:
sorry I do not understand. I can't install lineone 17 then? I speak Spanish and the translator does not understand well. Thank you
Click to expand...
Click to collapse
Yes, your can flash anything you want once you "boot" twrp.img instead of "flash" (or install) it. This device probably doesn't have a discreet Recovery partition, same as on the Google Pixel. It's probably a combination Bootloader/Recovery partition, which is why you can't overwrite the recovery, any instead you have to boot TWRP directly each time you want to use it.
I don't speak Spanish although I had two years of it nearly 40 years ago, but let me know if this doesn't help or you don't figure it out, and I'll try to find an adequate Spanish translation for what I'm saying.

Which Qualcomm interface driver for download mode?

Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...

sbsoft said:
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
Click to expand...
Click to collapse
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.

sarath medithi said:
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
Click to expand...
Click to collapse
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?

QFIL Flashing Procedure
sbsoft said:
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
Click to expand...
Click to collapse
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.

sarath medithi said:
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
Click to expand...
Click to collapse
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???

sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
can you share the qfil log or screenshot

sarath medithi said:
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
can you share the qfil log or screenshot
Click to expand...
Click to collapse
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!

sbsoft said:
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
Click to expand...
Click to collapse
Try to update your QFIL.i think there is a new version available. update it and try again. may be it is giving an error due to the programmer file which is an elf file. earlier it is .mbn or .bin file. hope you understand.

Did you succede in using QFIL ? @sbsoft

How to install the correct drivers for fastboot to a Windows 10 laptop?

Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!

Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish

Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!

Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:

Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!

Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!

Question My computer doesn't recognize the phone in fastboot even with drivers installed

Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.

Check in another USB Port, use original xiaomi's wire...and install latest USB drivers

I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)

Yup exact same thing, I hope somebody knows how to fix it and help us out.

Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.

I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!

liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one

liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.

Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.

Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.

seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.

liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.

hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.

download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.