[EXPERIMENTAL][RECOVERY][3.4.0][umi]Unofficial TWRP for Mi 10 Unified

[simonsmh]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.

#include <std_disclaimer.h>
/*
 *
 * We are 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 ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

Features:
- TWRP boots.
- Decryption is working.
- Vibration
- System, Vendor and Product partitions mount is working but you can't modify them.
- You can flash magisk, miui roms, kernels, firmwares, etc.


Not working:
- Partition formatting (upstream)
- ADB sideload (upstream)


Install guide:
To boot (Reccomended):

fastboot boot <twrp.img>

To install (NOT reccomended):

fastboot flash recovery <twrp.img>

Download:
Now build is checking "ro.boot.hwversion". If it is begined with "1" then use Mi 10 Pro cmi profile, otherwise it will use Mi 10 umi profile.
Please report ro.boot.hwversion if possible. You can get it from getprop command.
Mega Drive Link

Source code:
Device Tree
Recovery Source

Thanks:
@mauronofrio @bigbiff and more open source TWRP devs.

Mi 10 Pro (cmi) thread:
https://forum.xda-developers.com/xi...xperimental-unofficial-twrp-mi-10-10-t4106385

 

[adario73]

USB OTG ?

Hi,
very important for me: is USB OTG working to read ROM from it ?

thank you !

Tested : USB OTG not working.
fastboot reboot recovery.img hangs the phone.
Solved using another twrp for the moment.

 

[simonsmh]

Hi,
very important for me: is USB OTG working to read ROM from it ?

thank you !

It should work but I could not test it for you...

 

[pramyhoga]

Great. Here we start development section.

 

[k1n9n0th1n9]

tested:
can not mount system and vendor.
if you choose : reboot - recovery ( in this TWRP), the device will hang on fastboot.

 

[simonsmh]

tested:
can not mount system and vendor.
if you choose : reboot - recovery ( in this TWRP), the device will hang on fastboot.

Could you fetch a copy of log at /cache/recovery/log.gz for me?
You can only mount them with read only flag. It's super partition's limit.

 

[jayarajan]

Will mi 10 get twrp and other custom roms stuff??

---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------

No custom development till 5 months??!!

 

[simonsmh]

Hi guys, new build (rev. 2) has been uploaded. Tested fastboot flash recovery is working.
The way to fix it is just appending recovery dtbo from official recovery. OTG might still not working. Source code has been updated.
cc @k1n9n0th1n9 @adario73

 

[k1n9n0th1n9]

Hi guys, new build (rev. 2) has been uploaded. Tested fastboot flash recovery is working.
The way to fix it is just appending recovery dtbo from official recovery. OTG might still not working. Source code has been updated.
cc @k1n9n0th1n9 @adario73

can not select partitions system and vendor to mount

 

[simonsmh]

can not select partitions system and vendor to mount

Even with read-only flag? You could only mount system and vendor as read-only.

 

[head_djmusic]

Do not try to Chmod 755 cause phone won't boot! even after ROM installed and rooted, do not do that with any file manager cause will stop the phone from booting!

 

[simonsmh]

Do not try to Chmod 755 cause phone won't boot! even after ROM installed and rooted, do not do that with any file manager cause will stop the phone from booting!

Just don't do that if you are unfamiliar with AVB. You could disable this security feature by reflash vbmeta.img with disable verity and disable verification flag with fastboot. You can find more infomation on Google.

 

[simonsmh]

can not select partitions system and vendor to mount

Hi guys, new build (rev. 3) has been uploaded for fixing mount issue, please test when you have free time.

 

[nocturnoz]

Hi guys, new build (rev. 3) has been uploaded for fixing mount issue, please test when you have free time.

Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.

 

[simonsmh]

Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.

It's pretty weird since I didn't have this issue on my side, could you try it at command line?

mount /dev/block/mapper/system /system_root

Then check the result it printed and see if it mounts under /system_root

I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. Could you have a try?
-----
Could you grab a logcat for me?

adb logcat > logcat.log

 

[k1n9n0th1n9]

Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.

same

 

[nocturnoz]

It's pretty weird since I didn't have this issue on my side, could you try it at command line?

[B]1.: mount /dev/block/mapper/system /system_root[/B]

Then check the result it printed and see if it mounts under /system_root


I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. 2. Could you have a try?

-----
Could you grab a logcat for me?

[B]3. adb logcat > logcat.log[/B]

1.: mount: '/dev/block/mapper/system/system_root' not in fstab
2.: I'm running MIUI.EU 12 20.5.24 (weekly)
3.: ADB Sideload isn't working in TRWP.

 

[simonsmh]

It's pretty weird since I didn't have this issue on my side, could you try it at command line?

Then check the result it printed and see if it mounts under /system_root


I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. 2. Could you have a try?

-----
Could you grab a logcat for me?

1.: mount: '/dev/block/mapper/system/system_root' not in fstab
2.: I'm running MIUI.EU 12 20.5.24 (weekly)
3.: ADB Sideload isn't working in TRWP.

1. There is a space in it.
2. I will have a try with eu at weekends.
3. Since you can decrypt your data, I suggest you put it in your /sdcard instead. I will try to fix sideload soon.

Still it would be very helpful if you could grab a logcat for me.

 

[nocturnoz]

1. There is a space in it.
2. I will have a try with eu at weekends.
3.Since you can decrypt your data, I suggest you put it in your /sdcard instead. I will try to fix sideload soon.

Still it would be very helpful if you could grab a logcat for me.

1. mount /dev... gave an error that -t is required
1a.

mount -t /dev/blck/mapper/system /system_root
mount: '/dev/blck/dm-2' -> '/system_root': Device or resource busy

2. TWRP Backup is possible until vendor backup. Then I'll get Error 255.
3. How do I do that? :/
4. When I'm on my ROM MIUI 12, then I'll connect the phone via USB and launch the ADB logcat commmand? Or where do I have to get the logcat from?

 

[simonsmh]

1. mount /dev... gave an error that -t is required
1a.

mount -t /dev/blck/mapper/system /system_root
mount: '/dev/blck/dm-2' -> '/system_root': Device or resource busy

2. TWRP Backup is possible until vendor backup. Then I'll get Error 255.
3. How do I do that? :/
4. When I'm on my ROM MIUI 12, then I'll connect the phone via USB and launch the ADB logcat commmand? Or where do I have to get the logcat from?

Hi,
I mean logcat of TWRP, you can grab it on TWRP boot. ADB sideload is confirmed not working for now.
Could you try my latest build (rev.4) first? I rebased upstream source to see if it would fix system mounting issue for you.