• 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][11] LineageOS 18.1 [OFFICIAL]

Search This thread

userx404

Senior Member
Feb 14, 2012
110
15
Linz
NOTE
Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored.

Does anyone know where we can report bugs? I'm surprised the lineage team is okay with pushing out a nightly without a working speaker.

I sent some logs to @Olivier with an other issue, but not got a response jet.
I'm also interested whats the best way to put the mentioned logs.
@Cerhio
Is not a killer bug but it's a bug. But keep in mind LOS 18.1 for XZ2c is still really new (atm) and there could always be some bugs.
 

landsome

Senior Member
May 4, 2015
361
89
By the way, what is the best way to update LOS18 from a previous nightly?

I have gapps and magisk installed, and that may complicate issues. I had no end of problems when updating on the LOS17.1 (again, with gapps and magisk), both OTP and via recovery.
 
Last edited:

30jp

Member
Sep 25, 2020
23
17
By the way, what is the best way to update with gapps and magisk installed?

I had no end of problems when updating on the LOS17.1, both OPT and via recovery.
I wanted to install opengapp 10, but I couldn't. I think you need opengapp 11 for lineageOS 18.1, but it's not available on their site yet. So I don't have Google right now. You can download it through other channels, but I haven't tried that. Everything is working satisfactorily now without Google and won't have time to test things out for the next few weeks. Unless LineageOS 18.1 with MicroG is available for my XZ2 c.
 

landsome

Senior Member
May 4, 2015
361
89
I wanted to install opengapp 10, but I couldn't. I think you need opengapp 11 for lineageOS 18.1, but it's not available on their site yet. So I don't have Google right now. You can download it through other channels, but I haven't tried that. Everything is working satisfactorily now without Google and won't have time to test things out for the next few weeks. Unless LineageOS 18.1 with MicroG is available for my XZ2 c.
Thanks for the answer. Unfortunately, my question was not clear (I edited it the meantime).

I already have LOS18 with gapps and magisk installed. (Test opengapps for 11 are available here: https://sourceforge.net/projects/opengapps/files/arm64/test/; I have tested them on 4 phones and a dozen different ROMs, and they work flawlessly.)

Specifically, what I wanted to know was the best route for updating to a new nightly the LOS18 that I have already installed, keeping in mind that I use magisk and gapps. On the previous LOS17 I discovered that the only sure way to do it is: uninstall magisk, sideload the new nightly and gapps, then reinstall magisk. But that's very cumbersome.
 

30jp

Member
Sep 25, 2020
23
17
Thanks for the answer. Unfortunately, my question was not clear (I edited it the meantime).

I already have LOS18 with gapps and magisk installed. (Test opengapps for 11 are available here: https://sourceforge.net/projects/opengapps/files/arm64/test/; I have tested them on 4 phones and a dozen different ROMs, and they work flawlessly.)

Specifically, what I wanted to know was the best route for updating to a new nightly the LOS18 that I have already installed, keeping in mind that I use magisk and gapps. On the previous LOS17 I discovered that the only sure way to do it is: uninstall magisk, sideload the new nightly and gapps, then reinstall magisk. But that's very cumbersome.
Hi Landsom,
Thanks for the Opengapps site, I hadn't found it yet, I will definitely use it one day. With the last update of 18.1, I also had to reinstall Magisk. That goes pretty quickly. Change Magisk apk to zip, boot into recovery and install Magisk zip. In Lineageoss 17.1 I never had to do that, ota update and done. I think I used payload dumper then, but I'm not sure anymore, to install Magisk. https://www.thecustomdroid.com/how-to-extract-android-payload-bin-file/
I don't remember exactly how I did that. The notes are at home and I'm on vacation now ;-)
 
I use LOS recovery to flash Magisk. I have the old Magisk 21 on my sdcard. After flashing, I install Magisk manager and update to 23 version (direct installation)... That's all (I don't use gapps).
Growing desperate here. Reinstalled LOS again after wiping the phone from LOSrecovery (is that the best way to wipe everything?). Then flashed Magisk 21.4 through LOSrecovery/ADB sideload, installed the Magisk App - and then mobile internet is gone. I am using Afwall and AdAway, but the internet isn't working even before that. Where could I grab a log that is relevant?
I also noticed WiFi having issues when connecting to a different router then my own. Am I facing a hardware issue?
 

Cerhio

Senior Member
Feb 25, 2013
204
29

Raphos

