Di mana Anda mendapatkan kernel stormbreaker. Saya mencarinya selama sehari sekarang.
thisWhere did you get the stormbreaker kernel. Im searching for it for a day now.
Di mana Anda mendapatkan kernel stormbreaker. Saya mencarinya selama sehari sekarang.
thisWhere did you get the stormbreaker kernel. Im searching for it for a day now.
Man, saving imei 1 and 2 at the same time did not caused phone to brick?ALHAMDULILLAH MAGRIB 24/06/2021 I got a solution and my cellphone works normally again without having an additional kernel in it. trial with backup files from twrp & backups from mauimeta "updateparameter" from redmi 9 has a brother.
the process:
1. just write imei 2 then backup ditwrp all except super files
2. I use kernel to write imei 1&2 then
3. after the imei is written and I reboot the cellphone into twrp and restore the backup results as a whole
4. when finished, open Mauimeta immediately, unplug it and immediately plug in the usb so it's easy to read Mauimeta, run the process until it opens read IMEI (if only IMEI 2 is listed click write without filling IMEI 1)
5. Open in Mauimeta update parameters, click the normal redmi cellphone backup file option, then click download to flash.
6. reboot see the results, the original kernel from xiaomi and can update software normally.
1000% success Thank God this is finished for the IMEI stage Later, I will search for the system
I've tried like you said, imei 1 cannot be written still, kernel bugs and won't allow me to run miui12 normally (had to reinstall all again).no boss. 1. backup only says imei 2 (kernel is still original)
2. write imei 1 and 2 followed by install kernel strombreaker v1.0
3. restore backup
How to backup NVDATA ?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.
Doing a readback with spflashtool or doing a backup with twrp.
You should never flash using the "format all" mode, or you will lose imei and mac.Kind of new to xiomi. I waited 1 week to unlock bootloader. After unlocking i tried to install twrp recovery. On fastboot boot recovery.img command my phone went to bootloop. It wont stop even when my battery depleted completely. Whenever i connect it with pc bootloop starts again without pressing anything. I was frustrated then with sp tool mistakenly formatted phone without any system backup. Eventually i flashed downgraded stock rom. But my bootloader somehow locked again. Don't know how! And now my imei gone. Can't follow previous bootloader unlock process, cause adding account in mi unlock status reauires active sim card inserted. So now i can't take backup after changing imei in eng rom. Just imei lost. Everything else works. Am I missing something here? Any suggestion?
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
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
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
Doing a readback with spflashtool or doing a backup with twrp.
The password is attached on the thread.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)
You need MODEM META for that.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
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.
Yes.Hello.
Would I need to flash the ENG ROM and then use Meta Modem to do the imei2 rewrite?