[ROM] LineageOS 17.1/18.1 UNOFFICIAL - (Update: 2022-08-13)

Shall F-Droid be included in the ROM(s)?


  • Total voters
    173
Search This thread

kentchristopher

Senior Member
Nov 16, 2007
140
25
Successful dirty flash from linneage 17.1 2021-04-22 to the latest 17.1 2022-05-16 using TWRP 3.3.1.

Some notes:

- Removed Magisk using the Magisk app prior to flashing, as recommended
- In TWRP 3.3.1, the md5sum check not pass. If this is a known problem it would help if it were stated in the first post.
- ROM boots without problem
- No issues with the mic and headphones (test call using Google Voice)
- Camera works, GPS works, modem works

Only issue is that my cards in Google Pay now all show "Not set up". Anyone know how to resolve this? Already tried wiping GPay storage and cache. I would think that tapping "Not set up" would walk me through setting each card up (re-verification with each bank?) but tapping it does nothing.
 

toejam119

Senior Member
Successful dirty flash from linneage 17.1 2021-04-22 to the latest 17.1 2022-05-16 using TWRP 3.3.1.

Some notes:

- Removed Magisk using the Magisk app prior to flashing, as recommended
- In TWRP 3.3.1, the md5sum check not pass. If this is a known problem it would help if it were stated in the first post.
- ROM boots without problem
- No issues with the mic and headphones (test call using Google Voice)
- Camera works, GPS works, modem works

Only issue is that my cards in Google Pay now all show "Not set up". Anyone know how to resolve this? Already tried wiping GPay storage and cache. I would think that tapping "Not set up" would walk me through setting each card up (re-verification with each bank?) but tapping it does nothing.
I also had a slight issue in Google Pay after updating from 2022 march release to 20220516, I had to set up all my cards again. I accidentally typed the wrong security code in the first card, thought something was wrong with the app so I added both entries in Magisk denylist: com.google.comandroid.apps.walletnfcrel and com.google.androi...nfcrel:primes_lifeboat (before there was only the first one), cleared both cache and data of Google Play. Set up my cards and all worked fine.
Did you reinstall Magisk 24.3 + needed modules + add the app to denylist? If you check your device with Oprek Detector (root check), do you get all green marks?
I am using 18.1-20220516-UNOFFICIAL-lilac so I am not sure if the Android version difference is the issue or what. Maybe someone with 17.1-20220516-UNOFFICIAL-lilac can confirm?
 

kentchristopher

Senior Member
Nov 16, 2007
140
25
I also had a slight issue in Google Pay after updating from 2022 march release to 20220516, I had to set up all my cards again. I accidentally typed the wrong security code in the first card, thought something was wrong with the app so I added both entries in Magisk denylist: com.google.comandroid.apps.walletnfcrel and com.google.androi...nfcrel:primes_lifeboat (before there was only the first one), cleared both cache and data of Google Play. Set up my cards and all worked fine.
Did you reinstall Magisk 24.3 + needed modules + add the app to denylist? If you check your device with Oprek Detector (root check), do you get all green marks?
I am using 18.1-20220516-UNOFFICIAL-lilac so I am not sure if the Android version difference is the issue or what. Maybe someone with 17.1-20220516-UNOFFICIAL-lilac can confirm?

I didn't reinstall Magisk because the first post specifically says that Magisk is not required to pass SafetyNet check with this ROM. And I don't really need root. Obviously if that's that it takes I'll reinstall it, but it seems like it shouldn't be necessary.
 

Flamefire

Senior Member
Jul 26, 2013
214
488
Sony Xperia XZ1 Compact
Successful dirty flash from linneage 17.1 2021-04-22 to the latest 17.1 2022-05-16 using TWRP 3.3.1.
...
- In TWRP 3.3.1, the md5sum check not pass. If this is a known problem it would help if it were stated in the first post.

Only issue is that my cards in Google Pay now all show "Not set up". Anyone know how to resolve this? Already tried wiping GPay storage and cache. I would think that tapping "Not set up" would walk me through setting each card up (re-verification with each bank?) but tapping it does nothing.
Rechecked MD5 of lineage-17.1-20220516-UNOFFICIAL-lilac.zip: e95dab075ed2e4dd21f4db59675f4877
That is what I have here, what AFH says and what is in the corresponding md5 file, so if the check doesn't pass for you something is wrong on your side.

I'm using that 17.1 ROM myself, Google Pay works without Magisk and at least my PayPal "card" I added to it before still is there and works.

So I suspect something went wrong during your upgrade. Maybe redownload and reflash?
 
  • Like
Reactions: sieghartRM

kentchristopher

