new mbtwrp_xxx_umi. / twrp-3.4.2b-1206 / 1208 from wzsx150


sxHeavy

Members
Sep 11, 2018
122
40
I tried this about a month ago with 1206 and it did NOT work. It would not decrypt anything but would provide access to the encrypted directories and the like but there was no possibility of installing anything or making modifications (updating as an example). Mi 10 Youth Edition. Weekly update beta software, so it would crash all the time. I switched to the Stable branch and the phone only resets when I do an update (one per month or so). I simply deactivate the screen lock before updating and it works perfectly.
Thanks for feedback it may work only on MI 10 umi (I confirmed I even installed the latest weekly update by this process).
May other people confirm?

Edit :i confirm I did this today to flash latest weekly update and it works! Enter pin then validate then cancel
 
Last edited:

MAMAC

Members
Jan 24, 2017
156
40
Is this a new recovery?

Gesendet von meinem Mi 10 mit Tapatalk
Latest one is here

 
  • Like
Reactions: kral84

kral84

Members
Aug 28, 2020
83
20
But in the notes:

NOTES:
To use decryption on 12.2.5 and 12.2.4 vendor you need to fastboot boot everytimes you need.


not really.good...
 

B!GBOY

Members
Dec 27, 2010
129
40
Idk i didnt watch his thread. This is the last version released 24h ago.
It is the same file please stop posting the same comment again and again. we get that you want to "promote" your thread.

I am confirming for everyone else who read this thread that the files infact have the same checksum:
90381326bae874f405e264baff6ba12a MBTWRP_12.2.5_CMI.img
90381326bae874f405e264baff6ba12a TWRP_CMI.img

The post I mentioned linked the original post from the developer that cares to specify the twrp version and device names instead of just a generic zip named "TWRP" which would lead to people flashing wrong twrp on their devices

But in the notes:
NOTES:
To use decryption on 12.2.5 and 12.2.4 vendor you need to fastboot boot everytimes you need.
not really.good...
I don't know about mi 10 but the mi 10 pro's version looks to be working fine as far as decryption goes.

Also it takes a long time to boot into twrp, like a minute or so
 
Last edited:

Iain_B

Members
Mar 25, 2013
1,054
222
There still seems to be some confusion about TWRP for Mi 10 (umi).
There is still a problem with TWRP and decryption with recent ROMs. You cannot flash a TWRP that decrypts your data into the Recovery partition.
There is also some confusion because there are now two versions of 3.4.2b-1206. There is the version that is installed with the weekly ROMs - this does not decrypt. There is also another version which decrypts, but should never be flashed. I therefore now have gone back to using TWRP 3.4.2b-0623 to avoid any confusion.

The TWRP 3.4.2b-1206 that is installed with the weekly ROM does not decrypt, so installation of the weekly ROM can be via USB-OTG. There is no need to flash any other version of TWRP. This can permanently stay in the recovery partition.

If you wish to use a TWRP that decrypts, you must only boot into this - not flash - through Fastboot. This is temporary and does not stay in memory. For this I use TWRP 3.4.2b-0623. This must only be booted into, using the Fastboot command:
fastboot boot TWRP_umi.img
This decrypts your data and gives access to all of the basic TWRP functions. It takes about 70 seconds to load up. You have to sign in with a pattern, not password. And you have to click a few mms beneath the target.

If you accidentally flash the above ROM, you will get into a fastboot loop.
To get out of this, you can use TWRP 3.4.0 (LittleTurtle2333) - from GitHub with the Fastboot command:
fastboot flash recovery umi-3.4.0-11.0-1110.img
This puts this TWRP into the recovery partition - this is permanent, until replaced.
 
  • Love
Reactions: sxHeavy

MAMAC

Members
Jan 24, 2017
156
40
It is the same file please stop posting the same comment again and again. we get that you want to "promote" your thread.

I am confirming for everyone else who read this thread that the files infact have the same checksum:
90381326bae874f405e264baff6ba12a MBTWRP_12.2.5_CMI.img
90381326bae874f405e264baff6ba12a TWRP_CMI.img

The post I mentioned linked the original post from the developer that cares to specify the twrp version and device names instead of just a generic zip named "TWRP" which would lead to people flashing wrong twrp on their devices



I don't know about mi 10 but the mi 10 pro's version looks to be working fine as far as decryption goes.

Also it takes a long time to boot into twrp, like a minute or so
Sorry u are here??? Oh some admin? Or.... Also my thread is older than this one here or whatever and i did update twrp regulary in my thread, so thats my right to do and who are u here to decide what i can or canot???
 
  • Like
Reactions: katerpanne

B!GBOY

Members
Dec 27, 2010
129
40
There still seems to be some confusion about TWRP for Mi 10 (umi).
There is still a problem with TWRP and decryption with recent ROMs. You cannot flash a TWRP that decrypts your data into the Recovery partition.
There is also some confusion because there are now two versions of 3.4.2b-1206. There is the version that is installed with the weekly ROMs - this does not decrypt. There is also another version which decrypts, but should never be flashed. I therefore now have gone back to using TWRP 3.4.2b-0623 to avoid any confusion.

