Database Develop

[Guide][Gsi]HOWTO flash any gsi with redmi 6 pro (sakura)

{
"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"
}
* Disclaimer :
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite​
PLEASE READ CAREFULLY TO AVOID PROBLEMS
First of all u need an unlocked bootloader guide
Second of all u need adb fastboot
third of all u need is TWRP (works same with unofficial redwolf recovery)
here is a list of all gsi (for redmi 6 pro we need arm64 Aonly) all android 9 gsi support the notch
1. im on stock 8.9.20 !!! BUT ALWAYS USE LATEST FASTBOOT ROM BECOUSE OF ANTIROLLBACK!!! miflash link
2. then i reboot the device into fastboot mode (volume down + power, or adb command: adb reboot bootloader), and boot into twrp dont install it , with the command
Code:
fastboot boot twrpname.img
3. next step is to wipe data , write yes and format it.
4. then install globerom from here with magisk with expert settings https://mi-globe.com/rom-builder-features/?codename=sakura&img=redmi6pro.png&realname=RedMi+6+Pro with the LOADED TWRP (expert settings howto)
5. Then the device will boot into miui mi_globerom (can take alsmost 15-20mins, no joke) just wait until it hast booted.
6. then reboot into fastboot mode and again BOOT TWRP with
Code:
fastboot boot twrpname.img
7. wipe data again (write yes in twrp) like in step 3
8. then install the gsi image to system partition
9. reboot into system swipe yes if twrp says no system installed , and u will boot into the gsi of your choice,
10. then reboot into fastboot mode , boot twrp again with command:
Code:
fastboot boot twrpname.img
11. then finally install twrp image from your phone with the booted twrp . (dont forget to install img. not zip)
12. boot into installed twrp, install gapps, make a factory reset swipe, and boot into rom and make initial rom setup.
13. for magisk, again boot into twrp and flash,magisk , then reboot
for testing other gsi, 1. goto twrp, 2. wipe, 3. advanced wipe, and just wipe: system , chache, dalivik chache, and data , and install the next gsi to system partition
to revert back to stock flash fastboot rom (like this so u dont relock the bootloader) with miflash DONT RELOCK BOOTLOADER http://bigota.d.miui.com/8.9.20/sakura_images_8.9.20_20180920.0000.00_8.1_cn_840c43e70e.tgz !!!!BUT ALWAYS USE LATEST FASTBOOT ROM BECOUSE OF ANTIROLLBACK!!!!!
have fun and consider join us on telegram https://t.me/redmi6proofficial

placeholder

Looks like i got some questions for ya...
first, cant we use a normal developer rom issued by xiaomi and then flash magisk?
second, in 'fastboot boot twrpname.img' the "twrpname" is a variable right?
third, you did all the starting steps(untill loading the gsi) using remote twrp boot( just made the phrase myself), why not flash the image from the start? will something be different?(like system crash or phone bricking)
fourth, In the start you told "then i reboot the device into fastboot mode (volume down + power, or adb command: adb reboot bootloader), and boot into twrp dont install it , with the command" from where exactly did you boot the TWRP of? from the phone or your PC? (srry, am not well educated in this method)
fifth, it is irrelevant(not completely) but, will using the recovery rom instead of fastboot brick the user's phone?
sixth, about the gsi roms, you said arm64 A only, will there be a problem with flashing the roms with that A-A/B (partition style{ e.g. Pixel Experience}) and arm-arm64 (architecture{e.g. Pixel Experience})

