Develop Bugs

cannot get back my imei no matter what i do

When reflashing my stock ROM after flashing a custom rom, my imei shows as 0 but i still got signal and i can still make calls, my imei just shows 0
I am running 8.1.0 with an unlocked bootloader and
I have the moto g5 cedric varient, i have a EFS and persist backup but tried to restore them just shows 0 on my imei
I have the xt1675 varienr

do you have 4G working?

maserati2011 said:
do you have 4G working?
Click to expand...
Click to collapse
4G works, just my imei shows 0, i also backed up the QCN with qfil, just need help writing to the qcn file

mattwhite7102 said:
4G works, just my imei shows 0, i also backed up the QCN with qfil, just need help writing to the qcn file
Click to expand...
Click to collapse
Reflash the the rom again through LMSA (Lenovo Moto Smart Assistant) on your pc, make sure you select rescue not upgrade, make sure to select the correct G5 code (For example: XT1676)
Also have a look at my own I F*cked up! Help me please? thread, lots of info that might help you there.

maserati2011 said:
Reflash the the rom again through LMSA (Lenovo Moto Smart Assistant) on your pc, make sure you select rescue not upgrade, make sure to select the correct G5 code (For example: XT1676)
Also have a look at my own I F*cked up! Help me please? thread, lots of info that might help you there.
Click to expand...
Click to collapse
Tried it, my imei still shows 0 but on the stock rom i still have my dhob and shob bin files and mfastboot still sees my imei, so my imei is half broken and ill also take a look on that thread

T-Mobile OnePlus 7T Internat'l ROM Version Conversion – Guaranteed Method That Works If All Else Fails

If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible

I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?

dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.

draymond1987 said:
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
Click to expand...
Click to collapse
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?

dimelus said:
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
Click to expand...
Click to collapse
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot

draymond1987 said:
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
Click to expand...
Click to collapse
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm

dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
What I would do, and it's silly but could work. Go back into fastboot and issue the "
fastboot flashing unlock_critical" command, again. I know this happened to me too because I had these errors and I just tried, out of desperation. I dunno if it's because the phone is on the T-mobile software, that it freaks out like that, question mark?

dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Did you not flash 10.0.3HD65AA rom image which is step "I."? If you go out of step and not follow the instructions as they're laid out then of course you're going to have problems.

urbanman2004 said:
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
Click to expand...
Click to collapse
Thanks for your guide lines.. I am a very newby yet 71 years old.. been messing with hardware and software since 1984, always learning. new to Flashing Rom's , I converted two 6T's and 3 7T from TMO to 1+, the third 7T gave me a fit, because I purchased from someone who didn't tell me that someone had tried to convert to dual sim and I had a hard time to solve the issue.. Two things,, for everyone trying to do this.. Branded to Global or Dual Sim, One You have to have the Correct Drivers for Windows for the ADB and Fastboot.. and it has to be setup correctly.. as for some drivers that are signature issue for windows, and you have exclamation mark because of signatures, as for Win10,
restart your windows with Shift key held down and select restart, when it boots into blue screen select "troubleshoot"
from that select " Startup blue secreen. " after that Select Item #7 which is to forces Windows to ignore Signature error reporting. select Start , then go on with your process for Brand to dual sim or Global, etc..
THANK YOU for Your Information and Procedure Steps to Convert from Branded to Dual / Global, etc.. made it very less time consuming...Appreciate You and All those who have given Good Guidance - Thank You

does this method unlock the sim card?

goggolar said:
does this method unlock the sim card?
Click to expand...
Click to collapse
No, you have a completely separate issue. The OnePlus 7T device I purchased already had an unlocked sim card. You need to refer to your phone carrier who provides you service.

It needs the bootloader unlocked?

SBruno said:
It needs the bootloader unlocked?
Click to expand...
Click to collapse
Yep

