[DISCONTINUED][ZS620KL] LineageOS 18.1 (Android 11) for the Asus Zenfone 5z

[ThE_MarD]

@decentguy49 oh wow, neat! Tbh I figured SafetyNet needed to pass hence I asked about Magisk and any mods heh, well that's good news if you didn't need to do that stuff. Thanks for the information bro!

 

[decentguy49]

@decentguy49 oh wow, neat! Tbh I figured SafetyNet needed to pass hence I asked about Magisk and any mods heh, well that's good news if you didn't need to do that stuff. Thanks for the information bro!

i never had any issue with Gpay or any banking apps, not even on LOS17.1 (never used any Mods).

If you need any more info, let me know bro.

 

[ThE_MarD]

@decentguy49 even on 17.1? Hmm, by chance did you somehow relock your bootloader? Or is it still unlocked?

 

[decentguy49]

@decentguy49 even on 17.1? Hmm, by chance did you somehow relock your bootloader? Or is it still unlocked?

no bro, bootloader is still unlocked

 

[ThE_MarD]

Cool, ok thanks @decentguy49 for all the info!

 

[tartutic07]

Just a quick one, is NFC for contact less payments (gpay) working in this ROM.?
I am on another ROM where NFC is not working. And u miss it for contact less payments

 

[ThE_MarD]

Heyyo @tartutic07 , it was confirmed working here by decentguy49

https://xdaforums.com/t/official-zs...for-the-asus-zenfone-5z.4260769/post-85514089

 

[tartutic07]

Heyyo @tartutic07 , it was confirmed working here by decentguy49

https://xdaforums.com/t/official-zs...for-the-asus-zenfone-5z.4260769/post-85514089

He says Gpay is not working. But banking apps are.
All good. I am planning to change my ROM anyways.

 

[ThE_MarD]

He was saying it was working for him both banking and GPay. If by chance GPay isn't working for you? You might need to use Magisk and mods, but decentguy49 said he never had to though

https://xdaforums.com/t/official-zs...for-the-asus-zenfone-5z.4260769/post-85524419

 

[tartutic07]

He was saying it was working for him both banking and GPay. If by chance GPay isn't working for you? You might need to use Magisk and mods, but decentguy49 said he never had to though

https://xdaforums.com/t/official-zs...for-the-asus-zenfone-5z.4260769/post-85524419

Cool. I will check it out when I install the OS.

 

[h1ghn3zZ]

Thanks to @ThE_MarD for continuing this wonderful work. I was on the 17.1 ROM and was about to give up using this phone at the beginning of the year when Asus stopped giving out vendor security patches. Then, this ROM gives new life to my phone.

So far, i did not experience any problems. Banking apps (where i have accounts) and Gpay are also working fine.

I use Gcam which is also working fine. Battery drain is minimal.

 

[ThE_MarD]

Heyyo @h1ghn3zZ I'm super glad you're enjoying this! This is just a fun hobby for me since I have a family and I don't have time to sit down and play video games for hours on end lol... but achieving things on AOSP is definitely more rewarding as others get to enjoy the result of my hobby too.

Tbh vendor security patch number is fluff lol... technically? It encompasses device firmware as well, but there isn't a good way to test vendor security patch level like there is for system security patch level as a lot of vendor portions have proprietary code (especially the bootloader), so there's no way to determine if vendors are outright lying about their vendor security patch level and missing security patches.

The only serious security flaw I remember with vendor was long ago where qseecomd could be exploited if a rogue apk was granted root permissions and it could bypass security passwords... but our device is so new that it doesn't apply to us... but still, root is a major security flaw anyways, as the whole idea behind it is administrative access and bypassing selinux (Security Enhanced Linux), so not having root on your device and keeping up to date on system security patches and proper selinux enforcing are great ways to keep your device secure, afterwards? It's pretty much avoiding sketchy downloads and apk's (as sometimes pirate modded apks can carry the risk of security exploits too). That's why all I do with my devices is LineageOS and GApps. If I need root for testing changes to my devices? I only use adb root from my PC and then when I'm done I reboot my device.

 

[h1ghn3zZ]

Thanks for the reply and comments @ThE_MarD , specially the in-depth info on security.

In my previous years, i was naïve and foolishly install pirate modded apk's. Of course, in those days, i used my phone for gaming, mostly, so security was of little concern.

But now, i use my phone for important business work as well as financial matters. So, security is a top priority. That is why, i never root my phone even if i use custom roms. Although i test different roms, i always decided to use LOS for my daily driver, as soon as it becomes Official. I made sure that the phones i bought receive LOS and never settle for those high-specs, but low cost devices which flooded the market nowadays.

 

