fix the procedure, everything went well, I would like to know if there is any way for this procedure to change the bootanimation of the device (the operator's bootanimation was still left)
Hi,I followed your whole tutorial, but LG UP is giving this error. Can you help please?
I am trying to crossflash Japan Model to Global Model using G850EMW40a_00_0627.kdz.
I am currently in Android 12. you can see the version in screenshot. @netmsm
Mine is Japan Version (64GB ROM version). Do you think it matters in any way 64GB or 128GB?
These should give you a solid backup!Just modify your port number of choice.@netmsm Can you please modify your codes to backup all LUN partitions, using my partition list attached, for my G8x so that if anything goes south, I can restore my device?
or your g8 codes from here will be fine?
I am also attaching my current download mode picture and backed up lun partitions for your information and favorable action in this regard plz.
Thanks a lot. Much appreciated.These should give you a solid backup!Just modify your port number of choice.
Spoiler
LUN 0
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN0_Complete.bin --start_sector=0 --lun=0 --num_sectors=4068999 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN1
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN1_Complete.bin --start_sector=0 --lun=1 --num_sectors=2043 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN2
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN2_Complete.bin --start_sector=0 --lun=2 --num_sectors=2043 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN3
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN3_Complete.bin --start_sector=0 --lun=3 --num_sectors=2048 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN4
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN4_Complete.bin --start_sector=0 --lun=4 --num_sectors=383995 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN5
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN5_Complete.bin --start_sector=0 --lun=5 --num_sectors=3067 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN6
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN6_Complete.bin --start_sector=0 --lun=6 --num_sectors=1024 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
By the way,these are for the U.S. G8x which I own.I changed LUN 0 to match your partition list.Here's my list for the G8x U.S. variant as well.
LUN 0
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN0_Complete.bin --start_sector=0 --lun=0 --num_sectors=4863623 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN1
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN1_Complete.bin --start_sector=0 --lun=1 --num_sectors=2043 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN2
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN2_Complete.bin --start_sector=0 --lun=2 --num_sectors=2043 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN3
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN3_Complete.bin --start_sector=0 --lun=3 --num_sectors=2048 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN4
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN4_Complete.bin --start_sector=0 --lun=4 --num_sectors=383995 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN5
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN5_Complete.bin --start_sector=0 --lun=5 --num_sectors=3067 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
LUN6
fh_loader.exe --port=\\.\COM16 --convertprogram2read --sendimage=LUN6_Complete.bin --start_sector=0 --lun=6 --num_sectors=1024 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
I just remembered there was a similar case with the same phone and problem but I cannot remember whether the problem was solved or not!@netmsm @Surgemanxx
I followed tutorial, also erased both sides A & B: boot, system, vendor, product and user data along with sid a, sidb, modema , modem b and ftm. Still this error comes in LG UP.
I am attaching my log file too.
SHould I Use refurbish option or what?
Once you got a full backup yes.
The backups contain GPT info since they are starting at sector 0.2. Should I create back up of my current GPT partitions as well (please guide me how to) because my current partitions don't have OP_a & OP_b partitions.
I'm not sure I got you said but after crossflashing the device will have relative modem partition files. And, the issue of not changing network automatically will maybe gone.3. Can I use modems of other ROMs for better band support because I usually have network issued with my current ROM. While on 3g my phone does not make calls while data transfers works. Also my phone don't switch between 3g and 4g automatically. I need to turn off option in settings which says "use 4g network instead of 3g."
We haven't experienced such problem yet and logically we do not expect it. However, got backup of LUN5 partitions separately using Qfil just in case some jinxy thing happens!
Hi op, I found the same problem like you but I cant change the region as shown below and now I cant even boot into OS, any help?Some 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 ^_^
Hi =)Hi op, I found the same problem like you but I cant change the region as shown below and now I cant even boot into OS, any help?
EDIT:
I tried to crossflash my V500N to V450EM, at first it shown as V500N and after a reboot it shown as completed on the progress bar as the version changed to V45040a and I decided to unplug the phone, and now it show like the attachment
View attachment 5924449
hi op, thank you for reply!Hi =)
Please read the original post thoroughly. I put everything I know there.
Hi brohi op, thank you for reply!
Now I've been successfully booted into OS, but now my V50 cant detect any simcard, it's written as "no simcard, service disabled", got the SN but the NT-Code is missing, should I fix the NT-Code so I can use my simcard again or what I need to do?
EDITED:
Tried to fix the FFFFFF code using HxD but it already shown like this (pls ignore the 63 in red, it was already there but deleted mistakenly so I'd to write it again)View attachment 5924705
ah geez, seems I forgot to backup the LUN5Hi bro
You got backups, right? So just restore LUN5 partitions and FTM.
That's right, other phone's LUN5 backup is not useful but Octopus can help.Seems it cant be help if using other's V50 LUN5, welp, I'll try it later tonight using Octopus fix just like you said. About the FTM, should I restore using FTM that I've backed up before the crossflashing or after the crossflash?
The ones before making change in those partitions.the original ftm and modem_a was the file before I did the crossflash right?
You said you got no backup so there will be no restoration. Use Octopus/Octoplus to break IMPL lock which make you able to change NT-Code via hidden menu (*#546368#*500#). Although, after breaking the lock, you'll get network even with NT-Code "0". To break it just try to perform either IMEI Repair or Direct Unlock functions on Octopus; it costs some credits.Just to make clear, so I need to restore my LUN5 using Octoplus tools, right?
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!
Hey good for you, so the Open a11 must be the Kor version right? Either way, could u do a big favor and try to get to recovery? Of course don't erase anything, but just verify you can get to the recovery screen?
thnx!