yashsingh1/xdaforums huggingface dataset:
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] hafiz97_azim:
I just flashed the latest 20210514 build and playstore is not certified. Safetynet test also failed with CTS profile match. I clean flashed with 087 firmware and MindTheGapps 20210412. Should I try flashing with Q beta firmware instead?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Try with latest Q beta firmware or switch back to previous build. Everything same except build fingerprint. Latest asus fingerprint is not identified by safetynet so CTS fails.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] hafiz97_azim:
I tried flashing Q beta firmware and its still failed safetynet test.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I prepared build with auto record all calls option . If you want I can share build or patch. :)
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Good option. Share the patch. I will try to add this feature .
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Noted. Will be fixed by using old fingerprint. Meanwhile you can use 20210511 build on dirty flash.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
So, can I finally relock my bootloader if I install the latest LineageOS build (20210514)? AFAIK, AVB is supported now. I'm planning to use LineageOS recovery and this ROM if it supports it.

Downside is: DT2W is still not working. LineageOS current mainatiner, @Vivekachooz, managed to fix the issue on his Hackneyed kernel. It says in the changelogs.

TY.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Locking bootloader on this ROM is not tested. But this ROM project also available in fastboot mode containing signed images. As per document from AOSP, bootloader which support AVB allow locking bootloader only when signed images is flashed to device through fastboot and later OTA can be applied through signed recovery.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
That's an easy question to answer. No, you can't, it's impossible. The only way to relock the bootloader on this phone is to install stock firmware.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Maybe some developers will find the way to do that. For now I dont know any working solution to relock the fastbook. Even when you relock fastboot via stock software ( I havent tested it) you will not have any possibility to update software via OTA.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
Yep, you can't get any OTA updates on an unlocked device. Although I've unlocked my phone using official ASUS tool for that. When you do that, its serial number is recorded on ASUS servers. May be if you unlock the phone with unofficial unlocker it doesn't happen. Don't know about that.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
It's building now! Finally!

android #32138 · LineageOS

X00TD 20210518

buildkite.com
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I already use that source code with minor changes related to kernel like BFQ IO , westwood for wifi or SDR and changes for Dialer which have auto record option. You could download image from my previous posts and perform tests. The system is very stable so I think that official lineageOS for our phones will be great. :D NExt step will be kernel 4.19 :)
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
Official LOS 18.1 build - https://download.lineageos.org/X00TD
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] ThinkingTwice:
I cannot express my gratitude enough for all the hard work you have put into this Rom, and now for the official release!

One question that has come up before, but there doesn't seem to be a clear and definitive answer to it either on this thread or the Lineage website, is what Asus stock version should we be on when flashing LOS 18.1?

From what I could gather, we should not flash LOS 18.1 from any of the Android 10 versions (432 and 438), and instead should do so from Android 9. But which of these version should we choose between 0.82, 0.84, and 0.87?

Also, could the different stock versions from which we flash LOS 18.1 be the cause of certain issues? (I have had wifi and network issues with 0.87 I believe, and I have almost always faced the "slow charging" issue on both the stock rom and LOS 16)?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
How many of you are there?

As for the question, it doesn't really matter.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Check the device fingerprint in the ROM. If it uses android 10 fingerprint use the same stock ROM as base and flash your custom ROM. Official lineage and this ROM using blobs from .438 android 10 beta. That is "asus/WW_X00TD/ASUS_X00T_2:9/QKQ1/17.2017.2012.438-20201203:user/release-keys"

So you must be in stock android 10 beta .438 to flash this official lineage OS or this ROM project.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Good News, Asus Zenfone max pro M1 support locked bootloader in custom ROM.

Supported ROM : https://download.pixelexperience.org/X00TD ( Plus Edition - android 11 )

Proof :
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
It's a shame I'm not that fluent in Hindi but I'll try those two commands on an official 18.1 build.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
You can lock bootloader in lineage but You may face issue installing gapps after locking bootloader in lineage recovery. Pixel experience ROM used inbuild gapps in their build and it is also signed.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
I never use Gapps, so it shouldn't be a problem.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Rasyad:
since we already have official version of lineage os, do you have plan to add signature spoofing mate? @rajesh@xda

sadly official lineage os wont accept sig spoofing due security issue
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
No. The signature spoofing could be an unsafe feature. Instead you can opt for "lineage OS for microG". They support signature spoofing.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Rasyad:
so what the difference between this build and the official one? and los4microg a11 is doesnt support xoot yet
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
This project built on user build properties. Contains extra features and also signed by private keys. Official lineage OS uses userdebug builds and signed by lineage keys.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
I successfully LOCKED my bootloader. TY for the video above!

