LG G4 H815 Download Mode reboots after ~10 seconds - G4 Q&A, Help & Troubleshooting

Hello, first of all I want to apologise if this problem was already discussed, I tried searching in threads and also using the old friend google, but found nothing related.
So, yesterday, I managed to flash the a.o.s.c.p cypher OS (https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102), Oreo version, and after I tried rooting with Magisk I've got bootloop issues with the rom. After this, I reinstalled the zip file and it managed to go back to the OS, but every installed app would crash when tried to open. Because I did not find my backups (not too organised, I know) I tried flashing through LG UP the "LGH815 EU Nougat 7.0 BySezerSimsek.tot" file I had downloaded on my laptop, unfortunatelly, after 10~ seconds, the download mode just restarted and since then (though, it was doing this before I tried to flash with LG Up, but I thought that after I start flashing it will not reboot...), everytime I try to boot my device either normal or to recovery mode, it goes automatically to download mode, where it stays for 10 seconds and then reboots (So I'm not able anymore to use LG UP).
Also, tried LGMobile Support tool, but because I cannot keep the phone in download mode more than 10 seconds, it fails to do anything, it finished to download a firmware for it, but was unable to flash it.
Is there any chance I can "revive" it? the battery was about 50% when I started the first try with download mode, so now, it should be around 20-30% I guess.
In Download Mode, in the box, it says:
633A B49
Modified
P.S.1: After reading some more threads, I found that some people were stuck at 9% while flashing with lg up, but for me, as I said before, the download mode just keeps restarting no matter what I do with it ( even if I just leave it not connected to the pc)
P.S.2: After some more flashing with LGUP tries, I came to conclusion that the download mode restarts after ~17 seconds, and now, in the rectangle it says:
633A B56
Modified
P.S.3: I have been trying to flash "Europe H81520D_00_0115.kdz" and sometimes, if I get the timings right, I can get up to 25% (it restarts at 9%, ~19% and then 24-25%, so, it doesn't always give error after restarting and reconnecting to LG UP). I used the .dll extracted from .kdz file.

Hello, i have the exact same problem as yours with the same custom rom.
My phone stays around 20 seconds in download mode, i can launch LG UP to flash H81520i but 20 seconds is just not enough to flash the LG G4 firmware AFAIK.
I did see that there are some ways to launch the Qualcomm emergency mode but we'll need to disassemble the phone to short two pins to force it to boot in this mode.

I finally found the solution ! Follow this tutorial : https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212 You'll need to disassemble the phone in order to do this tutorial, after you've done the emmc flash you will need to reflash a rom with LGUP.

Nopraz said:
I finally found the solution ! Follow this tutorial : https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212 You'll need to disassemble the phone in order to do this tutorial, after you've done the emmc flash you will need to reflash a rom with LGUP.
Click to expand...
Click to collapse
Thank you for the reply.
I already fix my G4, but unfortunatelly I do not have like a detailed fix because: I went to a "Phone repair shop" and I left my phone there for one day. As I said, before I was not able to boot into recovery, the phone was restarting in download mode after ~17 seconds, and I had no idea about the battery percentage.
The next day I took back the phone and the guy there told me that there was not much he could do, but when I got home, the moment I tried to boot it, it went to recovery mode (twrp) where I tried to install a ROM (I forgot which one, but it was a .zip) and it failed to mount /cache. After that, I tried booting into download mode where it stayed for as long time as I needed without restarting. I was trying to flash 20D version (failed at 25% everytime) until I found this thread where the advice was to use the 20P version. After that it just worked fine.
So, I have no idea what did the guy from the "repair shop", I don't now if it was just related to my battery "running out of juice" or maybe he used any other "magic" box with tools for android smartphones (I've got back my phone with ~60% battery).
Also, before I went to the repair shop, I tried a method I found on xda, unfortunately I could not find the link right now, where I had to format a micro sd card and kind of "flash" (it's not actually flashing) a file to the SD card, put it inside the phone and just boot into Download mode (I'm not sure if it affected somehow the state of my phone)

Related

Need help. Flashed incorrect rom on my Vk810.

Im not that experienced but have been playing around trying to learn about roms etc. I used the flashify app to flash a rom but accidentally used the wrong rom. I grabbed the one for the v500 model instad of vk810. Needless to say it messed up. When the tablet boots it stays on the boot image for several minutes then it will attemp to update apps but gets stuck there. I have tried many fixes. The LG mobile tool doesnt work. I try to update recovery. It downloads the update but wont install. I cant force the tablet into recovery with button pushes. I have been able to put the tablet into twrp 2.7.8.1 recovery with droid explorer. From there I have tried to flash about 3 different roms that all say they should work for the vk810 but i get errors with all of them and they fail. Im not sure if there is any hope to get the tablet working again but hope someone can help.
First, I don't think you can use Flashify to flash a whole ROM at all. Definitely not recommended, even if it's is supposed to be capable of doing that. I haven't tested flashing ROMs with it so no idea if it can work or not.
Can you put it in Download mode? If so, install the Verizon LG drivers, reboot the PC and try LG Flash Tool 2014 with the 11A KDZ, you can get the KDZ from the link in my signature. It's easiest to root and put TWRP back on that old stock ROM.
FYI it would have to be in Download mode for the mobile tool to work - just in case you didn't know or didn't have it in Download mode. LG Flash Tool 2014 does the same thing as the mobile tool except the mobile tool re-downloads the newest KDZ every time you try it unless you hack it. It's much easier just downloading the KDZ separately and keeping it on file for times like this to flash with LG Flash Tool 2014.
Just remember, if you use LG Flash Tool 2014, ignore any error it throws at you. Just drag the dialog boxes out of your way, don't press any buttons in error dialogs. 99% of the time, if you just ignore them within 10-20 minutes it'll have successfully flashed your VK810 anyway.
Also, once you install the drivers and reboot, put your original USB cable that came with the VK810 into a USB 2.0 port on the PC, with the tablet completely off, hold the Up Volume button in, connect the tablet end of the USB cable and keep the Up Volume button pressed for another second or two, and you should see a very dim "Download Mode" graphic in the center of the screen. It's very hard to see. The first time you connect the tablet in Download mode to a different USB 2.0 port or Windows installation, it can take up to 10 minutes to actually load the driver you previously installed. Look in Device Manager under the Modem section to see when the driver is fully loaded by looking for the LG device entry there.
Question: I assume you mean TWRP v2.8.7.1, but I was just wondering where you found 2.8.7.1? I've only found 2.8.7.0, not that it's a big deal.

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?

