• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)

Search This thread

VD171

Senior Member
Jun 21, 2012
2,044
2
1,639
127.0.0.1
LG K10
Samsung Galaxy J7
I obviously unlocked my bootloader, I flashed patched vbmeta bc using stock vbmeta with disabled verity and verification gives error 0.
The vbmeta is okay, I am just super annoyed by not being able to flash a patched boot image without CMDLINE OVERFLOW
You really need patched vbmeta.
You can flash ANY patched vbmeta, any version will works perfectly.
 

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9
You really need patched vbmeta.
You can flash ANY patched vbmeta, any version will works perfectly.

Okay, I already tried the patched vbmeta for MIUI V12.5.1 but it didn't work so im going to try different ones.
Okay, I used the 12.0.1 patched vbmeta and now I can see the redmi logo with NO cmdline overflow, it just cant boot to miui so i will just flash a custom rom and be happy with it
 

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9
Apparentely you need to flash stock miui again.
And then, you can apply changes again.
Okay, I think I finally found the bottom of the problem.
I flash 12.0.6 and I still had the same issue when I make a change to the device's partitions such as boot it bootloops, which indicates it's a vbmeta issue, this is probably related to "Rewriting vbmeta struct at offset: 0" when using the disable verification and verity command, even patched vbmeta works like stock for me. I am just gonna back up all my devices IDs and my IMEIs then I'ma format all with sp and start over.
 

VD171

Senior Member
Jun 21, 2012
2,044
2
1,639
127.0.0.1
LG K10
Samsung Galaxy J7
Okay, I think I finally found the bottom of the problem.
I flash 12.0.6 and I still had the same issue when I make a change to the device's partitions such as boot it bootloops, which indicates it's a vbmeta issue, this is probably related to "Rewriting vbmeta struct at offset: 0" when using the disable verification and verity command, even patched vbmeta works like stock for me. I am just gonna back up all my devices IDs and my IMEIs then I'ma format all with sp and start over.
Format all does NOT solve any problem.
It just causes more problems.
NEVER TRY TO FLASH USING FORMAT ALL MODE.
Just flash stock miui using firmware upgrade and it's enought.
Firmware upgrade mode clear all user data and keep all sensitive data, like IMEI and MAC.
 

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9
Format all does NOT solve any problem.
It just causes more problems.
NEVER TRY TO FLASH USING FORMAT ALL MODE.
Just flash stock miui using firmware upgrade and it's enought.
Firmware upgrade mode clear all user data and keep all sensitive data, like IMEI and MAC.
I wanted to flash 12.0.1 Indonesia and i followed the method and still couldn't flash the vbmeta correctly.
Until I FINALLY found the problem.
My platform tools weren't working normally...
I kept trying to fix a simple problem...
anyways, if someone says that when writing vbmeta it says vbmeta writing struct at offset: 0
then tell them to use MINIMAL adb and fastboot.
that was the most unexpected issue I had...
 
  • Like
Reactions: VD171

VD171

Senior Member
Jun 21, 2012
2,044
2
1,639
127.0.0.1
LG K10
Samsung Galaxy J7
I wanted to flash 12.0.1 Indonesia and i followed the method and still couldn't flash the vbmeta correctly.
Until I FINALLY found the problem.
My platform tools weren't working normally...
I kept trying to fix a simple problem...
anyways, if someone says that when writing vbmeta it says vbmeta writing struct at offset: 0
then tell them to use MINIMAL adb and fastboot.
that was the most unexpected issue I had...
Yes.
I strongly suggest you to keep on adb and fastboot.
You can find them here:
 

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9
Yes.
I strongly suggest you to keep on adb and fastboot.
You can find them here:
I have a question though, I have been unable to mount product as r/w, I already managed to mount system and vendor as r/w, I just want to change a file in product.
 

VD171

Senior Member
Jun 21, 2012
2,044
2
1,639
127.0.0.1
LG K10
Samsung Galaxy J7
I have a question though, I have been unable to mount product as r/w, I already managed to mount system and vendor as r/w, I just want to change a file in product.
Did you already try this?
 

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9

Madmoud

