How to install Xiaomi.eu ROM for devices A/B


sorry for asking too much , but according to the getdroidstips link : https://www.getdroidtips.com/twrp-recovery-xiaomi-poco-x5-pro/

seems they link to (( moonstone )) TWRP , and i dont find moonstone associated with any device from the link in the first post , so can this be used ?
Im afraid of fastboot method as i bricked my f3 before , hard brick , dont know the reason why it happened , but i dont want fastboot method as much as possible
 
I already answered you once. You can't use TWRP designed for other devices !!
moonstone = Poco X5 5G
redwood = Poco X5 Pro 5G

You can have a look here.
 
Any ROM that is designed for your device. It is your choice whether to choose the Weekly or Stable version.

Xiaomi 13 = FUXI
 
Last edited:
  • Like
Reactions: JiaiJ
Please can the TWRP in the link on how to install walk on any redmi device too? I have redmi note 12 4g tapas global device and I want to flash Xiaomi EU rom on it.
 
Hello.

I have a redmi note 12 5g with xiaomi.eu 14 stable rom installed with the fastmode scripts. Perfect!
I followed gogocar62's instructions.
I used last current twrp toolkit hybrid and three differents twrp for this device, but not twrp is installed

And typing first
[AB]_boot_twrp.bat script but, twrp isn´t installed.

Second note. I have not tried using this other script
[AB-rec]_install_twrp.bat
Because I want to avoid briclking te device Can you get me out of this doubt. I do not want to cause a crash.

Is it necessary to install the two scripts for this device and what is their order of use, for the installation to be successful?

Thanks for your help
And you are sure that you install the correct TWRP, for your Note 12 and nothing else?
 
  • Like
Reactions: Stonesun
You have it written in the table. Your device is A/B without a dedicated recovery partition.
That's why you use an (A/B) script.

If you use manual terminal commands to install, proceed as follows.
Devices with Boot as Recovery (A/B):
These devices don't have a dedicated partition for recovery.
The recovery ramdisk resides in the "boot_a" and "boot_b" partitions.
A shared kernel is used for both the system and the recovery.
Due to that, you should never flash a custom recovery image directly to the "boot_a" and/or "boot_b" partitions. If you do that, the system will fail to boot.

Platforms: Snapdragon 678/680/695/778G/778G+/780G/870/888/888+
Devices: alioth, haydn, lisa, mona, moonstone, munch, odin, psyche, redwood(in), renoir, spes(n), star/mars, sunny, sunstone, taoyao, thyme, venus, veux/peux, vili
Image size: 192 MiB (201,326,592 bytes), or 96/128 MiB (100,663,296/134,217,728 bytes) for low-mid devices
Installation:

Code:
fastboot boot recovery.img
In the recovery interface: Advanced -> Install Recovery Ramdisk
 
  • Like
Reactions: Stonesun
if you have a file named twrp.img you need to type
Code:
fastboot boot twrp.img

Did you do it that way?
 
  • Like
Reactions: Stonesun
Hello friend.
Excuse my ignorance, but can you or someone tell me if this rom works on the moto g32?

I thank!
 
It's been a long time since I last updated my ROM. Currently, I have version v13.0.12.0 on my Mars device. After reading through a lot of information on this forum, I've become a bit confused. I'm not certain about the steps to update my ROM without losing all my data on the device.
I would be grateful for some assistance
 
Update instructions are in the first post. Choose an update method.
 
Hello, I installed the EU ROM via TWRP on my K70 Pro.
It’s done. It works very well.
But I have a question about TWRP.
I followed the production on page 1 and so I placed the ROM (.zip) in the phone memory. So I did point 4-5 and 6 and installed TRWB using the AB-REC button (depending on my type of device: K70 Pro).
It is at point 7 that I had a small problem: The message "Attempting to decrypt FBE for user". I would loop around, and then ask for my password again. After two or three tries, I could only "Cancel".
I then started the installation of the EU ROM, which I finally had to place on an OTG stick (because the ROM that I had placed in the memory of the phone did not appear in any directory of my phone when I wanted to install it. I do not know if it is related to this problem of description).
So I placed my ROM in an OTG stick and everything went very well.
My K70 Pro works great, but I suspect that the TWRP image file was not flashed properly, since I had to cancel due to this decryption issue. (And looking with the update function, I can’t find anything either).
So I have three questions:
1. How can I see if the TWRP image file has been successfully flashed into my phone.
2. Can I flascher this same TWRP image file again?
3. If I understood everything correctly, it is thanks to the TWRP image file flashed in the phone that we can get OTA updates and as I understood, it is the installation of the EU ROM that allows to permanently install TWRP in the phone. In case I can fashion my TWRP back into the phone, do I need to re-flash the ROM as well so that TWRP stays in my phone? Or it is not necessary.
The purpose of all this is to be able to get OTA updates.
 
1, TWRP is installed correctly if you see it on your device
2, You can always reinstall TWRP (doesn't affect ROM or user data)
3, Unfortunately TWRP for your device as well as for Xiaomi 14 series is not able to decrypt the data partition. That's why OTA will only notify you about the new update but you need to use OTG_USB to install the ROM.
TWRP is not part of xiaomi.eu ROM. It must be installed separately. The installed TWRP remains on the device even after the ROM update.

The conclusion is that due to the inability of TWRP to decrypt the storage, it is not possible to perform OTA updates and actions related to it.
So for updates you have to use OTG or update with fastboot method.
 
Un t
1, TWRP is installed correctly if you see it on your device
2, You can always reinstall TWRP (doesn't affect ROM or user data)
3, Unfortunately TWRP for your device as well as for Xiaomi 14 series is not able to decrypt the data partition. That's why OTA will only notify you about the new update but you need to use OTG_USB to install the ROM.
TWRP is not part of xiaomi.eu ROM. It must be installed separately. The installed TWRP remains on the device even after the ROM update.

The conclusion is that due to the inability of TWRP to decrypt the storage, it is not possible to perform OTA updates and actions related to it.
So for updates you have to use OTG or update with fastboot method.

Many thanks for all the valuable information that allowed me to install this EU ROM.
It saved me a lot of time and this ROM is really good. Thank you very much
 
Hello, at this point I have downloaded the Xiaomi.EU Alioth 1.0.3.0 and the Miflash_unlock folders and have them on my desk top.
I am working on Linx Mint -Victoria.

Fastboot and ADB are pre installed on my workstation, power + voldwn activates fastboot in my Redmi K40.
Developer mode is set on, OEM Unlocking, USB debugging activated.
The command adb devices identifies my Redmi K40 as
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
846ce8a device
Disconnecting USB cable shows no devices present.
The Mi files contain drivers in exe format, which seems to bears out gogocar62's comment re Windows.
However I note in the eu file, there is a Linux folder - BIN contains a Linux fastboot, + Linux fastboot first install and update files are present.
Does this mean the the operation is (somehow) doable via Linux?

Am I good to go and follow the instructions in the tutorial https://xiaomi.eu/community/threads/how-to-install-xiaomi-eu-rom-for-devices-a-b.62738/post-624043) linked to me by gogocar - or is there further work needed?
Has anyone successfully completed this via Linux - any suggestions, advice please?
Will this installation allow me to remove unwanted APPS - I basically only run Signal, WeChat and a few others.
Lastly, (for now) is there a way back -recovery, should everything go south?
I have at this point backed up my current O/S photos, videos etc to my work station.
Thanks everyone.
Bic