Develop Bugs

LS908 Bricked, heen help!

Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.

Can you enter recovery?
Sent from my LG-LS980 using XDA Premium 4 mobile app

Ouch bud you are hard bricked pretty much. It sounds to me from what you explained all the partitions are wiped clean. I don't think there is any recovery from that unless you have a nand programmer
Sent from my LG-LS980 using xda app-developers app

brockzilla said:
Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.
Click to expand...
Click to collapse
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.

abhinav.tella said:
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.
Click to expand...
Click to collapse
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.

brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.

brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
abhinav.tella said:
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.
Click to expand...
Click to collapse
from what he said it sounds like a hard brick

Damn, not even fastboot? Feel sorry for you.

[Q] Problems Unrooting T-Mobile G3 by LGFlashTool

Hey guys, fairly new user here. Prepare for rambling explanation, skip a paragraph if you don't care but the background info may be useful
Had some issues twice in the past 4 months, had to send in the phone and get a replacement (thank God for JUMP insurance) ; I used purpledrake to root my G3 shortly after it was released, it is my first Android device and I had a lot of experience with jailbreaking and unbricking iPhones so I thought I could handle it. After rooting I didn't go crazy, mostly cosmetic changes and preset apps like G3Tweakbox, I stopped google services from running because I couldn't find another way to get rid of the OTA notification. Less than a month after I did it, I was starting to have issues that I read were fixed by the OTA update, so I went online and found the process to unroot so I could update, then re-root once it was possible. Ended up getting stuck in the download mode screen and the phone wasn't even recognized by the LGFlashTool as being in DL mode. Spent a good 16 hours playing with it, gave up, hard factory reset and convinced T-Mobile that I'm a helpless college student and my phone broke. Got a new one, rooted and didn't bother. Now, stupidly, I assumed I had just made a silly mistake along the way and decided to try again o Monday, day before my birthday. Same thing happens. Send it in, got another today. I'm kinda frustrated because I really want to root it and get things looking the way I want to again, but I want to make sure I can unroot it properly if need be. I don't think I'd be interested in using custom roms just yet, maybe if I get an older device to play with and experiment. I just want root access for file management and minor visual/technical changes.
TL;DR
-Rooted using PurpleDrake : http://forum.xda-developers.com/tmobile-lg-g3/development/root-twrp-root-twrp-tmo-lg-g3-t2821005
-Phone was having issues, wanted to unroot/restore/reroot, followed this to the letter : http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
-Phone got stuck in DL mode. Sent it in, got another. I want to root again but not until someone can figure out what I did wrong or what went wrong and I know exactly what to do to be able to unroot properly.

It could be your usb is disconnecting mid flash. Just to be safe you shouldn't use that pc for flashing tots or kdzs again. On the same note if you install TWRP you can use the linked guide to unroot/reinstall/downgrade/upgrade with root via twrp. Almost no risk of hard bricking if you used supplied files and guide. The only thing that could hard brick you in the twrp method is the rpm partition but that most likely wont happen, almost can't happen unless you loose battery power at the time it flashes the rpm partition. The tot and kdz method have about 20 partitions that could hard brick you. Http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667

ThePagel said:
It could be your usb is disconnecting mid flash. Just to be safe you shouldn't use that pc for flashing tots or kdzs again. On the same note if you install TWRP you can use the linked guide to unroot/reinstall/downgrade/upgrade with root via twrp. Almost no risk of hard bricking if you used supplied files and guide. The only thing that could hard brick you in the twrp method is the rpm partition but that most likely wont happen, almost can't happen unless you loose battery power at the time it flashes the rpm partition. The tot and kdz method have about 20 partitions that could hard brick you. Http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
Okay, thank you Page, I'll do some research with what you linked before I try anything again. Guess it would be a good idea to learn my way around the twrp, seems like the best custom recovery for the G3

Can I use the VS986 root method for my AS986?

Has anyone rooted a model AS986? I cant seem to find any information on rooting and AS986, from what I've gathered its close the the VS986 but I don't want to brick my device.

scarda said:
Has anyone rooted a model AS986? I cant seem to find any information on rooting and AS986, from what I've gathered its close the the VS986 but I don't want to brick my device.
Click to expand...
Click to collapse
Don't do it. I have the AS986 version too and it will not work. What happens is that it will boot, then quickly for about two seconds flash a warning that says LG Security Issue or something like that, and then you will see the Verizon boot animation. Then, about a minute later it just randomly shuts off. It will do this every time you try to boot the phone. Luckily, before I did this root procedure, I created a backup image and just flashed that the same way I did the root method and my phone was back to normal. Still no root though.

SysPA1N1C said:
Don't do it. I have the AS986 version too and it will not work. What happens is that it will boot, then quickly for about two seconds flash a warning that says LG Security Issue or something like that, and then you will see the Verizon boot animation. Then, about a minute later it just randomly shuts off. It will do this every time you try to boot the phone. Luckily, before I did this root procedure, I created a backup image and just flashed that the same way I did the root method and my phone was back to normal. Still no root though.
Click to expand...
Click to collapse
Do you still have that back up? I just bricked mine being stubborn and need a backup img

