Database Info

[Guide] Flashtool/Fastboot ADB Driver Fix For Windows 8/8.1 ~ By Nero Young ~

Only For Xperia Devices​
Intro :
If you are trying to flash custom Kernal/ROM and getting an error of your device not been detected by your PC running on windows 8 then you will need to install the USB/ADB/Device drivers for your handsets.
This can be done by using following tutorial.
!! UPDATE !!
Date : 20 - April - 2014
Those who are on windows 8.1 and having trouble to install drivers will have to download and install windows 8.1 update from here http://support.microsoft.com/kb/2917929 and once you install that you can follow this guide.
Step 1 :
Suppose you are trying to install custom Kernal on windows 8 and you stuck at this screen and nothing happens even if you connect your device in fastboot mode then its due to missing 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"
}
Step 2 :
So now lets get started. Press "Start Key/Windows Key + C" or move your cursor to top right corner of the screen to activate the Charm Bar and click on "Settings Button" as shown in following figure.
Step 3 :
Now the setting panel will open. Click "Change PC Settings" from the bottom as shown.
Step 4 :
Now you will have this PC Settings screen.
Now click on General Tab. and scroll down to the bottom to find "Advance Start up Option" as shown below and click on Restart. This is immediate restart so make sure all programs are closed and saved.
Step 5 :
Your PC will reboot into Advance Start Up option. And you will see following screen. Now simply press on "Troubleshoot" option.
Step 6 :
In troubleshoot click on "Advance Options" .
Step 7 :
In advance option select "Start-Up Settings" .
Step 8 :
Now just press restart button in Start-Up settings as shown below. Your system will reboot in Start-Up Option Mode.
Step 9 :
Now after your system is rebooted you will get this following screen. Here to choose options we have to use function keys. Now press "F7" to select "Disable Driver Signature Enforcement" .
Now your PC will boot with Disabled Driver Signature Enforcement and you will be able to install Flashtool/Fastboot drivers.
You can get this drivers from Post #2.

Flashtool/Fastboot Drivers
Installing Flashtool/Flashboot Drivers​
Step 1 :
Download the Flashtool/Fastboot Drivers from this link.
[Xperia Device] Flashtool & Fastboot Drivers.zip
And extract it using winRAR or 7zip software.
Click on "[Xperia Device] Flashtool & Fastboot Drivers.exe".
Step 2 :
Setup will start, Click Next.
Step 3 :
Scroll down in selection panel and tick Fastboot dirvers and flastool drivers and click Next.
Step 4 :
Now pop up drivers installation menu will appear. Click Next to proceed.
A red alert Allow box will appear, simply allow it and install the drivers. Do this until the driver installation finishes.
Finally, check which drivers are succeeded in installation from final screen, it will have green right tick if installation is succeeded.

Thank You Very Much
Nice to see you around btw

@neroyoung
the wuala link is dead, could you please reload ?

irontech said:
@neroyoung
the wuala link is dead, could you please reload ?
Click to expand...
Click to collapse
Link Updated

i didi it ..... tanQ

cant find a word to thank you enough, i am so grateful

I did everything and it didn't work
I'm on windows 8.1

Yap - in win 8.1 RTM - this trick didn't work - still "enumeration failed".

Anyone found a solution for Win 8.1 RTM ?

me to waiting for 8.1 otherwise have to go back to previous version

I need this for Win 8.1

i have revert back to 8. but just now saw a post in xda below. can someone try and post feedback here?
" I think I found a solution, at least for my case with a Rockusb device and windows 8.1:
It seems that there is a usb root hub driver for every usb connected device. after I connect mine and disable driver signature it says device not recognized, so I uninstall the corresponding "USB-Root-Hub" under "USB-Controller" in device manager. my corresponding "USB-Root-Hub" was, for some reason that I don't know, the 3rd one from the bottom. as soon as i deleted it, it recognized the device normally and I can use fastboot again with windows 8.1."
http://forum.xda-developers.com/showpost.php?p=44288852&postcount=24

ok good new guys!!!!!!!!!!!!!!!!!!!!!! i did install 8.1 and tried the method i have posted above. and it did work not the 3rd USB-Root-Hub worked for me but i did uninstall several and even mouse stared not working but then it did work. so i repeat what i did..
first thing after flash 8.1 was i went to disable driver signature . then went into device manage and turn off my phone and connect it. as usual message came "device not recognized," so i did uninstall the Usb controll. u can see triangular mark there. then uninstall USB-Root-Hub. i didn removed several then i install flashtools and then installed drivers inside flashtools. yeahhhhhhhhhh and all works now
try your self guys

