How To Guide Flashing GSI roms on Redmi Note 10S and then fixing some issues, all without any custom recovery

Search This thread

RandomAccessVemuri

New member
Sep 20, 2021
4
10
Redmi Note 10S
By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)

This guide will help you to flash any GSI (Project Treble) ROM onto your Redmi Note 10S, and since TWRP, or any custom recovery for that matter, is not yet available, we have to manually install the GSI roms using fastboot (and fastbootd because of the dynamic partition). The process is lengthy but not that difficult.

It should go without saying that you should backup everything and be prepared to lose your data and potentially soft-brick your phone and the experience with GSI roms is not always known to be stable (although I have not seen any such problems yet aside from a few easy-to-fix bugs) so do all of this at your own risk.

Important to note is that if at anytime you mess stuff up or delete partitions you weren't supposed to (whatever the guides may say, don't erase the product partition, it won't help, you're gonna end up in a bootloop) and soft-brick your phone, as long as you can access fastboot you can easily fix the problem by using the MiFlash tool which will help you get back to square one (you won't have to wait to unlock the bootloader again so don't worry about that)

Now, for the disclaimer:
DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....experienced to weigh in his/her opinions. If you end up bricking your phone or if things go south, I'm not responsible, that's on you.

NOTE:
When I mention fastboot I'm referring to the standard "normal" fastboot and when I mention fastbootd, I'm referring to the dynamic/userspace fastboot which is different (which wiil be indicated by the fastboot screens during either of the modes)

I should mention that using this method I have been able to flash DotOS, Android 12 Beta 5, CorvusOS (my current daily driver) and in my daily driver (Corvus OS), It's passing SafetyNet and the WideVine certification is still at L1 even after rooting, however I have tested neither Google Pay nor Netflix, because I don't use either of them so your mileage may vary, however I did find Netflix in the play store so that is a bit encouraging ig.

Alright, with the appetizers out of the way, let's crack on to the main course:

PART 0: Requirements:-

Please ensure that the following requirements are met:
  • A Redmi Note 10S with an unlocked bootloader
  • OEM Fastboot driver and Fastbootd driver is installed
  • A preferred GSI rom (the file extension should be .img)
  • Being prepared to lose your data
  • Obtain android platform-tools along with knowledge about how to use it
  • Acceptance that the newly flashed GSI rom may/may not be completely stable.
  • Fastboot rom from here
If you have all that, you can move on to the next step

PART 1: Get Straight to Flashin':

This guide is rather straightforward because there really isn't much to it.

To begin with, extract the vbmeta.img from the Fastboot rom. Once you have done that, reboot your phone to fastboot mode.
Once the phone is in fastboot mode, on your computer, run the following command:
Code:
fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
to disable what is the android equivalent of window's secure boot

Once that is done, issue the following command:
Code:
fastboot.exe reboot fastboot
(No, there is no typo here, this is what needs to be done to enter the fastbootd mode, which is where the real fun begins)

Ensure that you are in fastbootd mode. The blue coloured "fastboot" text at the bottom will be replaced by a yellow coloured "fastbootd"

Okay, now for the most important command, type:
Code:
fastboot.exe -u flash system your_gsi_rom_of_choice.img

Done!

After this, don't forget to factory reset your device by:
Code:
fastboot.exe -w

Note: If you forget to do the factory reset, you're gonna end up with a frankenstein combination of your new and some configs of your previous rom, in this case reboot to bootloader (using power and volume down) and issue the factory reset command (fastboot -w)

And then for the toppings:
Code:
fastboot.exe reboot

That's.....about it. You should boot into your chosen rom. For the first time, the boot animation may stick around for a long time (5 minutes or more). However, if, even after an absurd amount of time (15-20), the rom doesn't boot up, try using MiFlash tool to get back to square one and try the whole process again.

Once it boots up, continue with the setup process and you will (hopefully) be at the home screen of your new rom.

PART 2: Le Bugs

Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.

Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)

1. Disabled Headphone Jack:

Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot

Your phone will now reboot and once it does, you will see that the headphone jack is functioning normally again.

2. Brightness Slider Fix:

This one does not require any root. However, this does require that you can access the device specific customisations,

