Develop Bugs

How to set device tampered back to false?

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

problem install driver MOOREFIELD

Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you

Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.

Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)

The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.

htc desire d820n hard bricked

Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.

George_Samy said:
Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.
Click to expand...
Click to collapse
Carefully read it can help you with https://forum.xda-developers.com/de...n-restarts-continuously-t3548182#post71073715

My case is almost the same, but mine isn't detected for Windows (neither adb nor loader).
I had disconnected the battery, but without any results.
Any idea?

Clamp all 3 buttons and hold 1 minute. What happens?

vuk1963 said:
Clamp all 3 buttons and hold 1 minute. What happens?
Click to expand...
Click to collapse
n
Unfortunately, nothing

How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the task manager on the computer to choose the interface adb to install the driver, specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY

vuk1963 said:
How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
All started when the phone isn't capable to install the official update to 6.0.
I decided to try other ROM's, opening the boot loader and installing the TWRP recovery. All goes well, but the ROM that are working better (Tomal - Discovery 2.00) had problems with my LTE networks.
Reading one of your post, I started to try to install the official 6.0, but I forgot to wipe the system before relock the bootloader.
After trying flash different RUU files through fastboot I used one from easy firmware: (0PFJIMG_A51_UL_K44_DESIRE_SENSE60_Orange_ES_1.28.75.5_Radio_01.01.010_U10305041_08.01.41222_2__combined_signed.zip) that belong to my CID (Orange Spain)
Then the phone don't respond to anything...
I will uninstall all drivers and programs and restart according your instructions...
Click to expand...
Click to collapse

vuk1963 said:
lcarrasc said:
Yes, sadly, you need to restore the bootloader,and it's very difficult to do it yourself http://4pda.ru/forum/index.php?showtopic=643084&st=7060
Click to expand...
Click to collapse
Thanks. I understand that my phone is lost
I tried to use QFIL (romkingz.net/2016/07/how-to-use-qualcomm-flash-image-loader) but the computer hasn't recognised the phone...
Click to expand...
Click to collapse

Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.

lcarrasc said:
Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.
Click to expand...
Click to collapse
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?

vuk1963 said:
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?
Click to expand...
Click to collapse
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.

lcarrasc said:
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.
Click to expand...
Click to collapse
I also run Windows 10 х86 and in Device Manager has a ports (COM and LРТ)

What it's expected to find in the com ports?

lcarrasc said:
What it's expected to find in the com ports?
Click to expand...
Click to collapse
Something like: Qualcomm HS-USB QDLoader 9008 port com

The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.

lcarrasc said:
The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.
Click to expand...
Click to collapse
Clamp all 3 buttons and hold 1 minute,and try different variants combinations with holding the volume buttons + and - and the power button,with the connection of the phone to the computer and to the power unit

I tried all possible combinations of buttons, and nothing...
Any idea?

Unbrick guide for 5T

Is there a OP5T unbrick guide? Or is it the same as the OP5?

nikolajkracht said:
Is there a OP5T unbrick guide? Or is it the same as the OP5?
Click to expand...
Click to collapse
I'd start by looking through this other question thread: https://forum.xda-developers.com/oneplus-5t/help/please-help-hardbricked-oneplus-5t-t3716057

OnePlus 5T unbrick tutorial
Link - http://www.oneplusbbs.com/forum.php?mod=viewthread&tid=3836845&extra=page=1&filter=typeid&typeid=136

would you please bring this tool because he need replay in fourm i cannot all chinese i try to register but i cannot
thankyou

GUIDE FOR UNBRICK ONEPLUS 5T:
This guide will fix all brick problems INCLUDING bootlocked, oem locked. It will fix the "Your device is corrupt and will not boot" problem. It will also works if you flashed the Oneplus 5 phone and ended with a upside-down screen, unusable touch screen.
guide inspired by https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Use the following file for unbrick (Msmdownloadtool)
https://mega.nz/#!QOJjGYRT!oLL9gRKQF9sE1PcVl241WvMQL-dhBaG24T5-ixo2pzs
It includes a Windows-only flasher and a recent OPS file.
Usage:
- Poweroff your phone (keep the power button for 40 seconds)
- Hold the volume up button for 10 seconds
- Connect USB-C cable
- Open device manager and ensure you have a "Qualcomm 9008 (COM3)" listed in Com ports. I had no driver to install (Windows 10).
- Unrar the 2GB file. It contains no error
- open the "dumpling_43_O.06_171206" folder
- Launch "MsmDownloadTool V4.0.exe"
- Click "Verify"
- Wait for "Md5 Check Ok!"
- Click "Start"
This will completely wide your device (oneplus 5T only !) and reinstall EVERYTHING (OxygenOS 4.7.2). The phone reboots automatically.
It will fix all brick problems.