PS. I'm using LineageOS 18.1 (Offcial) BTW.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Any bootloader warning on startup?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
Hi Rajesh,

The last OTA broke my gapps as OTA ran and system just got booted or I didn't realise gapps needs to be flashed. So the question. Can OTA scripts be modified to pause and remind to flash gapps or just not break the gapps previously installed?

Thank you for the wonderful ROM.

Sunil
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
No issue. Just re

No issue. Just reboot to recovery wipe system and vendor. Flash ROM and Gapps. Reboot. Since gapps is not included in this project try to flash OTA manually using TWRP. OTA is provided to ease update installation without losing Userdata.

Dirty flash wont affect gapps installed.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
OK, I can confirm that bootloader locking finally works.

I flashed official LineageOS recovery (which is pretty lackluster imho, but that's beside the point :)). Then I installed official LOS 18.1 build, rebooted into it, set pin code, although I don't think it's necessary, and rebooted back into bootloader.

Then I entered two commands which previously never worked: # fastboot flashing lock # fastboot flashing lock_critical. (I did it on Arch, hence the symbol of root terminal). Then rebooted one more time, the phone automatically booted into recovery with the message about obligatory factory reset. Don't freak out when you see it, it's supposed to happen after bootloader was locked. So, I agreed to reset, booted into the system, haven't seen the usual bull**** about my phone being forever cursed and rejoiced.

PS. One more thing. If you're going to use Magisk, make sure you've aquired patched by Magisk boot.img from your ROM and flashed it before relocking the bootloader.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
If ROM is installed with gapps, locking of bootloader supported in official lineage?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
Lineage is OTA updates on redmi note 4 works fine without need to flash gapps.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] keniff:
Is mic gain ok with whatsapp call? As it's very low with los official.. Should i move to this built?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
You can try this custom kernel from lineage official X00TD maintainer https://www.pling.com/p/1381603/
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
I don't know. I don't want to install this crap just to test it, sorry.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
That's interesting. I couldn't relock the bootloader on rajesh's build. I tried the build from 20.05. Flashed it with the official recovery. It works fine but when I try to relock the bootloader, the phone goes into 'red state'. Did somebody successfully relock the bootloader with any of custom builds from rajesh? May be I made a mistake somewhere, I'm not sure.

PS. In the official userdebug build in 'Developer options' there is an option called 'OEM unlocking'. You need to enable it if you want to flash custom boot image or whatever else, but I didn't find such an option in rajesh's build. So I guess something is missing.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Locking bootloader support not yet added. It will be added in upcoming build.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
It looks like the official build doesn't have the problem with infinite charging. Both on lock screen and in Battery settings there is an indication that the battery is fully charged ('Charged' on lock screen and 'Full' in battery settings).
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Build : lineage-18.1-20210523-X00TD-user-signed.zip

* AVB disabled and Verity Enabled.

* Locking bootloader supported. Works only with lineage recovery.

