Xiaomi 14 Ultra [TWRP]

[Rayglobe]

TWRP for Mi 14 Ultra

In fastboot
Fastboot flash recovery_ab recovery.img
Fastboot reboot recovery

Link for download

100 MB file on MEGA

mega.nz

 

[migmax1995]

I tried it and I get to the page for the recovery I see the logo and image but nothing else also I get stuck in a bootloop to recovery unless I press keys to get back to fastboot I have the Xiaomi 14 ultra

 

[Rayglobe]

I tried it and I get to the page for the recovery I see the logo and image but nothing else also I get stuck in a bootloop to recovery unless I press keys to get back to fastboot I have the Xiaomi 14 ultra

You must delete sdcard twrp directory and data/recovery directory. My recovery work on european and chinese ver not India one

 

[Chetzz]

Works just fine on mine, have chinese variant.

 

[migmax1995]

You must delete sdcard twrp directory and data/revovery directory. My revovery work on european and chinese ver not India one

i can reboot no problem after flashing but as soon as i try to reboot to recovery i see the teamwin logo and at the bottom teamwin and recovery project 3.7.1_12-Xiaomi14Ultra by Rayglobe but nothing else and when i try to reboot again i get rebooted to recovery no matter what, also my rom is aurora_eea_global_images_OS1.0.9.0.UNAEUXM wich it came with I bought in in spain. the only way to fix the bootloop is to flash the original recovery and flash original boot.img again.

Also in adb shell i can see those folders wich i didnt see before booting into recovery from my phones root folder : twres, twrp_ramdisk-timestamp

finally before booting to recovery after my first reboot i could not see any of these two sub-directories in root explorer : sdcard/twrp directory and data/revovery directory

 

[migmax1995]

I finally got it to work but had to go from scratch, here are the steps i took :

1. flash stock recovery via fastboot : fastboot flash recovery_ab recovery.img
2. flash stock boot image (boot.img) : fastboot flash boot boot.img
3. fastboot reboot

