[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-05-20)

[rez78]

Hi i've issue with latest build: if i try to install Magisk, the device go in boot loop. Any solution? Thanks

 

[WheelchairArtist]

can confirm android auto is working with the latest update

 

[.kaputnik.]

My XZ1C began suffering from bad reception coinciding with installing the LOS 17.1 November update iirc. Tnere's of course some uncertainty to exactly when it began, might be that I just happened to notice it then.

I never get LTE connection. Usually I'm getting HSPA with weak reception. Often it falls back on Edge, even in densely populated areas, where I used to have LTE iirc.

Been updating when new updates has been released, installed the February one today. There's been no noticeable difference between updates.

To me it looks very much like there's something up with the antenna connections. Assuming those are some kind of non-soldered variant. I've also had the phone in a far from dry jacket pocket when skiing in sub-optimal weather conditions earlier this winter. However, since opening the phone to check/clean those connections certainly will ruin the ingress protection, I thought I'd ask if there are any software things that potentially could cause these problems to check first?

When on Edge, it almost always helps to restart the phone to get HSPA again, which gives me some hope that it possibly could be something software related after all.

If relevant, carrier data from the Sony modem notification after boot:

Config: amss_fsg_lilac_tele2_sweden_ims_tar.mbn
Cust ID: 34

 

[tjlawson09]

Great

 

[Arcline]

My XZ1C began suffering from bad reception coinciding with installing the LOS 17.1 November update iirc. Tnere's of course some uncertainty to exactly when it began, might be that I just happened to notice it then.

I never get LTE connection. Usually I'm getting HSPA with weak reception. Often it falls back on Edge, even in densely populated areas, where I used to have LTE iirc.

Been updating when new updates has been released, installed the February one today. There's been no noticeable difference between updates.

To me it looks very much like there's something up with the antenna connections. Assuming those are some kind of non-soldered variant. I've also had the phone in a far from dry jacket pocket when skiing in sub-optimal weather conditions earlier this winter. However, since opening the phone to check/clean those connections certainly will ruin the ingress protection, I thought I'd ask if there are any software things that potentially could cause these problems to check first?

When on Edge, it almost always helps to restart the phone to get HSPA again, which gives me some hope that it possibly could be something software related after all.

If relevant, carrier data from the Sony modem notification after boot:

Config: amss_fsg_lilac_tele2_sweden_ims_tar.mbn
Cust ID: 34

For a start you could try the following things:
1. Check your APN
2. Dial *#*#4636#*#* > Phone Information > Then change "Set preffered network" to LTE only, then see if that works. When it does, revert it to how it was before.
3. Clean flash a different rom/variant of this rom.

 

[victor126]

My XZ1C began suffering from bad reception coinciding with installing the LOS 17.1 November update iirc. Tnere's of course some uncertainty to exactly when it began, might be that I just happened to notice it then.

I never get LTE connection. Usually I'm getting HSPA with weak reception. Often it falls back on Edge, even in densely populated areas, where I used to have LTE iirc.

Been updating when new updates has been released, installed the February one today. There's been no noticeable difference between updates.

To me it looks very much like there's something up with the antenna connections. Assuming those are some kind of non-soldered variant. I've also had the phone in a far from dry jacket pocket when skiing in sub-optimal weather conditions earlier this winter. However, since opening the phone to check/clean those connections certainly will ruin the ingress protection, I thought I'd ask if there are any software things that potentially could cause these problems to check first?

When on Edge, it almost always helps to restart the phone to get HSPA again, which gives me some hope that it possibly could be something software related after all.

If relevant, carrier data from the Sony modem notification after boot:

Config: amss_fsg_lilac_tele2_sweden_ims_tar.mbn
Cust ID: 34

if you think its hardware. flash the original sony firmware. see it works properly.

 

[victor126]

just did a clean install. will try out the apply modem feature this week when i drive to my sons job. usually drops connection on the way there.

so far so good.
been to bristol connecticut twice now where with past builds i would lose cell and not reconnect without a reboot 50% of the time. so far no loss of connection.

 

[victor126]

so far so good.
been to bristol connecticut twice now where with past builds i would lose cell and not reconnect without a reboot 50% of the time. so far no loss of connection.

spoke to soon. lost signal going to hartford connecticut today and it did not reconnect until i rebooted.

 

[jurkoman]

LineageOS 17/18/19 for Sony Xperia XZ1 Compact

RELEASE

This is an alternative ROM for the Sony Xperia XZ1 Compact.

Creating this to honor the great work of modpunk and derf elot from https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ which seems to be discontinued. Posting an own thread to keep the latest versions visible, I'm NOT claiming authorship over the ROM.
I basically just build the ROM using the latest changes from upstream LineageOS/Google and kernel updates (usually incorporated by derf elot ) See my post.

