yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] MSe1969:
I can't reproduce your issue. As you state, this happens with several apps, so I could think of two reasons:

a. Try wiping cache & dalvik in TWRP

b. Have you flashed anything on top of the ROM or do you use any Magisk modules?
[Xperia Z1 Compact Android Development] tramp20:
Thank you, I flashed already the update.

But I need help because I had never success with "adb root".

My adb Version 30.0.5 (Windows 10)

1. I cannot find "Root debugging" in the developer options, what is the correct German word?

2. adb root

restarting adbd as root

but I never see that this command finishes.
[Xperia Z1 Compact Android Development] 115ek:
Actually it should be there. However, I've just got a 18.1 device handy.

Perhaps it is also a problem caused by magisk. Can you do some settings in the magisk app?

I'm going to check a 17.1 build later on.

So normally a dialogue will pop up on your phone's screen asking for permissions. Most times I also need to enable flie transfer mode for it to be working.

In any way: You could also do the stuff @MSe1969 mentioned in the TWRP. But you need to mount /system first. And setprop also won't work. You need to set it directly in build.prop or default.prop. However, it's a bit strange that it doesn't show up for you.

@MSe1969 Actually you're building userdebug, not user, right?
[Xperia Z1 Compact Android Development] MSe1969:
The screenshot indeed shows, that this option is missing, which seems to be caused by Magisk.

What you need is a root session, when connected with your device via adb.

By the way, the reply "restarting adb as root" followed again by the command prompt is the expected answer. You can verify with "adb shell" that you have a root session (if you see the #). If you are in the root session, enter the "setprop ..." command and leave the session afterwards with "exit".
[Xperia Z1 Compact Android Development] tramp20:
I never get a command prompt after this reply. I have to kill adb with ctrl-C or to wait until the timeout after minutes.

The " dialogue will pop up on your phone's screen asking for permissions" was appearing ofc and file transfer over usb is enabled too.

Perhaps LOS 17.1 does not recognize Magisk as a root solution and does not show this option?

I cannot use LOS 18.1 without Magisk, there is until now for me no way to install/patch it :-(
[Xperia Z1 Compact Android Development] MSe1969:
Yes, userdebug - not user
[Xperia Z1 Compact Android Development] MSe1969:
If you have Magisk, you can also do the following: Enable the terminal (developer settings), launch it, enter the command su, grant root access via Magisk when the popup appears, and then enter the "setprop" command in the terminal.

You flashed already the update, but to close the topic.
[Xperia Z1 Compact Android Development] tramp20:
Thank you.

This command finished without errors :-)

But now the updater does no longer find an update:

"Die Suche nach Updates ist fehlgeschlagen. Bitte überprüfen Sie die Internetverbindung".

How can I revert the setprop command without restoring my backup?

Sorry I do not understand enough :-(

In LOS 18.1 the option rooted debugging is visible, perhaps it is only forgotten in LOS 17.1 :-)
[Xperia Z1 Compact Android Development] MSe1969:
As you have already manually flashed the update, it is normal that the updater woundn't propose you any update. This is what I mentioned already in my previous post.

The root debugging option is visible also in 17.1, but I think not, if you have Magisk flashed.

I can later check the Java code to give you a precise answer.
[Xperia Z1 Compact Android Development] yldun:
Thank you,

I updated to february update.

a. I just did that. On first reboot, I had no more access to camera at all with Simple Camera being the most talkative "CameraAccessException : CAMERA_DISCONNECTED (2) : Camera service is currently unavailable"

After rebooting, it's back to "normal". While I was playing around to check it was indeed the same (video recording is ok, I can switch between front and back camera, I can't save photo), I noticed an error : there is a small cam icon on top right, indicating the ressource "Camera" is used, I forced all cam' apps to close, but the icon is still here, preventing other use. I checked permissions, but nothing odd there.

b. since I picked version "A", I flashed pico opengapps on top of that. But no Magisk.

On Lineage 16.1, I did have Magisk installed.

I don't remember doing anything specific on my previous installation, but I don't do it so often, is there anything I could check to see if something is odd ?
[Xperia Z1 Compact Android Development] 115ek:
@yldun

