Xiaomi 17 Pro Max TWRP Not Working


xScarheadx

Members
13 Mar 2026
8
5
Hello,

i have tried to install twrp on my xiaomi 17 pro max like it was mentioned here https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/.

But i got a failed message in cmd there stands:
Warning: skip copying recovery_ab image avb footer (recovery_ab partition size: 0, recovery_ab image size: 134217728).
Sending 'recovery_ab' (131072 KB) OKAY [ 2.977s]
Writing 'recovery_ab' (bootloader) Partition recovery_a flashed failed
FAILED (remote: '(recovery_a) Image is too large for the partition.')
fastboot: error: Command failed

So I started a commant with:
fastboot flash recovery_a twrp-3.7.1_16-popsicle-YuKongA.img
fastboot flash recovery_b twrp-3.7.1_16-popsicle-YuKongA.img
fastboot reboot recovery

this one worked so that my twrp got installed but the problem is that it dont react to my touches. Means I stuck now in twrp when i open it. Can somebody help by solving this problem?

I have downloaded the twrp-3.7.1_16-popsicle-YuKongA.img (from https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/popsicle/)
and put it in the fastboot windows folder.

After that I have renamed the twrp-3.7.1_16-popsicle-YuKongA.img to recovery and installed it again with the promt:

fastboot flash recovery_ab recovery.img
fastboot reboot recovery

And this was the result:

Warning: skip copying recovery_ab image avb footer (recovery_ab partition size: 0, recovery_ab image size: 104857600).
Sending 'recovery_ab' (102400 KB) OKAY [ 2.426s]
Writing 'recovery_ab' (bootloader) Partition recovery_a flashed successfully
(bootloader) Partition recovery_b flashed successfully
OKAY [ 0.152s]
Finished. Total time: 2.651s

After the reboot in the recovery the twrp stucks anyway.

ok I have installed hyperos again with install and format data. After that my twrp was deleted. And than I installed twrp again by the correct way. But I still stuck in TWRP... Why.. Please help.

Newest Update: I have installed HyperOS 3.0.45.0 EU again with install and format data so i dont have TWRP anymore. Maybe someone can tell me how I can install TWRP in correct way.
 
Last edited:
Do somebody have a solution or do you somebody have the same problem on the Xiaomi 17 Pro Max?

Also the ZIP installation in my magisk are not working. It is turned on and i can grant root in some apps. Zygisk is on and Ramdisk also. But if I try to install modules there stands this is not a magisk module..
 
Idk if it works but in this german forum they say that they solved it.


I have the same problem, I hope it'll work.
 
  • Like
Reactions: xScarheadx
First of all a lot of love for your response. Its not correct that the problem has solved. The man writing in this german forum is myself. I wrote there before I asked here for a solution. I Just mentioned there like here what I tried to solve but nothing worked.

Maybe we will get a newer twrp soon and that will work. If u find a solution please let me know. I will also contact you when I find a way to bring the twrp to work.
 
First of all a lot of love for your response. Its not correct that the problem has solved. The man writing in this german forum is myself. I wrote there before I asked here for a solution. I Just mentioned there like here what I tried to solve but nothing worked.

Maybe we will get a newer twrp soon and that will work. If u find a solution please let me know. I will also contact you when I find a way to bring the twrp to work.
This is a common problem with the twrp for the first builds. It will probaby soon be corrcted.
 
  • Like
Reactions: xScarheadx
Hello,

i have tried to install twrp on my xiaomi 17 pro max like it was mentioned here https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/.

But i got a failed message in cmd there stands:
Warning: skip copying recovery_ab image avb footer (recovery_ab partition size: 0, recovery_ab image size: 134217728).
Sending 'recovery_ab' (131072 KB) OKAY [ 2.977s]
Writing 'recovery_ab' (bootloader) Partition recovery_a flashed failed
FAILED (remote: '(recovery_a) Image is too large for the partition.')
fastboot: error: Command failed

So I started a commant with:
fastboot flash recovery_a twrp-3.7.1_16-popsicle-YuKongA.img
fastboot flash recovery_b twrp-3.7.1_16-popsicle-YuKongA.img
fastboot reboot recovery

this one worked so that my twrp got installed but the problem is that it dont react to my touches. Means I stuck now in twrp when i open it. Can somebody help by solving this problem?

I have downloaded the twrp-3.7.1_16-popsicle-YuKongA.img (from https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/popsicle/)
and put it in the fastboot windows folder.

After that I have renamed the twrp-3.7.1_16-popsicle-YuKongA.img to recovery and installed it again with the promt:

fastboot flash recovery_ab recovery.img
fastboot reboot recovery

And this was the result:

Warning: skip copying recovery_ab image avb footer (recovery_ab partition size: 0, recovery_ab image size: 104857600).
Sending 'recovery_ab' (102400 KB) OKAY [ 2.426s]
Writing 'recovery_ab' (bootloader) Partition recovery_a flashed successfully
(bootloader) Partition recovery_b flashed successfully
OKAY [ 0.152s]
Finished. Total time: 2.651s

After the reboot in the recovery the twrp stucks anyway.

ok I have installed hyperos again with install and format data. After that my twrp was deleted. And than I installed twrp again by the correct way. But I still stuck in TWRP... Why.. Please help.

Newest Update: I have installed HyperOS 3.0.45.0 EU again with install and format data so i dont have TWRP anymore. Maybe someone can tell me how I can install TWRP in correct way.
There was a issue in TWRP. You need USB hub and mouse to use TWRP. I'm also use that method.
 
  • Like
Reactions: xScarheadx
Does anyone want to test my mod to see if the touch works?
I would or could but currently i dont need twrp. Also what happens if it get cracked? I dont can loose all my datas. The first time i mean for the bootloader unlock was also too much to set my phone back.
 
If it doesn't work, reflash the original recovery... I just tried to fix the touch... I would like to understand if with displays from different vendors it now chooses it correctly... Nothing should happen.
 
O man im struggling. The thing is i can understand that u need somebody who test your mod. And i know such Situation and want to help. On the other side if i will get root my banking apps will Stop working. And they work now without prob.

But you know what I will give it a try. How to communicate?
 
Last edited:
It's not root, it's recovery, my 17 pro max is arriving, I ordered it but I've already started working on it because I want a good recovery and an update from xiaomi.eu that works without problems. As if it were an original system. Write on telegram: @ab123ab567
 
It's not root, it's recovery, my 17 pro max is arriving, I ordered it but I've already started working on it because I want a good recovery and an update from xiaomi.eu that works without problems. As if it were an original system. Write on telegram: @ab123ab567
Send it to me I will try to test it tomorrow
 
It's not root, it's recovery, my 17 pro max is arriving, I ordered it but I've already started working on it because I want a good recovery and an update from xiaomi.eu that works without problems. As if it were an original system. Write on telegram: @ab123ab567
thanks for the help with 17 ultra twrp, btw i'm your tester for 17 ultra.
@antocorvo.30000 has manage to fix the touch issue for nezha and popsicle twrp, thanks for the work, next step he's working on memory decrypt.

Stay tuned guys..
 
  • Like
Reactions: hsnsnyn
How can I access the touch-enabled TWRP for Popsicles?

2509FPN0BC cihazımdan Tapatalk kullanılarak gönderildi