I wanted to add a couple of points, which I came across along the way of implementing the guidelines in this thread.
The usual caveat: if you brick your phone in the process, I shall not be held responsible, I have to warn you guys, this was not the most straightforward exercise I have done on my phones, and I did root a few of them.
Now, the points:
Problem: Both Google Chrome and Firefox have blocked the download of lg_android_31010.exe file as malicious software.
Solution: Use this link
http://answerslg.com/download-and-i...10-for-lg-android-devices/#Lg-usb-driver-3.10 and download the file LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe – it is the same as lg_android_31010.exe .
Problem: The downloaded QPST_2.7.411 file did not want to install properly throughits setup.exe. The Visual C++ 2005 package would get confirmed as “ok”, but the QPST would throw an error.
Solution: There is nothing wrong with the QPST package. On your Windows 7 press “Start”, and type “run cmd”. Find a path to the .msi file inside QPST folder (by using “cd..” and “cd [folder name] commands, where “cd” stands for “change directory”, greetings to MS DOS generation). Then enter the following command, which installs msi package files as admin:
msiexec /a "QPST 2.7.411.msi"
It will unpack the file into the Program Files (x86) folder. For me it still was not installed, so from the normal Windows environment I went into Program Files (x86) folder -> Qualcomm -> QPST folder, where it unpacked, right clicked on the .msi file and pressed „Install”. Only then did it install properly.
Problem: When you enter into QPST interface you may see only COM1 port available for choice, your Android Device COM Port is not shown, but in Windows Device Manager you can see that COM port Android Device is shown under COM** (where ** is a number of the COM port assigned).
Solution: Deselect The "Show Serial and USB/QC Diagnostic Ports only" on the QPST menu and the COM port of your device will appear in the list menu in QPST, just select it.
Problem: Some of the steps, like running adb commands through cmd, fastbooting an alternative kernel for DIAG mode, installing the drivers sound confusing.
Solution: First of all, there are several sets of drivers mentioned here, namely, LG drivers, Android drivers, ADB drivers, and QPST, and you need to install all. LG will be needed to recognise device on COM port in QPST, because QPST will communicate with the device via virtual COM port, while still connected through USB, and because backing up of your original QCN file and uploading of the alternative QCN file provided in this thread happens through QPST, you need to install QPST drivers before the procedure too, and Android and ADB will be needed for proper communication between your phone and your PC. Well, while LG and QPST cannot be avoided, the ADB and Android driver installation can be made easier and foolproofed by installing the Nexus Root Toolkit v.2.0.5, which you probably used already to root your phone in the first place. With it you can test whether the drivers have installed correctly (full driver installation guide – advanced+manual), can always check device connectivity (check devices), can call cmd utility and run your adb commands from it (advanced utilities -> Launch CMD Prompt), can even temporarily fastboot the kernel for DIAG mode, no need to download the alternative kernel separately (advanced utilities -> modified boot.img) and all this at a press of a button. So I can’t recomment the tool more for the purposes of this thread.
Question: Is there an alternative way to back up EFS file?
Answer: EFS yes, there is an easier way to do that, as described in this excellent guide
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 (use Nexus Root Toolkit), but it does not take care of your QCN file, for QCN you still need to run QPST, as described above.
One more question I had was whether my kernel had DIAG mode, or I needed to flash a temporary kernel, which has such capability. While you can go through a routine to check, my advice is to use fastboot to temporarily enter the system with the suitable DIAG kernel, which, as said above, easily done with the help of Nexus Root Toolkit.
Another qestion which I had and which did not have a ready answer, is whether a temporary kernel that you are supposed to flash will stick and replace the kernel you had before. The answer is that if you use fastboot, it will load once, and on your next reboot your notmal kernel will return. Hope someone will find this clarification useful.
That concludes my 1st attempt to give back to the excellent community at xda and the great bunch behind this and adjacent threads. Thank you guys, I did manage to unlock my Band 3 on a D820 model SlimKat 4.4.4 (tested) (yes, I rolled back from Lollipop, because I expect that another year or so will pass until the app developers will get to grips with it and adjust their apps on Google Play, and until all bugs and glitches within Lollipop itself are smoothed out to give us the seamless experience, mind you, I sat on 2.3 Gingerbread, Siyah kernel on my SGS II until now, having had this phone for 4 years, stability and reliability are king for me, yet flexibility and customization for comfortable use are a must, too). In fact, 3g is sufficient for me, as, probably, for most of us, especially given that a modem working on LTE Band 3 frequesncy in a 2m radius gives me a headache, tested on several occasions, so this was done for futureproofing, marketability and, of course, for the fun of it.