19

Redmi Note 10S

 2 years ago
source link: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/page-4#post-86994661
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

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

pumpkin072618

Senior Member
Feb 24, 2019
Yes, I installed the stock ROM and then went through the process again.
But all the ROMs I tried, after some time, starts to show bootloop. I'm tired... I currently have MIUI stock.

That's sad. I was already considering flashing gsi rom as my daily driver but having a random bootloop and need to reinstall all over again, that's just tiring. So as for you, should i stick to stock miui rom or would you recommend me to try gsi?

That's sad. I was already considering flashing gsi rom as my daily driver but having a random bootloop and need to reinstall all over again, that's just tiring. So as for you, should i stick to stock miui rom or would you recommend me to try gsi?

My RN10 is for everyday use. Three times I was without my cell phone because of these errors. I got angry. I decided to wait for a stable GSI ROM to try again. I need my cell phone during work.

Does anyone know if support for Pixel Experience Plus 12.1 v412 was discontinued since it hasn't changed version for 14 days?
Coincidentally, fellow developers, someone has installed rossemary or maltose a mojito or sweet rom
1650993909815.png

fatk1d

New member
Jun 13, 2018
Help. Trying to flash Pixel Experience and I'm getting sparse file format at header magic and not enough partition size.

ono123

Member
Apr 16, 2019
Can someone help me?
I already installed the drivers needed and followed every step carefully. But when flashing the gsi_rom.img (on my case it's pixel experience). I get an error saying
INVALID SPARSE FILE FORMAT AT HEADER MAGIC and then NOT ENOUGH SPACE TO RESIZE PARTITION.

Also, is it okay that when i fastboot reboot fastboot it directs me to my custom recovery(ofox) but it says i'm on the fastboot ??
Please help. Want to experience gsi rom. Thanks
Hi, I've previously installed a GSI rom but back to stock rom and when i want to install the GSI rom again, i got same problem with you. Here's what i did and successfully installed gsi rom again.
1. Downgrade the stock rom, i used 12.5.16 and downgrade to 12.5.14 (remember it will erase all of your data)
2. After successful downgrade, do setup and unlcok the bootloader
3. just follow the instruction on this thread and everything will be fine

i hope this will help you, and the most important thing is you should backup all of your data first.

pumpkin072618

Senior Member
Feb 24, 2019
Hi, I've previously installed a GSI rom but back to stock rom and when i want to install the GSI rom again, i got same problem with you. Here's what i did and successfully installed gsi rom again.
1. Downgrade the stock rom, i used 12.5.16 and downgrade to 12.5.14 (remember it will erase all of your data)
2. After successful downgrade, do setup and unlcok the bootloader
3. just follow the instruction on this thread and everything will be fine

i hope this will help you, and the most important thing is you should backup all of your data first.

Thanks mate! I'm already able to flash gsi.

pumpkin072618

Senior Member
Feb 24, 2019
Good day guys!
To all gsi user, i have 2 questions.

1. First, any gsi rom with offline charging animation? I already tried corvus, pixel experience but it was only stuck on redmi logo. No offline charging animation.

2. Is there a way to use stock camera to gsi rom? I really need the 1080/60fps. I used gcam but it is kinda laggy. I watched that you can use some module like anx but i have not yet tested it and not know which one is compatible.

Thanks!

Noé26

New member
Mar 27, 2020
Hi, I've previously installed a GSI rom but back to stock rom and when i want to install the GSI rom again, i got same problem with you. Here's what i did and successfully installed gsi rom again.
1. Downgrade the stock rom, i used 12.5.16 and downgrade to 12.5.14 (remember it will erase all of your data)
2. After successful downgrade, do setup and unlcok the bootloader
3. just follow the instruction on this thread and everything will be fine

i hope this will help you, and the most important thing is you should backup all of your data first.

No works for me...

batzkass

New member
Jun 7, 2022 Sélestat
First I would like to thank all contributors to this thread, and especially @RandomAccessVemuri. I own a Redmi Note 10s for a few months now, and I was tired about miui so I installed a GSI rom.
I have two unsolved issues however :
  1. I was unable to install DotOS (this exact image), on first boot I get infinite DotOS logo, up to 15 minutes. Does somebody have an idea about that ? That as my first GSI attempt.
  2. Using the exact same procedure (the one described in the post #1), I was however able to install Pixel Experience. Almost everything works very well with all the small fixes described in this thread... But there are two annoying sound issues described below.
  • Less annoying : during a call, passing to handsfree mode (speaker) "works", but after that if I disable handfree mode my interlocutor doesn't hear me anymore. I still can hear him however. The only way to re-establish the communication is to enable handsfree mode again. Also, it seems that my mic gain doesn't properly increase while in handsfree mode, but I'm not sure about that point.
  • More annoying : the in-call volume doesn't change and its very, very loud. Using the hardware buttons the corresponding visual slider moves but the volume doesn't. I made my own researches : from here it seems that it's a common issue with Mediatek+GSI roms ; then from here someone has written a dirty (yet functional) workaround for it, and (as the script doesn't work for our RN10s) from here I found an other version of the same script. With all these information I managed to make the in-call volume to "work" for magisk-rooted RN10s.
My questions about this second issue : does anybody experience it ? I'm surprised that no one mentioned it here.
For people who installed other gsi (corvus, dot, ...), is it better with them ?

I will detail the workaround procedure here if someone request it.

Top Liked Posts

  • 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)

    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.

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK