• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

simonsmh

Senior Member
Dec 14, 2015
297
543
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.
Code:
#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):
Code:
fastboot boot <twrp.img>
To install (NOT reccomended):
Code:
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
 
Last edited:

adario73

Senior Member
Jun 16, 2011
213
41
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.
 
Last edited:

simonsmh

Senior Member
Dec 14, 2015
297
543
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

Member
Dec 29, 2015
39
6
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??!!
 

head_djmusic

Senior Member
Nov 20, 2010
130
47
36
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

Senior Member
Dec 14, 2015
297
543
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.
 

nocturnoz

Senior Member
Feb 12, 2012
142
47
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

Senior Member
Dec 14, 2015
297
543
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?
Code:
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?
Code:
adb logcat > logcat.log
 
Last edited:

nocturnoz

Senior Member
Feb 12, 2012
142
47
It's pretty weird since I didn't have this issue on my side, could you try it at command line?
Code:
[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?
Code:
[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

Senior Member
Dec 14, 2015
297
543
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

Senior Member
Feb 12, 2012
142
47
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.
Code:
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?
 
Last edited:

simonsmh

Senior Member
Dec 14, 2015
297
543
1. mount /dev... gave an error that -t is required
1a.
Code:
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    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.
    Code:
    #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):
    Code:
    fastboot boot <twrp.img>
    To install (NOT reccomended):
    Code:
    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
    3
    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
    2

    ☝☝☝

    This one has helped a lot, thanks. I was about to go mad.

    So basically if you updated to 12.5 you won't be able to flash but boot to twrp3.4.2b (can be dld from above link)

    With this, and only this twrp and method I was able to update to 12.5 21.2.3 without any data loss.
    2
    Any chances for TWRP 3.5?
    2
    Thanks I'll check it. So far I'm just removing lock before flashing. Can't make magisk work with eu Android 11. Is it just me? It installs without errors but after boot shows not installed in magisk manager. 20.4

    please check in this thread my post and @sceryavuz and @mali301262 reply
    https://forum.xda-developers.com/showpost.php?p=83271559&postcount=29
    i'm rolling back to MIUI 11 *sigh* ... i need root and i need the magisk hide otherwise banks app don't start so no choice at the moment

    ---------- Post added at 06:04 PM ---------- Previous post was at 06:01 PM ----------


    i know ... this is the third point of my post (wzsx150 is on LR Team)

    ---------- Post added at 06:16 PM ---------- Previous post was at 06:04 PM ----------

    all true, no need to flash recovery. only use "fastboot boot twrp.img" for installing xiaomi.eu rom.

    i don't think there is a big difference in security terms from installing or temporary executing the recovery ... the recovery is executed only when you start invoking it, and also in a temporary execute, if inside there is somehing malicious, they can patch your installed rom

    .
    do that every update..

    it's a big hassle because you need a PC near you every time