Database Users

Serious issue

i urgently need help
I got some update from lg and after i agreed to install
phone doesn't boot
it goes into TWRP recovery
i tried putting it on download mode but its not happening
I tried hard resetting too
i deleted data and hence i dont have any files on my internal storage
I dont have a OTG cable .
pls help me out
i cant use terminal command also because there are no files in recovery folder

digkong said:
i urgently need help
I got some update from lg and after i agreed to install
phone doesn't boot
it goes into TWRP recovery
i tried putting it on download mode but its not happening
I tried hard resetting too
i deleted data and hence i dont have any files on my internal storage
I dont have a OTG cable .
pls help me out
i cant use terminal command also because there are no files in recovery folder
Click to expand...
Click to collapse
whether you can get into recovery and give you the download mode?Do you sec when starting up the phone LG logo?
Open LG supotr tool, connect your phone in download mode the tool detects the phone click on the option (top right corner) select upgrade recovery. PC will begin to download your original SW. wait and let the tool after the download and install SW (about 1 hour)
-installed drivers needed
-charged battery (90-100%)

Keep calm, pal !
Boot in TWRP, then "Advanced", then "Terminal Command" !
COPY THE FOLLOWING LINE VERY CAREFULLY : NO MISTAKE ALLOWED !
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then reboot, it should work !
And remember : NO update from LG via OTA when rooted on the G2 !

rohecla said:
And remember : NEVER take OTA update when rooted on any phone!
Click to expand...
Click to collapse
Fixed.

[Q] Stuck in bootloop after Kitkat update

Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?

Parinibbana said:
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Click to expand...
Click to collapse
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).

Phoost said:
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Click to expand...
Click to collapse
Thanks for the hint, but in fact I did not forget about it. I did replace the original one.

Parinibbana said:
Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Click to expand...
Click to collapse
Give this a try. It sounds like it will help.
http://forum.xda-developers.com/showthread.php?t=2582142

Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.

Stuck in bootloop but can push files using adb-commands
I would like to add, that I can push files to the device over adb when I am inside CWM-recovery. I can even flash ROMs, but all that doesn´t help, since afterwards I will still be in bootloop.
If I knew which files are corrupted causing the device not to get beyond the LG-bootlogo, then I could replace the corrupted files over adb.
Any ideas?

Parinibbana said:
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Click to expand...
Click to collapse
I would try to use the method i suggested to restore your Download mode, I can confirm that it will work. Then use download mode to flash the factory *.kdz or *.tot file to your device via the LG recovery tool. I'm not an expert at this, but i think you should focus on getting download mode working, then you can restore your phone to stock fixing whatever partition is broken and keeping your phone from booting. This will get your phone back to a factory stock and booting condition, then work on modding it to the way you want.
As a side note If TWRP is not available for your device i would assume you could just substitute CWM in its place. This really doesn't matter if your only trying to get to download mode to restore your phone.

Have you tried ADB Sideload?

MK45A said:
Have you tried ADB Sideload?
Click to expand...
Click to collapse
No, what is it? How would ADB sideload help in my situation?
Do I even need it, since I can flash any ROM successfully from within normal CWM-mode and have full access to adb-commands from within CWM. But whatever ROM I flash, afterwards I am still stuck in bootloop.
How could sideload help with that?

Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
In CWM, look for something like 'ADB Sideload' and then enable it.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
ADB sideload lets you push roms from your pc using command prompts to your phone.
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Have you tried out LG FlashTool?

MK45A said:
Have you tried out LG FlashTool?
Click to expand...
Click to collapse
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?

Parinibbana said:
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Click to expand...
Click to collapse
Can you write down the whole error or provide screenshots?

MK45A said:
ADB sideload lets you push roms from your pc using command prompts to your phone.
Click to expand...
Click to collapse
I see. This means, I don´t need to push the zip file to /sdcard/ beforehand, but can flash it directly from the laptop, right?

Here is a screenshot.

Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?

Parinibbana said:
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Click to expand...
Click to collapse
Today I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted.

Finally unbricked my phone.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.

Parinibbana said:
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/show....php?t=2451696
Click to expand...
Click to collapse
Interesting. Thanks for the feedback.

Download minimalabd https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Run this in adb
copy and past
adb shell
and also
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
and also past on cmd
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
This fixed my phone
NP

[Q] [HELP][LG L5 E610V][CWM] Impossible to boot into CWM

