[ROM][11] [User build][Signed]Lineage-18.1-X00TD-Asus Zenfone Max Pro M1

[[email protected]]

About LineageOS

Lineage-18.1-X00TD-Asus Zenfone Max Pro M1

Build type : UNOFFICIAL


Build and signed by @[email protected] | Rajesh R

Disclaimer : ROMs are built for development purpose only. Use at your own risk.

This ROM completely compiled on lineage source code and with minimum workarounds for a successful build. Builds are signed with release-keys.Before installing, refer instructions and changelog for each builds.


About build variants

ROM-Signed release key-user build

My Projects

lineage-18.1-20210726-X00TD-user-signed.zip

fastboot-lineage-18.1-20210604-X00TD-user-signed-images.zip

lineage-18.1-20210604-recovery-X00TD.img

TWRP recovery X00TD @Vivekachooz

Features

* Changelog-25
*Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Smooth ROM experience

Instructions

Backup procedure and precaution information

Must read before unlocking bootloader and flashing custom ROM

Some explanation regarding the whole widewine L1-L3-Qbeta etc ( Info @ https://t.me/ASUSX00TD from a member )

Starting from Q builds Asus has begun wiping DRM keys if bootloader is unlocked on that build, which is actually default behavior among most other OEMs like pixels, oneplus. Flashing Q builds (Stock beta 1 or latest) or custom ROM on unlocked bootloader through TWRP will permanently loose their L1 certification. widewine keys will be wiped by firmware itself as it detects unlocked bootloader. This also explains why some people, who flashed previous stock Q beta before on locked bootloader, even though first stock Q beta had L3 which means they hadn't fixed L1 on that beta that time , retained their L1/DRM keys on reverting to pie via downgrade zip provided by asus. So in conclusion Asus Q builds/custom ROM will wipe your DRM keys if flashed on Unlocked bootloader. Flashing on locked bootloader shouldn't be any problem!

Also those who have their persist partition backed up in pie should have no problem restoring their DRM keys in case thet got wiped by Q firmware/builds
How to Backup Persist ?

Dump all partitions and make complete backup | Partition layout and structure

Recovery method

use recoveries which support persist partition backup (eg. Orangefox)
Go to recovery > Backup > tick persist > backup > store it safe somewhere with multiple copies.

How to Restore Persist ?

Go to recovery > Restore menu > select backup > tick persist partition > Restore (process similar/different for different recoveries)

Upgrading to LineageOS 18.1

1. Make a backup of your important data
2. Download the build and also Gapps.
3. Download proper addons packages GApps for Android 11/Lineage OS 18.1
4. Make sure your recovery and firmware are up to date
5. For clean flash, Format your system,vendor,data and cache partition partition to install ROM and Gapps.
6. For installing updates format system,vendor and cache partition. keep data partition intact to flash ROM and Gapps.

Secure ROM experience

Avoid permissive selinux and rooting methods for secure ROM experience.
Refer
1. Root & SELinux Risks
2. TWRP password protection
3. TWRP encryption

Screenshots

Upcoming builds ( Only for volunteer testers )

lineage-18.1-20210529-X00TD-user-signed.zip

* To test Safetynet

To test any ROM

Requirements:

Windows/linux Pc
adb drivers
Usb cable.

Steps to take log:

1. Install adb drivers in pc and enable usb debugging mode in phone. Also enable root debugging if needed.
2. Connect phone through usb and type the command "adb logcat -d>logcat.txt" in adb command window.You can choose any name you want for txt file. If needed give admin privilege for adb command window.
3. This procedure can also be used to watch occurance of bugs at realtime by connecting phone at adb mode to pc.

Steps to take boot log:

1. Make sure adb is enabled in phone. Connect the phone in usb mode to pc and open adb command window.
2. Switch off the phone and type "adb logcat -d>bootlog.txt".
3. Initially "waiting for the device" message is noticed on adb command window and switch on the phone now. once the device powers on, boot log is recorded.

log text files are stored in location where adb drivers are installed.

Note : Test builds are released here and intended to test upcoming fixes and features.

Source Code

Kernel source code : https://github.com/LineageOS/android_kernel_asus_sdm660

Kernel developer credits : @SagarMakhar, Lineage Team


Credits
Google's AOSP Project.
Lineage OS for the source code and The Open GApps Project.
Contribute to Lineage OS at https://paypal.me/LineageOS
Contribute to Gapps at https://www.paypal.com/donate/?toke...EScTbkNmciIDl9n5LyDW&country.x=US&locale.x=US
Thanks to developers and their contribution on custom ROM development for Asus zenfone max pro M1.

Special thanks for the build server admin and @abhishekt295

Tester credits
1. @Orion281
2. @patkk

It's all free, but donations are welcome
Donations will be contributed to server maintenance

Support developers on their respective threads

Feedback and bug reports are welcome

Kindly use english language on comment section​

 

[[email protected]]

Changelog​

1. lineage-18.1-20210409-UNOFFICIAL-X00TD.zip
* Initial build.
* Engineering build properties
* Permissive selinux.

2. lineage-18.1-20210412-X00TD-user-signed.zip
* Enforcing selinux and user build properties
* Release-key signed.
* Android Verified Boot (AVB)

3. lineage-18.1-20210413-X00TD-user-signed.zip
* Fixes and kernel updates

4. lineage-18.1-20210418-X00TD-user-signed.zip
* New fixes

5. lineage-18.1-20210419-X00TD-user-signed.zip
* Fixes on DTW and battery status LED notification.
* Screen density.
* Vibration intensity control on accessibility settings.
* Clean flash recommended
* OTA support added for upcoming builds

6. OTA : lineage-18.1-20210423-X00TD-user-signed.zip
* Fixes on DTW and battery status LED notification.
* Fixes on SafetyNet Test
* Screen density.

7. OTA : lineage-18.1-20210428-X00TD-user-signed.zip
* Synced with source updates.

8. OTA : lineage-18.1-20210504-X00TD-user-signed.zip
* Synced with source updates.
* lineage recovery and fastboot zip support added.
* Safetynet fixes and lineage kernel updates.

9. OTA : lineage-18.1-20210511-X00TD-user-signed.zip
* Android Verified Boot (AVB) Enabled
* Security patch update
* Kernel updates

10. OTA : lineage-18.1-20210514-X00TD-user-signed.zip
* Updated device fingerprint and vendor patch level from latest asus android 10 beta.
* OTA link fixes.

11. OTA : lineage-18.1-20210517-X00TD-user-signed.zip
* Synced with source updates.

12. OTA : lineage-18.1-20210520-X00TD-user-signed.zip
* OTA Fixes and Synced with source updates.

13. Build : lineage-18.1-20210523-X00TD-user-signed.zip
* Test build with new features.

14. Build : lineage-18.1-20210525-X00TD-user-signed.zip
* AVB disabled and Verity Enabled.
* Locking bootloader supported. Works only with lineage recovery.
Note : Lock only if lineage recovery is flashed. If bootloader locked with twrp. Device fails to boot and only fastboot mode helps to solve the issue to unlock bootloader again.
* Dirty flash on previous build wont work. It is not OTA release. Only clean flash recommended.
* Added variable vibration control.
* Sound control features added.
* New features on dialer app.
* Adaptive sleep features.

15. OTA : lineage-18.1-20210528-X00TD-user-signed.zip
* Safetynet Fix.
* OTA supported only to lineage-18.1-20210525-X00TD-user-signed.zip

16. OTA : lineage-18.1-20210604-X00TD-user-signed.zip
* Synced with source updates and fixes.

17. OTA : lineage-18.1-20210726-X00TD-user-signed.zip
* Synced with source updates and fixes.

 

[osmosi]

 

[patkk]

I already tested it and have sent you feadback.

 

[Orion281]

SafetyNet is passing on latest build i.e. lineage-18.1-20210412-X00TD-user-signed.zip,

 

[Ramesh006]

Everything is fine but pubg footsteps sound is very low.

 

[MISONLN41]

Is GPS working? I couldn't get current location on Maps app...

 

[Orion281]

Is GPS working? I couldn't get current location on Maps app...

Yes, it's working fine for me.

 

[MISONLN41]

Yes, it's working fine for me.

Thank you. I'll try clean flash again.

 

[russelldlongno]

DT2W isn't working in the lockscreen. Any fix?

 

[[email protected]]

DT2W isn't working in the lockscreen. Any fix?

Checkout bugs. Did you check on other custom kernel?

 

[Orion281]

DT2W isn't working in the lockscreen. Any fix?

It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.

 

[russelldlongno]

It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.

I reflash it again using TWRP 3.4.0 by KudProject and currently I'm on firmware 87, yet still not working. What firmware are you using?

 

[russelldlongno]

It's working. I just checked again before replying to you. There's as option "Tape to wake" in display settings. Check if you it enabled. Also make sure you're on latest build.

I still can't fix it. I tried flashing firmware 087 via ASUS flash tool, clean flash everything, tried other custom roms if DT2W is working, still this specific ROM gives me headache. I can't find any solutions online either. Tried to flash multiple custom kernels, no luck. So how did you do it?

 

[Orion281]

I still can't fix it. I tried flashing firmware 087 via ASUS flash tool, clean flash everything, tried other custom roms if DT2W is working, still this specific ROM gives me headache. I can't find any solutions online either. Tried to flash multiple custom kernels, no luck. So how did you do it?

I'm also on the same firmware as you. I did a clean flash (wiped System, Vendor, Data, and caches). I use OrangeFox recovery. May I ask which build are you using?

 

[russelldlongno]

I'm also on the same firmware as you. I did a clean flash (wiped System, Vendor, Data, and caches). I use OrangeFox recovery. May I ask which build are you using?

The latest one (20210413). Still not working. haha

 

[Orion281]

The latest one (20210413). Still not working. haha

That's strange. Btw 20210413 build was re uploaded because previous build had some issue. Can you match this MD5 hash (9e92c5deb689891958a7ebfe150c337f) against your zip. Also, can you please post a screenshot of your display settings.

 

[russelldlongno]

That's strange. Btw 20210413 build was re uploaded because previous build had some issue. Can you match this MD5 hash (9e92c5deb689891958a7ebfe150c337f) against your zip. Also, can you please post a screenshot of your display settings.

The md5 that you gave is the same with my ZIP file. I can't give you any screenshots, at the moment, 'cause I don't know where's the setting for that. LineageOS seemed to remove it from the power menu. Anyway, there's an option in the "Display" section called "Tap to wake" (disabled by default when you first install the ROM) and I enabled it. I tested it multiple times, on and off, still no luck. What device variant are you using? Mine is 4GB/64GB. It's says on the box, "ZB602KL", but it doesn't support NFC. AFAIK, my model's supposed to support NFC. WEIRD.

 

[Orion281]

The md5 that you gave is the same with my ZIP file. I can't give you any screenshots, at the moment, 'cause I don't know where's the setting for that. LineageOS seemed to remove it from the power menu. Anyway, there's an option in the "Display" section called "Tap to wake" (disabled by default when you first install the ROM) and I enabled it. I tested it multiple times, on and off, still no luck. What device variant are you using? Mine is 4GB/64GB. It's says on the box, "ZB602KL", but it doesn't support NFC. AFAIK, my model's supposed to support NFC. WEIRD.

Mine is also 4GB/64GB midel, but it says ZB601KL on its box. This may be the cause of issue that you're facing.

 

[russelldlongno]

Mine is also 4GB/64GB midel, but it says ZB601KL on its box. This may be the cause of issue that you're facing.

Maybe? hahaha. Thanks for the reply though. As so you know, I tested some Android 11 ROMs too. I tested DotOS and crDroidand their DT2W feature doesn't work either. I also tested ArrowOS, but it's SELinux status is in "Permissive", so I can't use it. It's DT2W feature works though. Maybe some Android 11 ROMs share the same trees as this one? Who knows? Guess gotta live with it? haha

P.S. I want to use the LineageOS 17.1 from the same dev, but when I crank up the volume in full, the speaker starts to crack and it's pretty annoying.