CaptRicXT912 said:
Gracias por sus lineamientos .. Soy muy nuevo por 71 años .. he estado jugando con hardware y software desde 1984, siempre aprendiendo. nuevo en Flashing Rom's, convertí dos 6T y 3 7T de TMO a 1+, el tercer 7T me encajó, porque le compré a alguien que no me dijo que alguien había intentado convertir a dual sim y tenía un Es difícil resolver el problema. Dos cosas, para todos los que intentan hacer esto. Con la marca Global o Dual Sim, una Debe tener los controladores correctos para Windows para ADB y Fastboot ... y debe estar configurado correctamente ... como para algunos controladores que son un problema de firma para Windows, y tiene un signo de exclamación debido a las firmas, como para Win10,
reinicie sus ventanas con la tecla Shift presionada y seleccione reiniciar, cuando se inicie en la pantalla azul, seleccione "solucionar problemas"
a partir de ahí, seleccione "Pantalla azul de inicio". Después, seleccione el elemento n. ° 7, que obligará a Windows a ignorar el informe de errores de firma. seleccione Inicio, luego continúe con su proceso de Marca a SIM dual o Global, etc.
GRACIAS por su información y procedimiento Los pasos para convertir de marca a dual / global, etc. hicieron que consumiera mucho menos tiempo ... Le agradezco a usted y a todos los que han dado una buena orientación - Gracias
Click to expand...
Click to collapse
seria de mucha ayuda si usted o alguien me ayudara en este problema estoy atascado en la version de android 10 de t-mobile la computadora no reconoce el dispositivo almenos que lo reinicie de fabrica, en modo fastboot no lo reconoce y estoy desesperado soy nuevo en esto

Excellent work, it did the job for mine. Followed your procedure and a couple of interpretations to get through it to the end.
Thank You for the help!

This worked for me, I wasn't even trying to convert my phone.. just restore a soft brick turned semi-hardbrick.
I haven't done android modding since my Zuk Z1! Previously I had modded my Galaxy s3, some LG [it was the one with RGB home button, man I miss that], and Z1. ​​Yesterday I decided I was finally ready to mod my oneplus 7t [hd1907] after 2 years of ownership. Bootloader unlock, Rooted, modded some things, and then Sound wouldn't play in the speakers, wifi dead, hotspot dead, amongst other broken features. Trouble is, I wasn't thinking like I used to and didn't have my img files backed up. All I wanted to do was revert back to the stock firmware.. but I ended up in a softbrick somehow. I can't find tmo op7t firmware anywhere online.. I was going to try flashing it with adb.​​Well I came across your guide here, and when all hope was lost I thought I might as well give it a try.. and it worked! Now instead I'm on international software! Even better than just recovering stock! Well youtube is throwing a connection error but I am hoping it just means I need to update my gapps.. Thank you very much this helped me recover my phone..
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
I actually had "FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS" on the first flash as well, and it never booted properly either. On the second flash I was getting "Invalid sparse file format at header magic".. However in the end of the process my phone was working.
I'm going to update gapps and update firmware to the latest OTA now, which popped up in the notifications already! Thanks again Urbanman.
Edit: "some LG [it was the one with RGB home button, man I miss that]" I checked my post history it was LG optimus G pro.

I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?

k.stahanov73 said:
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
Click to expand...
Click to collapse
Superboy58 msmtool will get u global oos10, then ota to 11.0.9.1 or oos12 global

HueyT said:
Superboy58 msmtool получит u global oos10, затем ota на 11.0.9.1 или oos12 global
Click to expand...
Click to collapse
I can not flash through msm .. at the fastboot stage after a reboot I ALWAYS boot into the old system !! always! already made 50 attempts and changed the cords and ports and no use!

Maybe it's because I have Windows 7?

REDMI NOTE 9 (MERLIN) FINALLY FIRST METHOD TO FIX 1 SLOT IMEI

Hello guys,
This is the first method how to work with both sim 1 and sim 2 Imei's if you mistakly made by 'format all' option in sp flash tool.
WARNINGS:
- Possible risk of data loss ! Backup your files and contents !
- NO dongle and NO box is required.
- NEVER try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI.
- Keep your backup files safe and secure ! If you can, encrypt them.
- Never try to share your backups or your security and privacy will be compromised.
- USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
This method was released by HALABTECH and it's working ONLY with custom rom.
Big thanks to VD171 who shared the patched file.
If somebody has an idea how to implement this patch in stock rom it would be great too..
We need Engineering Rom to be installed first to be able to access meta mode.
Download Maui Meta or Modem Meta to write both original Imei's.
Next,flash the latest Miui rom 12.0.7 global and after it is finished with flashing before it goes to reboot press vol- to enter fastboot mode.
In Fastboot mode flash vbmeta and twrp.
In TWRP at first make format data,then reboot to twrp again,then wipe dalvik,data,cache and flash Pixel Experience custom rom and magisk 22,then make format data again,then restart the phone in fastboot again.
After put your phone in Fastboot Mode extract the patched file,(IMPORTANT) rename it to 'md1img' and flash it exactly like this: fastboot flash md1img md1img.img
Next and last step just reboot it by 'fastboot reboot' and very important thing, at first boot when you see the google logo immediately press the power button to restart the phone to be able to work normally.
Check if you have in both sim slots imeis and signals.
ENG ROM: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
Latest stock rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.7.0.QJOMIXM/
Patched file is in attachment below.