thank you i will tested
thank you i will test it .

EDIT 2 : The MSM Download Method worked for me! Thanks !
Did it work ?
https://androidfilehost.com/?fid=889964283620773422
If you want to try out the second method! (downloading right now to test it, since my device is unusable after oreo update...)
EDIT : Second method did help a bit but phone is still unconscious. Trying the MSM Download Tool right now

diminou91 said:
EDIT 2 : The MSM Download Method worked for me! Thanks !
Did it work ?
https://androidfilehost.com/?fid=889964283620773422
If you want to try out the second method! (downloading right now to test it, since my device is unusable after oreo update...)
EDIT : Second method did help a bit but phone is still unconscious. Trying the MSM Download Tool right now
Click to expand...
Click to collapse
were u on 128GB or 64GB version?

Bradl79 said:
were u on 128GB or 64GB version?
Click to expand...
Click to collapse
I have the 64GB version of OP5T, but I'm guessing the files are the same since we use the same OOS update. Should work for the 128GB version too

thankyou

Thank yo elwin94 ! It worked like a charm !
Thank A LOT !!!

Doenst work for me, sahara communication fails.

BazzBeater said:
Doenst work for me, sahara communication fails.
Click to expand...
Click to collapse
U need to check ur drivers

what do I do if the QUALCOMM 9008 is not listed?

brendonppagel said:
what do I do if the QUALCOMM 9008 is not listed?
Click to expand...
Click to collapse
make sure the drivers are installed
it should look like below
How To:
Code:
Step 1: Download Driver and Unbricktool
Step 1: Extract Drivers and Recovery Tool files on Desktop.
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
Step 6: Right Click on your device in the device manager and select Update Device Software. Choose manually the drivers folder and install the driver.
Step 7: When the device shows as "Qualcomm 9008", go run the MSM Download Tool as administrator.
Step 8: Click start at top left corner and wait for it to finish (green text will come).
Step 9: Disconnect phone from PC and boot into system.

elwin94 said:
GUIDE FOR UNBRICK ONEPLUS 5T:
This guide will fix all brick problems INCLUDING bootlocked, oem locked. It will fix the "Your device is corrupt and will not boot" problem. It will also works if you flashed the Oneplus 5 phone and ended with a upside-down screen, unusable touch screen.
guide inspired by https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Use the following file for unbrick (Msmdownloadtool)
https://mega.nz/#!QOJjGYRT!oLL9gRKQF9sE1PcVl241WvMQL-dhBaG24T5-ixo2pzs
It includes a Windows-only flasher and a recent OPS file.
Usage:
- Poweroff your phone (keep the power button for 40 seconds)
- Hold the volume up button for 10 seconds
- Connect USB-C cable
- Open device manager and ensure you have a "Qualcomm 9008 (COM3)" listed in Com ports. I had no driver to install (Windows 10).
- Unrar the 2GB file. It contains no error
- open the "dumpling_43_O.06_171206" folder
- Launch "MsmDownloadTool V4.0.exe"
- Click "Verify"
- Wait for "Md5 Check Ok!"
- Click "Start"
This will completely wide your device (oneplus 5T only !) and reinstall EVERYTHING (OxygenOS 4.7.2). The phone reboots automatically.
It will fix all brick problems.
Click to expand...
Click to collapse
I can't thank you enough! You saved my ass today good sir!!

Bradl79 said:
make sure the drivers are installed
it should look like below
How To:
Code:
Step 1: Download Driver and Unbricktool
Step 1: Extract Drivers and Recovery Tool files on Desktop.
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
Step 6: Right Click on your device in the device manager and select Update Device Software. Choose manually the drivers folder and install the driver.
Step 7: When the device shows as "Qualcomm 9008", go run the MSM Download Tool as administrator.
Step 8: Click start at top left corner and wait for it to finish (green text will come).
Step 9: Disconnect phone from PC and boot into system.
Click to expand...
Click to collapse
does your phone goes in fastboot mode, or this is not really for those devices which are not really dead but just want to restore it

dryspuri said:
does your phone goes in fastboot mode, or this is not really for those devices which are not really dead but just want to restore it
Click to expand...
Click to collapse
this is for if u cannot go into fastboot mode or if u cannot load ur OS through fastboot, if u are in fastboot mode the qualcomm driver will not show up, u have to power ur phone off completely and hold the vol up button for 10 sec, then plug in ur cable, ur screen will still stay black and u will see the qualcomm driver show up, then u will open the msm tool

Thanks that did the trick.
Sent from my BKL-L09 using Tapatalk

Hi! friends, can someone help me please, some of you have a download link that is not MEGA?

{Solved}I gotta super slim brick !!!!

I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175

mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?

Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.

Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?

LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???

Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens

LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?

Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?

LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question