MIUI 13 22.6.29

[Karpfenhai]

OP? I dont understand what you mean. Sry for the stupid question ;-)
I use the TWRP from the Update two weeks before.

This one?

3.6.2_12-Mi11Ultra-Mi11Pro_v3.7_A12-star-skkk_7bb5f333.img



Sent from my Mi 11 Ultra.

 

[Igor Eisberg]

Hi, updater can't download file.
Also HMK40Pro+ not flashable - Rom is haydn not haydn pro.

Can anyone help?

I wrote about this on another thread: https://xiaomi.eu/community/threads/22-6-22.66171/post-662762

Sounds like you need to get hold of that TWRP's developer (skkk) and let him know about that. There is no such thing as "haydnpro" when it comes to "ro.product.device" prop, which is what the updater-script checks for. Only "haydn" and "haydnin" exist.
Our recovery flashing scripts match our fastboot flashing scripts. If flashing via fastboot used to work for you, then the developer of that TWRP made a mistake.

 

[Denis19xx]

This one?

3.6.2_12-Mi11Ultra-Mi11Pro_v3.7_A12-star-skkk_7bb5f333.img



Sent from my Mi 11 Ultra.

Yes.

 

[gkalen]

I commented and changed for "haydnpro" but now gives me another error: "Could not extract 'META-INF/com/google/android/update-binary'

For Mi 11i , Haydn you have to change updater script to something like that below ..
Only the first line , make it ..

getprop("ro.product.device") == "haydn" || getprop("ro.product.device") == "haydnpro" || abort("E3004: This package is for \"haydn or haydnpro\" devices; this is a \"" + getprop("ro.product.device") + "\".");

This way can read haydn or haydnpro and installation will be completed just fine ..
You can even delete whole first line ..
This is a twrp issue ..

 

[Bec de Xorbin]

Sounds like you need to get hold of that TWRP's developer (skkk) and let him know about that. There is no such thing as "haydnpro" when it comes to "ro.product.device" prop, which is what the updater-script checks for. Only "haydn" and "haydnin" exist.
Our recovery flashing scripts match our fastboot flashing scripts. If flashing via fastboot used to work for you, then the developer of that TWRP made a mistake.

Fair enough. It's not a big deal to me to change that manually, although I cannot see any harm to add "haydnpro" until skkk fixes this but it's your choice obviously.

 

[Keetn3]

OP? I dont understand what you mean. Sry for the stupid question ;-)
I use the TWRP from the Update two weeks before.

Some users on Mi 10 Ultra faced this problem last week then he tried the following methods and it worked

Belshi:

1. Delete password/pin in setting

2. Reboot into TWRP

3. Boot into system

4. Set a new password/pin

5. Reboot to TWRP again

6. Now TWRP will ask for password/pin

 

[tomsten]

First run after dirty flash took almost 6mins (Mi 10) but everything works fine now

 

[Karpfenhai]

Yes.

Okay great, see the answer above for resetting your pattern, if twrp is not asking for it, data will never be decrypted.

Sent from my Mi 11 Ultra.

 

[Karpfenhai]

Some users on Mi 10 Ultra faced this problem last week then he tried the following methods and it worked

Belshi:

1. Delete password/pin in setting

2. Reboot into TWRP

3. Boot into system

4. Set a new password/pin

5. Reboot to TWRP again

6. Now TWRP will ask for password/pin

I wonder if this issue only occurs if the user had twrp installed under A11 back in the day, maybe it's a leftover and the twrp folder must be deleted first?

Sent from my Mi 11 Ultra.

 

[tomsten]

Could files checksums be added on forum in the future?

 

[minotavros]

Installed successfully. Thanks eu team for update!

From my poco f3 via Tapatalk

 

[juankar7]

Hello, I am trying to install twrp again on mi 11 pro to be able to use it again with 22-6-22 but there is no way, in the adb it appears connected but when inserting the command fastboot boot twrp.img it appears "no such file or directory" I have it in the root of the xiaomi and in the root of the adb installed in C. I am in version 22-6-15.
Thank you all,
Greetings.

As usual you have to have twrp.img in working directory, i.e. adb.exe directory

 

[Leal2845]

now the icon appears when opening some applications and it is quite ugly! it should be removed..

 

[Leal2845]

now the icon appears when opening some applications and it is quite ugly! it should be removed..

 

[Denis19xx]

Some users on Mi 10 Ultra faced this problem last week then he tried the following methods and it worked

Belshi:

1. Delete password/pin in setting

2. Reboot into TWRP

3. Boot into system

4. Set a new password/pin

5. Reboot to TWRP again

6. Now TWRP will ask for password/pin

It works when i don´t habe a pin or pattern. When i activate one of them it didn´t work.

 

[Karpfenhai]

now the icon appears when opening some applications and it is quite ugly! it should be removed..

Agreed!

Sent from my Mi 11 Ultra.

 

[desire1504]

Redi K40 pro update fine to 22.6.29 recovery from 22.6.22 fastboot, thank dev

 

[Denis19xx]

It works when i don´t habe a pin or pattern. When i activate one of them it didn´t work.

Edit: With a Pin it works With pattern no :-(

 

[Leanlioncourt]

First one trying on Lisa?

 

[Jorisimone]

Installed the rom without issues Poco F3! My recovery changed with nebrassy 3.6.2. Is there any recovery in the rom?

 

[Andreasgbr]

Hello guys and devs!Can you tell me if GPU TUNER settings are back in this update?I really miss that in 22.6.22 on Poco F3

 

[MrMcFly]

All so nice and easy with twrp. Just download to phone, flash on phone, reboot, flash magisk on phone and go.

TY devs, great job as always!

 

[aways]

For mi 10t pro no ota update?

 

[minotavros]

Installed the rom without issues Poco F3! My recovery changed with nebrassy 3.6.2. Is there any recovery in the rom?

Me too, twrp replaced

From my poco f3 via Tapatalk

 

[Mymymi]

OP? I dont understand what you mean. Sry for the stupid question ;-)
I use the TWRP from the Update two weeks before.

I had a password lock, and like you when I went in to twrp there was no file but I knew it should work because it did last week. So because last week I had taken off all password, fingerprint and photo unlocks when I flashed twrp, I removed them all just now - entered recovery and the file was there. So I suggest you disable all your phone locks and see if this works.