Astrek said:
Looks like i got some questions for ya...
first, cant we use a normal developer rom issued by xiaomi and then flash magisk?
second, in 'fastboot boot twrpname.img' the "twrpname" is a variable right?
third, you did all the starting steps(untill loading the gsi) using remote twrp boot( just made the phrase myself), why not flash the image from the start? will something be different?(like system crash or phone bricking)
fourth, In the start you told "then i reboot the device into fastboot mode (volume down + power, or adb command: adb reboot bootloader), and boot into twrp dont install it , with the command" from where exactly did you boot the TWRP of? from the phone or your PC? (srry, am not well educated in this method)
fifth, it is irrelevant(not completely) but, will using the recovery rom instead of fastboot brick the user's phone?
sixth, about the gsi roms, you said arm64 A only, will there be a problem with flashing the roms with that A-A/B (partition style{ e.g. Pixel Experience}) and arm-arm64 (architecture{e.g. Pixel Experience})
Click to expand...
Click to collapse
1. i didnt try that to be honest thats the way after so many tries to get it working,.. lost a day of my life and dont wanna do that again to test but its a valid point , will try later and if so edit the guide
2.yes easiest way is to write the command: fastboot boot and then drag and drrop the twrp image in the powershell window so u have the correct filepath
3.yes its like a remote twrp (in fact it doesnt get installed into recovery partition, it runs in your phone memory in backgrround ) becouse it doesnt work to install the twrp since miui doesnt "allow" that and android cant start ..so no u cant install twrp only install like mentioned
4.see above ..the phone boots the twrp
5.i was scared too to hell about bricking: so in short DO NOT INSTALL ANY MIUI VERSION ABOVE THE VERSION U ARE CURRENTLY USING latest now is 8.9.20 ... and 8.9.20 means 20.9.2018 all miui versions are like that so dont downgrade thats all
6.it will not boot thats all , but i would not try it ... its easy, all gsi roms have a Aonly arm64 build so just download that and there are no A-A/B its either A or A/B some times A is called Aonly , and there is arm and arm64 . we need arm64 A
its no problem to ask questions we all where new to this at some point just ask here or with a more quicker respond on the telegram group https://t.me/redmi6proofficial and ask for nofx161

thnx for the help... will root my phone once the MI countdown stops... once again thnx a lot and pls do keep up the good work.. really appreciate it!

Im on global 9.6.4 stable..which one should i download from globe rom?
Also im rooted using magisk..will that pose any problem?

loseyourself said:
Im on global 9.6.4 stable..which one should i download from globe rom?
Also im rooted using magisk..will that pose any problem?
Click to expand...
Click to collapse
there is no global rom for this device for now, only chinese or indian , i would recommend updating to miui 10 by ota or fastboot rom, and if u are on miui 10 u can do the same as stated in the guide above

Can we flash Mi A2 lite's stick Rom turning this ohone into one

AndroidAnand28 said:
Can we flash Mi A2 lite's stick Rom turning this ohone into one
Click to expand...
Click to collapse
NO DONT FLASH MIA2lite ROM , mi A2 lite has a different partiton sceme

nofx161 said:
NO DONT FLASH MIA2lite ROM , mi A2 lite has a different partiton sceme
Click to expand...
Click to collapse
Well then like the Mi 5X to Mi A1, we can't turn our phone to Android One

Is it possible to flash stock unrooted aosp on this device? I'm considering buying but don't want MIUI and need unrooted for corporate device management etc

BazmanFoo said:
Is it possible to flash stock unrooted aosp on this device? I'm considering buying but don't want MIUI and need unrooted for corporate device management etc
Click to expand...
Click to collapse
u can use any gsi, all are without root, only some have a rooted version too so would be no problem, but there is the same device with android one instead of miui, it is called mi a2 lite.

nofx161 said:
u can use any gsi, all are without root, only some have a rooted version too so would be no problem, but there is the same device with android one instead of miui, it is called mi a2 lite.
Click to expand...
Click to collapse
Perfect, thanks mate

I am on MIUI 10(Chinese Stable Version).
Can I skip instilling the global rom?
And…Which step should I do?
---------- Post added at 02:33 AM ---------- Previous post was at 02:23 AM ----------
Can I just flash(not boot) TWRP Recovery then ADVANCED WIPE then install the IMG File then reboot?

Rom Recommendations
Thanks for the guide.
I wanted to ask if you installed any P roms as daily drivers and which of them were the most stable and bug free for day to day use.
TIA

@nofx161
I am currently at v 9.6.5.0 (indian rom) latest version
What is the reason to flash global rom in steps (4 & 5) here in this tutorial?
Sent from my ONEPLUS A5010 using Tapatalk

