Related
Okay. so I have this Problem: I tried to install an incompatible Rom and im getting secure boot error boot certification verify. Normally would not be a problem. I have twrp installed and all the roms and files I would need to fix it. Here's the catch. The power button is broken so I have no access to the recovery menu. Just to turn it on I have to battery pop. Any help on getting into recovery through some back door? Can't get it to connect to ADB because I cant get past the secure boot error lol
Also I can get into download mode, but that still doesnt make the computer recognise it to connect with adb
From download mode you can use LGUP I think. You should be able to flash back to stock just to get it working again, and then go from there.
http://forum.xda-developers.com/showpost.php?p=64624324&postcount=2
However, I don't know what conflicts exist with doing that with a custom recovery or anything.
There's no conflict with custom recovery when flashing the official stock KDZ or TOT because either one will overwrite everything with the stock partitions. Personally, I recommend flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems KDZs sometimes can't. In my one try of using LGUp on the VS985 I didn't have any luck, so I stick with the old tools.
Also, in the future, please post questions in the Q&A section. I'll ask a moderator to move this thread.
Hey guys. Was able to finally get it fixed by flashing to 12b using the kdz method. Had issues installing twrp and had to use flashify premium. Finally got it all running and hooked up with cloudy g3 thanks for the advices
After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Garfoth said:
After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Click to expand...
Click to collapse
If you can get into TWRP still, I would try wiping the system and data. Then instead of LGUP, use uppercut (I'll link you to that if you need me to) to flash a KDZ to go back to stock
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Sorry to hear that. I think you have four options.
1) Reach out on the telegram v30 forum to someone with an Octoplus box to remotely resurrect your device.
2) Send it in for "repair".
3) Do it yourself, see https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946.
4) Buy a new phone.
The third option isn't hard, but may involve a lot of work so I'd go with the first one.
don"t worry too much, that phone is almost unbrickable, at least you are really unlucky, you will revive it. Wait for @ChazzMatt to give you some help before giving up hope entirely
Meanwhile, I can give you some advice because I was stuck one time on LG Logo, you were on which firmware when it last booted up?
While it is bootlooping, connect it to the pc, do a soft reset with power and volume down buttons, release them when the screen goes black and immediately press the volume up button to access fastboot menu, and if PC doesnt recognize it, shut down the phone by selecting it with volume button.
Deconnecting the phone and press volume down while reconnecting it to the pc to try to go to download mode and kdz your phone.
Somewhat working
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Update: Flashed US99820H and back in running order. I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Ergo-sum said:
Update: Flashed US99820H and back in running order.
Click to expand...
Click to collapse
Glad you got your phone working again!
Ergo-sum said:
I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Click to expand...
Click to collapse
Thoroughly discussed in the US998 Pie KDZ thread. Top of post #2 (one method), all of post #6 (three different workarounds).
If none of the 4 methods work for you, there are no other answers and you have to wait for another US998 Pie KDZ.
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
havetolearn said:
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
Click to expand...
Click to collapse
ChazzMatt said:
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
Click to expand...
Click to collapse
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
havetolearn said:
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
Click to expand...
Click to collapse
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Man there are so many broken oreo's firmware after update to pie.... Hmm, i think i will stay at pie because i need lg screen recording feature. It can record screen and system sound together. Thx for replying ChazzMatt
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
havetolearn said:
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
Click to expand...
Click to collapse
1) On my backup V30+ which is on stock US998 30b Pie (but doesn't have a SIM card inserted nor even signed into my Google account), it's connected fine to my home Wi-Fi network so I know it's not a stock US998 Pie issue...
2) This happens even on public free Wi-Fi networks? (Here in the U.S. we have McDonalds, Starbucks?) That would give you clue whether it's one particular router or all your phone has problem with. Or possibly problem with the type of encryption you have on your router.
Usually that message means the router is rejecting the device. You just have to figure out why. But is it one router or all?
3) If one particular router, try rebooting the Wi-Fi router itself.
4) Make sure you don't have any kind of router whitelist for certain devices or MAC addresses and your phone is not included. Or that you don't have some older b/g Wi-Fi chipset standard set; this one is not likely but I had that happen for an older Wi-Fi printer when I had "N" or higher set on my router.
5) On the phone, try forgetting the Wi-Fi network and refinding it. Enter in the password again.
6) Almost last, on the phone try the Network Settings Reset. (See screenshot from US998 30b Pie.) It will reset all network settings including Wi-Fi, Bluetooth.
7) Last, try Factory Reset?
In the same boat
Ergo-sum said:
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Click to expand...
Click to collapse
How did you unbrick your phone? I'm in the same boat as you. I can get to the Download mode, but not past the blue dot image. If I try to master reset, the phone just restarts after the second time I select yes. It's been bootlooping like this for a while now. For context, I was on US99820H(dirty flashed via twrp) when I tried to flash H93330k. @ChazzMatt, I know this is a long shot as what I did was incredibly stupid, but is there anyway I can get out of this?
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
But, how did you do that if you cant (couldnt) access to fastboot or recovery? Im crazy ?
please. help me.
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
Please help me, I am the same as you. please
phamtuyenk7d said:
Please help me, I am the same as you. please
Click to expand...
Click to collapse
See this post for Recovery of botched US998 30B upgrade:
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
Previous process:
Started from unlocked H931 Nougat
I'm afraid I actually forgot the precise order... maybe Nougat US998 -> Oreo, maybe Oreo H931 -> US998... Of course using Frankenstein method.
Using WTF..! method unlocked bootloader (I'm pretty sure at some point I also had twrp, and again, may have been prior to US998/Oreo flash... order).
Because of network problems flashed H931 Oreo, 2 years stable.
Current problem:
Flashed US998 Oreo from here: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Tried flashing US998 PIE from here: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
In LGUP instead of refurbish I clicked partition dl.
Phone was stuck in bootloop. I tried the button dance to Master reset, worked, however the erased system wasn't able to boot before anyway, how would this help I don't know. The bootloop stays.
Hoped to reach familiar Download mode, but couldn't even power the phone off (in no way from across the forum). Opened the phone, disconnected the battery - it's off. Tried to enter download mode... doesn't work. At least it charges. Tried to boot, entered bootloop again, master reset, bootloop again, disconnect battery.
Found this: https://forum.xda-developers.com/lg-v30/help/download-mode-doesnt-anymore-t3973801 , which leads to a possible solution here: https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-us998-30b-twrp-t3973811
I searched the comments, apparent solution was entering master reset menu and clicking yes in the dialog menus, which should start TWRP. I guess I don't have TWRP, because this does nothing much. A screen saying erasing appears, then goes to the same bootloop.
Bootloop, Download mode doesn't work, cannot acces TWRP. (soft brick)
Found no previous solution to work. (possibly couldn't find it)
Is there any help for me? Should I start looking for something less LG?
have you fixed it? Have you unlocked your device's bootloader yet?
If you have unlocked the bootloader then flash the laf.img file
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
If you want to update android 9 us998, please kdz via ROM h93030b to install twrp, then flash us99830b.zip via twrp
give it a try
Unfortunately not yet. Thanks for the tip, but until I find a way to boot anything on the phone, I guess I won't get to flashing.
I think @thao12345 is saying that (1) if your bootloader is unlocked (it must have been if you ever installed TWRP, unless you relocked it) and (2) if you are currently on US998 ROM, then you should have working fastboot flash commands, and you can fix almost anything.
Boot into fastboot from power off by holding Vol- while plugging in the cable. Of course ADB installed on computer. Test with "fastboot devices".
From there you can use "fastboot flash recovery twrp.img" to get TWRP, or "fastboot flash laf laf.img' to fix download mode. I believe laf.img can be found in the TWRP-flashable US998 ROM thread.
Once you have working download mode, the next step is to temporarily flash US998 Nougat using Partition DL and the latest Pie compatible LGUP. This should help clean up the phone.
TheDannemand said:
I think @thao12345 is saying that (1) if your bootloader is unlocked (it must have been if you ever installed TWRP, unless you relocked it) and (2) if you are currently on US998 ROM, then you should have working fastboot flash commands, and you can fix almost anything.
Boot into fastboot from power of by holding Vol- while plugging in the cable. Of course ADB installed on computer. Test with "fastboot devices".
From there you can use "fastboot flash recovery twrp.img" to get TWRP, or "fastboot flash laf laf.img' to fix download mode. I believe laf.img can be found in the TWRP-flashable US998 ROM thread.
Once you have working download mode, the next step is to temporarily flash US998 Nougat using Partition DL and the latest Pie compatible LGUP. This should help clean up the phone.
Click to expand...
Click to collapse
right. If the phone is in us998 or h930, you can flash the laf.img file.
If not in the two modes above but get bricked then you can try the ways to enter "EDL qualcom 9008" mode then rewrite the partition using a tool such as QFIL
---------- Post added at 02:08 AM ---------- Previous post was at 01:56 AM ----------
MarcRossi said:
Previous process:
Started from unlocked H931 Nougat
I'm afraid I actually forgot the precise order... maybe Nougat US998 -> Oreo, maybe Oreo H931 -> US998... Of course using Frankenstein method.
Using WTF..! method unlocked bootloader (I'm pretty sure at some point I also had twrp, and again, may have been prior to US998/Oreo flash... order).
Because of network problems flashed H931 Oreo, 2 years stable.
Current problem:
Flashed US998 Oreo from here: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Tried flashing US998 PIE from here: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
In LGUP instead of refurbish I clicked partition dl.
Phone was stuck in bootloop. I tried the button dance to Master reset, worked, however the erased system wasn't able to boot before anyway, how would this help I don't know. The bootloop stays.
Hoped to reach familiar Download mode, but couldn't even power the phone off (in no way from across the forum). Opened the phone, disconnected the battery - it's off. Tried to enter download mode... doesn't work. At least it charges. Tried to boot, entered bootloop again, master reset, bootloop again, disconnect battery.
Found this: https://forum.xda-developers.com/lg-v30/help/download-mode-doesnt-anymore-t3973801 , which leads to a possible solution here: https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-us998-30b-twrp-t3973811
I searched the comments, apparent solution was entering master reset menu and clicking yes in the dialog menus, which should start TWRP. I guess I don't have TWRP, because this does nothing much. A screen saying erasing appears, then goes to the same bootloop.
Bootloop, Download mode doesn't work, cannot acces TWRP. (soft brick)
Found no previous solution to work. (possibly couldn't find it)
Is there any help for me? Should I start looking for something less LG?
Click to expand...
Click to collapse
Are you having "Now waiting for any connection ..." error in download mode
Thanks guys, I get it now. I'll have to re-learn adb and fastboot, that's no problem I hope. I haven't had time to do it yet, I'll update later.
Are you having "Now waiting for any connection ..." error in download mode
Click to expand...
Click to collapse
I don't have download mode at all, I only have 2 different screens - bootloop (V30/unlocked bootloader logo) or charging screen. I cannot access download mode.
MarcRossi said:
Thanks guys, I get it now. I'll have to re-learn adb and fastboot, that's no problem I hope. I haven't had time to do it yet, I'll update later.
I don't have download mode at all, I only have 2 different screens - bootloop (V30/unlocked bootloader logo) or charging screen. I cannot access download mode.
Click to expand...
Click to collapse
If you can go to twrp recovery, you can go to reinstall the partition
If brick is black then try qualcom 9008 mode to rewrite the partition (I used to succeed this way)
thao12345 said:
have you fixed it? Have you unlocked your device's bootloader yet?
If you have unlocked the bootloader then flash the laf.img file
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
If you want to update android 9 us998, please kdz via ROM h93030b to install twrp, then flash us99830b.zip via twrp
give it a try
Click to expand...
Click to collapse
Yes, you are absolutely right, it works!
Thanks
Redy321 said:
Yes, you are absolutely right, it works!
Thanks
Click to expand...
Click to collapse
Could you tell us a bit more about what you did? Which model V30 do you have? How did you lose download mode? And what steps did you take to repair it?
I'll be honest, I ask because having seen your many posts in various threads here recently, all very similar to the one you posted here -- sharing no real information -- I think you're most likely a bot, trying to build post count before dropping a spam payload.
That is presumptuous on my part and I may be wrong. If so I apologize deeply and will update this post after seeing your response.
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