• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][Unofficial][10.0][signed][OTA] Lineage OS 17.1 for Xperia Z1 compact

Search This thread

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Your Magisk (framework) shows N/A so it is not workíng/installed and you should not have root!
Please try to get root back (without restoring a TWRP backup!) and look again for "adb root".
Good luck :)
So you can see the problems some of us have with Magisk > 20.4 and LOS > 17.1 :)
Hey, you're right; I wonder when I lost that. Strange thing is that I still can access root folders through file manager (just checked), therefor I thought I was still rooted. But I can't su from a terminal, so you're absolutely right
--- UPDATE ---
this is weird: tried to reinstall Magisk V21.4 from TWRP, and that appeared to work but back at system: still no root. Ran the Magisk uninstaller from TWRP then installed old V20.3, rebooted. Installed Magisk Manager, checked Magisk status and root through Terminal >> I'm back to be rooted now. Next wanted to check the adb root option but found I lost the "Developer options". After I re-instated them had to realize that the adb root entry now is gone :rolleyes:.
Back in Magisk Manager installed an update to V 8.0.7 (of the Manager app), then tried to update Magisk, but that didn't work at all: it jus downloaded the zip but nothing else although I had set the check at "direct install".

For me this isn't a problem really; Magisk V 20.3 seems to be working fine, and I hardly ever use adb root on that device. Still extremely weird. And apologies for my post above; I really should have checked properly before writing :oops:
 
Last edited:

tramp20

Senior Member
Jan 15, 2012
739
139
Rosenheim
For me this isn't a problem really; Magisk V 20.3 seems to be working fine,

If 20.3 is running:
update to 20.4
update only Manager to 8.07
update Magisk from manager to 21.4 release
if this all is running again make a TWRP backup only from boot partition so you can simply get root back through restoring this backup if you kill Magisk the next time :)
 
  • Like
Reactions: lm089

lm089

Senior Member
Jun 26, 2011
500
161
Munich
If 20.3 is running:
update to 20.4
update only Manager to 8.07
update Magisk from manager to 21.4 release
if this all is running again make a TWRP backup only from boot partition so you can simply get root back through restoring this backup if you kill Magisk the next time :)
Thanks, nice idea. But Magisk Manager doesn't let me update just to 20.4. It's all or nothing (OK, I could try to d/l an older version from somewhere here at XDA). But again: this is only my secondary device. Not a big issue to stay at this old version for the time being
 
Not sure whether that's related but every time while in TWRP flashing an update there's this line giving me a Sony firmware version string. Here it says:
"Target: Sony/D5503/D5503:5.1.1/14.6.A.1.236/2031203603:user/release-keys"
No, in fact that is the defined "build fingerprint" of our ROM, which in mimics usually the last "official" (Stock) fingerprint - it is not related to the true firmware.
To put it very simple:
Flashing our ROM replaces the boot partition (kernel, kernel ramdisk) and the system partition, which - next to LineageOS - also contains the so-called vendor blobs, which is the "majority" of the "firmware".
But other partitions, like e.g. the modem or the boot loader (and also further stuff, which may be there), are not touched.
And by flashing the latest Stock ROM via flash tool, as suggested by @115ek, the phone will also get those parts updated.
If there is somewhere a good firmware repository, those parts could also be explicitly flashed via fastboot ...
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
No, in fact that is the defined "build fingerprint" of our ROM, which in mimics usually the last "official" (Stock) fingerprint - it is not related to the true firmware.
To put it very simple:
Flashing our ROM replaces the boot partition (kernel, kernel ramdisk) and the system partition, which - next to LineageOS - also contains the so-called vendor blobs, which is the "majority" of the "firmware".
But other partitions, like e.g. the modem or the boot loader (and also further stuff, which may be there), are not touched.
And by flashing the latest Stock ROM via flash tool, as suggested by @115ek, the phone will also get those parts updated.
If there is somewhere a good firmware repository, those parts could also be explicitly flashed via fastboot ...
Thanks for the info; as far as I remember 14.6.A.1.236 had been the last version I had before rooting and flashing LOS so I had assumed...
 
Last edited:

yldun

New member
Feb 3, 2021
4
3
Unfortunately I don't know a way to check it directly.
Maybe someone else here has an idea.
By the way: the last official firmware was Lollipop on the Z1 compact.
You could flash it with the flashtool for example.
For getting the firmware have a look here.


One time is enough. With clean flash I mean wiping /data, /system, and /cache before the installation.
Oh well, I flashed the last firmware from stock rom, and then put twrp back and finally LOS.
And it's working.

So I'm happy now, thanks a lot for all the advices.
 
New builds with March 2021 ASB patches available

