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

[krasCGQ]

(1) does usb otg work - both in recovery and booted rom - with your soon-to-be-released twrp?

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

 

[m0han]

(2)after u restore full backup..dirty flash same rom to resolve boot loop

should try this. will report results.

 

[Vvk380]

@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

 

[krasCGQ]

@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

Weird, it works just fine for me, both on TWRP and via ADB...

 

[krasCGQ]

A year later...
3.4.0-0 is up, since I got back the X00T (even though it's not in prime physical condition anymore).

First 3 posts have been updated, so be sure to re-read everything carefully. Enjoy!

 

[Vvk380]

Weird, it works just fine for me, both on TWRP and via ADB...

Again i tried flashed ur older recovery its fine over it...again flashed 3.4,same issue

 

[merslei]

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?

 

[naitik2012]

since I got back the X00T (even though it's not in prime physical condition anymore).

so when can we expect Xenon and Lineage .. lol
welcome back bro

 

[krasCGQ]

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

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 .. lol
welcome back bro

I can't promise anything; screen and digitizer start to break

Sent from my MI 9 SE using XDA Labs

 

[Jaggerjacquez]

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.

 

[merslei]

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.

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]

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

 

[Swamoy]

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..

 

[merslei]

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....

 

[m0han]

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.

 

[merslei]

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

 

[krasCGQ]

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

 

[Tianhe]

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]

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]

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.