* 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.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Vedice:
Please help anyone, after flashing this rom i can't boot and can't go to twrp either, itu just stuck on the logo :(

How to fix this??
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
How this happened. Did you try dirty flash or clean flash. Which twrp did you use?

Try to flash lineage recovery in fastboot mode.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
do you have any repo with your changes?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
I can confirm that on the user build from 25.05 bootloader can be successfully relocked. Good job,

rajesh@xda.​
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
Any news about question above ?

Just to make sure i would like to have some clarifications, hoping you can help me.

Relocking bootloader scenario.

May gapps be a problem during relocking steps or do i permanently need to run a vanilla build ?

Once relocked, if an ota will come, could gapps be an obstacle for a hassle-free upgrading ?

Thank you in advance.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
Instead of relying on somebody else you could test it yourself and tell us about the results.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
I guess it must work on lineage because pixel experience ROM already locked bootloader using gapps even though gapps carries google signature. To make it work you must install ROM and gapps first by clean flash. Format data.. reboot to fastboot and flash lineage recovery and lock bootloader. If locking fails it boots to signed recovery by default. So that you can again format userdata to boot ROM in locked bootloader conditions. You should not lock bootloader if you are using twrp recovery. If anything goes wrong you may get red alert in boot screen but it can be easily solved by unlocking bootloader through fastboot.

To pass safetynet and preserve userdata locking bootloader is essential thing. Hereafter even it is custom ROM safetynet requirements are made strict on each android version. OTA can be applied on locked bootloader through lineage recovery.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
I successfully relocked the bootloader using official lineage 18.1 build.

These were the steps.

Booted twrp 3.5.2_9.

Wiped all partitions and formatted data ( clean flash ).

Rebooted twrp ( no need to do it, but this is my personal way lol ).

Flashed rom and gapps, open ones, nano package.

Rebooted twrp.

Flashed in recovery partition lineage recovery, last build available.

Rebooted to bootloader directly from twrp reboot menu.

Made recognize successfully my device by fastboot through ' fastboot devices ' command.

Run ' fastboot flashing lock ' and ' fastboot flashing lock_critical ' commands successfully.

Booted the system typing ' fastboot reboot ' command.

Lineage rom booted without any issues.

Checked updates and found them.

Checked bootloader status through fastboot command ' fastboot oem device-info ' and it returned to me the proof my bootloader is locked.

But...

We arrived at the ' but ' section lol.

I checked in play store settings my device certification, my device was still no certified.

As evidence of this fact i run safety net test app, cts check failed, as guessed.

I also cleared google play services and play store caches and datas then rebooted system but nothing changed.

Still not certified.

So, i' m thinking, which benefits did i get relocking the bootloader ?

Yeah, i don' t have that annoying alert message at boot anymore...

And i got a basic recovery now lol.

And think that I did all this to avoid magisk flash lol.

With an easy module i could get what i needed.

Don' t know...I really don' t know whether it' s worth it or not lol.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
If locking bootloader with gapps supported on official lineage then same works in this ROM project. I will fix safetynet issue on next OTA update.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
For safetynet fix and it may be gapps issue.

1. After locking bootloader and successfully booted ROM Enable developer option. Look for bootloader lock option and disable it. Clear playstore data and restart. It may fix safetynet issue. If you think to unlock bootloader again you need to enable bootloader unlock option in developer settings. If it is disabled state you cannot unlock bootloader even in fastboot.

2. If opengapps fails safetynet then try Nikgapps.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
1. Already enabled developer options after relocking the bootloader and checked for unlock bootloader option.

As if we were on stock rom, we have the opportunity to tap it on/off , hopefully it s not blanked.

As reported in my previous message,I already tried to clear google play services and play store caches and data then rebooted rom.

Then i checked again for play store device certification, but no luck.

What would it be the way out if unlock option in developer option was blanked ?

You wrote about an unfriendly scenario, if blanked we couldn 't unlock device even in fastboot...

Do you maybe know if we have the opportunity to enter in edl mode via fastboot ?

2. Even if i flashed lineage recovery i' m not so familiar with it, especially its features.

Could you kindly enlighten me about its factory reset option ?

We have in order format data/factory reset, format cache partition and format system partition.

Well, is the first one equivalent to twrp clean flash ? ( all partitons wipe and format data )

No problem about second option, format cache.

About the third option, format system partition, if used, will system and gapps be wiped for good ?

I mean, i know how to delete gapps using twrp, but i'm in little trouble on aosp recovery lol.

Thank you.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
To be secure and limited option use aosp recovery. If you want to compromise on your data and need more features on recovery use twrp. If twrp is installed as default recovery, For example it is possible to unlock your device even if you use password or pin protection in ROM.

TWRP is versatile option to install ROMs ,gapps and MOD zips but it is not secure as AOSP recovery.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] olzge:
Which recovery would you recommend if I wanted to lock bootloader again AND encrypt the phone? Would OrangeFox allow for both of these two things?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Dont lock bootloader if twrp is flashed as recovery. Use twrp to install ROMs. If ROM is found to be stable and can be used as daily driver then you can flash ROM's signed recovery to lock bootloader and encrypt your data .
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] dfantonio:
Hello guys.

The last OTA (20210525) broke my phone. After creating a backup yesterday and starting the update, the phone is now stuck at a recovery screen where it says "Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"

Is there a way the fix this issue without losing my data?

Perhaps I can apply the backup I did yesterday, but I can't find it anywhere on recovery.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sl0407:
下載自定義恢復-您可以下載Lineage Recovery。只需下載最新的恢復文件，其名稱類似於lineage-18.1-20210526-recovery-X00TD.img。

可以成功OTA