Senior Member
Nov 16, 2007
140
25
Rechecked MD5 of lineage-17.1-20220516-UNOFFICIAL-lilac.zip: e95dab075ed2e4dd21f4db59675f4877
That is what I have here, what AFH says and what is in the corresponding md5 file, so if the check doesn't pass for you something is wrong on your side.

I'm using that 17.1 ROM myself, Google Pay works without Magisk and at least my PayPal "card" I added to it before still is there and works.

So I suspect something went wrong during your upgrade. Maybe redownload and reflash?

I manually checked the md5 sum of the file on the SD card and it matched. I didn't find the md5sum file on the SD card so I'm thinking I just failed to make sure it had been copied over before flashing.

Further, I didn't reflash because Google Pay ... fixed itself: the message for each card now shows "Hold to reader" instead of "Not set up". I previously read a couple comments elsewhere online from people who said this issue fixed itself after anywhere from "a few" to 24 hours. That seems to be what happened with me as well (24 hours). That might be worth adding to the notes in the original post.
 

Flamefire

Senior Member
Jul 26, 2013
214
488
Sony Xperia XZ1 Compact
@Flamefire Have you tried the 19.1 rom? What do you think about it?
Haven't tried it. And it is maintained by derf elot, the original maintainer of the 17.1/18.1 ROMs. So should be good. I won't include it in my builds (yet) as I feel it won't be fair to derf elot who likely invested a serious amount of time to get the kernel binary blobs ready for LOS 19. So I'll leave that for a bit.
Further, I didn't reflash because Google Pay ... fixed itself: the message for each card now shows "Hold to reader" instead of "Not set up". I previously read a couple comments elsewhere online from people who said this issue fixed itself after anywhere from "a few" to 24 hours. That seems to be what happened with me as well (24 hours). That might be worth adding to the notes in the original post.
Good to hear! Well it seems to be a temporary issue only. Probably not happening always and maybe not again in the future, so your post here should suffice for info ;-)
 
  • Like
Reactions: sieghartRM

petefoth

Senior Member
What I did to test is simple make a backup of only data, restore it right away, and it wouldn't work anymore. System and vendor wouldn't have changed anyway, and the locking / passwords were 100% the same (I have the same for 12 years on my phone...). I think it might or could work if you change from one rom to the other, but if the rom and version remains the same, and you have no root, system and vendor shouldn't have changed in the first place I guess?
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
 

MarkMRL

Senior Member
Jul 1, 2011
537
99
Hi. I managed to install the update, everything went well, the headphone bug is definitely solved. So thanks a lot to the developer for fixing it, you definitely made this phone usable for at the very least a couple more year.
I'll drop a donation as soon as I can :D
 
Last edited:

decsimon

Member
Aug 12, 2015
49
5
Hi, i flash last ver 18. Bluetooth is ok with radio and headphone, but not with my balance....(there is some fix?)
If i flash last ver 17, boot is ok but launcher appears total black so it is not possible continue configuration...
Any solution?
Thanks
 

4qx

Senior Member
Mar 21, 2022
89
33
Hi, i flash last ver 18. Bluetooth is ok with radio and headphone, but not with my balance....(there is some fix?)
You can configure Audio Balance in Settings > Accessibility > Audio adjustment... unless you're talking about something else?

