Database Users

[Q] LG G2 T-Mobile stuck in CWM after OTA

I've already tried http://forum.xda-developers.com/showthread.php?t=2432476 and several other threads and I've run into different problems for all of them.
I can boot into download mode. The drivers are installed and seem to be working (it says LG D801 in Device Manager). I've tried both methods in the thread above. The first one doesn't work at all because the phone has to be booted in normal mode.
The second one doesn't work either. I get to where the FlashTool says READY, but when I plug the phone in while download mode is on, nothing happens. I thought this might be the COM port, so I went to change it in Device Manager, but the option isn't even available. The tab isn't available in the device properties.
There are several old zips I have on the phone that I've tried flashing, no dice. The LG Mobile Support Tool (that allows you to update the phone) just says that the software is up to date and won't let me do anything.
I'm going in circles now trying to fix this, anyone know what to do?
Thanks!
edit: adb also doesn't recognize the device. I think it might work to install TWRP and use the command in http://forum.xda-developers.com/showthread.php?t=2451696 from the phone, but I don't know how to replace CWM with TWRP.
edit 2: got adb working by installing the pdanet driver! I installed TWRP so I'm on that now. The commands in that thread still don't work though.

if you have adb access you should be able to use the first command from here to boot normally

XxZombiePikachu said:
if you have adb access you should be able to use the first command from here to boot normally
Click to expand...
Click to collapse
Thank you, however adb does not recognize it. adb devices returns nothing.

vvfs said:
Thank you, however adb does not recognize it. adb devices returns nothing.
Click to expand...
Click to collapse
well to install twrp you would just need to flash the zip from inside cwm, but if adb doesn't recognize the device then you cant adb push

XxZombiePikachu said:
well to install twrp you would just need to flash the zip from inside cwm, but if adb doesn't recognize the device then you cant adb push
Click to expand...
Click to collapse
So I'm SOL?

XxZombiePikachu said:
well to install twrp you would just need to flash the zip from inside cwm, but if adb doesn't recognize the device then you cant adb push
Click to expand...
Click to collapse
I got adb working now and installed TWRP, but the commands in the thread you posted didn't fix anything.
I've flashed a couple of ROMs and it still boots to recovery.

okay so you already tried dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota and dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc from the terminal inside twrp(one after the other), also since you got adb working did you try the ones through adb dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img and dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

Help, possible brick!!!!!!!!

I am/was rooted with custom recovery. I was running stock ROM with minor tweaks (g3 notification panel, etc). I downloaded the "knock code" update that just came out for the LG G2 (AT&T), not even thinking about the root/custom recovery, and then when I went to install it, it booted into TWRP recovery. I had no idea what to do from there (it would just reboot back to recovery if I rebooted), so I wiped the system then flashed my backup. Still nothing, it still booted into recovery. So then, being the smart guy that I am, I did a complete wipe of everything (internal storage and everything), and now I'm stuck at recovery with absolutely nothing. No backups or anything.
How do I get my phone back up and running?

brian85 said:
I am/was rooted with custom recovery. I was running stock ROM with minor tweaks (g3 notification panel, etc). I downloaded the "knock code" update that just came out for the LG G2 (AT&T), not even thinking about the root/custom recovery, and then when I went to install it, it booted into TWRP recovery. I had no idea what to do from there (it would just reboot back to recovery if I rebooted), so I wiped the system then flashed my backup. Still nothing, it still booted into recovery. So then, being the smart guy that I am, I did a complete wipe of everything (internal storage and everything), and now I'm stuck at recovery with absolutely nothing. No backups or anything.
How do I get my phone back up and running?
Click to expand...
Click to collapse
Try this..
What worked for me was from the TWRP terminal command was to type
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.

Bigsky40 said:
Try this..
What worked for me was from the TWRP terminal command was to type
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
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?

brian85 said:
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?
Click to expand...
Click to collapse
I thin you can ADB push a rom file to your phone, flash it in twrp, then enter those terminal commands which will allow it to boot normally

brian85 said:
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?
Click to expand...
Click to collapse
You took ota while having custom recovery ?
This will enable you to boot (if you didn't mess up another things on your system)
you may also: "adb push rom.zip /sdcard/rom.zip"
-where rom.zip is the name of your rom.

Can't figure out how to get ADB to recognize my phone. I downloaded SDK and all that. When I do "adb devices" I get "no devices found"

There's a bug in TWRP 2.7.0.0 that you can't activate ADB.
I suggest to boot into download mode (plug your phone to your computer USB while pressing volume UP key), open LG PC Suite, go to Mobile Device > Restore upgrade errors, and it will flash the latest stock firmware
Sent from my LG-D802 using XDA Premium 4 mobile app

After LineageOS Update 08.31.2017 i stuck in bootloop into twrp

Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian

did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM

one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?

Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks

Only solution back to stock & after install LOS and wait until bug is fixed.

I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted

Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796

WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.

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!

Tried to unroot my LG V20 by accepting OTA update, now stuck in boot loop to TWRP

Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.

fronzee88 said:
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
Click to expand...
Click to collapse
In twrp go to mount and make sure system is mounted, then try rebooting
Sent from my LG-H910 using XDA Labs

cnjax said:
In twrp go to mount and make sure system is mounted, then try rebooting
Click to expand...
Click to collapse
It still boots into TWRP.

fronzee88 said:
It still boots into TWRP.
Click to expand...
Click to collapse
Did you try restoring a back up
Sent from my LG-H910 using XDA Labs

cnjax said:
Did you try restoring a back up
Click to expand...
Click to collapse
I made a backup with TWRP before attempting the original update that caused this issue, but I am doubting the integrity of that backup, because I was not able to decrypt the "data" partition before making the backup. So I backed up the data partition in the encrypted state, but I am not sure if that is restorable or not. Instead, I just tried reflashing the ROM.
When I navigated to the TWRP backups folder where the backup was supposed to have been saved, I couldn't find the (most recent) backup, so I am not sure if I can actually restore anything, should the need arise.

While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian

runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Click to expand...
Click to collapse
I wasn't able to get connect with my laptop from adb (unauthorized message) but I did enter the dd command in a terminal directly in twrp itself (Advanced > Terminal). It worked!!! Thank you, thank you, thank you! Whew.

If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
-- Brian

runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
Good to know. Thanks!

runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
I'm having trouble finding the latest official TWRP download for LG V20 T-Mobile (H918). The device isn't listed on their official site. Any suggestions on how to upgrade?

TWRP 3.2: https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
-- Brian

runningnak3d said:
if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
Click to expand...
Click to collapse
I'm not sure what you mean by "download" mode, but my other question is: Will flashing a KDZ cause me to lose all my data? If so, how can I make a backup of all my data if the "data" partition is encrypted? I can't get TWRP to decrypt it even when entering the correct PIN that I normally use to unlock my encrypted phone upon regular bootup.
Note that Titanium Backup is not an option if I'm planning to unroot my phone.

Yes, flashing a KDZ wipes your phone.
If your data partition is encrypted, the only way to backup your data is from within the OS (copy to SD card) or use LG backup.

Btw the reason you arnt able to get into recovery via the buttons is because you were doing it wrong, its not hold power and volume down, its actually hold volume down, press power until the screen turns on, then (still holding vol down) tap the power button (either once at exactly the right time, or repeatedly which works more consistantly) until a screen appears asking if you want to factory reset. saying yes (via the volume and power buttons) twice boots twrp if installed, else it boots the stock recovery and wipes the phone.

runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
Click to expand...
Click to collapse
The same thing happened to me but on my V10. Would this command work on that phone?