Database Users

[Q] TMobile D801 Stuck in TWRP boot

Needing expert help. I have a rooted LG G2 D801 with a custom ROM installed. Was stupid enough to accept the most recent OTA and now it just continually goes into TWRP. Have tried to reinstall custom ROM from TWRP. Have tried the LG software to install the kdz file. Always gets stuck at step after extracting the kdz file. Even took it to a local guy and he got stuck in the same place.
I just want the phone back in working order. Don't care which ROM. Will pay $20 for anyone with the working answer.
Thx.

dba723 said:
Needing expert help. I have a rooted LG G2 D801 with a custom ROM installed. Was stupid enough to accept the most recent OTA and now it just continually goes into TWRP. Have tried to reinstall custom ROM from TWRP. Have tried the LG software to install the kdz file. Always gets stuck at step after extracting the kdz file. Even took it to a local guy and he got stuck in the same place.
I just want the phone back in working order. Don't care which ROM. Will pay $20 for anyone with the working answer.
Thx.
Click to expand...
Click to collapse
you can do a couple things. Sideload a new rom from your computer. Google how to setup the drivers and do it. OR from what Ive read you can delete the system partition like you are gonna flash a new rom then you wont get stuck when using the kdz to go back to stock.
Also look on the forums, I think you can run a command via shell in twrp to delete the fota dir and it should boot to. Dont quote me on that

dba723 said:
Needing expert help. I have a rooted LG G2 D801 with a custom ROM installed. Was stupid enough to accept the most recent OTA and now it just continually goes into TWRP. Have tried to reinstall custom ROM from TWRP. Have tried the LG software to install the kdz file. Always gets stuck at step after extracting the kdz file. Even took it to a local guy and he got stuck in the same place.
I just want the phone back in working order. Don't care which ROM. Will pay $20 for anyone with the working answer.
Thx.
Click to expand...
Click to collapse
if you can still get into the recovery you can try this http://forum.xda-developers.com/showthread.php?t=2451696
---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------
x714x said:
you can do a couple things. Sideload a new rom from your computer. Google how to setup the drivers and do it. OR from what Ive read you can delete the system partition like you are gonna flash a new rom then you wont get stuck when using the kdz to go back to stock.
Also look on the forums, I think you can run a command via shell in twrp to delete the fota dir and it should boot to. Dont quote me on that
Click to expand...
Click to collapse
that is correct http://forum.xda-developers.com/showthread.php?t=2451696

Thx all
Thx all. Will try out tonight.
XxZombiePikachu said:
if you can still get into the recovery you can try this http://forum.xda-developers.com/showthread.php?t=2451696
---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------
that is correct http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse

Tried to delete fota; no avail
Tried this method:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
That didn't help. Now trying to adb shell method from my computer.

dba723 said:
Tried this method:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
That didn't help. Now trying to adb shell method from my computer.
Click to expand...
Click to collapse
Did you write it correctly ? the code ? when you miss some space or something it wont work

Yes. It gave me a strange error about not enough space

Fixed....finally
Thanks for the pointers guys. The fix ended up being this from another post:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

dba723 said:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Dude, you are the best! Thank you so much. The /misc command fixed it for me!!

dba723 said:
Thanks for the pointers guys. The fix ended up being this from another post:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Woohoo.. Just saved me too. My kid accidentially hit the accept on an update when using a custom rom. Back to life now.
THANKS!!!!

[Q] Is it possible to repair my installation post official updating?

So I did a number on my phone in a half asleep stupor I allowed an official update to go through while running a custom recovery and debloated kitkat. I can't believe I did this to myself. Is there anyway to repair the installation other than wiping the phone again? It was one of those mini updates, but now I boot straight to recovery instead of the operating system.

I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.

I found an answer!
Gnex81 said:
I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.
Click to expand...
Click to collapse
I found the answer in another thread after an exhaustive search. Serious thanks goes out to the user 6ril1
6ril1 said:
Have you typed the two commands in TWRP
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
and
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
?
Click to expand...
Click to collapse
Here is the thread:
[FIX] Installed TWRP and now you're stuck after OTA?
So here is what you do:
1) Boot into recovery (TWRP)
2) Go to Advanced and then Terminal Command
3) VERY CAREFULLY TYPE IN EXACTLY THIS:
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" then RETURN
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc" then RETURN
Reboot and it should have fixed it up for you.

When Android Keep Booting Into TWRP Recovery

Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE

bhattyash32 said:
Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution:
Click to expand...
Click to collapse
Seems to happen a lot with people. Could others chime in on this solution?
Sent from my LGE LG-H830 using XDA Labs