LG G4 H815 Euro - Troubles flashing stock ROM

Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
FamousCarpet said:
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
Click to expand...
Click to collapse
uninstall any drive for g4 from pc and reinstall again and lgup. now reboot phone to download mode when lgup is open first check upgrade opsion and when open kdz check refurbish opsion and start. good luck
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
The best way to flash stock image is to use official LG Bridge app. Download it, turn off your phone, connect it to PC while holding volume up button - phone will go into download mode. Then there is option for software restore in LG Bridge but i won't tell u where exactly. If it won't work i would try on another PC. If it won't work maybe you would be able to flash stock image trough send_command but i won't help you with it.
FamousCarpet said:
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
Click to expand...
Click to collapse
open lgup torn off the phone press volume up insert usb cable wait to see download mode on phone release up button and see if everything go fine
Thank you a lot Avantu, the LG Bridge did the trick! I now have a factory rom!

I Bricked and Unbricked my day one V30 in one night (How to not be completly screwed)

I picked up my UK V30 H930 yesterday all fine and saw that LG have unlocked the bootloader on my model so I went ahead and tried it along with trying the alpha TWRP build
So I thought id write about what went wrong and how I recovered from it.
I made the mistake of letting the phone auto update to 10v software verion before I did this. As I had 10f on before when I bought the phone.
I went to load in all the software needed to unlock the bootloader and proceeded to do so but in my haste of the user data being wiped taking a longer then I thought it would I unpluged the phone to try "fastboot flash unlock unlock.bin" again . No such luck already unlocked. It booted back in fine so I thought everything was ok but that was the moment I thought could have caused my entire night to be ruined.
I thought with the bootloader saying it was unlock it was now fine to flash TWRP on now so went to do that and discovered it would no longer boot into the rom anymore coming up with the LG V30 Logo and just staying put. Thought it must be my 10v software version messing it up. Ok ill try to flash a 10f stock kdz. After about an hour or so of 'Finding my feet' with the phones boot methods for download mode, Fastboot and recovery I found that twrp was being strange with mounting the phone tried otherways eventually got the phone talking to the pc by using uppercut with LGUP and having the phone in download mode and the port com channel in device mananger set to com 41. After about 4 tries of flashing KDZ's to the phone it would just come with a "erasing" circle and proceed to get stuck on boot logo again so I messed about with .dlls and tried to other methods. Still nothing.
Now I tried LG Bridge's "Update error recovery" and I was actually talking to the phone for the 1st time so i let it do its thing which took well over an hour to download the kdz file. "Fine just work please". it got to the updating stage at 5% and froze and the phone being in download mode hadnt done a thing. I tried again but still nothing. Eventually now at 6am and having been up all night I went to give up but I manged to get it on to fastboot mode and by chance came across "flashing lock_bootloader" tried and it and it locked tthe bootloader back up (this thing of LG saying it cannot be undone must be rubbish?) now before I tried anything I rebooted the phone . IT BOOTED! onto the fresh 10v KDZ i had installed on it but before anything I wanted to see if it would now run with a unlocked bootloader on its own with no TWRP installed. It works! Now i just need a method of rooting but im now ready at least.
Hope this helps anyone with simular troubles.
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen ?
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
SGCMarkus said:
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
Click to expand...
Click to collapse
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Dreamxtreme said:
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Click to expand...
Click to collapse
nope, doesnt have one. Neither windows nor Linux fail at writing on it, or when deleting files, but as soon as I re-insert the SDCard all changes are reversed. Formatting doesnt work anymore, unknown error. Tried that in Windows, Linux and in the Phone (Androids formatting crashed, TWRPs produced an error after it timed out)

[HELP] Can boot into download mode/hard reset, but not ROM.

To preface, I can boot into download mode and access hard reset but cannot boot into the ROM as it just shows the "Broken Android" symbol
I've been trying a lot of steps.... So many guides... To fix my phone. I've chalked it up to an issue with my IMEI/ESF being corrupted as LG Flash Tool shows it as NULL" and fails after 3 seconds consistently. LG UP also fails at 6% spitting out generic errors. I've even tried LGMobile Support Tool and it downloaded the correct firmware but failed to apply it at 2% consistently.
I'm assuming this has to do with my ESF being corrupted. I've been looking up guides on how to "fix" it but keep coming up short as ALL of them require a back up or at least being able to boot into a ROM. However, no ROM will flash. The bootloader is locked and the device has no root options. At this point I'm drawing a blank. I've been going at this for 11 hours straight (no joke, been sitting here for 11 hours searching the forums for different fixes because I know how people feel about the same thing popping up repeatedly.
What caused this issue was trying to roll back the firmware to an earlier version using LGUP so I could unlock the bootloader. I've only been attempting with stock roms (both KDZ and TOT)
Any help would be appreciated.
The phone is still detected in DLMode and all the programs can find it and know it's a D852 but just wont take any firmware.

Categories

Resources