[V1][ENGINEERING][ROM] OFFICIAL Engineering Firmware for MERLIN (Redmi Note 9 / Redmi 10X 4G)

[SubwayChamp]

Thanks for your help i will search for it.

You also have to read something like this https://xdaforums.com/t/poco-f3-patched-firehose.4426531/page-2 it seems, like I said to you previously, your device share some specs with other (two) devices, and of course, its development, issues and solution may be shared too.

If you find a patched Firehose file for your device, you may use MiFlash to bypass authorization.

 

[Keffr3n]

Hi there, I know this is an old thread... but I cannot find a solution, I lost nvram partition, used engineering rom to write imei back (I still have the phone's box). but cannot flash a usable rom...
how could I transfer the imei data to an official miui rom?

What shouild I do to change the engineering rom with a user one? Thanks!

 

[SubwayChamp]

Hi there, I know this is an old thread... but I cannot find a solution, I lost nvram partition, used engineering rom to write imei back (I still have the phone's box). but cannot flash a usable rom...
how could I transfer the imei data to an official miui rom?

What shouild I do to change the engineering rom with a user one? Thanks!

IMEI can't be transferred specifically, but rewritten.
Firstly you need to recover the baseband, in order to can write the IMEI, maybe with the help of an ENG ROM, after that, you can try again with Modem Meta tool.

 

[YLTN]

Version 1

View attachment 5208113​

Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G

Build Date:
2020/05/13

Android Version:
QP1A.190711.020

Display ID:
AL2522-Merlin-V039-Q-0513

Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys

Security Patch:
2019/12/05

Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3

Kernel Version:
4.14.141-gf3c3c7a
Wed May 13 12:49:46 CST 2020

Download:
https://www.mediafire.com/file/lon7...V039-Q-0513_QP1A.190711.020_by-VD171.zip/file

Password:
Pass is in the attached file: PASSWORD_by_VD171.txt

How to flash it?
Use any scatter file specific for MERLIN.

Radio/Modem/Baseband properties:

md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB

Prop.default:

ro.build.version.incremental=258
ro.odm.build.version.incremental=258
ro.vendor.build.version.incremental=258
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V039-Q-0513
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.build.product=merlin
ro.product.board=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 258 test-keys
ro.board.platform=mt6768
ro.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.bootimage.build.date=Wed May 13 12:41:51 CST 2020
ro.build.date=Wed May 13 12:41:51 CST 2020
ro.odm.build.date=Wed May 13 12:41:51 CST 2020
ro.product.build.date=Wed May 13 12:41:51 CST 2020
ro.system.build.date=Wed May 13 12:41:51 CST 2020
ro.vendor.build.date=Wed May 13 12:41:51 CST 2020

MD5 hashes:

APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> e9dfb7dde67795157a871bc14b490054
boot.img -> d6e19a30d85a27379d91072665ad43c9
cache.img -> c40c137a18a26980d406d4ef0ccd7e61
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19_1_ulwctg_n -> b5bf654ddaacfd61e78c131f721974af
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 9b0fa19089a0310325b88eebc8e41ae7
dtbo.img -> 9b0fa19089a0310325b88eebc8e41ae7
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
lk-verified.img -> 0ba475d8c216b2613815b59e3db8da2b
lk.img -> 0ba475d8c216b2613815b59e3db8da2b
logo.bin -> 257508aa9cdeb690e4a4ed038c91ff76
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 27cd78644df092ade4ca03799dc3c2a3
md1img.img -> 27cd78644df092ade4ca03799dc3c2a3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> 4e040508c1878706a428c54ef0844e0f
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 7c1ecfd4e3d626957b6655f107824649
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> b24757bd125ad435bd2d26575b5c1d75
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> dbc21da31860042674fab69d07444e95
preloader_emmc.img -> dbc21da31860042674fab69d07444e95
preloader_merlin.bin -> bc7ebc0c2ca06b0d99856d595949e215
preloader_ufs.img -> 29ef0e631a45bf14555fd6b7adb7a7bf
product.img -> 7ec4f1ffd2b49d7c5b4f1bb5d3ba0dc6
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 77de275ef543e46bbedfd53b7e36f945
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> 6362f1beb617572680f3fc91640d3767
scp-verified.img -> 2cac6177dc7eec82421cb3f4a2776aff
scp.img -> 2cac6177dc7eec82421cb3f4a2776aff
secro.img -> 096587b863e1252d67b1b8307291db09
spmfw-verified.img -> 40345cc1edec88bcd510fa62eac01739
spmfw.img -> 40345cc1edec88bcd510fa62eac01739
sspm-verified.img -> 0ceaf392e89bf70c9a52a5c91cc75865
sspm.img -> 0ceaf392e89bf70c9a52a5c91cc75865
super.img -> 542873466ecc6603c81758cf6a000390
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 27976b65c09bd01e7963a5f3db563fc7
tee-verified.img -> 4f2fdf78d5be3a5de0154c46af69d476
tee.img -> 4f2fdf78d5be3a5de0154c46af69d476
userdata.img -> 802561cd4739f2f0aae7a51890a5866f
vbmeta.img -> 31da88d4a00b99b36081f859f17f808a
vbmeta_system.img -> a6b560b53a42c98fba204f2b69e70fd7
vbmeta_vendor.img -> 86fae46d211bdedcb49bd08e901d4d3f
vendor.img -> 1a15f790bf6c32fb959da9bc4dfce6e4

Do you need help with your MERLIN device ?
Read this FAQ: https://xdaforums.com/t/faq-guide-h...for-merlin-redmi-note-9-redmi-10x-4g.4225163/

It tells me I need exaid verified

 

[EACUAMBA]

YES, this is leaked but it is OFFICIAL developed and signed by xiaomi.
Only Xiaomi can sign images with xiaomi signature.
Are you insane?
Do you mean halabtech has any developer on its team?
LOL, LOL, LOL.
Halabtech is just a (good) copier.
I've never seen anything developed by halabtech team.
Except some bat files compiled to exe... LOL, LOL, LOL.
( IF ANYBODY NEEDS ANY FILE UPLOAED TO halabtech, JUST TELL ME AND I WILL PROVIDE THIS FILE TO YOU FOR FREE ! )


Read this: https://xdaforums.com/t/engineering...dmi-note-9-redmi-10x-4g.4227933/post-84441883

Hi brother, hope you doing well.

My Redmi Redmi Note 12 Pro+ (rubypro).
Lost Baseband when trying to flash European ROM.

I need ENG ROM for it, can you please provide one?

I created this thread and I tried nvram backup from other phones bits it didn't works.

https://xdaforums.com/t/nvram-backup-for-redmi-note-12-pro-5g-ruby-or-rubypro.4603205/

 

[SubwayChamp]

Hi brother, hope you doing well.

My Redmi Redmi Note 12 Pro+ (rubypro).
Lost Baseband when trying to flash European ROM.

I need ENG ROM for it, can you please provide one?

I created this thread and I tried nvram backup from other phones bits it didn't works.

https://xdaforums.com/t/nvram-backup-for-redmi-note-12-pro-5g-ruby-or-rubypro.4603205/

If it is a MediaTek device, you can flash back the right version at anytime, also consider that ENG ROMs don´t restore NVRAM nor solve any "added" issue, it´s for testing purposes, nothing more.

 

[EACUAMBA]

If it is a MediaTek device, you can flash back the right version at anytime, also consider that ENG ROMs don´t restore NVRAM nor solve any "added" issue, it´s for testing purposes, nothing more.

I read in some threads that I can flash ENGINEERING ROM to recovery from this problem.

Like this one https://xdaforums.com/t/guide-how-t...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/

 

[SubwayChamp]

I read in some threads that I can flash ENGINEERING ROM to recovery from this problem.

Like this one https://xdaforums.com/t/guide-how-t...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/

No, the only good for this purpose is they may or may nor, enable some options to can use other tool over it, for example, this ROM may enable engineering tools, so you can use a tool like Modem meta/maui meta, and so.

A dumped/backed up ROM from other device may solve (only) some of the issues, like calibration data, MaC, WiFi, baseband, but never the IMEI.

If your sole issue is right now, the baseband, you could root your device, then search for /data/nvdata path, delete every thing, reboot, you should copy that folder in a safe place, just in case. There are other methods though.

 

[EACUAMBA]

No, the only good for this purpose is they may or may nor, enable some options to can use other tool over it, for example, this ROM may enable engineering tools, so you can use a tool like Modem meta/maui meta, and so.

A dumped/backed up ROM from other device may solve (only) some of the issues, like calibration data, MaC, WiFi, baseband, but never the IMEI.

If your sole issue is right now, the baseband, you could root your device, then search for /data/nvdata path, delete every thing, reboot, you should copy that folder in a safe place, just in case.

For me solving baseband is a big step, with baseband I can't struggle with Maui Meta to write the IMEIs, the problem is that I can find any one with a rubypro (someone shared ruby, but ir doesn't work, because my phone is rubypro) to share with me the backups.

So if you know someone that can share with me rubypro backups, I will at least solve baseband.

 

[SubwayChamp]

For me solving baseband is a big step, with baseband I can't struggle with Maui Meta to write the IMEIs, the problem is that I can find any one with a rubypro (someone shared ruby, but ir doesn't work, because my phone is rubypro) to share with me the backups.