我的英語不好，對不起
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] olzge:
Is "ROM's signed recovery" referring to Lineage Recovery? And this should work with the ROM-.zip I download from the LineageOS site?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
I just unlocked bootloader again and flashed my beloved twrp lol.

Even if i' m used to stay for a long, long time on a single rom, i like to know i' ve a device open to the modding world.

Only twrp actually runs at the moment lol.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] dfantonio:
I've flashed the the newest build (20210525), but nothing happened and I'm still stuck at the recovery. Do you have any other idea? Or perhaps a guide on how to restore the backup I made yesterday
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
Dev was very clear in his post announcing newer build, 20210523.

No ota or dirty updates were allowed.

Only clean flash.

Anyway, try to recover your files this way.

Boot twrp.

Connect your device to a pc.

Go in mount section and enable mtp.

Your pc should be now able to see your device.

Transfer your files.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
Even after 0528 OTA update safety net test is failing?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] ThinkingTwice:
Thank you so much @rajesh@xda, I never actually thought about checking the ROM fingerprint, but it makes so much sense! (As you can tell I am still a bit of a noob ahaha).
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] srepole:
Which benefits did you get using firmware 438 as base ?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
This happens due to safetynet checks unlocked bootloader in default.prop "ro.oem_unlock_supported=1" Check oem unlock switch in developer settings.

By adding locking bootloader support, safetynet fails by default. One possible solution is to flash ROM and Gapps through twrp and flash lineage recovery through fastboot and lock bootloader.

After booting ROM in locked bootloader conditions go to developer setting and disable oem unlock option and reboot.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
Does that mean that I will have to use lineage recovery instead twrp and keep bootloader locked ?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Wait for next update. I try to fix this issue on unlocked bootloader.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
Yes please, thanks in advance...
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Check on build 20210604
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] sunchar:
thanks, safetynet is now passing
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] heyadmwutanime:
Which should I choose LineageOS 17.1 or 18.1? Which is more stable and won't corrupt after OTA update?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] jostrapa:
Hi guys, how are you? I had problems with my cell phone recently and it was turned off for a few days until it fixed. Once fixed I realized that when connecting corrupted the system (it was on the official android 10). I installed the official Lineage OS 18.1, system very fast and stable, but the mobile network is not working. Is there any way to install the separate modem to fix the problem, or do I need to return to stock to fix it?

Thanks for any help!
[Xiaomi Mi 10 Ultra ROMs, Kernels, Recoveries, & Ot] Xayah:
Evolution X 5.9 for the Xiaomi Mi 10 Ultra [cas]

/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/

Living, Breaking, Keep Evolving.

Pixel UI, customization and more, we are Evolution X!

- Team Evolution X -

@joeyhuab

@peaktogoo (Now RealAkito)

Reach us on Twitter! @EvolutionXROM

What are our features?

- Just flash and check "The Evolver"

You tell me

DO NOT FLASH GAPPS, ALREADY INCLUDED

First Time Install / Clean Flash

1. Reboot to Recovery

2. Download the proper ZIP for your device

3. Wipe Data/Cache/System when coming from non-AOSP ROMs

4 Flash the latest firmware for your device variant

5. Flash the ROM

6. Reboot to System and #KeepEvolving

Update / Dirty Flash

1. Reboot to Recovery

2. Download the proper ZIP for your device

3. Flash the ROM

4. Reboot to System and #KeepEvolving

Light Screenshots / Dark Screenshots / Download

Donate to me! / Official Chat / Device Support

​

Android OS version: 11.0.0_r39

Security patch level: Aug 5, 2021

Build author: Xayah

Kernel: Kernel

Device Tree: Cas Common

Device Vendor: Vendor

Source code: Evolution-X

ROM Developer: Xayah

---------------------------------------------------------------------------------------------------

Really thanks ChaptSand and Ramisky, they helped me a lot.
[Xiaomi Mi 10 Ultra ROMs, Kernels, Recoveries, & Ot] Pineappleman3001:
Really great so far, no issues, thanks!
[Xiaomi Mi 10 Ultra ROMs, Kernels, Recoveries, & Ot] vtec303:
is your 4g and /or 5g working on this rom? cheers
[Xiaomi Mi 10 Ultra ROMs, Kernels, Recoveries, & Ot] Pineappleman3001:
Working 👍
[Xiaomi Mi 10 Ultra ROMs, Kernels, Recoveries, & Ot] vtec303:
that's great, what country are you in? I am in UK, cheers