I tried the above method.
Phone is connected in flashmode but not in fastboot.
Am I doing something wrong ? Is there any way to flash kernel in flashmode ?

mathewgx said:
I tried the above method.
Phone is connected in flashmode but not in fastboot.
Am I doing something wrong ? Is there any way to flash kernel in flashmode ?
Click to expand...
Click to collapse
u need fastboot to flash kernel. are u sure u installed fastboot drivers??

Yes , I installed flashmode and fastboot drivers , from drivers folder of flashtool directory. But , my phone is only recognized in flashmode , even if I connect it while pressing up volume button ( that is fastboot for xperia ray).

mathewgx said:
Yes , I installed flashmode and fastboot drivers , from drivers folder of flashtool directory. But , my phone is only recognized in flashmode , even if I connect it while pressing up volume button ( that is fastboot for xperia ray).
Click to expand...
Click to collapse
Well i know this is some confusing. anyway my phone is RAY too. after doing above mentioned method mine is working fine. by the way i did it in a fresh install of Win 8.1. and the first thing after install i did it to check if it work or not. so i dont know if u can do the same.
suggest you to try again. if u can post a screen pic of you device manager

When I connect my RAY , is always recognized as flashmode (SEMC flash device at device manager).
But in win 8 , there is a Sony Ericsson seehcri Control Device at device manager when in fastboot. So , I think that is the river i'm missing.

guyss help... i have successfully flashed the mobile.... but when i try to switch it on.. the red led blinks but the mobile doesnt start up... when i put it in charge, green light is on.. i tried powering on while charging still no luck...

Driver for windows 7 or 8.1

hi guys my oneplus drivers can be install, try on wins 7 and 8.1 both dont work.
i followed all the guides and came to a dead end.
The guide said look for 'android device' in device manger, i cant find it, see pic .
Thanks, help would be grateful!
{
"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"
}

power on your phone.
disable android debugging.
install http://www.koushikdutta.com/post/universal-adb-driver
restart your computer
plug phone in
manually direct it to the universal adb driver.
operating system has nothing to do with your drivers not working.

hey buddy, how do i manually direct it to ADB?
i open device manger, selected update driver, try to find ADB , but the file was not there. i already install and restart my pc.
could it be the problem with my phone? Do advice thanks

lolitsryan96 said:
hey buddy, how do i manually direct it to ADB?
i open device manger, selected update driver, try to find ADB , but the file was not there. i already install and restart my pc.
could it be the problem with my phone? Do advice thanks
Click to expand...
Click to collapse
use this link to download samsung driver.
1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done

1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done[/QUOTE]
hmm, i cant find the ADB man, i already unistall any kind of adb and reboot pc.

luka1002 said:
1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done
Click to expand...
Click to collapse
lolitsryan96 said:
hmm, i cant find the ADB man, i already unistall any kind of adb and reboot pc.
Click to expand...
Click to collapse
What you can not find? in device manager?

1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done[/QUOTE]
cant find andriod device,

luka1002 said:
1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done
Click to expand...
Click to collapse
lolitsryan96 said:
cant find andriod device,
Click to expand...
Click to collapse
Try from recovery, and then connect your device.
try differend cable / USB port on computer

luka1002 said:
Try from recovery, and then connect your device.
try differend cable / USB port on computer
Click to expand...
Click to collapse
from recovery?

lolitsryan96 said:
from recovery?
Click to expand...
Click to collapse
jup. Turn off your phone. Press vol down + power (hope you have some custom recovery) and try to plug in to your computer.
Before that you could search in device manager for unknown devices...

I just use the Google Driver for everything, works fine

luka1002 said:
jup. Turn off your phone. Press vol down + power (hope you have some custom recovery) and try to plug in to your computer.
Before that you could search in device manager for unknown devices...
Click to expand...
Click to collapse
yeah, i ahve TWRP recovery, still cant get the correct drivers, i follow all methods, on windows 8.1 and 7. nothing seems to work. pissing me off man.

so , i turn off using that method and how to serch for device?
after that whats the next step? thanks for helpin my out

