[RECOVERY][X00T] KudProject's Unofficial TWRP 3.4.0-0 [16-06-2020]

Search This thread

Vvk380

Senior Member
Nov 22, 2016
239
43
Asus ZenFone Max Pro M1
@krasCGQ i tried ur twrp 3.4 from telegram and it has one bug
system partition is always mounted,cant unmount it manually also... Attaching SS
 

Attachments

  • Screenshot_2020-06-20-19-58-18.png
    Screenshot_2020-06-20-19-58-18.png
    61.7 KB · Views: 336
  • Like
Reactions: mzs114

merslei

Member
Aug 9, 2019
18
1
I'll just answer this since second one is already answered: yes (for TWRP side), since I'm using stock Asus import with it.

Sent from my MI 9 SE using XDA Labs

First of all thank you for your hard work! We appreciate it so much ? Can I ask why we pro m1 owners don't have official twrp? And what do you think is the problem when I try to flash custom rom I always get error when I followed their instructions such as wiping everything and ended up with no OS installed. I got error 7 and 11 on two different roms. But when coming from stock rom then install custom rom it went successfully though I suffered a lot of bugs. Currently figuring out the right way to clean install. My last time messing with custom rom was 3 years ago and had experince for 8 years. Messing with recovery is very different than before. PS. I was on 058 stock then tried to install pie custom rom. Was using 3.4.0 provided by user a week ago in havoc thread. Not sure if it's the same as yours. Is it safe?
 
Last edited:

krasCGQ

Recognized Contributor
Apr 13, 2015
5,433
4,937
20
Kendari
kud.my.id
First of all thank you for your hard work! We appreciate it so much ? Can I ask why we pro m1 owners don't have official twrp? And what do you think is the problem when I try to flash custom rom I always get error when I followed their instructions such as wiping everything and ended up with no OS installed. I got error 7 and 11 on two different roms. But when coming from stock rom then install custom rom it went successfully though I suffered a lot of bugs. Currently figuring out the right way to clean install. My last time messing with custom rom was 3 years ago and had experince for 8 years. Messing with recovery is very different than before. PS. I was on 058 stock then tried to install pie custom rom. Was using 3.4.0 provided by user a week ago in havoc thread. Not sure if it's the same as yours. Is it safe?
Adding a detached GPG signature together with releases is my latest attempt to ensure that it's easy to detect tampered packages, since it'll be verified against one of my GPG public keys.

Anything downloaded from my sources from now on will always pass such verification, unless you don't have my keys imported :p

About flashing, if you're moving between ROMs, always do a wipe of system and vendor before proceeding. Also, make sure package you're flashing isn't corrupted...

so when can we expect Xenon and Lineage :p .. lol
welcome back bro :)
I can't promise anything; screen and digitizer start to break :(

Sent from my MI 9 SE using XDA Labs
 
Last edited:

Jaggerjacquez

Senior Member
Sep 30, 2017
461
50
First of all thank you for your hard work! We appreciate it so much ? Can I ask why we pro m1 owners don't have official twrp? And what do you think is the problem when I try to flash custom rom I always get error when I followed their instructions such as wiping everything and ended up with no OS installed. I got error 7 and 11 on two different roms. But when coming from stock rom then install custom rom it went successfully though I suffered a lot of bugs. Currently figuring out the right way to clean install. My last time messing with custom rom was 3 years ago and had experince for 8 years. Messing with recovery is very different than before. PS. I was on 058 stock then tried to install pie custom rom. Was using 3.4.0 provided by user a week ago in havoc thread. Not sure if it's the same as yours. Is it safe?
Funny, isn't it? Zenfone Max M1 and Max Pro M2 got Official release of TWRP while Pro M1 didn't!!!!!!!!!!!! And someone would wonder WHY. Hmm. :rolleyes:
 

merslei

Member
Aug 9, 2019
18
1
Adding a detached GPG signature together with releases is my latest attempt to ensure that it's easy to detect tampered packages, since it'll be verified against one of my GPG public keys.

I have to reflash then just to be on the safe side. Can you give steps on how to verify your keys on your second post? I don't really know how to do it. I'm in windows 10. Also, are your twrp project open source?

About flashing, if you're moving between ROMs, always do a wipe of system and vendor before proceeding.
Strangely nothing good happening to me when I followed their instructions. So i do it the traditional way. From stock Oreo working my way up to Pie.

I have question I hope you don't mind helping. Let's say I was in 058 and had flashed RR pie. I want to switch to LR. Do I just wipe system and vendor? No need to factory reset, then flash the new rom? From what i understand some roms require you to be in stock? Is there a way to flash stock PIE directly from PIE custom rom? My traditional way took more than an hour to finish all the process. I was hoping like in Jellybean I can jump directly to Lollipop. Is it possible for Pie? Or do we have fastboot pie stock?

