[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Swift

[jrior001]

[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Swift

[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */[/COLOR]

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.

More detailed instructions at:
Install LineageOS on crackling
IF YOU ARE CURRENTLY RUNNING LINEAGE 15.1 w/ENCRYPTION A FULL DATA FORMAT WILL BE REQUIRED TO MOVE TO 16.0. AN ISSUE WITH ENCRYPTION WAS FOUND IN 15.1 THAT CANNOT BE CORRECTED WITHOUT A FULL FORMAT

Official Download link:
LineageOS Downloads

Recommended Google Apps package:
Open GApps (choose the variant you want)

Changelog:
Changes for crackling

Bug reports:
How to submit a bug report

Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS

XDA:DevDB Information
LineageOS, ROM for the Wileyfox Swift

Contributors
jrior001, mikeioannina, 115ek
Source Code: https://github.com/LineageOS

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x

Version Information
Status: Nightly

Created 2019-04-15
Last Updated 2020-03-29

 

[morita11]

@jrior001 Thats great news. Thanks for all your hard work! Much appreciated.

Can you say some words about the encryption problem? What was wrong with LOS' 15.1 way of doing it?
I saw you reverted the GPS blobs. Does that mean GPS fixing is faster now?

Edit: As to my question that I posted initially: Seems the problem is in front of the screen, found the answer already...

 

[jrior001]

@jrior001

Can you say some words about the encryption problem? What was wrong with LOS' 15.1 way of doing it?

I saw you reverted the GPS blobs. Does that mean GPS fixing is faster now?

We missed a change in 15.1 prior to it shipping that pretty much put every legacy device using he encryption in a bad place that can't be recovered from.

For gps, yes it does seem to be locking faster and tracking better while driving.

Sent from my Mi MIX 2S using Tapatalk

 

[Obscurax]

Patiently waiting for feedback before I update the phone of my wife. She's still using LOS 14.1, is it possible to update to LOS 16 (the phone is encrypted)?

 

[jrior001]

Patiently waiting for feedback before I update the phone of my wife. She's still using LOS 14.1, is it possible to update to LOS 16 (the phone is encrypted)?

Its possible that may work, but it is not a tested and supported upgrade scenario. I would highly advise taking every necessary backup precaution should you attempt that.

Sent from my Mi MIX 2S using Tapatalk

 

[lem22]

What is the latest bootloader LineageOS works with?
I can confirm that it doesn't boot when coming from the last stock firmware:

ro.build.display.id=TOS373K - N2G48B

 

[zappbrannigan62]

Regarding TWRP

Thanks a lot @jrior001 for giving us LineageOS 16!

Before I update, I have a few questions regarding TWRP:

1. What's the difference between the TWRP version linked in the wiki and the official one? When upgrading to 15.1, the official version did not work
2. Will TWRP be able to read encrypted partitions or does it still suffer form the problem you mentioned here: https://forum.xda-developers.com/showpost.php?p=77967754&postcount=111

Regards,
Zapp

 

[jrior001]

Thanks a lot @jrior001 for giving us LineageOS 16!



Before I update, I have a few questions regarding TWRP:

1. What's the difference between the TWRP version linked in the wiki and the official one? When upgrading to 15.1, the official version did not work
   
2. Will TWRP be able to read encrypted partitions or does it still suffer form the problem you mentioned here: https://forum.xda-developers.com/showpost.php?p=77967754&postcount=111
   

Regards,

Zapp

The one from the wiki decrypts 16.0 and 14.1 but nothing will decrypt 15.1.

Keep in mind the big red note in the OP if you are encrypted on 15.1, a full wipe/format will be requited to move to 16.0.

Sent from my Mi MIX 2S using Tapatalk

 

[kabu83]

Upgrading to 16 directly from 14.1 worked for me, no issue with encryption :good:

 

[ArmiDuctor]

Awesome guys. Finally we have gps again. Thanks thanks thanks.

I did run into an issue today. I was making videos and photos of hawaiian hula performance and after that of my girlfriend with a beautiful hawaiian sunset in the background. It turned out to be to much beauty for the phone as it rebooted when trying to make a photo. After the phone turned on again all the videos and photos where nowhere to be found. That is all the info i can give at this moment. When i find out more i will give an update.

Update: The reboots occur very frequently when using the photo app. I have to say that I flashed over LOS 15.1. Am I the only one with these issues or can other people confirm the bug?
Update2: Just saw that I had HDR enabled. That might have been the problem.

 

[indianahorst]

I got a similar problem:

after upgrading from 15.1 to 16.0 following the howto under - removed - I get sometimes - it doesn't seem to be correlated with the use of a certain app - a very annoying crash:

The display goes black, then it shows the Lock Screen for one second, then it goes dark again... and so on.
There is no other solution than opening the case, removing the battery, putting the battery back again and then starting the phone.

This is a really really annoying bug, much more annoying then the occasional reboots of LineageOS 15.1.

Please fix that. I am willing to support the develpers with any informations, if somebody tells me what to do.

 

[NotATechnician]

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.

More detailed instructions at:
Install LineageOS on crackling

I followed the instructions from the link exactly and now I have spent the long weekend looking to fix:
"Failed to mount '/system' (No such device)"

I installed TWRP (3.3.0-0) per this post (https://forum.xda-developers.com/wil...1/post72537703) and I am trying to install lineage os, which fails with:
"Updater process ended with ERROR: 7"

And then the above in response to "Updating partition details".

 

[jrior001]

I followed the instructions from the link exactly and now I have spent the long weekend looking to fix:

"Failed to mount '/system' (No such device)"



I installed TWRP (3.3.0-0) per this post (https://forum.xda-developers.com/wil...1/post72537703) and I am trying to install lineage os, which fails with:

"Updater process ended with ERROR: 7"



And then the above in response to "Updating partition details".

The latest recommended twrp is linked on the lineage wiki, https://wiki.lineageos.org/devices/crackling/install

If you still get errors, please post the entire message. "ERROR 7” is a general assert failure but if you read the rest of the message it usually tells you why it failed. If it doesn't make sense post it here or pull the recovery.log and post that here for me.

"adb pull /tmp/recovery.log" will pull the log.

Sent from my Mi MIX 2S using Tapatalk

 

[NotATechnician]

The latest recommended twrp is linked on the lineage wiki, https://wiki.lineageos.org/devices/crackling/install

If you still get errors, please post the entire message. "ERROR 7” is a general assert failure but if you read the rest of the message it usually tells you why it failed. If it doesn't make sense post it here or pull the recovery.log and post that here for me.

"adb pull /tmp/recovery.log" will pull the log.

Thanks! I did "fix" it in the meantime...

For the record, the version of TWRP is the latest (at current time of writing). But for anyone else stumbling on the thread for a fix..


I took the heavy-handed approach, not only wiped the /system partition, but reformatted as ext4 (it was previously splashfs)

Flashed Lineageos 16, GApps-9-arm64.nano, and the root add-in, wiped Dalvik and Cache, reboot to System.

But it only rebooted to Bootloader, no matter how I did it. So then I flashed crDroid4.7 just because it was in the folder even though I knew nothing about it. Wipe Dalvik&Cache, reboot to system and happy days, it chugged for a while before giving me a new set-up experience.

So, I flashed the Pie crDroid (5.3) and I am off to the races. crDroid is LineageOS based, so do not ask me why one boots and the other does not, but my Crackling Wileyfox has life again. So, I am somewhat using LineageOS and very grateful for all the people who put the work in.

 

[kabu83]

For the record, the version of TWRP is the latest (at current time of writing).

Might be that the latest version is not the latest 'recommended' version of TWRP? Have you tried 3.2.3.0?

 

[FtCat]

Might be that the latest version is not the latest 'recommended' version of TWRP? Have you tried 3.2.3.0?

Latest, 3.3.0-0, works for me with no issues.

Sent from my Wileyfox Swift using XDA Labs

 

[dedaol]

Is this rom SELinux Enforcing?

 

[jrior001]

Is this rom SELinux Enforcing?

Enforcing is mandatory on lineage officials.

Sent from my Mi MIX 2S using Tapatalk

 

[RoterfuX]

I can't get it working, it always fails at 47%. I tried different builds and it's always the same problem. I format the data and wiped cache & system before I did the sideload. TWRP version is the one from the lineageos wiki.
Any idea what could be the problem?

Thanks!

C:\WINDOWS\system32>adb sideload lineage-16.0-20190429-nightly-crackling-signed.zip
serving: 'lineage-16.0-20190429-nightly-crackling-signed.zip' (~47%) adb: failed to read command: No error

Edit: found this link https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 and I'll try it tomorrow again.

Edit2: didn't work. Copied the build and opengapps Pico to the SD card and flashed it via TWRP. Worked and the phone runs again.

 

[oliverjames]

Persistent mobile network issue

I upgraded from 15.1 to 16.0 at the first opportunity. Upon returning to France from a trip to neighbouring Switzerland I saw that my French mobile service had automatically switched to piggy-backing on it's Swiss roaming partner. This has cost implications and so I've now restored my previous installation of 15.1.

The problem I have with ver. 16 is that I cannot manually select the mobile network. Has this affected anyone else?