FEATURES

• Signed with dev keys
• EAS kernel
• Passes SafetyNet out of the box (thanks Rooted_Ansh, Havoc-OS Team and kdrag0n)
• Seedvault (Video)
• IMS support (thanks to Rooted_Ansh and also Shujath)
• 17.1 has stock Sony camera (not possible on 18+)

DOWNLOAD

You can download the latest release here.
HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
Make sure you download the right version, vanilla LineageOS is named lineage-*UNOFFICIAL-lilac.zip while the MicroG version is named lineage-*-MICROG--lilac.zip

REQUIRED FIRMWARE: 47.2.A.11.228

IMPORTANT: I only test the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and hopefully work. I only test them roughly.
Backup download

INSTALLATION

IMPORTANT: Magisk seems to cause issues (bootloops) on update, so remove it first and reinstall if required. Note that Magisk is usually not required unless you want root.

1. Put the zip file of the ROM on your SD card or internal store and boot into recovery.
2. When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". Do not wipe system! When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
3. Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
4. After updates you may now wipe cache&dalvik (option after install)

I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
TWRP 3.3.1-0 by modpunk / derf elot
Or use the latest TWRP for 17.1/18.1 or TWRP for 19.1.
3.7.0 Seems to work well with latest updates (decryption working) but LineageOS 19.1 (Android 12) requires the ones with "_12" suffix, e.g. 3.6.2_12.

For ease of use I suggest to flash this recovery (only required once):

1. Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
2. Flash TWRP by running this on the PC: fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
   (adjust the filename if necessary)
3. From now you can boot TWRP by turning on the phone with "Volume Down" + Power

I heavily recommend to make a full backup before any installation so you can go back in case of issues. Flashing an older ROM usually helps to recover bootloops etc.

Upgrades between versions​

Dirty-flashing (e.g. from 17.1 to 18.1) works well but you have to also flash a GApps version matching the Android version or the device will bootloop.
For the upgrade to 19.1 you may need to fully remove OpenGapps by wiping /system and install e.g. MindTheGapps.

SUPPORT

There is NONE. If you have any issues or question ask in the thread so maybe someone else knows the answer.
I'm just providing the ROM (Lineage 17.1 variant) I use myself for others to try to and just build the Lineage 18.1 ROM without much testing.
If you prefer to use a more well-tested Android 11 ROM, I suggest to look at Havoc-OS.
Contributions to the sources are welcome and likely get integrated into the next release.

Contributors
modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
Source Code: https://github.com/Flamefire/android_device_sony_lilac, Original: https://github.com/whatawurst/

If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
Also please consider donating to the original authors too or to local charities as requested by @modpunk

Special thanks to landsome for donating a test phone for bug hunting and development.

ROM OS Version: Android 10/11/12
ROM Kernel: Linux 4.4.x
Based On: LineageOS
GApps: None included, except for the MICROG builds. Recommended is OpenGApps for 17/18 and MindTheGapps for 19.

Hello, now in latest update of LOS 17.1 for lilac 02/25 (clean install) I am experiencing random UI reboots and one bug:
If i turn off device and turn on (no reboot), system sounds arent working, freeze and FC when i want to set an alarm in clock app or play music, no flashlight, camera cannot start and maybe something else which i havent noticed.
I havent installed any sound fx or something, which can broke system sounds.
It launches like with 80 percent functionality.
After restart, device work flawlessly, but still experiencing random UI reboot.
Comparing to older versions, i see performance improvement and battery lasts longer.
Otherwise, i am very satisfied. Really very nice ROM.
I dont know if someone has similar problems, but this is strange.

 

[paulquappe]

Hi! First of all, thanks Flamefire and everyone else for putting in the effort to keep the XZ1 alive

I've finally found a reason to sign up to these forums, but sadly not a pleasant one: After installing this build, I need to restore my TWRP backup, but even though it includes all partitions, I can only boot the phone if I format `Data`. I have redundancy for my photos, but formatting Data loses all my apps, messages, etc, so I'm looking for a way to recover. Shouldn't Data be restorable even after a format?

Here's what I did:

• Starting situation: Custom LOS with MicroG 18.1 (built myself from the whatawurst repositories)
  • I created a full backup from TWRP 3.5 from this using `adb backup --twrp`
• Dirty-flashed Flamefire's 18.1+MicroG builds from January
• Dirty-flashed Flamefire's 19.1+MicroG builds from January
• Dirty-flashed Flamefire's 19.1+MicroG builds from February
  • I created *another* full backup from TWRP *3.6* from this using `adb backup --twrp`

Up until this point, almost everything worked fine. 4G wasn't working in the 19.1 builds though (happy to debug another day), so I decided to restore my backup. Here's where things went south:

