I've Mi 9T Pro with Global MIUI 10.3.3.0 and magisk installed (i patched and flashed the boot image). I don't have a custom recovery installed.
Now i see that the last version of firmware is EMUI 11.0.3.0. My phone notify me only the OTA for the MIUI 10.3.4.0, so how should i update the phone without breaking or bootlooping? I supposed:
1) Flashing stock boot image of 10.3.3.0 (is the right way to remove magisk? I would reinstall later)
2) OTA to 10.3.4.0
3) Maybe OTA to 11.0.3.0 or installing manually
4) Flash Magisk patched boot image of 11.0.3.0.
Is the correct way? I'm missing some step? I don't want to reset the whole phone..
Thanks in advance.
Someone can help me?
WFree said:
Someone can help me?
Click to expand...
Click to collapse
If the update MIUI 11 is not shown from your system:
• Download the correct recovery ROM from here[/b];
• Put it in the folder "downloaded_rom" in the root of your internal memory;
• Select local update and then the ROM you placed in before;
• Install Magisk with the method you prefere (I suggest to modify the boot.img from a fastboot ROM).
MagikGab said:
If the update MIUI 11 is not shown from your system:
• Download the correct recovery ROM from here[/b];
• Put it in the folder "downloaded_rom" in the root of your internal memory;
• Select local update and then the ROM you placed in before;
• Install Magisk with the method you prefere (I suggest to modify the boot.img from a fastboot ROM).
Click to expand...
Click to collapse
But what about the current rom with Magisk installed, should i remove it first? Can i overwrite the boot image?
Flashing the full firmware (about 2.5gb) will erase my data partition?
Grazie.
WFree said:
But what about the current rom with Magisk installed, should i remove it first? Can i overwrite the boot image?
Flashing the full firmware (about 2.5gb) will erase my data partition?
Grazie.
Click to expand...
Click to collapse
It's not needed to uninstall Magisk before, because when you'll install the update through recovery, it will overwrite the boot partition. With the stock recovery you should be able to keep all your data and settings, but I suggest you to perform anyway a backup! Just in case.
MagikGab said:
It's not needed to uninstall Magisk before, because when you'll install the update through recovery, it will overwrite the boot partition. With the stock recovery you should be able to keep all your data and settings, but I suggest you to perform anyway a backup! Just in case.
Click to expand...
Click to collapse
Thanks again for the info. But just to be secure, here is reported the way to apply OTA with Magisk: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
There talk about uninstalling Magisk and restoring boot image, A/B Partitions, non A/B Partitions, and i don't know which partitions my device have. Moreover it talk about to don't modify the /system but i don't remember if i touched something, maybe the build.prop...
But, based on your previous response, i deduce that this instructions are valid only if i flash incremental update. Instead, if i flash the full rom there should not be problems, i'm right?
WFree said:
But what about the current rom with Magisk installed, should i remove it first? Can i overwrite the boot image?
Flashing the full firmware (about 2.5gb) will erase my data partition?
Grazie.
Click to expand...
Click to collapse
WFree said:
Thanks again for the info. But just to be secure, here is reported the way to apply OTA with Magisk: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
There talk about uninstalling Magisk and restoring boot image, A/B Partitions, non A/B Partitions, and i don't know which partitions my device have. Moreover it talk about to don't modify the /system but i don't remember if i touched something, maybe the build.prop...
But, based on your previous response, i deduce that this instructions are valid only if i flash incremental update. Instead, if i flash the full rom there should not be problems, i'm right?
Click to expand...
Click to collapse
Do not care about A/B partitions, as the Mi 9T Pro is a single partition device. So no problem related to installing files/updates to both partitions
Anyway, if the system detects that you have Magisk installed, simply uninstall it from the Magisk Manager, than proceed to the update
MagikGab said:
Do not care about A/B partitions, as the Mi 9T Pro is a single partition device. So no problem related to installing files/updates to both partitions
Anyway, if the system detects that you have Magisk installed, simply uninstall it from the Magisk Manager, than proceed to the update
Click to expand...
Click to collapse
Ok. Can i upgrade directly from 10.3.3.0 to 11.0.3.0, skipping then the 10.3.4.0 ?
WFree said:
Ok. Can i upgrade directly from 10.3.3.0 to 11.0.3.0, skipping then the 10.3.4.0 ?
Click to expand...
Click to collapse
Yes. I did so
MagikGab said:
Yes. I did so
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which type should i download? Recovery o Fastboot? What's the difference?
And should i download the Firmware or the MIUI?
WFree said:
Which type should i download? Recovery o Fastboot? What's the difference?
And should i download the Firmware or the MIUI?
Click to expand...
Click to collapse
Recovery ROMs must be flashed in the recovery and have .zip file extension; fastboot ROMs must be flashed with MiFlash tool and have .tar.gz file extension.
First of all, identify you device (global, EU, China, Indian...) looking in your device information. You have to remember these two letters in the label of the ROM:
E.g. PFKEUXM, that indicate your phone vendor, while the first letter indicates the Android version.
In few words, you need the recovery ROM. You'll need the fastboot ROM if you want to install Magisk without TWRP (search in Mi 9T Pro forum for: "Install Magisk without TWRP") or if you want to perform a clean flash with MiFlash tool.
Last thing: you need to download the ROM, not the firmware.
MagikGab said:
Recovery ROMs must be flashed in the recovery and have .zip file extension; fastboot ROMs must be flashed with MiFlash tool and have .tar.gz file extension.
First of all, identify you device (global, EU, China, Indian...) looking in your device information. You have to remember these two letters in the label of the ROM:
E.g. PFKEUXM, that indicate your phone vendor, while the first letter indicates the Android version.
In few words, you need the recovery ROM. You'll need the fastboot ROM if you want to install Magisk without TWRP (search in Mi 9T Pro forum for: "Install Magisk without TWRP") or if you want to perform a clean flash with MiFlash tool.
Last thing: you need to download the ROM, not the firmware.
Click to expand...
Click to collapse
Thanks. I've the European version, PFKEUXM. Anyway yes, after the upgrade i want flash Magisk without TWRP. With previous rom i've extracted the boot image from the update archive and patched with Magisk.
WFree said:
Thanks. I've the European version, PFKEUXM. Anyway yes, after the upgrade i want flash Magisk without TWRP. With previous rom i've extracted the boot image from the update archive and patched with Magisk.
Click to expand...
Click to collapse
Exactly what I've done!
PS: vedo che sei italiano, ciao! :victory:
MagikGab said:
If the update MIUI 11 is not shown from your system:
• Download the correct recovery ROM from here[/b];
• Put it in the folder "downloaded_rom" in the root of your internal memory;
• Select local update and then the ROM you placed in before;
• Install Magisk with the method you prefere (I suggest to modify the boot.img from a fastboot ROM).
Click to expand...
Click to collapse
- Tried to install 11.0.3.0 with local update from updater but it say "flash to this stable version is not allowed".
- Tried to install 10.3.4.0 with local update from updater, the phone reboot in recovery and start flashing but at 1% say "update.zip is corrupted". I tried also to download and install this update downloading directly from the updater but same thing happen.
I've uninstalled Magisk from Magisk Manager app: i clicked Uninstall and then Complete Uninstall, not Restore images.
Any suggestion?
WFree said:
- Tried to install 11.0.3.0 with local update from updater but it say "flash to this stable version is not allowed".
- Tried to install 10.3.4.0 with local update from updater, the phone reboot in recovery and start flashing but at 1% say "update.zip is corrupted". I tried also to download and install this update downloading directly from the updater but same thing happen.
I've uninstalled Magisk from Magisk Manager app: i clicked Uninstall and then Complete Uninstall, not Restore images.
Any suggestion?
Click to expand...
Click to collapse
The updater app can only install updates for the same region. Your OP suggests you have a global phone, but it looks like you're trying to flash an EEA update. Currently 11.0.1 is the latest global version.
Robbo.5000 said:
The updater app can only install updates for the same region. Your OP suggests you have a global phone, but it looks like you're trying to flash an EEA update. Currently 11.0.1 is the latest global version.
Click to expand...
Click to collapse
I attach config of my phone. Is the EU version right?
WFree said:
I attach config of my phone. Is the EU version right?
Click to expand...
Click to collapse
OK, yes you have the EU version already.
I don't know for sure, but I guess it won't jump from an Android 9 - MIUI 10 ROM to an Android 10 - MIUI 11 ROM.
You could try updating to the last MIUI 10 build first, and if that works, see if it will then update from the last 10 build to MIUI 11.
Robbo.5000 said:
OK, yes you have the EU version already.
I don't know for sure, but I guess it won't jump from an Android 9 - MIUI 10 ROM to an Android 10 - MIUI 11 ROM.
You could try updating to the last MIUI 10 build first, and if that works, see if it will then update from the last 10 build to MIUI 11.
Click to expand...
Click to collapse
I tried to update MIUI 10 with local update and with updater but fail with update.zip corrupted message
Hey, some smartphones have a incremental update to prepare the phones before big updates pra you can use mi flash and try via fastboot method
Nautilus99 said:
Hey, some smartphones have a incremental update to prepare the phones before big updates pra you can use mi flash and try via fastboot method
Click to expand...
Click to collapse
I tried incremental update from the current 10.3.3.0 to 10.3.4.0 as the updater suggest me. But still failing.
Related
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
MagikGab said:
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
Click to expand...
Click to collapse
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Robbo.5000 said:
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Click to expand...
Click to collapse
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
i have the same question too..
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
P12AV33N said:
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
Click to expand...
Click to collapse
I would just add to this that, although this is all that is required, I would still backup things, just in case.
It's always good practice when flashing things to backup what you can, even when it's not needed should things go smoothly. It only takes an absent minded moment of stupidity in TWRP to do some serious damage. As many people, myself included, can vouch for.
Thank you everyone!
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
macanovic88 said:
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
Click to expand...
Click to collapse
Flashing a minor update is fine to do as a dirty flash in TWRP.
Doing a major update is 50/50 (going from 10.3.x to 10.4.x as it's s change from Android 9 to 10, or going from 10.x.x to 11.x.x). You may be fine, you may have issues. It might be a better option to try using the 'save data' option in the Mi Flash Tool, which is the same as a dirty flash, but will still update vendor and firmware files, should they have changed between the versions.
You might be guided by what the OTA would do. Occasionally when an OTA provides a major version change, it will perform a clean flash and give you big warnings that this will happen first. If an OTA tells you this will happen, then I would definitely use the Mi Flash Tool and use the 'clean all' option.
As for the compatibility zip, it depends on the TWRP you are using. Just try as is first and if your get an error about the wrong device, then remove it and try again.
Thanks a lot, your answers are very helpful in this thread! ?
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
cgdams said:
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
Click to expand...
Click to collapse
You need to confirm if orangefox is actually ready for OTA by checking in its settings.
Sent from my Redmi K20 Pro using Tapatalk
How to install Xiaomi.eu ROM for Xiaomi MI 11
We will release fastboot ROM versions until TWRP for venus is released TWRP is RELEASED
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update your stock ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file BETA or STABLE
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file WEEKLY or STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
-----------EDIT 20.5.2021--------------
Since weekly 21.5.20, we are releasing TWRP version of our ROMs for MI11...
TWRP install via fastboot command
Code:
fastboot boot twrp.img
To change TWRP language to English, press bottom right button and select English..
TWRP for MI11 venus
For install ROM, just select in TWRP - Install - ROM zip - reboot
Enjoy..
Thanks for the ROM. Once my bootloader is unlocked I'll flash the ROM and report it.
Stupid question but EU network band work as it should ? L1 certificate? What about Google pay?
Lione2 said:
Stupid question but EU network band work as it should ? L1 certificate? What about Google pay?
Click to expand...
Click to collapse
all OK..
My xiaomi 11 still waitong for boatloader unlock 168 hours, will try it once unlocked
Is root possible?
I will try it in 6 days too.
pittrich said:
Is root possible?
Click to expand...
Click to collapse
use magisk patch boot.img, then flash it.
ingbrzy said:
Click to expand...
Click to collapse
Thx Master ! will try
ingbrzy said:
How to install Xiaomi.eu ROM for Xiaomi MI 11
We will release fastboot ROM versions until TWRP for venus is released
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_MI11_21.1.13_v12-11
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file WEEKLY or STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
Click to expand...
Click to collapse
Hi, will Google Pay work on this ROM with unlocked bootloader?
I have a Mi11 with a preliminary Global ROM but it's rooted and unlocked and GPay does not allow me to add cards. I managed to unroot (removing /system/xbin/su) but GPay still does not allow me to add cards, so I believe it's the unlocked bootloader.
Is there a way to lock bootloader safely?
I have MiFlash but I've heard that flashing ROM with clear and lock option may brick device.
Thanks
İs there turkish language
google pay works
deepblue2000 said:
google pay works
Click to expand...
Click to collapse
How is this possible?
I understood that GPay would not work with unlocked bootloader...
As I said, I have a Mi11 with a MIUI 12 test build: the ROM is rooted and bootloader is unlocked, I managed to delte root removing "system/xbin/su" but Gpay still refuses to add cards
I just unlocked bootloader, no root ! with root it never worked.
SafetyNet passes
GooglePay is working (added Paypal)
deepblue2000 said:
google pay works
Click to expand...
Click to collapse
How is this possible?
I understood that GPay would not work with unlocked bootloader...
As I said, I have a Mi11 with a MIUI 12 test build: the ROM is rooted and bootloader is unlocked, I managed to delte root removing "system/xbin/su" but Gpay still refuses to add cards
deepblue2000 said:
I just unlocked bootloader, no root ! with root it never worked.
SafetyNet passes
GooglePay is working (added Paypal)
Click to expand...
Click to collapse
Could it be that for test ROM that I have, which comes already rooted, even if I remove manually root, something remains in the system that make safetynet not pass?
maybe that there are some root files or something...
you can try, if you install the xiaomi.eu rom with full wipe/format data.
deepblue2000 said:
maybe that there are some root files or something...
you can try, if you install the xiaomi.eu rom with full wipe/format data.
Click to expand...
Click to collapse
I have two units, so will keep one with official global test build and will flash he other with xiaomi.eu
Is xiaomi.eu working fine? Any drawback? Is iit based on MIUI 12.5?
for me iit works amazingly well !!!
no problems so far. everything is smooth and fast.
yes it is Miui12.5 based
deepblue2000 said:
for me iit works amazingly well !!!
no problems so far. everything is smooth and fast.
yes it is Miui12.5 based
Click to expand...
Click to collapse
Ok, on device 1 I reflashed MIUI 12 test build, I removed root manually, root checker says I am not rooted but safetynet checker fails, maybe because it's not an officially approved Google ROM yet and it's stil an internal XIAOMI test build... After all XIAOMI engineer told me that if I lock the bootloader phone will even stop working (and that is why my 3rd sample got stuck in fastboot: will have to unlock now...)
Will test xiaomi.eu on device 2
How to install Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra
We will release fastboot ROM versions until TWRP for star/mars is released TWRP RELEASED
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update your stock ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file BETA or STABLE
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file WEEKLY or STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
-----------EDIT 20.5.2021--------------
Since weekly 21.5.20 and Stable 12.5.7.0, we are releasing TWRP version of our ROMs for MI11Pro/Ultra..
TWRP install via fastboot command
Code:
fastboot boot twrp.img
To change TWRP language to English, press bottom right button and select English..
TWRP for MI11Pro/Ultra mars/star
For install ROM, just select in TWRP - Install - ROM zip - reboot
Enjoy..
ingbrzy said:
How to install Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra
We will release fastboot ROM versions until TWRP for star/mars is released
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update your stock ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file BETA or STABLE
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file WEEKLY or STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
Click to expand...
Click to collapse
Thank you, for sure will make a donation as I've used few iterations of XIaomi EU already. Just one question. Will 5G work? As previously some users were reporting that after flashing to Xiaomi.eu it didn't.
5G is shown only when device is using 5G network.. not just when 5G coverage detected like in China ROM..
screenshot from China ROM "Fake 5G".. showing 5G but connected to 4G/LTE..
Deleted
Once I flashed the xiaomi.eu rom on my Mi 10 ultra I never managed to get 5G again, so it wasn't just when it wasn't being detected. This was reported by others so will wait to see what others say before I do mine this time.
ingbrzy said:
5G is shown only when device is using 5G network.. not just when 5G coverage detected like in China ROM..
screenshot from China ROM "Fake 5G".. showing 5G but connected to 4G/LTE..
Click to expand...
Click to collapse
I think its not the case for example in our subway there is only 5G coverage, so with china rom i have 5G and everything works perfectly but on xiaomi.eu i have no signal.....
Is there any point in installing this rom when global stock rom is available to flash over the CH version?
pafc66 said:
Is there any point in installing this rom when global stock rom is available to flash over the CH version?
Click to expand...
Click to collapse
I heard many opinions about the advantage of xiaomi.eu over global rom but I would also like to know what to do, because I would like to change the rom immediately after unlock
kuba319 said:
I heard many opinions about the advantage of xiaomi.eu over global rom but I would also like to know what to do, because I would like to change the rom immediately after unlock
Click to expand...
Click to collapse
I just installed the eu rom about for about 4 hours age and every thing seen fine. You can just follow the above youtube to install it very easy no problem at all!
Is this ROM working on the Chinese-only Mi 11 Pro?
overdom said:
Is this ROM working on the Chinese-only Mi 11 Pro?
Click to expand...
Click to collapse
I believes so!
There's posts in the xiaomi.eu forum saying they now have the same issue with the Mi 11 Ultra. As soon as they use the xiaomi.eu rom, they lose 5g.
deleted
veimus said:
Here you have explanation why is that happening: https://forum.xda-developers.com/t/...-xiaomi-mi-11-pro-ultra.4260617/post-84817831
Click to expand...
Click to collapse
I'm not sure I agree. In the same places where 5G worked with the CN rom, I got 4g speeds with the xiaomi.eu rom, 5G just didn't work once I'd flashed it. Others all had the same issue.
chistery said:
I'm not sure I agree. In the same places where 5G worked with the CN rom, I got 4g speeds with the xiaomi.eu rom, 5G just didn't work once I'd flashed it. Others all had the same issue.
Click to expand...
Click to collapse
I will test my phone with that 5G, if I have 5G network in my area to see what the story with that.
Global ROM also loose 5G ?
wching02 said:
I just installed the eu rom about for about 4 hours age and every thing seen fine. You can just follow the above youtube to install it very easy no problem at all!
Click to expand...
Click to collapse
can you post screenshot from About phone screen? thank you
It looks like latest xiaomi.eu version for Mi 11 Ultra fixed some 5G related issues . If they are related to 5G connectivity for China Version , that would be brilliant .
Good day,
I am trying to get my phone out of fastboot loop.
My device is CN version. Here are the steps I have done.
- bootloader is unlcoked
- tried flashing EU stable and weekly rom
- tried MiFlash tool to flash a stock CN rom.
All ended up in fastboot loop. Anyway I can revive my device?
Thank you for your help.
Machine_Head said:
Good day,
I am trying to get my phone out of fastboot loop.
My device is CN version. Here are the steps I have done.
- bootloader is unlcoked
- tried flashing EU stable and weekly rom
- tried MiFlash tool to flash a stock CN rom.
All ended up in fastboot loop. Anyway I can revive my device?
Thank you for your help.
Click to expand...
Click to collapse
seems only via EDL mode..
Thank you. I will learn how to do it.
This Guide is intended for OP7 Pro Devices that are already running Android 11 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the 11.0.1.2 OTA package.
INSTRUCTIONS
MAKE SURE you flash the correct boot image. Only flash the boot image of the OOS version you are running or you will have boot issues.
Install the latest Magisk Manager on your device if it is not already installed.
Download the patched boot image that matches your current OOS version from below.
Copy the downloaded image to your fastboot directory.
To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
11.0.1.2
magisk-patched-OOS-11.0.1.2-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
11.0.1.3
magisk_patched-boot-11.0.1.3.img
MD5: 26864b63727bba2c64ac929838d11f08
11.0.1.4
magisk-patched-boot-11.0.1.4.img
MD5: 0e6767c739b9cbf9e99562d01472d9c0
11.0.1.5
Due to problems updating and 11.0.1.5 being an incremental update, this image is not available
11.0.1.6
magisk_patched_boot_11.0.1.6.img
MD5: 765319532315e6a7a442b7bdaf2dfa57
stock_boot_11.0.1.6.img
MD5: eed8d7a8e338400f5b57fea41aae5a73
11.0.1.7
Incremetal Update - No Boot Image Available
11.0.1.8
magisk_patched_boot_11.0.1.8.img
MD5: bb820d2cde0f6dae11fc32d233aecf60
stock_boot_11.0.1.8.img
MD5: ffddf17538204f85ee98e1f805a4e103
I will continue to release these for future OTA's. I don't monitor TMO release dates, I just wait for the OTA notification on my phone so it may take longer for me to find out there is an update.
Feel free to PM me when a new update is pushed out.
weakNPCdotCom said:
This Guide is intended for OP7 Pro Devices that are already running Android 11.0.1.2 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the latest OTA package.
INSTRUCTIONS
Install Magisk Manager v23 on your device if it is not already installed.
Copy "magisk-patched-OOS-11.0-boot.img" to your fastboot directory. To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
magisk-patched-OOS-11.0-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
RELATED THREADS
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
Click to expand...
Click to collapse
Thanks for this very helpful thread. can you please provide me with both stock boot.img and patched boot image for European GM1913 running OS 11.0.1.1 GM21BA ? I have the stock image but won't boot if patched with latest magisk I've been trying for days (Also Tried Canary)
stuntora said:
Thanks for this very helpful thread. can you please provide me with both stock boot.img and patched boot image for European GM1913 running OS 11.0.1.1 GM21BA ? I have the stock image but won't boot if patched with latest magisk I've been trying for days (Also Tried Canary)
Click to expand...
Click to collapse
Im sorry but I only work with T-Mobile devices. I don't have any other firmware on hand and I do not have any way of testing things for other devices. How are you patching the boot image?
weakNPCdotCom said:
Im sorry but I only work with T-Mobile devices. I don't have any other firmware on hand and I do not have any way of testing things for other devices. How are you patching the boot image?
Click to expand...
Click to collapse
extracted the boot.img from payload.bin with python.
patched the extracted img with the latest magisk 23.0
flash the patched img with fastboot to both slots a and b
fastboot reboot aaaaaaaaand voila a nice bootloop
***********
solution
adb reboot bootloader
reflash stock img to slots a and b
fastboot reboot aaaaaaaaand voila a nice phone with no root hahaha
stuntora said:
extracted the boot.img from payload.bin with python.
patched the extracted img with the latest magisk 23.0
flash the patched img with fastboot to both slots a and b
fastboot reboot aaaaaaaaand voila a nice bootloop
***********
solution
adb reboot bootloader
reflash stock img to slots a and b
fastboot reboot aaaaaaaaand voila a nice phone with no root hahaha
Click to expand...
Click to collapse
does the device boot normally if you flash the unmodified boot image that you extracted?
are you using Magisk Manager to patch the boot image?
weakNPCdotCom said:
does the device boot normally if you flash the unmodified boot image that you extracted?
are you using Magisk Manager to patch the boot image?
Click to expand...
Click to collapse
yes, absolutely, the phone boots normally if reflashed with the unmodified boot image. and also yes I use Magisk Manager to select and patch the aforementioned image that can be found in the download folder.
stuntora said:
yes, absolutely, the phone boots normally if reflashed with the unmodified boot image. and also yes I use Magisk Manager to select and patch the aforementioned image that can be found in the download folder.
Click to expand...
Click to collapse
after a little searching, I have found some other people reporting bootloops with magisk that are caused by incompatible modules being installed.
if you had modules installed previously, you can remove them using adb shell.
Code:
adb wait-for-device shell magisk --remove-modules
It's not clear if you need to have magisk on the device first or not, but I would try this method to remove any installed modules, flash the patched boot image again, and see if that helps.
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
justencase6 said:
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
Click to expand...
Click to collapse
Can you provide a link or some context to help the rest of us get twrp working?
justencase6 said:
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
Click to expand...
Click to collapse
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
weakNPCdotCom said:
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
Click to expand...
Click to collapse
So how do u think I pulled the OTA 11 tmobile version, been away for a bit. I'll find the copy I have been using.
A way to get twrp and not loose it, wile in twrp android 10 going to 11.flash the 11 package right after flash the latest twrp check if in A or B then reboot recovery do the same to the other slot.the stock packs have there own recovery this will help maintain twrp.
weakNPCdotCom said:
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
Click to expand...
Click to collapse
If this is not enough prof then message me
11.0.1.3 boot image has been added to OP
justencase6 said:
If this is not enough prof then message me
Click to expand...
Click to collapse
oh, you are decrypted. I would rather not have to do that. also, you are running GM21AA but TMO is GM31CB.
In Nebrassy's repo we are one of a few that aren't supported
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a gm1915, it still has the sim lock on it. I just been able to change from 18831 to 18821. Use *#391# to switch to India.
Also I know how to generate the qr code to decrypt in the *#*#5646#*#* just need imei to generate the code
who can explain me step by step please i did not understand correctly i downloaded the file 11.0.1.3 and i dont know what to do next
weakNPCdotCom said:
This Guide is intended for OP7 Pro Devices that are already running Android 11.0.1.2 or 11.0.1.3 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the 11.0.1.2 OTA package.
INSTRUCTIONS
MAKE SURE you flash the correct boot image. Only flash the boot image of the OOS version you are running or you will have boot issues.
Install Magisk Manager v23 on your device if it is not already installed.
If you are on 11.0.1.2, copy "magisk-patched-OOS-11.0.1.2-boot.img" to your fastboot directory.
If you are on 11.0.1.3, copy "magisk_patched-boot-11.0.1.3.img" to your fastboot directory.
To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
magisk-patched-OOS-11.0.1.2-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
magisk_patched-boot-11.0.1.3.img
MD5: 26864b63727bba2c64ac929838d11f08
RELATED THREADS
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
Click to expand...
Click to collapse
Which fastboot directory are you talking about?
Thank you for this guide.
Can you make an OTA Update patched for Tmobile ? GM1915
Hi, I've unlocked the bootloader on my new Xiaomi Redmi Note 10 Pro because I like to have apps like adaway and macrodroid which need root access. I've rooted previous phones before but I'm far from an export on it. It's been a while since I have a new phone and had to figure it all out again. Anyway, I've messed up and I hope someone can help me out. I'll try to explain every step I did to make it easier to troubleshoot.
After unlocking, I installed Magisk Manager (the apk file) and got boot.img from a Miui zip. I did not realize I needed to use the EU version of Miui nor did I see that I have "sweet" instead of "mojito" so I got the latest mojito Global rom from here, thinking that would be fine. I let Magisk modify the boot.img and rebooted into fastboot. I flashed the modified boot.img and I also flashed OrangeFox as a recovery. After a reboot the phone got stuck on a fastboot loop so I figured I did something wrong.
After quite some research I came to the conclusion I used the wrong rom (global instead of EEA). So I found the EEA Miui rom and flashed that boot.img using fastboot. I was able to get back into the system. I let Magisk modify the new boot.img and flashed that again with fastboot. This ended up in a fastboot loop again so I flashed the previous boot.img again. At this point I came to the conclusion there was a "mojito" and a "sweet" version and I was trying to flash "mojito" rom on a "sweet" phone. Anyhow I found the "sweet" EEA rom and redid the previous steps. The phone does boot into system now, but wifi isn't working anymore. When I try to toggle it on, it just says "turning on" but it never switches on. I think I messed up some modem driver by flashing the other roms but I can't seem to fix it.
I saw somewhere that I could try to use flash_all.bat which is located in the fastboot roms, but this only gave errors talking about current antirollback version being higher than the package. It didn't matter which version of the package I used, so I gave up on this route quite quickly.
I assumed there was still something wrong with the rom so I went into OrangeFox and wiped everything. If I try to use OrangeFox to install any Miui zip, it fails without any useful message. The only zip I was able to install was OrangeFox itself which I only tried because I was thinking it might was OrangeFox that was f'ed up. I've added a pic of the error. This was with EU firmware from here which I found through the Pixel OS thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyhow, I was hoping flashing a different rom like PixelOS might fix the problem but OrangeFox refused to install any zip apart from it's own.
I hope someone can point me in the right direction because I'm starting to see less and less possible solutions. It's a brand new phone so there is no data on it that I need to save. Also, I was not able to find that V12.5.8.0.RKFEUXM version anywhere. It's either v13 something of V12.5.7.something.
In desperation I decided to download about 10 different versions and try them one by one in OFox. Ranging van V12.5.3.0.RKFEUXM up to the latest and to my surprise, the zip voor V12.5.7.0 actually worked and installed. The phone kept coming back to OFox though, so I wiped everything, did another format, went into fastboot and flashed the boot.img from that zip, did another format and behold, I got into system again and wifi was actually working again!
Anyhow from that point forward I simply installed Magisk again, let it modify the boot.img, flashed the modified boot.img, wiped and formatted in OFox and rebooted. Now I'm finally able to start configuring the phone as I wanted to do hours ago.. Although... I might retry flashing a later version again just to test since I'm not actively using the phone yet.
DeMetaal said:
In desperation I decided to download about 10 different versions and try them one by one in OFox. Ranging van V12.5.3.0.RKFEUXM up to the latest and to my surprise, the zip voor V12.5.7.0 actually worked and installed. The phone kept coming back to OFox though, so I wiped everything, did another format, went into fastboot and flashed the boot.img from that zip, did another format and behold, I got into system again and wifi was actually working again!
Anyhow from that point forward I simply installed Magisk again, let it modify the boot.img, flashed the modified boot.img, wiped and formatted in OFox and rebooted. Now I'm finally able to start configuring the phone as I wanted to do hours ago.. Although... I might retry flashing a later version again just to test since I'm not actively using the phone yet.
Click to expand...
Click to collapse
Use MiFlashTool.
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
BigChungus321 said:
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
Click to expand...
Click to collapse
Thanks a lot for this info! I did not know most of what you said so this helps a bunch.
So could me using this older OFox be the reason why I can't update to Miui 13? Because I now have a working Miui 12.5.7 on the phone and it says theres an update for Miui 13 but once thats downloaded and the phone reboots, it boots into OFox but doesn't actually install anything. Also I cant install the downloaded Miui13 zip which is, as far as I can tell, the same as the one the phone tries to download when pressing the update button.
I'll go look into this newer OFox or perhaps TWRP to see if that changes things. I've used TWRP before but switched at some point. I can't remember why.
BigChungus321 said:
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
Click to expand...
Click to collapse
Thanks mate! Your words might not mean much to you but you helped me out big time!
I installed the latest TWRP because I couldn't find OFox12 for this specific phone. So I used TWRP to install the Miui 13 zip I had previously downloaded and it worked flawlessly. Now I can finally start configuring the phone and start using it. Your message is much appreciated!
https://deac-fra.dl.sourceforge.net/project/orangefox-releases/sweet/OrangeFox-R12.1_3-Unofficial-sweet.zip
Just in case for next time u might wanna brick ur phone.
aLcaTr4z said:
https://deac-fra.dl.sourceforge.net/project/orangefox-releases/sweet/OrangeFox-R12.1_3-Unofficial-sweet.zip
Just in case for next time u might wanna brick ur phone.
Click to expand...
Click to collapse
Haha thanks. TWRP did the job though so I'll probably stick with that for now.