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
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
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.
In August, I bought this tablet, Lenovo TAB M10 (TB-X505F), to read and study for University. I rooted the device with Magisk. I also bought a 64 GB SD Card, which I installed and configured to expand the internal memory. About a month later, an OTA update failed to install; I removed the SD card, the OTA installed and the tablet went back to factory defaults; not pleasant, but not terrible. I reconfigured it, and kept using it.
Last couple of weeks, a new OTA was released. it tried to install a few times, and failed; just rebooted the OS with a generic failure message. One morning, it tried to update during the night, and I found it on the Recovery menu; a generic error message said it couldn't update. The OTA tried to update some more times, rebooting to the OS or going to the Recovery screen.
Yesterday, I removed the SD card and tried to install the OTA update; it failed, and sent the tablet again to factory defaults. Something happened, I can't tell what it was, and now the tablet is screwed. It won't boot; it won't go to recovery. I have no ADB, but I have Fastboot.
I worked with tablets and phones many times before: recovering, rooting, flashing, upgrading, downgrading, unlocking, unbricking, etc. I have the original ROM, and also the latest. I have the original boot.img, and the modified by Magisk. I tried to fastboot flash boot, recovery, and TWRP; it flashes "OK", but nothing happens: it won't boot to recovery. I tried to fastboot flash system, but it didn't do anything. This is a "system_1.img", "system_2.img", "system_n.img", not a ".sparsechunk"; I never had to deal with this one, I might be doing something wrong. I tried to fastboot flashall; nothing seems to work, although it looks like it is flashing ok. I don't know what to do or try anymore. Any help will be greatly appreciated. NB: I'm in Linux; I'll prepare a Windows box, in case it is needed.
Thank you very much. Best regards.
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
jwoegerbauer said:
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
Click to expand...
Click to collapse
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your response. I'm assuming is a Windows tool... I'm finishing setting up a Windows box to test; I'll take a look at it as soon as I have it; I'll test it and post the results.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
jwoegerbauer said:
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
Click to expand...
Click to collapse
Because I didn't have adb, only fastboot.
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
THIS THING WORKED LIKE MAGIC! THANK YOU VERY MUCH!
It was more difficult to set up the Windows box to make it work, than the rescuing of the tablet with this tool. A few clicks, wait for the image to download, follow some easy and clear instructions, and my device is alive, again. I feel I can't thank you enough.
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