Related
You may find that you need to return to stock/locked bootloader for various reasons. You can find how to do this by digging throughout various threads on this forum. decided to simplify things and bring it together in a single thread. After restoring you will be able to do OTA updates as well.
FLASHING FACTORY 5.8.019S
STEP 1: Download the backup
-- Source Thread: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
-- FILE: https://drive.google.com/file/d/0B5xyvHc4wgEVWHFKMWZqLWEyTTg/view?usp=sharing
Note: There is a TWRP backup for 20s currently on this forum. I do not recommend using it. Many have had issues booting after restoring it (me included).
STEP 2: Setup TWRP Backup Directory
If you download it to your PC use adb to push it to your device. You should have an existing directory within /sdcard/TWRP/BACKUPS/ that holds your backups. I believe the directory is your device id.
If the directory does not exist, you need to get the info from your device.
Code:
Run adb devices
It will be the hash listed by your device. Make a directory in TWRP/BACKUPS/ with the device id. Mine is "6293eaef".
For example, any backups that I want to restore to my device from TWRP need to be located in a sub-directory within: /sdcard/TWRP/BACKUPS/6293eaef/
At that point you should have the directory you need to copy the backup into.
STEP 2: Copy the Backup (originally named TWRP.zip) to /sdcard/TWRP/BACKUPS/6293eaef/stock
Do the following if you downloaded it to your computer:
Code:
adb push TWRP.zip /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
adb shell
cd /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
unzip TWRP.zip
If you downloaded to your device, you just need to move the zip file to the TWRP backups directory and extract it.
STEP 3: Restore in TWRP
Boot into TWRP recovery (if not already there).
Code:
adb reboot recovery
OR
Code:
hold volume up and press power button
RESTORE the backup.
I selected everything. This will install default recovery and remove TWRP.
Do a FULL wipe AFTER flashing. Be sure to wipe the data partition to clear any encryption.
[OPTIONAL] RESTORE LOCKED BOOTLOADER X727
This should not be necessary for X720 devices because the bootloader comes unlocked. I would only suggest re-locking if you need to return your device for warranty support.
To lock the bootloader you need to flash emmc_appsboot.mbn and xbl.elf from an OTA
Step 1: Get 5.8.020s OTA
-- File: https://www.androidfilehost.com/?fid=457095661767124419
After downloading extract 5.8.020S_sta.zip.
Inside the firmware-update folder are 2 files: xbl.elf, and emmc_appsboot.mbn. You need to flash both of these files in the bootloader to relock it.
Step 2: Boot to fastboot
Code:
adb reboot bootloader
OR
Code:
From power off, hold volume down and then press the power button.
Step 3: Flash stock bootloader from OTA zip
Run the following commands while in the firmware-update folder you extracted from 5.8.020S_sta.zip
Code:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
The bootloader is now locked again.
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
NOTE: I found that after using this method to re-lock the bootloader I could no longer use the guide for persistent bootloader unlocking.
If you want to unlock the bootloader again later, you need to manually flash the emmc_appsboot.mbn from the file in this thread:
https://forum.xda-developers.com/le...7-model-persistent-bootloader-unlock-t3500388
FILE: https://www.androidfilehost.com/?fid=313042859668275431
I hope that some of you find this helpful. Please let me know if there is any additional information that I should add to this thread. I will update it as needed.
Cheers!
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
ajegile said:
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
Click to expand...
Click to collapse
Fixed! That's what I get for copy/pasting the text vs the actual URL.
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
neozengar said:
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
Click to expand...
Click to collapse
Yes, this method will still work. It should also work for restoring to newer versions of stock (if needed).
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
neozengar said:
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
Click to expand...
Click to collapse
Yes
Will this work with Lineage 14.1?
Cuvillier said:
Will this work with Lineage 14.1?
Click to expand...
Click to collapse
This will take you back to stock regardless of what ROM you are currently running.
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Cuvillier said:
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Click to expand...
Click to collapse
Ill try to get some time to find links for the newer firmwares and update for those. We just had a new little one join the family so I'm pretty busy and tires nowadays .
Regardless, you can always update once you get back to stock in this guide.
Ok thank you.
This will work on x720 too ?
new small ota update for x720 just came out
Cuvillier said:
This will work on x720 too ?
Click to expand...
Click to collapse
Yes
slgooding said:
Yes
Click to expand...
Click to collapse
bootloader in x720 is already unlocked from LeEco
Hello folks,
I am using T.A.R.S. 21S EUI 5.8 USA version and TWRP 3.1.0
How do I return to stock? stock recovery, locked bootloader, and stock ROM so that I can get OTA updates?
I already tried:
https://forum.xda-developers.com/le-...oader-t3539513
I am able to restore successfully, but I am not able to install any OTA update with this and device is stuck with 19S only. I tried both local update and OTA update. UE boots into EUI recovery and says "Installation failed". I tried both 20S and 21S updates.
I think latest is 23S now.
Thanks
Brar
What device?
Hello. I want to return to stock x720 ROM. I won't to flash US version, so I need CN backup? Or how to do?
I flashed custom Recovery (TWRP), Kernel (BlackScreen), OS (AICP) and Root (Magiskv12). Should I flash trough recovery lastest official OS version?
I had to send the phone back to LeEco for repair, so needed to go stock.
Glad I found this post, thanks OP.
I tried the steps, all seemed to work okay, but now I am stuck at the leeco boot logo.
I can get to bootloader:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
I can also get to stock recovery, wipe data and update with update.zip
I think the phone is missing OS or something.
Please help.
I decided to make this thread so people won't brick their devices/lose their IMEI/explode their phone when trying to update to the recently leaked/released Oreo Motorola ROM.
This is very information dense. Please, read this and the linked threads carefully and do not miss any step unless told so.
WARNING: This will erase all your data, reset all your settings. MAKE BACKUPS.
I also do not hold responsibility for any negative outcomes out of following this tutorial.
Always look for as many sources of information as you can. There is always something that isn't 100% correct in every tutorial.
Also, making it clear. This is for those who are currently on an Oreo CUSTOM ROM such as Lineage, Pixel Experience or other.
Preparation Steps:
Backup all your important files to your PC. You should do that since everything will be reset.
Make sure your phone is well charged. 80% at least. You want to be safe.
Boot into fastboot.
Install Minimal ADB and Fastboot.
In the command prompt of Minimal ADB and Fastboot, type:
Code:
fastboot getvar all
You will see a bunch of lines come up on the screen. Scroll and look for
Code:
(bootloader) ro.build.fingerprint[0]
.
This will tell the last version of the Stock ROM (Nougat) you had installed.
Example: "NPNS25.137-92-4" Yours won't/may not be the same.
Write it down somewhere. You will need this version number.
Open this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ to download the exact version you found. If anything, download a version above the one you found. Never an inferior. Those are Motorola's Official Nougat ROMs.
Keep it somewhere accessible in your PC and extract the zip. Remember where you put it, you will need it later.
You will now proceed to check your persist partition. Aka: The thing everyone overlooks and screws your IMEI.
IMPORTANT: Take a look at https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 to find out if your persist partition has permission issues and see if it's recoverable. It is 99% likely that if you are on a custom Oreo ROM that the permissions won't be intact.
If that is the case (most likely), download NZedPred's TWRP Persist Restore zip into your phone.
Feel free to skip these last steps if you have a backup of your persist and efs.
Reboot into recovery and using the most recent TWRP make a backup of your persist and efs. (Information about this can be found on the second post of the "Fix Persist" thread. I am not willing to write a thousand instructions on one thread for the sake of not overcomplicating things.) //****ty steps: have/flash most recent TWRP > backup > select persist and efs > profit
These backups should be on a TWRP folder of the internal storage of your Moto G5. Reboot the phone (or mount USB) and copy that folder to your PC. In case anything goes wrong you will have a copy of your persist.
Steps:
Reboot into recovery (TWRP) using your preferred method. (Be it by the buttons, or via ADB (adb reboot recovery)).
Flash the TWRP Persist Restore zip.
Reboot into bootloader
Open (on your PC ofc) the folder with the extracted files of the Stock ROM zip (NOUGAT).
Open the extracted files folder then press Shift+RMB (Right Mouse Click/Button) and select "Open Command Prompt here" (It may work with Powershell??? If anything, write a post here)
For a quick test, type
Code:
fastboot
In case an error pops-up and tells you that it can't recognize such a command. Follow this article https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ to add Minimal ADB and Fastboot to your system environment variables
Now, make sure that the path to the left of the typing cursor is the path of the folder where you have your extracted Nougat ROM files.
Please, for your phone's OTA update ability sake. Make sure that you are flashing the exact version you had before. The version you found by running fastboot getvar all.
The commands below will attempt to update the bootloader and gpt. You should NEVER flash an older version of the bootloader.
If you wish, you can skip the GPT/Bootloader commands. I haven't done myself because I flashed the correct version I had before anyway.
Copy and paste these commands and press enter in the CMD.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will flash the Stock Nougat ROM you have downloaded and will reboot your phone. If all goes well you will be back on Nougat, set up your device as normal.
Attention, everything has been reset, erased, wiped.
Oreo OTA Steps:
After setting up everything, check for OTA's. You should be safe to install them. If you are on a recent firmware, you may only need to install security ones. Keep installing and checking until it says there are no more updates available.
This is where people **** up when they downgrade their bootloader by flashing an older Stock ROM than the one they had before.
Before proceeding, double check that there aren't any OTAs available or that Oreo is available at the time of reading this.
If Oreo is officially available, skip all of these steps and be happy.
Otherwise, if at the time of reading, there is a ZIP of the Oreo ROM that matches your region. Download it.
In case of RETLA, RETBR, and RETIN, at the time of writing, this is the correct file:
https://mega.nz/#!DxdSVaJb!5VEht-s6HYCNOZ2hXXVIPdFBqmWCuAvQL1Wzmp7rhZk or https://drive.google.com/open?id=1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY
In case you are on RETUS, RETAPAC, RETEU, etc. You may need another file that may not be available. The best course of action would be to wait for the Official OTA. :good:
Download it and put in the root of the internal storage of your Moto G5 Plus.
Go to the Settings app. In the Settings app, you'll want to find the OTA App (Motorola Update Services) by showing System apps and enable storage permissions.
Before you proceed: This is apparently indeed the official OTA that they will ship, which seems to be the same as the Soak 4. It's seemingly stable here, so, you should be fine to use that.
Check on your phone for an OTA.
Reboot it.
Check for an update again. There will be a prompt telling you about copying "system" files. Accept it.
After a while, another prompt will ask you about the update. There won't be a changelog, this is normal. Make sure your device is charged and install it.
Wait for the update to complete and you're done.
Tips:
You can also refer to this thread for some more information about fastboot flashing:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Refer to this thread if you need persist information:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Google and XDA are your friends.
It's good practice to wipe/reset your phone after you're done. Updates usually leave dirt behind. I haven't personally done this myself and everything is OK, but still...
Feel free to correct me on any mistake. It took me about an hour (or more) to write this and I could have potentially overlooked an important detail.
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo , what do you think? Thanks!
TheGameExtreme said:
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo, what do you think? Thanks!
Click to expand...
Click to collapse
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
I had hardbricked my phone and am using a tarp flashablr stock ROM. Can I use this method to go back to stock?
BlackScout said:
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
Click to expand...
Click to collapse
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
TheGameExtreme said:
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
Click to expand...
Click to collapse
Yeah, your bootloader is still from Nougat. One day, that could become a problem (hard brick) when taking OTA's.
You can easily fix that by going back to Nougat. (Just make sure to flash the exact version (or one above) the one you had before. Remember, never downgrade your bootloader.).
I think you can just fastboot flash NPNS-25.137.92-14 (since the difference between that and the base 92 patch is just security patches...), download the OTA zip that's been posted around and follow the last set of instructions here (The ones labeled Oreo OTA Steps)
Remember, flashing those TWRP zips made by NZedPred is technically not the same thing as fastboot flashing or taking an OTA. These zips don't upgrade your bootloader and the OP of those threads do not recommend you to take any OTAs.
Quoting from the source: https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The partition table and bootloader are not included, which makes it safer to up/downgrade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
So if you want to take the Oreo OTA and have an upgraded bootloader (C0.92), don't flash these. Flash the official Stock ROM (Nougat) images using fastboot then take the OTA.
I got all the information from this guide thanx but one doubt is there , i have my own efs nd persist and i have also backed it up so do i need to restore the restore zip or m i good to just fastboot flash nougat rom and update it via OTA to oreo? I m using custom oreo rom right now and i have never lost 4g or imei that means my efs and persist is my original..
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
karan3660 said:
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
Click to expand...
Click to collapse
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
psychopac said:
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
Click to expand...
Click to collapse
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
karan3660 said:
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
Click to expand...
Click to collapse
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
psychopac said:
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
Click to expand...
Click to collapse
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
karan3660 said:
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
Click to expand...
Click to collapse
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Click to expand...
Click to collapse
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
NZedPred said:
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
Click to expand...
Click to collapse
That would be a nice move from Moto/Lenovo.
So I should have said:
So you probably won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
nvrpayretail said:
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
Click to expand...
Click to collapse
This Oreo OTA requires the Brazil or Indian firmware to flash onto (possibly Latin America firmware). As you've found out, this OTA is NOT compatible with US devices as they're on a different stock build. You'd have to wait for the EU, APAC or US OTA updates to be leaked or released. You'd also have to be on the NPNS25.137-93-14 update to apply the OTA update when it arrives.
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version28.potter.retail.en.US.zip
Click to expand...
Click to collapse
Yup, I've checked the link and it's linking to the Brazil Oreo OTA update. Despite the suffix 'en.US', this does not necessarily mean this update is for the US devices.
Furthermore, looking at the OTA updater script, it specifically requires NPNS25.137-92-14 or OPS28.85-13:
Code:
Package expects build thumbprint of 8.1.0/OPS28.85-13/b8ea:user/release-keys or 7.0/NPNS25.137-92-14/16:user/release-keys
Since you have mentioned you have NPNS25.137-93-14 this OTA simply will not flash to your device. You must wait for the compatible OTA to be released.
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
Click to expand...
Click to collapse
Despite its name, it is not the us ota.
I did NOT Develop or create any of this! THANK YOU TO EVERYONE THAT DID!! Although it would be easier for me to directly link to the files, instead I linked to the creators page for you to download the files, and give them credit.
What did I do? I inherited a Tmobile LG G5 LG-H830 and couldn't find any good info to quickly get up and running a custom rooted ROM. So I spent a few days researching and testing, and decided to put all of this current info in one place in an easy to follow guide.
Who is this for? Someone like me that wants an all-in-one, easy to follow guide to get a Custom ROM installed, but NOT a lot of time. The other key here is this information is the latest as of March 2019. Once you get this going, customize all you want. And DO share!! This guide should work on ALL software versions out there.
What will you have when you're done? TWRP Recovery & LineageOS 15.1 (Oreo, Android 8). BUT, you can install your own ROM at that point instead if you want.
Quick Notes:
-About G5: https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648/
-Tmobile is easily bootloader unlockable, but no fastboot commands available! Dirtycow exploit is how to install the TWRP Recovery. All exploits are based on "20a", which is (Nougat Android 7.0). Guide will walk you through getting to this version.
-Root: Via Dirtycow exploit, Install TWRP & flash SuperSu
-LineageOs is the successor to CyanogenMod. It is directly based on AOSP, bare bones Android. ZERO bloat. You pick what Google apps get installed when you get to the GApps part.
This will wipe all of the data off your phone!! I am NOT responsible for ANYTHING you do!!
Summary:
-Prerequisites: ADB: Download Android SDK
-Unlock Bootloader
-Downgrade Android software to 20a (Nougat)
*Need 20a in order to flash TWRP https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
-Install TWRP Recovery via ReCowvery https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://github.com/jcadduono/android_external_dirtycow#running
-Install LineageOS
Unlock Bootloader:
-Enable Developer options
-Enable OEM Unlock
-Connect USB PC<->Phone
-Unlock: adb reboot bootloader
fastboot oem unlock
fastboot getvar unlocked (Should say unlocked)
fastboot reboot (get out of fastboot)
adb reboot bootloader (restart into bootloader)
Downgrade to H83020a: (Nougat Android 7.0) https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
-Download & Install LGUP_Store_Frame_Ver_1_14_3.msi https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
-Download & unzip UPPERCUT_1.0.0.0.zip https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
-Download & Install Latest LG Windows PC drivers http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
-Download H83020a_00_1107.kdz https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
-Turn OFF device then place in Download Mode: Hold Volume Up while plugging in USB cable.
-Double-click the UPPERCUT.exe to load LGUP... ( I got errors, then clicked abort - not sure whats going on here, but continue with steps below)
-Open LGUP (desktop shortcut)
-Select device
-Check "Upgrade" box
-Check BIN File box under File Type then select H83020a_00_1107.kdz
-Click START button to flash file to G5 (you may have to close and reopen LGUP before being able to hit Start)
-Phone reboots
-"Encryption Unsuccessful" message: Click Reset phone & allow it to do its thing
Install TWRP Recovery - ReCowvery Method
https://github.com/jcadduono/android_external_dirtycow#running
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496
-Download (4) ReCowvery files to ADB.exe directory: https://build.nethunter.com/android-tools/dirtycow/arm64/
-Download latest TWRP to ADB.exe directory & rename to twrp.img: https://dl.twrp.me/h830/
-Command Steps: https://github.com/jcadduono/android_external_dirtycow#running
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img
adb shell
$ cd /data/local/tmp
$ chmod 0777 *
$ ./dirtycow /system/bin/applypatch recowvery-applypatch (wait until done, ~2min)
$ ./dirtycow /system/bin/app_process64 recowvery-app_process64 (will see Tmobile screen, continue)
$ exit
adb logcat -s recowvery (still tmobile screen)
"[CTRL+C]" (Keyboard CTRL+C to break from cmd)
adb shell reboot recovery (wait for phone to reboot to Android)
adb shell
$ getenforce (should say Permissive)
$ cd /data/local/tmp
$ ./dirtycow /system/bin/run-as recowvery-run-as
$ run-as exec ./recowvery-applypatch boot (wait for it to flash boot image)
$ run-as su (should say "We have root access")
ls /sdcard/twrp.img (should show file)
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery (flash TWRP)
reboot recovery
-Should be in TWRP!
TWRP Recovery Startup & Disable Encryption:
-Swipe to allow modifications
-Disable encryption & Root:
-Download latest no-verity zip to adb.exe folder: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
-Copy to no-verity phone:
adb push no-verity-opt-encrypt-6.0.zip /sdcard
-Flash latest no-verity zip via TWRP
-Download latest SuperSu to adb.exe folder: (SuperSu/Root is only needed here if you will stick with Nougat rooted, won't hurt regardless) https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
-Copy SuperSu to phone:
adb push SR5-SuperSU-v2.82-SR5-20171001224502.zip /sdcard
-Flash SuperSu zip via TWRP
-Format Data (REQUIRED!):
-TWRP->Reboot->Recovery
-TWRP->Wipe->[Format Data]
-Reboot
-Flash SuperSu again (? I didnt do this and didnt end up with SuperSu, hoping this fixes that)
-Wait for Android to boot, will show "Android is starting" message. Go through phone setup
-Should have SuperSu installed & root
*If you don't have SuperSu:
-Reboot to recovery (Enable Developer option, enable adb debugging, adb reboot recovery)
adb push SR5-SuperSU-v2.82-SR5-20171001224502.zip /sdcard
-Flash SuperSu zip. Wipe Cache/dalvik. Reboot System.
-Ignore Warning message on boot. This is because we unlocked the bootloader.
-Should have SuperSu now!
Install UNOFFICIAL LineageOS-15.1 (Oreo, Android 8) https://forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-15-1-g5-t3806842
-Download GApps: (Pick you own style, I chose mini) https://opengapps.org/?arch=arm64&api=8.1&variant=nano
-Download LineageOS for G5: https://forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-15-1-g5-t3806842
-Download to-x86cpu.zip: https://forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-15-1-g5-t3806842
-Copy files to phone
-Restart phone into TWRP Recovery: adb reboot recovery
-TWRP:
-Flash to-x86cpu.zip
-Back, Back, Reboot->Recovery
-Flash LineageOS
-Wipe cache, and dalvik cache
*Optional: Flash Magisk (root, customization, etc) https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-Flash GApps
-Wipe->Factory Reset (swipe)
-Reboot . Will reboot a couple times. Then see arch with circle moving. Wait ~5 minutes. Enjoy.
-Install MagiskManager-v7.0.0.apk (Required for Magisk) https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reserved1
Reserved2
Please share any customizations you think others would want. Like how to increase the volume (mine is low, unless the speaker is broken!), status bar tweaks, ...
Thank You for this....worked for me...
You're awesome, I just picked up an H830 for $45 on ebay, last flagship with swappable batteries. The camera with gcam port is superb, so everything I need in a phone still.
Hello sir. i have missed disable encryption steps.
and now my phones getting encrypted.. what should i do.. please help. :crying:
Encryption Unsuccessful
I've done everything correctly using this guide and the dirtycow github link, but no matter what I still get the "Encryption Unsuccessful" message.
It tells me that the password I entered was correct, but the data is corrupted and that I need to factory reset my phone. Pressing the reset phone button brings me to TWRP.
Really hope I didn't kill my phone...how do I fix this?
---------- Post added at 05:57 AM ---------- Previous post was at 05:39 AM ----------
I give up. How do I bring this back to stock
One correction, on the step "adb push twrp.img" , need to add " /sdcard/".
Worked great. Now running stock 30c with mk2000 kernel, rooted with magisk. Thanks for the writeup!
You need to follow the twrp recovery startup instructions now, flash no-verity etc...
Asdfguy86 said:
I've done everything correctly using this guide and the dirtycow github link, but no matter what I still get the "Encryption Unsuccessful" message.
It tells me that the password I entered was correct, but the data is corrupted and that I need to factory reset my phone. Pressing the reset phone button brings me to TWRP.
Really hope I didn't kill my phone...how do I fix this?
---------- Post added at 05:57 AM ---------- Previous post was at 05:39 AM ----------
I give up. How do I bring this back to stock
Click to expand...
Click to collapse
You need to follow the twrp recovery startup instructions now, flash no-verity, format data....
Then grab the oreo 30c zip from the tmobile g5 xda forum and flash it from twrp
boxes said:
You need to follow the twrp recovery startup instructions now, flash no-verity, format data....
Then grab the oreo 30c zip from the tmobile g5 xda forum and flash it from twrp
Click to expand...
Click to collapse
I did do all of that stuff as well, but it still would give me the Encryption Unsuccessful message. I guess I installed TWRP correctly at least because pressing "Reset Phone" would take me to TWRP. From there I would try formatting data and flashing no-verity/supersu.
If I feel like making another backup of my phone one day I'll give this custom rom thing another try, but thanks for the help!
No SuperSu
I can't get SuperSu to install so my phone is not rooted.
I see in your instructions that you had to install it twice but that didn't help.
I originally installed LinageOS 16.0 but when I saw you used 15.1 I went back and installed that.
Neither worked.
When I try to install SuperSu with TWRP, I see the lines:
- patching sepolicy
--- Failure, aborting
I'm assuming that is the problem.
When I invoke getenforce under TWRP, it shows 'Permissive' but when I try under LinageOS, it shows 'Enforcing'.
Under Settings/System/Developer options/Root Access I can only choose between 'Disabled' and 'ADB only'.
Any idea where to go from here? How would I go about starting over?
TIA, Jim
jimmcghee said:
I can't get SuperSu to install so my phone is not rooted.
Click to expand...
Click to collapse
Well...
Never mind.
After looking at it all for about the 50th time, I noticed the optional install of Magisk.
It ain't so optional. At least, for me.
I flashed it and installed the apk and
I NOW HAVE ROOT!!!
I don't claim to understand it but SuperSu didn't flash/work and Magisk does.
Hope this helps some other poor soul.
While I'm at it, I saw a post about how the line
adb push twrp.img
in 'Install TWRP Recovery - ReCowvery Method' should have been
adb push twrp.img /sdcard/
Any chance that could be corrected in the walk through?
And,
the gapps for LinageOS 15.1 is 8.1 but the one for LinageOS 16.0 (the newest) is 9.
I probably should have known this but would you consider mentioning this in the walk through?
I know, users are neeever happy. What can I say.
Except, of course, thanks for putting all this toheather. I'm sooo tickled I've finally gotten this working.
Asdfguy86 said:
I did do all of that stuff as well, but it still would give me the Encryption Unsuccessful message. I guess I installed TWRP correctly at least because pressing "Reset Phone" would take me to TWRP. From there I would try formatting data and flashing no-verity/supersu.
If I feel like making another backup of my phone one day I'll give this custom rom thing another try, but thanks for the help!
Click to expand...
Click to collapse
I saw that someone else had this same issue, the solution was to use an older version of TWRP, they no longer encountered the encryption unsuccessful message. I actually used an older version when I did this, I believe it was twrp-3.2.3-0-h830.img
I didn't have any issues. I should have mentioned this earlier on.
Once you get the phone all setup though, you'll want to flash the latest TWRP from within TWRP or flashify. I found that the older version of TWRP had issues making backups of certain partitions.
boxes said:
I saw that someone else had this same issue, the solution was to use an older version of TWRP, they no longer encountered the encryption unsuccessful message. I actually used an older version when I did this, I believe it was twrp-3.2.3-0-h830.img
I didn't have any issues. I should have mentioned this earlier on.
Once you get the phone all setup though, you'll want to flash the latest TWRP from within TWRP or flashify. I found that the older version of TWRP had issues making backups of certain partitions.
Click to expand...
Click to collapse
Thanks a bunch! This did actually work for me, and now I have TWRP + rooted stock kernel with SuperSU.
I did have to flash SuperSU twice for it to work, but since then it's been flawless.
boxes said:
You're awesome, I just picked up an H830 for $45 on ebay, last flagship with swappable batteries. The camera with gcam port is superb, so everything I need in a phone still.
Click to expand...
Click to collapse
hey boxes - which GCam port are you using (and on which ROM)? I have a few stock 20a H830 phones (haven't flashed with LOS or other custom yet) as well as a LOS 17.1 I just flashed yesterday and having issues getting GCam to run without FC'ing on any of them... thnx man
mgreig said:
hey boxes - which GCam port are you using (and on which ROM)? I have a few stock 20a H830 phones (haven't flashed with LOS or other custom yet) as well as a LOS 17.1 I just flashed yesterday and having issues getting GCam to run without FC'ing on any of them... thnx man
Click to expand...
Click to collapse
Not sure which one I was using anymore tbh (got a new phone), try some of Arnova's and CStark27 builds-
https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
boxes said:
Not sure which one I was using anymore tbh (got a new phone), try some of Arnova's and CStark27 builds-
https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
Click to expand...
Click to collapse
I'll give it a go - thanks much
how do I revert back to stock? device shows up as "LGE Mobile for VZW USB Serial Port" on my pc, & LGUP/Uppercut says "Unknown Model" - tried flashing a stock zip on 1 phone thru TWRP but ended up bricking it (usb is not even detected)
edit: never mind, I got it restored using flash tool
edit2: hmm, re-tracing my steps I think it's possible I tried to flash an h850 rom thru twrp, causing the brick (careless mistake after long, tiring day - still looking for h830 firehose to recover that phone) - so I probably didn't need to use flash tool
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Unlocked bootloader
working ADB/fastboot on a PC
the TWRP image downloaded
Pie firmware on the active slot
Installation guide (pre metadata encryption):
Copy the twrp image to your phones storage and/or micro sdcard
Start cmd/powershell/terminal with working adb/fastboot
Reboot to bootloader
adb reboot bootloader OR
turn off the phone (or reboot), as soon as it turns on, hold volume down while USB cable is connected
If youre unofficially bootloader unlocked, and you nuked laf, its volume up and USB for you
fastboot boot TWRP-judypn-boot.img
Confirm allow system modifications if asked
Press cancel if asked for a password (aka when youre encrypted, could also be that it doesnt show you /data at all and no password screen)
Go to Advanced -> Install Recovery Ramdisk
Select the TWRP image which you copied to your phone/sdcard earlier
TWRP will now be installed to both slots (boot_a and boot_b)
Go to Reboot -> Recovery to make sure TWRP is successfully installed
Features:
Install recovery ramdisk:
Selecting this, and then an image (e.g. of TWRP) allows you to install the ramdisk (where TWRP resides for example) into both currently installed kernels/boot images
Inject TWRP after install:
Automatically injects current installed TWRP into the boot image of the ROM/zip youre installing when ticked
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
How to flash ROMs (PRE metadata encryption):
Reboot to TWRP
Make a backup
Install -> select the ROM zip -> tick Inject TWRP -> Swipe for install
wait... ROM will be installed into the NON ACTIVE slot (if youre on a, it will be installed to b, and vice versa)
Reboot system
for gapps, magisk or other mods:
DO NOT REBOOT TO SYSTEM from last step
Go back -> Reboot -> select the non active slot (to where the rom got installed to) -> select recovery
Install gapps, magisk, and whatever else you want
Reboot system
How to initially flash ROMs (metadata encryption):
Reboot to existing TWRP
Make a backup of everything you want to keep
Copy backup to PC (or another external medium)
Flash the ROM
Do NOT inject TWRP (this will break recovery otherwise)
Go to reboot -> Select opposite slot
Reboot to recovery
Perform factory reset (this is to setup encryption)
Apply update (from ADB) with adb sideload for gapps/magisk
reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Use as usual
Reboot system
How to update ROMs (metadata encryption):
Reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install -> Select ROM zip
do NOT inject TWRP
Reboot -> select opposite slot (it will tell you even which it installed the ROM to)
Reboot bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install gapps/magisk
Or
reboot recovery
apply update -> from adb (in e.g. Lineage recovery)
On PC: adb sideload <new version zip>
(Advanced -> ) Reboot recovery
adb sideload gapps/magisk
reboot system
Warnings:
Updating a ROM means reflashing the mods you flashed too (e.g. Gapps), addon.d doesnt work properly
Be aware of the slot you are currently on
If youre flashing a ROM to a slot, make sure you also have the required firmware (abl, modem, and so on) in that slot
Infos:
System image/Vendor image and system/vendor are redundant, the image variants are direct copies of the partition (and also their size) while the others are "simply" files copied and repacked
How to use decrypted stock by @Xsavi : https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Metadata encryption TWRP requires 10 firmware to use properly, no guarantee for it to work on Pie firmware!
Download:
Metadata bootable: https://drive.google.com/file/d/1hdzeH3AIQVf3siQNsI27IS_vmghPESEG/view?usp=sharing + Install zip: https://drive.google.com/file/d/1CQUfg54zD838detcIJqdRiKXdVNtd6Iy/view?usp=sharing
Bootable: https://drive.google.com/open?id=1UnIFbJlXHl6x4azq6H6yS-PRfk-omdTP
Old: https://drive.google.com/open?id=1p3IrbeOxM4ay01JccyifWDuxqqrE0_Dl
Sources:
device tree: https://github.com/SGCMarkus/android_device_lge_judypn-twrp/tree/android-9.0
kernel: https://github.com/SGCMarkus/android_kernel_lge_sdm845/tree/lge-pie-v409-20a
XDA:DevDB Information
TWRP for Judypn, ROM for the LG V40
Contributors
SGCMarkus
ROM OS Version: 9.x Pie
Version Information
Status: Alpha
Created 2019-09-20
Last Updated 2019-09-20
Hmm interesting I see ?
Wow. The V40 got TWRP too. Awesome.
Wooo new twrp! Great work Markus!
How hard would it be to get this working on the V35? I can get it to install and boot into recovery, but it does not register touch input.
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
lowridincrew said:
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
Click to expand...
Click to collapse
did you have pie firmware also in the slot where you installed LOS to?
otherwise.... nothing is ever really a brick, you still have 9008 mode as last option
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
How do the two slots work? I thought that these were for current ROM in one and then new ROM in the other, alternating with each ROM update. Why is one for the ROM and the other holding system partition additions? I would expect gapps to integrate into both A and B sides at once on top of each ROM...
Is there documentation on this?
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
EDIT: tried different USB-C cables and one worked like a charm.
seacrow01 said:
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
Click to expand...
Click to collapse
What happens if you try and access the bootloader aka the fastboot...
Ainz_Ooal_Gown said:
What happens if you try and access the bootloader aka the fastboot...
Click to expand...
Click to collapse
Nothing, phone just reboots like nothing is there. neither the button combo nor the "adb reboot bootloader" command works.
So I got on of the US models unlocked bootloader Verizon I got fastboot can I flash this one to my 405ua verizon?
In fastboot i see Judypn But I believe they flashed a open Korean on mine Im trying to get back to US firmware twrp and magisk if at all possible
Well I can confirms this works for pie on a 405ua unlocked bootloader...Nice work mate...
After reading through a bit and playing around. I got recovery installed on ramdisk recovery. Got out of my bootloop by fastboot flashing stock boot img from my current firmware. I did notice slot b I still have stock recovery which helped getting out of the failed encryption loop. And I also have download mode there.
How to unlock bootloader in indian firmware????
why i cannot enter fastboot mode on my lg v40 v405UM with android pie. When i command adb reboot bootloader it goes to restart phone.Not enter fastboot mode. Please help me.Sorry for my english
Hi anyone can help me after flashing twrp my phone doesnt reboot or does it take long to boot after flashing twrp
lowridincrew said:
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
Click to expand...
Click to collapse
What drivers did you use? I can't get my LGUP to recognize the device. I'm trying to flash stock back to a working copy of Lineage 16 with twrp.
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
xaxxelous said:
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
Click to expand...
Click to collapse
Both, as pie uses the same kernel as TWRP when booted
Short Story: Updated to pie us99830b kdz after flashing some things and clean flashed 10 roms again and somehow wifi wanted work ok since then. I also made backups but I am not clear if they will work without first getting pie blobs through kdz. This fix is not necessary on all LG V30 variants so first check if your model works with the roms fine. May also want to double check Zachs adb shell commands do not work on your device or do that also just in case (bottom).
Suggestions: This may actually take some time if you run into problems. Might be good idea to throw your sim in another phone so you don't stress. Smoke a bowl or open a beer.
Warning: AOSP rules may apply here although everything seems well with both permissive/enforcing for me. See that thread. Proceed at your own risk. If anytime you are not detected in download mode you must flash an oreo stock twrp zip such as h93120h or us99820e.
Files: Wifi working for me with this method on each 10 rom I have tested(Liquid, Lineage, AEX, ION, Havoc) so find one of those. You may also need us99820b kdz(us99810d if 20b doesn't boot clean some reason), the h93030q twrp zip, kernel(huamea 1.9.3 suggested) and h930 22j modem (https://drive.google.com/file/d/16o93WU262HWv2fKPYnMxC81GY6bJ3Txd/view?usp=sharing).
Quick Steps:
20b kdz partion all boot to setup screen then power down+fastboot+install/boot twrp+ magisk-decrypt-ak3remover zips+boot to setup screen again(don't setup) then power down+download mode+ 30b kdz partition all. Decrypt error for me first boot with 30b kdz so "reset phone" may be needed if greeted with that screen. Get to actual setup screen on 30b then power down+fastboot+twrp(cancel on encrpyt error)+format+wipe all(but sd)+reboot recovery. Then finally your selected poison havoc q+open gapps+magisk+decrypt for a clean flash. After booting in once I then reboot to twrp and flash huamea because it temporarilly removes root which needs to be reflashed.
Troubleshooting Suggested Steps:
Prior Potentially Unecessary Steps*
i. First install the 10 rom without wifi and make a backup or use mine below of chosen rom (in my case us99830b clean flashed to liquid/lineage)
ii. Clean flash h93030q twrp zip +magisk+disable encrypt+22j modem.img boot to startup screen then reboot to recovery
iii. Format data then wipe all but sdcard/otg and restore the Q backup. Goal here is to get the wifi initially clicked in, but the calling quite likely will still not work now. You can attempt to flash some stock modems to see if they work for you but I had no such luck. Reflash 22j modem after if you do test others.
iv. If the 30b kdz has not been booting up flash us99820b kdz partition all then reinstall twrp. If the 20b kdz restarts by itself after booting up you must partition dl all us99810d kdz first before 20b.
Steps
1. Format data then wipe all but micro sd don't reboot
2. Go back and reboot recovery
3. Magisk+disable encrypt
4. Power off then download mode(volume up while plugging in cable)
5. Partition dl all us99830bkdz using patch lgup
6. Let it boot to first welcome screen but don't setup anything
7. power off then fastboot mode(volume down while plugging in cable)
8. In adb & fastboot enter fastboot flash recovery then fastboot boot twrp.img
9. Will get decrypt error still in twrp for second just hit cancel
10. Repeat steps 1 & 2
11. FLash Liquid 10.1+Opengapps or Microg if wanted+ Magisk+ disable decrypt zips and boot it to start screen but don't setup
12. -Optional-Reboot Recovery Flash Humea kernel 1.5-1.9.3 or another to stabilize wifi/ better battery life(could possibly be done in prior step, may possibly lose root) and reboot
13. Andy's Fingerprint fix for internal error promp at startup(some roms ok without): Download osmosis busybox and magisk props config hide. Reboot then type "su" in any terminal then "props", follow prompts and select lg-v30 h930. The error should go away on boot.
*The prior steps here initally fixed wifi for me but I still didn't have calling, so I chose partition dl all partitions(only way kdz seems to boot) using patched lgup back to us99830b to test again which I assumed would cancel this procedure out so alas still not 100% sure if required. A dev has said though if you get wifi on your device once you will always have it. Wifi has been sticking for me afterwards until flashing any oreo kdz then I must re follow quick steps.
Backups - magisk w/ huamei Kernel 1.5, opengapps, fingerprint fixed
LineageOs 17 https://drive.google.com/drive/folders/1uQSDWDYFjGlEQ-gdyyn8QVgT5tB6Cjku?usp=sharing
Liquid 10 https://drive.google.com/drive/folders/1w9e_oLWpDR5bWk5jhs4xs1H9Q-AOv0NI?usp=sharing
Zachs Faster Wifi Fix for some lucky LG V30 users:
" - you need a kernel with dm-verity disabled (custom kernel, etc.) - for now the one of the haumea_I.base kernels allow this process
- Magisk must be installed (root permissions)
- get into a shell and become root (adb shell -> su ; or via other means)
- cp -a /vendor/etc/wifi/WCNSS_qcom_cfg.ini /mnt/vendor/persist-lg/wifi/WCNSS_qcom_cfg.ini
- in my example wlan_mac.bin is copied to /storage/emulated/0/joan_int/wlan_bins/wlan_mac.bin (that's internal storage and a newly created folder joan_int and subfolder wlan_bins)
so the final command to "fix" all is
cp -a /vendor/etc/wifi/WCNSS_qcom_cfg.ini /mnt/vendor/persist-lg/wifi/WCNSS_qcom_cfg.ini
cp /storage/emulated/0/joan_int/wlan_bins/wlan_mac.bin /mnt/vendor/persist-lg/wifi/wlan_mac.bin
chmod 644 /mnt/vendor/persist-lg/wifi/wlan_mac.bin
you copy over the WCNSS_qcom_cfg.ini file to the expected place (the symbolic link is wrong)
and copy over the missing wlan_mac.bin also to the expected place"
wlan_mac.bin here https://drive.google.com/file/d/1GM-IBe0CJ9hA4s2TAzas8IJcN67FOMR3/view?usp=sharing
Shouts out to @ChazzMatt , @SGCMarkus, @kherio, Andy, Zach, Chiru, Harris, and others on telegram for the group think. Any difficulities after following these steps you can hit up @tyl xda / Andy on telegram, he was able to use a slightly differed spin using persist lg files which may work for you. I will try to update as things get figured out