Hi. I've lost ma IMEIs. Hopefully read this guide, but when I've done this steps, the phone goes tho fatboot after restart :/ Please help...

in twrp you must format data,wipe cache,dalvik and data,then close avb2 and disable twrp check in advanced mode.

The patch file is the MD1IMG.img of the ENGINEERING ROM AL2522-Merlin-V039-Q-0513.
Here, you can find this file and other MD1IMG versions for MERLIN:
[BASEBAND][IMG][STOCK][MD1IMG] MODEM Image Partition for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Original Stock MD1IMG.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G What is it? This image partition contains the MODEM/BASEBAND/RADIO. How to flash it? fastboot flash md1img md1img.img (Engineering)...
forum.xda-developers.com

Please share the custom rom, or do I just have to flash this patch.zip

i just flashed pixel experience cleared cache and data after that wrote imei with maui meta latest version by selecting load db from target and it worked for me. though wifi is still showing nvram error but it can still connect to wifi.

UnexpectedUser said:
i just flashed pixel experience cleared cache and data after that wrote imei with maui meta latest version by selecting load db from target and it worked for me. though wifi is still showing nvram error but it can still connect to wifi.
Click to expand...
Click to collapse
You can write MAC too.

sir you said "In Fastboot mode flash vbmeta and twrp." but i cant find vbmeta file.

Moss je vb said:
sir you said "In Fastboot mode flash vbmeta and twrp." but i cant find vbmeta file.
Click to expand...
Click to collapse
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com

after flashing vbmeta and twrp the phone says system has been distroyed. it some how knows i put custom recovery in it. and my boot loader is locked. what can i do ?

Moss je vb said:
after flashing vbmeta and twrp the phone says system has been distroyed. it some how knows i put custom recovery in it. and my boot loader is locked. what can i do ?
Click to expand...
Click to collapse
Flash the miui firmware again and then unlock the bootloader.

nvdata is corupt because i give it imei with eng rom. so when i try to flash stock rom it says nvdata is corupt

VD171 said:
Flash the miui firmware again and then unlock the bootloader.
Click to expand...
Click to collapse
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.

Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
You need to repair your imei using engineering rom and modem meta tool.

Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
silahkan terjemahkan ke english.
banyak tutorial yang membingungkan.
jika ingin unlockbootloader cukup menulis imei sim 2.
jika bermasalah penulisan imei ambil file preload dan md1img dari rom_eng.
jika ingin eksperimen bermainlah di md1img.
----------
MOD EDIT: English Translation Below
please translate to english.
a lot of confusing tutorials.
if you want to unlock bootloader just write imei sim 2.
if you have problems writing imei take the preload and md1img files from rom_eng.
if you want to experiment play on md1img.

hckbkl said:
silahkan terjemahkan ke english.
banyak tutorial yang membingungkan.
jika ingin unlockbootloader cukup menulis imei sim 2.
jika bermasalah penulisan imei ambil file preload dan md1img dari rom_eng.
jika ingin eksperimen bermainlah di md1img.
Click to expand...
Click to collapse
English only.