So if you know someone that can share with me rubypro backups, I will at least solve baseband.

To recover the baseband, sometimes, may it be incredible easy, like doing what I pointed out, also erasing the nvdata region, using SP flash tool, sometimes, a simple update may solve it.

If you are a middle advanced user, you can use the second method, search for the scatter file, look at the lenght/address of the NVDATA region, select the second tab on SPFT, Manual format flash, baseband has to be recovered this way, always that you didn´t change the PMT (I don´t think so).

And, exactly the contrary, you need a baseband working, to can go for the next, recover (or try to) the IMEI.

 

[EACUAMBA]

To recover the baseband, sometimes, may it be incredible easy, like doing what I pointed out, also erasing the nvdata region, using SP flash tool, sometimes, a simple update may solve it.

If you are a middle advanced user, you can use the second method, search for the scatter file, look at the lenght/address of the NVDATA region, select the second tab on SPFT, Manual format flash, baseband has to be recovered this way, always that you didn´t change the PMT (I don´t think so).

And, exactly the contrary, you need a baseband working, to can go for the next, recover (or try to) the IMEI.

I will try what you said, with flash tool. But I already wiped this partition with mtkclient is not equivalent?

 

[SubwayChamp]

I will try what you said, with flash tool. But I already wiped this partition with mtkclient is not equivalent?

Yes, it could be the same, but, just maybe, also search for a dumped ROM for your device

 

[EACUAMBA]

Yes, it could be the same, but, just maybe, also search for a dumped ROM for your device

Thanks for your help mate,

I'm searching all the internet, I used Yandex and I searched in Russian, I used Baidu and searched in Chinese but nothing. I'm really tired. But I will keep looking for.

 

[texet2577]

what password?

 

[SubwayChamp]

what password?