[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-02-25)

[foresto]

January updates out. Security updates only, MicroG versios will follow in about a week when I'm back from vacation. Stay safe!

Thanks for tagging the repo, and welcome back!

 

[dmalanij]

First of all thanks and congratulations to every contributor on the Lineage OS mod for XZ1C; I really like this device so having the chance to keep it updated is great.

I'm wondering if anyone in this thread can give me some advice: yesterday I flashed Lineage OS 19.1 (in particular the build lineage-19.1-20230120-UNOFFICIAL-lilac) together with GApps (MindTheGapps-12.1.0-arm64-20220605_112439), which seems to be working fine. But I have just installed a few things and was thinking on moving to the MICROG build, so: any suggestion on how to proceed?

Based on what's said on the first post I guess the way to go is wiping everything from TWRP and flashing the mod, does it make sense? I'm unclear if I need to use a specific TWRP version and if so, which one.

On top of that not sure what could be the procedure for going back, I guess again wiping everything and flashing LineageOS and MindTheGapps...

Sorry for the questions but as I've mentioned last year, I'm totally newbie on these matters. Thanks in advance

 

[stokojmoj]

I have a problem with NikGapps.

Been using HavocOS until recently (latest v4.19) and now switching over to LOS 18.1. Mostly because I read Android Auto for some people works on LOS and also wanted to try it out and HOS hasn't been updated in a while.

I flashed the latest 18.1 build and the lates NikGapps, however, during he initial setup when trying to restore my Google backup, the restore crashes and goes back to WiFi selection screen. I tried with all NikGapps that have Google Backup, and I get the same issue.

When trying with OpenGapps and MindTheGapps, I don't get this issue, but Android Auto also doesn't work for me with them.

Has anyone encountered this issue?

 

[stokojmoj]

Forgot to mention, I tried with LOS 17.1 as well. At the initial copy apps & data screen I get the same issue. However, if I skip that and skip adding an account, add the account in Backup settings afterwards and then go to "Finish Setup", it works and I am able to restore my backed-up data. Unfortunately this workaround isn't successful on 18.1...

 

[petefoth]

Based on what's said on the first post I guess the way to go is wiping everything from TWRP and flashing the mod, does it make sense?