Hi there,
this is my first post bu I have been playing with my LG L5 e610v for long time. I have had installed CyanogenMod 10.1, 10.2 and 11.
This last time, I came back to the stock rom and now is impossible for me to boot into CWM.
I have tried:
Installing a KDZ with a rooted stock rom with CWM
Copying using adb and dd command many differents CWM images (6.0.28, 6.0.4.7)
Using rommanager app
but always the result is the same: I boot to recovery and it gets stuck in the LG logo. I have to switch off and switch on again and the stock ROM starts again, but no way to boot CWM.
I have tried even overwritting emmc_appsboot.img, but no results.
Please, could you help me? I need CWM for installing CyanogenMod again.

try this,extract cwm and copy the image file to your internal sd card,open terminal emulator and type following line
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17
than enter
after this type reboot recovery and your phone reboots to it

It worked!! But I cannot understand... why it works using the terminal emulator and not using adb??
Thank you very much!

maybe anything was wrong with installer script or something,glad to see its solved.greeetz

I really dont understand. copying the img using dd works only 1 time. The second time, If I tried to boot (using key combination or writing reboot recovery in the terminal emulator) it gets stuck again in the LG logo. I have to copy again the image for start CWM again...
Any ideas why this is happening?

have u tested with format system before flash cwm,maybe there is a weird rest from an programm or something which blocked,but i never have see it?

After a hundreds of removes and installations, formatting and everything now is working fine. I cannot say what solved the problem, but definitely using terminal emulator was a huge step hehe
thanks!

great,now you can start to flash custom roms,the journey begins........

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

Always booting to TWRP

I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.

If you still have twrp just flash stock from there.

basicreece said:
If you still have twrp just flash stock from there.
Click to expand...
Click to collapse
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.

I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2

ahk31 said:
I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2
Click to expand...
Click to collapse
Thanks for pointing out that thread!
I downloaded the bootloader and succesfully installed it using `adb sideload LG-H87010f-Flashable.Bootloader.zip`
But the phone still only boots to TWRP.
So I tried to flash a complete stock rom from https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-10t-rom-t3654134
I did wipe Dalvik/ART, Cache, System and Data and afterwards installed that rom.
Unfortunately these steps didn't make any difference to the boot sequence.
I've been trying again to get into the download mode using key combo's and using `adb reboot download` but it reboots to TWRP instead.
What should I try now?

I finally managed to enter download mode!
In the end I figured that I confused the key combo from my previous phone with this one.
I should only hold the volume up button and then plugin in the usb cable.
What I tried numerous times was a combo of volume up and power button.

for reference and people showing up here later. Doing lineage OTA updates on the G6 forces the device into that endless boot loop into recovery. You get out there by entering the shell in TWRP and dd'ing some zeros somewhere. I had it once but sadly did not write down how I solved it. Google for boot loop and twrp you will find hits here on xda where you see a dd if=/dev/zero line and explaining what todo. It is a bit different for each device, but the article tells you what to look for. As I understood it, writing some zeros at the start of a partition ends the loop, but I am no expert there, it just worked for me.
Oh yes, and stay away from lineage OTAs
Edit: ok, not xda but reddit, anyway here is the link
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
The life saving post is a comment further down by muniak
I'm using TWRP 3.1 and still had this issue.
Despite thinking my phone was rooted, I couldn't su, adb as root or anything, so I couldn't /fstab. I ended up looking around and comparing the path I was in with other's. So if you're having this problem just keep going around typing ls and pressing tab like below. Basically you're looking for "by-name/misc" in "/dev/block/platform/".
ls /dev/block ls /dev/block/platform ls /dev/block/platform/[dir or two] ls /dev/block/platform/[dir or two]/by-name ls /dev/block/platform/[dir or two]/by-name/misc
Then the dd if=/dev/zero of=/dev/block/platform/[dir or two]/by-name/misc count=1 bs=32
Good luck and thanks so much for the help!
Click to expand...
Click to collapse

ikbentomas said:
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.
Click to expand...
Click to collapse
Then flash the stock zip.....
If you had searched the forum you would see the stock zips and bootloaders all complied for twrp.

ikbentomas said:
I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.
Click to expand...
Click to collapse
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers

Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
I had the same problem, this command worked for me, thanks!

Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Worked for me too. Many thanks.

Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Thanks, your solution worked for me too

Same happend to me, there are some post that say you have to boot to bootloader and send bootloader continue command with your PC, however that didn't work for me. To flash with LG UP you have to have your phone off, connect USB cable to PC, press Vol+ on phone and connect the USB cable to the phone, it should start in a mode called download mode, then LG UP should find your device