why was recovery part of 9.10.17 package

[Natherul]

I also posted this in the 9.10.17 thread but duplicate it here as Im genuinely curious as to why a recovery was included as it can prove to cause issues as detailed.

dirty installing this broke my install. It seems to be down to the download coming with a recovery install. What happened was that when trying to install the system did not want to boot after install and going back to recovey just caused bootloop. Reinstalling TWRP then did not prompt me with decryption and did not work with command line decrypt either.

Clean installed on top of that and after setting up I went to TWRP to make a backup and noticed that TWRP has been reinstalled again with a new version (noticed due to different TWRP boot logo and language set to chinese by default which my install did not).

Why was TWRP included in this package for MIX3?

hash for the files using windows 10 certutil:
My TWRP file (downloaded from twrp directly 3.3.1.0)
b024bbb9eee17d79b4890572195b0c51636620c5

The recovery in the 9.10.17 package
c5ccd79eb02351c78657404df72aaa7009b5da7a

 

[ingbrzy]

For support encryption for Android 10.. No issue for other users...

 

[alter314]

For support encryption for Android 10.. No issue for other users...

I'm not quite sure of it. I have the same bootloop issue on my mi9t, and if you browse the forum, you find several more threads like this..
I'm coming from 9.8.15, and i tried a dirty flash, but i just get into a bootlop.
I tried every compatible twrp version i could find, and every method i found, but since far (2days of constant trying) i have no luck.
My assumption is, that if i make a clean install with format data, it will work just, fine, but no, i don't want to do everything over again. :/ But im running out of ideas.

 

[LOLO9393]

I'm not quite sure of it. I have the same bootloop issue on my mi9t, and if you browse the forum, you find several more threads like this..
I'm coming from 9.8.15, and i tried a dirty flash, but i just get into a bootlop.
I tried every compatible twrp version i could find, and every method i found, but since far (2days of constant trying) i have no luck.
My assumption is, that if i make a clean install with format data, it will work just, fine, but no, i don't want to do everything over again. :/ But im running out of ideas.

Same boat as your!
I was forced to format data (I knew it before the step to Android 10).
But what is not yet ready is encryption because TWRP3.3.1.2 and Android 9 was perfectly encrypting and none of the available TWRP's are able to encrypt! Russian 3.3.1.4, chinese LR 3.3.1.0916 and greek 3.3.1.910 red latest.
Surely I will not encrypt by settings feature, Because I doubt it well operates.
We must be patient for some times and wait for steady state situation.

 

[MeiGuddet]

As I wrote in the weekly 9.10.17 thread I'm now using chinese TWRP 3.3.1-0916 which came with the ROM. It works fine with de-/encryption of my Mi 9T.
I noticed the issue with Greek TWRP because it didn't ask for a password anymore and I wasn't able to do a backup before flashing 9.10.17. So I just dirty flashed 9.9.26 again over 9.9.26 and then TWRP was working.
Before I was using Greek TWRP but since 9.9.26 it couldn't handle anymore with decrypting my device.

 

[LOLO9393]

As I wrote in the weekly 9.10.17 thread I'm now using chinese TWRP 3.3.1-0916 which came with the ROM. It works fine with de-/encryption of my Mi 9T.
I noticed the issue with Greek TWRP because it didn't ask for a password anymore and I wasn't able to do a backup before flashing 9.10.17. So I just dirty flashed 9.9.26 again over 9.9.26 and then TWRP was working.
Before I was using Greek TWRP but since 9.9.26 it couldn't handle anymore with decrypting my device.

Thanks for your direction.
I've reinstalled 9.10.17 via 3.3.1-0916 Chinese twrp and I confirm encryption is done as required.
Perfect!

 

[Natherul]

I think my issues really comes from last weeks update and not this as it came with android 10 for perseus but no recovery in that, so if official 3.3.1.0 is not able to decrypt it then thats where the issues came from.

And I was careful to not update to 10 because of this however the update list at that point showed perseus as 9.0 and not 10.0