[GUIDE] How to Root LG G8X!!! - LG G8X ThinQ Guides, News, & Discussion

This Guide will explain how to root your LG G8X
* Disclaimer*
* 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
* YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*Wait, what? No. Me or somebody else will help you
Click to expand...
Click to collapse
Prerequisites
Unlock phone using the guide here: https://forum.xda-developers.com/t/guide-how-to-unlock-bootloader-of-lg-g8x.4198025/
Do not restore abl before rooting.
Magisk Patched Boot (20e, Indian Variant): https://drive.google.com/file/d/1s2A7RUOptXer5LGMtbGV9SKg0kcyL_NP/view?usp=drivesdk
1. Download the magisk patched boot.
2. Copy it over to your fastboot directory.
3. Connect phone in fastboot mode.
How to put phone to fastboot mode?
#1: Using Button Combination
Power off phone, press and hold Vol- and insert usb cable. You’ll be in fastboot
#2: Using ADB
Connect phone to pc, enable USB Debugging. Then run this command
Code:
adb reboot fastboot
4. Now run the command
Code:
fastboot flash boot Magisk_Patched.img
fastboot reboot
5. Download and install Magisk Manager
6. Done! Your phone is rooted now.
To restore Network follow the guide in bootloader unlock thread...
If you have a different G8X variant or are on a different firmware​
1.Backup boot_a or boot_b using QFIL (Partition Manager>Read Data, Check Bootloader unlock guide for more details)
2. Install Magisk Manager
3. Click on Install and use Patch image function.
4. Save the boot image to pc.
5. Flash it in Fastboot using the command given above.
Known Issues: FP is broken
Thankyou

