[Tutorial] Crossflash, Bypass OPID Mismatched Error
- Thread starter netmsm
- Start date
-
- Tags
- crossflash lgup opid
Don't let it take too long to go to "Partition Manager" rather it is required to quickly open "Partition Manager" after getting into EDL mode otherwise QFIL will give error.
I tried to follow this guide, but I got stuck at step A6 (select port and select the phone). It doesn't show up in the list (unless I tick the Show Non QLoader/DIAG Port, at which point the next step returns an error). I have installed the drivers specified. Could anyone help?
It sounds like you didn't install the qualcomm usb driver? It's in the zip file, there are 2 executables in it, one is under the directory 'driver'.
I'm not sure if it should have been installed automatically or not, didn't use that zip myself.
cheers
I'm pretty sure of both. I ran the exe in the driver folder and restarted. I activated EDL mode by switching the phone off, holding down the volume up button and connecting it to the PC.
Well, that's not the way to activate edl mode. The combination you're using puts the device in LGUP or aka Download mode.
To get the phone in edl mode, when booted, press and hold both the vol down button and pwr button, at same time.
Hold them until u get a 'count down' screen, going from 5 to zero. Once at zero, keep holding the buttons but also start pressing the vol plus button as rapidly as u can.
If the screen goes blank, and stays there, it's in EDL mode. If it reboots, simply try it again.
OK, I have a problem. I followed the guide through Step C3 (Partition DL), but I accidentally selected Upgrade instead of Partition DL. Now I am getting the dreaded Opid Mismatched error. I did the backups as directed in Step B1 but I have no idea where the backups are or how to access them. Can anyone help?
Qfil tells you, in the output created by it when it does a backup, where it puts them. They are in your home directory/ appdata / qualcomm etc etc, I don't recall the exact directory off the top of my head.
But the name of them doesn't correspond to the partition name, so if u didn't rename them when u did ea backup, the only way to **guess** which file is which is by the size of the file.
But here's the thing, if u accidentally selected 'upgrade', just start again and do 'DL'.
cheers
There must be. If I had a Mediatek device I'd work on it.
What kind of problem do you have when you attempt to crossflash, it prevents from crossflashing at the beginning or prevents from booting by throwing OPID Mismatched Error or both?
If it prevents from flashing, we need to find partitions containing OP related data.
We have to find partitions that bridge OPID checker function to OPID data container partitions if it gives OPID Mismatched Error.
@netmsm Here is the GPT output for the K51
And LGUP doesn't let me crossflash from the beginning. I tried deleting FTM and both OP partitions then trying to use LGUP to crossflash a KDZ, but it gives a "Cannot change NA_2 to NA_5" error. I can try out whatever you suggest, the K51 is not my main device.
GPT Table:
-------------
boot_para: Offset 0x0000000000800000, Length 0x0000000000100000, Flags 0x00000000, UUID f57ad330-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA
proinfo: Offset 0x0000000000900000, Length 0x0000000000300000, Flags 0x00000000, UUID fe686d97-3544-4a41-21be-167e25b61b6f, Type EFI_BASIC_DATA
para: Offset 0x0000000000c00000, Length 0x0000000000080000, Flags 0x00000000, UUID 1cb143a8-b1a8-4b57-51b2-945c5119e8fe, Type EFI_BASIC_DATA
efuse: Offset 0x0000000000c80000, Length 0x0000000000080000, Flags 0x00000000, UUID 3b9e343b-cdc8-4d7f-a69f-b6812e50ab62, Type EFI_BASIC_DATA
spare1: Offset 0x0000000000d00000, Length 0x0000000000300000, Flags 0x00000000, UUID 5f6a2c79-6617-4b85-02ac-c2975a14d2d7, Type EFI_BASIC_DATA
nvcfg: Offset 0x0000000001000000, Length 0x0000000002000000, Flags 0x00000000, UUID 4ae2050b-5db5-4ff7-d3aa-5730534be63d, Type EFI_BASIC_DATA
nvdata: Offset 0x0000000003000000, Length 0x0000000004000000, Flags 0x00000000, UUID 1f9b0939-e16b-4bc9-bca5-dc2ee969d801, Type EFI_BASIC_DATA
metadata: Offset 0x0000000007000000, Length 0x0000000002000000, Flags 0x00000000, UUID d722c721-0dee-4cb8-838a-2c63cd1393c7, Type EFI_BASIC_DATA
misc2: Offset 0x0000000009000000, Length 0x0000000000800000, Flags 0x00000000, UUID e02179a8-ceb5-48a9-3188-4f1c9c5a8695, Type EFI_BASIC_DATA
ftm: Offset 0x0000000009800000, Length 0x0000000000800000, Flags 0x00000000, UUID 84b09a81-fad2-41ac-0e89-407c24975e74, Type EFI_BASIC_DATA
md_udc: Offset 0x000000000a000000, Length 0x0000000001800000, Flags 0x00000000, UUID e8f0a5ef-8d1b-42ea-2a9c-835cd77de363, Type EFI_BASIC_DATA
expdb: Offset 0x000000000b800000, Length 0x0000000001800000, Flags 0x00000000, UUID d5f0e175-a6e1-4db7-c094-f82ad032950b, Type EFI_BASIC_DATA
frp: Offset 0x000000000d000000, Length 0x0000000000800000, Flags 0x00000000, UUID 1d9056e1-e139-4fca-0b8c-b75fd74d81c6, Type EFI_BASIC_DATA
protect1: Offset 0x000000000d800000, Length 0x0000000000800000, Flags 0x00000000, UUID 7792210b-b6a8-45d5-91ad-3361ed14c608, Type EFI_BASIC_DATA
protect2: Offset 0x000000000e000000, Length 0x0000000000800000, Flags 0x00000000, UUID 138a6db9-1032-451d-e991-0fa38ff94fbb, Type EFI_BASIC_DATA
seccfg: Offset 0x000000000e800000, Length 0x0000000000800000, Flags 0x00000000, UUID 756d934c-50e3-4c91-46af-02d824169ca7, Type EFI_BASIC_DATA
nvram: Offset 0x000000000f000000, Length 0x0000000004000000, Flags 0x00000000, UUID a3f3c267-5521-42dd-24a7-3bdec20c7c6f, Type EFI_BASIC_DATA
persist: Offset 0x0000000013000000, Length 0x0000000003000000, Flags 0x00000000, UUID 8c68cd2a-ccc9-4c5d-578b-34ae9b2dd481, Type EFI_BASIC_DATA
persist_lg: Offset 0x0000000016000000, Length 0x0000000000800000, Flags 0x00000000, UUID 6a5cebf8-54a7-4b89-1d8d-c5eb140b095b, Type EFI_BASIC_DATA
p_persist_lg: Offset 0x0000000016800000, Length 0x0000000000800000, Flags 0x00000000, UUID a0d65bf8-e8de-4107-3494-1d318c843d37, Type EFI_BASIC_DATA
md1img_a: Offset 0x0000000017000000, Length 0x0000000006000000, Flags 0x00000000, UUID 46f0c0bb-f227-4eb6-2fb8-66408e13e36d, Type EFI_BASIC_DATA
spmfw_a: Offset 0x000000001d000000, Length 0x0000000000100000, Flags 0x00000000, UUID fbc2c131-6392-4217-1eb5-548a6edb03d0, Type EFI_BASIC_DATA
scp_a: Offset 0x000000001d100000, Length 0x0000000000100000, Flags 0x00000000, UUID e195a981-e285-4734-2580-ec323e9589d9, Type EFI_BASIC_DATA
sspm_a: Offset 0x000000001d200000, Length 0x0000000000100000, Flags 0x00000000, UUID e29052f8-5d3a-4e97-b5ad-5f312ce6610a, Type EFI_BASIC_DATA
lk_a: Offset 0x000000001d300000, Length 0x0000000000200000, Flags 0x00000000, UUID 9c3cabd7-a35d-4b45-578c-b80775426b35, Type EFI_BASIC_DATA
tee_a: Offset 0x000000001d500000, Length 0x0000000000500000, Flags 0x00000000, UUID e7099731-95a6-45a6-e5a1-1b6aba032cf1, Type EFI_BASIC_DATA
spare2: Offset 0x000000001da00000, Length 0x0000000000600000, Flags 0x00000000, UUID 8273e1ab-846f-4468-99b9-ee2ea8e50a16, Type EFI_BASIC_DATA
logo_a: Offset 0x000000001e000000, Length 0x0000000000800000, Flags 0x00000000, UUID d26472f1-9ebc-421d-14ba-311296457c90, Type EFI_BASIC_DATA
dtbo_a: Offset 0x000000001e800000, Length 0x0000000000800000, Flags 0x00000000, UUID b72ccbe9-2055-46f4-67a1-4a069c201738, Type EFI_BASIC_DATA
vbmeta_a: Offset 0x000000001f000000, Length 0x0000000000800000, Flags 0x00000000, UUID 9c1520f3-c2c5-4b89-4282-fe4c61208a9e, Type EFI_BASIC_DATA
vbmeta_system_a: Offset 0x000000001f800000, Length 0x0000000000800000, Flags 0x00000000, UUID 902d5f3f-434a-4de7-8889-321e88c9b8aa, Type EFI_BASIC_DATA
vbmeta_vendor_a: Offset 0x0000000020000000, Length 0x0000000000800000, Flags 0x00000000, UUID bece74c8-d8e2-4863-fe9b-5b0b66bb920f, Type EFI_BASIC_DATA
boot_a: Offset 0x0000000020800000, Length 0x0000000002000000, Flags 0x00000000, UUID ff1342cf-b7be-44d5-5ea2-a435addd2702, Type EFI_BASIC_DATA
laf_a: Offset 0x0000000022800000, Length 0x0000000002800000, Flags 0x00000000, UUID a4da8f1b-fe07-433b-cb95-84a5f23e477b, Type EFI_BASIC_DATA
md1img_b: Offset 0x0000000025000000, Length 0x0000000006000000, Flags 0x00000000, UUID c2635e15-61aa-454e-409c-ebe1bdf19b9b, Type EFI_BASIC_DATA
spmfw_b: Offset 0x000000002b000000, Length 0x0000000000100000, Flags 0x00000000, UUID 4d2d1290-36a3-4f5d-b4af-319f8ab6dcd8, Type EFI_BASIC_DATA
scp_b: Offset 0x000000002b100000, Length 0x0000000000100000, Flags 0x00000000, UUID fdce12f0-a7eb-40f7-5083-960972e6cb57, Type EFI_BASIC_DATA
sspm_b: Offset 0x000000002b200000, Length 0x0000000000100000, Flags 0x00000000, UUID 0fbbafa2-4aa9-4490-8389-5329328505fd, Type EFI_BASIC_DATA
lk_b: Offset 0x000000002b300000, Length 0x0000000000200000, Flags 0x00000000, UUID a76e4b2f-31cb-40ba-6a82-c0cb0b73c856, Type EFI_BASIC_DATA
tee_b: Offset 0x000000002b500000, Length 0x0000000000500000, Flags 0x00000000, UUID f54ac030-7004-4d02-8194-bbf982036807, Type EFI_BASIC_DATA
spare3: Offset 0x000000002ba00000, Length 0x0000000000600000, Flags 0x00000000, UUID c4c310e2-4a7e-77d3-1848-61e2d8bb5e86, Type EFI_BASIC_DATA
logo_b: Offset 0x000000002c000000, Length 0x0000000000800000, Flags 0x00000000, UUID 3734710f-0f13-1ab9-4c73-12a08ec50837, Type EFI_BASIC_DATA
dtbo_b: Offset 0x000000002c800000, Length 0x0000000000800000, Flags 0x00000000, UUID 85a5b02f-3773-18b3-4910-718cde95107e, Type EFI_BASIC_DATA
vbmeta_b: Offset 0x000000002d000000, Length 0x0000000000800000, Flags 0x00000000, UUID 6fce83a6-5273-4748-4511-c205ebb4b8ad, Type EFI_BASIC_DATA
vbmeta_system_b: Offset 0x000000002d800000, Length 0x0000000000800000, Flags 0x00000000, UUID 3645e6a3-a7e3-19b2-4149-172c10190eef, Type EFI_BASIC_DATA
vbmeta_vendor_b: Offset 0x000000002e000000, Length 0x0000000000800000, Flags 0x00000000, UUID f60b92b4-0e2f-91b6-4afb-2d0b643bab4b, Type EFI_BASIC_DATA
boot_b: Offset 0x000000002e800000, Length 0x0000000002000000, Flags 0x00000000, UUID d05cedfe-20b7-68b3-f259-4fe25317f2fc, Type EFI_BASIC_DATA
laf_b: Offset 0x0000000030800000, Length 0x0000000002800000, Flags 0x00000000, UUID 54060b67-fa74-5c82-1661-44821e54dced, Type EFI_BASIC_DATA
eksst: Offset 0x0000000033000000, Length 0x0000000000080000, Flags 0x00000000, UUID c0a128fb-59d1-0a9e-e8f0-ea3d36a9d658, Type EFI_BASIC_DATA
encrypt: Offset 0x0000000033080000, Length 0x0000000000080000, Flags 0x00000000, UUID f5f5a7f8-f8ec-3ba1-c9cb-4e2a7cbc7d07, Type EFI_BASIC_DATA
rct: Offset 0x0000000033100000, Length 0x0000000000100000, Flags 0x00000000, UUID 736d618a-5b79-530b-ac9d-895339690613, Type EFI_BASIC_DATA
spare4: Offset 0x0000000033200000, Length 0x0000000000600000, Flags 0x00000000, UUID a2342ac6-4c40-b02c-4f51-e90d46f93454, Type EFI_BASIC_DATA
power: Offset 0x0000000033800000, Length 0x0000000002800000, Flags 0x00000000, UUID 339d6f74-bcb8-f02b-4a69-ae0152bcadc0, Type EFI_BASIC_DATA
mpt: Offset 0x0000000036000000, Length 0x0000000002000000, Flags 0x00000000, UUID 2cd122a3-6142-31a9-8812-cb60fbead9be, Type EFI_BASIC_DATA
fota: Offset 0x0000000038000000, Length 0x0000000001000000, Flags 0x00000000, UUID c09b7bd1-5e46-450c-d597-adf4072a8d6b, Type EFI_BASIC_DATA
els: Offset 0x0000000039000000, Length 0x0000000001000000, Flags 0x00000000, UUID 448a65b8-a5d4-bdb0-ebdd-bf4ea3ceafc6, Type EFI_BASIC_DATA
carrier: Offset 0x000000003a000000, Length 0x0000000003800000, Flags 0x00000000, UUID b1b1e374-8c7f-b48a-75d5-ce0ca20f1183, Type EFI_BASIC_DATA
srtc: Offset 0x000000003d800000, Length 0x0000000000800000, Flags 0x00000000, UUID 24d37dd4-caf8-1a6e-45be-89e4b0705843, Type EFI_BASIC_DATA
eri: Offset 0x000000003e000000, Length 0x0000000000800000, Flags 0x00000000, UUID 37957b10-67ef-1440-3b89-6200484311b6, Type EFI_BASIC_DATA
operatorlogging: Offset 0x000000003e800000, Length 0x0000000001000000, Flags 0x00000000, UUID 441c978b-5309-1faa-913c-32c5f087e9ae, Type EFI_BASIC_DATA
super: Offset 0x000000003f800000, Length 0x0000000200000000, Flags 0x00000000, UUID 575fb526-8d23-61c4-fed5-e9e040eb0741, Type EFI_BASIC_DATA
OP_a: Offset 0x000000023f800000, Length 0x000000003c000000, Flags 0x00000000, UUID d8bbfddf-8e4c-8cf5-e3ca-fc4f02e1c49a, Type EFI_BASIC_DATA
OP_b: Offset 0x000000027b800000, Length 0x000000003c000000, Flags 0x00000000, UUID 7c881e59-5172-82a8-5c30-42abbd467b7d, Type EFI_BASIC_DATA
userdata: Offset 0x00000002b7800000, Length 0x000000048ec00000, Flags 0x00000000, UUID aa224eb0-1781-c4d2-1ed8-b39e64810df6, Type EFI_BASIC_DATA
flashinfo: Offset 0x0000000746400000, Length 0x0000000001000000, Flags 0x00000000, UUID a03b5e9f-674c-998f-fbf4-e24b171a35f3, Type EFI_BASIC_DATA
And LGUP doesn't let me crossflash from the beginning. I tried deleting FTM and both OP partitions then trying to use LGUP to crossflash a KDZ, but it gives a "Cannot change NA_2 to NA_5" error. I can try out whatever you suggest, the K51 is not my main device.
protect1 and protect2 look suspicious partitions! You may backup and erase them for a test.
Please give me screenshots of "download mode" before and after erasing ftm, op and protect partitions.
Thank you so much! That worked. Unfortunately, I now have yet another problem: Cricket (my carrier) disabled my phone, apparently as part of a policy of banning phones that do not support VoLTE. I followed the guide from here to add VoLTE support, but the code *#*#4636#*#* shows VoLTE Provisioned as unselected and grayed out. Gah!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
55Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.7
Thanks, netmsm and kt-froggy for the guides.First off, big THANKS to the OP (netmsm) and other people who contributed to this thread and made this guide very clear and useful!
So, after perusing this thread for a long time, trying to understand the ins and outs of the process and any possible snafus, I decided to take the plunge after the Open_CA A12 (40a) got released recently, and to flash it onto my G8 originally from US Cellular. The crossflash went smoothly with no issues at all. A nice surprise was that the BL remained unlocked - I was prepared to go through the whole unlocking process again before rooting, but didn't have to. I got the empty S/N (easy fix), and the infamous NT-Code error. This is where I got stuck for a while. I tried fixing it by editing the cust_path_mapping.cfg file as suggested in the thread. The problem is that I couldn't save the changes in that stupid file by using ANY root explorer/editor! Tried half a dozen different apps with no luck at all. BTW, anyone has any ideas what I may have been doing wrong?? Yes, I am properly rooted with Magisk.
Anyway... Everything worked fine on the phone, but that lame error was really getting under my skin - I could have ignored it, but I hated not being able to get rid of it. So... After more reading, I came across some info on hex-editing the FTM partition (in a totally unrelated topic). The NT-Code in FTM binary is stored at the offset 00014000. My error message was referring to the code "FFFFFF,85". The original cust_path_mapping.cfg file (which I couldn't edit) had a line referring to "FFFFFF,82". So, having all backups available, I decided, just for the heck of it, to change the last digits of the NT-Code in the FTM partition to match the "82" listed in the file. What could go wrong? I can always restore a backup... After flashing the edited FTM in QFIL, rebooted the phone, and - bingo! The NT-Code error was gone, and the phone was still fully functional. This was my happy face after spending a good hour and a half trying to get rid of it, and finally succeeding:
Cheers, and thanks again for all the info!
I figured out how to remove the NT code error without root.
You will first need a file manager that can access the root directory.
I personally used "Solid Explorer File Manager" to access the cust_path_mapping.cfg file to read the NT-Code that came with the firmware.
You can use the Solid Explorer File Manager to access the root directory by going to settings then scrolling down and checking the box "show root storage". You will now be able to access the root storage.
You can access the cust_path_mapping.cfg by going to root/system/product/OP. Then open the file and note the code. Mine was FFFFFF,82=/product/OP.
Create a backup of the FTM partition the open the FTM file with HxD app. (Make sure you have a copy of the FTM file in case something goes wrong)
Go to line 00014000 and edit the line. depending on the phone, edit the first 2 sets of numbers/letters with 3 characters separated by a comma. ("FFF,FFF), then the last set of numbers/letters with 2 characters to match the code in the cust_path_mapping.cfg file.
(Mine was
"2","310,120,FFFFFFFF,FFFFFFFF,FF","312,530,FFFFFFFF,FFFFFFFF,FF" and I changed to
"2","FFF,FFF,FFFFFFFF,FFFFFFFF,82","FFF,FFF,FFFFFFFF,FFFFFFFF,82") because I was getting NT code error
310120, 312530 ; FF, FF
Note:
1. The line could span from 00014000 to 00014040 like mine. Each line is separated with "". I had 2 lines and had to change both lines. You can have only 1 line
2. Make sure you don't delete the line but just select the content and overwrite it with new text. deleting might affect other lines below with content. ( I deleted some lines and my phone factory reset)
After that just save the FTM and load it to your phone using QFIL and the error will be gone.
I've only tested it on my LG G8, OPEN CA firmware so I'm not sure if it will work on others.6Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^5
So, we just got this sorted. Thanks to SGMarkus as he mentioned it's the ftm partition that controls recovery access and fastboot access. So, with the newly flashed kdz, as it is, you can't even get to fasboot although u flashed the eng abl to it.
But! Restore your old ftm, after flashing, and then you'll get access to both recovery and ability to get to fastboot after flashing eng abl.
cheers!4First off, big THANKS to the OP (netmsm) and other people who contributed to this thread and made this guide very clear and useful!
So, after perusing this thread for a long time, trying to understand the ins and outs of the process and any possible snafus, I decided to take the plunge after the Open_CA A12 (40a) got released recently, and to flash it onto my G8 originally from US Cellular. The crossflash went smoothly with no issues at all. A nice surprise was that the BL remained unlocked - I was prepared to go through the whole unlocking process again before rooting, but didn't have to. I got the empty S/N (easy fix), and the infamous NT-Code error. This is where I got stuck for a while. I tried fixing it by editing the cust_path_mapping.cfg file as suggested in the thread. The problem is that I couldn't save the changes in that stupid file by using ANY root explorer/editor! Tried half a dozen different apps with no luck at all. BTW, anyone has any ideas what I may have been doing wrong?? Yes, I am properly rooted with Magisk.
Anyway... Everything worked fine on the phone, but that lame error was really getting under my skin - I could have ignored it, but I hated not being able to get rid of it. So... After more reading, I came across some info on hex-editing the FTM partition (in a totally unrelated topic). The NT-Code in FTM binary is stored at the offset 00014000. My error message was referring to the code "FFFFFF,85". The original cust_path_mapping.cfg file (which I couldn't edit) had a line referring to "FFFFFF,82". So, having all backups available, I decided, just for the heck of it, to change the last digits of the NT-Code in the FTM partition to match the "82" listed in the file. What could go wrong? I can always restore a backup... After flashing the edited FTM in QFIL, rebooted the phone, and - bingo! The NT-Code error was gone, and the phone was still fully functional. This was my happy face after spending a good hour and a half trying to get rid of it, and finally succeeding:
Cheers, and thanks again for all the info!