Hi all, new builds are available and offered as OTA updates via the updater app.

A. Standard LineageOS 17.1 build
  • Security String 2021-03-05
  • System Webview on 88.0.4324.152

B. Pre-installed microG build variant with additional security patches
  • Security String 2021-03-05
  • Bromite System webview updated to 88.0.4324.207
  • Bromite Browser updated to 88.0.4324.207
  • F-Droid 1.11
  • microG 0.2.18.204714

@115ek - please update OP/Changelog

Regards, M.
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Which build Variant? And to all: Same experience?
oops, sorry: standard variant.
But meanwhile I experienced a more serious issue:
Downloaded the zip to my phone, botted to TWRP, then after creating a full backup flashed the ZIP.
Then tried to reboot to system, but I always end up in TWRP.
Restored my backup, back in system now.
Strange, experienced a similar problem recently with another old XPeria device (TabletZ, running LOS 16).
 
Last edited:

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Yes, there was indeed an issue with the download URL in the .json file, this is now fixed, so the updater should show now updates.
Updater still isn't seeing anything new to download. Should I do something so that the updater can use your latest changes?
Apart from that: did you change something in the zip file itself, since yesterday I mean?
Just tried once more to install the version dated 2021-03-09, but same result: boot starts the LOS animation, shows it for quite a while, then suddenly goes back to the Sony logo and finally ends up in Twrp
Any more info I can provide?
 
Last edited:
OTA update is also here not working.

I installed with TWRP. For some reason I can't get Magsik (root) working. But when I restore the boot.img from my backup, before the upate, it was working (detected).
This time, there was no kernel patch available, so restoring your last boot.img was fine, as the kernel didn't change compared to February. I am not really familiar with Magisk, but normally, there should be a "survival script" to restore Magisk after each update, shouldn't it?
As indicated, neither @115ek nor I are Magisk experts (neither are we Magisk users), so we can't really help with Magisk issues.
Hope, that other forum participants could step in?
 
Updater still isn't seeing anything new to download. Should I do something so that the updater can use your latest changes?
Normally, press refresh - but if you have already flashed the update manually, it is normal that the updater doesn't find anything.
If you have restored the February build and you are on the February build, the updater should show the update.
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Normally, press refresh - but if you have already flashed the update manually, it is normal that the updater doesn't find anything.
If you have restored the February build and you are on the February build, the updater should show the update.
Strange, I thought I had the February build installed, but apparently I'm still running the January one. I'll try to update to the Feb one first, hopefully that alos will solve the boot-to-twrp issue
 