vistaholylight said:
I am on MIUI 10(Chinese Stable Version).
Can I skip instilling the global rom?
And…Which step should I do?
---------- Post added at 02:33 AM ---------- Previous post was at 02:23 AM ----------
Can I just flash(not boot) TWRP Recovery then ADVANCED WIPE then install the IMG File then reboot?
Click to expand...
Click to collapse
just use the guide and do the same as in the guide there is no other way to get a usable gsi if u dont belive me then just try ,.. u will end up in a bootloop nothing more.

l2o88j said:
@nofx161
I am currently at v 9.6.5.0 (indian rom) latest version
What is the reason to flash global rom in steps (4 & 5) here in this tutorial?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
i dont know the reason why we need that steps , but i was unable to get a working gsi without those steps

nofx161 said:
just use the guide and do the same as in the guide there is no other way to get a usable gsi if u dont belive me then just try ,.. u will end up in a bootloop nothing more.
Click to expand...
Click to collapse
I know. Thanks!
---------- Post added at 01:21 AM ---------- Previous post was at 12:44 AM ----------
nofx161 said:
just use the guide and do the same as in the guide there is no other way to get a usable gsi if u dont belive me then just try ,.. u will end up in a bootloop nothing more.
Click to expand...
Click to collapse
And I am on MIUI 10.0.5.0 STABLE. Which rom should I flash in step 4?

nofx161 said:
just use the guide and do the same as in the guide there is no other way to get a usable gsi if u dont belive me then just try ,.. u will end up in a bootloop nothing more.
Click to expand...
Click to collapse
And in the guide you said "ALWAYS USE LASTEST FASTBOOT ROM BECAUSE OF ANTIROLLBACK".
What does "fastboot rom" mean?
Is my stable 10.0.5.0(Latest Stable Version ) up to standard?

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

[ROM][13.0][OnePlus8T] PixelExperience [AOSP/UNOFFICIAL] - JUNE 24, 2023

YOU MUST HAVE STOCK OOS13 INSTALLED ON BOTH SLOTS TO AVOID TOUCH SCREEN ISSUES. IF YOU ARE ON A11 or A12, THEN UPDATE TO A13. IF YOU ARE ON A13 then you are good to flash this already. Use copy partions if you want to make sure firmware is on both slots.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
YOU MUST BE ON STOCK ANDROID 13 ON BOTH SLOTS FOR IT TO WORK PROPERLY. IF NOT, THEN UPDATE TO A13.
THANKS TO THE ENTIRE PE TEAM FOR HAVING THEIR SOURCE AVAILABLE FOR USE!!!
What's working?
You tell me
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
DOWNLOAD ROM & RECOVERY FILES HERE
Put recovery files in same folder as your fastboot or platform tools folder.
Install instructions also located here.​
Android OS version: 13.0​
Security patch level: June 2023​
Device Source code: https://github.com/PixelExperience-Devices​
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250​
Source code: https://github.com/PixelExperience​
ROM Developers: jhenrique09, Broly
Maintainer: TheSayaMan
XDADevDB Information
PixelExperience A13 ROM for OnePlus 8t Kebeb
REBOOT TO BOOTLOADER
fastboot -w​fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash recovery recovery.img
Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
adb sideload PixelExperience-Plus-kebab-WEEKLY-13.0-20230624-UNOFFICIAL.zip
REBOOT TO SYSTEM TO SETUP. IF YOU WANT ROOT, THEN BOOT BACK TO RECOVERY AND ADB SIDELOAD MAGISK
adb sideload magisk.apk or rename magisk.apk to magisk.zip and adb sideload magisk.zip
IF YOU ARE ALREADY ON PREVIOUS UPDATE, YOU CAN DIRTY FLASH NEW UPDATE. REBOOT TO BOOTLOADER.
IN RECOVERY, SIMPLY ADB SIDELOAD NEW UPDATE.
UPDATES ARE INSTALLED TO INACTIVE SLOT IN CASE OF INSTALL ISSUE, YOU CAN REVERT BACK TO PREVIOUS BOOTABLE SLOT.

Oos12 or oos13 based ?

i try flash on oos13.

diegots said:
Oos12 or oos13 based ?
Click to expand...
Click to collapse
I have tested on 13. No idea if it will work on 12. It definitely will not work on 11.

vallobrescia said:
i try flash on oos13.
Click to expand...
Click to collapse
It will work fine

