How to set device tampered back to false?

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
I will explain how to set the device tampered back to "false" on the Wileyfox Swift.

Required:

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]
 
Last edited:

cyaneo

Senior Member
Jul 15, 2011
58
10
0
Saltcastle City
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
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".
 
Last edited:

cyaneo

Senior Member
Jul 15, 2011
58
10
0
Saltcastle City
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.
 
Last edited:

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
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.
 

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
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".
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.
 

xfile087

Senior Member
Apr 21, 2006
237
22
0
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?
 
Last edited:
  • Like
Reactions: Dior DNA

fa_a2z

New member
Feb 25, 2016
1
0
0
Probably I have to use a special cable?
Hi,
This is my first post. (active lurker previously):p 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.
 

Pak0St

Senior Member
Dec 15, 2015
61
8
0
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 ;)
 

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
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 ;)
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
 

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
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?
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
 

andikicker

Member
Feb 24, 2012
34
42
0
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
Thanks for response