Thanks dude for your respons
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
Do i have to install decrypt.zip?
OMNI now has R47. Pls update this project.
Sent from my ZenFone Max Pro M1 using XDA Labs
"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.
Unmodified Stock Firmware Support
With introduction of unmodified stock firmware support, I need to clear up some confusions you've if any. Notes below are copy-pasta from my post elsewhere:
In plain text:
The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
You need to be on stock before booting the recovery for the first time, then afterwards you can flash any stock firmware.
If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs.
How to set password on this twrp?
Password in Recovery is not a good idea, it will be deleted after reflash recovery.
The most secure way is ENCRYPT your data partition, enable secure startup to active encryption password or if you don't enable secure startup, the password will always "default_password" and anyone can unlock your data using that password.
To decrypt correctly:
Make sure you have same or newer security patch recovery (Eg: Ur rom is r43, you can use r43 or r47 recovery. Ur rom is r47 you must use r47 or newer. If you use 10.0 r2 SAR, you must use 10.0 r2 SAR or newer 10.0 SAR recovery.)
Go to recovery, it will automatic ask for password or pattern to decrypt.
If ur password is text or PIN and it ask for pattern, cancel, go to terminal, type "twrp decrypt <YourPasswordOrPIN>".
All hackers will not be able to read anything in your Data partition, they must format Data partition to unlock it. But FORMAT = ALL GONE!!!
Loss > Stolen
Additional: That's why secure startup is not needed if you didn't unlock your bootloader because all data will be format after you unlock it, "default_password" can't be used because stock recovery doesn't support decrypt and you can't install any custom recovery with a locked bootloader.
Encrypt is the best way to protect your data.
Unlocking bootloader is not dangerous like everything you read on the internet if you already encrypted your data and active it correctly.
Latest recovery: https://androidfilehost.com/?fid=1899786940962609436
Format Data & System and then reinstall, encrypt.Thanks for your such detailed post, It really healped me to chose the best way to protect data. I need one more help I actually used havoc os and encrypted my data but now I want to clean instrall the os again because there are some issue in the os which can be shorted by reinstralling it only. But I am not able to delete the system from twrp because it is not able to access it due to encryption. The only way I know to remove encryption is by resetting phone and disabling encryption from setting. But that way is not working because when I press reset from the setting it bring me to recovery. There I get a new option in mount to decrypt I am not sure if thats the decrypt option i want to use. When I tap it says enter password but i never set one so i press cancel and nothing happens. I think there may be other ways to do what I want but sadly I am a noob so would need a little advice/help. Thanks in advance for help
/* * 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. */
fastboot flash recovery twrp-3.x.x_9-<kernel>-y-KudProject-X00T.img
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.
gpg --import krascgq.gpg
gpg --verify <build-name>.sig <build-name>