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!
Related
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.
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.
all credits go to thecubed.
i feel sorry for the guy @ q&a section, that had the same experience . had to go through wipe.
will have to remember to update via lg pc suite now to retain apps etc. then just redo bump if ever. thanks autoprime,thecubed and the rest of the amazing devs.
http://forum.xda-developers.com/showthread.php?t=2451696
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
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
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
if that doesn't work, try autoprime's with added step for misc.
after that you can delete the files located at (using es file explorer) device>cache>fota
autoprime said:
LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone. You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery or use adb commands below to fix boot issues..
Code:
adb shell
su
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 bs=256 count=1 conv=notrunc
reboot
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse
I broke my previous G5+, so I bought another one and quickly unlocked the bootloader etc. with drtechie's toolkit.
Boot/Reboot always goes to TWRP. How do I clear this?
I'm able to boot ResurectionRemix by going in to FastBoot/BootLoader by holding 'Vol-' + 'Power' and picking 'Start'.
Tordenflesk said:
I broke my previous G5+, so I bought another one and quickly unlocked the bootloader etc. with drtechie's toolkit.
Boot/Reboot always goes to TWRP. How do I clear this?
I'm able to boot ResurectionRemix by going in to FastBoot/BootLoader by holding 'Vol-' + 'Power' and picking 'Start'.
Click to expand...
Click to collapse
Me too, phone is XT1687, factory unlocked, bootloader unlocked rooted, install was good most of the day, an OTA update / reboot BAM!
TWRP every reboot
Wipe caches in TWRP and reboot if it's caused by an OTA update, a quick Google search would have found that... This issue has been addressed dozens of times here.
acejavelin said:
Wipe caches in TWRP and reboot if it's caused by an OTA update, a quick Google search would have found that... This issue has been addressed dozens of times here.
Click to expand...
Click to collapse
ResurectionRemix doesn't do OTA, and wiping caches doesn't affect this afaik.
Tordenflesk said:
ResurectionRemix doesn't do OTA, and wiping caches doesn't affect this afaik.
Click to expand...
Click to collapse
Sorry, I don't know your issue... I meant to quote @thomwin321as that is likely the issue there.
No-one?
Tordenflesk said:
I broke my previous G5+, so I bought another one and quickly unlocked the bootloader etc. with drtechie's toolkit.
Boot/Reboot always goes to TWRP. How do I clear this?
I'm able to boot ResurectionRemix by going in to FastBoot/BootLoader by holding 'Vol-' + 'Power' and picking 'Start'.
Click to expand...
Click to collapse
Try flashing the stock rom in fastboot, it fix the problem with the recovery, after, install custom recovery, root and custom rom.
I have solved this issue! For reference, the following threads were useful:
https://forum.xda-developers.com/showpost.php?p=74320886&postcount=6
https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
The key is finding the correct misc file to zero out. From a terminal with root access, or the TWRP terminal:
# cd /dev/block/platform/soc
# find . -name misc
./7824900.sdhci/by-name/misc
# dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Further reboots should no longer go to TWRP. Enjoy!
martinmcu said:
I have solved this issue! For reference, the following threads were useful:
https://forum.xda-developers.com/showpost.php?p=74320886&postcount=6
https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
The key is finding the correct misc file to zero out. From a terminal with root access, or the TWRP terminal:
# cd /dev/block/platform/soc
# find . -name misc
./7824900.sdhci/by-name/misc
# dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Further reboots should no longer go to TWRP. Enjoy!
Click to expand...
Click to collapse
The last command worked on my G5 and helped me to get out from TWRP bootloop. Thanks!
pochutkova.smotana said:
The last command worked on my G5 and helped me to get out from TWRP bootloop. Thanks!
Click to expand...
Click to collapse
This really worked?
---------- Post added at 02:26 AM ---------- Previous post was at 01:53 AM ----------
pochutkova.smotana said:
The last command worked on my G5 and helped me to get out from TWRP bootloop. Thanks!
Click to expand...
Click to collapse
#dd line?
jerryspring said:
This really worked?
---------- Post added at 02:26 AM ---------- Previous post was at 01:53 AM ----------
#dd line?
Click to expand...
Click to collapse
Yeah the other stuff doesn't work (permission denied) but the last DD line worked for me.
This works for TWRP Bootloop fix if your phone OS is only accessible via Fastboot but it keeps booting in to TWRP without you hitting the buttons.
Thanks!
Use this command
Fastboot continue
It will solve your problem
Perfect Solution
NO use of pc!
open twrp recovery.
mount system, leave the rest as it is.
Go to advanced, terminal
type dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
run it.
done problem solved.
The 7824900 or the path to misc can be different for different devices(other than moto g5 plus) but you can navigate that through file manager inside twrp.
I can confirm this work on g5s plus (sanders) running pie rom, thanks neighbor!
I did the step mentioned :
# dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
And now my phone is stuck at screen where it says "your device has been unlocked and can't be trusted. ID : N/A, your device will boot in 5 seconds".
When I do Power button + volume up/down nothing happens. It turns off the screen and shows the same screen again.
martinmcu said:
I have solved this issue! For reference, the following threads were useful:
https://forum.xda-developers.com/showpost.php?p=74320886&postcount=6
https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
The key is finding the correct misc file to zero out. From a terminal with root access, or the TWRP terminal:
# cd /dev/block/platform/soc
# find . -name misc
./7824900.sdhci/by-name/misc
# dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Further reboots should no longer go to TWRP. Enjoy!
Click to expand...
Click to collapse
You sir is my savior. THXXXXXXXXXXXXXXXXXXX
Hi, I'm trying to resolve this issue too running the adb shell command, but I'm getting 'Permission denied' when I use WIndows command prompt, guess I need to be rooted?
I reflashed stock 8.1 yesterday with the Moto G5 Toolkit and it was booting into the 'No command' screen...
TWRP gone too.
Edit: I got it to work by flashing TWRP then running the dd command from the Advanced > Terminal inside TWRP
BopNiblets said:
....snip....
Edit: I got it to work by flashing TWRP then running the dd command from the Advanced > Terminal inside TWRP
Click to expand...
Click to collapse
That's the way it has to be done right from the start.
martinmcu said:
I have solved this issue! For reference, the following threads were useful:
https://forum.xda-developers.com/showpost.php?p=74320886&postcount=6
https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
The key is finding the correct misc file to zero out. From a terminal with root access, or the TWRP terminal:
# cd /dev/block/platform/soc
# find . -name misc
./7824900.sdhci/by-name/misc
# dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Further reboots should no longer go to TWRP. Enjoy!
Click to expand...
Click to collapse
It worked for me. Thank you very much.
Issue Resolved; Little Tweak needed.
Thanks for the posts. I was able to resolve the issue.
However if the "dd" line doesn't work then try the following steps which resolved my reboot issue!
# cd /dev/block/platform/soc
# find -name misc
you will get the below result!
./7824900.sdhci/by-name/misc
if you are successful until this step then we just need cut short the "dd" code because we are already in the right directory!
just use the following command,
# dd if=/dev/zero of=/7824900.sdhci/by-name/misc
That's it!! you shouldn't be seeing the TWRP boot loop again!
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!