[ENGINEERING][ROM][OFFICIAL] OFFICIAL Engineering Firmware for LANCELOT (Redmi 9 / Redmi 9 Prime)

Search This thread

blazesprings

Member
Jan 30, 2016
7
0
@VD171 Hello brother, do I have to unzip the zipped firmware file before loading the Scatter file?
Can you please tell me how to load the firmware file to SP Flash tool? Please help. Thanks
 

Roberto_83

Member
Dec 31, 2022
35
1
@VD171 Hello brother, do I have to unzip the zipped firmware file before loading the Scatter file?
Can you please tell me how to load the firmware file to SP Flash tool? Please help. Thanks
Usually you download TGZ.
Unzip TGZ to TAR
Unzip TAR to DIRECTORY

Now with SP_FLASH_TOOL select the scatter into:

DIRECTORY/IMAGES/MT6768_Android_scatter.txt

Automatically SP_FLASH_TOOL select all the file
 

Attachments

  • Immagine.jpg
    Immagine.jpg
    24.3 KB · Views: 9

blazesprings

Member
Jan 30, 2016
7
0
Hello @Roberto_83 I am not seeing any progress in the progress bar.
1. I have loaded the scatter file to the SP Flash Tool. preloaded, recovery, vbmeta.... all are getting selected.
2. Pressed the Download button.
3. Connected the phone in switch off mode.
Am i doing anything wrong or have I skipped anything? Here's the screenshot. Please help.
Can you please give a short tutorial how to flash using SP Flash Tool?
1674981511554.png


Thanks.
 

Roberto_83

Member
Dec 31, 2022
35
1
Hello @Roberto_83 I am not seeing any progress in the progress bar.
1. I have loaded the scatter file to the SP Flash Tool. preloaded, recovery, vbmeta.... all are getting selected.
2. Pressed the Download button.
3. Connected the phone in switch off mode.
Am i doing anything wrong or have I skipped anything? Here's the screenshot. Please help.
Can you please give a short tutorial how to flash using SP Flash Tool?
View attachment 5822635

Thanks.
Hi,
I send you a private message conversation.
Please reply me

Bye
 

Roberto_83

Member
Dec 31, 2022
35
1
Thanks,

*I connected with USB Debug.
*I send "adb device" and I see phone
*I send "adb reboot fastbpot" and phone restart
*I send "fastboot flash vbmeta vbmeta.img" and I see transfer information, but after few second I see transfer completed and from PC black screen I see errore transfer.

Maybe I have to unlock bootloader?

You told me I can flash vbmeta also without unlock bootloader but maybe I dont understand.

For other people, the only ufficial ROM that let me to restored also NFC with also split screen is 12.0.1.0 QJCMIXM
 

Roberto_83

Member
Dec 31, 2022
35
1
If you have locked bootloader, you can flash vbmeta and boot from sp flash tool
If I use SP FL TOOL to flash vbmeta and boot (after write IMEI 2), as I had already tried, I reboot and system show SYSTEM DESTROYED.

I tried to do immediately after wrote IMEI2 (without reboot).
And also I tried to do after boot system, register Google account, waiting for app upgrade, than power off and connect with SP FL TOOL.
But in both cases, always returned SYSTEM DESTROYED.

So the only way is to unlock bootloader I think.
 
Vcom drivers works however, also if they are unsigned. For modem meta, install libusb and mtk drivers from attached file and read carefully these steps:
1) Format & flash MIUI (MIUI 13 should work);
2) after flash, deselect ALL partitions except md1img;
3) in md1img, select attached IMG file in my previous post and flash it (remember to tick ONLY md1img);
4) format nvdata & nvram;
5)Power off phone, open modem meta (click connect button) and mtkmeta utility, press and hold vol- and connect it to pc; modem meta should have to recognize phone automatically;
6) write only IMEI 2 and reboot (if you write both IMEI, you'll get NV data is corrupted and phone won't boot);
7) the SIM should work (remember to put it in slot 2);
Optional step(if you want also IMEI 1):
8)flash attached vbmeta.img and boot.img, open Modem meta and write IMEI 1; phone should boot and both IMEI's should work.
Try to refollow carefully this guide
 

yas8say

