Database Info

[Q] Fastboot blues on the Moto X: is this the end?

Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?

Factory reset doesn't even work, I get "no valid piv block in sp for system"
I just ran mfastboot erase cache and at the command prompt I get:
(bootloader) Failed to erase partition
FAILED: Remote failure
The phone screen says, 'Failed to erase partition cache'
This doesn't sound good.... Is there anyway can get this thing booted?

Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong.
I've decided to return it. I think my data is lost.

Can't unlock bootloader

I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.

ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?

Any ideas guys?

aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.

zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?

aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk

zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.

Stuck at "Launching flashstock.bat"

So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.

This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...

dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Just trying to help, beekay...
Thanks for the link - I'll read it carefully.

dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.

No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...

This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not

mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them

mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk

While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...

[HELP] XT1563 Bricked after trying to root it

After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?

If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.

TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?

MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:

TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.

Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)

Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB

Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.

Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards

krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.

Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.

krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.

Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards

SOLVED

krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8

Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?

mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.

Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)

I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.

If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.