If i flash last ver 17, boot is ok but launcher appears total black so it is not possible continue configuration...
You could try installing another launcher such as Nova Launcher or Lawnchair into the phone with ADB AppControl. If after that you cannot get into Settings to change the launcher (it's called Default Home App in Settings), and pressing Home button does not give you the choice to select it, you could try disabling the default launcher with ADB AppControl first.

Alternatively, you could try LineageOS 19.

Does this work on SO-02K?
LineageOS 19 does for sure, this should too. If it doesn't, you could reflash to 19.
 

decsimon

Member
Aug 12, 2015
49
5
You can configure Audio Balance in Settings > Accessibility > Audio adjustment... unless you're talking about something else?


You could try installing another launcher such as Nova Launcher or Lawnchair into the phone with ADB AppControl. If after that you cannot get into Settings to change the launcher (it's called Default Home App in Settings), and pressing Home button does not give you the choice to select it, you could try disabling the default launcher with ADB AppControl first.

Alternatively, you could try LineageOS 19.


LineageOS 19 does for sure, this should too. If it doesn't, you could reflash to 19.
Sorry! No balance but weight scale i have problem...my poor english is here😅
Lineageos 19 is too young rom with more problem actually
 
Last edited:

J719

New member
Jun 13, 2022
1
0
Hello, just getting my xz1 compact in from Japan today and wondering which rom currently works the best out of the box? Was looking at lineage 19 but seems like people are having issues with volte. I have TMobile. Been a while since I've done any flashing and what not. Or should I just stick to Android 9
 

echo124

Senior Member
Jan 6, 2016
586
99
Can someone make VoLTE work with files from other xperia phone to put carrier code into modem?VoLTE work on tmobile but not other.
 

victor126

Member
Sep 30, 2017
42
11
Can someone make VoLTE work with files from other xperia phone to put carrier code into modem?VoLTE work on tmobile but not other.
works on T-Mobile and its subsidiaries because they provisioned the volte

att and its subsidiaries white listed the xz1c because Sony didnt give them the proper paperwork so att claims.
 

keldeo66

New member
Jun 20, 2022
1
1
I'm loving this ROM thanks for the hard work! However it has one glaring flaw. Any ideas why, I can't connect to band 12? I'm on Tmobile in the USA. Volte works fine on other bands, such as 2, 4, 66 and I've even seen band 41 work. Vowifi works aswell. I can actually see it with cell mapper, but the phone refuses to even attempt to connect. Band 12 works perfectly fine with the stock rom. I'm using the correct, tmobile USA ims modem as well. Thank you.
 
  • Like
Reactions: 4qx

jurkoman

Senior Member
Oct 24, 2015
70
11
LineageOS 17.1/18.1 for Sony Xperia XZ1 Compact

logo.png


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.1)

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.
REQUIRED FIRMWARE: 47.2.A.11.228

IMPORTANT:
I only test the 17.1 releases myself. The 18.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 for LineageOS 17.1
TWPR 3.5.0-0 by derf elot for LineageOS 18.1
Or use the latest TWRP from https://twrp.me/sony/sonyxperiaxz1compact.html.

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.

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
ROM Kernel: Linux 4.4.x
Based On: LineageOS
Hello!
I am using your rom (latest 5/16/22 update) for 2 weeks and is very nice.
However it has some problems comparing to older Havoc OS 3.11.
Note: No Gapps, latest Magisk installed
1. More battery drain and more hot. I am able to get max. 5 hours SOT and some 2 days turned on with 25 percent. I noticed some drain when i dont use device. It isnt bad but in past ROM i was able to get easy 8 hours SOT and after 3 days i had still some 20 percent of battery.
Also feeling more hot than older Havoc.
2. Some smaller freezes or input lag + random freeze and restart UI when I connect to PC.
3. Sometimes after turning on, flashlight option is grayed (cannot turn on) or camera FC but i had this problem also in Havoc. Restart device will help.
4. Connecting to network still takes long time, but i had this problem on called Havoc OS.
 
Last edited:

decsimon

Member
Aug 12, 2015
49
5
In lineageos 17.1 gps work not fine, because lost capability to find actual position. So i must to restart phone and recalibrate bussola with google maps....there are some gps fix to flash? I use magisk...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    July update is out. Not much new except for the usual security updates.

    > Rom lineage 17.1 is working good. But could there be a implementation for miracast/wfd to turn off the device display itself to save energy.
    > I know its a specific sony stock rom thing that could miracast with the screen off and that there is not a single custom rom that fix that. But my hopes are high that this could be implemented.

    If another custom ROM had that so I could use its implementation then I might include it. But otherwise I don't really want to add features but focus on keeping the device usable and secure. That's already enough work ;-)
    1
    Has anyone else faced issues where the phone shows the wrong date/time on startup?

    On a fresh boot, the time is 9:58am on Saturday 18 September. It stays like this for approx 15 seconds until it finally updates to the current time (using network sync).

    However, if I keep the phone on airplane mode, the time stays wrong until I disable airplane mode.

    I'm wondering if this is a bug
    • with the most recent version of the ROM (I'll try with last month's version as well)
    • with the GApps package I'm using (I'm using the mini package which replaces stock clock with google clock)
    I'll update this post if and when I have more information.

    ----
    Update 1: Reflashed the September ROM with a smaller GApps package (micro instead of mini) and date/time issue still shows up. So GApps and the Google Clock isn't to blame. I'll try August ROM and see what happens.

    Update 2: Flashed the August ROM and the datetime issue still persists.

    Update 3: I'm attaching steps on how to reproduce this and I'd be really interested to see if anyone else is able to reproduce this:
    1. Make sure your phone's time is currently normal/correct
    2. Put phone into airplane mode
    3. Reboot phone
    4. Time should now be wrong on startup
    5. Disable airplane mode, time should now be updated once network connectivity is back

    I just encountered this same problem (almost a year after this author's post) on 17.1-20220516. While it doesn't seem like a big deal on the surface (time & date sync as soon as it gets a network connection), it has the annoying side-effect of totally throwing off the battery stats, as shown in this screenshot:

    Screenshot_20220801-110635_Settings.png


    I didn't see any further posts offering solutions but wondering if anyone else might know what's causing this.

    On an semi-related note, I encountered this trying to figure out what's causing the battery drain seen in that screenshot: 60% drop in less than a day with at least 8 hours of that time in airplane mode. The numbers/percentages listed just don't add up.
    1
    I have recently made unofficial and custom LOS 17.1 and 18.1 builds of LineageOS for microg for lilac, based on FlameFire's most recent builds.

    The builds are available in this AndroidFileHost directory

    More information at https://github.com/petefoth/unofficial-l4m-builds/blob/main/README.md
    Updated builds available, based on @Flamefire's July release. Sorry for the delay.

    On the 18.1 builds, banking apps from UK’s Co-operative Bank are working fine (Co-operative Bank Personal and Business apps, and Smile banking app). Sadly they don't work on the 17.1 builds :(
  • 51
    LineageOS 17.1/18.1 for Sony Xperia XZ1 Compact

    logo.png


    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.1)

    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.
    REQUIRED FIRMWARE: 47.2.A.11.228

    IMPORTANT:
    I only test the 17.1 releases myself. The 18.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 for LineageOS 17.1
    TWPR 3.5.0-0 by derf elot for LineageOS 18.1
    Or use the latest TWRP from https://twrp.me/sony/sonyxperiaxz1compact.html.

    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.

    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
    ROM Kernel: Linux 4.4.x
    Based On: LineageOS
    20
    CHANGELOG


    2022-08-12

    • August security patches
    • Kernel update (v4.4-st20)
    2022-07-25/28
    • July security patches
    • Kernel update
    2022-06-30
    • June security patches
    • Kernel update
    • Backport fix for CVE-2021-39686
    • Workaround fixing bootloop with recent OpenGapps (20220503 tested)
    2022-05-16
    • May security patches
    • Fix mic volume issue with wired headsets
    • Known issue: OpenGapps after 15/2 result in bootloop
    2022-05-03
    • April security patches
    • Kernel update (CIP st5-tag)
    • Removed LineageOS updater (unused application here)
    • Added Sony identification packages (Compatibility for some Sony apps from other sources)
    2022-03-20
    • March security patches
    • Updated some carrier configs (mostly Indian&Chinese) for IMS (VoLTE...)
    • Better support for flip covers
    • Allow disabling battery optimizations for the SMS app
    2022-02-20
    • February security patches
    • Kernel 4.4.302 (final LTS kernel)
    • Re-enable VoLTE toggle switch (there were reports of modem crashes when VoLTE is disabled, can't reproduce this, hence added the setting back)
    2022-01-23
    • January security patches
    • Kernel 4.4.299
    • Wireguard v1.0.20211208
    • Enhanced display brightness range
    • Experimental Ultra-Dim mode
    2021-12-19
    • December security patches
    • Kernel 4.4.295
    • QCom driver updates
    • Fix some permission issues
    • Reset phone ID to XZ1C
    2021-11-29
    • November security patches
    • Kernel 4.4.291
    • Fix IMS on 17.1
    • Fix/enhance Wifi-Display
    • Fix some power hints
    • Update APNs
    2021-10-19
    • October security patches
    • Kernel 4.4.288
    2021-09-18
    • September security patches
    • Include some more security patches from AOSP
    • Clang 11 for LOS 17.1 version (same as 18.1, improved optimizations)
    • Misc bugfixes backported from Android 11 to Android 10
    • Kernel 4.4.283
    2021-08-11
    • August security patches
    • Fix bug with switch 3G->4G in XperiaParts not working on slow boot
    • Include some more security patches from AOSP
    • Kernel 4.4.279
    2021-07-20
    • July security patches
    • Kernel 4.4.275
    2021-07-03
    • June security patches
    • Update to Linux Kernel 4.4.272
    • Updated APNs
    20
    I'm happy to announce the June update. Took a lot more work as I backported quite a bit to our kernel to fix CVE-2021-39686 although I'm not sure we were ever really affected by that. Anyway the backport fixes that hole and a few potential others making the device a bit safer!
    15
    @MarkMRL Update 20220516 is out which should also fix the headset issue. Reproduced, found and fixed it as far as I can tell.
    14
    I updated the ROM with the January security patches. I also included the "Ultra Dim" QuickSettings tile to reduce the screen brightness (overall). But that is experimental. I'm thinking about including that in the range of the brightness, i.e. make the lowest brightness levels less. Problem is that there are only 255 values possible so I have to define a switch-over point somehow and distribute those 255 values over effectively 2 distinct ranges. Let's see...

    I also added Google Drive downloads temporarily as a backup if AFH fails again...