---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------

Funny, isn't it? Zenfone Max M1 and Max Pro M2 got Official release of TWRP while Pro M1 didn't!!!!!!!!!!!! And someone would wonder WHY. Hmm. :rolleyes:

Yeah. First thing I did was to search but nothing can be found. Strange that M1 seems to have more development than M2. I was debating whether to buy that or this one.
 

krasCGQ

Recognized Contributor
Apr 13, 2015
5,433
4,937
20
Kendari
kud.my.id
I have to reflash then just to be on the safe side. Can you give steps on how to verify your keys on your second post? I don't really know how to do it. I'm in windows 10. Also, are your twrp project open source?
1. For Windows, I can't. But for Linux users, it's on 3rd post.
2. Everything is published on GitHub organization.

Strangely nothing good happening to me when I followed their instructions. So i do it the traditional way. From stock Oreo working my way up to Pie.

I have question I hope you don't mind helping. Let's say I was in 058 and had flashed RR pie. I want to switch to LR. Do I just wipe system and vendor? No need to factory reset, then flash the new rom? From what i understand some roms require you to be in stock? Is there a way to flash stock PIE directly from PIE custom rom? My traditional way took more than an hour to finish all the process. I was hoping like in Jellybean I can jump directly to Lollipop. Is it possible for Pie? Or do we have fastboot pie stock?
Common sense: clean flash required, which involves resetting the device.

And you can just skip going to stock before flashing custom ROMs, which I did on X00T; just remember proper firmware combination. However, I once in a while, on other devices, reflashed stock firmware just to have a very clean system before reflashing custom ROMs.

Sent from my MI 9 SE using XDA Labs
 
Last edited:

Swamoy

Senior Member
Jan 27, 2019
1,414
1,314
Kolkata
Sir if you don't mind, I have one request.. You have 3.18 based common kernel, 4.9 based common kernel but you have stopped 4.4 based common kernel development..

For land (Redmi 3S), I always merge your 3.18 (now 4.9) common kernel source blindly bcz I know It'll work.. But now with X00T, I can't find your 4.4 based active common kernel source.. I really love your common kernel development..

Sir if possible plz start your 4.4 common development again.. It will be very helpful for new developers like me..

Thanks a lot sir.. Lots of love.. ❤️❤️❤️
 
Last edited:

merslei

Member
Aug 9, 2019
18
1
Common sense: clean flash required, which involves resetting the device.
Sent from my MI 9 SE using XDA Labs
That's what I did format and wipe everything, but why when I used your 3.4.1.0 I got error failed to unmount /system device or resource is busy when trying to wipe system and vendor or flash magisk, how to fix this? I tried to use your 3.3.1.0 I can mount unmount system but then met with 0mb storage, there's nothing inside folders. only root folders without files. Can you please advise me what to do. When I used the one provided by other user it worked flawlessly but then the size is different to yours. Nothing works. OTG also doesn't get recognize
This is already me coming from clean flash. I'm afraid I have to setup again from the start.. Had done it at least more than five times because of various bugs....
 
Last edited:

m0han

Senior Member
Apr 30, 2012
4,350
1,535
Changelog twrp-3.4.0-0-KudProject-X00T
  • Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
  • Only allow user to backup system and vendor images
  • set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
....
is there any reason for removing the option to allow partitions to be backed up? any particular benefit to backing up 'images'?
tried this twrp. encountered some 'issues'. not sure if this is affects the sanctity of the backup. hope @krasCGQ would clarify.

Screenshot_2020-06-22-22-44-21.jpg Screenshot_2020-06-22-22-47-00.jpg
 

merslei

Member
Aug 9, 2019
18
1
is there any reason for removing the option to allow partitions to be backed up? any particular benefit to backing up 'images'?
tried this twrp. encountered some 'issues'. not sure if this is affects the sanctity of the backup. hope @krasCGQ would clarify.

View attachment 5046325 View attachment 5046327

I'm on Pie, never tried 10 nor plan to try so I believe twrp version in this thread is enough BUT
I don't know why all the versions I've tried from the OP ended up with different errors on each different versions. It's unusable for me. One thing I love about OP's twrp is it is very secure it asks for passcode before proceeding to recovery but unusable. Reverted to the one you provided but I'm not sure who made that but it is working flawlessly albeit won't let me install custom rom directly. I'm just concerned about security issue. Is it signed or what? Also anyone can access it. It lacks security feature.. this is cons of not having official twrp
 
Last edited:

krasCGQ

Recognized Contributor
Apr 13, 2015
5,433
4,937
20
Kendari
kud.my.id
Sir if you don't mind, I have one request.. You have 3.18 based common kernel, 4.9 based common kernel but you have stopped 4.4 based common kernel development..

