good luck
as far as i know u cant get the sony cam to work on android 11 roms only android 10
[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2024-03-30)
- Thread starter Flamefire
- Start date
good luck
as far as i know u cant get the sony cam to work on android 11 roms only android 10
I already read this guide and you can use this exploit only if you run Android 8 on your phone... However downgrading to Android 8 with newflasher tool broken my Camera but upgrading again to Android 9 with FOTA fixed it
Wow, if you want to keep your data don't delete DATA.
- wipe system
- istall ineage
- istall gapps nano or pico
- wipe cache/dalvik
- the risk is that there was no standard gapps pack before
It has been a long-standing mistake for me that the caller hears an echo during a phone call if I turn down the speaker, it is partially solved, but it is completely eliminated only by speakerphone. Unfortunately I can't find the call noise filtering / noise cancellation off option in the call app.
You have noticed this?
You have noticed this?
I'm running the latest stock os rooted right now, but I would like to go Lineage. How's the camera quality on this one? On my other phones that I updated to LOS the camera quality took a nosedive to the point of being nearly unusable compared to stock, for example, my OnePlus3 works perfectly on LOS but I can just forget about the camera. The XZ1 has a good camera, especially for videos. Is the quality good on LOS, or is there some way to fully restore the original camera software?
Original (sony) camera only works with 17.1, not with 18.1!
I'm using 17.1 with the sony camera app and I'm very happy with it. Best pictures I ever made with a phone.
But I can't compare to the camera app in stock rom...
You could check out about the backup and restore of the drm keys (mentioned a few posts above) but I never done this and I don't know if this really enhances the camera quality in LOS or is only relevant for going back to stock. I always just lived happily with the loss of the drm keys. (But if you are rooted in stock, you maybe even lost them already, if you unlocked the bootloader?)
I'm using 17.1 with the sony camera app and I'm very happy with it. Best pictures I ever made with a phone.
But I can't compare to the camera app in stock rom...
You could check out about the backup and restore of the drm keys (mentioned a few posts above) but I never done this and I don't know if this really enhances the camera quality in LOS or is only relevant for going back to stock. I always just lived happily with the loss of the drm keys. (But if you are rooted in stock, you maybe even lost them already, if you unlocked the bootloader?)
I tried to do a command via adb, the command was "adb root" but adb gave an error "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options". I have Root enabled for adb and apps in Magisk, and there is no option to enable root for adb in developer settings (since Magisk is installed). Root seems to be working fine otherwise. I do not remember having this issue on modpunk's 17.1. I did dirty flash this Flamewire's 17.1 version over modpunk's 17.1. I didn't uninstall Magisk before dirty flashing, it seemed to install itself during Flamewire's 17.1 dirty flash. Everything else works fine so far on this release. Anyone else have this issue?
U mean like dirty flash ? i believe it is better to flash it clean if u come from another rom if u dirty flash it might cause problems.
The reason for not being able to adb root in @Flamefire ROM might be the commit for spoofing verified boot, etc... It spoofs e.g. the property "ro.debuggable"
@Flamefire I guess it is sufficiant for GPlay certification to not spoof ro.debuggable?!?
@Flamefire I guess it is sufficiant for GPlay certification to not spoof ro.debuggable?!?
`adb root` works for me, so I don't think that is the issue. However I do not have Magisk.
I think it is required because MagiskHide does set that too, so I'd rather not unset it
hmmm... interesting... I cannot confirm with my experience. I am running self-built (and signed) LOS 16 and I had the same issue with activation possibility of adb root in developer settings (just as @toejam119 described). Just spoofing ro.boot.vbmeta.device_state, ro.boot.verifiedbootstate, ro.boot.flash.locked, vendor.boot.vbmeta.device_state, vendor.boot.verifiedbootstate fixed the issue for me and GPlay cert passes (at least on LOS 16).
There was a patch which enables adb root in userdebug builds: https://github.com/LineageOS/android_system_core/commit/01266f589e6deaef30b782531ae14435cdd2f18e
This is then used in https://github.com/LineageOS/android_system_core/blob/lineage-17.1/adb/daemon/main.cpp#L73
So yeah, only thing I can imagine is something with Magisk
This is then used in https://github.com/LineageOS/android_system_core/blob/lineage-17.1/adb/daemon/main.cpp#L73
So yeah, only thing I can imagine is something with Magisk
I do believe Flamefire is right, I think it is Magisk's hide function. I also have MagiskHide Props Config module installed. I tried uninstalling Magisk and the Magisk app temporarily but I couldn't get adb root to work, perhaps I should've gone inside MagiskHide Props Config and revert some changes(?), though all I did in the past was change the fingerprint so the SafetyNet would pass while rooted and in LineageOS.
But it's ok since I can just use "adb shell" and then type "su" to use commands with superuser rights via my pc. Tested and it works good.
But it's ok since I can just use "adb shell" and then type "su" to use commands with superuser rights via my pc. Tested and it works good.
Hello folks,
I'm currently using the 2021-07-20 18.1 release, which is working like a champ on my XZ1C.
If I wish to update to the 2021-08-11 release, is it simply a case of downloading the zip, booting into recovery, and flashing? Do I need to reflash GApps, or erase anything?
Cheers!
I'm currently using the 2021-07-20 18.1 release, which is working like a champ on my XZ1C.
If I wish to update to the 2021-08-11 release, is it simply a case of downloading the zip, booting into recovery, and flashing? Do I need to reflash GApps, or erase anything?
Cheers!
Last edited:
I don't think he needs to wipe system if he's only updating from:
18.1 2021-07-20
to
18.1 2021-08-11
Unless I totally missed something. Simply flashing the zip should be enough? Someone correct me if I'm wrong.
Similar threads
Top Liked Posts
-
1
-
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.