VD171 said:
English only.
Click to expand...
Click to collapse
sorry bos i am tired translate to english.
i am indonesian man.
me just help my brother in the world.
cobalah saudaraku memahami juga bahasa kami indonesia.

Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
inti dari penulisan imei hanya preload(dari rom_eng) dan md1img.img(bisa pakai md1img.img dari versi lain atau dari rom_eng).
prosesnya
1. flash lebih bagus dengan pilihan "format&download"
2. kita harus backup terlebih dahulu file tambahan bisa dari redmi 9 normal atau kalau mentok ya ponsel kita yang hilang imei.
3. file backup yang saya saranin : nvcfg,nvram,proinfo,protect1,protect2
{file ini kita baca di scatter dari address dan partition, kita ubah NONE menjadi file(contohnya nvcfg.img), false dibawahnya kita ubah menjadi true, ini kita edit melalui note++}
backup ini berguna untuk file tambahan penguat sinyal komunikasi dan data jaringan.
4. boleh flash format total atau hanya file preload dan md1img.img(file rom_eng). setelah flash bagusnya unlockbootloader.
5. format manual menggunakan flashtool nvdata dan nvram (nilai format ada di scatter, address dan partition)
6. buka mauimeta (10.18versi) kita tulis imei 1 dan 2, lalu restart
7. ponsel akan error tapi tenang, kita format lagi dengan flashtool nvdata dan nvram
8. buka lagi mauimeta dan hanya tulis imei sim 2
9. selesai bila kita kembali ke flashtool, kita centang file nvcfg,nvram,proinfo,protect1,protect2,spmw,scp,sspm,tee lalu flash dan restart ponsel
jaringan ponsel akan lebih segar, imei 1 dan 2 terbaca, komunikasi jaringan cepat dan lancar,
catatan :
• perlu dibuat scatter menggunakan note++
• perlu backup file yang diperlukan
• bagikan tutorial ini disitus atau postingan anda untuk membantu saudara kita yang lain.
• jangan mudah percaya situs jaminan terjamin tutorial ampuh
1000% teruji
----------
MOD EDIT: English Translation Below
The essence of writing IMEI is only preload (from rom_eng) and md1img.img (you can use md1img.img from other versions or from rom_eng).
the process
1. flash is better with the "format&download" option
2. We must first backup additional files from the normal redmi 9 or if it's stuck, our cellphone has lost its IMEI.
3. backup files that I recommend: nvcfg,nvram,proinfo,protect1,protect2
{We read this file in the scatter from address and partition, we change NONE to a file (for example nvcfg.img), we change false below it to true, we edit this via note++}
This backup is useful for additional files of communication signal boosters and network data.
4. You can flash the total format or just the preload file and md1img.img(rom_eng file). after flash the good unlockbootloader.
5. manual format using flashtool nvdata and nvram (format values are in scatter, address and partition)
6. open mauimeta (10.18version) we write imei 1 and 2, then restart
7. the phone will error but calm down, we format it again with flashtool nvdata and nvram
8. Open Mauimeta again and write only IMEI SIM 2
9. finished when we return to flashtool, we check the files nvcfg, nvram, proinfo, protect1, protect2, spmw, scp, sspm, tee then flash and restart the phone
mobile network will be fresher, imei 1 and 2 are read, network communication is fast and smooth,
notes :
• need to create scatter using note++
• need to backup necessary files
• share this tutorial on your site or post to help our other brothers and sisters.
• don't easily trust guaranteed guaranteed tutorial sites, powerful tutorials
1000% tested

hckbkl said:
1000% teruji
Click to expand...
Click to collapse
English only.

VD171 said:
English only.
Click to expand...
Click to collapse
just translate brother

LG G3 D855 Hard Bricked, stuck in bootloop, no DL mode, no Recovery. BoardDiag AP pass, EMMC pass, SDRAM pass

Hey guys I have a problem with my LG G3 D855 model stucked at bootloop.
The deal is that I already tried to short two pins on motherboard and do qualcomm flash with LG BoardDiag tool.
Everithung went well AP pass, EMMC pass and SDRAM pass, all good.
Succesfuly restore all boot images and yet still stuck at bootloop, no download mode and no recovery mode.
I used this TOT file LGD855AT-00-V10e-EUR-XX-JUL-08-2014-16G+0.tot I guess that's the right one.
Tried with both DoardDiag 2.99a and 3.99c. But still with no luck.
My system is Windows 10 64bit, Qualcomm 64 bit version used in Windows test mode.
I followed couple of xda tutorials, and all went fine till the end, without beign able to go into Download Mode.
Any suggestions? Does anybody saw this kind of case?