(copypasta'ed from the other thread)
For those who have yet to do this, I suggest extracting boot_a/b at the same time you flash the abl image. Prior to doing the fastboot oem unlock, use the Magisk patch file option (installed on the same or another device, and doesn't need to be rooted) to create a rooted boot image using adb push/pull. Once you fastboot oem unlock, go back into the bootloader and instead of fastboot flash boot, you can fastboot boot magisk_patched.img.
Once you go through the setup, you can open Magisk, which will download and install the full Manager app, at which point it will most likely reboot. You will need to fastboot boot again, and you should be able to do a normal Magisk install. I've usually found that as long as the patched boot is of the same Android version and within a few month of the patch level, it'll boot happily enough to do this. Afterwards, you can restore your abl image as you no longer need to use fastboot commands.
Doing this allows Magisk to save the stock boot image, and also allows you to get OTA updates by restoring the stock image right before any updates. Otherwise you will never be able to do an OTA update as it checks if the boot partition has been modified before installing the updates. Since there are no kdz for the US carrier models, your only other option would be to "brick" your device to try get your carrier's service center to restore a working firmware image.
-- Starfox

Sorry I posted in the wrong thread. I've deleted the contents, but wasn't able to delete the post itself

Guys, I am trying to follow this guide using the "different variant" method, but as soon as I boot after flashing boot.img the touchscreen doesn't work. Only way to get it back is to flash the boot_a.bin and boot_b.bin using QFIL. What am I doing wrong?

Is there a magisk patched image for the g850u20i

Is there an update for magisk patch image for 20b (unlocked US variant)?
Edit: Got my 20b version rooted.
Downloaded stock rom for the G850QM20b, extracted the kdz file to dz to .img grabbed the stock boot_a.img file and ran it in Magisk manager app, took the converted .boot.a.img (now renamed magisk_patched_clT14.img) and dropped it in platform tools, went fast boot, then flashed it. Came back up great, no issues and root access is clear.

Dapeplezchamp said:
Is there a magisk patched image for the g850u20i
Click to expand...
Click to collapse
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos

robnitro said:
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
Click to expand...
Click to collapse
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.

Dapeplezchamp said:
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Click to expand...
Click to collapse
follow the video here, I got it to work
hold power and vol down , itll countdown to reboot.... as soon as it does that- while holding down and power tap the up button
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com

Is there a image for the g850UM20g?
edit:
I have a copy of boot_a but in the fastboot it tells me that I am using abl_b and I don't know if boot_a is compatible with abl_b and i can't enter EDL mode

So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?

zdanee said:
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
Click to expand...
Click to collapse
Yes, rooting will be gone and Bootloader remains unlocked forever. You have to root it again in A10

For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.

Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x

Kanhei015 said:
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Click to expand...
Click to collapse
I do. But it's an EU version, so I'm not sure it would work for you. However it's easy to just make your own!
- Install Magisk manager on the phone. You don't need open bootloader or anything for that
- Get your own 20f boot_a using QFIL
- Copy your own boot_a to the phone or on an SD card
- In Magisk Manager you choose to install magisk, select patching an IMG file method and give it the boot_a
- If Magisk reports success you'll now have a magisk_patched_boot_a file. Copy that back to your PC
- Using QFIL flash that in place of your original boot_a
- Keep a copy of your original boot_a thou, you can go back with QFIL at any time.
- If you mess up royally and the phone doesn't boot, you can still recover it by re-flashing your firmware with LGUP 1.17. You'll have to download your region's firmware for that and you'll loose all data, so make a backup beforehand!

edit: double post

zdanee said:
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Click to expand...
Click to collapse
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.

james508959 said:
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
Click to expand...
Click to collapse
I also messed up at first, since there were no ready-made boot_a for my region/version I just grabbed the indian one for 20e, and yes, that did break my audio, fingerprint and possibly network, I didn't test that one. I did have a KDZ for my region thou, so I flashed back a 10c version, I needed the 1.17 tool, not the 1.14 or 1.16 one (those did not work) and in my case I needed the second version of 10c, not the first one to fix the fingerprint. After flashing 10c I did all the steps and regained my fingerprint reader without an issue (so no, it did not work right away, I did need to go into the service menu and do the test), audio and network also worked right away. After that I flashed my latest KDZ (20h) and using magisk manager made my own boot_a and was able to root with a working fingerprint. I did not dare to update Magisk after this thou, I only needed it to grant root for my adblocker, and it's hidden from everything else, I don't think I'll ever even start magisk again, so I don't really want to update it either.

Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.

james508959 said:
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
Click to expand...
Click to collapse
No, I did not restore abl_a/b, and after KDZ the bootloder remained open, so there is no need to, the phone still reports an open bootloader at boot. If it _does_ override it thou it seems it's not neccessary to have, as I could root the phone and could keep the open bootloader anyways.
I used QFIL to get my own boot_a, and used it again to flash it back too.
My EU (Hungarian T-mobile) version is also G850EMW. My understanding is that if LGUP lets you flash a KDZ it's probably gonna work, but in the worst case scenario as long as you have a known good KDZ for your model you can always come back to that, so I guess you can experiment?
I've also only found a 20b version of KDZ for TWN, but it's release date is similar to 20h in the EU, so maybe these numbers doesn't mean they are the same KDZ, only that 20x meant it's Android 10 and the letter is the revision. Based on this it's possibe you don't need a 10c to restore your fingerprint, just try the earliest 10x KDZ you can get your hands on (for me the 10c was the earliest one). Alternatively you can try the 10c I used for mine, it's EU Hungarian, but the default language is still English and you'll re-flash it anyways: https://lg-firmwares.com/downloads-file/21667/G850EMW10c_00_OPEN_EU_DS_OP_1122

Related

I brick my RS988, but I still have twrp.

So I rooted my device and life was good than I made something a system app and then I deleted it. :facepalm: Next thing I know I reboot and it comes to the unable to test corruption screen and the led light keeps flashing blue. I still have TWRP. Can it be saved?
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
You can try the KDZ because that's basically fool proof, but you can also try to manually flash the partition image for the one that's broken. I think that's the system partition in your case.
PleaseHelpMe12 said:
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
Click to expand...
Click to collapse
You're best bet would be to put it in download mode and flash the latest kdz using LGUP or uppercut. I've always used the original LGUP but seems like most now use uppercut and seems like uppercut is probably a better choice. You will have to reflash TWRP after you get back up and running and root as well as using the kdz will replace TWRP.
Sweet. It's alive again, but I can't access bootloader via adb reboot bootloader.
Edit: nevermind. I didn't update.

Stuck in fastboot mode,with only restart or shut down for options

So today i decided to update magisk to its latest versio, it all whet well,i did within android. later on in the day i decided to reboot myphone, and to my surprise it got stuck o thelgv30 thinq scree, after decide 10m was enough i rebooted and the it was stuck in bootloop, so i decided to restore my nanddroid , after it was done i hit reboot to system, and now it will only noot to fastootmode,, its as if there is nothing flashed to boot or system. any help will greatly appreciated.
EDIT: VERY OLD POST; WE CAN NOW USE NEWER MAGISK
____________
By "latest" you mean Magisk beta? You can only use stable 16.0 Magisk. Stated in the bootloader unlock/TWRP/root instructions that beta Magisk will mess up your phone.
Download Magisk or SuperSu. Magisk 16 (Use stable Magisk -- which right now is 16.0! Magisk "beta" will mess up your phone.)
Click to expand...
Click to collapse
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
ChazzMatt said:
By "latest" you mean beta Magisk. You can only use stable 16.0 Magisk. Stated in the bootloader unlock instructions that beta Magisk will mess up your phone.
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
Click to expand...
Click to collapse
yea that what i did fml. what do i do reflash the oreo kdz?
siulmagic said:
yea that what i did fml. what do i do reflash the oreo kdz?
Click to expand...
Click to collapse
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
Isint the master reset disabled with twrp? master reset only boots twrp, when you have twrp installed, i will try to wipe with lgup.
Thanks for the help man, phone is backup and running.
siulmagic said:
Thanks for the help man, phone is backup and running.
Click to expand...
Click to collapse
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
If you were using Trebel TWRP you have to use normal TWRP and restore the backup GPT in order for a stock nandroid to work or a stock based clean flash...
jmej88 said:
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
Click to expand...
Click to collapse
To fix stuck in fastboot or download mode
Connect phone in download mode
go in patched LGUP flash h93320f_00_open_ca_op_0612.kdz
With partition dl option
(not working go in device manager select modem
Then lge mobile usb modem right click disable driver try again)
help me:,(
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
I had the same problem but I tried many different versions but it was still stuck in fastboot i'm so scared help me pls
Im stuck in fastboot mode too after chip reset. Tried kdz us998 10 with no luck.
Anybody have other suggestions?
....edit.
Fixed flashing Canadian kdz.
mines wont go into download mode just keeps going to fastbootloader
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Flash twrp and flash rom.
Sent from my VS996 using Tapatalk
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Download kdz flashable zip then extract it. Flash the system.img and boot.img file via fastboot
This just happened to me today. It was either from the newest Magisk (v22) or from the newest YouTube Vanced. Those were the only things that changed recently on my phone. Rebooted today and it will only go to Fastboot mode and that's it.
Master Reset will get me into TWRP, but I think my USB port on the phone is damaged, it will charge but neither my Windows nor Linux PCs will recognize that it's plugged in. So it's like only USB charging works but not USB data. So I think I'm screwed, idk if it's fixable. Sad day.
Am also stack here qhile trying to unlock my bootloader using @bilong9 thread on my v300l .please help
This also happened to me while trying to update to Magisk 22. First I had an error with Magisk in a restart cycle, then when I tried to update manually from the APK I got stuck in a fastboot loop with no ADB access. I was able to boot to TWRP from fastboot on my PC, then re-flash the Pie image. My settings were all lost, but I did get my phone back at least. BEWARE of Magisk 22, or at least until it's fixed for the V30!
edit: I found that I COULD install Magisk 22.0.zip while following these instructions for restoring my phone:
LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) WTF...! LG V30,V30+,V30S (MOST VARIANTS) BOOTLOADER UNLOCK, TWRP, ROOT INSTRUCTIONS HERE >>>CLICK HERE TO POST #193
forum.xda-developers.com
after a few extra prompts from the Magisk app, v22 now works.
I've had no issues using Magisk v22 with an LOS 17.1 (Android 10) based ROM. It could just be that there's a problem with it on either LG stock or Pie ROMs.
UPDATE
* Variant: US998 US Cellular/Carrier Unlocked
* ROM: Rooted Stock Pie (US99830b)
* Magisk: v21.4
So it seems the issue is not that it "soft bricks", but something about the new installation process of Magisk v22 goes wrong with the /boot partition, causing the phone to only be able to boot into Fastboot mode.
After getting my phone fully recovered and restored from the last failed attempt (and making a new TWRP backup), I attempted the v22 update again. First Magisk attempted to download and install the new v22 app, and then a popup notification said "additional setup is required for your device, press OK to reboot". So I hit okay, and that's when once again I got stuck in Fastboot with no other options.
If you have a TWRP/nandroid backup, you can easily fix this by performing the Master Reset process in order to boot into TWRP, and then just Restoring the /boot partition from your TWRP backup. This will get you back to Magisk v21.4 where you were before, which is where I'm currently at.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
I've seen on both reddit and XDA that several people are saying they updated to v22 without issue, but it's unclear if they were on Stock or Custom ROM. My guess would be that Custom ROMs are probably working fine and it's the Stock ROM that's having the issue.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
Click to expand...
Click to collapse
I simply renamed the available .apk to .zip and it flashed in TWRP.
edit: the ROM I'm using is from this thread, which says it is 99% stock, whatever that means.

Possibly dense question about OEM unlock and magisk flash

EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
molotov_sh said:
EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
Click to expand...
Click to collapse
EDIT:
See post #7 below for root on this phone without TWRP.
For root for this phone WITH TWRP, see this post.
ChazzMatt said:
No, what you said won't work. See this thread below.
You need TWRP to root, by the way.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Click to expand...
Click to collapse
You don't need TWRP to root (some) other phones with Magisk, hence my original probing question. Originally when I did some poking around this forum I couldn't tell if some of the hackery being used was specifically for network locked phones or for some custom rom needs.
It looks like the subtlety here is that LG doesn't really unlock when you choose OEM unlock, it just lets you then request unlocking from them (or the trick you've linked). What a right pain in the behind.
Thanks for the pointer.
molotov_sh said:
You don't need TWRP to root (some) other phones with Magisk, hence my original probing question. Originally when I did some poking around this forum I couldn't tell if some of the hackery being used was specifically for network locked phones or for some custom rom needs.
It looks like the subtlety here is that LG doesn't really unlock when you choose OEM unlock, it just lets you then request unlocking from them (or the trick you've linked). What a right pain in the behind.
Thanks for the pointer.
Click to expand...
Click to collapse
In my experience, very few phones actually unlock bootloader with simple "OEM unlock". That setting only works if the OEM or carrier wants it to work.
XIAOMI makes you wait TWO months for bootloader unlock:
https://www.xda-developers.com/xiaomi-2-month-wait-unlock-bootloader/
Note I didn't say no phones, I said very few -- compared to the plethora of brands available.
For instance, Motorola makes you request a bootloader unlock code, but Verizon Motorola phones are not eligible.
Sent via open market LG US998 V30/V30+
I'm confused... 10c didn't need TWRP
So I last rooted when I was running 10c on my open market bootloader unlocked US998 V30 (through the official LG method with an LG-generated unlock.bin) and all I had to do was get a boot.img and let Magisk patch it then flash it using adb/fastboot flash.
I have updated to 20d (many thanks ChazzMatt for the KDZ and instructions) and was going to use westwood24's 20d boot.img with Magisk to systemless-ly root again. Since it seems to be asked a lot, I prefer to leave my /data encrypted and never noticed a slowdown without disabling rctd and prefer to have dm-verity on. If there's a way to do that with TWRP and leave stuff encrypted I'm all for it.
Is it no longer possible to flash back a patched boot.img to have just Magisk root and an otherwise completely stock device?
Kakari said:
So I last rooted when I was running 10c on my open market bootloader unlocked US998 V30 (through the official LG method with an LG-generated unlock.bin) and all I had to do was get a boot.img and let Magisk patch it then flash it using adb/fastboot flash.
I have updated to 20d (many thanks ChazzMatt for the KDZ and instructions) and was going to use westwood24's 20d boot.img with Magisk to systemless-ly root again. Since it seems to be asked a lot, I prefer to leave my /data encrypted and never noticed a slowdown without disabling rctd and prefer to have dm-verity on. If there's a way to do that with TWRP and leave stuff encrypted I'm all for it.
Is it no longer possible to flash back a patched boot.img to have just Magisk root and an otherwise completely stock device?
Click to expand...
Click to collapse
You're doing very advanced stuff, and I don't know the answer to that. A developer could give you answers...
I do know I prefer TWRP custom recovery for purposes of having backups. Like having a nifty time machine where you can erase mistakes you make.
TWRP can also let you flash zipped files to install other elements to your phone.
"Stock" recovery is fairly useless in my opinion.
Magisk systemless root without TWRP
ChazzMatt said:
You're doing very advanced stuff, and I don't know the answer to that. A developer could give you answers...
I do know I prefer TWRP custom recovery for purposes of having backups. Like having a nifty time machine where you can erase mistakes you make.
TWRP can also let you flash zipped files to install other elements to your phone.
"Stock" recovery is fairly useless in my opinion.
Click to expand...
Click to collapse
I decided to just 'go for it' again and it still works with Magisk 16 and 17.1 (I didn't dare try 17 with the possible bootloop problems). In the interest of not making something 'advanced' & possibly dangerous too accessible I'll share what I did in broad strokes so molotov_sh and future me can have a rough guide.
The process was:
0. Have an unlocked bootloader (either you have an open market US998 and used the official method or the WTF method)
1. Download the 20d update (what I'm using a newer one will hopefully also work) and the LGUP dev version.
2. Plug in your V30 using a USB2 cable and switch it to File Transfer mode.
3. Open LGUP
4. 'Upgrade' the phone using the KDZ from (1), let it reboot, finish and check that the phone boots, I like throwing in an extra reboot with the phone unplugged from the computer just to be sure. Do any backups of app data, make sure you have 2FA backup codes etc.
5. Reconnect the phone and open LGUP again and choose 'Dump'
5a. It's probably a good idea to dump the whole of your phone excluding 'userdata' just in case. I had a timeout error after about 30-35 minutes but it seemed to get all portions.
6. Choose the 'boot' checkbox for what you want to dump and choose a folder to save it in. The file it dumps is in .img format but does not have a file extension.
7. When its done, unplug the phone, close LGUP, reboot the phone to the regular OS, and plug it back in in file transfer mode.
8. Copy the boot image you dumped in (6) onto the phone, perhaps under Internal SD/Download (I'd add the .img and possibly a version like boot20d.img)
9. Install MagiskManager.
10. Open it, choose Install, Patch Boot Image file, choose the .img file you copied in (8). When its done (without any errors!) you'll have a patched_boot.img file
11. Copy patched_boot.img onto your computer (I like placing it right next to my fastboot executable); you might have to wait a few minutes or restart since the phone can be slow to show newly created files.
12. Unplug your phone & turn it off. Then hold volume down while your plug in the USB cable.
13. Open a terminal/command prompt and navigate to the patched_boot.img file and then run
Code:
fastboot flash boot patched_boot.img
14. It'll take a few tenths of a second and said 'OK'/'Done'. Then enter
Code:
fastboot reboot
and unplug the phone after it starts rebooting. I had mine go through 2 reboot cycles and then it was fine, Magisk works and SafetyNet checks pass.
Recovery is stock and I can have a working hosts file and TitaniumBackup. I use LGBridge for more significant backups.
molotov_sh said:
EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
Click to expand...
Click to collapse
See @Kakari's post just above this one for root without TWRP, using a patched boot.img.
@Kakari I actually posted a PM to @ChazzMatt about a day after I originally posted here with roughly your procedure (I think he may have seen this thread before that PM). I debated posting it here as I didn't have a clean experience with FOTA 20r to 20y (potential for others to suffer data wipes) - in the end I had to LGUP to go to 20y, see below.
For anyone interested in following my method it will wipe your data.
Let me quote my PM to him here:
Thanks for the pointer the other day
I've used your detailed guides, roms and the rather impressive group discovery thread to come up with a simpler method if you're just after root only and you want the official ROM - "light" root users.
As an aside, I should note that after downgrading to 20r (H930 European here), unlocking the bootloader and hard resetting the FOTA wouldn't bump me to 20y, it'd go through the motions and just wipe the phone each time it rebooted to apply it. So I used LGUP to flash 20y (what I was on before rooting with no updates available) and it's all good for now.
My steps:
- Downgrade to unlockable ROM version using LGUP. EU H930 20r here.
- Flash new_unlock.bin to unlock bootloader in fastboot.
- Hard reset as suggested.
- Flash "latest" official ROM using LGUP. EU H930 20y for me as I wanted what I had originally.
- Get the matching boot image (I pulled boot_6.bin from the 20y kdz)
- Feed to to Magisk Manager's install.
- Flash it in fastboot (fastboot flash boot <patched_boot_6.bin>)
Now I have an entirely stock ROM except for boot, so in theory FOTA capable. Rare use case possibly, but saves TWRP and the funky recovery flashing - which looked like it might also trip safetynet with the LG anti-root stuff (I guessed that might hit system?).
Not sure how FOTA will work going forwards for me, but my hope is that all I'll have to do is reflash a Magisk'ed boot. That'd (hopefully) be the only downside - needing to wait for a boot image to regain root, or (somehow) extract it from the phone.
In reality given my FOTA wipe experience I imagine full backups in advance (titanium in my case, as no twrp) will probably be necessary, just like one should do before flashing any custom ROM or update I suppose. Also as it's a modified boot, if the FOTA does a delta update/verify on it that could get awkward, and would necessitate another trip to LGUP.
Your work on the LG V30 has been invaluable, I hope the above is useful.
Click to expand...
Click to collapse
So yes, I have root with Magisk but no need for TWRP! Thanks for your input anyway, it may help others especially as it has LGUP backup bits.

How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)

All fix avilable (no network solved)
Watch it carefully do it step by step as showen in my video you will never brick if you follow my video
All required files are in the video description
This guide Tested on the firmware (20e ,20c,20d) (if you didn't see your firmware don't worry leave a command , I will help you ! )
How to check the frimware:
* Go to Settings - >System -> About phone -> sofware version ( eg: V20e-IND-XX so use 20e rootboot file)
All required files are in the video description
watch it in 720p only 40 mb
subscribe for more lg g8x content !!!
If any issue let me know i will help you with that
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
cyr4n0 said:
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
Click to expand...
Click to collapse
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
[email protected] said:
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
Click to expand...
Click to collapse
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
The one you provided was not help ,Give me the stock boot_a img (download the whole kdz and extract the boot_a.img)
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
Or you can flash the kdz back (make sure you are using the correct KDz
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
rainbowtuba said:
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
Click to expand...
Click to collapse
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
[email protected] said:
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
Click to expand...
Click to collapse
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
rainbowtuba said:
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
Click to expand...
Click to collapse
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
[email protected] said:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
Click to expand...
Click to collapse
Thank you, here is the boot_a.img
EDIT: I have potentially good news! I was completely stuck in a boot loop, but using the files from the KDZ (modem_a, modem_b, boot_a,boot_b, abl_a, and abl_b) and pushed them each with fastboot. The device restarted (with sound!) and it is resetting to stock now. We'll see what happens!
rainbowtuba said:
Thank you, here is the boot_a.img
Click to expand...
Click to collapse
How to restore download mode ?
can we root on 20f?
What about 20b
I own a LG G8x Sprint fw model with SW version g850um20f build qkq1.200216.002 with April Security patch. I unlocked the bootloader with this method after I sim unlocked it today. Interestingly I have now a T-mobile splash screen perhaps because I tested the sim unlock with my t-mobile sim? Either way it provisioned all the T-mobile operator software so it got rid of all the Sprint garbage and loaded volte wifi calling etc...I have yet to test all the features but it did it all for me after the factory reset happens when the boot loader unlocks. I did not load the original abl_a abl_b backup files back to the device. Was the patched abl file a US model dump?
Me gustaría saber si la versión 20j de sprint también se puede rootear
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
20b
Adminislayer said:
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
Click to expand...
Click to collapse
I did 20j sprint yesterday.
The hardest part was to get into EDL.
Where are you stuck?
BTW, does anyone have the twrp bin for these phones? I can't find a working link. I just want to boot into twrp temporary to do a system image.

How To Guide Relock bootloader and get stock recovery oneplus nord 2 Indian/EU: works for any MTK device

Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!​You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot

Categories

Resources