So, in my case, I had to go into {Device Name} Settings > Misc features and then tick the Force alternative backlight scale . Once you have done that, reboot and your brightness slider will be working properly again. Also, if you noticed sudden fluctuations after booting or when device goes to sleep earlier, that should all be fixed as well.


Conclusion:

At this point, you should be ready to rock the world along with your phone. Depending upon the rom you have chosen (DotOS for example), your widevine certification and safetynet may be compromised, even after trying out several fixes (which is what happened in my case). So if that happens to you, I suggest that you either change your rom, hunt around for some solutions or just, you know, live with it.
In my case, (As I mentioned before) I'm using CorvusOS where the widevine rating and safetynet are unaffected, with the latter requiring some special fixes.

Hope that helped. I look forward to hearing from you people about any recommendations or discussion. If you have any problem with the process or think that something may be wrong, post it in the replies and I'll be happy to get back to you (depending upon the time, of course)
 
Last edited:

miravision

Senior Member
Oct 5, 2021
285
182
How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?

Can you please fill the listing for our rosemary device on GSI wiki @ github?

 

J6idot

Senior Member
How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?

Can you please fill the listing for our rosemary device on GSI wiki @ github?

Better than stock, using gpu to render UI and powersave governor.
 

miravision

Senior Member
Oct 5, 2021
285
182

Pre-flash info:​

  • Device name: Xiaomi Redmi Note 10S (rosemary)
  • Earlier rom: MIUI 12.5.7 (India)
  • Rooted?: No

Tested images:​

  • Corvus OS
  • Android 12 Beta 5
  • DotOS

Steps to install​

Refer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/

Hardware Support post flashing​

ComponentComment
CameraWorks but Gcam is a little unstable
Speaker/MicWorks, headphone jack requires a tiny tweak
BluetoothNot tested but I'm sure it works
Wi-FiWorks
SIM/Mobile Data/ VoiceNot tested
VoLTENot tested
FingerprintWorks
NFCNot tested
Offline ChargingWorks
Display Refresh rate60hz (same as before)
Screen BrightnessWorks like before after a small tweak
Volume scaleWorks fine
5GN/A
SafetyNet post root?
:heavy_check_mark:
(requires modification)
WideVine certification post flash and rootL1 (requires modification)

Personal Notes:​

  • Battery life seems to have reduced a bit
  • Phone (extremely rarely) reboots out of nowhere.
  • Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
  • I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)
 
Last edited:

J6idot

Senior Member

Pre-flash info:​

  • Device name: Xiaomi Redmi Note 10S (rosemary)
  • Earlier rom: MIUI 12.5.7 (India)
  • Rooted?: No

Tested images:​

  • Corvus OS
  • Android 12 Beta 5
  • DotOS

Steps to install​

Refer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/

Hardware Support post flashing​

ComponentComment
CameraWorks but Gcam is a little unstable
Speaker/MicWorks, headphone jack requires a tiny tweak
BluetoothNot tested but I'm sure it works
Wi-FiWorks
SIM/Mobile Data/ VoiceNot tested
VoLTENot tested
FingerprintWorks
NFCNot tested
Offline ChargingWorks
Display Refresh rate60hz (same as before)
Screen BrightnessWorks like before after a small tweak
Volume scaleWorks fine
5GN/A
SafetyNet post root?
:heavy_check_mark:
(requires modification)
WideVine certification post flash and rootL1 (requires modification)

Personal Notes:​

  • Battery life seems to have reduced a bit
  • Phone (extremely rarely) reboots out of nowhere.
  • Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
  • I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)
nope, for me it increased.
 

miravision

Senior Member
Oct 5, 2021
285
182
Personal Notes:
  1. Battery life seems to have reduced a bit
  2. Phone (extremely rarely) reboots out of nowhere.
  3. Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
  4. I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.

Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...

nope, for me it increased.

Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?
 
Last edited:

J6idot

Senior Member
Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...



Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?
Screenshot_20211008-190919753.jpg
 

miravision

Senior Member
Oct 5, 2021
285
182
Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?

Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?

With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:

  1. Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
  2. Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks
 
Last edited:

J6idot

Senior Member
Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?

Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?

With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:

  1. Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
  2. Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks
