I'LL UPLOAD MY RMX2151 FULL BACKUP SOON, STAY TUNED
Bro i need Realme 7 2151 all partition backup except super and userdata I have mtk client tool so please send me on telegram my id is @its_mee_ghanubanna94
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Please
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
Which stok rom u have installed in your realme 7 please
Please
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
Which stok rom u have installed in your realme 7 please
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
I tried all bin file by mtk client tool after recovery flash ozip A.91 file on realme 7 2151 but now baseband unknown after/ before no chance
Please tell me which Stok rom you now running on your realme realme 7 2151
Please
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
Which stok rom u have installed in your realme 7 please
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
Bro you have baseband unknown issue or not
Before you have faced baseband unknown issue or not
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
Which issue are you face now at that time realme 7 2151
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
I have recover my imei number through root by magisk with twrp
realme 7 2151
@Ghanshyam_parmar said:
I have recover my imei number through root by magisk with twrp
realme 7 2151
Click to expand...
Click to collapse
But baseband unknown issue is not gone no worry in future I will fix it also
@Ghanshyam_parmar said:
But baseband unknown issue is not gone no worry in future I will fix it also
Click to expand...
Click to collapse
To fix your baseband follow this:
1 reboot to custom recovery
2 go to mount and select nvram, nvdata partitions and mount them
3 go to advanced, select file manager.
4 navigate to /nvdata/md/nvram and delete that folder
5 reboot, your baseband should be fixed.
Mark Yngell Kate said:
REALME 7 RMX2151 FULL PARTITION BACKUP INCLUDING NVRAM, NVDATA, CAMCPU OPPOCUSTOM ETC.
-markyngellkate
Click to expand...
Click to collapse
How do you recommend to flash it ,
Mtkclient or twrp recovery??
This is a .rar file so I take it it should be mtkclient backup.
magnumoZeus said:
How do you recommend to flash it ,
Mtkclient or twrp recovery??
This is a .rar file so I take it it should be mtkclient backup.
Click to expand...
Click to collapse
yes mtk client
Mark Yngell Kate said:
I'LL UPLOAD MY RMX2151 FULL BACKUP SOON, STAY TUNED
Click to expand...
Click to collapse
Plz upload full back up
Related
Hello, I can not upload a ROM stock from the MIUI website in any way by the MiFlash program or by TWRP.
_theos_ said:
Hello, I can not upload a ROM stock from the MIUI website in any way by the MiFlash program or by TWRP.
Click to expand...
Click to collapse
Miflash does not work for me, flash OrangeFox recovery and try to update, this method worked for me without issues miui_MI8LiteGlobal_V10.3.1.0.PDTMIXM_8f2efd3fd2_9.0 global version... this is name of rom and rom must contain system.new.dat.br file and similar files ending with dat, br.....make folder log inside Miflash root folder. This may help
Stefke93 said:
Miflash does not work for me, flash OrangeFox recovery and try to update, this method worked for me without issues miui_MI8LiteGlobal_V10.3.1.0.PDTMIXM_8f2efd3fd2_9.0 global version... this is name of rom and rom must contain system.new.dat.br file and similar files ending with dat, br.....make folder log inside Miflash root folder. This may help
Click to expand...
Click to collapse
I flash orangefox and nothing else gave me further error 7 pops up
_theos_ said:
I flash orangefox and nothing else gave me further error 7 pops up
Click to expand...
Click to collapse
Strange, try to wipe vendors, system etc... and then mount partitions in OrangeFox. Also disable siignature check and other stuff's... try to flash dm-verity disabler first...you can try also Pitch black recovery
Stefke93 said:
Strange, try to wipe vendors, system etc... and then mount partitions in OrangeFox. Also disable siignature check and other stuff's... try to flash dm-verity disabler first...you can try also Pitch black recovery
Click to expand...
Click to collapse
ok thank you for your help
Can someone please help me,I always receive error from sp flash tool "error status sec img type mismatch (0xc00202a)"
I'm trying to flash nvram and nvdata in redmi 6A,
Thank you
anybody?
jasmin811 said:
Can someone please help me,I always receive error from sp flash tool "error status sec img type mismatch (0xc00202a)"
I'm trying to flash nvram and nvdata in redmi 6A,
Thank you
Click to expand...
Click to collapse
jasmin811 said:
Can someone please help me,I always receive error from sp flash tool "error status sec img type mismatch (0xc00202a)"
I'm trying to flash nvram and nvdata in redmi 6A,
Thank you
Click to expand...
Click to collapse
jasmin811 said:
Can someone please help me,I always receive error from sp flash tool "error status sec img type mismatch (0xc00202a)"
I'm trying to flash nvram and nvdata in redmi 6A,
Thank you
Click to expand...
Click to collapse
Hi. This error generally means that you are trying to flash a wrong file or corrupted one. Make sure you are flashing file with name nvdata.img and nvram.bin in the nvdata and nvram partitions respectively.
A favor you could do to me is that I am right now suffering from a little similar problem. I have lost nvram and nvdata. Could you please send me nvdata and nvram backup. I swear to God that I won't steal your IMEI. I will change them back to mine. I have them. I just need these two files to get out of this problem. I am right now. Please help me. I have same phone. Redmi 6a
jasmin811 said:
Can someone please help me,I always receive error from sp flash tool "error status sec img type mismatch (0xc00202a)"
I'm trying to flash nvram and nvdata in redmi 6A,
Thank you
Click to expand...
Click to collapse
Try redowbload another version or another host download fasboot zip
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
Do you flash it using sp flash tool?
Tmi313 said:
Do you flash it using sp flash tool?
Click to expand...
Click to collapse
You can flash it using sp flash tool or fastboot too.
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
yoalcuadrao said:
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
Click to expand...
Click to collapse
You need MODEM META for that.
VD171 said:
You need MODEM META for that.
Click to expand...
Click to collapse
Thank you i can change succesfully IMEI with Maui META but... now how to get back to MIUI 11 without lost again IMEIS? when i try to flash with SP Flashtool it says PMT changed and i must format again
yoalcuadrao said:
Thank you i can change succesfully IMEI with Maui META but... now how to get back to MIUI 11 without lost again IMEIS? when i try to flash with SP Flashtool it says PMT changed and i must format again
Click to expand...
Click to collapse
If you write the IMEI to the slot1, your device will be stucked in bootloop.
You need to keep blank and null the imei for slot1.
Only xiaomi centre can recover the imei for slot1.
Just write only imei for slot2 and everything will works perfectly.
About PMT changed error, you need to use the SAME scatter file !
If you face any other issue, try attaching the screenshot too
VD171 said:
If you write the IMEI to the slot1, your device will be stucked in bootloop.
You need to keep blank and null the imei for slot1.
Only xiaomi centre can recover the imei for slot1.
Just write only imei for slot2 and everything will works perfectly.
About PMT changed error, you need to use the SAME scatter file !
Just use the scatter file "WITHOUT_EFUSE--no_boundary_check", it will work for engineering roms and release roms.
If you face any other issue, try attaching the screenshot too
Click to expand...
Click to collapse
sir can you attach that scatter file please¿? and what i must to do? use that scatter file on both rom files?
yoalcuadrao said:
sir can you attach that scatter file please¿? and what i must to do? use that scatter file on both rom files?
Click to expand...
Click to collapse
(Sorry. Ignore.)
yoalcuadrao said:
Thank you i can change succesfully IMEI with Maui META but... now how to get back to MIUI 11 without lost again IMEIS? when i try to flash with SP Flashtool it says PMT changed and i must format again
Click to expand...
Click to collapse
if you want to restore them you can use a custom recovery, i suggest you the pitch black one, just flash it, then backup the nvram, nvdata, protect_s and protect_f partition using it then when you reflash the normal miui rom you just reflash the recovery before first system boot and restore the backup you made (you have to put the backup in a sd card or else you will lose it) don't forget to unlock the bootloader as each times you flash the phone you need to format all
razers211 said:
if you want to restore them you can use a custom recovery, i suggest you the pitch black one, just flash it, then backup the nvram, nvdata, protect_s and protect_f partition using it then when you reflash the normal miui rom you just reflash the recovery before first system boot and restore the backup you made (you have to put the backup in a sd card or else you will lose it) don't forget to unlock the bootloader as each times you flash the phone you need to format all
Click to expand...
Click to collapse
NEVER TRY TO FLASH USING THE format all MODE !
Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI.
The guide for that, is here: https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
yoalcuadrao said:
Thank you i can change succesfully IMEI with Maui META but... now how to get back to MIUI 11 without lost again IMEIS? when i try to flash with SP Flashtool it says PMT changed and i must format again
Click to expand...
Click to collapse
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.
VD171 said:
You need MODEM META for that.
Click to expand...
Click to collapse
Hello.
Would I need to flash the ENG ROM and then use Meta Modem to do the imei2 rewrite?
yoalcuadrao said:
sir can you attach that scatter file please¿? and what i must to do? use that scatter file on both rom files?
Click to expand...
Click to collapse
PathBoy92 said:
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.
Click to expand...
Click to collapse
PathBoy92 said:
Hello.
Would I need to flash the ENG ROM and then use Meta Modem to do the imei2 rewrite?
Click to expand...
Click to collapse
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.
the baseband version of this rom is
MOLY.LR12A.R3.MP.V98.P16
but for the global Redmi 9 it is:
MOLY.LR12A.R3.MP.V98.P57
this incompatibility is probably why you cannot restore both IMEIs with it.
shemmati said:
the baseband version of this rom is
MOLY.LR12A.R3.MP.V98.P16
but for the global Redmi 9 it is:
MOLY.LR12A.R3.MP.V98.P57
this incompatibility is probably why you cannot restore both IMEIs with it.
Click to expand...
Click to collapse
Yes
VD171 said:
Yes
Click to expand...
Click to collapse
so, is there a way we can change the baseband version of this rom or grab a rom with the correct baseband version?
shemmati said:
so, is there a way we can change the baseband version of this rom or grab a rom with the correct baseband version?
Click to expand...
Click to collapse
Did you try to flash only the md1img.img ?
VD171 said:
Did you try to flash only the md1img.img ?
Click to expand...
Click to collapse
i manually changed the AP DP folders and the md1img and flashed the rom again, the baseband version changed to P57. the previously written IMEIs are there, but no network.
erased NVRAM and NVDATA to write the IMEIs again, but ModemMeta couldn't write IMEIs to the phone anymore.
who makes these Engineering Roms? where do these roms come from?
maybe we can beg them give us our version or at least guide us how to solve this baseband version problem.
FOR DUAL SIM IMEI REDMI 9
REDMI 9 IMEI NULL/ERROR
1. PREPARE rom_eng/CSC according to each device, take the file preload&cust&md1img to be replaced or moved to a global rom
(use: when reading dimauimeta it's easier & can directly write imei , remember only imei
2, if you want everything you have to install the STROMBAKER FOR LANCELOT kernel)
2. Direct flash global rom version preferably below 11.8.O (remember to replace 3 files numbered 1), after flashing, open Mauimeta and click connect, just unplug and plug it in directly without having to turn it off, write only IMEI 2 (safe for initial boot and backup process), then disconnect & turn on the cellphone normally.
3. After the main menu appears, just check the IMEI has appeared in *#06# or in the settings, if you can unlock the bootloader, you can go to the next stage.
4. unlockbootloader, install twrp preferably version 3.5.2, then in twrp backup only nvdata & nvram& boot, then install strombreaker kernel or special interest in lancelot.
5. directly open Mauimeta click connect, in twrp just restart the system and finally Mauimeta reads automatically, then enter both IMEI and restart again, and check IMEI *#06#
6. if you want to keep using the kernel, you don't have to continue this step, but if you want the original kernel, we continue.
back to twrp, just restore the backup results and restart, check the imei, both are still complete and change only the kernel (return to the original kernel)
7. I tried to upgrade to a rom, the only remaining IMEI 2, if you want 2 IMEI to read, do the above steps again.
ATTENTION: do not update the rom for sure the imei will be lost.
my advice:
MAUIMETA ~ requires preload reading which I suggest replacing earlier & cdc (well, we install this cdc manually, download the file, when Mauimeta asks for our cdc in the computer manager and we install it manually on the reading in question in the computer manager).
LIBUSB~ is useful for locking the mtk preload when first plugged into the computer.
BYPASSMTK~ is useful for locking preloads but with preload changed from rom_eng, so bypass software is not needed when flashing.
so the important thing from these 3 points is the cdc file
very few people want to explain this wide in my opinion.
thanks for CAMMARA.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote Reply
Report
[IMG alt="Raiz"]https://forum.xda-developers.com/data/avatars/s/8020/8020437.jpg?1606891852[/IMG]
RaizForum Moderator
Staff member
12 minutes ago
SEE YOU NOW said:
FOR DUAL SIM IMEI REDMI 9
REDMI 9 IMEI NULL/ERROR
1. PREPARE rom_eng/CSC according to each device, take the file preload&cust&md1img to be replaced or moved to a global rom
(use: when reading dimauimeta it's easier & can directly write imei , remember only imei
2, if you want everything you have to install the STROMBAKER FOR LANCELOT kernel)
2. Direct flash global rom version preferably below 11.8.O (remember to replace 3 files numbered 1), after flashing, open Mauimeta and click connect, just unplug and plug it in directly without having to turn it off, write only IMEI 2 (safe for initial boot and backup process), then disconnect & turn on the cellphone normally.
3. After the main menu appears, just check the IMEI has appeared in *#06# or in the settings, if you can unlock the bootloader, you can go to the next stage.
4. unlockbootloader, install twrp preferably version 3.5.2, then in twrp backup only nvdata & nvram& boot, then install strombreaker kernel or special interest in lancelot.
5. directly open Mauimeta click connect, in twrp just restart the system and finally Mauimeta reads automatically, then enter both IMEI and restart again, and check IMEI *#06#
6. if you want to keep using the kernel, you don't have to continue this step, but if you want the original kernel, we continue.
back to twrp, just restore the backup results and restart, check the imei, both are still complete and change only the kernel (return to the original kernel)
7. I tried to upgrade to a rom, the only remaining IMEI 2, if you want 2 IMEI to read, do the above steps again.
ATTENTION: do not update the rom for sure the imei will be lost.
my advice:
MAUIMETA ~ requires preload reading which I suggest replacing earlier & cdc (well, we install this cdc manually, download the file, when Mauimeta asks for our cdc in the computer manager and we install it manually on the reading in question in the computer manager).
LIBUSB~ is useful for locking the mtk preload when first plugged into the computer.
BYPASSMTK~ is useful for locking preloads but with preload changed from rom_eng, so bypass software is not needed when flashing.
so the important thing from these 3 points is the cdc file
very few people want to explain this wide in my opinion.
thanks for CAMMARA.
Click to expand...
Click to collapse
I tried it with Miui 12.5 with android 11 and it didn't worked. I mean, I already had the IMEI 2 written and working, but when I installed the stormbreaker kernel it was softbricked, and not detected by MauiMETA. So I didn't go any further. Is there any advice for this?
migueacastro said:
Saya mencobanya dengan MIUI 12.5 dengan Android 11 dan tidak berhasil. Maksud saya, IMEI 2 saya sudah ditulis dan berfungsi, tetapi ketika saya menginstal kernel stormbreaker itu menjadi softbrick, dan tidak terdeteksi oleh MauiMETA. Jadi saya tidak melangkah lebih jauh. Apakah ada saran untuk ini?
Click to expand...
Click to collapse
It's still giving me that problem, I mean, it softbricks after flashing that kernel
migueacastro said:
Itu masih memberi saya masalah itu, maksud saya, itu softbricks setelah menginstal kernel itu
Click to expand...
Click to collapse
kernel use if you done flash rom global and can open menu normal
after that you instal kernel
if you instal kernel after flash, you phone will error to register activation
i am indonesia, very hard to english language
What flash tool did you use
Did you flash in fastboot? Sorry im newbiee
kazuhiko23124 said:
Did you flash in fastboot? Sorry im newbiee
Click to expand...
Click to collapse
the essence of writing imei is only preload from rom_eng and md1img.img from rom_eng
the process
1. just flash preload and md1img
preload : to read boot without complicated bypass
md1img : for imei writing permission
after flash md1img we must format nvdata and nvram from flashtool so that no errors occur when entering Mauimeta (data format is in scatter)
2. For IMEI writing, use the Mauimeta application, IMEI writing is only for IMEI Sim2, if all are written, there will be an error.
3. If you want 2 IMEIs to be written, you have to complete the above process until the start menu opens, then go back to TWRP, install the Strombreaker kernel, then open Mauimeta again, just write down all IMEIs (kernel works fine on ROM 11.0.9 or above)
required files:
1.preload.bin from rom_eng
2.md1img.img from rom_eng
3.mauimeta good version 10
4.cdc driver for advanced reading of mauimeta
5. flashtool with DA and AUTH, can be used bypass
6.unlockbootloader for those who want to use the strombreker kernel via twrp,
7. the root process is easier in minimaladb
100% success guaranteed
hckbkl said:
the essence of writing imei is only preload from rom_eng and md1img.img from rom_eng
the process
1. just flash preload and md1img
preload : to read boot without complicated bypass
md1img : for imei writing permission
after flash md1img we must format nvdata and nvram from flashtool so that no errors occur when entering Mauimeta (data format is in scatter)
2. For IMEI writing, use the Mauimeta application, IMEI writing is only for IMEI Sim2, if all are written, there will be an error.
3. If you want 2 IMEIs to be written, you have to complete the above process until the start menu opens, then go back to TWRP, install the Strombreaker kernel, then open Mauimeta again, just write down all IMEIs (kernel works fine on ROM 11.0.9 or above)
required files:
1.preload.bin from rom_eng
2.md1img.img from rom_eng
3.mauimeta good version 10
4.cdc driver for advanced reading of mauimeta
5. flashtool with DA and AUTH, can be used bypass
6.unlockbootloader for those who want to use the strombreker kernel via twrp,
7. the root process is easier in minimaladb
100% success guaranteed
Click to expand...
Click to collapse
The preload and md1mg will be copied from rom eng? And then move it to global rom(11.0.9)? And then flash it?
kazuhiko23124 said:
The preload and md1mg will be copied from rom eng? And then move it to global rom(11.0.9)? And then flash it?
Click to expand...
Click to collapse
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
hckbkl said:
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
Click to expand...
Click to collapse
If I already have miui 11.0.9 , i will just flash it just like this?
z
hckbkl said:
no,
flashing version 11.0.9.
after than flash just preload & md1img,
than you will bee write imei with mauimeta
remember only imei simcard 2 if you not instaling kernel
step
1.flasing v11.0.9
2.unlockboitloader & instal twrp
3.flash md1img & preload rom_eng
4.format nvdata & nvram, addres & partition in scatter rom folder image
5.open mauimeta write imei simcard2(if not use kernel),if 2 imei write after write imei you reboot to twrp and instaling kernel(best strombreaker)
enjoy
Click to expand...
Click to collapse
or i will just replace the preloader and md1img from eng rom in miui 11 and then flash it in fastboot? if yes sir, which preloader i will choose preloader.img, preloader_emmc.img, pre loader_lancelot.bin or pre loader.ufs?
kazuhiko23124 said:
View attachment 5394409or i will just replace the preloader and md1img from eng rom in miui 11 and then flash it in fastboot? if yes sir, which preloader i will choose preloader.img, preloader_emmc.img, pre loader_lancelot.bin or pre loader.ufs?
Click to expand...
Click to collapse
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
hckbkl said:
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
Click to expand...
Click to collapse
I still dont get it sir, im sorry I am too newbie for this
hckbkl said:
after flash you format nvdata & nvram.
after that open mauimeta write imei simcard 2.reboot
Click to expand...
Click to collapse
how to format nvdata and nv ram sir
kazuhiko23124 said:
cara memformat nvdata dan nv ram pak
Click to expand...
Click to collapse
open scatter in your rom v11.0.9
in folder image ,open scatter.txt copy addres number & partition number to spflashtool(nvdata & nvram search)
format manual in spflastool like flash rom
after that open mauimeta to write imei simcard 2
kazuhiko23124 said:
how to format nvdata and nv ram sir
Click to expand...
Click to collapse
news trick
# for not unlock bootloader
1.preload.bin and md1img.img from rom_eng
2. flash format&download or flash download rom version 11.0.9 (insert or replace the preload file from rom_eng)
3. when finished, flash only md1img from rom_eng then format nvdata (the format code number is discatter)
4. after that open mauimeta(cdc drive is needed to read imei) write only imei simcard 2, reboot
5. Please enter micloud & register for the unlockbootloader process if needed.
# for already unlocked bootloader
6. root hp & go to twrp install strombreaker kernel, restart and enter mauimeta write both imei simcard 1 & 2
7. flash again using rom version 11.0.9 uncheck recovery, vbmeta (all vbmeta), userdata, super, boot, logo, md1img.
hckbkl said:
news trick
# for not unlock bootloader
1.preload.bin and md1img.img from rom_eng
2. flash format&download or flash download rom version 11.0.9 (insert or replace the preload file from rom_eng)
3. when finished, flash only md1img from rom_eng then format nvdata (the format code number is discatter)
4. after that open mauimeta(cdc drive is needed to read imei) write only imei simcard 2, reboot
5. Please enter micloud & register for the unlockbootloader process if needed.
# for already unlocked bootloader
6. root hp & go to twrp install strombreaker kernel, restart and enter mauimeta write both imei simcard 1 & 2
7. flash again using rom version 11.0.9 uncheck recovery, vbmeta (all vbmeta), userdata, super, boot, logo, md1img.
Click to expand...
Click to collapse
What is hp sir
You mean root my device? And then Im going to install twrp? If I successfully installed the twrp, Im going to reboot my device? And enter mauimeta? (In what state fastboot or just turn off the phone for entering mauimeta?)
Then if im successfully write both imei 1 and 2
Im going to flash the miui 11.0.9 and uncheck recovery, vbmeta, user data, super, boot, logo, md1mg?( in fastboot too?)
As the title says ,
My IMEI is Null and Baseband is Unknown after flashing and the boot and recovery going corrupt
tried flashing the GSI , tried flashing stock rom using MTK client but its still the same ,
anyone has the right mtk AP DB file database for our mtk 6893 to flash the imei ?
the last AP DB file databse is only updated till march of 2022 and there is no
AP DB database file for mt 6893.
Any idea how i can flash imei on our device ?
Also Everything works except imei and fingerprint .
You have overwritten persist.img which is partition responsible for fingerprint. You cannot flash any other devices persist partition to fix it as it is unique for every device. Give your phone to OnePlus service center.
PattasuBalu said:
You have overwritten persist.img which is partition responsible for fingerprint. You cannot flash any other devices persist partition to fix it as it is unique for every device. Give your phone to OnePlus service center.
Click to expand...
Click to collapse
Well the thing here is the service center wants to shell out money from me by claiming the motherboard is damaged due to water which is false . Water did go in my cellphone 4 to 5 months back and the problem right now is because of my boot.img and recovery going corrupt due to wrong firmware flashing . Now for fingerprint i believe you its the persist image , regarding the imei its the nvram i dont know exactly which one . Service center did flash my mobile as per their claims but still the cellphones imei and fingerprint is not working and i think thats because they might have flashed the wrong files or they just wanted to shell out money thats all i can say .
Apart from the service center advice , if anyone has the twrp backup of their partions please give me a link or let me know or some other way to flash the imei of our device by flashing the mediateks 6893 imei , i can see how other people are flashing their imei devices using the mediateks tool SP write one , but there are no base band files for our 6893 / 1200 dimensity to flash the imei .
rohit4989 said:
Well the thing here is the service center wants to shell out money from me by claiming the motherboard is damaged due to water which is false . Water did go in my cellphone 4 to 5 months back and the problem right now is because of my boot.img and recovery going corrupt due to wrong firmware flashing . Now for fingerprint i believe you its the persist image , regarding the imei its the nvram i dont know exactly which one . Service center did flash my mobile as per their claims but still the cellphones imei and fingerprint is not working and i think thats because they might have flashed the wrong files or they just wanted to shell out money thats all i can say .
Apart from the service center advice , if anyone has the twrp backup of their partions please give me a link or let me know or some other way to flash the imei of our device by flashing the mediateks 6893 imei , i can see how other people are flashing their imei devices using the mediateks tool SP write one , but there are no base band files for our 6893 / 1200 dimensity to flash the imei .
Click to expand...
Click to collapse
Try this https://miaccountguide.com/mtk-imei-repair-tool-download/
Chaitanya Dixit said:
Try this https://miaccountguide.com/mtk-imei-repair-tool-download/
Click to expand...
Click to collapse
tried that already , doesnt work for nord 2 .
rohit4989 said:
tried that already , doesnt work for nord 2 .
Click to expand...
Click to collapse
You dont have your mtkclient partition backup?
Chaitanya Dixit said:
You dont have your mtkclient partition backup?
Click to expand...
Click to collapse
Nope , can you send me your mtk client backup ? if its working ?
rohit4989 said:
Nope , can you send me your mtk client backup ? if its working ?
Click to expand...
Click to collapse
PattasuBalu said:
You have overwritten persist.img which is partition responsible for fingerprint. You cannot flash any other devices persist partition to fix it as it is unique for every device. Give your phone to OnePlus service center.
Click to expand...
Click to collapse
Bro I don't think there would be any such thing as unique partition or something , that would be just an overkill for a phone that costs 30k . See this link how the calibration of fingerprint is done through engineer mode I guess and also I think oneplus just doesn't want to give the appropriate files for flashing. The phone is not listed on the main site , there are no official files to flash the device . Like you make a mid range flagship and delist it within 1 year of production from your main website ? Sorry for the rant but see this fingerprint calibration video and also I think the information regarding the fingerprint would be wrong regarding the persist image file , that's just overkill hardware spec on a phone that costs 30000
rohit4989 said:
Nope , can you send me your mtk client backup ? if its working ?
Click to expand...
Click to collapse
https://files.giovix92.workers.dev/0:/OnePlus Nord 2/Stock ROMs/ Download appropriate firmware and try to restore via mtkclient.
Chaitanya Dixit said:
https://files.giovix92.workers.dev/0:/OnePlus Nord 2/Stock ROMs/ Download appropriate firmware and try to restore via mtkclient.
Click to expand...
Click to collapse
Did that already, it still won't fix the imei , can you give me the link of vcom drivers please ? I uninstalled my vcom drivers and now I can't find it
rohit4989 said:
Did that already, it still won't boot up , can you give me the link of vcom drivers ? I uninstalled my vcom drivers and now I can't find it
Click to expand...
Click to collapse
What is the issue? Can you clarify?
Here is the vcom drivers link https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
Chaitanya Dixit said:
What is the issue? Can you clarify?
Here is the vcom drivers link https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
Click to expand...
Click to collapse
If you want scatter file for DN2101
Chaitanya Dixit said:
If you want scatter file for DN2101 then contact me.
Click to expand...
Click to collapse
Can you make a thread and post it ? It would be helpful for all of us xdians
rohit4989 said:
Can you make a thread and post it ? It would be helpful for all of us xdians
Click to expand...
Click to collapse
No brother because it is not signed firmware, for that you need to unlock BL
Chaitanya Dixit said:
No brother because it is not signed firmware, for that you need to unlock BL
Click to expand...
Click to collapse
Bro , when we are flashing a full file from BROM mode it doesnt matter if we have a unlocked BL or Locked BL , i repeat it wont
matter when we are flashing a full firmware through BROM mode if we have a locked BL or unlocked BL
rohit4989 said:
Bro , when we are flashing a full file from BROM mode it doesnt matter if we have a unlocked BL or Locked BL , i repeat it wont
matter when we are flashing a full firmware through BROM mode if we have a locked BL or unlocked BL
Click to expand...
Click to collapse
I tested it already using sp flash tool. Because of verified boot you cant flash scatter file with locked BL.
Chaitanya Dixit said:
I tested it already using sp flash tool. Because of verified boot you cant flash scatter file with locked BL.
Click to expand...
Click to collapse
the whole purpose of sp flash tool is to install a whole new firmware , you can definitely install it with a locked bl or unlocked bl , make sure you are in BROM mode and you have enabled the mtk bypass
Chaitanya Dixit said:
I tested it already using sp flash tool. Because of verified boot you cant flash scatter file with locked BL.
Click to expand...
Click to collapse
can you link me the firmware file where you got the scatter ?
rohit4989 said:
can you link me the firmware file where you got the scatter ?
Click to expand...
Click to collapse
Here is the link https://www.mediafire.com/file/gjnje80ou9vevl1/ONE_PLUS_NORD_2_SCATER_FILE_GsmMafia.Com.rar/file