The TWRP 3.4.2b-1206 that is installed with the weekly ROM does not decrypt, so installation of the weekly ROM can be via USB-OTG. There is no need to flash any other version of TWRP. This can permanently stay in the recovery partition.

If you wish to use a TWRP that decrypts, you must only boot into this - not flash - through Fastboot. This is temporary and does not stay in memory. For this I use TWRP 3.4.2b-0623. This must only be booted into, using the Fastboot command:
fastboot boot TWRP_umi.img
This decrypts your data and gives access to all of the basic TWRP functions. It takes about 70 seconds to load up. You have to sign in with a pattern, not password. And you have to click a few mms beneath the target.

If you accidentally flash the above ROM, you will get into a fastboot loop.
To get out of this, you can use TWRP 3.4.0 (LittleTurtle2333) - from GitHub with the Fastboot command:
fastboot flash recovery umi-3.4.0-11.0-1110.img
This puts this TWRP into the recovery partition - this is permanent, until replaced.
That must be specific to UMI, I do not experience that with CMI. Did you try the 3.5.0 TWRP? does it have the same problem when flashed as 3.4.2b?
 

Iain_B

Members
Mar 25, 2013
1,054
222
That must be specific to UMI, I do not experience that with CMI. Did you try the 3.5.0 TWRP? does it have the same problem when flashed as 3.4.2b?
It is, unfortunately, specific to Mi 10 - umi. There were initially issues with cmi and lmi, and it then developed with only umi and encryption. If it is dealt with as mentioned above, and TWRP only booted into, it is very manageable.
3.5.0 for umi? No, I have not tried it. I'll have a search for it and maybe test it.
 
  • Like
Reactions: B!GBOY

B!GBOY

Members
Dec 27, 2010
129
40
It is, unfortunately, specific to Mi 10 - umi. There were initially issues with cmi and lmi, and it then developed with only umi and encryption. If it is dealt with as mentioned above, and TWRP only booted into, it is very manageable.
3.5.0 for umi? No, I have not tried it. I'll have a search for it and maybe test it.
it's the recovery posted earlier (#102) named MBTWRP and solved the encryption problem when using pin code for CMI.
 
  • Like
Reactions: Iain_B

Iain_B

Members
Mar 25, 2013
1,054
222
Thanks for the pointer. I shall do a full backup and test it out.
This is from just booting into it:
It stays a long time on the first page, rather than with other versions, nothing loads to start with.
It decrypts from pattern;
Clicking (finger) is actually on the position, rather than a few mms below;
Advanced wipe: I nearly wiped my data because the cache checkbox is in a different location;
It seemed to get confused with the 3.4.2b-1206 (ROM version) when rebooting back into recovery. It went into 1206, holding the decryption patter, and so was already decrypted. But it also seems to loop because the USB connection with PC keeps making and breaking (repeating the connection sound);
It seems to reboot OK into System;
Going into Recovery from System seems to have held the decryption from before. But there is still the make / break loop with the USB connection;

I flashed it into recovery, and fastboot rebooted into it and from here it seemed quite stable. I moved around through System, Fastboot and Recovery, and it seemed quite stable here as well.

So the awkward bit is with the 3.4.2b-1206 that is with the ROMs.

I then re-installed the ROM and Magisk. Cleared Dalvik & cache, and deleted the data/system/package_cache folder. I rebooted to system and finished up in 1206 recovery. Rebooted to system again, and again finished in Recovery. So I'm stuck in a recovery loop.

I'm therefore flashing 3.4.0 (LittleTurtle), and booting into 3.4.2b-0623, and again re-installing the ROM and Magisk.

It's not working, so I'm trying to restore. Once I get back, I shall not be using this! :(
 

Iain_B

Members
Mar 25, 2013
1,054
222
So with the Mi 10 (umi) version, there appears to be a conflict with the TWRP 1206 that comes with the weekly ROM, which is not good. There were mounting errors when trying the TWRP restore, which has never happened before. There were errors when trying to go back to stock ROM.

If people start using the Mi 10 (umi) version that I tried, and get into problems, it is going to be very difficult to help them to sort it out. So I hope that no-one will start to use it!
 

kral84

Members
Aug 28, 2020
83
20
Jupp latest weekly after flash twrp from @Superwitschi working !!!! THX men...

//flash via TWRP_umi (working) not with littleturkey version...(not working)


/// Or install latest weekly its included!!
 
Last edited:

Iain_B

Members
Mar 25, 2013
1,054
222
So with the Mi 10 (umi) version, there appears to be a conflict with the TWRP 1206 that comes with the weekly ROM, which is not good. There were mounting errors when trying the TWRP restore, which has never happened before. There were errors when trying to go back to stock ROM.

If people start using the Mi 10 (umi) version that I tried, and get into problems, it is going to be very difficult to help them to sort it out. So I hope that no-one will start to use it!
It seems that I could well have been unlucky this morning when I did all of my testing. I must say that I did push things!
I've just installed the new 21.3.3 ROM, which has the 3.5.0-MB TWRP included, and did a few tests. So far all seems OK.
I've put a fuller report here, under this week's ROM. Hopefully it will continue to be without problems.