So I had a bit of a hiccup trying to go from US998 to H933. The plan was to go from US998 Oreo to H933 Oreo and then update to Pie with the TWRP zip. But I never made it that far. Many things happened before getting back to US998 Oreo, which was my original starting point, but they should be irrelevant.
General disclaimers apply. Do this at your own risk. I've only done this one time on my phone with help and advice from @cloud1250000. This hasn't been "tested" further then that and this guide was written after the fact.
Please read the entire guide first then go back and follow step by step.
Prerequisites:
adb installed - Follow 3rep, steps 1, 2 and 3. here to install.
LG drivers installed
LGUP dev patched installed - located here - Courtesy of @tecknight.
See "HOW TO INSTALL DEV PATCHED LGUP" to install
Needed Files:
Stable TWRP 3.2.3.7
Original Pie recovery aka "original-recovery-pie.img" - Courtesy of @cloud1250000
Original Pie laf aka "laf-pie.img" - Courtesy of @cloud1250000
H933 Pie kdz - H93330k_00_OPEN_CA_OP_0906.KDZ
You'll also need:
AnyKernel 3 RCTD Remover - Courtesy of @JohnFawkes
Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) - Courtesy of @Zackptg5
Magisk - latest here or v19.3 direct link
Rename TWRP-3.2.3-7-default.img to TWRP.img
Place the following on the root of your microsd card (though you could put it on your internal sd, you would just have to adjust the paths)
TWRP.img
original-recovery-pie.img
laf-pie.img
You can put these anywhere you like on your sdcard
AK3_RCTD_Remover.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Magisk-v19.3.zip
0) WARNING - You will be formating the internal data partition. Backup/move files from the internal storage or you will lose them!
1) Start with a H933 phone that has been converted to US998 on an Oreo rom, with bootloader unlocked. I was on this kdz specifically: US99820a_04_0330.kdz
2)Boot into download (vol + and plug in cable) mode/connect phone to the computer. Then open up the dev patched LGUP.
3) Select this kdz H93330k_00_OPEN_CA_OP_0906.KDZ.
4)Flash with partition DL, select all EXCEPT recovery.
5)It should reboot into recovery/TWRP
6.a) WARNING, Following procedure might be risky. Please read up on flashing laf and see if it's ok with you. I don't really know how risky it is, but I figured I would put in this warning.
6.b) Open a command window on your computer and run the following commands with adb. This puts TWRP into the laf partition and the stock recovery back into the recovery partition. Meaning we won't have TWRP in recovery but we will have a backup of it in laf, which we'll need. *inspired by @runningnak3d from the H932 root*
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/laf
dd if=original-recovery-pie.img of=/dev/block/bootdevice/by-name/recovery
7)Power off phone, turn it on. Let it do its thing for a bit, there will be a reboot and it will stay on LG logo for awhile. It should eventually boot to a setup screen. Great Pie is installed, now we need to install a few things in TWRP. Turn off the phone.
8)Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
9.a) Follow from step 7 from this post. There is some of step 6 that should be followed also.
If you followed all of that you should have installed Magisk, Disable_Dm-Verity_ForceEncrypt_08.18.2019, and AnyKernel 3 RCTD Remover and performed a factory reset and did a format of data.
9.b) The final step of the above should have had you boot into android, once you've done that you can turn off your phone
10) Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
11) Flash TWRP back to recovery by running the following command
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery
11.b)If you would like to restore laf (so you can use LGUP) then also run this to restore LG's download mode. *It can be desirable to leave in the laf partition also. By leaving it there if for some reason you lose TWRP in recovery then you can boot into download mode and you'll have TWRP there. This is a personal decision.*
Code:
dd if=laf-pie.img of=/dev/block/bootdevice/by-name/laf
You're done, you now should have a H933 phone on H933 Pie with root.
If your mobile data doesn't work or you're not getting LTE, check your apn setting and play around on your phone to see if it will pick it up. Check that mobile data is on etc. Remove sim, turn off phone, insert sim then turn on phone etc. If none of that works then:
Reboot to TWRP/recovery (you can do so in Magisk, modules, 3 dots, reboot recovery) and run:
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot and you should have data/LTE back
Big credit to @cloud1250000 who walked me through all of this, I was just a pawn. I can't thank Cloud1250000 enough!
Info and files taken from these posts:
https://forum.xda-developers.com/showpost.php?p=80363769&postcount=21
https://forum.xda-developers.com/showpost.php?p=80432411&postcount=135
Thanks to @cloud1250000 for the original-recovery-pie.img and laf-pie.img
Thanks to @ChazzMatt for all his help on the forums and I've linked to a lot of his stuff
Thanks to @runningnak3d for the inspiration for step 6b from his work on the H932 root. Please go here and click the THANK BUTTON!
Thanks to @tecknight for the DEV PATCHED LGUP! Please go here and click the THANK BUTTON!
Thanks to @Zackptg5 for the Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler)
I don't normally write guides but I had went through this and thought others would benefit from knowing the process. Please let me know if it needs some improvements.
nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?
cloud1250000 said:
nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?
Click to expand...
Click to collapse
Yeah, I'll ask mod to move it. I'll also reference it in the H933 Pie post #1.
Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.
bnevets27 said:
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.
Click to expand...
Click to collapse
Sort of, Step 8 of that guide did not work for me as I could not get into DL mode at that point, so I had to go back and dump the stock recovery, then flash it from within TWRP to get past that part. That guide also doesn't include the step to wipe modemst1 and modemst2 from TWRP, which was required for me to get data back.
I don't recall having issues with formatting data though, but honestly I was trying so many things I don't exactly recall what worked and what didn't. The whole process was a real pain lol.
cloud1250000 said:
Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..
Click to expand...
Click to collapse
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!
You can't use lgup to replace the recovery with the original one because download mode won't work until you master reset.. and master reset is done by the original recovery lool.. so the original guide won't work because of that. (If you switch from us998 to another model)
Twrp in laf is good and I'm glad I reviewed the h932 root thread for that reason lol BUT you do lose download mode and lgup.. but you can easily revert it back with twrp with the laf I provided..
Anyway, it's very straightforward to do the switch.
Also do not go down to nougat for master reset.. since it remove twrp from laf (surprisingly they removed that in the pie master reset.. also pie does it master reset by itself.. it's just the best.)
christopherrrg said:
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!
Click to expand...
Click to collapse
Make sure if you want to try customs roms to go with the h930 version (if available.. )
finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )
cloud1250000 said:
finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )
Click to expand...
Click to collapse
Did you brick your initial H933 or have you always been on ls998?
I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back
cloud1250000 said:
I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back
Click to expand...
Click to collapse
That's awesome! Great ending!
I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.
If it doesn't boot into TWRP, then what does it boot into?
Are you sure you're NOT flashing recovery?
BTW you might also find help in this telegram group
https://t.me/LGH933CAN
I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.
fljanders said:
I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.
Click to expand...
Click to collapse
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...
ChazzMatt said:
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...
Click to expand...
Click to collapse
It was, pretty sure there's nothing wrong with the guide, the concept makes sense it's just forcing LGUP to skip the recovery partition that's proving to be a challenge. I've got lgup_cmd installed though cannot find any info on how to specify Partition DL installation/skip recovery partition.
Following the guide I select Partition DL and the H933 pie kdz firmware, after selecting start I select all partitions and de-select Recovery however as below it seems to ignore that and flash the default recovery partition regardless:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
David X said:
I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.
Click to expand...
Click to collapse
Hey, not sure if anyone is still having issues with their devices not booting to TWRP after flashing 933 and therefore losing root + recovery, but after a day of trying to accomplish this on a non-Frankenstein US998 I realized how to force boot to recovery and preserve access.
Immediately when the phone reboots after flashing the .kdz...
Hold the power and volume down until you see the V30 logo, then release and reapply the power button.
Basically trying to master reset. Confirm repeatedly and it will boot to TWRP instead of wiping.
From there you can preserve TWRP, flash magisk, dm verity, etc. Golden :good:
Related
[Guide][Tutorial] Root TWRP LG G5 using Autorecowvery[H830 & V20A only][Noobfriendly]
This is guide to root and install twrp on lg g5 T-Mobile using recowvery method.
Read 4th post before proceedingThis method is to root & install TWRP on only T-Mobile LG G5 running Nougat 20a software. If your phone isn't on 20a then first downgrade/upgrade to 20a software.
Before asking a question, first, see FAQ in 3rd post. In that way you can save a lot of time.
For Video Guide refer to 5th Post
You need to disable antivirus before extracting files. Because we are using DirtyCow vulnerability here. Which is technically a virus (It's not dangerous for pc but for exploiting android to get root access). If you can't disable AV then don't proceed because process will not work
Download:1: Recowvery (2nd post)
2: Minimal adb (2nd post)
3: TWRP
A: H830 | For H850 (Refer to this Post and read carefully)
[Download TWRP 3.0.2 as 3.1.0 is having some little issues with flashing with autorecowvery] Always download latest TWRP available for your device to avoid most issues.
(rename it to recovery.img)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Procedure:Drivers should be installed. Also install minimal ADB and fastboot.
1: Make sure to unlock bootloader. Backup internal data because it will be erased.
A: First enable developer options and toggle “Enable OEM unlock” to ON. Also enable “USB Debugging”.
B: Run Minimal ADB and Fastboot. Enter Command
Code:
adb devices
C: You will see permission dialogue on phone. Tick “Always allow” and ok.
D: Now enter.
Code:
adb reboot bootloader
E: Now phone be in fastboot mode. Enter
Code:
fastboot oem unlock
F: This will wipe all data on internal storage. Now Enter
Code:
fastboot reboot
G: Now OS will get booted. Bootloader will be unlocked but phone should be in factory reset condition. So again enable “USB Debugging”.
THEN
2: Connect phone with pc in MTP mode and copy recovery.img to phone’s internal storage (Make sure to select MTP as always to avoid problem during procedure). Extract recowvery software. (If it causes permission problems extract it to USB device and perform process from there)
3: Run “EasyRecowvery.cmd”. Press “5” -->Enter then press “7” -->Enter to disable integrity check. Then enter “0” to go back. Skip it if you are using Recowvery G5 modified.
4: Now press “2” and wait until it says warning. Press “y” -->Enter. (It won't say warning in Recowvery G5 modified)
5: It will do rest process. After Flashing TWRP it will flash “no-opt-encrypt” (This is most important to save twrp from being removed by OS)
6: Phone will boot into TWRP. Here on phone it will ask for decrypt code. Cancel it. Swipe to allow modification.
7: On pc press any key, the flashing process on phone will automatically get started. Then it will reboot into OS.
8: To flash supersu, select option 3 from recowvery windows and phone will boot into twrp. Same as step 5-6 it will automatically flash supersu.
Now Your rooted and have twrp install.
Note: For removing Encryption.
To flash a custom rom and remove encryption in twrp, you need to once format data in twrp else you won’t be able to wipe and install any custom rom in your phone.
Attachments
Recowvery G5 modified is fully working, so you can try it.
I'm still keeping easyrecowvery 1.3 in this thread as a backup plan.
Read Read Read Before using This
Test Version --> Ricksy-Recowvery | Mirror
(Ricksy Recowvery is streamlined, checks free version of EasyRecowvery. It has no unlock checks, no model verification so use it only if you're fully sured about what you're doing. It includes but isn't limited to unlocked bootloader, USB Debugging Enabled, Being on V20a firmware, LG Drivers installed, PC allowed as Trusted in USB Debugging as always)
Remember to copy latest TWRP to root of internal storage as recovery.img before proceeding.
Old Test
There is also Addition of Recowvery G5 modified 2.0 Test version as well (This script has some additional features)
(I have also turned off most security checks, so you should have an more easy rooting experience. However, this increase risk of bricking device if you do not read things properly). If you can provide your experience of using this script please share your knowledge.
Download Test version either from here or here or through attachments
FAQ
Recowvery tool is causing permission errors when I run it through computer's internal HDD storage. What shall I do?
Ans: There are possibly 2 workarounds for that.
A: Extract the zip to external USB storage and Run the tool.
B: Change the name of folder, in which recowvery tool is, to "1" and copy to root of storage e.g. "Computer:\D:\1".
Can I re-lock my bootloader after rooting and TWRP flashing?
Ans: No, as recovery partition modified now, this will brick your device.
Can I use V20C or later on my phone after rooting and flashing TWRP?
And: You can't take OTA after rooting as this might create a brick but fortunately @autoprime created TWRP flashable zips of firmwares e.g 20c,20f,20i and he might create newer builds too. Anyways here's the Auto Prime's thread, Go to "LG G5 Files" link and download file as per your variant and choice.
I bricked my phone after following this guide and now I can access only download mode, what shall I do now?
I'm on other version than 20a, What shall I do?
Ans: Really? It seems like you're kidding because this guide can never harm your device, It can either do it's work or not but there is no way for it to brick a device (Unless you don't read carefully).
Ans: You can take your phone back to v20a by using the following guide.
AnywaysYou can always bring your phone back to life by following this Back to Life thread.
How to remove encryption in TWRP? or I'm unable to access my phone's internal storage from TWRP, What shall I do?
Ans: So for this process.
a: Boot into twrp.
(you can boot to TWRP by any app or by vol- and power button combination or from option “5” --> “5” in recowvery toolkit (command window).
b: In TWRP, cancel code Windows, Swipe to allow modification then
Click -->Wipe-->Format Data-->type “yes”-->enter.
You need to do this only once. After that you can flash roms and zips unlimited times.
Will this root method work on 20c/d/e/f or others?
Well, it shouldn't. Because I tried this on 20c and it never worked, so I believe it will not work on any software other than 20a because LG removed that exploit to root after 20a. But you can try your luck and tell me if you succeed.
a: Thanks a lot i have one lg g5 h830 and i have some fear to lose the unlocking and i want to modify the phone.
b: Same i have anyone please answer it will i lost the UNLOCKING (Modified by shopkeeper) if i FLASH another ROM?
What are you people trying to ask here?
Bootloader Unlock:
Bootloader can be locked and unlocked anytime you can to do so just by typing commands in fastboot mode. In T-Mobile G5 the fastboot mode do not accept flash command that's why we can only lock and unlock bootloader.
TWRP:
As commands are limited in fastboot mode of T-Mobile G5, we are unable to flash twrp through fastboot mode. So, for this process we rely vulnerability found in G5 firmware. The only currently found method for doing so is by using dirtycow exploit to flash TWRP on H830. Only V20a contains this vulnerability to do so.
Summary:
So to flash TWRP and enjoy freedom of using custom rom (Which I suppose you refer as Unlock to) you need to be on V20a. Which can be flashed easily through LGUP with Uppercut or use my LG FlashTool method (Link in FAQ section). When on V20a firmware simply use this or your preferred method for flashing TWRP.
If you want to go back to stock, simply flash any stock KDZ and lock bootloader. If you want to get TWRP again, simply unlock bootloader and flash V20a kdz (or flash V20a kdz and unlock bootloader) then instal TWRP by using the process.
Important:
Currently our stock firmwares are running Anti-Rollback (ARB 01), LG can increment this whenever they want, whenever LG increase ARB to 02 or upper then you won't be able to get back to ARB 01 firmwares (e.g V20a ) again. Which means you can unlock bootloader but won't be able to flash TWRP as dirtycow is patched after 20a. So you will lose the ability to flash TWRP which means unlocked bootloader is useless unless someone finds another method of flashing TWRP.
So, if you want to stay unlocked, then make sure to install TWRP as described above and flash latest TWRP flashable stock base zips or use other roms like Fulmics or AOSP based. It's very simple and easy .
First of All:
After Flashing let me know about your experience by answering the poll, this will help me in updating this post.
POLL is ended, so let me know about your experience with toolkit and thread readability in comments.
Disclaimer:
Before proceeding, remember I’m not responsible for anything bad happened to your device by following this or any of my guide. I’m just trying to help. So always do it on your own risk…
Don’t blame me or Any other developer.
All tools here are developed by different personalities. I’m just providing a guide on using these tool. Always say thanks to me and them. And If possible, donate them. They really deserve it.
Thanks be to:
@jcadduono For Recowvery tool
Source thread [V20 originated]
Due to some issue YouTube video aren't being played directly on XDA. So, you need to watch it here (Maybe some resistance on XDA side because things are good on my blog)
https://www.youtube.com/watch?v=F5PdTW8QHcA&t
Video Tutorial:
<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/F5PdTW8QHcA" width="480"></iframe>
https://youtu.be/G_4ayiZbSkM<br />
<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<iframe width="320" height="266" class="YOUTUBE-iframe-video" data-thumbnail-src="https://i.ytimg.com/vi/G_4ayiZbSkM/0.jpg" src="https://www.youtube.com/embed/G_4ayiZbSkM?feature=player_embedded" frameborder="0" allowfullscreen></iframe></div>
<br />
[YOUTUBE]<object width="445" height="364"><param name="movie"
value="http://www.youtube.com/v/AK9aZyJJNIo&hl=en_US&fs=1&rel=0&color1=0x234900&color2=0x4e9e00&border=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/AK9aZyJJNIo&hl=en_US&fs=1&rel=0&color1=0x234900&color2=0x4e9e00&border=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="445" height="364"></embed></object>[/YOUTUBE]
For which software version is this applicable?
arjunking said:
For which software version is this applicable?
Click to expand...
Click to collapse
Nougat v20a only as the thread title says.
I had to extract to a USB device to get recowvery to work but it went smoothly from there, until I got to TWRP to flash the no verity zip. It hung on hit any key to continue, it didn't dawn on me till later I should have mounted USB storage (derp), but I already had the no verity zip and SuperSU on my external SD so I just flashed them manually, booted, and had root. Then I formatted data, lost root, and flashed SuperSU again to get it back. I later flashed @autoprime 20c zip with SuperSU and now I'm rooted with TWRP on 20c, tyvm for the tutorial
Char_G said:
I had to extract to a USB device to get recowvery to work but it went smoothly from there, until I got to TWRP to flash the no verity zip. It hung on hit any key to continue, it didn't dawn on me till later I should have mounted USB storage (derp), but I already had the no verity zip and SuperSU on my external SD so I just flashed them manually, booted, and had root. Then I formatted data, lost root, and flashed SuperSU again to get it back. I later flashed @autoprime 20c zip with SuperSU and now I'm rooted with TWRP on 20c, tyvm for the tutorial
Click to expand...
Click to collapse
First of all you welcome, 2nd thanks for writing about your experience.
I am not completely assured but to make recowvery work in internal hard drive you need to change the name of recowvery folder to "1". Next time whenever you root try this method and let me know wether it worked...
And as you mentioned about having difficulty in flashing no verity. I think this issue is happening only on TWRP 3.1.0, on TWRP 3.0.1 it works fine, i think .
Does this method work with the latest update to 20f? Can I just try it without bricking my phone?
Sent from my LG-H830 using Tapatalk
dksoni411 said:
First of all you welcome, 2nd thanks for writing about your experience.
I am not completely assured but to make recowvery work in internal hard drive you need to change the name of recowvery folder to "1". Next time whenevee you root try this method and let me know wether it worked...
And as you mentioned about having difficulty in flashing no verity. I think this issue is happening only on TWRP 3.1.0, on TWRP 3.0.1 it works fine, i think .
Click to expand...
Click to collapse
Thanks, I'll try that next time. I did use TWRP 3.0.1 though, but I'm thinking that without mounting USB storage, perhaps the verity zip couldn't be found to be flashed.
This worked perfectly!! Thank you so much again! I had to extract the recowvery to a usb stick and run it from there (it wouldn't run properly from the computer hd) and at first I got an error as I had put the recovery.img on the external phone sd. My bad. Anyway... I just copied it over to the phone sd and started over, and it worked exactly as explained in the OP.
AWESOME effort by everyone involved. XDA rules!
Btw... can I relock the bootloader now? And one more thing... I turned off "automatic system updates" in developer mode. I assume if I update to v20c or newer I will lose root? And I guess I should not update the supersu either?
Thanks again! You rock!!
d3th.m0nk3y said:
This worked perfectly!! Thank you so much again! I had to extract the recowvery to a usb stick and run it from there (it wouldn't run properly from the computer hd) and at first I got an error as I had put the recovery.img on the external phone sd. My bad. Anyway... I just copied it over to the phone sd and started over, and it worked exactly as explained in the OP.
AWESOME effort by everyone involved. XDA rules!
Btw... can I relock the bootloader now? And one more thing... I turned off "automatic system updates" in developer mode. I assume if I update to v20c or newer I will lose root? And I guess I should not update the supersu either?
Thanks again! You rock!!
Click to expand...
Click to collapse
As you installed TWRP, so recovery partition is modified which means if you relock bootloader, you will brick your device.
Also if you want to use V20c check @autoprime's thread for the TWRP flashable zip of V20c or later (if there any).
And if you want to update supersu you can do it either by newest supersu zip to flash it through TWRP or by updating it through playstore then update binary through supersu it self, but I think updating supersu mostly changes nothing.
dksoni411 said:
As you installed TWRP, so recovery partition is modified which means if you relock bootloader, you will brick your device.
Also if you want to use V20c check @autoprime's thread for the TWRP flashable zip of V20c or later (if there any).
And if you want to update supersu you can do it either by newest supersu zip to flash it through TWRP or by updating it through playstore then update binary through supersu it self, but I think updating supersu mostly changes nothing.
Click to expand...
Click to collapse
Ok. Thanks for all the info. I think I will keep the v20a with the current supersu. It works perfectly! Hopefully it will not "automatically update between 23:00 and 04:00" as it says in "about phone/update center/system updates". From what I understand, it shouldn't as long as I have the "automatic system updates" set to OFF in developer options.
How can I boot into TWRP? When I reboot and try to enter TWRP I always end up in the hard reset menu where it asks if I want to wipe the phone... Do I have to boot into TWRP through ADB fastboot?
d3th.m0nk3y said:
Ok. Thanks for all the info. I think I will keep the v20a with the current supersu. It works perfectly! Hopefully it will not "automatically update between 23:00 and 04:00" as it says in "about phone/update center/system updates". From what I understand, it shouldn't as long as I have the "automatic system updates" set to OFF in developer options.
How can I boot into TWRP? When I reboot and try to enter TWRP I always end up in the hard reset menu where it asks if I want to wipe the phone... Do I have to boot into TWRP through ADB fastboot?
Click to expand...
Click to collapse
When you boot to recovery through hardware key combination, say yes through hardware keys twice (as you want to reset), it will take you to TWRP, thats the logic from lg g2
dksoni411 said:
When you boot to recovery through hardware key combination, say yes through hardware keys twice (as you want to reset), it will take you to TWRP, thats the logic from lg g2
Click to expand...
Click to collapse
He is absolutely correct. That's exactly what I did on my H830 yesterday.
Keep up the great work people......
Got it after a few attempts
Thanks for the step by step. It is a good walkthrough for a tough device. With all the previous complicated, and sometimes confusing/conflicting, instructions in other (older) threads for the H830 I was nervous to try.
I struggled a little getting it to work; 1) .cmd returned "don't have permission to create log or backup files..." when running from my "documents" directory, had to run it in a root folder. 2) I got the wrong TWRP version at first and the process said success, but never made it to TWRP.
It was the most challenging of any device I have owned to get root, but happy to crack it. Thanks!
root 20f?
does this root method work on 20f?
hp786 said:
does this root method work on 20f?
Click to expand...
Click to collapse
Well, it shouldn't. Because I tried this on 20c and it never worked, so I believe it will not work on any software other than 20a. But you can try your luck and tell me if you succeed.
Salam bro,I followed your method and rooted the phone,after rooting I wiped system, data and cache so I could flash fulmics 2(based on v20c) which I had already downloaded,it flashed successfully but after booting on startup screen there's this popup error"settings keep closing " because of which I can't do anything so can u please tell me where did I go wrong,should I have wiped the system or not?
WARNING
DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO.
If you do, I am not sure what shape your phone will be in.
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock). If you don't, you will probably brick your phone.
If you use this on any model V30 besides the H932, you will be stuck in a bootloop, and you will not be able to fix it since you will have wiped out download mode!
This is safe if no mistakes are made (typos, missing a step, etc). However, if you do mess up, the risk is high that you lose download mode at best, or brick your phone at worst.
If you deviate from this procedure, and think: "I can just skip a step, or I can do this on my own Linux install". Don't complain if you brick your phone.
PREREQUISITES:
You MUST to be on 10d: link
You must have H933 10h laf installed. You will need the KDZ: link
We are going to flash this using the patched LG UP: link MOD EDIT: original link dead. Try THIS ONE instead
It MUST be installed in: Crogram Files (x86)LG ElectronicsLGUP
You can't just unzip it anywhere and run it, it will not find the model file.
You need TWRP: link
You need an SD card that is formatted for FAT16 with TWRP copied onto it EXACTLY as it is named when you download it.
You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL.
After installing TWRP, grab @weakNPCdotCom's latest TWRP flashable ROM threads: Oreo 20s or Pie 30d
MOD EDIT: If your phone is (or has been) on Pie, you need to use a later LGUP version to roll back to Nougat 10d, then SWITCH to the original LGUP version linked below for the remaining steps. See this post for details.
PROCEDURE PART 1: Getting a working LAF onto your phone
By far this is the most dangerous part of this procedure.
Make sure you are on or downgraded to 10d
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions -- ignore it, and click OK.
As a safety feature, LG UP will start flashing those modified partitions after laf completes flashing.
After the flash is initiated, pay close attention to the "step" and as soon as it changes from laf to another partition, PULL THE USB CABLE!
If you let it completely flash the H933 KDZ, your phone WILL reboot, and you WILL have a brick that can't be fixed.
You NEED to pay attention. The additional partitions that are flashed are very small. The second that step changes from laf to
the next partition, PULL THE USB CABLE!
Click OK and it will start flashing.
Once laf is flashed, and you have pulled the USB cable, you can click exit, and then re-open LG UP.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
MOD EDIT: Refer to THIS POST to make sure that LGLAF is able to read the SD card
Code:
git pull
git checkout h932-dd-write
./step1.sh
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination (with phone off, hold vol down + power. When the LG logo appears, immediately release and then hold power until you get the the factory reset screen. Choose yes twice and you will be in TWRP) to IMMEDIATELY boot into recovery. If you don't, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
CREDITS:
Lekensteyn -- His base work on the G2 / G3 gave me a GREAT headstart!
@steadfasterX - He added some real nice features, great guy to bounce ideas off, and just testing crazy ideas because he wasn't afraid to brick his phone Also, for FWUL
tuxuser - Helping with my lacking in Python
@smitel - His original reverse engineering of LG UP. Great inspiration!
-- Brian
XDA:DevDB Information
[H932] lafsploit 1.5, Tool/Utility for the LG V30
Contributors
runningnak3d
Version Information
Status: Testing
Created 2018-09-14
Last Updated 2020-07-21
PROCEDURE PART 1: Getting a working LAF onto your phone
Make sure you are on version 10d. Again, check in Software Info / Software Version if you are unsure.
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions (cache, OP, userdata) -- ignore it, and click OK.
Click OK and it will start flashing.
Once the flash completes, your phone will reboot into the OS. Just power off, and go back into download mode.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP and rooting
Make sure the SD card is in your phone.
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
Code:
git pull
git checkout h932-dd-write
./lglaf.py
These next commands you will type into the LGLAF shell. It will look like this:
Code:
LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)
Type a shell command to execute or "exit" to leave.
#
You will type these commands at the # prompt that you see above. When you enter the commands, you will NOT get any indication that the command completed. However, if you get this:
Code:
Hello, I am LAF. Nice to meet you.
then you typed the command incorrectly, and you need to try again. There are TWO spaces between !EXEC and toybox.
Also, the phone will NOT indicate that flashing is taking place since we are using dd and NOT the normal WRTE opcode. When you enter !CTRL POFF, the phone will go to 100%.
Lastly CAPS matter. These lines need to be typed exactly (better to use copy / paste). If you mess up, it is no big deal, just try again.
Code:
!EXEC toybox dd if=/storage/external_SD/twrp.img of=/dev/block/sde bs=4096 seek=10246\0
!CTRL POFF
You can now pull the USB cable, and your phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination to immediately boot to TWRP:
Power off your phone
Hold vol down + power.
When the LG logo appears, immediately release power (and ONLY power) and then immediately hold power again until you get the the factory reset screen.
You never let go of vol down until the factory reset screen appears. Once it appears, you can release both buttons.
Choose yes twice by using the vol down key and power to select, and you will be in TWRP.
You should only tap the power key to select yes. Don't press and hold, and don't spam the power key.
It takes TWRP a little bit to boot -- be patient.
If you don't do this, and you let the phone boot into the OS, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
By THIS part, I mean if you mess up the key combo, and the phone boots to the OS, you only have to do PART 2 -- not this entire process.
ROOTING:
OK, so now you are in TWRP, we need to flash a few things or TWRP will be wiped out, and your phone will be encrypted again.
First swipe to allow modifications
Choose wipe / format data / type yes
Choose reboot / recovery -- this will reload TWRP. Do not choose reboot / system. Make sure that when it reboots you are able to mount data without it prompting for a pin / passcode.
If it does, then you need to format data again and reboot to recovery because you chose WIPE and not FORMAT.
Pick install, and browse to your SD card where you have Magisk, dm-noverity-opt-encrypt, and rctd remover
You can install each one individually, or you can add them all together in the queue -- it is your choice. Also, Magisk needs to be flashed first -- the order of the other two zips doesn't matter.
Now that they are flashed, reboot to recovery yet again just for good measure. If everything looks good, reboot to system and you should have a rooted phone.
OPTIONAL:
If you would like a second copy of TWRP on your laf partition (I *highly* recommend this), follow these instructions:
Download the version of TWRP that you want to install onto laf.
Rename it to twrp.img
Boot your phone to TWRP, and connect it to your PC
Open a command prompt where you downloaded TWRP and type:
adb push twrp.img /sdcard/
adb shell dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/laf
With the phone off, hold vol up and plug in the USB cable and you should be greeted by your second copy of TWRP.
CLEANING UP:
If you do NOT want TWRP on laf, then we at least need to get the H932 laf back onto your phone.
Download this zip onto your phone: h932_laf.zip
Boot to TWRP
Choose install, and browse to where you downloaded the zip
When it finishes flashing, you will have the H932 laf back.
I can't say this enough, you should really consider keeping two copies of TWRP around. You will never be in a situation where you go: "Man, I wish I had download mode, but all I have is TWRP".
However, there are plenty of times that you may wish that you had a second copy of TWRP. Imagine flashing a ROM that wipes out recovery. Oppps. Imagine flashing a new version of TWRP and
it doesn't boot -- again -- opps.
-- Brian
I've added link to WTF instructions pointing T-mobile H932 users to here. ALL other V30/30+/V30S can use that easier method, but T-mobile H932 HAS to use this method.
OK -- those are the final instructions for now. Root away!
I have upgraded to Oreo, and then downgraded to 10d and tested this 4 times so I know it works fine. However, getting H933 laf onto your phone is dangerous. PLEASE pay attention and pull the USB cable. You can be too quick -- pulling it while it is still flashing laf. If you do, then you just need to flash 10d and start again. However, if you wait and your phone reboots, the H933 has a different RSA key and your phone is toast.
I don't have a TMO G7 to test with, but this should work for them as well. Just need to find the correct laf to flash for them.
-- Brian
I remember when the OP released this method for the T-Mobile G6 (I used to have one). Many bricked their phones in the process. Others were successful and happy. Too risky for me.
I can't post a screenshot right now, but here ya go -- proof that this works:
Code:
joan:/ $ su
joan:/ #
joan:/ # cd sys
sys/ system/
joan:/ # cd system/
joan:/system # cat build.prop | grep H932
ro.product.model=LG-H932
ro.lge.swversion=H93210d
ro.lge.factoryversion=LGH932AT-00-V10d-TMO-US-JAN-11-2018-ARB00+0
joan:/system #
-- Brian
First thing: Nice job, Brian! Thank you, and those who helped bring this to light by being guinea pigs.
Second: Brian, there appears to be a break in the link for FWUL. I was still able to copy the link text, then take the break out after pasting it into the address bar to get to the page, but wanted to let you know that the break is there.
runningnak3d said:
OK --
I don't have a TMO G7 to test with, but this should work for them as well. Just need to find the correct laf to flash for them.
-- Brian
Click to expand...
Click to collapse
Man I hope that's true but the g7 has a locked bootloader HTC style unlock now. LG haven't unlocked the Tmo version last I checked unless I missed something
Also, so it's okay to OTA to Oreo now? I'm on nougat and much rather be on Oreo
NOOO Don't ever take an OTA. You will need to flash an Oreo zip to get back. I am guessing there isn't one since there would be no need.
I don't have time to make one today unfortunately.
EDIT: and what?! you mean TMO finally has a locked bootloader on the G7 just like all other carriers? They didn't just strip fastboot flash, they removed oem unlock as well?
-- Brian
inuyasha1999 said:
First thing: Nice job, Brian! Thank you, and those who helped bring this to light by being guinea pigs.
Second: Brian, there appears to be a break in the link for FWUL. I was still able to copy the link text, then take the break out after pasting it into the address bar to get to the page, but wanted to let you know that the break is there.
Click to expand...
Click to collapse
Fixed. Please let me know if you catch anything else.
-- Brian
runningnak3d said:
NOOO Don't ever take an OTA. You will need to flash an Oreo zip to get back. I am guessing there isn't one since there would be no need.
I don't have time to make one today unfortunately.
EDIT: and what?! you mean TMO finally has a locked bootloader on the G7 just like all other carriers? They didn't just strip fastboot flash, they removed oem unlock as well?
-- Brian
Click to expand...
Click to collapse
I should have added im sick in bed today and haven't rooted yet so itd be a 100pct stock OTA. Is it still not recommend to OTA to Oreo beforehand?
And yup, it appears LG has done the HTC style unlock and the Tmo version isn't unlockable yet and probably won't be Imo. I think it was LG but could be Tmo since it seems the more custs they get, the more like at&t they become
Josh McGrath said:
I should have added im sick in bed today and haven't rooted yet so itd be a 100pct stock OTA. Is it still not recommend to OTA to Oreo beforehand?
And yup, it appears LG has done the HTC style unlock and the Tmo version isn't unlockable yet and probably won't be Imo. I think it was LG but could be Tmo since it seems the more custs they get, the more like at&t they become
Click to expand...
Click to collapse
If you did, you will be wasting your time since you have to downgrade to 10d.
I will try to get a 20a flashable zip up as soon as I can.
-- Brian
runningnak3d said:
If you did, you will be wasting your time since you have to downgrade to 10d.
I will try to get a 20a flashable zip up as soon as I can.
-- Brian
Click to expand...
Click to collapse
Wow. Being so sick has made me not think straight . I can't believe I didn't think about that since you have to flash back to 10d.
No pressure on the flashable. It isn't that big of deal for me or us but thanks for thinking about us with the extra work.
Hey Brian. I dont know if you saw my pm but im glad it works
@me2151 No, sorry, my PM box is so backed up. I am going to have to spend some time this weekend going through it.
This isn't quite the same as lafsploit for the H918, but the concept came from research for that project.
Next tasks:
* Get Oreo and root working on the V20
* Get all other G6s root in addition to the H872
* Consider buying a V30 so I can help here as well
-- Brian
runningnak3d said:
@me2151 No, sorry, my PM box is so backed up. I am going to have to spend some time this weekend going through it.
This isn't quite the same as lafsploit for the H918, but the concept came from research for that project.
Next tasks:
* Get Oreo and root working on the V20
* Get all other G6s root in addition to the H872
* Consider buying a V30 so I can help here as well
-- Brian
Click to expand...
Click to collapse
Ah lol. My pm had jsut suggested taking a look into the h932 since its similar to the h918 in regards to bootloader. yea you should join us. I have my P rom working now. ill probably hold off on releasing it to the public though til i do more features. However. Only non stock rom to have enforcing on Joan
@runningnak3d
You stated, "You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL."
When I went to the page it has 2 options/2 types of FWUL... which should we download:
"Main Download Server:
persistent mode ( read FAQ #4 ): Latest version (click)
forgetful mode ( read FAQ #4 ): Latest version (click)"
I'm guessing Persistent mode version....?
Thanks
runningnak3d said:
WARNING
DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO.
If you do, I am not sure what shape your phone will be in.
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock). If you don't, you will probably brick your phone.
If you use this on any model V30 besides the H932, you will be stuck in a bootloop, and you will not be able to fix it since you will have wiped out download mode!
This is safe if no mistakes are made (typos, missing a step, etc). However, if you do mess up, the risk is high that you lose download mode at best, or brick your phone at worst.
If you deviate from this procedure, and think: "I can just skip a step, or I can do this on my own Linux install". Don't complain if you brick your phone.
PREREQUISITES:
You MUST to be on 10d: link
You must have H933 10h laf installed. You will need the KDZ: link
We are going to flash this using the patched LG UP: link
It MUST be installed in: Crogram Files (x86)LG ElectronicsLGUP
You can't just unzip it anywhere and run it, it will not find the model file.
You need TWRP: link
You need Magisk: link
You need an SD card that is formatted for FAT16 with TWRP copied onto it and named twrp.img. Also copy the Magisk zip onto the card.
You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL.
PROCEDURE PART 1: Getting a working LAF onto your phone
By far this is the most dangerous part of this procedure.
Make sure you are on or downgraded to 10d
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions -- ignore it, and click OK.
As a safety feature, LG UP will start flashing those modified partitions after laf completes flashing.
After the flash is initiated, pay close attention to the "step" and as soon as it changes from laf to another partition, PULL THE USB CABLE!
If you let it completely flash the H933 KDZ, your phone WILL reboot, and you WILL have a brick that can't be fixed.
You NEED to pay attention. The additional partitions that are flashed are very small. The second that step changes from laf to
the next partition, PULL THE USB CABLE!
Click OK and it will start flashing.
Once laf is flashed, and you have pulled the USB cable, you can click exit, and then re-open LG UP.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
Code:
git pull
git checkout h932-dd-write
./lgaf.py
!EXEC toybox dd if=/storage/external_SD/twrp.img of=/dev/block/sde bs=4096 seek=10246\0
!CTRL POFF
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination (with phone off, hold vol down + power. When the LG logo appears, immediately release and then hold power until you get the the factory reset screen. Choose yes twice and you will be in TWRP) to IMMEDIATELY boot into recovery. If you don't, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
You will have to format data, and make sure you flash Magisk before rebooting into the OS!
CREDITS:
Lekensteyn -- His base work on the G2 / G3 gave me a GREAT headstart!
@steadfasterX - He added some real nice features, great guy to bounce ideas off, and just testing crazy ideas because he wasn't afraid to brick his phone Also, for FWUL
tuxuser - Helping with my lacking in Python
@smitel - His original reverse engineering of LG UP. Great inspiration!
-- Brian
XDA:DevDB Information
[H932] lafsploit 1.5, Tool/Utility for the LG V30
Contributors
runningnak3d
Version Information
Status: Testing
Created 2018-09-14
Last Updated 2018-09-14
Click to expand...
Click to collapse
Feedback
I had a moment to go through the instructions as a "typical user", and am providing feedback to make this as painless as possible, crystal-clear, & hopefully prevent any bricks!: (Please correct any inaccuracies!!)
runningnak3d said:
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock)...
Click to expand...
Click to collapse
EVERYTHING should be said!!! Especially things that will brick our phones People like me that ARE extremely computer literate and have been 'custom rom-ing' for almost a decade still won't know all of these nuances. I've been just catching up on all of these advancements with the V30 and your latest discovery, read hundreds of posts, but I still won't pretend to know everything! And apparently a mistake like this could've made my phone gar-bosh. So don't underestimate peeps like me So: in Android phone settings->Developer Options: There are 2 checkbox(es) we need to select? "OEM Unlock" and "Fastboot OEM unlock"? (Im not sure about the latter mostly)
runningnak3d said:
...You MUST to be on 10d...
Click to expand...
Click to collapse
Link or steps if you're NOT? Ways to check? (I like many users will either get a random phone off ebay, or have one already, and won't know our baseline or how to determine this. & is this a deal breaker if it's not 10d?)
runningnak3d said:
...You must have H933 10h laf installed...
Click to expand...
Click to collapse
Link or steps if you're NOT? Does that link also contain the software or is there another link we need? (Again, if there's another link, version-mismatch might cause unpredictable results for some users)
Fat32: I've used SwissKnife https://swissknife.en.uptodown.com/windows to do easy FAT (same as FAT16) formatting. I say this because I already saw issues around this.
I'm looking to buy a V30 only since you figured this out Much thanks! I'll say that again, you're awesome & I'm jealous! It sounds like now ALL variants can get the bootloader unlocked and a custom recovery installed: H932 via this thread/method & all other variants via WTF exploit (Again, please keep me honest!). (I just want to double-check my info so I (& others) buy a phone that will be able to get a custom ROM & plan to get the H932 and will report back if/when I get band 71 working for those interested.
I know some of you that have been in this since the beginning are thinking, come on man, read the posts! Like I said, I have been for over a week. There are thousands of posts, and even if I/we read EVERYTHING, we still wouldn't be able to decipher the bad info from the good! ...so thanks for your patience I'll post more once I actually try this. And thanks again Brian!! Really awesome...
---------- Post added at 03:07 PM ---------- Previous post was at 03:01 PM ----------
runningnak3d said:
* Consider buying a V30 so I can help here as well
Click to expand...
Click to collapse
Umm... For all of us that use this and get it working, I think we should do donations until Brian can get a free V30, eh?!? (Can't yall read between the lines ) Besides, think of all the additional support you'll get if he actually has a phone to test with!! haha
@igotroot
Did you get it working yet? If not I can run you through the hardest part of it. Also, choose the persistent FWUL. Basically persistent mode means it saves your data when you leave. It's just easier that way
I bought a LG V35 recently. When I got the phone, I found its rooted already and looks like bootloader is unlocked since the 1st screen shows the warning unlocked messages. See attachments.
After I got into the system, I could see magisk and used root permission without any problem.
I wanted to do a system backup in the customer recovery like twrp or CWM. (I thought it should be there, since phone is rooted) But after I clicked "reboot to recovery" with TaiBackup APP, I could not get into recovery and screen shows "erasing data" and then rebooted. When system was started up again, phone was done a factory reset and magisk did not work any more...(I checked, I still can see the unlocked bootloader messages at that time)
Then I had to send my phone to the seller and got rooted again. I really do not understand how the seller rooted this phone!!
Now I am wondering if I can flash any custom recovery like twrp? I do not see LG V35 in official twrp's support device list. Dare I try the twrp for LG G7 or LG V30 or others?
If I have to try twrp for LG G7, is there anybody knows how to do a recovery backup via ADB beforehand? Anything I can do to minimize the risk?
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
crumbling9999 said:
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
Click to expand...
Click to collapse
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
vlad48 said:
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
Click to expand...
Click to collapse
Please tell me how to backup both boot images? Thx
alex.coffen said:
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Click to expand...
Click to collapse
Is there somebody can tell me how to solve the issue that i can not install any module in magisk?
Can i update the magisk framework to 18.1 when the root method is coming from the patching boot image?
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
runningnak3d said:
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
Click to expand...
Click to collapse
Thanks for your answers.
I bought this phone from taobao which is a bigest famous online shopping site in China. I do not know how they unlocked the bootloader and tell me if something I can help with.
I unlocked LG G2/G4/oneplus 5T myself so I know the basic knowledges about how to execute ADB command and the normal root process. But I do not know the one using patched magisk boot img way.
As far as I understand, you meant that we can temporarily boot into the G7 twrp to use its functions but we cannot actually flash the twrp to the phone. Booting to G7 twrp image, is it safe? (The "safe" I mean is that, if I encounter problems, at least I still can startup the phone with rooted. Otherwise, I need to send my phone to the seller who is 2000KM away to root it again...Last time I booted into its recovery, all my data was erased...) Anyway, I will try it as you suggested, but I will put it the 2nd priority.
The 1st priority is that, I truely want to solve the problem I met about installing magisk module failed. See my attachment. I want to know if I can fix the problem by updating the magisk framework. I need the "safe" way as I just said.
So if I click "yes" in the 33.jpg I attached, do you know which would happen?
A. brick the phone
B. restart and get a factory reset, then I cannot use root any more
C. nothing changed, still install module failed but root can work
D. Solve the problem and can install module successfully
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Thanks for explaining. That is what I worry about. Some questions for you:
1. I have used LGUP to dump boot_a and boot_b. (Very slow, took 1 hour. I renamed them to boot_a_org.img and boot_b_org.img, they are no difference with cksum). So this is currently boot images patched by seller? So, no matter what problems I encounter, I can flash boot_a_org.img(boot_b_org.img) back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
2. You mentioned "Patch it via Magisk Manager". I can directly patch boot_a_org.img to do it? I think boot_a_org.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
3. "Patch it via Magisk Manager". can only be done in my V35 phone, or it is OK to do it in other phones?
4. Can I try to boot into G7 twrp then I can flash the newest magisk via twrp? In this way I can fix my problem?
Thank you very much in advance.
1. Download LGUP from HERE
(make sure you put it in the right place afterwards: C:\Program Files (x86)\LG Electronics\LGUP)
2. Shut down your phone and then press VOL+ button and connect it via USB cable to your computer (The phone will boot in download mode).
3. Start LGUP.exe and select DUMP mode. DUMP only those partitions (place checkbox):
abl_a
abl_b
boot_a
boot_b
xbl_a
xbl_b
This will finish our backup preparation, so report back once done.
(Also just come to a better idea - compress and upload somewhere your boot_a file I'll try to patch it with latest Magisk and upload it back to you)
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Laf has new security that prevents reading for now. LG UP 1.14 and 1.15 can't read .. and I can't find a copy of 1.16.
-- Brian
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
vlad48 said:
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
Click to expand...
Click to collapse
This only works for v35 phones with unlocked bootloader?
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
alex.coffen said:
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
Click to expand...
Click to collapse
The files I dumped from LGUP are bin file or img file?
I try to patch the boot.img file but everytime I get error. See attachment.
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
vlad48 said:
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
Click to expand...
Click to collapse
Yes, all 0-es. What should I do? I have already re-installed the USB dirver 4.2.0. See attachment.
Since I failed to use LGUP dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d， @vlad48
Since I failed to use LGUP to dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d， @vlad48
* Do NOT update to Pie yet if you wish to unlock bootloader in order to root.
For bootloader unlock purposes, you will need to temporarily convert to North American variant with fastboot flash commands (known as Frankenstein) and temporarily downgrade to early Oreo KDZ versions with no later than July 2018 security patch. After bootloader unlock and TWRP installation, then you can use H933 TWRP flashable zip (ROM) to update to most recent Verizon firmware while having root. Read the Root Sticky here if you wish to know more.
* If you've already updated to Pie with locked bootloader, see post #3 for instructions on how to downgrade to earlier Oreo firmware to first unlock bootloader. Or downgrade back to most recent Oreo because you decided you don't like Pie.
* If you have no desire to unlock bootloader or your bootloader is already unlocked, see full image KDZ and KDZ-based TWRP-flashable zips below.
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
Whereas you do need to update to stock Pie first as a foundation before trying to install "Android 10" LOS-17 custom ROMs. However, those ROMs are still unfinished work in progress -- so if you don't like them and want to go back to the older stable LOS-16 "Pie" custom ROMs, then you've totally ignored the warning above. Again, stock Pie makes permanent changes.
NOTE: After installing Pie, if you get weird lag,
* try this fix. Just make a backup in LG Bridge. Nothing else. Somehow CREATING the backup (but not actually using it to restore anything) re-sets some stuff in Pie, so it acts like it should? I know it sounds strange but it works. Thanks to @thefpspower for the tip!
* OR If that doesn't work or you don't have access to PC, try this: go to Settings> Restart & Reset> Reset App Preferences. Thanks to @HoussiLAM for that tip. Both may do the exact same thing, I've not experimented to see.
[VS996][STOCK][PIE]VS99630d_02_0821_ARB00.KDZ
3.5GB
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
md5: 33f28828c855418e34e7bf4eb0ca2ae3
TWRP FLASHABLE VERSION (ROM):
NONE YET
VS996 30D seems to be basically 30C with old August 2019 security update, even though Verizon claimed 2020 security update. Dev proved otherwise. There's absolutely no changes over 30C firmware and the TWRP flashable zip made from it is problematic. Forget about it and use 30C below.
__________________________________________
PREVIOUS FIRMWARE (2019)
[VS996][STOCK][PIE]LG V30 VS99630c_00_0904_ARB00.KDZ
3.5GB
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
DOWNLOAD LINKS:
* LG Bridge MIRROR
(Thanks to @drewcu!)
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
* Mega MIRROR
(Thanks to @HueyT!)
* Google Drive MIRROR
(Thanks to @HueyT!)
md5: c49d3a56acc3aa7f51f8a6ca72fc666a
TWRP FLASHABLE VERSION (ROM):
(Thanks to @JohnFawkes!)
* MAIN DOWNLOAD THREAD (see post #1)
* Android File Hosts MIRROR
3.1 GB
md5: 04b46053e4fe028f6fe239ac6460c85d
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
Flash the "ROM" with latest TWRP. Flash Magisk + @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler) immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
This TWRP flashable zip has the new Pie encryption disabled. No encryption enforced, but you can encrypt in TWRP if you want afterwards.
The dev recommends formatting data before installing this TWRP-flashable zip: "format data before flashing, not wipe but format". That's your decision. Others have not.
* Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
TWRP-FLASHABLE NOTES:
If those instructions above do not work for you for some reason, then go through these full blown steps (adapted from Section 6 of WTF Instructions):
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 TWRP-flashable zip
d. Install the latest stable Magisk zip.
e. Install @JohnFawkes 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 back 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.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, please make another TWRP backup.
___________
Screenshots thanks to @belfastraven:
__________
Here's how to flash with LGUP:
----------------------------
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash PIE KDZ either via UPGRADE (to keep your data, but see Note about TWRP) or via REFURBISH or PARTITION DL. If the latter, then in the pop up box "Select All". Use the attached patched LGUP in this post.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader). If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP. Or use the TWRP-flashable zip (ROM) instead of LGUP, which will keep your data and will keep TWRP.
3) IF your bootloader is unlocked, it will remain unlocked. If it's not unlocked, then you will just be updating to Pie -- but will have to temporarily downgrade to early Oreo if you ever want to unlock bootloader for root.
_
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
As mentioned before, use UPGRADE, REFURBISH or PARTITION DL modes. REFURBISH and Partition DL are probably best.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
HOW TO DOWNGRADE BACK TO OREO BECAUSE YOU DON'T LIKE PIE
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install. (Most recent Oreo KDZ 20k is at the top in that thread)
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut.
Choose Process : PARTITION DL or REFURBISH
----------------------------
3) DOWNGRADING ANY LG V30/V30+/V30S TO EARLIER OREO KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (post 101 of Frankenstein thread)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER (with early Oreo), GO READ WTF INSTRUCTIONS
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Sticky everyone should read.
____________
EXTRAS
If you root with stock Pie KDZ (after unlocking bootloader in early Oreo), then you will need to flash Magisk modules or manually edit build prop to get root-enabled DTS, Equalizer, and lockscreen weather animations. Dual Speaker mode gives you audio directed at your face, besides the main downward facing speaker. High Impedance Mode give you more volume.
(NOTE: The TWRP flashable zips already have this, thanks to the devs who make them.)
* Fully enable LG DTS 3D stereo (root needed) + Equalizer
* LG V30 Lockscreen EXTRA Weather Animations Enabler
* DUAL SPEAKER MODE + HIM (High Impedance Mode)
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://photos.app.goo.gl/NCm643Y7prJhDLaS2
Verizon VS996 stock Pie OTA 30c hit today. See screenshots in post #2 of this KDZ thread, courtesy @belfastraven.
Full image KDZ should hit in a couple of days. We'll post it here, and fill in the blank links above.
Soon after @JohnFawkes will probably make a TWRP-flashable zip, generously donating his time and talents. Please do NOT ask for ETA! But it's finally here.
Until then, locking the thread back until we have the KDZ ready to post! Stand by...
We have LG Bridge KDZ server link for VS996! Thread now unlocked!
drewcu said:
Been checking daily for an updated KDZ since 20K and finally this morning it happened! They skipped over 20L in terms of publishing the KDZ so now we are on 30C (Pie):
http://pkg02.lime.gdms.lge.com/dn/d...BO7C2M5ABB5B4C20IX/VS99630c_00_0902_ARB00.kdz
Click to expand...
Click to collapse
More mirrors to follow.
TWRP flashable zip done by @JohnFawkes. See link in post #2.
ChazzMatt said:
TWRP flashable zip done by @JohnFawkes. See link in post #2.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1BtUnRhR1aWfjvoYqYG0em6jSh3yR3Zf8/view?usp=sharing
SHA1: F1134A642DEC96A10D6CBED9A92322CEF29671DC
ChazzMatt said:
TWRP flashable zip done by @JohnFawkes. See link in post #2.
Click to expand...
Click to collapse
https://mega.nz/#!RVw0HYRT!ltedQlTE_hQCRu0HtSYeSEZUXZL4UZKar0tzKbEu49o
SHA1: F1134A642DEC96A10D6CBED9A92322CEF29671DC
So this fixes stuck on boot?
....
Flashed kdz, still won’t boot.
Sent from my iPad using Tapatalk Pro
MicroMod777 said:
So this fixes stuck on boot?
....
Flashed kdz, still won’t boot.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
You may have to downgrade to H933 10H canadian NOUGAT, boot it up, then KDZ to this. I believe NOUGAT Canadian sets up the partitions correctly for PIE to work. Try it and let us know. It's the same fix for AOSP looping after stock PIE. As long as you use PARITION DL, select ALL the partitions and not mix and match (like last time that cost you QLD 9008 brick), you'll be OK.
HueyT said:
You may have to downgrade to H933 10H canadian NOUGAT, boot it up, then KDZ to this. I believe NOUGAT Canadian sets up the partitions correctly for PIE to work. Try it and let us know. It's the same fix for AOSP looping after stock PIE. As long as you use PARITION DL, select ALL the partitions and not mix and match (like last time that cost you QLD 9008 brick), you'll be OK.
Click to expand...
Click to collapse
Well, guess that didn't work either.
I'm thinking of what we could possibly try is for somebody to be on pure stock VS996, never did bootloader unlock, and then do a dump of all the partitions. Then make a rom to flash every single partition in twrp. A dump has more partitions listed than on a flash Partition DL.
Anybody able to dump for us a pure virgin VS996?
@ChazzMatt I have successfully flashed my VS996 frankenstein'ed to US998 from Oreo to VS996 Pie using this KDZ and LG UP PARITITION DL. However, contrary to links provided here, I don't think I will be able to flash TWRP using fastboot? How one could root his VS996 Pie?
HueyT said:
You may have to downgrade to H933 10H canadian NOUGAT, boot it up, then KDZ to this. I believe NOUGAT Canadian sets up the partitions correctly for PIE to work. Try it and let us know. It's the same fix for AOSP looping after stock PIE. As long as you use PARITION DL, select ALL the partitions and not mix and match (like last time that cost you QLD 9008 brick), you'll be OK.
Click to expand...
Click to collapse
What's odd is the Canadian Pie flashed sucessfully.
Sent from my LG-H931 using Tapatalk
micx_pl said:
@ChazzMatt I have successfully flashed my VS996 frankenstein'ed to US998 from Oreo to VS996 Pie using this KDZ and LG UP PARITITION DL. However, contrary to links provided here, I don't think I will be able to flash TWRP using fastboot? How one could root his VS996 Pie?
Click to expand...
Click to collapse
You could use the TWRP flashable zip, but only if you have TWRP already installed on US998 firmware.
Better procedure below.
vs996 still won’t boot, too.
We have a working method for people with TWRP who are having trouble getting across the line for Pie. Most people have no problems updating. I didn't. However, for those who are having issues, there's a workaround, but you need TWRP installed.
Helpful people been testing this out...
WORKAROUND FOR THOSE PEOPLE GETTING STUCK ON LG LOGO WHEN UPDATING TO PIE
https://forum.xda-developers.com/showpost.php?p=80347089&postcount=6
Also will NOT boot for me. Stuck on the white Verizon screen. I did the official 30c OTA within system settings and that would not boot at all either. This Pie "update" is rigged. I also flashed the US998 30b KDZ and that would not boot either.
* Do NOT update to Pie yet if you wish to unlock bootloader in order to root.
For bootloader unlock purposes, use the H930DS Oreo KDZ versions with no later than July 2018 security patch: 20b.
Look at the names for dates in the title in that thread link. AFTER you unlock bootloader, then you can update to newer firmware (like this Pie). Flashing a newer KDZ (like to Pie) will not re-lock your bootloader.
With unlocked bootloader, then on Pie KDZ you can install TWRP and root.
Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
To install TWRP (or re-install TWRP on Bootloader Unlocked Pie) and root, PLEASE follow these instructions for success!
* If you've already updated to Pie with locked bootloader, see post #3 for instructions on how to downgrade to earlier Oreo firmware to first unlock bootloader. Or downgrade back to most recent Oreo because you decided you don't like Pie.
* If you have no desire to unlock bootloader or your bootloader is already unlocked, see full image KDZ and KDZ-based TWRP-flashable zips below.
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
Whereas you do need to update to stock Pie first as a foundation before trying to install "Android 10" LOS-17 custom ROMs. However, those ROMs are still unfinished work in progress -- so if you don't like them and want to go back to the older stable LOS-16 "Pie" custom ROMs, then you've totally ignored the warning above. Again, stock Pie makes permanent changes.
NOTE: After installing Pie, if you get weird lag,
* try this fix. Just make a backup in LG Bridge. Nothing else. Somehow CREATING the backup (but not actually using it to restore anything) re-sets some stuff in Pie, so it acts like it should? I know it sounds strange but it works. Thanks to @thefpspower for the tip!
* OR If that doesn't work or you don't have access to PC, try this: go to Settings> Restart & Reset> Reset App Preferences. Thanks to @HoussiLAM for that tip. Both may do the exact same thing, I've not experimented to see.
If you want LG FM Radio app, then download from here and install.
[H930DS][STOCK][PIE]LG V30+ INDIA H930DS30b_00_OPEN_ESA_DS_OP_0903.KDZ
3.1GB
ONLY for H930DS, H930, H930G, H930D! Do NOT ask if others can flash this!
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
* LG Bridge MIRROR
* Mega MIRROR
(Thanks to @tech_infinity!)
* Google Drive MIRROR
(Thanks to @ankurpandeyvns!)
md5: 43456a7c461237a278334503692f61ba
TWRP FLASHABLE VERSION (ROM):
(thanks to @seadersn!)
ONLY for H930DS, H930, H930G, H930D! Do NOT ask if others can flash this!
* Android File Hosts MIRROR
* Google Drive MIRROR
(Thanks to @seadersn!)
* Mega MIRROR
(Thanks to @tech_infinity!)
md5: 86b93b695c9b7c521368d38f70e73e18
Flash the "ROM" with latest TWRP. Flash Magisk + @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler) immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
This TWRP flashable zip has the new Pie encryption disabled. No encryption enforced, but you can encrypt in TWRP if you want afterwards.
The dev recommends formatting data before installing this TWRP-flashable zip: "format data before flashing, not wipe but format". That's your decision. Others have not.
* Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
TWRP-FLASHABLE NOTES:
If those instructions above do not work for you for some reason, then go through these full blown steps (adapted from Section 6 of WTF Instructions):
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 TWRP-flashable zip
d. Install the latest stable Magisk zip.
e. Install @JohnFawkes 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 back 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.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, please make another TWRP backup.
___________
Here's how to flash with LGUP:
----------------------------
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash PIE KDZ either via UPGRADE (to keep your data, but see Note about TWRP) or via REFURBISH or PARTITION DL. If the latter, then in the pop up box "Select All". Use the attached patched LGUP in this post.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader). If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP. Or use the TWRP-flashable zip (ROM) instead of LGUP, which will keep your data and will keep TWRP.
3) IF your bootloader is unlocked, it will remain unlocked. If it's not unlocked, then you will just be updating to Pie -- but will have to temporarily downgrade to early Oreo if you ever want to unlock bootloader for root.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
As mentioned before, use UPGRADE, REFURBISH or PARTITION DL modes. REFURBISH and Partition DL are probably best.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
HOW TO (temporarily) DOWNGRADE BACK TO OREO FOR BOOTLOADER UNLOCK
(or DOWNGRADE BECAUSE YOU DON'T LIKE PIE)
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install -- for bootloader unlock would be H930DS 20b.
(If you just don't like Pie, then choose the most recent KDZ in that thread, which is at the top.)
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut.
Choose Process : PARTITION DL or REFURBISH
----------------------------
3) DOWNGRADING ANY LG V30/V30+/V30S TO EARLIER OREO KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (post 101 of Frankenstein thread)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER (with early Oreo), GO READ WTF INSTRUCTIONS
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Sticky everyone should read.
____________
EXTRAS
If you root with stock Pie KDZ (after unlocking bootloader in early Oreo), then you will need to flash Magisk modules or manually edit build prop to get root-enabled DTS, Equalizer, and lockscreen weather animations. Dual Speaker mode gives you audio directed at your face, besides the main downward facing speaker. High Impedance Mode give you more volume.
(NOTE: The TWRP flashable zips already have this, thanks to the devs who make them.)
* Fully enable LG DTS 3D stereo (root needed) + Equalizer
* LG V30 Lockscreen EXTRA Weather Animations Enabler
* DUAL SPEAKER MODE + HIM (High Impedance Mode)
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://photos.app.goo.gl/NCm643Y7prJhDLaS2
In post #2, the for 30b the LG Bridge server link is active. The other mirrors will be up within 24 hours.
FYI: @seadersn
EDIT:
AFH mirror is now up.
Google Drive mirror is now up.
LG-Firmwares mirror is now up. They are using "30b", like I have.
@ChazzMatt Here's a mega mirror of the kdz file.
https://mega.nz/#F!XBd0wAoT!MQpZReO7TxG6RYUdgQ3zEg
PS: Thanks for making such a detailed thread as always :fingers-crossed:
@ChazzMatt when can I get the TWRP flashable version??
Thanks for the great work.
vamsi37 said:
@ChazzMatt when can I get the TWRP flashable version??
Thanks for the great work.
Click to expand...
Click to collapse
Not available yet
I am in twrp version of eu pie can I update by lgup to this version
vamsi37 said:
@ChazzMatt when can I get the TWRP flashable version??
Thanks for the great work.
Click to expand...
Click to collapse
We have great devs who make our TWRP-flashable zips, but they do it in their spare time. @seadersn will probably create this one, as he also created the one for the EU H930. @JohnFawkes may assist.
pdpmoto said:
I am in twrp version of eu pie
can I update by lgup to this version
Click to expand...
Click to collapse
Yes, as long as you read this in post #2:
"If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP."
You would flash full KDZ in Partition DL (all partitions) or Refurbish mode. Your bootloader will still be unlocked. Once on Pie then you would use fastboot commands to re-install TWRP and the three root files (encyrption disabler, no root check, Magisk).
I have this Instructions post (linked in post #1 of this thread) just for this scenario. Here it is again:
REINSTALL TWRP AND ROOT ON PIE KDZ
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3287
ChazzMatt said:
We have great devs who make our TWRP-flashable zips, but they do it in their spare time. @seadersn will probably create this one, as he also created the one for the EU H930. @JohnFawkes may assist.
Yes, as long as you read this in post #2:
"If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP."
You would flash full KDZ in Partition DL (all partitions) or Refurbish mode. Your bootloader will still be unlocked. Once on Pie then you would use fastboot commands to re-install TWRP and the three root files (encyrption disabler, no root check, Magisk).
I have this Instructions post (linked in post #1 of this thread) just for this scenario. Here it is again:
REINSTALL TWRP AND ROOT ON PIE KDZ
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3287
Click to expand...
Click to collapse
Thanks, but using lgup to flash kdz and again using fastboot commands to flash TWRP will erase my internal storage. So I'll be waiting for flashable zip.
?
vamsi37 said:
Thanks, but using lgup to flash kdz and again using fastboot commands to flash TWRP will erase my internal storage. So I'll be waiting for flashable zip.
?
Click to expand...
Click to collapse
Sure. I was replying to two different questions, that involved TWRP.
Drive Mirror: https://drive.google.com/open?id=1BSfUWjut39FUn_3ZDoNJhDBRzQ9rKarm
Hi ChazzMatt,
Yesterday night I installed the pie kdz and the process went butter smooth. Thank you very much.
Trouble started afterwards. Initially it was very slow, so slow that sometimes I thought it has hanged which got little better with time.
After sometime, I tried to install root. First installed twrp, booted to twrp. But, twrp can not mount data. It says system decrypt.
I did a factory reset, did not set any password, again tried twrp (using adb/fastboot). But it still can not mount and decryption fails
with whatever password.
Any idea what I might be doing wrong? Just to inform, when first time I installed the pie kdz, I didnt do the factory reset
girishv said:
Hi ChazzMatt,
Yesterday night I installed the pie kdz and the process went butter smooth. Thank you very much.
Trouble started afterwards. Initially it was very slow, so slow that sometimes I thought it has hanged which got little better with time.
After sometime, I tried to install root. First installed twrp, booted to twrp. But, twrp can not mount data. It says system decrypt.
I did a factory reset, did not set any password, again tried twrp (using adb/fastboot). But it still can not mount and decryption fails
with whatever password.
Any idea what I might be doing wrong? Just to inform, when first time I installed the pie kdz, I didnt do the factory reset
Click to expand...
Click to collapse
Read first paragraph of this thread again and you might know what you did wrong. I assume here that you didn't unlock bootloader before installing Pie.
girishv said:
Hi ChazzMatt,
Yesterday night I installed the pie kdz and the process went butter smooth. Thank you very much.
Trouble started afterwards. Initially it was very slow, so slow that sometimes I thought it has hanged which got little better with time.
After sometime, I tried to install root. First installed twrp, booted to twrp. But, twrp can not mount data. It says system decrypt.
I did a factory reset, did not set any password, again tried twrp (using adb/fastboot). But it still can not mount and decryption fails
with whatever password.
Any idea what I might be doing wrong? Just to inform, when first time I installed the pie kdz, I didnt do the factory reset
Click to expand...
Click to collapse
Sounds like you didn't flash the decryption disabler file or at least the NEWER (Pie) decryption disabler. Which means you also may not have flashed the newer root check disabler file?
There's a link for Pie TWRP/root Instructions near top of post #1 of this thread. The steps and files have changed for Pie KDZ.
I also posted it again top of this current page... And here it is again.
All necessary files are attached to that post.
INSTALL/REINSTALL TWRP AND ROOT ON PIE KDZ
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3287
Hey , I'm on pie v29g-global with June security patch, can I update it with this Indian pie?
oofyrey said:
Hey , I'm on pie v29g-global with June security patch, can I update it with this Indian pie?
Click to expand...
Click to collapse
Do you have an H930 variant? What model do you have?
This KDZ is only for LG H930 variants, preferably H930DS or H930D. But technically is compatible with all H930 variants (like H930, H930G) -- as long as you understand non-dual SIM H930 variants will see "ghost" second SIM card icon in status bar.
Also it's meant for India/ESA region, so there may be some regional differences you don't need -- like LG India app, if you don't live in India.
29G? Was that some failed Pie beta? There's no H930 variant KDZ with that kind of numbering...
For all V30 variants, actual official LG Pie KDZ releases (not buggy betas) start with "30" for every variant -- except Sprint which apparently can't count correctly.
Thanks for the reply.
But, how can I flash them when it do not mount any system. I can not even drag them from PC
Can you please give me a detailed new steps for pie kdz.
On another note, I am getting lot of "system UI stopped working" errors and some times its so slow, I thought of throwing it at a wall.
ChazzMatt said:
Sounds like you didn't flash the decryption disabler file or at least the NEWER (Pie) decryption disabler. Which means you also may not have flashed the newer root check disabler file?
There's a link for Pie TWRP/root Instructions near top of post #1 of this thread. The steps and files have changed for Pie KDZ.
I also posted it again top of this current page... And here it is again.
All necessary files are attached to that post.
INSTALL/REINSTALL TWRP AND ROOT ON PIE KDZ
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3287
Click to expand...
Click to collapse