Senior Member
Jul 31, 2015
231
83
Elsass
Growing desperate here. Reinstalled LOS again after wiping the phone from LOSrecovery (is that the best way to wipe everything?). Then flashed Magisk 21.4 through LOSrecovery/ADB sideload, installed the Magisk App - and then mobile internet is gone. I am using Afwall and AdAway, but the internet isn't working even before that. Where could I grab a log that is relevant?
I also noticed WiFi having issues when connecting to a different router then my own. Am I facing a hardware issue?
Hi,

Sorry I have no idea… I'm just a lambda user... I'm using AdAway too but not Afwall.

Did you install LOS18 direct after stock ?

Sometime for custom rom installation you have to install the last stock rom at first, boot once on it so that the phone can catch something from your provider. Don't ask me what, I don't know.

Did you have a look at your Apn's ? I must always create a new one with good configurations, especially for MMS and sometimes for 4G.
 
I checked the APN's according to my provider and they are fine. The weird part is that it works until the point when I flash Magisk.
I had LOS 17.1 before and in LOS Wiki they say it requires latest Android 10 firmware. It's some time ago, but I remember having done that. Where do I check if it has everything it should, do you know?

Edit: I'm on RQ2A.210505.003
 
Ok wow, OTA resulted in bootloop today and it is definitely because of something being wrong with Magisk. Happy to wipe the whole thing and start fresh. Is LOS Recovery good enough for that? Asking because their wipe functionality only says "Factory Data Reset" or something, is that what I'm looking for? And for future experiments: Do I have to do the copy-partitions-**.zip part again and could that have been the problem all along (did it once obviously when initially installing LOS on the xz2c for the first time.
 

landsome

Senior Member
May 4, 2015
361
89
Ok wow, OTA resulted in bootloop today and it is definitely because of something being wrong with Magisk. Happy to wipe the whole thing and start fresh. Is LOS Recovery good enough for that? Asking because their wipe functionality only says "Factory Data Reset" or something, is that what I'm looking for? And for future experiments: Do I have to do the copy-partitions-**.zip part again and could that have been the problem all along (did it once obviously when initially installing LOS on the xz2c for the first time.
That should not have been the problem if OTA worked before - on LOS18.