Member
Sep 17, 2021
20
4
Redmi Note 9
Did you already try this?
I just want the product partition to be r/w, not the system/vendor bc I want to change the boot animation
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi, @VD171 I realise you must have very good control of your Redmi Note 9 merlin! (y)! Thank you for these patched boot.img - very good idea.
    Where I have got to is that I have learned that on Linux Debian Buster I can get back to a reliable base MIUIV12.0.3.0. QJOMIXM by
    flash-all.script
    from within the ROM. (Other readers should understand how + why that might work before trying!)

    I now see that V12.0.3.0 is not one that you regularly list. My question is really about this numbering. Is there a base version of the ROM that you favour, that gives the user best control of the device?

    Thanks in advance, and many thanks for curating these threads.
    I suggest you to keep on LATEST MIUI.
    But, I suggest you to mix some partitions from older MIUI:
    - PRELOADER: V12.0.4.0 (or older): It allows you to flash using SPFLASHTOOL without the EDL mode and bypass the authentication.
    - LK: V12.0.4.0 (or older): It allows you to flash ANY version of the TWRP or PBRP.
    1
    PATCHED BOOT.IMG for MERLIN by VD171

    For what do I need it ?

    At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom recovery.
    Keep attention, it is not pre-rooted.

    Works with:

    - Xiaomi Redmi Note 9
    - Xiaomi Redmi 10X 4G

    Firmware Versions:
    - (Engineering) AL2522-Merlin-V039-Q-0513
    - (Engineering) AL2522-Merlin-V044-Q-0920
    - V12.5.2.0.RJOMIXM
    - V12.5.1.0.RJOMIXM
    - V12.0.1.0.RJOMIXM
    - V12.0.8.0.QJOMIXM
    - V12.0.7.0.QJOMIXM
    - V12.0.6.0.QJOMIXM
    - V12.0.5.0.QJOMIXM
    - V12.0.4.0.QJOMIXM
    - (India) V12.0.4.0.QJOINXM
    - V11.0.5.0.QJOMIXM
    - V11.0.4.0.QJOMIXM

    How to flash it?
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    fastboot flash boot boot_vd171.img

    MD5 hashes:
    AL2522-Merlin-V039-Q-0513: a04fdd922f5e5dd49c7772e75defa06e
    AL2522-Merlin-V044-Q-0920: 9239a1fc45ba5be6ea83527eeddb2728
    V12.5.2.0.RJOMIXM: e18546706fdbf35404b2116601231a09
    V12.5.1.0.RJOMIXM: e172cfa9c96c5f829170db671baadba3
    V12.0.1.0.RJOMIXM: a446c9d747247c4ce8016da83cbdc932
    V12.0.8.0.QJOMIXM: dd3e581fc2ee1e2ef7b56a843bdd4d9d
    V12.0.7.0.QJOMIXM: 884ea8c8798c594db58359796fa14f30
    V12.0.6.0.QJOMIXM: 146f1254604bf9b57335eae1cd60dd03
    V12.0.5.0.QJOMIXM: 3a46568b0e3d2aafc607a8d2add1bf40
    V12.0.4.0.QJOMIXM: be2f0c391b22dcc9ed8d4dbbb7900cd8
    (India) V12.0.4.0.QJOINXM: 416a03273045e616d67f76e3b3c50807
    V11.0.5.0.QJOMIXM: 262ec3ba40c53add7f651188920618b8
    V11.0.4.0.QJOMIXM: 48b568eddcd1a888fe0286beb2ed4f4a



    :unsure: Do you need help with your MERLIN device ?
    Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
    1
    will this work on 12.0.9.0 QJOEUXM???
    This is not rooted.
    1
    Thank you very much for this much valued advice. (y)

    I was now able to install eOS, e-0.15-q-20210310-UNOFFICIAL-merlin.zip from


    using a newly flashed MIUI V12.0.9.0 EU and it is running very well. Thanks.

    Many thanks also to the ROM builder credited within the link.
    Good work, my friend.
    You are welcome
    1
    Hi! Thanks for all the things you have shared for this phone. I got an issue every time i flash this patched boot.img i get stuck in a bootloop, and the only way to get out of that is to flash the stock boot.img again. Any ideas why this is happening?
    You are welcome, my friend.
    Did you flash patched vbmeta too?