Do you were on the latest official firmware sony released before installing lineage?

This would be 14.6.A.1.236 I think.

The final consequence to solve the issue would be a clean flash. So if you can afford it, this would be the fastest solution.
[Xperia Z1 Compact Android Development] yldun:
Err, I don't know. Can I check it now somewhere (not in LOS system I think) ? And eventually upgrade the firmware ?

By clean flash you mean reinstall LOS 17.1 one more time or (if this makes sense) does it involve trying to set the official Kitkat rom first ?
[Xperia Z1 Compact Android Development] 115ek:
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.
[Xperia Z1 Compact Android Development] lm089:
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"
[Xperia Z1 Compact Android Development] lm089:
At least not in general: I'm running latest Magisk, and on my device the adb root option is showing (and working as well):
[Xperia Z1 Compact Android Development] lm089:
Tried this, but ended up in a loop, showing the boot animation for some time until I forced the device to shut down (longest time I waited was well over 10 minutes).

What I did:

- ran your adb command then found the update through OTA; downloaded and installed. After install was finished ended up in the loop

- forced the device to shutdown, booted again to system ==> boot loop

- forced shutdown, then booted into TWRP; downloaded the update from SourceForge (via PC), then pushed the image to the device, then flashed the update from TWRP; cleaned DALVIK/Cache, tried to boot to system ==> boot loop

- another forced shutdown and boot into TWRP; restored latest Nandroid (from just before the OTA attempt) ==> now I'm back in system

Let me know if you need more info; if it's a log please tell me which one you need (after all these years flashing Android devices I still cannot remember which log is needed for what, and where/how I can get which; sorry for that :oops:)
[Xperia Z1 Compact Android Development] tramp20:
I have 3 Z1c with the same Magisk version, LOS 17.1 and almost the same apps (to test) and no "adb root" option :-(

Do you have "debugging app" checked?
[Xperia Z1 Compact Android Development] lm089:
Look at my Screenshot, those are the checked options. Plus marked "file transfer" in the USB options while connecting device to pc.

Don't get me wrong, I'm not doubting your issues. Just wanted to clarify that Magisk alone cannot be responsible for that
[Xperia Z1 Compact Android Development] tramp20:
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 :)
[Xperia Z1 Compact Android Development] lm089:
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:
[Xperia Z1 Compact Android Development] tramp20:
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 :)
[Xperia Z1 Compact Android Development] lm089:
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
[Xperia Z1 Compact Android Development] MSe1969:
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 ...
[Xperia Z1 Compact Android Development] lm089:
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...
[Xperia Z1 Compact Android Development] yldun:
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.
[Xperia Z1 Compact Android Development] MSe1969:
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

https://sourceforge.net/projects/lin17/files/amami/LineageOS_17_signed/lineage-17.1-20210309-UNOFFICIAL-signed-amami.zip/download

Security String 2021-03-05

System Webview on 88.0.4324.152

B. Pre-installed microG build variant with additional security patches

