Easy steps/screenshots to install Windows drivers for FastBoot to work with XA2 Ultra - Sony XA2 Ultra Guides, News, & Discussion

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.

Related

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus Player Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Hello Nexus Player users. NRT has supported this device for a little while but I never had a dedicated thread.
This device is definitely the most unique of the Nexus lineup - so lets try and keep the posts in this thread specific to this device alone.
Enjoy!
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
haeffnkr said:
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
Click to expand...
Click to collapse
You don't need a mouse, the root is fully automated in this release.
Sent from my Nexus 5X using Tapatalk
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
haeffnkr said:
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
Click to expand...
Click to collapse
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
WugFresh said:
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
Click to expand...
Click to collapse
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
haeffnkr said:
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
Click to expand...
Click to collapse
Very nice software indeed, thanks WugFresh, had that issue multiple times, when you get the screen that adb doesn't detect device, give it a minute or two and hit continue and it should redetect it. hope it helps. I think installed driver is fine.
confirmed adb doesn't see device once you hit the temporary twrp.
worked really well, thanks for the software!
I had issue initially connecting to the player it took me couple of tries/toggles of adb (developer tools) to get the USB to recognize, and one time of hard boot while unlocking for no reason it just hung there but the device was unlocked.
upsame problem exactly as people above.i can unlock my nexus player but says adb device recovery was not found.and i have android device in device manager working properly.i've tried everything and not new to rooting phones,tablets or any device that can be rooted and romd.
update switched to another pc and worked fine.thanks
Thanks so much for this application! Worked like a charm on Windows 8.1 and Windows 10. Flawlessly installed TWRP after i flashed the purenexus recovery which is bad.. It got stuck after installing the flash for some reason.
twrp 3.0 not available and it wont proceed with out it.. can you help?
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
serpentxx said:
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
Click to expand...
Click to collapse
Any luck finding the twrp 3.0.0.0 recovery?
unfortunately not, i ended up using SkipSoft toolkit which installed an older TWRP for the latest official rom, seemed to work without issue, and once installed apparantly the twrp recovery can self update itself
Now that twrp is available again, I have a question.
I was having some success using this tool to root when I was interrupted by the lack of recovery image and that's a good thing I think because it gave me time to look into things a bit more. When rooting do I need to be able to navigate the twrp recovery? I ask because the instructions I've seen say a OTG cable and mouse are needed in twrp, which I don't have and I will need to order one online since there don't seem to be any retail stores in my area with one. I'd just hate to get stuck half way through this thing when I'm really just trying to root so I can get my ouya games running on the Nexus player.
EDIT: Have tried again and was unsuccessful. Downloaded the latest TRWP from the other section of the Nexus Player forum and it rejected it as a bad hashcode. Looks like the app will need an overhaul to deal with changes in where files are located before it will continue to be useful. Frustrated. I was under the impression the Nexus line of Android devices were supposed to be easy to root and unlock--so far they've been anything but for me.
Where can I download the file TWRP-3.0.0.0-fugu.img ?
Where can I download the file TWRP-3.0.0.0-fugu.img ?
The file on the twrp site dont work.
I just got it working with the current TWRP-3.0.0.0-fugu.img.
Download "3.0.0-0" from the TWRP site.
Rename the file to "3.0.0.0" (remove that "-").
Copy file to (program path)/Nexus root toolkit/data/Recover_custom/TWRP.
Then run the tool. It'll think it already downloaded the file.
BTW, I had a LOT of issues with the ADB drivers. Easiest fix I found, was delete the driver in device manager, then unplug/plug in device. Didn't think I'd ever get past that first TWRP screen.
Here's the link to download the 3.0 TWRP.img for nexusplayer.
https://dl.twrp.me/fugu/

Can't seem to get past the stuck at 50% Bootloader unlock issue.

In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
stefipant said:
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Click to expand...
Click to collapse
You still have problem, unlocking your device?
Sent from my Xiaomi Mi 5 using XDA Labs
vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
abelmaster said:
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
Click to expand...
Click to collapse
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Click to expand...
Click to collapse
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
abelmaster said:
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
Click to expand...
Click to collapse
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
vgdoc said:
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
Click to expand...
Click to collapse
Thanks for posting your link, this helps me find it quick. Now one last question (I hope . Where can I find/download the version 9 driver?
"Google USB driver" in the SDK tools application. That is the version 9 driver.
vgdoc said:
"Google USB driver" in the SDK tools application. That is the version 9 driver.
Click to expand...
Click to collapse
When I type SDK tools application into windows menu bar nothing pops up, so i guess you mean the android sdk manager?
{
"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"
}
But where in the SDK manager can I "google" (or do you mean "search") for something?
In SDK manager did you install tools > Android sdk tools and tools > Android sdk platform-tools ?
If not try to install them, then check you can detect your device with adb tools :
connect your phone with usb
windows key + r
in prompt enter cmd
go to your adroid sdk platform-tools directory with "cd" command
then type "adb devices"
Your device should be find
Here an example :
Code:
cd /D F:\android\sdk\platform-tools
F:\android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
74a9b5b5 device <<<<<<<<<<<<<<<<<<<
If you do not see your device there is something wrong, try to install this pack from xda :
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It worked for me.
If it still not work after installation usb driver from xda have a look in the miFlashunlock log directory, open the MiFlashUnlock.log file and check the error.
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
I'm convinced it's impossible.
I've done a clean install of all the drivers (either via SDK or the minimal adb packs), tried doing what crim did... Still stuck on 50% error. Mind boggling stuff.
vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
same problem guys plz help me
---------- Post added at 02:43 AM ---------- Previous post was at 02:04 AM ----------
dkmsn8 said:
same problem guys plz help me
Click to expand...
Click to collapse
ok i did it guys thanks
Crim Soukyuu said:
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
Click to expand...
Click to collapse
I dont know why this worked, but it did. Finally! I tried this method a couple of times and the fourth time it works. Have to say that mi unlock did not install the driver for me, I searched for it online with the built in windows driver update. It gave me the kedacom one again, but it worked!
vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
eros1on said:
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
Click to expand...
Click to collapse
and i believe other guys with this problem can also solve it via this method.
i solved it by;
1.disable internet coonection cause of auto update driver
2.uninstall kedacom driver, select delete files.
3.update driver manually and select let me pick driver.
4. choose usb composite device than try "fastboot oem-devices" command .
if it shows your device. unlock wont be stuck at %50.

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!

Device not detected in Fastbootmode.

SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"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"
}
TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:
TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty
TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...
Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)
See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution
reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Also I got this from continually trying to boot:
TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?
TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.

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.

Categories

Resources