The only suggestion I can offer is to try a newer firmware. (E.g. V10l) You should be able to extract the newer images from the kdz and use the partition table from the V10e tot, since the sizes don't change.
I had a similar problem when I downgraded to that V10e tot on a replacement board with exchanged eMMC-chip. Got a bootloop and eventually ended up in fastboot, since the kernel obviously could not deal with that type of chip.
If you also end up in fastboot once, you can try a tethered boot to a newer laf (download mode) image to be able to flash with LGUP.

macgyver77 said:
The only suggestion I can offer is to try a newer firmware. (E.g. V10l) You should be able to extract the newer images from the kdz and use the partition table from the V10e tot, since the sizes don't change.
I had a similar problem when I downgraded to that V10e tot on a replacement board with exchanged eMMC-chip. Got a bootloop and eventually ended up in fastboot, since the kernel obviously could not deal with that type of chip.
If you also end up in fastboot once, you can try a tethered boot to a newer laf (download mode) image to be able to flash with LGUP.
Click to expand...
Click to collapse
Hey @macgyver77,
Thanks for you answer
I can only do a flash with BoardDiag Tool, shorting two pins directly on motherboard. But still stuck at bootloop.
I made one mistake telling that I don't have recovery mode. I have it, but it's useless, because when I press factroy reset, it starts and reboots into bootloop again, every time.
So, if I extract KDZ I only get extensions .bin, but with BoardDiag I need extension .mbn.
Did you mean to extract KDZ and use primaryGPT from V10l to V10E TOT or the opposite?
And how to convert from .bin to .mbn or the other way arround?
I can not go into DL mode or ADB mode or FASTBOOT mode.