For land (Redmi 3S), I always merge your 3.18 (now 4.9) common kernel source blindly bcz I know It'll work.. But now with X00T, I can't find your 4.4 based active common kernel source.. I really love your common kernel development..

Sir if possible plz start your 4.4 common development again.. It will be very helpful for new developers like me..

Thanks a lot sir.. Lots of love.. ❤️❤️❤️
Depends ™

is there any reason for removing the option to allow partitions to be backed up? any particular benefit to backing up 'images'?
tried this twrp. encountered some 'issues'. not sure if this is affects the sanctity of the backup. hope @krasCGQ would clarify.
1. I might add option to backup persist image if it's ever necessary.
2. asusfw partition is pretty much meaningless for us since it contains only regulatory information which will be shown on stock depending your device region.

I always see option to "clone" entire image as a better choice than creating a compressed archive of whole content of partition. Providing option to only backup images of both partitions sure will decrease likelihood of people trying to backup both system and system image, resulting in wasted space.

I'm on Pie, never tried 10 nor plan to try so I believe twrp version in this thread is enough BUT
I don't know why all the versions I've tried from the OP ended up with different errors on each different versions. It's unusable for me. One thing I love about OP's twrp is it is very secure it asks for passcode before proceeding to recovery but unusable. Reverted to the one you provided but I'm not sure who made that but it is working flawlessly albeit won't let me install custom rom directly. I'm just concerned about security issue. Is it signed or what? Also anyone can access it. It lacks security feature.. this is cons of not having official twrp
By installing TWRP itself, you're already opening yourself into having your data stolen by whoever steals your phone, unless you encrypt it with non-default password...

Official and unofficial are just tags, depend on whoever maintains it.

Sent from my MI 9 SE using XDA Labs
 
  • Like
Reactions: Swamoy

Tianhe

Senior Member
Mar 16, 2011
659
152
1. I might add option to backup persist image if it's ever necessary.

I always see option to "clone" entire image as a better choice than creating a compressed archive of whole content of partition. Providing option to only backup images of both partitions sure will decrease likelihood of people trying to backup both system and system image, resulting in wasted space.

Persist backup is desirable IMO, helps if ever there is the problem of lost MAC, IMEI, Wifi broken etc. while flashing stuff.

Sometimes a device restores only either one - System or System image and bootloops if the other one is used. Trust me, I have faced this issue on A/B devices. Better to create a full TWRP backup and restore partition-wise ( I can always copy the TWRP backup to external HDD to free phone memory)
 

Jaggerjacquez

Senior Member
Sep 30, 2017
461
50
Persist backup is desirable IMO, helps if ever there is the problem of lost MAC, IMEI, Wifi broken etc. while flashing stuff.

Sometimes a device restores only either one - System or System image and bootloops if the other one is used. Trust me, I have faced this issue on A/B devices. Better to create a full TWRP backup and restore partition-wise ( I can always copy the TWRP backup to external HDD to free phone memory)
True indeed
 

Xda user 101