luka1002 said:
use this link to download samsung driver.
1. remove any ADB driver
2. install this one
3. reboot
4. Manually update driver from device manager (when device connected) (Go to Device Manager, find the Android device, and select Update Driver Software
5. Select ADB Interface from the list
6. Select SAMSUNG Android ADB Interface
Done
Click to expand...
Click to collapse
i just love you for this one!

bender_8 said:
i just love you for this one!
Click to expand...
Click to collapse
:good:

[UBL][NOOB-Friendly] Xperia M2 Bootloader Update FTFs (New update available)

Hey guys!
Since there was no thread about it yet, and since Sony released recently a new bootloader update for the Xperia M2, I decided to open a new one, and explain a little more how it works.
The bootloader update is used, in the Xperia M2, to unlock the R/W features in the recovery partition. This means that, if you've an UBL device, and you flash the update, you'll get permissions to install a new UBL recovery inside the partition itself. So, you won't need to include an external ramdisk inside your boot image.
How can I obtain it?
You've currently 2 ways:
1. Download and install Emma and apply the update from there, which will be always the latest available.
2. Download it through an FTF (explained below).
How can I install it if I choose FTF way?
First, download the latest FTF from below. Once downloaded, place it in flashtool's firmware folder, which is located in C:\Users\<your-name>\.flashTool\firmwares\.
Now, launch Flashtools (it needs to be version 0.9.18.6 or below, mandatorily), choose the FTF update (you'll easily notice which one it is), and simply hit flash.
Once prompted, connect your device while off to the Micro-B end of the USB cable, and, while you press & hold the Vol- key, connect the USB-A end to the PC. Then flash will start.
How can I install a custom recovery?
Download my ADB Pack 'Herramientas-de-flasheo.zip'.
Now, unzip my ADB Pack 'Herramientas-de-flasheo.zip', which contains basic ADB and Fastboot executables to a folder in your desktop. Also, copy the file Recovery file you downloaded to that folder.
Put your phone in Fastboot mode, this means, while pressing and holding the Vol+ button, connect the USB cable. Once the Led goes blue, stop pressing it.
Now, execute the following keyboard shortcut (Win+R) and type inside the Run prompt CMD. Inside the Command Prompt, using CD (change directory), navigate to the folder you created in the desktop. It'll be something like...
Code:
cd C:\Users\linuxct\Desktop\adbpack\
Now, execute the following command:
Code:
fastboot flash recovery <[COLOR="Purple"]NAME-OF-THE-RECOVERY[/COLOR]>.img
How can I access the recovery?
To enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the Sony logo, stop holding the Vol- Button.
DOWNLOAD: Latest Bootloader Update FTF [ver 1.716]
--------------------
DOWNLOAD MIRROR: Latest Bootloader Update FTF [ver 1.716]

Amazing work as always @linuxctt
Maybe be our Cyanogenmod 13 maintainer...? I'll walk my self out

There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy

imzihad said:
There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy
Click to expand...
Click to collapse
That's the one I commonly use, but I found easier the one I wrote in the tutorial

Thanks
Thank you Linuxct, It works as always.
Do i need install Ric disabler this time?

Can I update D2302 with this

I can't see any file in the flashboot firmware selector dialog box.
{
"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"
}

nishchayv said:
I can't see any file in the flashboot firmware selector dialog box.
Click to expand...
Click to collapse
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...

linuxct said:
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...
Click to expand...
Click to collapse
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.

nishchayv said:
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.
Click to expand...
Click to collapse
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.

linuxct said:
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.
Click to expand...
Click to collapse
Thanks fo your help. BTW I have downloaded version 0.9.18.6 from this linkhttps://drive.google.com/file/d/0B1AAC4lt7nzOQzR3aTZKUFZqem8/view?pli=1 and it's working fine for me.

hi, I have stock kitkat so can i still update my bootloader using flashtool, i have root and unlocked bootlloader

Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37

gabrielmr said:
Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37
Click to expand...
Click to collapse
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.

linuxct said:
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.
Click to expand...
Click to collapse
It worked, I just started Flashtool in administrator mode.

Flashtool and Emma gives a hard time (Jul 2016)
Hi,
Same as gabrielmr... Emma installed, seems to update and restart, and then disappear in the background. Ok, then I'll use flashtool. Oh wait, there is a new version, before all, I'll update it and then flash the ftf. So I updated to latest version and... no way to see that firmware. If I had read the tread closely, I would have seen that flashing with Flashtool Version 0.9.19.8 would have taken 2 seconds, instead of trying my best to use the last flashtool version, which doesn't show the downloaded firmware XPERIAM2_1.716_BOOTLOADER_UPDATE_(ONLY_OPEN_DEVICES).ftf.
Just saying for noobs following the procedure.:cyclops:

Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance

aleksa069 said:
Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance
Click to expand...
Click to collapse
Basically yes only for unlocked bootloader devices

Hey, i have got problem with Flashtool. AVAST Says, that version have malware. Can someone send my that version witchout malware?

Hello, it will work with Xperia m2 dual d-2302?,
Thanks in advance
Sent from my D2302 using Tapatalk

Impossibility to istall flashtool driver on Win10

As i wrote in the title.
I'm facing the impossibility to istall driver needed for flashtool usage.
I already istalled flashtool and driver (located inside driver folder)
To do this i have used the "disable driver signing enforce" mode in windows 10.
But when i connect my XZ premium in flashmode i still have an unrecognised device in system.
And i receive the same error "windows found the driver but an error occured" if i try to manually istall SOMC flash device driver
this happen in normal mode and with driver verify mode disabled.
ADB and fastboot havw the same problem but i solved it disabling the driver signature verification
Still can't solve the problem with flashtool driver

Evil_Sephiroth said:
As i wrote in the title.
I'm facing the impossibility to istall driver needed for flashtool usage.
I already istalled flashtool and driver (located inside driver folder)
To do this i have used the "disable driver signing enforce" mode in windows 10.
But when i connect my XZ premium in flashmode i still have an unrecognised device in system.
And i receive the same error "windows found the driver but an error occured" if i try to manually istall SOMC flash device driver
this happen in normal mode and with driver verify mode disabled.
ADB and fastboot havw the same problem but i solved it disabling the driver signature verification
Still can't solve the problem with flashtool driver
Click to expand...
Click to collapse
You need more than one USB driver, there is the Sony drivers, as well as the Google ADB driver, if you're going to go into recovery.
It's really tiresome all these different drivers and sometimes Windows just picks the wrong one at random. So don't be surprised that the driver that windows says you need has to be forced manually into something different.

Didgesteve said:
You need more than one USB driver, there is the Sony drivers, as well as the Google ADB driver, if you're going to go into recovery.
It's really tiresome all these different drivers and sometimes Windows just picks the wrong one at random. So don't be surprised that the driver that windows says you need has to be forced manually into something different.
Click to expand...
Click to collapse
i have done it, fastboot work fine, i also istalled twrp without problem..but i'm now without system and i need flashtool to flash a stock ftf or a zip to flash in recovery.
and it seems i can't use flashtool no matter what
{
"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"
}
this is the error i get....phone connected in flashmode but no way to fix that driver error.

Evil_Sephiroth said:
i have done it, fastboot work fine, i also istalled twrp without problem..but i'm now without system and i need flashtool to flash a stock ftf or a zip to flash in recovery.
and it seems i can't use flashtool no matter what
this is the error i get....phone connected in flashmode but no way to fix that driver error.
Click to expand...
Click to collapse
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
As I said, Windows chooses the wrong driver by default nd you have to manually correct it.
You don't have a device that's different from everyone else, so you just need to experiment until it works, don't give up.
Edit: but if you're having this much trouble installing drivers, should you really be trying to force new firmware on your phone?
If flashing goes wrong you can brick your phone, just sayin.

Didgesteve said:
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
As I said, Windows chooses the wrong driver by default nd you have to manually correct it.
You don't have a device that's different from everyone else, so you just need to experiment until it works, don't give up.
Edit: but if you're having this much trouble installing drivers, should you really be trying to force new firmware on your phone?
If flashing goes wrong you can brick your phone, just sayin.
Click to expand...
Click to collapse
i've done it till 10 days ago....and now i have this problem, and i don't know why
Btw it's already without system, but i still have a working twrp and unlocked bootloader.
Even selecting different driver i still receive that error.

Didgesteve said:
You go to the device drivers, while the phone is plugged in, update the driver, then add a different driver using the .inf file from from a different driver folder.
Click to expand...
Click to collapse
sorry to revive this but how one is supposed to add the .inf from a diff driver folder? you mean from here?:

OnePlus 8 T-Mobile Conversion Problem

Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"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"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!

Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.

SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.

Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!