I got my phone working. I don't know exactly what happened but I could boot into 9008 mode only. No matter what I try to do, the phone would not boot normally. I did the process again, but I flashed the .bin file we were supposed to download, instead of the .img file. Maybe I misread something and you're supposed to do that to begin with. Either way it booted and I don't even dare to try again. Hope this helps SOMEBODY.
V60 Bootloader Unlock and Magisk Root
- Thread starter crimsonrommer
- Start date
Update on this:
I have flashed the Taiwan version V600EA10e_00_0930.kdz over the version I had after crossflashing from ATT,
Poland V600EA20k_00_1112.kdz. For some reason, I did not get the NT error, and my AOD display is back. Fingerprint also works out of the box. I also don't have to install the hidden menu APK - it is present here and I can check my Cover Display FW Version which I couldn't before with the other EA ROM (It is LMV600N-V01m_00) and upgrade it. I can also see 5G NR Band selection which wasn't on the other ROM. APN is also accessible. I had a bit of a scare when tinkering with the hidden menu LTE bands trying to see if anything influenced HSDPA in any way and it gave me no 4G for a bit but it's fine now.
Maybe there's a catch somewhere but right now I'm not seeing it.
Edit: As expected, GPay does not work (likely because of the unlocked bootloader). Not a surprise but it would have been nice.
Last edited:
Looks like its related to LG's tracking and software update, so probably not.
MPT - LG's incognito version of KnowledgeC - forensicmike1
Learn how LG has been tracking its users for years, and how devices are not purging this data on a factory reset.
www.forensicmike1.com
What's the best place to get firmwares? I had a timeout on lg-firmwares.Com while trying to grab EA20k (Poland). I managed to find it elsewhere, but the filename is suspect (and attained with a KDZ Downloader in Spanish). Can anyone confirm the file size as 6,134,527,440 bytes?
I don't know what's the difference I only downloaded and tested the 20k FW under Poland region from one of the lg fw site.
Late to the party again. Regarding that NT-code error with 20k Polish firmware (and perhaps others since this seems like a regional check), is there no easy way to disable the check on startup? It's not a big deal, as stated above, but I wouldn't mind getting rid of it.
Oh, I did find this. Looks like it requires reflashing so I think it can be tolerated here as well, lol.
Also this:
I figured out how to get rid off the NT code error on my cross-flashed AT&T variant (IMPL value is 1, locked) with modifying the ftm partition, However, after changing it, mobile data stopped working (tried setting the APN for my courier but without luck) and the NT Code in the MID information of the hidden menu instill show the same old value
The good side is that
* in Mobile networks settings, APN and network operator can be set now
* the NT code error is gone
* a bunch of new apps appear in the app drawer
* in Update center settings, there is a new item "Software Update" (not sure if this really works because my phone already on the latest version)
* weather wedge is available
Any ideas to fix the mobile data issue??
This is how I did it:
1. back up the ftm partition with QFIL in case something goes wrong
2. edit a copy of the backed up ftm file with hex editor (I used HxD)
3. at the offset 00014000 update your NT code and save (use the right-click command "Past write" so that the file size will not be altered)
Notes: My AT&T v60 had been cross-flashed to the EU version, the value at this offset is all zeros for some reason (previously was a long NT code begins with "15","310,410...
4. flash the modified ftm back and exist 9008 mode
reference:
Getting access to recovery combination(FTM mod)
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * YOU are choosing to make these modifications, and if you point the finger at me for messing...forum.xda-developers.com
This is what I done to get rid of the NT-CODE error + having mobile data after editing ftm .
In QFIL find ftm.bin, manage partition data / read data. find the folder where the backup partition was saved .
In HxD editor open the backed up ftm partition .
Find offset 00014000 right click ,pastewrite your NT-code I did "1","FFF,FFF,FFFFFFFF,FFFFFFFF,11" (for Europe)
Flash edited ftm back with qfil,reboot ,
Extract from your kdz (or from your FW with QFIL ) modem_a .
With 7zip, navigate to (modem_a\image\modem_pr\mcfg\configs\mcfg_sw\generic\Korea\ROW\Commercial\) extract mcfg_sw.mbn
Enter Hidden menu / SVC/ choose Field Test, then LTE Data Test, and change the Tethering Mode from Android to QMICM.
Usb debugging must be off!
Open PDC tool in QPST,
Load the extracted mcfg_sw.mbn
after that right click on ROW_commercial, setselectedconfig-sub0, it will have status "pending"
press activate,
reboot or reset Network Settings , mobile data should work now after every reboot or factory reset .
(thanks jdlfjk xda)
P.S.- DO NOT DELETE any of the existent profiles in the menu,done that and IMEI was gone!
In QFIL find ftm.bin, manage partition data / read data. find the folder where the backup partition was saved .
In HxD editor open the backed up ftm partition .
Find offset 00014000 right click ,pastewrite your NT-code I did "1","FFF,FFF,FFFFFFFF,FFFFFFFF,11" (for Europe)
Flash edited ftm back with qfil,reboot ,
Extract from your kdz (or from your FW with QFIL ) modem_a .
With 7zip, navigate to (modem_a\image\modem_pr\mcfg\configs\mcfg_sw\generic\Korea\ROW\Commercial\) extract mcfg_sw.mbn
Enter Hidden menu / SVC/ choose Field Test, then LTE Data Test, and change the Tethering Mode from Android to QMICM.
Usb debugging must be off!
Open PDC tool in QPST,
Load the extracted mcfg_sw.mbn
after that right click on ROW_commercial, setselectedconfig-sub0, it will have status "pending"
press activate,
reboot or reset Network Settings , mobile data should work now after every reboot or factory reset .
(thanks jdlfjk xda)
P.S.- DO NOT DELETE any of the existent profiles in the menu,done that and IMEI was gone!
List Firmware KDZ of LG V60 ThinQ 5G / LMV600EA
List Firmware KDZ of LG V60 ThinQ 5G / LMV600EA - Download Free and Max speed from LGROM.com
lgrom.com
I was trying to identify what i was doing wrong when "Making /system RW (Credits to Leronex_1)"
Step 5 was yielding error code 73 and I wasn't sure what was wrong
Turns out that the error is expected and that's what step 6 was for, this wasn't clear to me, can you please update the step so others know?
Step 5 was yielding error code 73 and I wasn't sure what was wrong
Turns out that the error is expected and that's what step 6 was for, this wasn't clear to me, can you please update the step so others know?
Last edited:
I was able to make system RW using twrp method of wiping data, reboot to fastboot, flash modded vendor.img I found online and then allow reboot to system. Go back to twrp and system is no longer encrypted.
Last edited:
I can't get the phone into fastboot mode after i load the engineering bootloader. Should I start over at step 1? I tried plugging in the USB while holding volume down, but just see the boot screen followed by the battery charging screen going from 0 to 100 in a few seconds.
Edit: got it to work finally after about 10 tries. Engineering bootloader wasn't loading for some reason.
Edit: got it to work finally after about 10 tries. Engineering bootloader wasn't loading for some reason.
Last edited:
I would like to try that file too. I don't currently have access to a Linux machine.
So, new problem after previously performing all the steps on page 1 and successfully cross-flashing this Verizon unit to V600EA20k_00_1112.kdz. Basically, I just realized earlier today after trying some root-requiring apps/root checkers: They are reporting it's not actually rooted! Even though the bootup screen confirms inability to lock the bootloader (implying root access), Root Checker (from the Play store) claims it's not properly installed (and Battery Charge Limit app claims similar). Has anyone seen this or have a clue how to overcome (I.E. is there a change I need to make in one of the partitions, do I need to re-root the phone after installing the above stock firmware, etc.?)?
You probably have bootloader unlocked but lost root when you cross flashed. You need to patch boot_a with magisk and flash that in fastboot.
Nailed it. I didn't realize flashing stock firmware also reset the root status. I had to go back into device manager to manually install the Android bootable driver again since fastboot wasn't seeing the device (I only crossflashed less than 3 weeks ago) and don't recall manually uninstalling this driver. There's also an instruction that doesn't seem to apply in the Magisk boot instructions (emphasis mine), specifically #11:
Boot_b hadn't been mentioned up to this point in said instructions (nor had that particular renamed image file). Is this evidence of dual booting capability (and perhaps copied over from some other tutorial)?
Finally, do we expect anymore firmware updates for this device or is it likely EOL since we're coming up on 2 years?
Yes, I should have mention that - boot_a and boot_b are the same thing, android uses what is called "Seamless updates" ,when upgrading OTA .
('seamless updates', allows for firmware updates to be installed to a secondary partition while the phone remains in use. this eliminates downtime between firmware updates to a single reboot, after which the secondary partition becomes the main one and the update has already completed. this also acts as a failsafe in case an update goes wrong – the system can fall back on the previouous partition.)
I do believe V60 will most likely see A12 update soon.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I just downloaded and installed Android 12 today actually. I'm on metro pc's (t-mobile). Hope is not lost.
I'm curious to see if root would work for Android 12 still. It would be nice if I could get wifi calling working for t mobile on this unlocked sprint phone..1
Give it try,but probably not.If it's a variant you can download the firmware for and do an LGUP refurb it may work.I would relock the bootloader first then do the LGUP refurb. so you don't run in to any problems.1
You're all making it so difficult for yourself guys, no update? No problem, just download the kdz and use the upgrade option. No need to relock the bl a thousand times.1
W0t?? The bootloader is unlocked and there is no check. Just use Standard LG root method with patching boot partitions.1
Yes,there is kdz's for A11 but none for A12 as of yet.And the only way it will OTA update to 12 is the bootloader will have to be relocked and not rooted or it won't update. -
19Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you.
The firehose is attached below.
DISCLAIMER: I am not responsible for any damages this may cause as I am merely translating the guide, I am not responsible for you bricking your device because of a missed step so read carefully,
Also, Please backup your data beforehand as this does wipe the phone. Also please note that if you are on android 11 LG Backup will not work after unlocking, neither does the LG Bridge tool.
***IF YOU WANT ANDROID 12, UPDATE BEFORE ROOTING, I HAVE CONFIRMED IT WORKS FINE***
Requirements:
- Get QPST Here
- Get the FIrehose Here
- Engineering Bootloader Here
- Adb and Fastboot Here
- Qualcomm Drivers Here (When installing make sure to select wwan)
- Frp with oem unlock bit set for Verizon Here Not for demo units!
- Slight knowledge of the command line
- A Brain
- If you already have it unhidden go to Developer Options under Settings -> System and enable OEM Unlock as well as USB Debugging. If you don't see Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom. Verizon Users: You will not see the oem unlock option, we will fix this later in this guide.
- 2) Get it into 9008 Mode: (This may take several tries)
- Make sure you are connected to your computer via USB.
- Hold Volume Down and Power until it shuts off
- Now here's the tricky part, as soon as the screen turns off, immediately start tapping volume up quickly, but do not let go of volume down and power, if you did it successfully you will see your screen is off but it appears either in Device Manager or Windows plays the Device Connected sound.
- Open and Configure QFIL as shown below:
- After that click Browse and select the Firehose you downloaded earlier
- Next go to the Tools menu at the top then select Partition Manager (If this errors please reboot back into edl using the steps mentioned above!)
- After that wait for QFIL to connect then a new window will pop up. FInd abl_a and abl_b, right click on each and click Manage Partition. First thing you want to do for each is click Read Data. This will back them up in case of anything going wrong. QFIl will tell you where it stores them. Then for each click Load Image and select the Engineering Bootloader you downloaded from before.
- Once you get that done for both abl_a and abl_b click close on both the Raw Data Manager and Partition Manager and wait for QFIL to say Finish Reset to EDL in the logs at the bottom.
- Now it's time to get into Fastboot.
- Press and Hold Power and Volume Down for 9 seconds
- Once you either see it disappear from QFIL or you hear it disconnect from your PC, let go of power, until you see Fastboot Mode on your Phone's screen.
- Open the command prompt on your computer.
- Once it's in fastboot verify if fastboot can see it by doing fastboot devices, if it can't see it troubleshoot here:
- Check your USB Connection
- Double check you installed the adb and fastboot stuff from earlier in the post
- There may be a chance WIndows doesn't recognize it properly. So follow these steps:
- Open Device Manager by doing Windows + X and clicking Device Manager
- There may be an already open row that says Unknown Devies
- Right click on android and select Update Drivers
- Select Browse my computer for drivers
- Select Let me pick from a list of available drivers
- Select Android Device
- Select Android Bootloader Interface
- Click Ok on the pop up
- Once that finishes double check the phone can be seen in fastboot devices
- Now here comes the fun part, unlocking! Please make sure you have your data backed up.
- If you are on verizon (and it's not a demo unit)
- Make sure you downloaded the file from above for the unlocked frp
- Do fastboot flash frp frp.img
- Do fastboot reboot and let it boot into android once, no need to set it up
- Reboot back to Fastboot using step 9
- Do fastboot oem unlock
- Select Unlock the Bootloader using volume down and power, your phone will wipe and reboot
- On any other variant
- Do fastboot oem unlock
- Select Unlock the Bootloader, your phone will wipe and reboot
- If you are on verizon (and it's not a demo unit)
- And that's it! Rooting guide will be on post 3.
8Rooting with Magisk:
You need to have already done the unlock mentioned above
- Go back to the guide and go all the way to the Partition Manager part, but don't flash anything.
- Now find and right click boot_a, click Manage Partition Data, and click Read Data do the same for boot_b.
- Wait for that to finish, when it does QFIL will tell you where it stored it.
- Grab the file and place it somewhere as a backup.
- Rename it to something like boot_a.img and boot_b.img
- Either use an existing device with Magisk or restart your device and install the magisk app from Here (make sure to download the Magisk-v2x.x.apk)
- Transfer the images you got to your phone in whatever method you'd like.
- In the Magisk App where it says Magisk, click Install, then choose Select and Patch a File. Make sure to patch both boot images separately!
- Wait for that to finish, after that transfer the modified image back to wherever you want to keep it. To make it easier rename it to something like MagiskPatchedBoot_a.img and MagiskPatchedBoot_b.img
- Get into fastboot by Either:
- Shutting the phone off, and holding volume down while plugging in the usb cable
- Do adb reboot bootloader if you have adb debugging setup.
- Now in the directory of your patched image do fastboot flash boot_a MagiskPatchedBoot_a.img and fastboot flash boot_b MagiskPatchedImage_b.img
- Now do fastboot reboot and you're golden!
4Hey! I'm in the same situation as you, carrier unlocked ATT ebayed to Europe, stuck on A10. Were you be able to crossflash? If so, i would thank you deeply for a quick rundown on the steps
- Download and install QPST, when installed launch it and select the firehose and Nand type e.g. UFS.
- Download and install this LGUP from here: . In the installer select "Install LG Drivers"
- Put phone into edl mode, here is how: Hold Vol- and pwr, when the screen turns black keep holding them and Repeatedly press vol+ You will see "Qualcomm HS-USB QDLoader 9008" under "Ports (COM & LPT)" in device manager when it is in edl. If the screen shows anything after reboot, instantly retry again.
- When it is in EDL Mode, open partition manager and make a backup of these partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
- After backing up, erase the same partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
- Now after erasing it is sort of important to not let it boot to android, and instead boot to download mode. Here is how: force reboot with vol- and pwr button. As soon as it disconnects from windows, Release the Vol- and Power buttons and hold Vol+ to get into Download Mode.
- When it enters Download mode, open LGUP and select partition DL. Select your favourite V60 KDZ too.
- 8. Click on start, then it will prompt you to select partitions that can be flashed, select every partition EXCEPT "SID_A SID_B AND ABL_A ABL_B" then confirm.
(NOTE: DO NOT CLICK "SELECT ALL" IT IS BUGGED AND WILL FLASH ALL PARTITIONS, EVEN IF UNSELECTED AFTER)
- Let it install, after that you should be done, hidden menu won't work but you can install this apk to be able to enter hidden menu and fix the fingerprint on an unlocked bootloader.
Written by: Leronex
3Misc Fixes:
- Open the dialer and dial: ` *#546368#*600# ` | Verizon (V600VM): ##228378 (+ send)
- SVC Menu > Handprint > HandID Logging = ON | ON VERIZON SKIP THIS STEP
- Device Test > SAAT > Service Menu – Manual test > Optical Fingerprint test Complete the test and when a green circle shows tap it, when you see a button “pass” click it. At the end it should fail so just click the “fail” button when there is no “pass” button anymore. Start the test by clicking "start", then hold the green circle with your finger till the test finishes. On the last test it will fail so just click on "fail".
- Repeat 3 times and try adding a fingerprint, if fingerprint still does not work just restart and retry again.
- Download system systemrw_1.31d_BUNDLE.zip from https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
- Place folder systemrw_1.31d in /data/local/tmp on the phone
- Place sysrw_repair_v1.31d on your linux machine
- Go to adb shell, su and then do "chmod +x /data/local/tmp/systemrw_1.31d/systemrw.sh"
- Then in adb shell do cd /data/local/tmp/systemrw_1.31d and do ./systemrw.sh size=15 or 20 and wait till its done
- Go to the linux machine and cd to sysrw_repair_v1.31d from step 3
- Connect adb with your phone and make sure to not accidentally disconnect it (This will take a while)
- In the sysrw_repair_v1.31d directory, do sudo ./sysrw_repair.sh and make sure your Linux machine has at least 25gb Storage space, this process will take more or less 30 mins depending on how fast the machine is
Make sure to follow the guide to make /system rw or else you will end up in a non bootable system!
1. Add these lines below to your build.prop (First set permissions on the build.prop so you can write it)
Code:Debug Options persist.dbg.ims_volte_enable=1 persist.dbg.volte_avail_ovr=1 persist.dbg.vt_avail_ovr=1 persist.dbg.wfc_avail_ovr=1 # Radio Options persist.radio.rat_on=combine persist.radio.data_ltd_sys_ind=1 persist.radio.data_con_rprt=1 persist.radio.calls.on.ims=1
Make sure to set the Permissions back to chmod 600
2. Reboot, go to settings > Networks > Calls > Enable WIFI Calling
3. If it won't turn on by itself you might need to enter the Service menu and go to SVC Menu > VoWIFI > WIFI Calling Toggle = 1
Credit: Leronex (Discord), Leronex_1 (XDA)You must make /system RW using the guide above
1. adb shell, pm uninstall -k --user 0 com.lge.rctprovider
2. adb reboot bootloader, fastboot erase rct, Reboot to System
3. adb shell, pm uninstall -k --user 0 com.lge.srtc
4. Download and install the Magisk module: https://github.com/null-dev/lg-v60-rct-disable-magisk/raw/master/lg-v60-rct-disable-magisk.zip, then reboot the phone.
5. Delete /mnt/product/persist-lg/rct folder
Done, how to check if it is disabled? "Adb shell", "su" and "getprop | grep rct". If it shows nothing as output that means the service is not running. After that check the service menu *#546368#*600# > SVC Menu > LG RCT (Has to say Disabled)On TMO After 20j:Code:adb shell pm uninstall -k --user 0 com.lge.lgdmsclient
Code:adb shell pm uninstall -k --user 0 com.lge.android.atservice adb shell pm uninstall -k --user 0 com.lge.gdec.client adb shell pm uninstall -k --user 0 com.lge.lgfota.permission adb shell pm disable --user 0 com.lge.pickmeCode:adb shell pm disable --user 0 com.lge.phonemanagement1. Download and install QPST, when installed launch it and select the firehose and Nand type e.g. UFS.
2. Download and install this LGUP from here: https://drive.google.com/file/d/1VxecFNYK2Lr7w1HVg-mNIGEoVa8CSHFt/view?usp=sharing . In the installer select "Install LG Drivers"
3. Put phone into edl mode, here is how: Hold Vol- and pwr, when the screen turns black keep holding them and Repeatedly press vol+ You will see "Qualcomm HS-USB QDLoader 9008" under "Ports (COM & LPT)" in device manager when it is in edl. If the screen shows anything after reboot, instantly retry again.
4. When it is in EDL Mode, open partition manager and make a backup of these partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
5. After backing up, erase the same partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
6. Now after erasing it is sort of important to not let it boot to android, and instead boot to download mode. Here is how: force reboot with vol- and pwr button. As soon as it disconnects from windows, Release the Vol- and Power buttons and hold Vol+ to get into Download Mode.
7. When it enters Download mode, open LGUP and select partition DL. Select your favourite V60 KDZ too.
8. Click on start, then it will prompt you to select partitions that can be flashed, select every partition EXCEPT "SID_A SID_B AND ABL_A ABL_B" then confirm. (NOTE: DO NOT CLICK "SELECT ALL" IT IS BUGGED AND WILL FLASH ALL PARTITIONS, EVEN IF UNSELECTED AFTER)
9. Let it install, after that you should be done, hidden menu won't work but you can install this apk to be able to enter hidden menu and fix the fingerprint on an unlocked bootloader. https://drive.google.com/file/d/1g-7BQ_Jlmi-5tpbMg383LaiYr5YjTmqQ/view?usp=drivesdk3
One question in advance:
If your device has a SIM lock, what I'm going to write here might not work for you.
But more like a refusal of the LGUP tool to do the flash shouldn't actually happen.
As a first step you should select yourself in the following menu:
* # 546368 # * 600 # ---> SVC Menu ---> MID Info
Save or write down the data specified there, especially the data under "MID Values".
Furthermore, write down the values of the IMPL and FUSG
I'm assuming that you have the right firmware for cross-flattening as a kdz file. I did several steps ...
First from AT&T to Verizon, then from Verizon to TMO and then from TMO to EA (EUR). I did it for no particular reason, I just tried it out.
I used LGUPCMD as a tool (see appendix). In the archive you will find detailed instructions on how to use the tool. I hope you know how to work with command line ...
Before you get started, 2 more questions:
Which software version do you have now?
Which software version do you want to end up with?
With Crossflash, I would not update from Android 10 to 11 straight away, but do it in a second flash as an upgrade.
But then you need the GUI version of LGUP (also in the appendix).
You will most likely get an NT code error at some point, don't get nervous, you can get rid of it relatively easily, preferably in Android 10 ...