Member
Jun 8, 2019
19
3
I have a request can you please roll the next update with lockscreen on twrp I know that it wont completely secure my phone as it will still be hack able by usb port but If someone tries to delete the data from twrp it is easy for them. So maybe a lock screen is good idea. Plus if we forget the password we can flash the twrp again and wont lose any date except twrp setting.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 61
    https%3A%2F%2Fimg.xda-cdn.com%2FpSvihPyfhapF9LoHqaNVoQ9y7kw%3D%2Fhttp%253A%252F%252Flh3.googleusercontent.com%252F2HtVAF5zfNMlmKhF0QYqCSr1rsstB1btNfdKl7WvGTcZkOSKCYNxdXwsSizx9VhiPg%253Dw300


    [SIZE=+1]This is basically a tl;dr thread.
    I don't want to make a thread that everyone will lazy to read.
    [/SIZE]​

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    [SIZE=+1]Disclaimer[/SIZE]​
    Code:
    /*
     * 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.
     */

    [SIZE=+1]Requirements[/SIZE]​
    • 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.

    [SIZE=+1]Flashing Instructions[/SIZE]​
    I assume you've done (very) basic steps on preparing to flash your device.
    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-y-KudProject-X00T.img
      Where x and y are version of TWRP you're going to flash.
    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.

    [SIZE=+1]Downloads[/SIZE]
    Webserver | MEGA
    Old releases only: OSDN | AndroidFileHost

    [SIZE=+1]Known Issues[/SIZE]​
    • 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.

    [SIZE=+1]Special Thanks[/SIZE]​
    • 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.

    [SIZE=+1]Device Sources[/SIZE]​

    XDA:DevDB Information
    Unofficial TWRP 3.x (X00T), Tool/Utility for the Asus ZenFone Max Pro M1

    Contributors
    krasCGQ
    Source Code: https://github.com/KudProject/bootable_recovery-twrp


    Version Information
    Status: Stable
    Current Stable Version: 3.4.0-0-KudProject
    Stable Release Date: 2020-06-16
    Current Beta Version: 3.3.0-0-20190513
    Beta Release Date: 2019-05-13

    Created 2019-01-09
    Last Updated 2020-06-28
    24
    [SIZE=+1]Some stuffs...[/SIZE]​
    Another TWRP thread? Why?
    I like to keep discussions about my builds separate. Moreover, the existing TWRP that already available on XDA before doesn't seem to be maintained anymore.

    I flashed via fastboot but it always fails.
    Check or change your cable, use other USB slot (especially 2.0 one if 3.0+ doesn't work), or if needed try to flash recovery with USB connected to a hub.

    [SIZE=+1]Changelogs[/SIZE]​
    twrp-3.4.0-0-KudProject-X00T
    • Merged TWRP source changes up to 11 June 2020 (UTC+8)
    • Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
    • Switched f2fs-tools to latest AOSP master
    • Only allow user to backup system and vendor images
    • set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
    • Updated prebuilt kernel based on S082 source drop
    • F2FS kernel driver updated to 5.3-rc1 with backports up to 5.7-rc1 from 4.9
    • Switched to arter97's fork of exFAT
    • Switched from NTFS kernel driver to FUSE ntfs-3g due to incomplete write support

    twrp-3.3.1-0-X00T-20190526
    • Fixed stock ROM flashing due to missing prop
    • Fixed FDE decryption

    twrp-3.3.1-0-X00T-20190525
    • Updated F2FS on kernel to 5.2-rc1
    • TWRP 3.3.1 + upstream changes

    twrp-3.3.0-0-X00T-20190513
    • Updated base to android-9.0
    • Updated blobs from 16.2017.1903.050
    • Support for flashing unmodified stock firmware (please read notes!)
    • Rebased kernel to S050 source drop
    • Updated F2FS on kernel to 5.1-rc1
    • TWRP 3.3.0 + upstream changes

    twrp-3.2.3-0-X00T-20190217
    • Now based on whyred official TWRP tree
    • Reverted kernel to stock-based as-released (S339) with F2FS upstream and sdFAT included
      (this should fix USB-OTG support while retaining support with latest f2fs-tools)
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20190118
    • Pick more patches from LineageTWRP project
    • Updated f2fs-tools to latest development branch
    • Slight cleanup
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20190115
    • ADB sideload fixed for everyone
    • f2fs-tools v1.12.0
    • Disabled Synaptics' firmware update driver entirely
    • Removed qcacld-3.0 from kernel
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20190108
    • Removed ntfs-3g from recovery
    • Included several extra recovery keys
    • Updated kernel to S338-based
    • Disabled Synaptics' startup firmware update
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20181231
    • Updated platform security patch override to 2018-11-01 (matches 338 firmware)

    twrp-3.2.3-0-X00T-20181226
    • Imported more proprietary blobs from stock 337 firmware
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20181224
    • Allow wiping vendor partition
    • 2nd CPU target set to Cortex-A73
    • Initial import of proprietary blobs from stock 337 firmware
    • Updated kernel to S337-based
    • TWRP upstream changes

    twrp-3.2.3-0-X00T-20181215
    • Removed texfat and tntfs stock modules
    • Enabled DT2W

    twrp-3.2.3-0-X00T-20181214
    • Rebased to shakalaca's tree
    • CPU target set to kryo
    • Updated platform security patch override to 2018-10-01 (matches 337 firmware)
    • Switched to my rebased kernel
    • TWRP upstream changes (android-9.0 branch)

    twrp-3.2.3-0-X00TD-20181024
    15
    [SIZE=+1]Notes[/SIZE]​
    • "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. :(

    [SIZE=+1]Unmodified Stock Firmware Support[/SIZE]​
    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:
    Code:
    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.

    In plain text:
    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.

    [SIZE=+1]Verifying released builds[/SIZE]​
    This was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.

    Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.

    You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.

    To import on Linux:
    Code:
    gpg --import krascgq.gpg

    To verify builds on Linux:
    Code:
    gpg --verify <build-name>.sig <build-name>

    Windows users will need to search for compatible tools.
    13
    A fixed build, that also fixes FDE decryption has been pushed. Enjoy.
    8
    As I've given X00T to my father and due to lack of testing on my further limited-testing builds, I decided to stop all further updates to the recovery.

    I'll still keep this thread open for further discussion of my and Alex builds.

    Sorry if this sounds disappointing but I've no further choice.

    Sent from my MI 9 SE using XDA Labs
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone