xda-developers Wileyfox Swift Swift General How to set device tampered back to false? by yasteellutch
FORUMS
Remove All Ads from XDA

How to set device tampered back to false?

127 posts
Thanks Meter: 31
 
Post Reply Email Thread
Page 2 of 3 1 2 3
10th January 2016, 07:58 PM |#11  
OP Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly
Quick Reply Reply
 
 
16th January 2016, 04:35 AM |#12  
OP Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Quote:
Originally Posted by cyaneo

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.
Quick Reply Reply
11th February 2016, 09:51 PM |#13  
Senior Member
Thanks Meter: 22
 
More
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?
Quick Reply Reply
The Following User Says Thank You to xfile087 For This Useful Post: [ View ] Gift xfile087 Ad-Free
7th March 2016, 09:38 AM |#14  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by void2000

Probably I have to use a special cable?

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.
Quick Reply Reply
14th March 2016, 02:21 AM |#15  
Member
High Wycombe
Thanks Meter: 6
 
More
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
Quick Reply Reply
15th March 2016, 07:52 PM |#16  
OP Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Quote:
Originally Posted by Pak0St

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
Quick Reply Reply
15th March 2016, 07:55 PM |#17  
OP Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Quote:
Originally Posted by xfile087

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
Quick Reply Reply
27th March 2016, 09:23 PM |#18  
Junior Member
Thanks Meter: 11
 
More
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

Quote:

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(S tring sFileName)

bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownload ArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download

Thanks for response
Quick Reply Reply
24th May 2016, 07:38 PM |#19  
Junior Member
Thanks Meter: 0
 
More
Error
Download failded
Code: 
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Quick Reply Reply
29th July 2016, 06:46 AM |#20  
OP Senior Member
Flag Johannesburg
Thanks Meter: 31
 
More
Quote:
Originally Posted by vadimnew

Download failded

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

You made a mistake @vadimnew
Quick Reply Reply
1st October 2016, 02:00 AM |#21  
Senior Member
Thanks Meter: 195
 
More
Quote:
Originally Posted by yasteellutch

[...] But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. [...]

Which fastboot log files are you referring to? And can't they be deleted as well?
Quick Reply Reply
Post Reply Subscribe to Thread
Page 2 of 3 1 2 3

Tags
brick, fastboot, lollipop, unbrick, wileyfox

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread


Top Threads in Swift General by ThreadRank