• Restoring my first backup was very unreliable and I had to manually patch up the `archive.ab` file to skip the oem.ext4 and cache.ext4 backups. After restore, the phone boots back to recovery until I format Data
• Restoring my *second* backup worked more reliably, but again my phone boots back to recovery unless I format Data

I have *some* redundancy in case this Data partition is forever lost, but I really wonder what's going on here. Am I out of luck or is there something I'm missindo

I remember some bug where you can't restore a backup on LOS18.1 if screen lock was enabled while the backup was done.
See Quote below:

This may be old news but I have discovered a workaround for the problem in the 18.1 build where restoring a backup kills the device. If you remove all screen locks (PIN, pattern, password) before making a backup, it is possible to restore the backed up data. After restoring, you will then to force stop Trebuchet and clear its data, and evrything should be back to normal. More details in this post in the /e/OS community forums

 

[xdahippo]

I remember some bug where you can't restore a backup on LOS18.1 if screen lock was enabled while the backup was done.
See Quote below:

I disabled PIN/fingerprint lock before taking the backup in both cases.

I've used my SeedVault backup to partially recover in the meantime, but it's really concerning that (what's supposed to be) the "if all else fails" backup is the one that doesn't appear to work at all :/

 

[petefoth]

I hope this post isn't too late...

First, my TWRP backups were all done from within TWRP with the phone running in Recovery, not using `adb backup --twrp` so I don't know if they two methods are functionally equivalent.

Are you able to get back to your original setup (i.e. your custom ROM, with your backup restored?

but it's really concerning that (what's supposed to be) the "if all else fails" backup is the one that doesn't appear to work at all :/

My '"if all else fails" backup' is to backup using Android Backup and Restore Tools project. You need rooted debugging enabled, and access to a Linux machine (real or virtual). I have used these scripts to backup my apps and data and then to

1. Restore to the same device, running the same or different custom ROM
2. Restore / migrate to a completely new / different device

Not everything gets retored - any apps whose account data is handled by Accuont Manager (e.g DAVx5, NextCloud) will lose the account settings, as will K-9 Mail (though you can export your settings before the backup, and re-import them after the restore). See this post in the /e/OS community forums for more information on my experiences with this.

If you can get back to your original setup then this may be worth a try. Good luck!

 

[jurkoman]

Now battery lasted 3 days +20% with 5hrs SOT, very nice ! No gapps.
2 more bugs:
Camera taking blank photos if default storage is set to sd card.
Front camera gives white screen, freezes, FC and then i cant open camera when is flashlight turned on.

Maybe it is related only to Sony camera app, i havent tested other camera apps.

 

[foresto]

I uploaded the new updates yesterday. Took a bit longer than usual especially due to some tricky updates to the kernel and XperiaParts

This update seems to have broken extract-files.sh, preventing a clean build from source. Reported on github as issue 13.

 

[Flamefire]

Hello, now in latest update of LOS 17.1 for lilac 02/25 (clean install) I am experiencing random UI reboots and one bug:
If i turn off device and turn on (no reboot), system sounds arent working, freeze and FC when i want to set an alarm in clock app or play music, no flashlight, camera cannot start and maybe something else which i havent noticed.
[...]
I dont know if someone has similar problems, but this is strange.

I'm using that ROM (17.1) myself on my daily device and haven't encountered any issues at all. So looks like something with your device, not the ROM itself.

Now battery lasted 3 days +20% with 5hrs SOT, very nice ! No gapps.
2 more bugs:
Camera taking blank photos if default storage is set to sd card.
Front camera gives white screen, freezes, FC and then i cant open camera when is flashlight turned on.

Maybe it is related only to Sony camera app, i havent tested other camera apps.

I assume you are (still) using 17.1 as you mention the Sony camera app. I'm a bit confused: Above you said that the camera cannot start.

I just tried to reproduce the other issues: Camera works fine for me, I've always had the default set to SD and front camera does also work. I can imagine issues with camera and the flashlight feature as the former may want to access the light which may be already in use in that situation but it also does work fine for me.
In fact the camera is one of the things I test on a spare device for a new ROM before even installing that on my own phone as a working camera is a good hint that a big part of the system works.

So I can only imagine that there is still something left on your device interfering with the current ROM. If you don't mind loosing your data reflash the Stock firmware with newflasher, TWRP and then this ROM making sure to wipe /data, /cache and dalvik in the process. Or if you don't want to flash stock wipe /system, /cache & dalvik and format /data, then reinstall the ROM (without rebooting TWRP) which might help.
At the very least try wiping /cache & dalvik (keep your data)

This update seems to have broken extract-files.sh, preventing a clean build from source. Reported on github as issue 13.

Answered there (a link to the issue in your post would be helpful as I don't get a notification on GH, but found it anyway): In short: It does work (I always do clean builds, by now 6 times), check your extracted system image

 

[xdahippo]

First, my TWRP backups were all done from within TWRP with the phone running in Recovery, not using `adb backup --twrp` so I don't know if they two methods are functionally equivalent.

Thanks for the reply! I actually think they use slightly different storage formats, so next time backing up to the SD card may be worth a try.

Are you able to get back to your original setup (i.e. your custom ROM, with your backup restored?

Maybe I'm misunderstanding the question, but my problem is exactly that I can't boot the restored backup unless I format the restored data partition... at which point it wouldn't be my original setup anymore. (The backup I created covers all partitions, and adb does not support partial restores)

My '"if all else fails" backup' is to backup using Android Backup and Restore Tools project. You need rooted debugging enabled, and access to a Linux machine (real or virtual). I have used these scripts to backup my apps and data and then to

1. Restore to the same device, running the same or different custom ROM
2. Restore / migrate to a completely new / different device

Not everything gets retored - any apps whose account data is handled by Accuont Manager (e.g DAVx5, NextCloud) will lose the account settings, as will K-9 Mail (though you can export your settings before the backup, and re-import them after the restore). See this post in the /e/OS community forums for more information on my experiences with this.

Yeah I've read about this project after the failed backup as well. Looks like another good line of redundancy in addition to SeedVault and partition backups.

For now I've come to accept that the original data partition is just lost forever despite my best attempt at creating a proper backup. I was kinda hoping there'd be some takeaway lesson here like "If you format Data once, restoring old backups won't work anymore [for some reason]" to explain what went wrong. But it looks like my best bet is trying to back up to SD card rather than through adb in the future and cross fingers that'll work better

 

[Ephesus]

Thanks Flamefire for keeping the device alive.
I am using 19.1 MicroG and getting great battery life.


I did a clean flash of 19.1 2023-02-25 MicroG from stock and I can't seem to find the settings for MicroG and don't see it listed in the system apps.
When I check in /system/product/priv-app I see the folder for GmsCore and the fake store, but there is no apk in it.
Is there additional setup needed in order to get MicroG working?

 

[Flamefire]

I did a clean flash of 19.1 2023-02-25 MicroG from stock and I can't seem to find the settings for MicroG and don't see it listed in the system apps.
When I check in /system/product/priv-app I see the folder for GmsCore and the fake store, but there is no apk in it.
Is there additional setup needed in order to get MicroG working?

Looks like something went wrong on my side and the apps were missing from the (source) where they were supposed to be. Not sure why.
Anyway I took measures to avoid this in the future.
I also uploaded a fixed build (same name, md5 c66cd526c6c92fd9eaa61e42153d3b8e) to AFH, so just download and flash that. You likely don't even need to wipe your data if you don't want to.

 

[asdf2345]

I wish there was a good 15.1/8.1.0 ROM, basic functionality worked great with that version.

With 17.1:
Camera, if set to SD, takes blank pictures.
I don't get some notifications that I should be getting (text messages)
My VPN randomly disconnects and requires manually turning it off and back on to get it to reconnect.

 

[jurkoman]

I'm using that ROM (17.1) myself on my daily device and haven't encountered any issues at all. So looks like something with your device, not the ROM itself.

I assume you are (still) using 17.1 as you mention the Sony camera app. I'm a bit confused: Above you said that the camera cannot start.

I just tried to reproduce the other issues: Camera works fine for me, I've always had the default set to SD and front camera does also work. I can imagine issues with camera and the flashlight feature as the former may want to access the light which may be already in use in that situation but it also does work fine for me.
In fact the camera is one of the things I test on a spare device for a new ROM before even installing that on my own phone as a working camera is a good hint that a big part of the system works.

So I can only imagine that there is still something left on your device interfering with the current ROM. If you don't mind loosing your data reflash the Stock firmware with newflasher, TWRP and then this ROM making sure to wipe /data, /cache and dalvik in the process. Or if you don't want to flash stock wipe /system, /cache & dalvik and format /data, then reinstall the ROM (without rebooting TWRP) which might help.
At the very least try wiping /cache & dalvik (keep your data)


Answered there (a link to the issue in your post would be helpful as I don't get a notification on GH, but found it anyway): In short: It does work (I always do clean builds, by now 6 times), check your extracted system image

I tried at least 2 times reflashing .228 full firmware with newflasher, right after successful boot and basic setup rebooted into fastboot mode, flashed latest official TWRP, format /data, reboot again into twrp as suggested by twrp, wipe /system, /cache, installed this rom with magisk 25.2, again wipe /cache and reboot. I will try again reflash stock .228 but i suppose it will be same.