Member
May 6, 2019
32
1
Vcom drivers works however, also if they are unsigned. For modem meta, install libusb and mtk drivers from attached file and read carefully these steps:
1) Format & flash MIUI (MIUI 13 should work);
2) after flash, deselect ALL partitions except md1img;
3) in md1img, select attached IMG file in my previous post and flash it (remember to tick ONLY md1img);
4) format nvdata & nvram;
5)Power off phone, open modem meta (click connect button) and mtkmeta utility, press and hold vol- and connect it to pc; modem meta should have to recognize phone automatically;
6) write only IMEI 2 and reboot (if you write both IMEI, you'll get NV data is corrupted and phone won't boot);
7) the SIM should work (remember to put it in slot 2);
Optional step(if you want also IMEI 1):
8)flash attached vbmeta.img and boot.img, open Modem meta and write IMEI 1; phone should boot and both IMEI's should work.
Hello ,
Is this temporary or permanent fix?
Like if I update the rom will it be back to square one?
 
Hello ,
Is this temporary or permanent fix?
Like if I update the rom will it be back to square one?
Sadly it's temporary because if you do an upgrade to next version of Android, your device will brick; but If you upgrade to next MIUI, your device should work because MIUI 13 and 14 will have same android version on this device. I can't fix that brick issue
 

Roberto_83

Member
Dec 31, 2022
35
1
Try to refollow carefully this guide

Hi KING

I follow your guide carefully and i reach point number 6.
I'd like to add point number 7, so to get also IMEI 1.

I don't have any issue to follow your guide from 1 to 6 ( I can format and flash all the time I want and starting with all ROM I want ( I downloaded all ROM) I reach always 6.

I am also able to flash 11.0.9.0 and than upgrade with OTA till 12.5

Now I understand that for point 7 I have necessary to unlock bootloader.
There aren't any other way.

I have a issue in this way:
  • I connect MI Account into the options
  • I open development option
  • I enable OEM unlock and Debug USB
  • When I check MI Account Status I receive an error message, for example "try later" or "you have no connection" or "request parameter error"
If I try at the same to unlock bootloader with my PC, fastboot mode, connect cable, I reach 99% and than I receive an error because MI Account Status is not connected.

I try to create also another account and try but nothing.

Do you know any tricks?

THX
 
Hi KING

I follow your guide carefully and i reach point number 6.
I'd like to add point number 7, so to get also IMEI 1.

I don't have any issue to follow your guide from 1 to 6 ( I can format and flash all the time I want and starting with all ROM I want ( I downloaded all ROM) I reach always 6.

I am also able to flash 11.0.9.0 and than upgrade with OTA till 12.5

Now I understand that for point 7 I have necessary to unlock bootloader.
There aren't any other way.

I have a issue in this way:
  • I connect MI Account into the options
  • I open development option
  • I enable OEM unlock and Debug USB
  • When I check MI Account Status I receive an error message, for example "try later" or "you have no connection" or "request parameter error"
If I try at the same to unlock bootloader with my PC, fastboot mode, connect cable, I reach 99% and than I receive an error because MI Account Status is not connected.

I try to create also another account and try but nothing.

Do you know any tricks?

THX
You get mi account error without SIM card
 

Roberto_83

Member
Dec 31, 2022
35
1
You get mi account error without SIM card
I installed SIM into slot number 2 after wrote IMEI with modem meta.
I got 3G and 4G connection, I can make phone conversation or using telegram/whatsapp/SMS messaging. So my network works.

I could use my phone also with only one SIM, but I'd like to restore completly
 

Roberto_83

Member
Dec 31, 2022
35
1
Flash my boot and vbmeta files and try to write IMEI 1
Now, with only IMEI 2 restored and bootloader locked, I think I can't flash your file with ADB Command, but if you tell me that I can do it, I'll try.
The only solution that I know is to flash using SP Flash Tool.
I tryed with spflashtool but after flash, when I power-on the phone I receive a SYSTEM DESTROYED message and phone swap into fastboot.
 
Now, with only IMEI 2 restored and bootloader locked, I think I can't flash your file with ADB Command, but if you tell me that I can do it, I'll try.
The only solution that I know is to flash using SP Flash Tool.
I tryed with spflashtool but after flash, when I power-on the phone I receive a SYSTEM DESTROYED message and phone swap into fastboot.
Sadly the unique method is to flash both files from fastboot, there aren't any other way.
 

Roberto_83

Member
Dec 31, 2022
35
1
Sadly the unique method is to flash both files from fastboot, there aren't any other way.
Hello, IDIOT-BOY come back :)

Please I ask another time your help.
I delete my MI ACCOUNT before logout by my phone.
Now the phone is locked in black screen asking me a password of an account deleted.

I tried to reflash (sp_flash_tool with format+download) a stock ROM but nothing to do.

