The 8150 firehose won't work for the Stylo 5.The Stylo 5 has a sdm450 chipset,and you need to find the proper firehose before you can do anything with Qfil.You can try this one,but I highly doubt it will work.
hi same error failed
The 8150 firehose won't work for the Stylo 5.The Stylo 5 has a sdm450 chipset,and you need to find the proper firehose before you can do anything with Qfil.You can try this one,but I highly doubt it will work.
i think this is because the attached firehose file is for oppo devices, i opened on hex editor and saw multiple entries that mentioned OPPO. the issue for us is that LG probably used a specific firehose that unfortunely never was leaked
hmm right atleast we tried i bought another phone can i read software and write firmware ? here is logo software version Q720MS20fView attachment 5875783i think this is because the attached firehose file is for oppo devices, i opened on hex editor and saw multiple entries that mentioned OPPO. the issue for us is that LG probably used a specific firehose that unfortunely never was leaked.
i think this is because the attached firehose file is for oppo devices, i opened on hex editor and saw multiple entries that mentioned OPPO. the issue for us is that LG probably used a specific firehose that unfortunely never was leaked.
100 TESTED in G850u sprint and V500N KoreanHi 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.
Hi how to fix q720ts software version Q720TSS90H?
We would need the firehose,which so far I haven't found one that works with the 5.I've been looking for one to try on the LG Wing and Velvet's.Wish someone could figure out a similar process for the Pixel 5 . . . use qfil to delete a few partitions, then use a tool similar to LGUP to flash a different rom.
Right now, it seems to me the only way around the problem of Verizon Pixels having the 'Enable OEM unlock' option greyed out.
first open QFIL, select flat build, storage type UFS only then boot phone in EDL mode and select portHello netmsm, I wanted to try this on my g8x but I keep having this error message about a "sahara" protocol failed. Can you please help me and tell what I'm doing wrong? I share with you a ss of the message.
no selection to edit code in this menu, you can only look
Either because of the installed KDZ or some locking protocols or software flaws. Try another, different KDZ and if it persists then the locks should be removed using Octopus box.
Pull the FTM,and modify the NT Code at offset 14000 with a Hex Editor.Make sure you paste write it,and not enter the NT-Code by hand.The write the FTM back to the device.
I have edited a many of them,and never had any issues.The key is to paste write it,or you will face those errors.I fixed diferent way, edit cfg in system/product/op, but for this you will need patched vbmeta partition, disable verification, if you change NT code in FTM file via QFIL its works but only one time, when phone boot up network OK, no NT errors but if you restart phone its stoping, no internet, no calls like no SIM inserted...
I didn't have this problem. Edited the NT Code in FTM using hex editor, flashed via Qfil, the phone works fine after reboots, including calls and the network access.if you change NT code in FTM file via QFIL its works but only one time, when phone boot up network OK, no NT errors but if you restart phone its stoping, no internet, no calls like no SIM inserted...
The G8s is the European variant of the G8,and I can't say for sure how well it will work on a G8 Verizon variant.I own the G8x,which is AT&T branded.You can give it a shot,but personally I would go with the G820QM open firmware.All variants of the firmware can be found at the link below.Thanks, this worked.
Where can i get a europaen firmware?
Or can i flash G8s LMG810 firmware instead?
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!
Sure!Pick your firmware and go!
Use this version of LGUP and give it a try!Delete any previous versions!Qfil worked but when i try too flash it with lgup, it crashes at 4%.
Dll file and lgupconfig file are installed.
Now i have bootloop.
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!