https://sourceforge.net/projects/lin17/files/amami/LineageOS_17_signed/lineage-17.1-20210307-UNOFFICIAL-microG-signed-amami.zip/download

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.
[Xperia Z1 Compact Android Development] lm089:
Just for info: even today the updater tells me that there aren't any updates. No problem for me, though
[Xperia Z1 Compact Android Development] MSe1969:
Which build Variant? And to all: Same experience?
[Xperia Z1 Compact Android Development] lm089:
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).
[Xperia Z1 Compact Android Development] marsa47:
^ My update via TWRP was fine.
[Xperia Z1 Compact Android Development] waterpolo:
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).
[Xperia Z1 Compact Android Development] MSe1969:
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.
[Xperia Z1 Compact Android Development] lm089:
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?
[Xperia Z1 Compact Android Development] MSe1969:
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?
[Xperia Z1 Compact Android Development] MSe1969:
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.
[Xperia Z1 Compact Android Development] tramp20:
Yes on standard on several Z1c :-(
[Xperia Z1 Compact Android Development] lm089:
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
[Xperia Z1 Compact Android Development] MSe1969:
Still now, after having pressed "refresh"?
[Xperia Z1 Compact Android Development] MSe1969:
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.
[Xperia Z1 Compact Android Development] lm089:
Alright, now it came back to me; had confused the situation with another issue I recently had with my Xperia tablet. So let me recap the current situation with my Z1c:

Device is still running the January build; updater keeps telling me that there aren't any updates, no matter how often I press "refresh"

flashing one of the recent updates (February or March) from twrp both result in this behaviour:

after installing in twrp choose "boot to system"

LOS boot animation appears and runs for an exceptionally long time (feels like 3 - 5 minutes)

then still in the animation screen goes black, then SONY logo appears

no boot animation now, but reboot to TWRP

What I tried so far to solve this:

from the working January build I created a simple backup of just the boot partition; after trying to flash a newer build, and then back in twrp I restore just that boot image ==> does not help

before flashing the update build uninstall Magisk (V 21.4) from TWRP, then flash the update ==> down't help either

So at the moment it looks like I'm stuck at the January build.

Apart from doing a complete wipe then trying a new setup: any idea what I could try to solve this?
[Xperia Z1 Compact Android Development] MSe1969:
In regards to the "Updater does not show any updates" issue:

If you go to Settings - About Phone - Android Version : What is the exact value shown at 'LineageOS-Version' ?

In regards to the issues to flash via TWRP, please try the following:

Make a full backup and copy / store it to a different place than Internal memory (you may need it later!)

Next, use the option "Fix SELinux contexts" in the "Extended" menu, reboot to system (just to see, whether it boots normally), and reboot again into TWRP. If you end up in a bootloop, proceed with step 4.

Now try to flash the update again.

If unsuccessful, make a backup of your internal memory, too

format the /data partition and reboot to recovery. /That's why you must make a backup of Internal memory!)

If your device has been encrypted before, don't restore anything, but just flash the January build again, reboot and encrypt the device again.

Reboot to recovery, restore your full backup and restore your internal memory.

Reboot to system and verify, that all is fine.

Reboot to recovery and flash the update.
[Xperia Z1 Compact Android Development] lm089:
Before I begin, just to be sure: with "internal Memory you reference the /data partition, correct?
[Xperia Z1 Compact Android Development] MSe1969:
Not exactly.

I mean the portion of it, which is visible to your apps, and appears, when you connect your phone via USB and allow file transfer.

Or in other words, that part you can see in a non-root file explorer app like the shipped file browser.

Also often referred to as "internal SD" card, the target of the symlink /sdcard.

That part, which is skipped, when you do a full backup in TWRP.
[Xperia Z1 Compact Android Development] lm089:
it says "17.1-20210114-UNOFFICIAL-signed-amami"
[Xperia Z1 Compact Android Development] MSe1969:
Hmm, ok - could you please do another thing?

Connect to the phone with a root terminal (either via adb or in TWRP with mounted /system partition, whatever) and give me the output of the command grep UNOFFICIAL /system/build.prop
[Xperia Z1 Compact Android Development] lm089:
amami:/ $ su
amami:/ # grep UNOFFICIAL /system/build.prop
ro.lineage.version=17.1-20210114-UNOFFICIAL-signed-amami
ro.lineage.releasetype=UNOFFICIAL-signed
ro.modversion=17.1-20210114-UNOFFICIAL-signed-amami
[Xperia Z1 Compact Android Development] MSe1969:
Thanks - hmm, ok, then I really don't have a good explanation, why the Updater does not show you the update...

@115ek - maybe I am blind, but I have verified each entry of the amami.json file already. Maybe you see something, which I have overlooked?
[Xperia Z1 Compact Android Development] lm089:
Unfortunately didn't work. Performed all steps, skipping #6 as the device is not encrypted.

There's only one difference to the situation before:

before the device stopped booting after ~5 minutes into the boot animation. After performing step #2 (SE Linux fix) the boot animation apparently now goes on forever; I forced stopping boot up after ~10 minutes.

Meanwhile I'm back up @ the January build.

Before I go ahead and do a complete clean installation: any more ideas what I could try to do?
[Xperia Z1 Compact Android Development] MSe1969:
I had a funny situation once with a different device (S2 tablet):

I had to re-enter TWRP and manually wipe cache and dalvik and afterwards it booted ok. Maybe worth a try?
[Xperia Z1 Compact Android Development] lm089:
Had that too several times in the past. So I tried that already.

Never mind if this can't be solved remotely; this is my secondary device with just a few apps installed, and I use Titanium to backup my data.
[Xperia Z1 Compact Android Development] 115ek:
Maybe something was messed up with the ro.lineage.releasetype :unsure:

I'm going to check that on my side if I get some time (most likely at the weekend).

@lm089 could you get a log after searching for updates?

adb logcat -b all > logcat.txt

Else a quick and dirty solution would be flashing manually. But you told that you ended up in a bootloop, right? That's strange, though.

Is anyone here who did a successful update to the march version - on microg or standard build?
[Xperia Z1 Compact Android Development] waterpolo:
Dirty flash in TWRP was working for me, but I can't for some reason Magisk working. I restore the boot.img from january and then everything working smooth. I haven't see any bootloop.
[Xperia Z1 Compact Android Development] lm089:
here's the log file just before I reset and clean flash my Z1c:

UPDATE: well I tried, but upload's not working (from PC). OK to send it via PM? Or other preferences?

UPDATE 2: last attempt, this time using Chrome instead of Firefox...

UPDATE 3: still not working; see PM please
[Xperia Z1 Compact Android Development] 115ek:
Could you check if it finds updates when you set SE linux to permissive by

setenforce 0

You need to be root for this, of course.

Enable root over adb in developer options for example and then use

adb root && adb shell setenforce 0

EDIT: I don't think that matters here. Please see below.
[Xperia Z1 Compact Android Development] 115ek:
@MSe1969

By seeing the following line in the log @lm089 supplied I'm pretty sure it's related to lineage.updater.uri

03-16 14:03:28.821 7062 7062 D UpdatesActivity: Checking https://download.lineageos.org/api/v1/amami/unofficial-signed/eng.androi.20210114.180500

Could you check that?

EDIT: Can someone share the output of

adb shell getprop lineage.updater.uri

It should be

https://raw.githubusercontent.com/lin17-microg/OTA/lineage-17.1/amami.json

If it's not, that causes the update problems.
[Xperia Z1 Compact Android Development] tramp20:
F:\FastBoot>adb devices

List of devices attached

CB5A20MV00 device

F:\FastBoot>adb shell getprop lineage.updater.uri

F:\FastBoot>
[Xperia Z1 Compact Android Development] tramp20:
@All

All who are not able to install Magisk 22.x in LOS 17.1 or 18.1 (installing the magisk-v22.0.zip with TWRP) should read this thread (started by me):

https://github.com/topjohnwu/Magisk/issues/3636

especially the last postings from bleckdeth.

Patching the boot.img for our old Z1c is no longer necessary.

Only a simple patch in the magisk-v22.x.zip is necessary. I did it already several times in LOS 17.1 and 18.1 to help testing.

I hope that will survive the next OTA too (if it will come).
[Xperia Z1 Compact Android Development] lm089:
Ok, I just did a complete fresh and clean install of the February build because I wanted to check the updater. Result: no update found.

Thanks for hinting; you might remember that I had that problem, too. Now with the newly encountered bootloop after updating this LOS zu the latest builds I decided to do a complete fresh/clean install of my Z1c. Because I had fully working backups I dared to also install Magisk V22 - and it's working now. So at least in my case I assume that over the years my device had gotten "dirty" somehow, and that I have a "clean" setup now.

On the other hand, after reading your linked github discussion I wonder however whether that is probably only temporary? I'll keep an eye on this
[Xperia Z1 Compact Android Development] tramp20:
The patch is only needed for the first installation of Magisk until tjohnwu has changed his code (at least this bug is recognized/confirmed by him).

Updates to a newer build of Magisk are possible without problems.
[Xperia Z1 Compact Android Development] veloc_h:
Same experience: the first from January 14