I don't know what caused this problem for you or why you had to use BoardDiag in the first place, but after I downgraded to V10e (successful flash using LGUP) I saw almost the same behaviour: Bootloops on normal boots, bootloops when trying to get to download mode, recovery apparently worked and cleared data (android robot logo shortly visible), but no effect on bootloops. However, after letting the device bootloop for several times, I eventually ended up in fastboot mode sometimes.
When you try to go to download mode, do you see the "Download mode loading" logo (similar to left picture here: https://lgaristo.com/lg-aristo-ms210-download-mode-recovery-mode-safe-mode/) briefly before the device bootloops?
From what I can see the "mbn" files BoardDiag extracts from the tot file are the same files that the "LG Firmware Extractor" saves as "bin" files, so it should be possible to exchange the files just by renaming. (Compare results from extracting V10e tot with both programs in pics below.)
I never actually had to use Boarddiag to recover, but my idea would have been to flash images from a newer firmware kdz (V10l) with it. However, I saw that the "aboot.img" sizes are different (V10e: 1.5 MB, V10l: 2.0 MB), so I'm not sure about that, because the partition layout may have changed between those versions. My next idea would have been to flash the V10e files using boarddiag, with just the laf partition exchanged to the V10l version. Maybe that would allow to get download mode to work. The "laf.mbn" file I attach here is the partition image from V10l - same size as the V10e image.

macgyver77 said:
I don't know what caused this problem for you or why you had to use BoardDiag in the first place, but after I downgraded to V10e (successful flash using LGUP) I saw almost the same behaviour: Bootloops on normal boots, bootloops when trying to get to download mode, recovery apparently worked and cleared data (android robot logo shortly visible), but no effect on bootloops. However, after letting the device bootloop for several times, I eventually ended up in fastboot mode sometimes.
When you try to go to download mode, do you see the "Download mode loading" logo (similar to left picture here: https://lgaristo.com/lg-aristo-ms210-download-mode-recovery-mode-safe-mode/) briefly before the device bootloops?
From what I can see the "mbn" files BoardDiag extracts from the tot file are the same files that the "LG Firmware Extractor" saves as "bin" files, so it should be possible to exchange the files just by renaming. (Compare results from extracting V10e tot with both programs in pics below.)
I never actually had to use Boarddiag to recover, but my idea would have been to flash images from a newer firmware kdz (V10l) with it. However, I saw that the "aboot.img" sizes are different (V10e: 1.5 MB, V10l: 2.0 MB), so I'm not sure about that, because the partition layout may have changed between those versions. My next idea would have been to flash the V10e files using boarddiag, with just the laf partition exchanged to the V10l version. Maybe that would allow to get download mode to work. The "laf.mbn" file I attach here is the partition image from V10l - same size as the V10e image.
Click to expand...
Click to collapse
I had to use BoardDiag because that's how it's only possible for me to do a flash, because I can go into Download Mode.
When I want to go into DL mode, first show LG logo and then reboots into bootloop. And if I let phone to do a couple of loops phone become very hot under the power button because of the chips.
I tried your method but still the same. I even tried with Marshmellow 6.0. I extracted all files and rename it to .mbn and flash all the nessesery files. And same bootloops.
The Only thing I can think of is to try a new battery. I saw some people on the net with the bootloops, and when they replace old battery with the new one bootloops stops and phone runs normaly.
But the problem is I don't want to buy new battery to find out that it's not the problem
Maybe I can go to some service if they have working battery to try that way, I don't know. Will see.
@macgyver77 thanks a lot for the suggestions ​

estou com mesmo problema, comprei uma placa lg g3 d855 32gb aliexpless,
versão KVT49L.D85510o 4.4 kk, tentei atualizar para Global D85530B_00_1217 pelo LGflashTool2014 não instala, tentei outras versões de rom d855 e nada, ai tentei pelo LGUP a rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, aconteceu isso, loop infinito, não entra em modo download e nem modo recovery,
fiz procedimento pelo BoardDiag 2.99, só consegui extrair a rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, as outras da erro ao extrair , fiz tudo como no como descrito pelo nenadlalos83, consigo entrar modo download, só que não consigo instalar nenhuma rom pelo LGflashTool2014, para 2% antes de instalar,
pelo LGUP consigo instalar as rom LGD855AT-00-V10b-HKG\TWN\EUR, todas instalam mas loop infinito...
alguma idéia possa fazer pra corrigir?
também não achei a rom que veio nele pra download (D85510o 4.4)
só achei essa mas parece instalar pelo twrp, não consigo entra recovery
D85510o.zip | ROM by Xi0N83 for G3 - Android File Host​i have the same problem, i bought a lg g3 d855 32gb aliexpless card,
version KVT49L.D85510o 4.4 kk, I tried to update to Global D85530B_00_1217 through LGflashTool2014 it does not install, I tried other versions of rom d855 and nothing, then I tried through LGUP the rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+ 0, this happened, infinite loop, does not enter download mode or recovery mode,
I did the procedure through BoardDiag 2.99, I was only able to extract the rom LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G+0, the others gave an error when extracting, I did everything as described by nenadlalos83, I can enter mode download, only I can't install any rom by LGflashTool2014, to 2% before installing,
by LGUP I can install the roms LGD855AT-00-V10b-HKG\TWN\EUR, they all install but infinite loop...
Any ideas I can do to fix it?
I also couldn't find the rom that came with it for download (D85510o 4.4)
I just found this one but it seems to install through twrp, I can't enter recovery
D85510o.zip | ROM by Xi0N83 for G3 - Android File Host

Question poco f3 preso no recovery mode.

<Moderator Edit>: English translation added to the top.
My poco f3 was stuck in recovery mode, it has two options: "TRy Again" and "factory data resett", but it doesn't work back to the same screen.
Original:
Meu poco f3 ficou preso no modo recovery, tem duas opções: "TRy Again" e "factory data resett", porém não funciona volta pra mesma tela.

Israel F3 said:
<Moderator Edit>: English translation added to the top.
My poco f3 was stuck in recovery mode, it has two options: "TRy Again" and "factory data resett", but it doesn't work back to the same screen.
Original:
Meu poco f3 ficou preso no modo recovery, tem duas opções: "TRy Again" e "factory data resett", porém não funciona volta pra mesma tela.
Click to expand...
Click to collapse
I'm not sure what you've done to it. Have you unlocked the bootloader and flashed custom ROM or recovery?
With what you said I would say boot into fastboot mode and flash stock firmware with XiaoMiFlash tool.

I seen your message in my notifications and figured no one would answer you because that's how it goes so I figured well he's probably freaking out thinking he broke his phone. If you have done anything to change something like flashing roms or root let me know either way it's probably fixable.
Just don't try to get into EDL mode that's not needed and make sure no one tells you to type adb commands to erase anything people think it's funny to tell people how to erase bootloader and totally hard brick a device.