Related
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
Abandoned War Place said:
FIX REFUBRISH/DOWNGRADE ETC STUCK AT 16% DOWNLOAD MODE UNABLE TO GET BACK TO STOCK
error 0x2000 invalid command response Has Been FixeD WITH THE LASTEST DLL FILE
FILE INCLUDE (DLL+PATCH_DLL+SETUP LGUP+DRIVER) package
Please Read The *READ ME FILE FOR THE RIGHT INSTALLATION WITHOUT GETTING ANY PROBLEM :
Link Easy To Download No Ads Bulllsh*t.................. :
https://drive.google.com/file/d/0B_yWw6RLoA-gdTMtZFczMUhQOHM/view?usp=sharing
Click to expand...
Click to collapse
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBzib...230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
Click to expand...
Click to collapse
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
jam1445 said:
3. One the Write Completes. Eject Card and insert in your LG G4 H811. Press Volume Up Button while connecting the USB Cable.
4. There you go, it will open the download mode.
Click to expand...
Click to collapse
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Good job. If your using this and you're gonna buy a SDCard on purpose, be aware that this fix might not work on your device. Ehehe
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
inso420 said:
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
Click to expand...
Click to collapse
are these what you looking for.?
https://forum.xda-developers.com/showpost.php?p=73586554&postcount=921
VS986 Stuck on Download Mode
Jirrick said:
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Click to expand...
Click to collapse
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
inteLzzz said:
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
Click to expand...
Click to collapse
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Jirrick said:
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Click to expand...
Click to collapse
No could it be caused by low battery? I remember it being like 30% when I bricked it, and does it charge under 9008 mode?
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Jirrick said:
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Click to expand...
Click to collapse
It does not bootloop, straight up dead. Just shows 9008 forever on the pc, I left it for like 2 hours like that yesterday. I'll leave it overnight today and if not I'll hack up a direct 5v 1a charger to charge the battery directly. If both don't work i'll probably flash LS991 files in QFIL and use it as a tablet afterwards.. damn i got this phone not even 2 weeks ago perfect condition and all. Will not buy any more damn LG devices.
Oh, I thought your phone was rapidly bootlooping like mine did. Sounds like the person who sold it to you was aware that the phone is on last legs (probably even baked the phone so it runs for few days more) and screwed you over. My next phone wont be LG either.
Hello,
I tried to install TWRP unsuccessfully on my D852. In the process, I removed my laf.img. The strange thing is that I see two files on my phone, one in the internal storage size 16.5MB and one on the SDcard size 32MB. How do I know which one to install? Is there a difference between them? If I install the wrong one, will my phone still work?
I am running the Telus Lollipop 5.0.1 from storagecow, if this could help you giving me the right answer.
Thank you,
Update - I was able to extract laf_393216.bin from the Telus KDZ (TELUS D85220F_00.kdz) I installed on my phone. The size of this file is 19MB.
What do I do with a BIN file? How to I install it on the phone?
Thank you,
Hello, me, again,
I can't believe no one knows how to do this. Please help! I can't do anything on my phone, luckily it still boots to LP 5.0.1.
laf.img was removed using ADB. I backed it up before removing it and now I can't seem to be able to restore it because the phone doesn't go to download mode.
It was very easy to remove and I can't find a way or someone to help me restore it...
I tried to enter Download Mode by powering the phone off, pressing Vol+ and plugging USB cable.
I get a black screen with the following:
[500] Fastboot mode started
[590] -Reset-
[590 -Portcharge-
[710] Fastboot: processing commands
Anyone knows how to get into download mode from here?
Thank you,
U must restore your phone from 9008 Qualcomm DLoad.
Update - I was able to restore my laf.img and boot.img using adb.
After that, I got download mode working and was able to complete flashing original Rogers MM on my phone. Perfect!!!
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
BigBadSheep said:
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
Click to expand...
Click to collapse
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Absolute Territory said:
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Click to expand...
Click to collapse
Thanks, but already did that.
I end up extracting img files from the TOT file and sending them to the phone using the dd command.
And I dd-ed every single file (36 files per total) but with no use.
Tried with TWRP recovery and with stock recovery...nada!
It must be the jumpy connection. I will try again someday later on.
Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Jimmynidas said:
Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Click to expand...
Click to collapse
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
AsItLies said:
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
Click to expand...
Click to collapse
As of right now I have a kdz for my phone, I have a Verizon model. Where I'm having trouble with now is I can't get the phone into Download mode. When I do it says my device failed a routine safety check and then boots to fastboot mode.
I also have a couple patched magisk boot partitions from the initial install. I loaded them via QFIL and I can now get to the Verizon bootup screen, but it gets stuck in a loop.
Update:
I got into Download mode by going into the system recovery and doing a factory reset. Now I need to figure out LG UP.
Last Update (Hopefully) Lol:
I installed the kdz using LGUP and it seems to have worked! I'm back in the stock OS and touch input is working. I'm relieved. I hate leaving things like this in a broken state if it's possible to fix it.
Thank you @AsItLies for responding and helping out!
Pukkaras said:
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Click to expand...
Click to collapse
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Woo, thats great, that you resolve your problem! I will try to do all like in your manual.
imei.guru said, that for my imei i have :
Model: LGABCD
Region: ABC
LG LMG820N
With such region i did not find kdz at lg-firmwares.com
When my smartphone boot up (when it was worked) i see LG U+ when booting.
Also it was trying to set korean language. What do you think, which kdz should I take? And what version of android?
also solved my problems - here i described here how https://forum.xda-developers.com/t/...lg-g8-alphaplus-alphalm.4354847/post-86038237
Jimmynidas said:
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Click to expand...
Click to collapse
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
indrajyoti_indra said:
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
Click to expand...
Click to collapse
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Jimmynidas said:
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Click to expand...
Click to collapse
I find out that Windows 11 is the problem. Something to do with stupid driver signature. Used Windows 10 and that worked. Thanks.