[RECOVERY][X00T] KudProject's Unofficial TWRP 3.5.2_9-1 (k4.4/k4.14) [16-05-2021]

/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

• ASUS ZenFone Max Pro (M1) ZB601/2KL (of course)
• Unlocked bootloader, in either ways (official, unofficial)
• Some knowledge on how to deal with your device... and patience.

1. Reboot device to bootloader. If device is powered off, press and hold Power + Volume Up button until ASUS logo with "FASTBOOT MODE" message appears.
2. Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
   
   Code:

   fastboot flash recovery twrp-3.x.x_9-<kernel>-y-KudProject-X00T.img

   Where:
   • x and y are version of TWRP you're going to flash.
   • kernel: k4.4 - stock firmware or custom ROMs with FDE encryption; and k4.14 - FBE for custom ROMs with FBE encryption.
3. IMPORTANT: After flashing, immediately press and hold Power + Volume Down for about 10 seconds button to reboot to recovery.
4. Swipe the option to allow modifications. This way, you'll trip Android Verified Boot (AVB) and it's required to flash no verity zip in order to be able to boot stock ROM.

• k4.4: Due to QTI keymaster's behavior, only specific stock firmware as well as custom ROMs with same platform security patch level that can only be decrypted by TWRP. Applicable versions will be indicated explicitly in the changelog.
• k4.14: Recovery may start with very low vibration level. You can adjust vibration intensity in settings later.
• k4.14: Recovery can only decrypt userdata partition encrypted using AES-256-XTS algorithm. Only ROMs using Qualcomm's Inline Crypto Engine (ICE) with 4.14 kernel may also be decrypted by the recovery as well. This can be assumed an intended behavior since implementation of fscrypt_ice on msm-4.14 and msm-4.19 kernels are completely different. Tell ROM maintainers wanting to switch to FBE to use AES-256-XTS instead.

• Dees_Troy and everyone behind TWRP
• shakalaca - base device tree used for older releases
• Ankit Gourav - his work on whyred
• Shivam Kumar Jha - person who kickstarted ZenFone Max Pro (M1) development
• Everyone involved in testing numbers of test builds.

• TWRP repository fork
• Device tree
• Kernel source: k4.4 - k4.14

• Merged TWRP source changes up to 25 April 2021 (UTC+8)
• Builds are now splitted for devices running FDE (targetting stock, running 4.4 kernel) and FBE encryption (targetting custom ROMs, running 4.14 kernel, only works with ROMs using AES-256-XTS encryption)
• FDE: Can decrypt 16.2017.2009.087 stock firmware and any custom ROM with 5 September 2020 security patch
• Restored ability to backup system and vendor partition (images backup for these partitions are recommended)
• Switched to build system libraries from source
• Added persist partition backup support
• Added support for NFC availability check in recovery
• Added support for formatting asusfw partition in GUI
• Updated set_version script to match up Android 10's system-as-root behavior
• FBE: Updated crypto blobs from 17.2017.2012.438 stock firmware

• "fastboot boot" command isn't supported by our bootloader. Don't ever try that. (blame ASUS/Huaqin)
• I'll try to always keep this recovery updated especially when ASUS releases firmware update that also updates AOSP security patch. Security patch set in TWRP needs to match stock firmware used so TWRP can decrypt data partition. This isn't possible with current state as the bump is useless.

Starting this build, recovery supports flashing stock firmware without modifying the updater-script. In order for it to be possible, ro.product.device has to be set to ASUS_X00TD.
This, however, breaks flashing of custom ROMs that check for either X00TD or X00T.
Simply supporting it doesn't mean that you can flash stock firmware directly; you need to be at least on stock when you flash the recovery, so required properties can be exported to /persist which then will be set on every recovery boot up.

Still not sure though, as some ROMs check for ro.product.device and then fallback to ro.build.product for matching devices.

Flashing incremental OTAs are supported but not recommended, since you'll most likely flash verity disabler at the minimum and get the flashing failed upon patching boot.

1. The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
2. You need to be on stock before booting the recovery for the first time, then afterwards you can flash any stock firmware. 21 June 2020 UPDATE: Now not required, as it's now hardcoded in the script itself and since touching persist is never a good idea to begin with.
3. If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs. This also includes TWRP tampering system to prevent stock recovery from overwriting TWRP.

gpg --import krascgq.gpg

gpg --verify <build-name>.sig <build-name>

theraaj said:

size is almost half from official recovery ?

Click to expand...

Click to collapse

Ak-64 said:

First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?

Click to expand...

Click to collapse

vladlp said:

Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is android.hardware.keymaster@3.0-service-qti with "-qti" at the end. Than encrypted data will work. I already test it.

Click to expand...

Click to collapse

gusbalaa said:

Any planning to official sir ?
Sorry if asking.

Click to expand...

Click to collapse

SlamDec said:

sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm

Click to expand...

Click to collapse

krasCGQ said:

I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.

ADB sideload has been fixed on that build, BTW.

Click to expand...

Click to collapse