How To Guide Flashing GSI roms on Redmi Note 10S and then fixing some issues, all without any custom recovery
- Thread starter RandomAccessVemuri
- Start date
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
I've managed to fix it and would be down to help someone else
Greetings. As was ststed earlier, we would appreciate it if you have a fix for a particular issue, to please share it with the rest of the community
so that all members may benefit from your solution.
After all, that has been the spirit of XDA for 20+ years as noted in XDA Rule #12:
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50
Hey everyone, a little followup on this. I don't own this device anymore, but now i have a Note 11S, which is very similar in some ways to the Note 10S (you also have to flash an Android 11 stock rom or you get similar issues, etc.)
I used Pixel Experience 13 GSI for a short period of time on my Note 10S before it died due to water damage and i had the same issue i'm having right now on my Note 11S, which is delayed notifications due to Doze being bugged on some GSIs (like PE 13). I think it might be an issue only on some Android 13 GSIs, but i'm not too sure. Either way, see here for a thread i made on the Note 11S which has a kinda crappy but working solution which should work on the Note 10S as well since the issue was literally identical.
That's all, i just wanted to drop in to say this
(btw, the Note 10S is back alive, i cleaned the motherboard with some alcohol because there was still some white-ish leftover from the water and it booted back up! now it's running MIUI and someone else's using it though, so i can't exactly test this to be sure, but it should work)I have issues on a gsi thats on top of MIUI 14 firmware. I get *unknown baseband* and it doesnt even detect sim card. Though this can be solved by downgrading the md1img (modem image) i still want to use it with the newer modem image for extra security. Also AOD doesnt work anymore
They're pretty rare to find nowadays. I mean even if you want to use MIUI, why not just use the stock MIUI?
Hi, I follow the exact steps of the OP except for the argument flash -u which doesn't work, so I've doing this straight from a stock ROM for my POCO M5s (rosemary_p) (flashall.bat from rosemary_p_eea_global_images_V13.0.6.0.SFFEUXM_20231025.0000.00_12.0_eea_28f06ea5d6.zip)
After entering these 5 commands, the cell network which worked in MIUI doesn't work on the GSI rom (crDroid-10.1 v2024.01.22).
I've tried to restore persist.img, thinking it will fix the issue (I've done it via TWRP as flashing persist via fastboot gives me a "partition is write protected" but I still don't have the cell network (Android asks me the PIN code, but I can't connect to network).
Does someone knows or have the same issue ?
After entering these 5 commands, the cell network which worked in MIUI doesn't work on the GSI rom (crDroid-10.1 v2024.01.22).
I've tried to restore persist.img, thinking it will fix the issue (I've done it via TWRP as flashing persist via fastboot gives me a "partition is write protected" but I still don't have the cell network (Android asks me the PIN code, but I can't connect to network).
Does someone knows or have the same issue ?
Top Liked Posts
-
There are no posts matching your filters.
-
6By 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 mentionfastbootI'm referring to the standard "normal" fastboot and when I mentionfastbootd, 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
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:
to disable what is the android equivalent of window's secure bootCode:fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
Once that is done, issue the following command:
(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)Code:fastboot.exe reboot fastboot
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 featuresand then tick theForce 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)2Pre-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
Component Comment Camera Quality looks better than stock Speaker/Mic Works, headphone jack requires a tiny tweak Bluetooth Works Wi-Fi Works SIM/Mobile Data/ Voice Sim works but mobile data does not work VoLTE Does not work Fingerprint Works NFC Not tested Offline Charging Works Display Refresh rate 60hz (same as before) Screen Brightness Works like before after a small tweak Volume scale Works fine 5G N/A SafetyNet post root? Not tested WideVine certification post flash and root Not 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.
22Hey 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