Nick216ohio said:
Seems to happen a lot with people. Could others chime in on this solution?
Click to expand...
Click to collapse
I got my phone less than 24 hrs ago and have dealt with this the entire time. Not only do I get stuck in recovery but when I do use the terminal code to get out of it, I get stuck in reboots after any ROM installation. I have seen many users having both issues and find it hard to believe there hasn't been some kind of fix. I know not all are caused by the same thing but many I'm sure are.

Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Than reboot.
(May in rare causes loose TWRP but u will get out loop - be patient takes sometimes 7 Minutes+ for boot up the ROM)
Worked for me.
jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse

4r44444 said:
Boot to TWRP recovery, open Terminal inside TWRP and type:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Than reboot.
(May in rare causes loose TWRP but u will get out loop - be patient takes sometimes 7 Minutes+ for boot up the ROM)
Worked for me.
Click to expand...
Click to collapse
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc

jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Worked for me as well, funny thing was I almost didn't search thoroughly and was going to enter the other commands.

Ducter said:
Worked for me as well, funny thing was I almost didn't search thoroughly and was going to enter the other commands.
Click to expand...
Click to collapse
+1

jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
I got in that Bootloop by doing a Factory Reset with Root and TWRP. Formatting and Flashing the LG-H85020D-Flashable.COMPLETE.zip just ended in TWRP again.
Your Command fixed that issue!

jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Thank you jeffsga88 your code worked!

Also here to give my thanks!

recovering from dding into soc devices...
@4r44444 , @jeffsga88, Thanks for the guidance here. I could get out of the TWRP recovery boot loop with the dd dumps to soc devices. You have saved my phone from bricking. Cheers for your great help and guidance to the community !!!
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""

nitkam said:
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""
Click to expand...
Click to collapse
The permanent fix is in the same thread as the temporary one, specifically THIS post

Nimueh said:
The permanent fix is in the same thread as the temporary one, specifically THIS post
Click to expand...
Click to collapse
Thanks for the link. It has made my almost dead phone working again.

I got stuck yesterday in that same loop your code worked for me thanks...

No such file or directory, HELP ME!! Code isn't work

nitkam said:
@4r44444
@jeffsga88 Where is this guide for fixing the misc parition properly? ""but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for)""
Click to expand...
Click to collapse
Yeah - be careful with this - I did this and bricked mine - it went from unable to boot into Android to unable to boot fullstop... eventually managed to get it restored to factory (using LGUP), but MAC addresses all reset to 0's on every reboot - so now need to run macchanger on every boot...

jeffsga88 said:
Actually, you shouldn't use the above commands unless the following command doesn't work. That used to be the recommended method of getting out of TWRP, but it was realized that using the first command wipes your misc partition and then you end up with a Mac address that changes in every reboot (there is a temp fix for this I have a guide for). But anyways try to use the following to get out of TWRP bootloops:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
I tried this command after flashing lineage rom on my Nexus 5x. After flashing the rom, you initially see the Lineage logo, but it never boots, it just goes on into recovery. I flashed the rom 2 times, but same effect. After this I tried the command up here from the terminal, but nothing changes. Every time I reboot, it just boots back into TWRP. What do I have to do if this command does not work? Anyone have an idea? I saw the other commands in this thread, but it seems like most people don't think it's wise to execute those, so i'm just asking to be sure.
I also tried restoring the original backup of the phone I made in the first place before flashing lineage, but that just ends up in a bootloop where I end up in a screen with the google logo and the unlock sign. I followed these instructions to the letter, but somehow the phone is now bricked.. https://wiki.lineageos.org/devices/bullhead/install

So, no ideas here? I frantically tried getting the phone to boot into the bootloader, and after I don't know how many reboots it finally responded to my holding the vol down button, and got into the bootloader. From there I was able to flash back the entire phone to factory settings (I did not want to risk having to try over and over again to get it into the bootloader) and I'll keep it at that for now. I'm pretty experienced with custom roms on several Nexus 4, 5 and Galaxy Note II, but I've never had anything like this after flashing a rom.

Worked like magic the first time around. Thank you so much your your skills and sharing it
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
[/QUOTE]

FYI: If you run into these problems when using a MediaTek powered device, replace the of= path with
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para
Enjoy!

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

TWRP bootloop after LineageOS OTA Update

Hi everyone,
I came into a TWRP bootloop and don't know how to get out. Here's how it happened:
I wanted to start the OTA Update of LineageOS and clicked on install after it was downloaded. The device restarted and booted into TWRP. Nothing else happened. So I decided to do a reboot from TWRP (without doing anything else).
Instead of booting LineageOS it booted again into TWRP.
Now I am caught in this bootloop. The phone always boots into TWRP instead of LineageOS.
Any idea how to fix this?

Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.

gnackwatschn said:
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
I've encountered too the same problem (my phone version is the h870). Do you have any ideas on why this is happening? I managed to successfully install manually the ota package with twrp (/data/org.lineageos.updater/app_updates) but twrp still keeps looping

I have the same problem. I've tried installing lineage os ota update both via system settings and install manually via twrp but ended up with bootloop. Is there's a way to solve this?

