SUGGESTION

[Alvy200]

When publishing a xiaomi.eu version that includes a newer android version, it might be useful to have an update of twrp that supports that os version inside the zip itself, cause if an older version is installed, during the update data cannot be decrypted and format becomes mandatory.

 

[Poney70]

What?

You don't need to format your data at all, you can use your device without issue even if the currently installed TWRP can not decrypt your data partition. You can just wait for a new TWRP release and even install a new TWRP version by yourself!

If no TWRP version with new data encryption support is available, you can also use USB-OTG device to install ROM update.

And xiaomi.eu ROMs always try to include a working TWRP (encryption support/backup support/etc.) for your device of course. ^^

 

[Alvy200]

What?

You don't need to format your data at all, you can use your device without issue even if the currently installed TWRP can not decrypt your data partition. You can just wait for a new TWRP release and even install a new TWRP version by yourself!

If no TWRP version with new data encryption support is available, you can also use USB-OTG device to install ROM update.

And xiaomi.eu ROMs always try to include a working TWRP (encryption support/backup support/etc.) for your device of course. ^^

I tried to install the weekly rom, but it failed decrypting data, and suggested to format and clean flash rom.

Sent from my M2007J3SG using Tapatalk

 

[Igor Eisberg]

We usually do include TWRP, like we do for cmi, umi and lmi, for that exact reason.
Sometimes, a compatible TWRP gets released after we released the ROMs with the compatible TWRP release... in that case, we don't include TWRP.
There are instances where multiple TWRP releases are available, in which case we don't want to mess with the user's choice.
But to sum this up, TWRP is not our responsibility. We release ROMs, the user is responsible for updating his TWRP.

I tried to install the weekly rom, but it failed decrypting data, and suggested to format and clean flash rom.

Sent from my M2007J3SG using Tapatalk

In which case your TWRP doesn't support data decryption for Android 11. There is zero we can do about that. It's not like we have a better TWRP release to offer.

 

[Alvy200]

We usually do include TWRP, like we do for cmi, umi and lmi, for that exact reason.
Sometimes, a compatible TWRP gets released after we released the ROMs with the compatible TWRP release... in that case, we don't include TWRP.
There are instances where multiple TWRP releases are available, in which case we don't want to mess with the user's choice.
But to sum this up, TWRP is not our responsibility. We release ROMs, the user is responsible for updating his TWRP.


In which case your TWRP doesn't support data decryption for Android 11. There is zero we can do about that. It's not like we have a better TWRP release to offer.

I had android 10 stable, to update to weekly i had 3.4.0 twrp and had the error. Needed to format and use otg to reflash

Sent from my M2007J3SG using Tapatalk

 

[Alvy200]

I had android 10 stable, to update to weekly i had 3.4.0 twrp and had the error. Needed to format and use otg to reflash

Sent from my M2007J3SG using Tapatalk

Then I installed 3.5.0 beta twrp

Sent from my M2007J3SG using Tapatalk

 

[Poney70]

I had android 10 stable, to update to weekly i had 3.4.0 twrp and had the error. Needed to format and use otg to reflash

Sent from my M2007J3SG using Tapatalk

Stable -> Weekly = You have to format data and it has nothing to do with TWRP...

 

[Alvy200]

Stable -> Weekly = You have to format data and it has nothing to do with TWRP...

Oh ok!
I red that this was only for downgrade, not upgrade

Sent from my M2007J3SG using Tapatalk

 

[Poney70]

Oh ok!
I red that this was only for downgrade, not upgrade

Sent from my M2007J3SG using Tapatalk

Yes it's an upgrade but... it requires format data in most cases.

 

[Alvy200]

Yes it's an upgrade but... it requires format data in most cases.

Can u tell me why? I'm curious

Sent from my M2007J3SG using Tapatalk

 

[Poney70]

Can u tell me why? I'm curious

Sent from my M2007J3SG using Tapatalk

I can't answer to this question without being 100% certain but I found that it can be related to the security patch date info in the /system/build.prop file:

In Weekly ROMs by xiaomi.eu, this date info can be older than the real security patch date of the ROM. Why? It's for passing SafetyNet "CTS Profile Match" test.

China Beta ROMs by Xiaomi (Weekly ROMs by xiaomi.eu are based on them) don't pass SafetyNet so xiaomi.eu should must use fingerprint build info & security patch date info from a Stable ROM).

And you can't boot to system if you have an older security patch date info than your latest used ROM.

 

[Alvy200]

I can't answer to this question without being 100% certain but I found that it can be related to the security patch date info in the /system/build.prop file:

In Weekly ROMs by xiaomi.eu, this date info can be older than the real security patch date of the ROM. Why? It's for passing SafetyNet "CTS Profile Match" test (Beta ROM doesn't pass SafetyNet so you have to use a fingerprint build & security patch date info from a Stable ROM).

And you can't boot to system if you use an older security patch date info than your latest used ROM.

Oh got it
Not easy but ok

Sent from my M2007J3SG using Tapatalk

 

[Igor Eisberg]

I can't answer to this question without being 100% certain but I found that it can be related to the security patch date info in the /system/build.prop file:

In Weekly ROMs by xiaomi.eu, this date info can be older than the real security patch date of the ROM. Why? It's for passing SafetyNet "CTS Profile Match" test.

China Beta ROMs by Xiaomi (Weekly ROMs by xiaomi.eu are based on them) don't pass SafetyNet so xiaomi.eu should must use fingerprint build info & security patch date info from a Stable ROM).

And you can't boot to system if you have an older security patch date info than your latest used ROM.

That's correct, fingerprint and security patch dates we use for weeklies are usually older so they could pass SafetyNet check.

 

[Alvy200]

That's correct, fingerprint and security patch dates we use for weeklies are usually older so they could pass SafetyNet check.

It's like a security patch downgrade

Sent from my M2007J3SG using Tapatalk

 

[Igor Eisberg]

It's like a security patch downgrade

Sent from my M2007J3SG using Tapatalk

Changing the displayed date isn't changing the actual security patch...