Alright so, first of all, powersave governor underclocks to 500mhz -774 mhz. Some of the apps don't use the fully black amoled theme. And i keep my phone off overnight.

About the GPU? governor, same stock one because there is no way to change it/downclock it.

When scrolling, seems smooth to me, it might lag a little but i don't care.

And no, microphone doesn't lag.

Everything with CPU rendering (not GPU)
 

J6idot

Senior Member
Hey OP, i would like to also add that few sGSI might completely soft brick the phone.

If you install an sGSI, reboot, and then it bootloops after like 5 seconds, the phone will not boot.
I tried one sGSI, got this problem, reflashed DotOS and it still wouldn't boot, as it would be stuck at the boot animation.
I tried:
Reflashing DotOS
Reflashing the boot image
Reflashing vendor/product
Formatting and wiping continuosly the userdata partition. Nothing.
The only way to fix this is by flashing stock.

Also, if your phone reboots after like 10 seconds or more, then bootloops, reflashing the rom you were using will probably work fine.
 

miravision

Senior Member
Oct 5, 2021
285
182
How well does the latest Android 12 GSI final release, available since a few days ago, work on the 10s?

Please post detailed review with bug fixes and patches required for various issues on the main rosemary treble GSI rom Github repository to help everybody track the progress on the final release of Android 12 on the 10s.
 
Last edited:

seyren00

Member
Jul 15, 2021
8
1
Redmi Note 10S
Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"
 

Attachments

  • Screenshot_20211019-235649_Pixel_Launcher.png
    Screenshot_20211019-235649_Pixel_Launcher.png
    1.3 MB · Views: 743
  • Screenshot_20211019-235704_Configuración.png
    Screenshot_20211019-235704_Configuración.png
    140.5 KB · Views: 745
  • Screenshot_20211020-000640_Pixel_Launcher.png
    Screenshot_20211020-000640_Pixel_Launcher.png
    244.8 KB · Views: 716
  • Screenshot_20211020-001711_Google_Play_Store.png
    Screenshot_20211020-001711_Google_Play_Store.png
    678.1 KB · Views: 690
Last edited:

miravision

Senior Member
Oct 5, 2021
285
182
Have you stayed on DotOS or moved to a different GSI? Please post battery usage along with other points you mentioned that have gotten better or worse
Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"
 

ono123

Member
Apr 16, 2019
7
1
if i want to try DotOS which version should i download? theres a64 and arm64, i haven't installed a custom rom on my phone for a long time.
 

ono123

Member
Apr 16, 2019
7
1
PART 2: Le Bugs

Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.

Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)

1. Disabled Headphone Jack:

Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot

I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?
 

EL66K

New member
Nov 7, 2021
2
0
Can installing a different rom help with the video playback oversharpening, etc.? I mean all the miravision related issues. And what happends with HDR playback?
 

RandomAccessVemuri

New member
Sep 20, 2021
4
10
Redmi Note 10S
I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?
Hi,

You can root the phone using the general procedure (or as shown here) But TL;DR:
  1. Get the boot.img from the fastboot ROM (here)
  2. Install the Magisk Manager APK (from official sources only)
  3. Patch the boot.img with the magisk manager
  4. Flash the boot.img by fastboot flash boot patched_boot.img
  5. Reboot and open Magisk manager
  6. It will prompt you to do some stuff after which your phone should be rooted (it should actually be rooted once you flash the boot.img and boot up the phone but Magisk Manager lets you manage superuser related stuff)