TheSayaMan said:
It will work fine
Click to expand...
Click to collapse
which recovery did you use? is the twrp from the official site ok?

Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)

SaigoW said:
Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)
Click to expand...
Click to collapse
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.

vallobrescia said:
which recovery did you use? is the twrp from the official site ok?
Click to expand...
Click to collapse
Yes twrp is fine or if your on another custom rom, you can use that one as well. I will post a recovery for this when I can.

TheSayaMan said:
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.
Click to expand...
Click to collapse
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ

logan_007 said:
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ
Click to expand...
Click to collapse
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.

does this one work better or the one on the official site?

TheSayaMan said:
Sì twrp va bene o se sei su un'altra rom personalizzata, puoi usare anche quella. Pubblicherò un recupero per questo quando posso.
Click to expand...
Click to collapse
Good job, I'll run this thread right.

TheSayaMan said:
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.
Click to expand...
Click to collapse
I use Pixel Experience recovery to flash the rom.
I flashed in the official Oxygen OS 13 version，It booted fine and everything works fine.
and then unlocked the OEM, extracted the Pixel Experience 13 recovery and then flash into this Pixel Experience recovery.
Also follow the tutorials to flash the rom
(https://wiki.pixelexperience.org/devices/kebab/install/)
After the first boot devices,the screen touch is not working.
{
"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"
}
Then I followed your instructions and the screen touch did not work either.
-----
I use the same way flash, PE ROM 12 is everything works, and I have used it for half a year.
Also I can't use twrp,I can't use twrp since android 11, even though I flashed in the latest version, it can't decrypt my data correctly and can't identify my data correctly. Maybe it's just a problem with my phone.
So I can't flash the PE rom via twrp either
just now I went to test the latest version of LineageOS android 13, also following the official tutorial to use LineageOS recovery to swipe in, and found the same problem, normal boot up, the result is the same as PE rom is on the new user guide page, the screen touch does not work.
---
I haven't seen too many people report this kind of problem, I think there may be some strange problems with my phone. TAT

vallobrescia said:
does this one work better or the one on the official site?
Click to expand...
Click to collapse
The official hasn't updated the security patch yet.

Thread updated with recovery install instructions.

Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?

M_Power01 said:
Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?
Click to expand...
Click to collapse
It's a known problem. I switched to Nova Launcher and then disabled that.

No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.

Dior DNA said:
No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.
Click to expand...
Click to collapse
Although this is Android 13. It's based on Android 12 so you must have a12 on both slots for it to work properly. Sorry for the confusion. I have updated the instructions, sorry.

How To Guide [GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Windows-Only]

XIAOMI.EU ROMs Flashing Guide:
MIUI 13 (Stable)
{
"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"
}
Requirements:
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers, android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of c: drive and connect your device to fastboot mode and double click on flash_all.bat
A cmd window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the.eu rom zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select eu rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to system.
Done.
Updating via Updater app: (ROM Type: Recovery)
(A Xiaomi.eu ROM must already be installed on your device)
Download Xiaomi.eu ROM zip file
Copy the ROM zip file to the internal storage
Updater -> Menu (...) -> Select update package
Select the ROM zip file
Confirm any dialogs
Done!
Installing with Fastboot: (ROM Type: Fastboot)
Download Xiaomi.eu ROM zip file
Extract the ROM zip to root of c : drive.
Connect phone ins fastboot to PC via USB cable
Run one of the installation scripts (according to your PC operating system):
- first_install_with_data_format - with data wipe, if you're flashing Xiaomi.eu ROM for the first time or downgrading.
- update_rom - without data wipe, if you're updating from an older Xiaomi.eu ROM.
Done!
Remember:
If you are going from MIUI 13 (or later) Weekly ROM to MIUI 13 Stable ROM, you are doing a downgrade, so format data is mandatory!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MIUI 13 (Weekly)
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of c: drive and connect your device to fastboot mode and double click on flash_all.bat
A cmd window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of c: drive.
Go into folder.
Run fastboot installation script in folder 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
Done.
NOTE FOR ALL:
Make sure to always extract and move the stock rom folder in root of c: drive (this helps avoid flashing errors)The path should look something like this:
C:\spes_global_images_YourVersionhere
Also make sure the same to unzip xiaomi.eu rom folder in the root of c: drive:
C:\xiaomi.eu_multi_HMNote11_YourVersionHere
Then flash Xiaomi.EU according to instructions above.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Must do all the process again if flashing a new rom
If you get a error like this: assert failed _dynamic partitions package_extract_file(dynamic_partitions_op_list) ERROR 1
Then go to the guide here and re do all the steps in the guide and when it comes to flashing twrp, then use twrp 3.6.1 to flash rom then flash twrp 3.7.0 according to the process in guide (if the rom you flashed is a12/a13) or use shrp 3.1 instead of using twrp after re doing all the steps and then flash rom.
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel is also integrated.

Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu

NOSS8 said:
Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu
View attachment 5820261
Click to expand...
Click to collapse
Updated ! Thanks !

what is your experience after flashing the ROM. The system eats 18GB of space (is this normal or just my phone?) and I don't know why and even though a lot of spam is going away with this rom there is a lot more

wasteoinc said:
what is your experience after flashing the ROM. The system eats 18GB of space (is this normal or just my phone?) and I don't know why and even though a lot of spam is going away with this rom there is a lot more
Click to expand...
Click to collapse
Did you do a clean flash?

NOSS8 said:
Did you do a clean flash?
Click to expand...
Click to collapse
I think I did, the phone was new and I did a fastboot install of the xiaomi.eu rom
But all this a/b system I don't pretend I get it much

wasteoinc said:
I think I did, the phone was new and I did a fastboot install of the xiaomi.eu rom
But all this a/b system I don't pretend I get it much
Click to expand...
Click to collapse
So you used first install.bat.
I don't have this device but on my 12 pro the system takes 13GB (Xiaomi Eu rom).

Does anybody have a lag issue in the control center? 90Hz feels like 60Hz

NOSS8 said:
Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu
View attachment 5820261
Click to expand...
Click to collapse
Big woop. I don't want stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
EDIT: changed supposed stock MIUI users on XDA (everyone) to proven (me).

Sheist! said:
Big woop. No one, including me, wants stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
Click to expand...
Click to collapse
This is your opinion but not that of the 781 users of this version, for example.

Sheist! said:
Big woop. I don't want stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
EDIT: changed supposed stock MIUI users on XDA (everyone) to proven (me).
Click to expand...
Click to collapse
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Why are you scared to flash magisk ?
Btw , are you getting issues in which your device randomly reboots (with animation) sometimes and apps crash unnecessarily ?
I have no nfc Indian 6 64 variant and I get this issue in all .eu roms for my device .
These issues are nowhere to be found in other custom roms .

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Where are you getting ads

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Magisk installs a bit funky with the RN11 since I stayed on the crDroid recovery. I recall I had to do the adb sideload method. Go under the Add Update section. You still need the boot.img and vbmeta.img from your installed ROM.

Sheist! said:
Magisk installs a bit funky with the RN11 since I stayed on the crDroid recovery. I recall I had to do the adb sideload method. Go under the Add Update section. You still need the boot.img and vbmeta.img from your installed ROM.
Click to expand...
Click to collapse
You could have chosen apply update chosen your SD card then flashed magisk.zip

LolFlasherNoob said:
You could have chosen apply update chosen your SD card then flashed magisk.zip
Click to expand...
Click to collapse
Actually, the recovery would not recognize the external SD. Nothing changed on it. I did freak a bit until the sideload worked from PC. Still won't read it in the stock crDroid 9.2 recovery but every other place it does.
Edit: it is just the recovery that fails to read it. Apps within system read it fine, and it mounts. "unsupported filesystem exfat" as seen in recovery. I did not format in exfat, though.

LolFlasherNoob said:
...
Btw , are you getting issues in which your device randomly reboots (with animation) sometimes and apps crash unnecessarily ?
I have no nfc Indian 6 64 variant and I get this issue in all .eu roms for my device .
These issues are nowhere to be found in other custom roms .
Click to expand...
Click to collapse
No I had no such issues , I have the version with NFC. I finally got magisk and adaware so now I will cool a bit before trying something different. LineageOS seems not supported anymore and from the other custom roms still not sure if you get more issues than miui.eu

Question Wifi no longer working after rooting (and making some mistakes)

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.