Database Users

Doh! another one here with a brick. Can you solve this one?!

here goes...
Accepted an OTA from LG while running Rayglobe.
Stuck in CWM boot loop.
Cannot restore nandroid or install any zip from the sd card.
Managed to get adb and entered the command below, but still stuck in the CWM loop.
Here's what happens
C:\Users\WIN 7 HP>adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
~dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota # dd if=/dev/blo
ck/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.623509 seconds, 51.3MB/s
~ #
can you see whats wrong?
Many thanks

Any make sense of this for me? the poor phone is dead

mwatson said:
Any make sense of this for me? the poor phone is dead
Click to expand...
Click to collapse
install your recovery of choice again. or of your recovery still works, wipe and install your rom of choice again.

mwatson said:
here goes...
Accepted an OTA from LG while running Rayglobe.
Stuck in CWM boot loop.
Cannot restore nandroid or install any zip from the sd card.
Managed to get adb and entered the command below, but still stuck in the CWM loop.
Here's what happens
C:\Users\WIN 7 HP>adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
~dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota # dd if=/dev/blo
ck/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.623509 seconds, 51.3MB/s
~ #
can you see whats wrong?
Many thanks
Click to expand...
Click to collapse
here's what I did when I was in a very similar situation as you. I was using CWM and I got caught in the same boot loop I was trying to get into download mode. After doing some research you have to download TWR p on your computer and saiboat it.. (Sorry was using speak to text) you have to sideload twrp and then flash it.. Reboot the phone and it will be in twrp.. Then you can put it in download mode and flash stock ROM back on... Or you can sideload a ROM that you kbiw works and flash it.. You go to install on cwm and then look for install from sideload... Use adb to push IT.. Look up (can boot loop xea) on Google and there will be some very helpful post that will tell you exactly how to do what I'm saying

darkobas said:
install your recovery of choice again. or of your recovery still works, wipe and install your rom of choice again.
Click to expand...
Click to collapse
Thanks for your help.
My recovery still works, but when i install a zip from sd like rayglobe for instance, it goes through the aroma set up, reboots but goes straight back into CWM recovery. I get a message saying android-secure.img missing.
I also cannot install a nandroid back up

joewaz said:
here's what I did when I was in a very similar situation as you. I was using CWM and I got caught in the same boot loop I was trying to get into download mode. After doing some research you have to download TWR p on your computer and saiboat it.. (Sorry was using speak to text) you have to sideload twrp and then flash it.. Reboot the phone and it will be in twrp.. Then you can put it in download mode and flash stock ROM back on... Or you can sideload a ROM that you kbiw works and flash it.. You go to install on cwm and then look for install from sideload... Use adb to push IT.. Look up (can boot loop xea) on Google and there will be some very helpful post that will tell you exactly how to do what I'm saying
Click to expand...
Click to collapse
Thanks for your advice. I wasn't sure if you could flash one recovery on top of another.
If I cannot install a zip on CWM, do you think I will be able to with TWR?

mwatson said:
here goes...
Accepted an OTA from LG while running Rayglobe.
Stuck in CWM boot loop.
Cannot restore nandroid or install any zip from the sd card.
Managed to get adb and entered the command below, but still stuck in the CWM loop.
Here's what happens
C:\Users\WIN 7 HP>adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
~dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota # dd if=/dev/blo
ck/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.623509 seconds, 51.3MB/s
~ #
can you see whats wrong?
Many thanks
Click to expand...
Click to collapse
I ran into the same issue last night. This fixed it on my twrp recovery. I'm not sure how it works for CWM but if you're running through adb shell would it not be the same?
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.

Thanks for your help guys, I managed to install TWRP but now i'm stuck in a loop with TWRP instead of CWM.
I wiped and install Rayglobe, but i'm now in a different loop.
any fixes?

Did you try the post above yours?
Sent from my LG-D800 using Tapatalk

tdevaughn said:
Did you try the post above yours?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes, just done that and its back in the room!
Thanks all, 5 days of stress over!:fingers-crossed:

coldcrush390 said:
I ran into the same issue last night. This fixed it on my twrp recovery. I'm not sure how it works for CWM but if you're running through adb shell would it not be the same?
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
Where are you typing this? I tried in adb shell while in cwm and now i got twrp to flash and i'm stuck there. I go to advanced and terminal command and it's asking me to choose a file and bringing up my sdcard. I choose select and it open terminal and I entered everything but the phone just boots back to recovery.
mwatson said:
Thanks for your help guys, I managed to install TWRP but now i'm stuck in a loop with TWRP instead of CWM.
I wiped and install Rayglobe, but i'm now in a different loop.
any fixes?
Click to expand...
Click to collapse
I'm in the same situation.
mwatson said:
Yes, just done that and its back in the room!
Thanks all, 5 days of stress over!:fingers-crossed:
Click to expand...
Click to collapse
so how did you do it! My cousin is stressing and I'm stumped as how to fix this.
[UPDATE]
He got it working. He was putting a space after the period and before the 1 so it wasnt working. Once entered correctly the phone booted fine.

imucarmen said:
Where are you typing this? I tried in adb shell while in cwm and now i got twrp to flash and i'm stuck there. I go to advanced and terminal command and it's asking me to choose a file and bringing up my sdcard. I choose select and it open terminal and I entered everything but the phone just boots back to recovery.
I'm in the same situation.
so how did you do it! My cousin is stressing and I'm stumped as how to fix this.
[UPDATE]
He got it working. He was putting a space after the period and before the 1 so it wasnt working. Once entered correctly the phone booted fine.
Click to expand...
Click to collapse
I did that too. I saw what i did wrong and re entered. Glad he got it fixed.

coldcrush390 said:
I ran into the same issue last night. This fixed it on my twrp recovery. I'm not sure how it works for CWM but if you're running through adb shell would it not be the same?
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
Only overwriting fota did not work for me. I had to do it to misc as well. Cheers.

[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.

Recovered from soft brick, how do I proceed?

I recently got a new G2 D800. I was amazed how easy it was to root using towelroot and adding recovery using autorec. I thought all was well until I accepted some google updates. After updating and rebooting, I was limited to the TWRP screen. So using TWRP terminal, I typed the following commands:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Phone rebooted properly, had an error something about invalid installation. I clicked OK and never saw error again. But now Google+ and GoogleDrive want to update. Do I dare permit this update or will it brick my phone again?

I suggest you flashing stock kdz to make sure your phone is normal again

Tried to OTA update, now phone only boots into TWRP. ROM is still there.

Hi all, I'm having an issue where I tried to do the OTA update, which failed since I have a TWRP installed.
Now, whenever I boot my phone, it goes to TWRP by default. I can still go to the bootloader and start (or fastboot continue) to enter my OS, but is there a way that I can set that by default?
Thanks!

You can't install OTA update if you're rooted/TWRP. First you'd have to unroot.
Anyways to fix your problem do this:
Go to TWRP> advanced> terminal> and type these 2 commands
1)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/fota
2)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Should get you out of TWRP bootloop

The OTA is in cache... Wipe caches, reboot, and don't accept the OTA again.

LiteSoul said:
You can't install OTA update if you're rooted/TWRP. First you'd have to unroot.
Anyways to fix your problem do this:
Go to TWRP> advanced> terminal> and type these 2 commands
1)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/fota
2)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Should get you out of TWRP bootloop
Click to expand...
Click to collapse
Yeah, I realized that afterwards, which was what I mentioned in the OP.
Thanks so much btw, that worked! Guess now we wait until a custom 83 is released

LiteSoul said:
You can't install OTA update if you're rooted/TWRP. First you'd have to unroot.
Anyways to fix your problem do this:
Go to TWRP> advanced> terminal> and type these 2 commands
1)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/fota
2)
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Should get you out of TWRP bootloop
Click to expand...
Click to collapse
This solved my problem. Thank you so much!

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!