[ROM][OFFICIAL][enchilada][13] LineageOS 20

[zyonee]

Cannot give a complete answer here, but I had similar problems a few months ago, where I screwed up my Gapps installation, and the only good way I found to fix it was a full clean setup again. :/

Yeah, that's what I was afraid of. Oh well, guess I'll have to do it when I can find the time.

 

[lord high executioner]

The update through the Updater app took WAY too long (was at around 30 percent after almost five hours, so I stopped it and decided to sideload the zip file instead.

Still living in 2015, I merely flashed the zip and then gapps. Boot loop. Turns out I needed to reboot once again to recovery to allow it to switch to the other slot where the update was flashed. Did the procedure again, this time with a reboot in between and it booted fine - or so I thought.

Crashes with Google messages, Gmail and other Google apps. So I had to uninstall and reinstall what I could, including Google Contacts and Phone. Eventually I got rid of all the crashes, but now my contacts refuse to sync, even when enabling sync for contacts.

I've done a workaround by exporting all contacts from Google on the web as a large vcf and imported them as device contacts, but I'd like to get this working properly again.

Is there a safe way to remove the gapps components including user data and then reinstalling the gapps package or am I screwed and need to backup/reinstall everything?

Just follow the wiki
https://wiki.lineageos.org/devices/enchilada/install#installing-lineageos-from-recovery
and do a fresh install BUT SKIP THE factory reset, of course (Steps 3 and 4).
That's what I did when the OTA update failed me, and it worked w/o any data loss.

 

[TemperateRoot]

Considering this as a replacement for the dated OOS11 my OP6 is running now - it's rooted and I've been fighting with Google Wallet working now that I'm temporarily back on my OP6.

Does anyone have experience with this specific case? Can I just flash this build and then not root so that I won't run into Wallet/banking app issues? Could I even flash and then lock the bootloader again?

Thanks in advance for the info!

 

[zyonee]

Just follow the wiki
https://wiki.lineageos.org/devices/enchilada/install#installing-lineageos-from-recovery
and do a fresh install BUT SKIP THE factory reset, of course (Steps 3 and 4).
That's what I did when the OTA update failed me, and it worked w/o any data loss.

Actually, this is what I already did - this is what got me out of the boot loop, but syncing contacts is still not working. Guess I'll have to backup everything and make a fresh install instead.

 

[Spaceoid]

Actually, this is what I already did - this is what got me out of the boot loop, but syncing contacts is still not working. Guess I'll have to backup everything and make a fresh install instead.

Yeah, that's my experience as well. Google apps started working again, but the syncing was broken with no way to get it back to function.

 

[lord high executioner]

Yeah, that's my experience as well. Google apps started working again, but the syncing was broken with no way to get it back to function.

Well, I need GAPPS for the Playstore only and don't sync anyhing with Google, as far as possible, so I never noticed whether it works or not.
Anthing in the logcat output?

 

[lm089]

then lock the bootloader again?

Never dared to try, but from I understand locking or unlocking the bootloader *always* results in a full wipe.

Can't really give advice on the rest as I don't use Wallet. Apart from that I really like this ROM. I never regretted the switch from OOS

 

[espionage724]

Updated from 20230606 to 20230613 and had issues with Google apps not wanting to run, some prompt about updating Google services, and Play Store kept closing on startup. Reflashing Gapps didn't help. I ended up factory resetting and Gapps seem fine on a fresh 20230613 install.

I like the return of the network traffic monitor!

 

[Spaceoid]

Updated from 20230606 to 20230613 and had issues with Google apps not wanting to run, some prompt about updating Google services, and Play Store kept closing on startup. Reflashing Gapps didn't help. I ended up factory resetting and Gapps seem fine on a fresh 20230613 install.

I like the return of the network traffic monitor!

Won't help or anything, but for me, the update went smoothly, no issues so far.

 

[solidsnake_119]

6. Can the camera do 60 FPS video recording from any app from LOS?

I wonder if anyone has any insights into this?

 

[lm089]

A very big THANK YOU to all the devs involved!

 

[poruid]

Builds of 6 June and 13 June 2023 have app audio continuously interrupted; 3 seconds audio, 1 second silence. Very annoying, a regression ?
Falling back to build of 23 May 2023 (*) restored the audio functionality. Status of the build of 30 May 2023 has not been checked)