SLLogan said:
Do you still have that back up? I just bricked mine being stubborn and need a backup img
Click to expand...
Click to collapse
I do still have the backup but I'm not sure if it would work or not. I'm not sure (you probably can) if you can transfer files using download mode or Send_Command Mode. The file is also 4.18GB so I'll provide a link when I do get this uploaded. But if all else fails this is what I did when one of my backups didn't work (I have the AS986 Version by the way): MAKE SURE YOU HAVE THE AS986 OR THE VS986 BEFORE DOING THIS. I'M ALSO NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE.
When you messed yours up, were you on 11a or 10b? If you were on 11a, go ahead and try this. If you were on 10b, I'm not sure what to do. Sorry.
1. You should use this guide: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
2. When you go to download the KDZ you'll notice that the AS986 KDZ isn't there. Just download the VS98611a KDZ. It's close enough.
3. Follow the guide that I gave you in step 1.
4. You should bootup like nothing happened.
Somethings may be different because you flashed a Verizon KDZ but at least you have your phone back right?
This worked for me but it may be different for you.
MAKE SURE YOU HAVE THE AS986 OR THE VS986 BEFORE DOING THIS. I'M ALSO NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE.
If you need more help or clarification, just let me know.
Hope I Helped!
Also, as a side note, stay away from the Verizon Updater. It hard bricked my G4. (I sent it in for repair already) So just resort to the safe LG Bridge Updater.

I rooted an AS986 the other day by injecting the phone's system image with root on Linux, and flashed in download mode. Did not use the Verizon image or KDZ.

shoes22 said:
I rooted an AS986 the other day by injecting the phone's system image with root on Linux, and flashed in download mode. Did not use the Verizon image or KDZ.
Click to expand...
Click to collapse
That's what I did too.

Phone no longer bricked (yay!), but not fastboot

The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image

yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..

sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?

kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/

mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?

New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?

kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717

mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.

kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?

Bricked LG G8 after flashing ARROW OS & TWRP

Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!

JuSkoch said:
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
Click to expand...
Click to collapse
Sounds like you might just need to reverse what you did to try to get twrp. If you have the boot partition for Arrow flash that back, if you don't have it should be pretty easy to get it from someone.
If that doesn't work can always use qfil and flash the necessary partitions to get LGUP to work, then flash or crossflash to a kdz and start again with stock.

You're in good company. I went down the same path and have become adept at repeatedly bricking and un-bricking my G8. (LM-G820QM5) I picked up 2 tidbits of info that have been helpful. The first is that my G8 ThinQ will not boot Android when the engineering abl_a.bin has been flashed on to it to enable fastboot. Sure it will fastboot, and go into EDL or download mode, but in order to boot the OS, I have to put the normal abl_a.bin and abl_b.bin back.
The second lesson I learned the hard way is that sometime LGUP fails to flash when the phone is in download mode. I was searching around XDA and came across a very helpful post from starlyn1232. They posted a command line utility that has been successful in un-bricking my G8 when LGUP failed.
I downloaded the appropriate kdz from lg-firmwares.com and the starlyn1232's utility from https://forum.xda-developers.com/t/lgup-flash-utility-based-on-lgup-1-16-cmd-and-lgup-1-17-lgup_common-dll.4112121/

Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!

JuSkoch said:
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
Click to expand...
Click to collapse
I would highly recommend looking at bkerler edl utilities. You can easily find his git page which has the download option for an iso linux boot which has everything installed.
It's a bit involved / complicated figuring out the command line interface, but once done you can backup everything and it will create the xml files needed to reload it.
I would suggest this for everyone but especially for those with sprint or att devices, as there is no kdz available for them.
I've recovered from various issues too many times to count with backups I've made for v40, v35, and now G8 (2 of them).
cheers

Could you pass the tutorial on how to install TWRP?

Does anyone have rawprogram0.xml
Patch0.xml for lg g8

Ashfaq Ahmed spsc said:
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Click to expand...
Click to collapse
So the rawprogram xml will be for ea lun, and it will vary by which rom you're trying to flash, it will also vary by segment starting positions for the partitions. IE, there is no generic version of it.
2nd, you don't need a patch xml, just click cancel or skip for that entry. Note; the rawprogram xml is usually generated when a backup of the binaries is made, and it will be for that specific backup.

Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.

MR_ZenR0 said:
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
Click to expand...
Click to collapse
Hello, I Managed to Fix it by loading my backed-up original boot_a.bin and boot_b.bin using QFIL, I have successfully passed that Verizon logo now and should be able to go from here, not that anybody asked, I just thought someone in the future might have some use out of this information here. so if you are from the future and you read this, you are welcome and good luck