netmsm said:

Hi ^_^
First of all, go to Qfil and make backup of LUN5 partitions.

Then, restore the original FTM. (Use the attached file if you do not have it).
If it doesn't help, try another KDZ and again restore the original FTM.

Again, if it doesn't work out, make a full backup and then proceed to the next one.
Flash the phone through chip erase.
DO NOT PERFORM CHIP ERASE IF YOU HAVE NOT MADE A FULL BACKUP.

Hello sir thank you for the reply and guide do you have any post on how to flash the FTM file I tried to search for the tutorial but cannot find it. I just found how to modify the FTM file and do I need to backup using Qfil or other program?. sorry for my inexperience in this kind of stuff

hajimxmiku said:

Hello sir thank you for the reply and guide do you have any post on how to flash the FTM file I tried to search for the tutorial but cannot find it. I just found how to modify the FTM file and do I need to backup using Qfil or other program?. sorry for my inexperience in this kind of stuff

Hello my friend =)
You need to learn how to use Qfil. We create and restore a backup using Qfil. We barely flash FTM instead we restore it using Qfil.
In the part B of this thread it is generally explained how to use Qfil.
Using Qfil make backup of LUN5 partitions; be very careful to not erase them just "read" them.

netmsm said:

Hello my friend =)
You need to learn how to use Qfil. We create and restore a backup using Qfil. We barely flash FTM instead we restore it using Qfil.
In the part B of this thread it is generally explained how to use Qfil.
Using Qfil make backup of LUN5 partitions; be very careful to not erase them just "read" them.

Hello thank you for the reply when you say full backup do I need to backup LUN5 only or I need to backup All?, I already backup LUN5 if all LUN0,LUN1,LUN2,LUN3,LUN4,LUN5,LUN6,LUN7 ?

hajimxmiku said:

Hello thank you for the reply when you say full backup do I need to backup LUN5 only or I need to backup All?, I already backup LUN5 if all LUN0,LUN1,LUN2,LUN3,LUN4,LUN5,LUN6,LUN7 ?

Hello *_* You're welcome *_*
If you have already flashed the phone there's no use to make a full backup (all LUNs) and just LUN5 is enough to make backup from.

@netmsm Bro, do you know how I can enable the PDM option in LGUP for the G8X?

×RaúlMX× said:

@netmsm Bro, do you know how I can enable the PDM option in LGUP for the G8X?

Hey buddy =)
It's already explained here, troubleshooting section, #8.

hello what are the gpt files for LGv60 thinq tmobile?

hello there Why is Fh_loader.exe not running inisde qfil folder?

Antonroxas said:

hello what are the gpt files for LGv60 thinq tmobile?

Hello =) I do not have it.

Antonroxas said:

hello there Why is Fh_loader.exe not running inisde qfil folder?

Hello =) fh_loader can be called using CMD (command prompt).

netmsm said:

Hello =) I do not have it.

Hello =) fh_loader can be called using CMD (command prompt).

I'm getting this error sorry I'm new to this
'fh_loader.exe' is not recognized as an internal or external command,
operable program or batch file.

Antonroxas said:

I'm getting this error sorry I'm new to this
'fh_loader.exe' is not recognized as an internal or external command,
operable program or batch file.

Please read the instructions once more and carefully.

netmsm said:

FTM is a temp place and its data are regenerated after flashing the phone. Changing IMEI in FTM will not change the phone IMEI.
FSG is the backup of Modemsts. Repairing IMEI process can alter Modemsts but not FSG.
LG has put a new lock in NVM to prevent identity data from getting changed. In addition, the bridge to Modemsts is Modem partition which carry another lock called IMEIPROT.
When we erase all partitions, NVM is cleared but IMEIPROT still exists in Modem. The only way to rewrite IMEI is to modify Modem by removing IMEIPROT. However, losing NVM will awake another lock which prevents Modem from detecting Sim, resulting in the error "this phone is permanently locked" even after rewriting IMEI.

Then, is there no way to clear both NVM & IMEIPROT at the same time? I have "permanently locked" problem (because of too much entering wrong code) and I want to fix it. LG V60 AT&T model.

fukko123 said:

Then, is there no way to clear both NVM & IMEIPROT at the same time? I have "permanently locked" problem (because of too much entering wrong code) and I want to fix it. LG V60 AT&T model.

The only tool than have access to nvm is Octopus.

I just created the unbrick lg v50s file. There may be an error. I relied on the rawprogramx.xml file in the unbrick lg v50 file and the PartitionsList of lg v50s saved from QFIL to create a new rawprogramx.xml file. I replaced the partition addresses in the rawprogramx.xml file of lg v50 with the new partition addresses in the PartitionsList of lg v50s. gpt_main or gpt_backup files remain the same (perhaps these files of v50 are the same as v50s). other files are taken from the kdz rom of lg v50s (lgu kr v510n20s).
You have to find a way to load rawprogramx.xml in QFIL somewhere else.
When it finishes downloading, press and hold the volume button - simultaneously with the power button for about 12 seconds and then release. Wait about 5s, hold down the volume + button to enter Download mode to reinstall the rom. If it doesn't power up, try again.
Here is the unbrick lg v50s link: https://drive.google.com/file/d/1eo6gm8EGbVXSvWZCjZMJmVluXKTrJeOt/view?usp=share_link

abg360 said:

it appears this error:
17:14:55: INFO: 3. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt') with AccessMode='w'


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


17:14:55: {ERROR: Calling fopen with with access mode 'w' on 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt was NOT successful' }

ERROR: Could not append to 'port_trace.txt'

Log is 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt'

SORRY FIXED I HAVE TO GIVE ADMIN ACCESS IN PROPERTIES
EXACTLY I HAVE TO PUT .\fh_loader.exe

Click to expand...

how did u fix this error??

AAMIRALI034838 said:

how did u fix this error??

Run CMD as administrator.