[ROM][UNOFFICIAL] LineageOS 14.1 for Wileyfox Swift 2/Plus/X

ShiftyBloke

Senior Member
Jan 13, 2011
144
16
48
Its in the fourth post on this Page. Its a full ROM install recovery file so you will need to extract the bootloader file.
Getting this when trying to flash.

It states Device State is Unlocked, assume there's something I'm missing..

FAILED (remote: Critical partition flashing is not allowed)
 

TedSamol

Member
Jun 5, 2016
18
5
13
Hello there, I flashed the latest version of this ROM (the OTA enabled one) on the Swift 2 Plus and now I cannot turn on the flashlight from the quick settings. Apart from that I can use it as a flash from the camera app just fine. Also, great work! Now with the OTA integration the ROM is much better!
 
Last edited:

LenAsh

Retired Forum Moderator
Mar 20, 2011
4,746
4,709
0
Midlands, UK
Hi all, just installed the 20171121 build after update the bootloader and radio part from 249H fastboot image and work smoothly, thanks for the tips in the last pages ! ;)
For the clarity of others, you did this from the stock ROM:

  • fastboot flash radio NON-HLOS.bin
  • fasboot flash bootloader emmc_appsboot.mbn

Or something else?

Was the bootloader locked or unlocked before and after?
 
  • Like
Reactions: ShiftyBloke

Zanfib

Member
Oct 24, 2011
7
2
0
Colmar
www.famille-link.fr
Yes LenAsh, for the whole story :

My Wileyfox Swift 2X has the "original" CyanogenMod version from Wileyfox. I have unlocked the bootloader for flash TWRP in recovery and the LineageOS 13 version from the other thread. A good start ! When this version 14.1 come to life I tested the ROM with it without update the radio and bootloader part from official nougat and worked like a charm.

I've seen the need to update the bootloader for the last 14.1 Lineage ROM and downloaded the last wileyfox fastboot image (version TOS249H) and execute the flash-radio.sh script (I run Linux), including modem, aboot and splash from nougat.

And All works perfectly !
 
  • Like
Reactions: LenAsh

ShiftyBloke

Senior Member
Jan 13, 2011
144
16
48
For the clarity of others, you did this from the stock ROM:

  • fastboot flash radio NON-HLOS.bin
  • fasboot flash bootloader emmc_appsboot.mbn

Or something else?

Was the bootloader locked or unlocked before and after?
Thanks for clarifying those points. I'm still struggling to flash the bootloader saying its not writable, but its unlocked?
 

image45

Senior Member
Nov 16, 2014
563
78
0
York
Yes but there seems to be an issue with the flashlight not working from the pulldownmenu. It still works within camera, but not when doing hdr+ or something... So I guess this will be related...
OK, I never had that on the November build however I had random apps closing on me still so I returned to the October build and this issue stopped for me.
 

VBCerobil

Senior Member
Jul 19, 2017
91
104
0
35
Zwevegem
OK, I never had that on the November build however I had random apps closing on me still so I returned to the October build and this issue stopped for me.
It seems to be camera related... Been trying a few builds now with backports of things that could cause this error but so far, no success...
 

image45

Senior Member
Nov 16, 2014
563
78
0
York
It seems to be camera related... Been trying a few builds now with backports of things that could cause this error but so far, no success...
The October build is totally solid for me, no apps have force closed and I have even run it on all radio/ bootloader versions too with no issues on WiFi or 4g data.
 

image45

Senior Member
Nov 16, 2014
563
78
0
York
I can't flash the later bootloader either... suggestions welcome
If you don't wish to change the bootloader you can change the bootloader version in the updater-file to the one on your device then TWRP will not trigger error 7 and should install the ROM for you.

I did this as I am on final marshmallow bootloader and don't wish to change.

Everything is working fine for me.

From my earlier post:

For your information I unpacked the new build and edited the updater-script:-

Code:
 This package is for device: marmite,omni_marmite; this device is " + getprop("ro.product.device") + "."); ) ;
assert(getprop("ro.bootloader") == "marmite-13-gd77d4b8" || getprop("ro.bootloader") == "marmite-N-g5531d45" || abort("This package supports bootloader(s): marmite-13-gd77d4b8, marmite-N-g5531d45; this device has bootloader " + getprop("ro.bootloader") + "."); ) ;
I replaced one of the bootloader versions with my own (marmite-13-gd77d4b8) , then re-compressed full files into a new recovery. zip file that I flashed successfully with currently no issues.
 
Last edited:

LenAsh

Retired Forum Moderator
Mar 20, 2011
4,746
4,709
0
Midlands, UK
That worked... still puzzled why I can't flashboot a bootloader. I fastboot flashed 249H to get the phone working then flashed the 21/11 version of Lineage. I had previously flashed that without modding the updater script. My version of the bootloader is marmite-N-ge8bbd8f whatever that's from.

The stock recovery version of 319H posted here soft bricks the phone, BTW.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone