WTF Bootloader Unlock, TWRP Install and Root
READ in Web Browser, NOT an app!
Do NOT try this with T-mobile H932. You will brick your phone. H932 has different RSA encryption from any other V30 variant. To root T-Mobile H932 V30/V30+, go HERE.
Unlocking bootloader/rooting your LG V30/V30+/V30S does NOT remove any LG stock firmware features. Very common question due to Sony phones. This is not a Sony phone.
WTF V30/V30+/V30S Bootloader Unlock and Root
(For Every Variant EXCEPT T-Mobile H932)
1) fastboot flash commands
2) LG Oreo firmware with the bootloader unlock exploit. (Pre-July 2018 Android security patch firmware; don't worry, we can get you there.)
That's a WINNING combination.
Here's what we will be doing:
It's not complex. Will take you 20 minutes IF you're prepared with all necessary files downloaded.
* Convert to model with early Oreo and fastboot flash commands,
if you don't already have that. (Pre-July 2018 Oreo firmware; don't worry, we can get you there.)
* Flash bootloader unlock code.
* Install TWRP.
Confirm TWRP is installed.
* Flash "no encryption" file and "no check root" file.
* Root.
* Done.
The instructions are detailed, but the procedure isn't complex, really. (See Section 7 for trouble-shooting tips, if you need them.)
_______
US998 and all H930* variants on early Oreo have fastboot flash commands and bootloader unlock flaw. (With pre-July 2018 security patch firmware; don't worry, we can get you there.) At present, if you have post-July 2018 Android firmware, you can temporarily downgrade to unlock your bootloader.
That's why you need to convert your V30/V30+/V30S to early Oreo on one of those models,
IF it's not already one. North American variants V30/V30+/V30S would use US998 Oreo, while the rest of the world V30/V30+ would use H930 or H930DS Oreo.
The rest of this post tells you how to do that, provides the tools and answers all your questions.
PRINT OUT AND READ SEVERAL TIMES.
FAQ on V30 CUSTOM ROMs < READ, then come back here.
________
All credit goes to @TxanMoe who accidentally discovered this bootloader unlock exploit. He shared it with us, shot a video explaining. He started out with an AT&T H931, ended up with bootloader unlocked, rooted US998.
He found the LG Oreo update to V30/V30+ has an XDA-friendly exploit which allows easy bootloader unlock and root for MOST V30/V30+/V30S variants. LG has now patched this, but you can temporarily downgrade to earlier Oreo firmware.
(actual screenshot from @TxanMoe's video)
Even though it's fairly simple process (just flash fake bootloader unlock.bin file), there were requests for someone to write up the exact steps. Here you go.
Thank you also to
@Wotta whose
bootloader unlock and root guide I cribbed a lot of steps from.
Please go to that link and thank him! I am giving him full credit for that section. I changed very little. He worked very hard to create that guide.
I: INTRODUCTION
In my opinion
the LG V30/V30+ ("plus" only denotes more internal memory, nothing else) was the "Best Phone of 2017".
*
2017 Galaxy Note 8 came in CLOSE second, but due to more comfortable size the V30 won.
* With
2018 Galaxy S9 and S9+, again due to Goldilocks size LG V30/V30+ is my choice -- even though the 2018 phones have newer Snapdragon.
* The end-of-2017 V30/V30+ was really what the early-
2017 LG G6 SHOULD have been, which LG crippled with their stupid "regionalized" specs scheme.
* Hardware-wise with Qi wireless charging, 3.5mm headset jack, quad DAC, and microSD slot, the "V30" series has features other phones like the
2017 Google Pixels SHOULD have. (Google forbids microSD slots, but they gave up Qi wireless and headset jack for no good reason when they were an early advocate of Qi wireless; Google razzed Apple in 2016 for ditching the headset jack, yet they did the same in 2017.)
* With 1440p OLED, Qi wireless, and IP68 dust/water resistance the
LG V30 is what OnePlus PRETENDS to be. All top-tier Androids (Samsung, LG, Motorola, HTC, Sony, etc.) have at least 1440p since 2014. Same with high IP ratings in recent years. OnePlus has no excuse for not having those features, IF they claim to be a premium phone.
The only negative to the V30 is LG doles out "official" bootloader unlock code to only 3 variants, via LG Developer Bootloader Unlock website. LG approved IMEI with Device ID must be submitted for official bootloader unlock.bin which can be flashed via fastboot. Also, LG doesn't honor their own promises. They never gave bootloader unlock to the Open Market US998 V30+/V30S, and the Open Market US998 V30 only has LG bootloader unlock through hacking the dropdown menu of the website.
HOWEVER, @TxanMoe discovered that with the early Oreo updates, all V30/V30+/V30S can now flash a fake bootloader unlock code. Then flash TWRP and root via Magisk -- just as if you had used LG's official bootloader unlock. Crazy, huh? But it works.
Starting with the July 2018 security patch, LG has blocked this exploit but you can revert to prior firmware with dev patched LGUP. HA!
________
2: WHO CAN UNLOCK THEIR BOOTLOADER/ROOT USING THIS METHOD?
Only the T-mobile H932 can not.
Do NOT try it with T-mobile H932. You will brick your phone. To
root T-Mobile H932 V30/V30+, go HERE.
South Korean carrier models more difficult. They
can bootloader unlock and root -- but getting modem back is a couple extra steps.
@bilong9 has solved
the problem:
Hi. I have fixed my phone wave (radio/modem).
He created a
separate thread for Korean variants to help others.
Everyone else with V30/V30+ can bootloader unlock, root, have working modems, and even more. I'll explain further down.
This also works with the 2018 LG V30S -- which is just another V30 variant (same code name JOAN). Needs to be on pre-July 2018 Oreo firmware, to which you downgrade.
TLDR:
For the V30/V30+, flash the fake bootloader unlock.bin file on early Oreo US998, Oreo H930* (including G, D, DS) firmware. North American variants will temporarily
convert V30/V30+ to US998 (via
Frankenstein method) and then do that.
* All North America variants will use pre-July 2018 Oreo US998 KDZ. (But will need to go through Frankenstein first if not already on US998.)
Do NOT try this with T-Mobile H932. You will brick your phone.
* All H930G can use pre-July 2018 H930 Oreo KDZ firmware.
* For H930D/DS, you can use
your region early Oreo KDZ or pre-July 2018 H930 Oreo KDZ. India H930DS should use
pre-July 2018 IND H930DS Oreo KDZ so they have have India-specific VoLTE.
* South Korean carrier variants
could also use H930 KDZ but be careful with modem. (There's more instructions
Korean carrier variants here, thanks to
@darkidz555 and
@bilong9 for their help with this.)
Here's the newest self-made unlock.bin file from
@TxanMoe:
try this one new_unlock.bin
https://is.gd/Jmy39s
Also, I attached it to this file to this post as a zipped file. Unzip it.
________
3: PREP
- Download/install LG Mobile Drivers for Windows.
- Download/install Windows ADB to Windows. When installing, right click on the .exe and "Run as Administrator". Temporarily disable antivirus when installing. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Here are 3 different ADB installations to choose from:
If you can't get the new_unlock.bin to flash successfully, in the Section 7-Trouble Shooting Tips we will ask you to try ANOTHER ADB installation.
- Enable known extensions on Windows PC. Also, make Windows Hidden Files and Folders visible.
- Download either US998 Oreo KDZ or European H930 Oreo KDZ, depending on the phone you have -- with pre-July 2018 firmware.
* North American variants (AT&T H931, Canadian H933, Sprint LS998, Verizon VS996, etc) would use pre-July 2018 US998 Oreo firmware AFTER Frankenstein.
* European H930G would use the pre-July 2018 firmware KDZ.
* Most H930D/DS would use their region's pre-July 2018 Oreo KDZ.
Alternatively, then either use the pre-July 2018 H930 Oreo KDZ or this CIS H930DS Oreo KDZ.
* India H930DS would use the pre-July 2018 IND H930DS Oreo KDZ, which has India-specific VoLTE for carriers like Jio.
* If you have a native US998 or H930 and you are not on early Oreo, you need to upgrade/downgrade to pre-July 2018 KDZ. This exploit does not work with stock Nougat or Pie.
* V30S needs pre-July 2018 Oreo KDZ.
- Download current TWRP-3.2.3-7-default.img from this page. Rename it TWRP. If you've enabled known file extensions, you will really see TWRP.img. Do NOT add the ".img" -- it should already be there. If it's not, go enable "known file extensions" in Windows!
- Download @TxanMoe unlock.bin from this link or use the zipped file attached to this post. Unzip it, of course. This is the MAGIC.
- Download attached Magisk 18.0
- Download @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler), or use attached file.
- Download @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler), or use attached file.
(Put these last three on microSD card if you have one. If you don't, then drag these files over from PC later in TWRP and flash them as instructed below.)
___________
4: WHAT'S NEXT?
* If you have US998 or any H930 variant, are on pre-July 2018 Oreo already, then go to Section 5.
* If you have US998 or H930, are on Nougat or Pie, then you need to use Dev Patched LGUP (attached to post #1 of both the
US998 and
H930 Oreo KDZ threads) to update/downgrade to pre-July 2018 Oreo. Then go to Section 5.
* If you have any other North American variant than US998, then use the
Frankenstein method to convert to Oreo 20a or 20b US998. (You can update to newer firmware after unlocking bootloader.)
Read that Frankenstein post carefully; you have to flash to Nougat US998 first, THEN to Oreo US998. You should NOT avoid those steps. That post is my documentation for converting LS998 V30+ to US998 V30+. Adapt to your model.
After completing that, then go to Section 5.
* If you have European H930G just use
LGUP to convert to Open Market H930 with pre-July 2018 Oreo KDZ. Now go to Section 5.
NOTE: All H930 variants have fastboot flash commands. But you still need pre-July 2018 firmware. H930D/DS users will still have dual SIM functionality even on Open Market H930 Oreo KDZ.
However,
India H930DS users should use
[STOCK][OREO]LG V30+ IND H930DS 20b KDZ for India carrier VoLTE. This version of firmware is safe, as it pre-July 2018 security patch. You can upgrade to newer firmware later after bootloader unlock.
__________
5: LET'S GO -- UNLOCK BOOTLOADER
Confirm you’re in developer mode. If Settings doesn’t show Developer Options, go to Settings/About Phone/Software Info, click Build number 7 times.
As per the
LG Dev page, confirm Developer Options “OEM Unlock” and “USB Debugging” are enabled.
Connect to USB and switch to Photo Transfer Mode. (If you’re a normal user, you probably default to USB. You need Photo.)
A prompt will appear on your phone to ask you to accept this PC to be authorized for USB Debugging.
On your PC, copy the new_unlock.bin you downloaded into your Android development tools directory (in my screenshots, sdk\platform-tools).
Next
open command window inside that folder.
Inside that command window, run (type and hit enter):
adb devices
to ensure the device (and only the device) is listed. If it’s not listed, verify that Photo Transfer mode. Sometimes you will need to do this step again, to ensure it eventually shows your device.
(This screenshot by @Wotta shows flashing unlock.bin. But you will really be flashing new_unlock.bin.)
Reboot phone into Fastboot mode
adb reboot bootloader
You should hear the Windows sounds of USB devices going and coming. And the phone has an odd screen.
From the same directory (Android tools),
fastboot flash unlock new_unlock.bin
THIS IS IT. This should take only a few seconds to run, but on one phone I rooted took three minutes. Be patient.
Reboot with: fastboot reboot
You will now get entirely different start-up screens than normal -- it shows a warning that your device cannot be checked for corruption. (and a reference to
http://g.co/ABH) This is just the "bootloader unlock warning" screen.
It's just a scary picture LG shows you as the phone boots to discourage you from unlocking your bootloader.
Ignore it. It will
NOT prevent you from doing anything.
Your phone has now been hard reset.
Now your phone has been wiped, so you need to go through the initial phone setup options, to get to Android. Switch USB to Photo Transfer again.
You can verify that it’s unlocked either from the Developer Options – OEM Unlock is no longer available because it’s already unlocked, or by verifying Unlocked with getvar
(In a few days, the OEM Unlock option will be available again. It's just greyed out immediately after this process.)
________
6: INSTALLING TWRP AND ROOTING
Installing TWRP:
1. Switch to developer mode, USB debugging. (OEM Unlock is now not selectable right now, greyed out. In a few days it will again be selectable.)
2. Switch USB to Photo again; default is charging.
3. As before,
on your PC from the Android tools directory,
adb reboot bootloader
4.
Fastboot flash recovery TWRP.img (Remember you re-named this file to just TWRP.img earlier.)
(Thanks to @tech_infinity for this recent screenshot. February 2020.)
Do NOT reboot your phone after flashing TWRP! Instead, immediately boot to TWRP by using this command:
fastboot boot TWRP.img
Ignore the bootloader unlock warning, which is your new splash screen. Eventually you will boot into TWRP.
6.
INITIAL TWRP ACTIONS!
a. At the bottom of the screen,
immediately swipe to allow modifications. Do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.
b. Back up the system. This isn’t essential, but you’d be silly not to. (Has saved more than one person.) Select “back up”.
c. Select the microSD card for backup (or USB OTG).
d. Back it up. This will take about 10 minutes if written to micro SD card.
e. Do
NOT install the TWRP "app" if offered.
7.
MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do
before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip.
(This is to give the encryption disabler root privileges)
d. Install the Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install the AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select
reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again.
(This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
(Thanks to
@jdgesmlls for helping to re-write that previous section to clarify better. Also thanks to
@downwiththebanksters for giving the entire post a thorough inspection to clarify/explain various points better.)
If booting fails with an encryption error, did you
format (f above) the partition? If not, reinstall TWRP and go through the steps again.
You will now have a factory reset phone, and have to set up the phone again, but should have root (via
Magisk.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot to LG Oreo, install THIS app to easily facilitate rebooting to TWRP recovery in the future:
NOXX Advanced Power Menu
Also,
please make another TWRP backup.
TLDR:
* flash twrp:
fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
* boot twrp:
fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
* swipe to allow modifications
(do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
* select WIPE data
* wipe caches
* flash Magisk
* flash encryption disabler
* flash root check disabler
* FORMAT DATA, type yes
* reboot to TWRP
* re-flash Magisk
* reboot to system
STRONG SUGGESTION: After successfully doing all this, when you finally boot to LG Oreo, install THIS app to easily facilitate rebooting to TWRP recovery in the future:
NOXX Advanced Power Menu
Also,
please make another TWRP backup.
________
7: TROUBLE SHOOTING
MOST people have no problems. If you do, look through this list.
1) You can't flash the new-unlock.bin code.
Look at your current "About Phone". You want to confirm you're on early Oreo with pre-July 2018 security patch firmware.
Example: For any North American variant you Frankensteined, ensure you are on
US998 Oreo 20a or 20b (pre-July 2018) firmware.
2) If you can't flash the new_unlock.bin code or you can't flash TWRP.
* Look in your ADB folder on your PC and
confirm all known Windows file extensions enabled.
* Confirm
all Windows hidden files and folders are visible.
If that doesn't help, try this:
3) Confirm USB debugging is on in Developer Options, and your
PC has authorization for your phone.
4) Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
5) Re-install
LG mobile drivers.
6) Try another USB cable.
7) Installing
this Windows driver found attached to this post. (Thanks
@gazzacbr and
@FZZF.)
8) Install
Google USB driver. (Thanks
@s0lidsneak.)
9) Or try another USB port on your computer or
try cheap USB 2.0 hub
10) Error message "too many links"? Install
this bat file.
11) Reboot the computer.
12) Try another computer. (THIS usually
solves the problem. Kudos if you find an an
old Win7 PC.)
13)
Master Reset (full reset of phone using hardware buttons). Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
_____________
8: SETTINGS
I know everyone has their own settings, but for new owners who want a reference point for all the various submenus and customization, I'll share screenshots of my settings. You can always change to what you like.
https://is.gd/K9Fkw3
_____________
9: EXTRAS - MODEMS, RESTORING VARIANT FIRMWARE, UPDATES TO LATEST FIRMWARE
If you now have bootloader unlocked, rooted "US998" (either native or other North America variant converted) you will now have these bands:
http://www.lg.com/us/cell-phones/lg-US998-Unlocked-v30
US998
CDMA: 800 MHz CDMA
2G GSM: 850/900/1800/1900 MHz
3G UMTS (HSPA):850/900/1900/2100 MHz
4G LTE Bands: 1/2/3/4/5/7/12(17)/13/20/25/66
Frankenstein changes everything for North American phones, including bands.
Whereas, if you have native
"EU H930", you have these bands below.
Flashing any H930 variant to other H930 variant does NOT change bands for those variants, it only changes firmware.
EU H930
2G GSM: 900 / 1800 / 1900
3G (HSPA): 850 / 900 / 1900 / 2100
4G LTE: 1/2/3/4/5/8/12/17/20/28/38
REPEAT: if H930DS you will have your same H930DS modem bands even though you are on EU H930 firmware.
__________
UPDATE H930, US998, H930DS with latest stock firmware TWRP-flashable "ROMs"
After using early Oreo firmware to bootloader unlock, install TWRP and root, you can now update to latest Pie or last stable Oreo firmware by flashing these zips in TWRP:
Do
NOT crossflash any North America variants like US998 with any stock H930* firmware!
__________
You would want to use these carrier-branded
stock firmware TWRP-flashable "ROMs" below if the variant you need has bands or features that the "converted" US998 phone does not.
NO, you cannot flash T-mobile modem over any of these. T-mobile modem partition has different RSA encryption. But you can flash other modems.
For Verizon customers, download and install
@JohnFawkes's
TWRP-flashable stock "ROM", based on latest VS996 Pie KDZ to get Verizon voice mail, VoLTE and Wi-Fi calling.
After flashing it in TWRP, then just re-install Magisk. Debloat with Titanium backup.
________
For AT&T customers ONLY, download and install
@david.542569's
TWRP-flashable stock "ROM", based on recent H931 Oreo firmware to get AT&T Wi-Fi calling and video calling. (There is no Pie TWRP-flashable zip and probably never will be.)
After flashing it in TWRP, then just re-install Magisk.
H931 owners: If you are NOT on AT&T network, then stay on US998 firmware! AT&T firmware is ONLY for AT&T users.
________
For Sprint customers ONLY, download and install
@JohnFawkes's
TWRP-flashable stock "ROM", based on Oreo LS998 firmware to get the extra Sprint LTE bands back. (LS998 never got Pie from Sprint/LG.)
After flashing it in TWRP, then just re-install Magisk. Debloat with Titanium Backup.
I've been running it over a full day now, debloated and tweaked a bit. RCS and VoLTE is working after ##72786# and a PRL and profile update. Thanks again!
Sent from my LG-LS998
Also, more
Sprint resources here. Thread created by
@JWnSC, for Sprint users. Some information may be outdated due to the newer TWRP-flashable ROM above, but still may help answer other questions.
_________
Korean variants should follow these instructions by
@darkidz555.
@bilong9 has made a helpful video for Korean carrier variants:
https://is.gd/m3bAeA
Read
more in this thread for the Korean carrier models, created by
@darkidz555.
Here's a
TWRP-flashable zip "ROM" for Korean variants, thanks to
@koo04034.
@bilong9 update to
Korean Pie.
_____________
9A: EXTRAS -- LG V30 Unlocked Bootloader Warning Disabler
When you unlock your bootloader, LG throws a "scary" warning picture at you every time you reboot your phone:
It doesn't hurt anything, but it can be annoying. If you want to get rid of it, keep reading.
This was a TWRP-flashable zip file from ROM Dev
Aeronliru, a.k.a.
AeronLee:
=======
Unlocked Bootloader Warning Disabler
Compatible with H930, H930D, H930DS, V300, H933, US998, LS998, VS996, H931, T-Mobile H932 with both
Pie & Oreo firmwares. CHECKED!
=======
There was a
dedicated thread for this mod. The developer asked me to post it to help people -- but then he left the community and then he asked me to remove it. I did.
However,
someone found you could still access the
original post with downloadable zip attachment in the Internet Wayback Machine (which shows historical posts).
< That is the post where it's discussed in that thread. If you click on the link in that discussion, you should see the original post with attachment. (You may need to disable any VPN to access the historical thread in the Wayback Machine.)
I am still honoring the Dev's request, as I indeed removed the attachment -- but if people can still access it in
other ways I can't stop them. All credit for this mod goes to genius
Aeronliru, a.k.a.
AeronLee.