My advice: if you start fresh, install the stock rom on A and B via newflasher (don't forget to boot both to desktop), then follow installation instructions to get LOS. Skip the copy partitions part if you do that.

As for the failed OTA, did you update from the previous LOS18 nightly?
 
  • Like
Reactions: patroj
As for the failed OTA, did you update from the previous LOS18 nightly?
Yes but I don't think that's a ROM related problem. After I aborted boot and started it again, it finished booting with my Magisk modules disabled. I think there is a trouble maker among those.

And for your tips, thanks! Last weeks OTA worked without a problem. Do you mean flash stock on both partitions and then boot the phone (and I reckon with SIM in making it connect to mobile network, 4G and all?), then reboot to recovery and install LOS? And now as I'm in questioning mode: How important is the latest LOS recovery, does it have to be the same as the built all the time?
 
  • Like
Reactions: Magchild
...+ thanks to faruk, I got VoLTE and VoWiFi to work ( O2 Germany )

Could you please link to the post that helped you? Or was it via other media?

Or post the full XDA username like @robert12345678 for example? Searching this thread with faruk returns only your post @ the present & by Member does not work because nobody is using faruk only.
***
 

landsome

Senior Member
May 4, 2015
361
89
Yes but I don't think that's a ROM related problem. After I aborted boot and started it again, it finished booting with my Magisk modules disabled. I think there is a trouble maker among those.

And for your tips, thanks! Last weeks OTA worked without a problem. Do you mean flash stock on both partitions and then boot the phone (and I reckon with SIM in making it connect to mobile network, 4G and all?), then reboot to recovery and install LOS? And now as I'm in questioning mode: How important is the latest LOS recovery, does it have to be the same as the built all the time?
Yes, exactly what I suggested.

I do not typically have the latest recovery. Rarely bother to update them. But maybe it's worth the bother, who knows...

Btw, OTA worked for me last time. With gapps and magisk. So I will just skip this one, I guess.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Do I need any special steps if I install LineagoOS on my XZ2 compact Dual-sim. or is the installation proces identical for the single-sim and dual-sim devices?
    Follow the installation procedure on the official ROM site. It worked for me on the dual sim.
    1
    Just an update from me: everything is working great! Battery is awesome and it's running fast.

    Only thing I'd note is that:
    -low brightness is practically black.
    -google assistant doesn't work with "okay google" when the screen is off.
    Hi. I can not confirm that good battery life. At least not compared to stock. In standby I had with rooted stock Rom, using Greenify to kill apps in background but with activated Google location sharing, a power consumption of 1%/hour up to 2%/hour. With Bluetooth and listening music in background for 2 hours (display off) I had maybe 3% - 4%/hour.
    With lineage 18 I have 2%/h in energy saving mode, so no location sharing, reduce data transfer, etc. So best case. Normal use has already approx. 4% without music in background. For me stock was better. PS: Los 18 also rooted, Greenfield, same apps installed.

    But - generally Los 18 works really fine. No important bugs so far for me, and Rom feels really fast. And no frozen screen (I had sometimes with stock Rom - that was really annoying).
    I can confirm issue with camera button and ok Google problem when screen is off. But this doesn't matter to me. I am curious on next updates.
    1
    This rom seems stable to be daily (so far) its very responsive, battery life is ok.
    For anyone wondering: I tried A LOT gcams, only this one worked and it actually produces decent images and videos.
    I only managed to get viper4android working after freezing the built in audiofx application included with titanium backup. Using audio modification library didn't help, it actually broke v4a. Installing just v4a and enabling legacy and compatibility mode (with audiofx frozen) did the trick.
    Fingerprint is slow, cant compare with stock because i got rid of it as soon as i got the phone in my hands :)
    1
    What's the reason? Could find any explanation here. The first post only says it does not work "at the moment".
    As far as I understood, a library incompatibility.
  • 10
    The first official 18.1 build is up, enjoy: https://download.lineageos.org/xz2c
    9
    A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
    5
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.

    Code:
    /*
    * Your warranty is now void.
    *
    * I am 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 me for messing up your device, I will laugh at you.
    */

    NOTE
    Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
    Hint: "It doesn't work" is not a bug report and posts like this will be ignored.


    KNOWN ISSUEs
    • The Sony stock camera does not work at the moment.

    INFO
    This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.

    DOWNLOAD
    Official builds

    NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.

    All unofficial builds

    INSTRUCTIONS
    Just flash the builds as usual. Make sure to be on the latest stock firmware.

    SOURCE
    LineageOS
    Kernel
    3
    After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.

    General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).

    Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
    Use a STOCK TWRP
    Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.

    Newflasher:
    I used v42, probably newer versions work, too, try not to use an older version

    Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.

    Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.

    Now let's get to the process of flashing LOS:

    Step 1 - Flash an original working SONY image into Slot A:
    Boot into fastboot mode, so the blue light is on.
    Type:
    fastboot reboot bootloader
    (Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).

    fastboot --set-active=a
    fastboot reboot bootloader

    You can check that Slot A is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: a

    Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.

    Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.

    When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.

    You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.

    Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.

    Step 2 - Flash an original working SONY image into Slot B:
    Boot into fastboot mode, so the blue light is on.
    Type (similar to Step 1):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    You can check that Slot B is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: b

    WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.

    Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.

    Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.

    When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.

    You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.

    At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.

    Step 3 - Boot the original SONY image up to the home screen where the apps show:

    Actually you should be in Slot B already, but if you are not:
    Boot into fastboot mode, so the blue light is on.
    Type (similar to Step 2):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    You can check that Slot B is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: b

    Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).

    Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.

    Power off your phone.

    Step 4 - Flash twrp into Slot B

    Type (similar to Step 2):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    fastboot flash boot twrp.img

    This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.

    Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.

    Boot your TWRP in Slot B.

    WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.


    Step 5 - Flash LOS into Slot A

    Once TWRP is running, go to Wipe.

    WARNING: DO NOT perform factory reset.

    Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'

    WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.

    Go back to TWRP home screen.

    From there go to Advanced and from there to ADB Sideload.

    From the computer start installing your LOS image (sideload).

    On the computer type:

    adb sideload <Your LOS image>.zip.

    ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.

    Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c

    Download the zip file, don't unpack it, use adb sideload to upload the zip file.

    Forget about the Recovery image on the LOS homepage. You don't need it.

    When flashing completes, you can wipe Delvic Cache.

    WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.

    Do NOT install the TWRP app, skip this step.

    Reboot

    Step 6 - Boot LOS

    LOS is in Slot A, TWRP is in Slot B.

    You can alternate between the slots from fastboot.

    fastboot reboot bootloader
    fastboot --set-active=a
    fastboot reboot bootloader

    A reboot should boot LOS.

    ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.

    Let me know as feedback, if I can clarify better or if this description is ok.
    3
    Do I need any special steps if I install LineagoOS on my XZ2 compact Dual-sim. or is the installation proces identical for the single-sim and dual-sim devices?
    Follow the installation procedure on the official ROM site. It worked for me on the dual sim.