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

HELP!!! Hard Brick Hydrogen

My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys

seti007 said:
My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys
Click to expand...
Click to collapse
What happens by trying to go into TWRP?
Enviado desde mi MI MAX mediante Tapatalk

I flashed eu rom yesterday?
What exactly happened??

Thanks for the answer guys following are my responses.
Albertkuba said:
What happens by trying to go into TWRP?
Absolutely nothing happens with any button combination. The screen remains dark. When I unplug the battery and plug it back in ic the computer recognizing it as an edl device 9008
Enviado desde mi MI MAX mediante Tapatalk
Click to expand...
Click to collapse
hassan_eldhraawy said:
I flashed eu rom yesterday?
What exactly happened??
Click to expand...
Click to collapse
I had Nigel's lineage ROM running perfectly on my phone. I got an itch to Try out the new MIUI 9. Downloaded the latest ROM and then the latest Superuser. Installed both of them and tore up. The ROM installed fine without any error messages. While installing SuperSU the phone just died. it was plugged into power so not sure why the screen just went dark.

Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...

nijel8 said:
Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...
Click to expand...
Click to collapse
Thank you Nigel for your input. I will give this a try and get back with you.

Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(

seti007 said:
Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(
Click to expand...
Click to collapse
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...

nijel8 said:
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...
Click to expand...
Click to collapse
You have a keen eye Nigel. Yes I messed up the first time and used the wrong folder. Afterwards, I tried this with the proper folder with the correct firmware from the link you provided. Tried putting it in root drive and renamed the folders so there were no spaces. Even tried a newer fastboot firmware but still the same result. Looking around on google, apparently the Sahara error is very common and no real solution.
Thanks again for your help Nigel.

Hi Nigel, I'm wondering if you or anyone else who feels up to the challenge would be willing to work on this phone? I can send it to you with a self addressed envelope. I'm willing to pay for your time. I have exhausted all options but nothing has helped. would be great to have my phone back . If anyone is willing to take me up on this, please pm me. Thanks

PLEASE HELP H815 HARD BRICK no fastboot, no 9008 and no recovery USU

Hi People,
I manage to brick my LG G4 H815.
The phone was fine and I flashed this https://forum.xda-developers.com/g4/development/rom-h-rom-g6-port-t3660459 after that my phone simply didn't turn on not even an LG logo only black screen but it does vibrate when I try to power it up. When I plugged it into the PC I get nothing t doesn't detect the device at all.
I tried the 9008 drivers and still nothing.
PLEASE HELP!
*edit: also forgot to mention also download mode doesn't work*

if it's bricked you can force it to qualcomm 9008 mode by shorting the test point pins then use qfil

nardndoka said:
Hi People,
I manage to brick my LG G4 H815.
The phone was fine and I flashed this https://forum.xda-developers.com/g4/development/rom-h-rom-g6-port-t3660459 after that my phone simply didn't turn on not even an LG logo only black screen but it does vibrate when I try to power it up. When I plugged it into the PC I get nothing t doesn't detect the device at all.
I tried the 9008 drivers and still nothing.
PLEASE HELP!
*edit: also forgot to mention also download mode doesn't work*
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212
When your device is UsU'd as your title suggests ensure you follow post 2 there as well
Sent from my OnePlus 6T using XDA Labs

qfil problem
steadfasterX said:
https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212
When your device is UsU'd as your title suggests ensure you follow post 2 there as well
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
I got my phone to a 9008 state, installed the drivers QPST with vcredist and NET Framework I replaced the files like you mentioned the USU files and I get this weird error in the log file
-
Start Download
Program Path:C:\Users\Jon\Desktop\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
-

Ok. I fixed it now thanks

nardndoka said:
Ok. I fixed it now thanks
Click to expand...
Click to collapse
what did you do ?

Sahara error

I'm getting Sahara error on qfil and I've tried the latest Mi flash tool which keeps on responding packet error I'd appreciate if a little help was given...

Bravin Joshua said:
I'm getting Sahara error on qfil and I've tried the latest Mi flash tool which keeps on responding packet error I'd appreciate if a little help was given...
Click to expand...
Click to collapse
Qfil app latest version

Bravin Joshua said:
I'm getting Sahara error on qfil and I've tried the latest Mi flash tool which keeps on responding packet error I'd appreciate if a little help was given...
Click to expand...
Click to collapse
on zuk z2if your device is detected correctly and you are getting saraha error there are only following reasons
1 disable driver signature/ or use test mode win 10
2 install drivers and use latest qfil
3 you did not run qfil as admin
4 you are taking too long to click download after inserting in the device (set all the parameters connect phone and click download asap)

Question [SOLVED] Bricked OP9Pro, can't get to fastboot, sahara communication failed

Seems like I succesfully bricked my OP9Pro. Tried to restore in MSMDownloadTool v4.0. Oneplus 9 Pro LE2123.
Phone is detected correctly in Windows device manager(QDLoader 9008, I get to EDL by holding Vol+ and Vol- buttons and connecting the cable). When I try to flash, MSM breaks on Sahara communication failed(FH: 258).
Qualcomm drivers are from Windows Update Center(I connect my phone in EDL mode, click Update and in optional updates section there is the needed driver - Qualcomm Incorporated - Ports).
What should I do?
I saw a python EDL workaround script, but I'm not sure if helps me or if it even works (saw it somewhere on xda, the only thing I remember that it was in some of oneplus's devices thread and the sript name was edl.py, sorry
Tried on one laptop(Acer Nitro< none of the ports gave a succesful result). Gonna try on my second(Asus ROG GL702VMK, it seems to have better ports connection). Gonna write an update message.
I can't get to fastboot, recovery, etc. Phone seems to give no signs of life, there is even no charging notification when the cable is connected(but maybe phone isn't turned off actually, not sure)

You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using

Shooter7889 said:
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Click to expand...
Click to collapse
Thanks for advice, I got further but now it stopped on Param Preload with "Device not match image"
I use MSMDownloadtool for EU and my phone is EU version(LE2123)

So, I am kinda happy cuz I booted to system.
I used this guide(https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/). Used MSM Download tool with Indian f/w.
Then I tried to return to EU version, but I got the same param preload error. I used this version of MSM and it flashed successfully.
So now I guess the issue is solved. Thanks @Shooter7889 for ur advice with lite firehose

Uncheck "check sha256" for mismatch device issue. Or find correct msm. You're welcome. I had same issue after bricking my 9pro and not being able to run msm successfully.