then it got in the stock recovery and i had the option to reboot to system which i usually do, but i opted for wipe data and confirmed the wipe (be careful as this will erase all your data on the phone you'll have to configure it again and restore your files, apps and configs)

4. Wipe data and confirm from stock recovery
5. VERY IMPORTANT dont boot into phone just yet instead maintain power button and volume down to reboot into fastboot
6. In fastboot flash the twrp recovery from Rayglobe in the post (i renamed the file to recovery_twrp.img) : recovery_twrp.img
7. fastboot reboot recovery

ET VOILA!

i got into the recovery finally haha just will have to restore backup from xiaomi, google, and neo backup and i should be good to go!

 

[migmax1995]

I finally got it to work but had to go from scratch, here are the steps i took :

1. flash stock recovery via fastboot : fastboot flash recovery_ab recovery.img
2. flash stock boot image (boot.img) : fastboot flash boot boot.img
3. fastboot reboot

then it got in the stock recovery and i had the option to reboot to system which i usually do, but i opted for wipe data and confirmed the wipe (be careful as this will erase all your data on the phone you'll have to configure it again and restore your files, apps and configs)

4. Wipe data and confirm from stock recovery
5. VERY IMPORTANT dont boot into phone just yet instead maintain power button and volume down to reboot into fastboot
6. In fastboot flash the twrp recovery from Rayglobe in the post (i renamed the file to recovery_twrp.img) : recovery_twrp.img
7. fastboot reboot recovery

ET VOILA!

i got into the recovery finally haha just will have to restore backup from xiaomi, google, and neo backup and i should be good to go!

EDIT: As soon as I boot once and try to boot back in recovery i get stuck on splash screen again so after first successful boot twrp stop working i think it has to do with encryption. i tried many different way i can reboot over and over in twrp no problem unless i do one successful boot to system then i need to go trough all the steps mentionned before to get TWRP to work again

 

[HinataHinata]

Thank you for the development. My device has been flashed in

 

[Rayglobe]

New ver. with MAgisk Delta inside

100 MB file on MEGA

mega.nz

 

[doxies_971]

New ver. with MAgisk Delta inside

100 MB file on MEGA

mega.nz

Hello when the bootloader is unlocked, the ROM xiaomi.eu install, what is the procedure to follow to install twrp on my xiaomi 14 ultra.

 

[doxies_971]

Hello I followed the procedure to install twrp on my xiaomi 14 ultra.
But to my surprise it remains stuck on twrp and I can't do anything.
I ran the commands below :
fastboot flash recovery_ab recovery.img
fastboot reboot recovery
fastboot erase misc
fastboot set_active a
and nothing more the phone remains stuck in fastboot mode I messed up and did the manipulation manually with the power / - button to exit fastboot mode
Can you help me please.

 

[Mark F]

Flash the original recovery or the whole rom via fastboot. But just update, not wipe.

 

[doxies_971]

Flash the original recovery or the whole rom via fastboot. But just update, not wipe.

Hello, thank you for your answer, I did it and still the same result, it restarts on the twrp recovery and it remains blocked there, nothing to do

 

[Senpy]

If you use `fastboot erase misc`, it should unset opening recovery when you use `fastboot reboot`

Don't touch recovery for now. As far as I see, there's no real value in it at the moment, even if it loaded recovery correctly.

 

[doxies_971]

If you use `fastboot erase misc`, it should unset opening recovery when you use `fastboot reboot`

Don't touch recovery for now. As far as I see, there's no real value in it at the moment, even if it loaded recovery correctly.

Since this morning I've been trying to unlock my phone on twrp but nothing to do, I reinstalled the ROM, did the update and it restarted on twrp I'm going to try to do it with the official hyperos ROM with miflash to remove everything because I'm lost

 

[Senpy]

It's not going to the rom, so changing that won't do anything.

Phone on -> boot mode -> {rom, recovery, fastboot}

Right now it's set to boot to recovery, so you need to unset that. Set active won't change anything since you most likely flash to both A and B slots.

If erase didn't fix it, flash the init_boot and boot image for your room.

I forgot what I did to get out of recovery loop, but it was some combination of those commands.

 

[doxies_971]

It's not going to the rom, so changing that won't do anything.

Phone on -> boot mode -> {rom, recovery, fastboot}

Right now it's set to boot to recovery, so you need to unset that. Set active won't change anything since you most likely flash to both A and B slots.

If erase didn't fix it, flash the init_boot and boot image for your room.

I forgot what I did to get out of recovery loop, but it was some combination of those commands.

Sorry I use Google translate to communicate with you. But I don't understand what you mean. Do you have a tutorial to follow the procedure. What a hassle, very complicated to find a solution

 

[Senpy]

Go to folder you extracted rom.
Run:
```
fastboot erase misc
fastboot flash boot_ab images/boot.img
fastboot flash init_boot_ab images/init_boot.img
fastboot reboot
```

These are the commands I usually use to fix boot issues.

 

[doxies_971]

Go to folder you extracted rom.
Run:
```
fastboot erase misc
fastboot flash boot_ab images/boot.img
fastboot flash init_boot_ab images/init_boot.img
fastboot reboot
```

These are the commands I usually use to fix boot issues.

So if I understand correctly.

I open my ROM xiaomi.eu file that I installed on my xiaomi 14 ultra.

I run cmd I put the phone in fastboot mode with the power and volume button - then I type exactly the same command that you quoted me here :

fastboot flash boot_ab images/boot.img

fastboot flash init_boot_ab images/init_boot.img

fastboot reboot

And normally everything should be back to normal?

 

[Finch]

In Windows Powershell i type this:

./fastboot erase misc (Enter)

,/fastboot flash boot_ab "Drag and drop file" (Enter)

Getting this:
Warning: skip copying boot_ab image avb footer (boot_ab partition size: 0, boot_ab image size: 100663296).
Sending 'boot_ab' (98304 KB) OKAY [ 2.352s]
Writing 'boot_ab' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

well then i tried
./fastboot flash init_boot_ab "drag and drop file here"

and again i get:
Sending 'init_boot_ab' (8192 KB) OKAY [ 0.194s]
Writing 'init_boot_ab' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Well i still stuck at Mi Logo =/

 

[FastRider]

Please tell me a working TWRP for flashing the EU. What is in this thread, as I understand, is more suitable for flashing the elite. Which TWRP will be correct For EU firmware to install Magisk and obtain root rights. ?

 

[Senpy]

Please tell me a working TWRP for flashing the EU. What is in this thread, as I understand, is more suitable for flashing the elite. Which TWRP will be correct For EU firmware to install Magisk and obtain root rights. ?

You don't need TWRP to get root. Just patch init_boot or boot like magisk/apatch/kernelsu want and flash it in fastboot

 

[FastRider]

You don't need TWRP to get root. Just patch init_boot or boot like magisk/apatch/kernelsu want and flash it in fastboot

I need twrp for convenience and installation of magisk, as well as viperFX modules. Can you suggest a working version of TWRP for EU firmware?

 

[ffrrf]

I need twrp for convenience and installation of magisk, as well as viperFX modules. Can you suggest a working version of TWRP for EU firmware?

All Model fixed

 

[Senpy]

I need twrp for convenience and installation of magisk, as well as viperFX modules. Can you suggest a working version of TWRP for EU firmware?

The only benefit of TWRP is updating the ROM. Rooting is done once per ROM update.

ViperFX and other modules can be installed within your root manager. Not sure how TWRP is more convenient for this as you need to reboot into recovery, flash, and then reboot vs install and reboot. Took me less than 5 minutes to grab the driver and apk, then install it.

For working versions, there's only 1 build for the 14 ultra and I never got it to work. If you want one, either build it yourself, commission someone to build it for you, or change devices. TWRP doesn't even fully work as it can't decrypt the user data partition and you would need to otg in order to update the ROM.