dwisatriow said:
I have the same problem. I've tried installing lineage os ota update both via system settings and install manually via twrp but ended up with bootloop. Is there's a way to solve this?
Click to expand...
Click to collapse
Did you enter twrp via power off - key sequence or via the ota menu?

TWRP Loop
Mr-Kappa said:
Did you enter twrp via power off - key sequence or via the ota menu?
Click to expand...
Click to collapse
I am in the same boat, but about to try the fix above.
From what I've read elsewhere, this is a known bug in TWRP, and some useful person berated someone else for not knowing about having the correct bootloader (???), but when you're doing an update, that doesn't seem a logical thing?
In answer to your question Mr Kappa, when the system has downloaded the update, you tap to install, and it just does it's own thing, and hey presto, you're stuck in a twpr boot loop. This happens on all models it seems, from LG, Samsung, Moto, and lord only knows how many others, but the fix (and the only fix unless you leave USB debugging enabled) is this "dd if=" command, which is different for each make and model of phone.
***IF you have USB debugging enabled** - reboot to bootloader from TWRP (it will allow you to do this) then connect to your PC, open a command window (assuming you've got ADB/FASTBOOT installed) and type in "FASTBOOT CONTINUE". Apparently this works, but I've not enabled USB debugging so I can't try it (sensible security feature).

Try this one...
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-1-x-t3627595

Mr-Kappa said:
Did you enter twrp via power off - key sequence or via the ota menu?
Click to expand...
Click to collapse
I entered it via "reboot recovery" menu on flashify apps.

thx bro its work!!!

I am sorry to be asking at the wrong forum, but does anyone know the dd command for LeEco Le 1s? I am stuck with the same problem and am not able to find any solution for my model anywhere
I would be grateful if someone was kind enough to help me out here.

I had the same issue and was able to fix as the OP said but I wanted to add a couple steps that might not be obvious to some newbs like me.
Turn on the phone and let TWRP load. Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Worked for me on LG G6 US997.

gnackwatschn said:
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
THANK YOU VERY MUCH !!!!!
YOU HELP ME TO FIXING MY PHONE DUDE (anyway, I came from google search and I'm using LineageOS 15 on my zenfone. Got a bootloop to TWRP and I try to do what you say and surprisingly it works ! :highfive

Thanks, I use this every time an OTA update breaks boot.
gnackwatschn said:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse

Hey there, I'm having same problem.
I couldnt run the command in windows, but I did on Recovery terminal (OrangeFox), even tho the command runs properly, I still cant get out of Recovery.
Any idea?

gnackwatschn said:
Hi everyone,
I came into a TWRP bootloop and don't know how to get out. Here's how it happened:
I wanted to start the OTA Update of LineageOS and clicked on install after it was downloaded. The device restarted and booted into TWRP. Nothing else happened. So I decided to do a reboot from TWRP (without doing anything else).
Instead of booting LineageOS it booted again into TWRP.
Now I am caught in this bootloop. The phone always boots into TWRP instead of LineageOS.
Any idea how to fix this?
Click to expand...
Click to collapse
Yes, its the root that caused it. in twrp backup the data to mmc/otg/internal -> copy the lineage os zip file, gapps.. to a mmc or otg, in twrp -> wipe cahe,dalvik, data.. exept internal stor-> select storage, install lineage then gapps , dont install magisk/root zip, restore data, reboot system, install update -> reboot-> install rootzip.
next time unistall root then update.

gnackwatschn said:
Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
im sorry i am a newbie here.I have the same problem with a xiaomi redmi 7,i was forced to re-install the whole rom with the newest update because of the bootloop.Where exactly do i execute this command? in my computer? or in fastboot mode?

I have the same problem but my pc does not detect my phone when Im trying to connect it and use ADB, I tried 2 different cables. Is there anything I can do or my phone turned into expensive brick?
EDIT: I ignored what my pc was telling me (that no device is connected) and simply went to adb and typed the code above. It works, thank you

jdrouill said:
Turn on the phone and let TWRP load. Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Bro! You are my hero <3 Thank You so kindly much!

I just registered and only wanna say to you that "you're doing god's work". Thanks a lot. Keep em coming to this gem. Youre awesome. Thanks a lot!
gnackwatschn said:
Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse

Jonarius said:
im sorry i am a newbie here.I have the same problem with a xiaomi redmi 7,i was forced to re-install the whole rom with the newest update because of the bootloop.Where exactly do i execute this command? in my computer? or in fastboot mode?
Click to expand...
Click to collapse
yes, using your PC, try searching about adb and how it work first.
here: https://www.xda-developers.com/install-adb-windows-macos-linux/
It aint hard, after that you can execute these:
Turn on the phone and let TWRP load (Even though bootlooping and stuck on the TWRP logo). Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Worked for me on Xiaomi 6X recently. Good luck!