Strange, I thought I had the February build installed, but apparently I'm still running the January one. I'll try to update to the Feb one first, hopefully that alos will solve the boot-to-twrp issue
Normally, it should not matter in regards to boot-to-recovery.
However, it could indeed be an explanation for the update not shown, as we had at that time an issue with the build-type as specified in the build.prop file.
Edit: I'll download the Jan and Feb builds and will check the build.prop files.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    New builds with July 2021 ASB patches available

    Hi all,
    new builds are available and already offered as OTA updates via the updater app.


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    2
    Just installed it yesterday, everything is great. This ROM has LDAC support if anyone's wondering. Even Stock doesn't support LDAC. Thanks again.
    1
    • Kernel: Many sec. patches applied

    Awesome to see my CVE patcher used more!
    You might want to give it another run, I did a huge addition for 3.4 recently from @haggertk's 3.4 backports.

    You might also put the patches on an another branch, as patch output can change/improve overtime and it'll be easier to maintain that way.
    1
    I did already apply before Kevin's 3.4 backports from his LineageOS Samsung msm8974 branch and for the recent patching action with this ROM's Sony msm8974 kernel, I used the patches listed in here as this is also a msm8974 kernel in your 17.1 directory.
    Do you recommend to me to look further?

    And by the way, whilst I have the opportunity to communicate with you:
    As I prefer to truly apply the commits to my/our kernel forks, I have noticed, that few of your patches do not contain commit messages. For some of them, I found them and applied accordingly, but at least for that one I did not manage to find it.
    Do you have the commit message(s) handy?
    And if not - would you like me to make a pull request for those patches, where I was able to identify the originating upstream commit?

    > I used the patches listed in here

    The program is intended to be used to check which patches apply.

    > I have noticed, that few of your patches do not contain commit messages.

    Many of them are plain diffs due to various reasons, eg. Gerrit only gives base64'ed plain diff
    I'm happy to accept patches that replace diffs with matching patches.

    > but at least for that one

    That is https://lkml.org/lkml/2017/10/2/352

    --

    In case it isn't clear, patches are added to this file first https://raw.githubusercontent.com/Divested-Mobile/Kernel_Patches/master/Kernel_CVE_Patch_List.txt

    then downloaded with the program https://github.com/Divested-Mobile/CVE_Checker

    and also checked using the program

    you can use https://github.com/Divested-Mobile/CVE_Checker/blob/master/mk_dir_from_list.sh to convert the program output to a directory of the patches

    you can download prebuilts of the program here https://gitlab.com/divested-mobile/cve_checker/-/jobs/artifacts/master/browse?job=build

    furthermore a large amount of the patches in the list are extracted using this tool https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec, you can add any kernel you want to the script config and extract matching patches from any given repository, and propagate that back into the final patch list


    edit: here is example output https://github.com/SkewedZeppelin/android_kernel_sony_msm8974/commits/fixup it contains an additional ~60 patches
  • 19
    This thread aims at providing LineageOS 17.1 builds for the Sony Xperia Z1 compact with current security patches.
    You can consider this thread as a successor of our LineageOS 16.0 thread, where you may also find some useful information.
    This is the joint effort of 115ek and MSe1969 (contributions welcome).

    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
    *
    */

    We offer two build variants:
    A. Standard LineageOS 17.1 build
    This build flavor aims at providing LineageOS 17.1 "as is" with most recent security patches.
    If you want to install Google Apps (GApps) you have to use this build variant.
    GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
    Just check the package comparison to see what fits your needs.

    B. Pre-installed microG build variant with additional security patches
    For the security/privacy focused (more details about below feature list, see here)
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore
    • eSpeak TTS engine (FOSS TTS solution)
    • Bromite as default browser
    • Additional security hardening features listed below
    • Cloudflare as default fallback DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google/Sony when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Firewall (control internet access per app - under Trust)
    • Constified JNI method tables


    Status
    List template by AdrianDC
    Code:
    - Partitions (Data, Cache) : Ext4 and F2FS supported
    - Bluetooth : Ok
    - WiFi : Ok
    - WiFi Hotspot : Ok
    - RIL - Phone - Data : Ok
    - GPS : Ok
    - Camera : Ok
    - Camcorder : Ok
    - Lights : Ok
    - MicroSD : Ok
    - Accelerometer : Ok
    - Compass : Ok
    - Gyroscope : Ok
    - Touchscreen : Ok
    - FM Radio : Ok (mono)
    - ANT+ : Ok
    - Vibrator : Ok
    - Microphone : Ok
    - Audio & music : Ok
    - Bluetooth audio : Ok
    - MHL: broken
    - NFC : Ok
    - Kernel : Ok
    - Graphics : Ok
    - 3D Rendering : Ok
    - Clock : Ok
    - Offline Charging : Ok
    - USB : Ok
    - USB OTG : Ok
    - Encryption : Ok
    - SEPolicies : enforcing
    Limitations
    Following limitations are known:
    • NFC-HCE does not work (needed for example for google pay)
    • FM does not work in stereo mode (mono works fine, though)
    • MHL does not work
    • 5 GHz hotspot does not work (2.4 GHz hotspot works fine) (5 GHz option disabled with 2020-03-11 build as it isn't even available on stock)
    • GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example). fixed with 20200520 build
    • Using GApps AND encrypting the device may result in bootloops. More infos here.
    • Standard Trebuchet Launcher shows small artifacts in the fonts of app names in some situations.
    Download
    FAQ
    What recovery system to use?
    Please use this TWRP if you want to use OTA updates and/or encryption.

    What about root access?
    Root isn't included per default (except root over adb, but it's off by default).
    If you want to gain root access to your apps use magisk (everything > 20.4 is broken):
    ANT+ isn't working?
    You need the 2 apps:
    afterwards setting proper permissions is essential!
    1. Go to Apps & Notifications -> See All Apps
    2. Select 'ANT Radio Service'
    3. Select Permissions
    4. Select Additional permissions
    5. Slide switch to allow using of ANT hardware
    This refers to those instructions which worked for me :)
    I've got problems AND have magisk/exposed installed
    We won't support anything related to magisk/exposed/other heavily system modifying things.
    If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.

    Bugreports
    You'll find information about logging here.
    Please also note how you got the error or how it can be reproduced.
    Sources
    Credits
    • SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
    • NeoArian: also big thanks to him ;)
    • rcstar6696
    • SuperLamic
    • drakonizer
    • AdrianDC
    • munjeni: thanks for tips and tricks
    • nailyk: thanks for tips and tricks
    • All the other contributors on sony msm8974 platform
    • LineageOS team

    Installation instructions


    XDA:DevDB Information
    Lineage OS 17.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact

    Contributors

    115ek, MSe1969, SpiritCroc, NeoArian, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
    Source Code: https://github.com/lin17-microg/local_manifests

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.4.x

    Version Information
    Status:
    Stable
    Stable Release Date: 2020-12-29

    Created 2019-11-22
    Last Updated 2021-07-10
    8
    New builds with May 2021 ASB patches available

    Hi all,
    new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-05-05
    • System Webview on 90.0.4430.82

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-05-05
    • Bromite System webview updated to 90.0.4430.204
    • Bromite Browser updated to 90.0.4430.204
    • microG upstreamed (but no new version)
    • Update: AuroraServices 1.1.1

    @115ek - please update OP/Changelog

    Regards, M.
    7
    New builds with July 2021 ASB patches available

    Hi all,
    new builds are available and already offered as OTA updates via the updater app.


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    7
    New builds with March 2021 ASB patches available

    Hi all, new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-03-05
    • System Webview on 88.0.4324.152

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-03-05
    • Bromite System webview updated to 88.0.4324.207
    • Bromite Browser updated to 88.0.4324.207
    • F-Droid 1.11
    • microG 0.2.18.204714

    @115ek - please update OP/Changelog

    Regards, M.
    6
    Changelog

    10.07.2021

    • ASB Security string 2021-07-05
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • standard build only:
      • System Webview on 91.0.4472.101
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.146
      • microG 0.2.21.212158-2
      • AuroraStore 4.0.7
    14.06.2021
    • ASB Security string 2021-06-05
    • A few kernel patches
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.102
      • Upstreamed microG (0.2.19211515-9)
    12.05.2021
    • ASB Security string 2021-05-05
    • standard build only:
      • System Webview on 90.0.4430.82
    • microG build only:
      • Bromite System webview updated to 90.0.4430.204
      • Bromite Browser updated to 90.0.4430.204
      • microG upstreamed (but no new version)
      • Update: AuroraServices 1.1.1
    11.04.2021
    • ASB Security string 2021-04-05
    • standard build only:
      • System Webview on 89.0.4389.105
    • microG build only:
      • Bromite System webview updated to 90.0.4430.59
      • Bromite Browser updated to 90.0.4430.59
      • F-Droid 1.12
      • Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
    09.03.2021
    • ASB Security string 2021-03-05
    • standard build only:
      • System Webview on 88.0.4324.152
    • microG build only:
      • Bromite System webview updated to 88.0.4324.207
      • Bromite Browser updated to 88.0.4324.207
      • F-Droid 1.11
      • microG 0.2.18.204714
    07.02.2021
    • ASB Security string 2021-02-05
    • misc. kernel patches
    • microG build only:
      • Bromite System webview updated to 88.0.4324.141
      • Bromite Browser updated to 88.0.4324.141
      • F-Droid 1.10-alpha-234
      • microG 0.2.17.204714-5
    14.01.2021
    • ASB Security string 2021-01-01
    • standard build only:
      • Kernel slightly upstreamed
      • System Webview: Fix of persistent histogram bug (eating space in some cases)
    • microG build only:
      • Bromite Webview on 87.0.4280.131
      • Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
      • Updated F-Droid to 1.10-alpha1-212
    29.12.2020
    • introduce microG build variant (see this post or the OP for more information)
    18.12.2020
    • synced LineageOS sources (security patch level December 05, 2020)
    08.11.2020
    • synced LineageOS sources (security patch level November 05, 2020)
    • Seedvault is included officially now (inbuilt backup solution)
    07.10.2020
    • synced LineageOS sources (security patch level October 05, 2020)
    13.09.2020
    • synced LineageOS sources (security patch level September 05, 2020)
    17.08.2020
    • synced LineageOS sources (security patch level August 05, 2020)
    13.07.2020
    • synced LineageOS sources (security patch level July 05, 2020)
    16.06.2020
    • further GPS improvements
    • synced LineageOS sources (security patch level June 05, 2020)
    20.05.2020
    11.05.2020
    • synced LineageOS sources (security patch level May 05, 2020)
    16.04.2020
    • synced LineageOS sources (security patch level April 05, 2020)
    15.03.2020
    • fixed livedisplay
    • fixed OTA update URL
    11.03.2020
    • remove 5GHz hotspot option as it isn't available even on stock
    • start signing builds
    • enable OTA updates
    • synced LineageOS sources (security patch level March 05, 2020)
    28.02.2020
    • fixed sony bootlogo
    • fixed TWRP time bug
    25.02.2020
    • fixed buggy bootanimation
    11.02.2020
    • DRM fix (Netflix and co should work now)
    • synced LineageOS sources (security patch level February 05, 2020)
    01.02.2020
    • SE enforcing
    • synced LineageOS sources (security patch level January 01, 2020)
    22.11.2019
    • initial release