[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2024-03-30)
- Thread starter Flamefire
- Start date
magiskmanager.com is not the official website for Magisk Manager. I recommend people use the official site to install Magisk, https://github.com/topjohnwu/Magisk and https://github.com/topjohnwu/Magisk/releases
Which repos to use for Android R /e/ OS builds?
I have been making unofficial and custom Android Q /e/ OS builds for a while now. I started using the Whatawurst github repos, then moved to @Flamefire repos for more recent builds as there was more recent activity in the lineage-17.1 branch there.
I am about to start on the adventure of an Android R build, and I was wondering which repos to use for that. I have noticed a fair bit of recent activity in the whatawurst repos, some of which seems to be coming from Flamefire. Is the plan to pull (some, many, most, all) Flamefire's commits into the whatawurst repos, or are they likely to stay diverged?
Thanks for any ideas, and thanks for all the work on these LOS ROMs for lilac
Edited: the question relates to Android R builds, not Q
I have been making unofficial and custom Android Q /e/ OS builds for a while now. I started using the Whatawurst github repos, then moved to @Flamefire repos for more recent builds as there was more recent activity in the lineage-17.1 branch there.
I am about to start on the adventure of an Android R build, and I was wondering which repos to use for that. I have noticed a fair bit of recent activity in the whatawurst repos, some of which seems to be coming from Flamefire. Is the plan to pull (some, many, most, all) Flamefire's commits into the whatawurst repos, or are they likely to stay diverged?
Thanks for any ideas, and thanks for all the work on these LOS ROMs for lilac
Edited: the question relates to Android R builds, not Q
Last edited:
Do you mean a different java compiler, or C compiler? Which one? I build from source, and would be interested in trying it.
@Flamefire Can you explain why you changed our device's build description to make it look like a Google Pixel device?
I had to switch to 18.1 in order to get my banking app (Nordea Codes 1.12.0) to work (previous version 1.11.2 would work just fine). The app would just crash or stay open doing nothing with no way to interact with it. I did notice that removing Magisk and reinstalling the banking app would work, but I want my root. I did use MagiskHide and had safetynet working just fine, but the 1.12.0 version would just not work. For some reason LOS 18.1 + Magisk works fine with it.
Well, I noticed a feature missing that was in 17.1, it's in the notification light settings when you want to add applications and select colors for the blinking light for each app, the "+" button on top right is gone, so I cannot add applications to the list. I had to resort to 3rd party app called Light Manager 2, it's fine but it needs to have a notification icon on the status bar and I don't like it. I already have 1 other icon in there permanently (Call Blocker) and it took forever for me to get used to it. Anyway to get the button back?
edit: the "+" appears when you select "Use custom values"
Well, I noticed a feature missing that was in 17.1, it's in the notification light settings when you want to add applications and select colors for the blinking light for each app, the "+" button on top right is gone, so I cannot add applications to the list. I had to resort to 3rd party app called Light Manager 2, it's fine but it needs to have a notification icon on the status bar and I don't like it. I already have 1 other icon in there permanently (Call Blocker) and it took forever for me to get used to it. Anyway to get the button back?
edit: the "+" appears when you select "Use custom values"
Last edited:
@toejam119 You need to enable the custom app settings for the LED first so that this button becomes visible --> "Use custom values"
Oh my god, I thought I pressed that button, but I only disabled "Choose colors automatically" instead *facepalm*, thanks though!
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
----
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:
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)
----
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:
- Make sure your phone's time is currently normal/correct
- Put phone into airplane mode
- Reboot phone
- Time should now be wrong on startup
- Disable airplane mode, time should now be updated once network connectivity is back
Last edited:
@Flamefire thank you so much for reducing the brightness of the white sony splashscreen on device startup <3
Last edited:
Dirty flashed 2021-09-18 from 2021-07-20 -- all good 
Thanks @Flamefire for the continued support (and all previous/current contributors)!
Thanks @Flamefire for the continued support (and all previous/current contributors)!
After installing version 11, it is not possible to return to android 10. I installed stock firmware, tried to put 17.1, but the phone just restarts, freezes, etc. I tried various combinations all day, only 18.1 works. For what reason did it happen? Yes, I also changed the TWRP versions. Without success.
Last edited:
Sure you really got rid of all traces of Android 11? Had some trouble doing the same operation, but finally succeeded the way described below. It assumes you've got ADB/Fastboot + drivers and Newflasher + flashmode drivers installed and working. Be warned I'm no expert in this field, there are probably better/simpler ways of doing it. You might want to wait for comments from more knowledgeable/experienced users than me before attempting this yourself.
- Do whatever backups etc you need.
- Turn off the phone, remove the SD card if you have one installed.
- Boot TWRP (assuming you have it installed).
- Wipe -> dalvik/art, system, cache, data, internal storage (this is probably redundant, but did it anyways).
- Wipe -> Format Data.
- Turn off the phone.
- Boot in Flash mode (hold Vol Down, plug in USB cable. The LED should light up green).
- Flash the latest stock rom, prepared for use with Newflasher (delete all .ta files from the archive, etc). There seems to be different opinions on deleting persist*.sin from the archive. I did, and it worked. You might want to read up further on this subject.
- Reboot phone to Fastboot mode (pull the USB cable, hold Vol Up, and plug the USB cable again. LED should light up blue).
- Flash TWRP for Android 10 (fastboot flash recovery <image name>)
- Boot TWRP.
- Advanced - ADB Sideload. Tick the checkboxes and swipe.
- Sideload the LOS rom (adb sideload <LOS zipfile>)
- Sideload OpenGapps if you want them (ARM64, 10.0, whatever variant you want) (adb sideload <OpenGapps zipfile>). You'll have to enable ADB sideloading in TWRP again before flashing.
- Reboot phone to Android. Hopefully it works now. Do whatever configuration you want. Restore backups. Install SD card again.
Last edited:
I did everything except this step. I just did the wipe, then installed 17.1 LOS. I will do as you wrote, thank you very much for the detailed explanation.
Same problem here,date and time is always the time from the first start after flashing, changes about one minute later when phone has fully booted.
GPS not working as well and my signal strenght is really bad since flashing newest 18.1, starting a call takes sometimes about 30s until it starts ringing and people don't understand me and I don't understand them.
I have to go back to modpunks 17.1 from december 2020, that one was working like a charm.
Hope I can downgrade without installing Stock again like @.kaputnik. wrote?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8Currently uploading the remaining builds (19.1 & MicroG versions) after some more testing and fixes. Play Integrity now passes on all builds and Wallet should hence work again. You can also use the PIF JSON file to change the fingerprints in case it gets blocked, as if PlayIntegrityFork was installed. Place it at /data/adb/pif.json to use. Only Build fields are supported though (i.e. not the properties)
See the example file or better /vendor/etc/pif.json on the phone for the format and current usages.
The time issues on 17.1 persist and are hard to fix if at all so I stopped searching for a fix after some time as it works on 18 & 19 and on 17 the auto-set from network is "good enough". Or just don't reboot ;-)8Happy Easter!
I uploaded the 17 & 18 versions of the new ROM to GDrive. Google wallet seems to work. The 19 and MicroG versions still need some testing, will upload after Easter.
@snoopy29 not sure what you mean exactly. Can you Clearly describe the issue? But likely not fixed as I have spent a lot of time on IMS, kernel issues and the Play Integrity stuff especially if the time issue only happen on reboot it is annoying but not crucial. I haven't seen it on 17-non-MicroG (using network time which might hide it)4
This is unrelated to the builds, but a huge wave of Bans of devices (actually fingerprints) from Google. So I assume even the stock ROM won't be usable anymore. Previously I implemented a Play Integrity spoofer into the ROM itself which made it work so far.
I have a workaround ready which at least passes PlayIntegrityChecker, so hopefully also the Wallet check. But it is also possible that no custom ROM will work anymore... E.g. I had an app detecting "an insecure device" even though even Google Wallet was still working so the spoofing was in effect but not enough.
Another question:
Is there anyone where IMS is not working although it should be supported by the carrier? If so on which version of this ROM are you on? I could provide a test version attempting to workaround that issue.4
I've seen that, IIRC someone posted a link to that earlier or at least one that led to that. I'm using this solution but again have modified in a way that it will be integrated into the ROM with the next release (testing in progress right now), such that Magisk is not required. I've spent some time to make it flexible enough such that it will work as long as possible without rebuilds as I'll switch to LOS 20+ after this last release since there won't be any security updates (reasonably) possible.
I just tested 17.1 and 18.1 non-MicroG on 2 devices and either option seems to works fine. With the option enabled the behavior is as expected:
- Lock phone by pressing the power button -> Display turns off
- Touch (not press) the power button with registered finger -> Display turns on and phone unlocks
However I've seen the issue randomly pop up. Sometimes waiting a minute after locking the phone won't turn the FP sensor back on until the phone is unlocked via pattern/PIN. Strange...
Note that the setting is not in XperiaParts but in regular android settings Security->Gear icon next to "screen lock".
The behavior including defaulting to ON is from LOS upstream. I might change that though for 17/18 where I backported it.
Very strange indeed. Then yes, disabling IMS by default might be the safe call here. As a workaround you could remove the SIM for the initial setup.
I'll try to avoid the performance issue for this final build. But can't be sure as I don't know what might be causing it and testing something that appears after a week is unfeasible.3
Yes this is possible that this is the same issue which was fixed at that point. Will be fixed in next release, thanks for confirming my suspicion! -
58LineageOS 17/18/19 for Sony Xperia XZ1 Compact
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact.
It is based on the great work of modpunk and derf elot from https://xdaforums.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ with recent security updates, some backported from newer versions.
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. (Backup download when AFH isn't uploading)
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 use the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and roughly tested, i.e. boots, WiFi works and SN passes/MicroG self check shows OK.
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.
- Put the zip file of the ROM on your SD card or internal store and boot into recovery.
- When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". You don't need to wipe system. When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
- Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
- After updates you may now wipe cache&dalvik (option after install)
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):
- Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
- 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) - From now you can boot TWRP by turning on the phone with "Volume Down" + Power
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 too and build the Lineage 18/19 ROMs without much testing.
Contributions to the sources are welcome and likely get integrated into the next release.
Contributors
modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
Source Code: Device tree: https://github.com/Flamefire/android_device_sony_lilac
Kernel: https://github.com/Flamefire/android_kernel_sony_msm8998
If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
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.27CHANGELOG
2024-03-30
- Kernel updates (CIP tag -st50)
- Reduce performance issues
- Play Integrity workaround (based on osm0sis work)
- Attempt to enable IMS by default for all providers (mostly from @antoniu200 )
- Feburary security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st49)
- January security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st48 & LOS common kernel merge)
- December security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st47 & additional security fixes)
- Fix for critical Bluetooth vulnerability (CVE-2023-45866)
- November security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st46 & additional security fixes)
- Updates to the kernel scheduler backported from LOS 20 common kernel
- Fix for CVE-2023-5217
- October security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st45 & additional security fixes)
- Fix for CVE-2023-4863 (actively exploited!)
- September security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st44)
- August security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st43)
- Increased headset volume
- Add Sony camera app to 18 & 19 (files copied from xperiance)
- July security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st42)
- June security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st41)
- Fix noise when calling with a headset
- Configurable fingerprint sensor when screen is off (Settings->Lockscreen)
- Fix Play Integrity checks --> Google Wallet works
- Minor improvements that were missed earlier
- May security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st40)
- April security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st39)
- March security patches (backports from 18.1 to 17.1)
- Kernel updates (CIP tag -st38)
- Fix possible camera issues on 18.1
- February security patches
- Kernel updates (e.g. CIP tag -st37, also add some missing patches to 19.1 kernel)
- Use newer compiler (Clang 12.0.7) for kernel, possibly improving performance/battery life
- Add "Re-apply Modem" setting to XperiaParts to help with connection/modem-crash issues
- Clear some space on /system & /vendor partitions by removing files no longer needed
- Fix Android Auto connection
- January security patches
- Kernel updates
- MicroG builds added (build date 31st Jan, but same sources)
- December security patches
- AGPS fix (using Google servers)
- Kernel updates (e.g. Wireguard v1.0.20220627, improved security against stack attacks)
- November security patches
- WLAN driver update
- Huge APN update
- October security patches
- Kernel update
- APN for DIGI HU
- Option to switch temporarily to 2G on boot
- September security patches
- Kernel update
- APN update
- August security patches
- Kernel update (CIP st20)
- July security patches
- Kernel update
- June security patches
- Kernel update
- Backport fix for CVE-2021-39686
- Workaround fixing bootloop with recent OpenGapps (20220503 tested)
- May security patches
- Fix mic volume issue with wired headsets
- Known issue: OpenGapps after 15/2 result in bootloop
- 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)
- 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
- 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)
- January security patches
- Kernel 4.4.299
- Wireguard v1.0.20211208
- Enhanced display brightness range
- Experimental Ultra-Dim mode
- December security patches
- Kernel 4.4.295
- QCom driver updates
- Fix some permission issues
- Reset phone ID to XZ1C
- November security patches
- Kernel 4.4.291
- Fix IMS on 17.1
- Fix/enhance Wifi-Display
- Fix some power hints
- Update APNs
- October security patches
- Kernel 4.4.288
- 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
- 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
- July security patches
- Kernel 4.4.275
- June security patches
- Update to Linux Kernel 4.4.272
- Updated APNs
18April updates are out, enjoy! Again I had to backport every security patch from 18.1 to 17.1 so it really seems to be dying...
I might switch to building LOS 20 though as derfelot doesn't seem to be providing updates anymore. And especially the battery charge/protection service that might be coming there looks promising...
Sorry no. I'd need to research how to create that recovery and maintaining 3/6 different ROM versions is already enough work especially with the hugely increased time/effort to keep LOS 17, so I can't afford to do even more.