At this point your phone should be rooted and you can proceed with the above instructions. However I'm more than confident that you could fix the headphone jack by looking into the Device specific settings. That's how I fixed it in a later install, anyways.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)

    This guide will help you to flash any GSI (Project Treble) ROM onto your Redmi Note 10S, and since TWRP, or any custom recovery for that matter, is not yet available, we have to manually install the GSI roms using fastboot (and fastbootd because of the dynamic partition). The process is lengthy but not that difficult.

    It should go without saying that you should backup everything and be prepared to lose your data and potentially soft-brick your phone and the experience with GSI roms is not always known to be stable (although I have not seen any such problems yet aside from a few easy-to-fix bugs) so do all of this at your own risk.

    Important to note is that if at anytime you mess stuff up or delete partitions you weren't supposed to (whatever the guides may say, don't erase the product partition, it won't help, you're gonna end up in a bootloop) and soft-brick your phone, as long as you can access fastboot you can easily fix the problem by using the MiFlash tool which will help you get back to square one (you won't have to wait to unlock the bootloader again so don't worry about that)

    Now, for the disclaimer:
    DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....experienced to weigh in his/her opinions. If you end up bricking your phone or if things go south, I'm not responsible, that's on you.

    NOTE:
    When I mention fastboot I'm referring to the standard "normal" fastboot and when I mention fastbootd, I'm referring to the dynamic/userspace fastboot which is different (which wiil be indicated by the fastboot screens during either of the modes)

    I should mention that using this method I have been able to flash DotOS, Android 12 Beta 5, CorvusOS (my current daily driver) and in my daily driver (Corvus OS), It's passing SafetyNet and the WideVine certification is still at L1 even after rooting, however I have tested neither Google Pay nor Netflix, because I don't use either of them so your mileage may vary, however I did find Netflix in the play store so that is a bit encouraging ig.

    Alright, with the appetizers out of the way, let's crack on to the main course:

    PART 0: Requirements:-

    Please ensure that the following requirements are met:
    • A Redmi Note 10S with an unlocked bootloader
    • OEM Fastboot driver and Fastbootd driver is installed
    • A preferred GSI rom (the file extension should be .img)
    • Being prepared to lose your data
    • Obtain android platform-tools along with knowledge about how to use it
    • Acceptance that the newly flashed GSI rom may/may not be completely stable.
    • Fastboot rom from here
    If you have all that, you can move on to the next step

    PART 1: Get Straight to Flashin':

    This guide is rather straightforward because there really isn't much to it.

    To begin with, extract the vbmeta.img from the Fastboot rom. Once you have done that, reboot your phone to fastboot mode.
    Once the phone is in fastboot mode, on your computer, run the following command:
    Code:
    fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
    to disable what is the android equivalent of window's secure boot

    Once that is done, issue the following command:
    Code:
    fastboot.exe reboot fastboot
    (No, there is no typo here, this is what needs to be done to enter the fastbootd mode, which is where the real fun begins)

    Ensure that you are in fastbootd mode. The blue coloured "fastboot" text at the bottom will be replaced by a yellow coloured "fastbootd"

    Okay, now for the most important command, type:
    Code:
    fastboot.exe -u flash system your_gsi_rom_of_choice.img

    Done!

    After this, don't forget to factory reset your device by:
    Code:
    fastboot.exe -w

    Note: If you forget to do the factory reset, you're gonna end up with a frankenstein combination of your new and some configs of your previous rom, in this case reboot to bootloader (using power and volume down) and issue the factory reset command (fastboot -w)

    And then for the toppings:
    Code:
    fastboot.exe reboot

    That's.....about it. You should boot into your chosen rom. For the first time, the boot animation may stick around for a long time (5 minutes or more). However, if, even after an absurd amount of time (15-20), the rom doesn't boot up, try using MiFlash tool to get back to square one and try the whole process again.

    Once it boots up, continue with the setup process and you will (hopefully) be at the home screen of your new rom.

    PART 2: Le Bugs

    Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.

    Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)

    1. Disabled Headphone Jack:

    Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
    Through your computer, issue the following commands (one-by-one, don't copy-paste them):
    Code:
    adb shell
    su
    setprop persist.sys.overlay.devinputjack true
    reboot

    Your phone will now reboot and once it does, you will see that the headphone jack is functioning normally again.

    2. Brightness Slider Fix:

    This one does not require any root. However, this does require that you can access the device specific customisations,

    So, in my case, I had to go into {Device Name} Settings > Misc features and then tick the Force alternative backlight scale . Once you have done that, reboot and your brightness slider will be working properly again. Also, if you noticed sudden fluctuations after booting or when device goes to sleep earlier, that should all be fixed as well.


    Conclusion:

    At this point, you should be ready to rock the world along with your phone. Depending upon the rom you have chosen (DotOS for example), your widevine certification and safetynet may be compromised, even after trying out several fixes (which is what happened in my case). So if that happens to you, I suggest that you either change your rom, hunt around for some solutions or just, you know, live with it.
    In my case, (As I mentioned before) I'm using CorvusOS where the widevine rating and safetynet are unaffected, with the latter requiring some special fixes.

    Hope that helped. I look forward to hearing from you people about any recommendations or discussion. If you have any problem with the process or think that something may be wrong, post it in the replies and I'll be happy to get back to you (depending upon the time, of course)
    2

    Pre-flash info:​

    • Device name: Xiaomi Redmi Note 10S (secret)
    • Earlier rom: MIUI 12.5.15 (Global)
    • Rooted?: Yes

    Tested image:​

    • Pixel Experience 12 Unofficial (phh v401)

    Hardware Support post flashing​

    ComponentComment
    CameraQuality looks better than stock
    Speaker/MicWorks, headphone jack requires a tiny tweak
    BluetoothWorks
    Wi-FiWorks
    SIM/Mobile Data/ VoiceSim works but mobile data does not work
    VoLTEDoes not work
    FingerprintWorks
    NFCNot tested
    Offline ChargingWorks
    Display Refresh rate60hz (same as before)
    Screen BrightnessWorks like before after a small tweak
    Volume scaleWorks fine
    5GN/A
    SafetyNet post root?Not tested
    WideVine certification post flash and rootNot tested

    Personal Notes:​

    • Native screenrecord causes device to freeze and crashes SystemUI. Third party screen recorders work fine tho so it's not a big problem.
    • Mobile data extremely rarely works.
    • System UI is very laggy, especially the app drawer [thanks @Redmi note 10s user]
    • Gcam camera quality looks better than stock, but photo view is very laggy (looks like 15fps) despite video is smooth. Also video shooting only works on main cam the other two are just black.
    • There is a noticeable performance drop in games and compile speed in AIDE.
    • ============================
    • There are many other bugs, most of them are fixable with little tweaks, but these are the most important for me and I didn't find a workaround yet.
    After using this rom for about two weeks, I think I'm going back to stock (or LiteE). The features I miss the most are floating apps (there are some alternatives but they are not as practical as stock rom), and especially MOBILE DATA is important. Please tell me if mobile data has been fixed and I will consider coming back to this rom.
    2
    If anyone wondering how to fix 4G VoLTE and Bluetooth. Contact me on XDA forums
    I've managed to fix it and would be down to help someone else
    share it public or report
    2
    Hey everyone, i never really use XDA anymore but i just wanted to drop in to say this:

    You should probably roll-back to MIUI 12.5 before flashing any GSI for the best experience, there's no antirollback protection at the time of writing (if there is MiFlash will warn you).
    I chose Pixel Experience 12 (v414, as v415 seems to have issues booting on MediaTek), and when flashed over the currently latest MIUI 13 my screen cutout was off, AOD didn't work, and the earpiece speaker was VERY loud during calls, i didn't have these issues under Pixel Experience 11 (flashed over MIUI 12.5) earlier this year.

    So i rolled back to MIUI 12.5 and flashing Pixel Experience 12 again, the screen cutout works perfectly just as i remember it on Pixel Experience 11 (the status bar isn't too near to the top of the screen), AOD worked right out of the box, and the earpiece speaker volume is fine (it's still louder than normal, but it's not extremely loud like on the same GSI running under MIUI 13).

    Another tip for y'all:
    It's not recommended to use fastboot -w to erase data, as this can cause some GSIs to be stuck on the bootanimation.
    Instead, type "fastboot reboot recovery" while in fastbootd, the recovery screen will pop up immediately, and wipe data from here then reboot.

    If you've already done fastboot -w and got stuck in a bootloop (infinite bootanimation), don't worry, just hold vol up + power to force restart the phone (once you see the Redmi logo release the power button) until you get into MIUI Recovery, wipe data then reboot and your GSI will boot fine.

    If you get a "failed to resize partition" error or similar, reflash MIUI using MiFlash, i don't know why exactly this fixes the issue, but it does.
    1
    Make sure this is checked in Misc featuresView attachment 5541197
    OMG. IT WORKED! THANKS A LOT