That may not be necessary. I would try backing up your apps and data (using TWRP and Android Backup and Restore Tools project. Then try dirty flashing the microG version

If the dirty flash desn't work, then format data, clean flash, boot, then restore your apps and data. Detailed instructions in the last part of this /e/OS forums post

 

[albenex]

Hi all,
I'm using LOS 17,1 latest version just flashed, and my need is to have Android Auto working (Peugeot e-208)

At the First i used opengapps with no luck, then wiped everything and tried NikGApps core for android 10 + NikGApps Android Auto Add-on.
Also no luck.

Tried different cables which I used successfully before (also LOS 17 but coming from older releases)
car keep saying Android Auto Error `check equipment which may be not compatible'.

Do you have any suggestion? Anyone with similar issue and who have managed to solve?

 

[petefoth]

Do you have any suggestion? Anyone with similar issue and who have managed to solve?

I've not tried it myself, but this thread looks interesting
https://forum.xda-developers.com/t/microg-android-auto-fully-working.4319159/

 

[Flamefire]

But I have just installed a few things and was thinking on moving to the MICROG build, so: any suggestion on how to proceed?

Based on what's said on the first post I guess the way to go is wiping everything from TWRP and flashing the mod, does it make sense? I'm unclear if I need to use a specific TWRP version and if so, which one.

You can try to only wipe system and install the MICROG build. But I guess the data stuff from the other GApps won't be compatible so you may need to wipe data too (factory reset).
In any case wiping cache&dalvik is a good idea.
If all fails just flash the stock ROM and then the MICROG build. Of course you (also) loose your data but that should always work.

I'm using LOS 17,1 latest version just flashed, and my need is to have Android Auto working (Peugeot e-208)
...
Do you have any suggestion? Anyone with similar issue and who have managed to solve?

derfelot has found something which may fix this. I'll likely add this to the February builds if I get to that. I can't test that though as I don't have an Android Auto device/car.
Anyway when I include that stuff I'll mention it in the changelog, so keep an eye there

 

[dmalanij]

Thanks @petefoth and @Flamefire for your replies and advices.
I ended up wiping everything (I've already lost most of the stuff few weeks ago) so was no big deal.

The only thing to remark is that on first boot I got a message that factory reset was needed and inmediately reboot into recovery. I wiped it again and from then on, everything went fine.

 

[Flamefire]

I uploaded the new updates yesterday. Took a bit longer than usual especially due to some tricky updates to the kernel and XperiaParts

 

[victor126]

I uploaded the new updates yesterday. Took a bit longer than usual especially due to some tricky updates to the kernel and XperiaParts

just did a clean install. will try out the apply modem feature this week when i drive to my sons job. usually drops connection on the way there.

 

[7alvoo]

Completely smooth update, thank you very much!
my setup:
twrp-3.7.0_9-0-lilac
lineage-18.1-20230120-UNOFFICIAL-lilac --> lineage-18.1-20230225-UNOFFICIAL-lilac
NikGapps-core-arm64-11-20220908-signed --> NikGapps-core-arm64-11-20230218-signed

 

[Arcline]

Hey, could someone use the Momo detection app and show the results? I'm curious if it detects custom rom using this rom.

 

[victor126]

Hey, could someone use the Momo detection app and show the results? I'm curious if it detects custom rom using this rom.

where is it ? play store?

 

[victor126]

where is it ? play store?

found it and it did detect magisk

 

[victor126]

found it and it did detect magisk

but safetynet checks out ok

 

[Arcline]

but safetynet checks out ok

Hey thanks! Hide the magisk app and it should be fixed.
But do you get "The device is running a custom rom" and "Init.rc is modified" in Momo?

 

[victor126]

Hey thanks! Hide the magisk app and it should be fixed.
But do you get "The device is running a custom rom" and "Init.rc is modified" in Momo

it is hidden already
using LSPosed with magisk zygisk deny list

 

[Arcline]

it is hidden already
using LSPosed with magisk zygisk deny list

Ah I see. I get the same results with Los20, that's why I'm asking. If you want to hide Magisk and su/zygisk use ether Shamiko or MagiskHide/Magisk Delta by HuskyG. Problem is, my bank account detects I'm running a custom rom and I think it has something to do with what Momo is showing.

 

[xdahippo]

Hi! First of all, thanks Flamefire and everyone else for putting in the effort to keep the XZ1 alive

I've finally found a reason to sign up to these forums, but sadly not a pleasant one: After installing this build, I need to restore my TWRP backup, but even though it includes all partitions, I can only boot the phone if I format `Data`. I have redundancy for my photos, but formatting Data loses all my apps, messages, etc, so I'm looking for a way to recover. Shouldn't Data be restorable even after a format?

Here's what I did:

• Starting situation: Custom LOS with MicroG 18.1 (built myself from the whatawurst repositories)
  • I created a full backup from TWRP 3.5 from this using `adb backup --twrp`
• Dirty-flashed Flamefire's 18.1+MicroG builds from January
• Dirty-flashed Flamefire's 19.1+MicroG builds from January
• Dirty-flashed Flamefire's 19.1+MicroG builds from February
  • I created *another* full backup from TWRP *3.6* from this using `adb backup --twrp`

Up until this point, almost everything worked fine. 4G wasn't working in the 19.1 builds though (happy to debug another day), so I decided to restore my backup. Here's where things went south:

• Restoring my first backup was very unreliable and I had to manually patch up the `archive.ab` file to skip the oem.ext4 and cache.ext4 backups. After restore, the phone boots back to recovery until I format Data
• Restoring my *second* backup worked more reliably, but again my phone boots back to recovery unless I format Data

I have *some* redundancy in case this Data partition is forever lost, but I really wonder what's going on here. Am I out of luck or is there something I'm missing?