First noticed this when running an Internet radio app concurrently with Google Maps and the audio of the radio app would function correctly again after closing Maps (with Android Auto the Maps app is always active). Did not notice this during normal calling.

(*) fallback with adb sideloads of build and MindTheGapps in Recovery; also most of the Google apps needed reinstall or update afterwards.

 

[gamertag128]

A very big THANK YOU to all the devs involved!

View attachment 5932439

Incredible that we got this feature Huge respect to the devs!

 

[Spaceoid]

Anybody here having problems with his health insurance app?
I use Zygisk, Deny List, renamed my Magisk package, and I always freeze my Magiks app before using my health insurance or banking app. I also use the Universal SafetyNet Fix.

Worked well for both apps till last week. Since then, I cannot use my health insurance app (DAK, Germany) anymore. I always get a prompt that rooted devices AND custom ROMs are not allowed.
I assume the app started detecting my ROM, not my root.
Anybody having similar experiences and maybe some help?

 

[beneda]

Anybody here having problems with his health insurance app?
I use Zygisk, Deny List, renamed my Magisk package, and I always freeze my Magiks app before using my health insurance or banking app. I also use the Universal SafetyNet Fix.

Worked well for both apps till last week. Since then, I cannot use my health insurance app (DAK, Germany) anymore. I always get a prompt that rooted devices AND custom ROMs are not allowed.
I assume the app started detecting my ROM, not my root.
Anybody having similar experiences and maybe some help?

Hello,

Same problem, i've rooted mine, install Magisk and all SafetyNet Fix etc, Bank app works well but i've CTS profile match in FAIL so because of that can't use Wallet App ( Google pay ).. don't know how i can bypass this error, i've tried many things without succes. I'am currently searching a rom on android 13 with CTS profil match in succes natively without root like AwakenOs. If you know a rom that have Cts on succes let me know

 

[Spaceoid]

Hello,

Same problem, i've rooted mine, install Magisk and all SafetyNet Fix etc, Bank app works well but i've CTS profile match in FAIL so because of that can't use Wallet App ( Google pay ).. don't know how i can bypass this error, i've tried many things without succes. I'am currently searching a rom on android 13 with CTS profil match in succes natively without root like AwakenOs. If you know a rom that have Cts on succes let me know

I even got CTS profile match. Still, the DAK (health insurance) app won't work.

 

[beneda]

I even got CTS profile match. Still, the DAK (health insurance) app won't work.

What's you've followed to have Cts profil in succes, if you can help me to do that, you will be a life saver

 

[Spaceoid]

What's you've followed to have Cts profil in succes, if you can help me to do that, you will be a life saver

I just followed this link:

Works with the current version of Magisk and all modules, too.

 

[beneda]

I just followed this link:

Works with the current version of Magisk and all modules, too.

Thank you very much video help me, but i used this :

for 26.1 and safetynet-fix-v2.4.0-MOD_1.2.zip change and fix it

 

[lm089]

Anybody here having problems with his health insurance app?
I use Zygisk, Deny List, renamed my Magisk package, and I always freeze my Magiks app before using my health insurance or banking app. I also use the Universal SafetyNet Fix.

Worked well for both apps till last week. Since then, I cannot use my health insurance app (DAK, Germany) anymore. I always get a prompt that rooted devices AND custom ROMs are not allowed.
I assume the app started detecting my ROM, not my root.
Anybody having similar experiences and maybe some help?

Had or have a similar issue esp. with the health insurance app (TK, Germany, in my case). To be exact: could get to work but only to a certain extent. Esp the app would not let me connect my insurance card via NFC. On the other hand, most banking apps aren't a problem. Another app I never managed to run on my OP is the German Sparkasse PushTan app.
What's really strange about this, though, is the fact that I managed to install and run both the TK app, incl. NFC connection as well as the Sparkasse app on my old Sony Xperia Z1c running an unofficial version of LOS 18.1. That phone is NOT rooted at all. Maybe the phone is just too old/too exotic for the app devs to bother and find ways to detect a tampered device...