[ThE_MarD]

@h1ghn3zZ I used to be the same too lol, albeit Dolby Atmos mods sound good? That forced selinux permissive is painful so I eventually gave up on those.

 

[h1ghn3zZ]

I can't really comment on that because i rarely use my phone for listening to music or watch movies etc.

Anyway, i just want to mention here that its been a breeze using this ROM as my daily driver

 

[tartutic07]

So I get an error when setting up the Google pay. Anyone else facing this issue?

 

[Deleted member 11587027]

The fingerprint drivers are messed up in this 100.10.107.123 update. But 100.10.107.110 had proper fingerprint drivers.
Could you look into the issue? It usually happens when my palms tends to become sweaty or oily sometimes.
Use the drivers from 100.10.107.110 to resolve it.

 

[ThE_MarD]

Heyyo @tartutic07 , here is a guide that I saw on heart (Lenovo Z5 Pro GT) in order to pass that but I haven't tried it as I've haven't used Magisk or mods in years...

Google Pay - Lineage OS 18.1 - 16/09/2021 - Working

I have made a purchase in an actual shop for goods using Google Pay on Heart. My device has a locked Bootloader.

These are the steps I took.
1. Install Magisk
2. Hide the Magisk app
3. Turn on MagiskHide (I did nothing more than this, I didn't hide any other apps rather than those set by default, you may need to hide your bank apps if you have them installed, but I cannot confirm this)
4. Install MagiskHidePropsConf - reboot
5. Install a terminal app (I used Termix)
6. Open terminal and type props (if you're using Termix run su first to grant permissions)
7. Follow institutions https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#usage I chose the "Edit device fingerprint" option and selected the Pixel 5 as the device id.
8. I cleared data for Google Play Services and Google Play Store and rebooted
9. when you open Google Pay you should be able to add card
10. Go to shop, consume.

@mahafa , tbh this is the first I've heard of FP issues due to drivers, but I can make a test build with downgraded ones from v100 just to see if it helps. I'm on night shift right meow, but once I get some spare time I'll make the build.

 

[ThE_MarD]

@mahafa , I just checked our vendor blobs and the fingerprint drivers haven't changed since 100.10.107.92, so I'm not quite sure what your problem is sorry. You could backup all your important data off of your device and flash a fastboot ROM onto your device of the stock ROM and test if that .123 build the fingerprint sensor works ok or if .107 is the good one?

You can see here, Dec 19, 2020 we imported from .92 and then only modified those blobs to work with our source-built vendor

History for Z01R/proprietary/vendor/lib64/libgoodixfingerprintd_binder.so - TheMuppets/proprietary_vendor_asus

Contribute to TheMuppets/proprietary_vendor_asus development by creating an account on GitHub.

github.com

The only blobs that changed on 123 was a few minor blobs unrelated to FP

Z01R: Update blobs from UL-Z01R-WW-100.10.107.123-user · TheMuppets/proprietary_vendor_asus@a3a3dcc

from WW_Z01R-WW_user_100.10.107.123_20210131-user-20210131 Change-Id: I609da8d3dcbe258784e2097df494d9971633a9cb

github.com

 

[Deleted member 11587027]

@mahafa , I just checked our vendor blobs and the fingerprint drivers haven't changed since 100.10.107.92, so I'm not quite sure what your problem is sorry. You could backup all your important data off of your device and flash a fastboot ROM onto your device of the stock ROM and test if that .123 build the fingerprint sensor works ok or if .107 is the good one?

You can see here, Dec 19, 2020 we imported from .92 and then only modified those blobs to work with our source-built vendor

History for Z01R/proprietary/vendor/lib64/libgoodixfingerprintd_binder.so - TheMuppets/proprietary_vendor_asus

Contribute to TheMuppets/proprietary_vendor_asus development by creating an account on GitHub.

github.com

The only blobs that changed on 123 was a few minor blobs unrelated to FP

Z01R: Update blobs from UL-Z01R-WW-100.10.107.123-user · TheMuppets/proprietary_vendor_asus@a3a3dcc

from WW_Z01R-WW_user_100.10.107.123_20210131-user-20210131 Change-Id: I609da8d3dcbe258784e2097df494d9971633a9cb

github.com

Oh ok, then it's only my issue because for me it started with official asus firmware 100.10.107.123 and official lineage builds so I thought its because of 100.10.107.123 firmware and it's blobs.

I think I have to be more careful that dirt doesn't get in to fp sensor and make sure my hands are dry. It's very rare that it happens.