I am able to reboot with new installed rom, but if I connect to WIFI or SIM-CARD, after few seconds it returns in black screen.

Only ENG ROM work with WIFI or SIM without black screen.

Is there any solution to delete this check??

Thanks to all
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Works with:
    - Xiaomi Redmi 9
    - Xiaomi Redmi 9 Prime

    Build Date:
    2020/06/23

    Android Version:
    QP1A.190711.020

    Display ID:
    AL2615-lancelot-V011-Q-0623

    Build Fingerprint:
    Redmi/lancelot/lancelot:10/QP1A.190711.020/6:userdebug/test-keys

    Security Patch:
    2019/12/05

    Radio/Modem/Baseband Version:
    MOLY.LR12A.R3.MP.V98.P16

    Download:
    https://www.mediafire.com/file/7fs4...V011-Q-0623_QP1A.190711.020_by-VD171.zip/file

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

    How to flash it?
    Use the attached scatter file.

    Radio/Modem/Baseband properties:
    Code:
    md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V98_P16_2020_04_05_21_55.xz
    md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V98_P16_2020_04_22_12_37.xz
    md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V98_P16.EDB
    md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V98_P16.XML.GZ
    md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V98_P16.EDB

    Prop.default:
    Code:
    ro.build.version.incremental=6
    ro.odm.build.version.incremental=6
    ro.vendor.build.version.incremental=6
    ro.build.version.security_patch=2019-12-05
    ro.vendor.build.security_patch=2019-12-05
    ro.build.display.id=AL2615-lanceelot-V011-Q-0623
    ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.9.1_huaqin.q0mp1.k69v1.64_P17
    ro.build.product=lancelot
    ro.product.board=lancelot
    ro.product.odm.device=lancelot
    ro.product.odm.model=lancelot
    ro.product.odm.name=lancelot
    ro.product.product.device=lancelot
    ro.product.product.model=lancelot
    ro.product.product.name=lancelot
    ro.product.system.device=lancelot
    ro.product.system.model=lancelot
    ro.product.system.name=lancelot
    ro.product.vendor.device=lancelot
    ro.product.vendor.model=lancelot
    ro.product.vendor.name=lancelot
    ro.build.flavor=lancelot-userdebug
    ro.build.description=lancelot-userdebug 10 QP1A.190711.020 6 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/lancelot/lancelot:10/QP1A.190711.020/6:userdebug/test-keys
    ro.odm.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/6:userdebug/test-keys
    ro.product.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/6:userdebug/test-keys
    ro.system.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/6:userdebug/test-keys
    ro.vendor.build.fingerprint=Redmi/lancelot/lancelot:10/QP1A.190711.020/6: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=Tue Jun 23 16:00:24 CST 2020
    ro.build.date=Tue Jun 23 16:00:24 CST 2020
    ro.odm.build.date=Tue Jun 23 16:00:24 CST 2020
    ro.product.build.date=Tue Jun 23 16:00:24 CST 2020
    ro.system.build.date=Tue Jun 23 16:00:24 CST 2020
    ro.vendor.build.date=Tue Jun 23 16:00:24 CST 2020

    MD5 hashes:
    Code:
    APDB_MT6768_S01__W2006 -> 7177e8c1bb17e5fd98f0e6723799c50d
    boot-debug.img -> 8cd7eda58701088c5080fc18eee2d01b
    boot.img -> 81cc18e714ea49a328f6f4da95d08268
    cache.img -> df336c69fc9169d8c248bf0159dabd19
    Checksum.ini -> 37b76d2bc20b7da2f98f68d64b2c2390
    crclist.txt -> e5f360ad6f480f9635cca523487d1936
    cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
    DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V98_P14_2020_04_02_09_21_1_ulwctg_n -> b98ee0dd6410d951a97dc06195ba83e8
    dtb.img -> bfe051e750bab9942d3509be26852f76
    dtbo-verified.img -> 4849e7b4147d1f145b6cabeb89ad75f4
    dtbo.img -> 4849e7b4147d1f145b6cabeb89ad75f4
    efuse.img -> 421f2cead0fbea555680b96136555941
    exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
    lk-verified.img -> 03f3abe6f7b74eae1bb2faf5117662b3
    lk.img -> 03f3abe6f7b74eae1bb2faf5117662b3
    logo.bin -> e72a0fbf91e0efcc13012c71312fc376
    md1arm7.img -> a0453e723dc84255940d7791740d06db
    md1img-verified.img -> 8be0824b8be8d366c08a346df1d73a76
    md1img.img -> 8be0824b8be8d366c08a346df1d73a76
    md3img.img -> 9a9c185e3f6234103e5949716b9962d2
    MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.XML.GZ -> 376361df52cddd8e2d8127c009ad9a97
    MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.EDB -> 762c8ba299c76dde214394d8e7e3fc7e
    MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V98_P14_1_ulwctg_n.EDB -> a5757c7b6acf3e52ce051d731f1e11ab
    MT6768_Android_scatter.txt -> 49ccb3ee5ebcd5a1da213f6e6a97f6e0
    preloader.img -> 97d4bf8c5d7eb7077242643355154121
    preloader_emmc.img -> 97d4bf8c5d7eb7077242643355154121
    preloader_lancelot.bin -> 3d78e9cdf37504c6f4b6e085b9c0ed23
    preloader_ufs.img -> 2ca4e781fc1716fb9f818fd3bc13708a
    product.img -> 8a2a3b2e34c7ad615385f52a578ac19e
    ramdisk-debug.img -> e983139c5a4a17f856b48a9168462246
    ramdisk-recovery.img -> 83730e31866842708346352df1364019
    ramdisk.img -> b280f1a76fd113fa4a2819c131bd5a4b
    recovery.img -> 85a47773595b006fd430826f5b88d76c
    scp-verified.img -> fad098e9a4ac55809437bcda5702d5e2
    scp.img -> fad098e9a4ac55809437bcda5702d5e2
    secro.img -> 096587b863e1252d67b1b8307291db09
    sparsecrclist.img -> 9a027470a494d216f144b6a2ac86c440
    sparsecrclist.txt -> ff3cdb1767f609ccd66fb994b02e030a
    spmfw-verified.img -> 34c71ef9e7b790d06b1c935a36d41c7c
    spmfw.img -> 34c71ef9e7b790d06b1c935a36d41c7c
    sspm-verified.img -> 49adc450b2c4aca22ed17a59064e4dc3
    sspm.img -> 49adc450b2c4aca22ed17a59064e4dc3
    super.img -> fd0ac354f4e40d4ffb9fd4e11b9d2e3b
    super_empty.img -> a6d56d7a12d989bf31511d866449291d
    system.img -> dab92acecad053e31bebe8d2872029b5
    tee-verified.img -> 25e64f2ddb3d8cffa1fd6a1f7d2137a2
    tee.img -> 25e64f2ddb3d8cffa1fd6a1f7d2137a2
    userdata.img -> fc22c593b15f28f4fe0f9a462334ea70
    vbmeta.img -> d763d4e03d647df580e193da6c046b5b
    vbmeta_system.img -> 51618fef8d4e5c535c5c779a4cf4e8b7
    vbmeta_vendor.img -> 4c12ab0788baad9d32d95dbd33da1442
    vendor.img -> 4878e677e80d6ceaa73c30722682d41f
    3
    How to backup NVDATA ?
    Doing a readback with spflashtool or doing a backup with twrp.
    2
    password doesn't work. i don't understand why it's necessary to encrypt a zip like this when it's the only circulating image to my knowledge. not good for anyone in the future trying to find an engineering rom with potentially no password. going to look for a download elsewhere (hopefully)
    The password is attached on the thread.
    Enjoy
    2
    Thank you man, please someone can post a tutorial how to fix the IMEI with this rom? Normal AT commands is not working :( gives ERROR
    You need MODEM META for that.
    2
    sir can you attach that scatter file please¿? and what i must to do? use that scatter file on both rom files?
    Hi bro, could you help me? I have both Imeis in unknown, with MauiMeta or Modem Meta can I rewrite them? Could you tell me how you did it? You would help me a lot. Thanks.
    Hello.
    Would I need to flash the ENG ROM and then use Meta Modem to do the imei2 rewrite?
    Yes.

    You can repair only imei for slot2 by yourself.
    Only Xiaomi Centre can recover imei for slot1.
    If you try to write the imei for slot1, you will get NV DATA corrupted and your device will be bricked in a bootloop.

    If you want to recover the imei for slot2, just follow this step:
    1. Flash the ENGINEERING ROM.
    2. Enter in META MODE using MODEM META:
    Download: https://androidmtk.com/download-modemmeta-tool
    Guide: https://androidmtk.com/use-modem-meta-tool

    3. Write IMEI for slot2 and keep blank/null for slot1.
    4. Backup NVDATA partition.
    5. Flash any other MIUI (or custom) ROM you want.
    6. Restore NVDATA partition.

    Done.