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.
Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
akumalol said:
Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
Click to expand...
Click to collapse
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
blitzkriegger said:
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
Click to expand...
Click to collapse
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
akumalol said:
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
Click to expand...
Click to collapse
FYI. I managed to finally boot again on Android 7 using the OTA update from here. https://www.reddit.com/r/Nexus6P/comments/4z4ru1/android_n_ota_link_for_nexus_6p_from_601_to_70/
The problem is i cant get back to MM and i guess i have to wait somehow for the updated apps to work with Nougat.
My computer isn't even detecting my phone within ADB... any help?
Licensedbeast said:
My computer isn't even detecting my phone within ADB... any help?
Click to expand...
Click to collapse
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
I officially hate Android 7. Boot loops galore. Factory reset without restoring ANYTHING is the only way to keep it from looping right now.... But its only been an hour so we'll see. Like you I'm unable to rollback to MM. My computer also is working with adb. I've updated my sdk to the newest version too. I can get the device serial number in fastboot, but the reboot commands give me error device not found.
akumalol said:
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
Click to expand...
Click to collapse
Damn... I tried Factory Resetting... and all I had to do was unplug and re plug. Thanks that worked
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
bogomil4e said:
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Click to expand...
Click to collapse
Was running the Nougat 7.0 WETA ROM, and had some issues with sound performance, plus battery life was tanking, so went to using Vanir 6.0.
Wiped and installed (I assume from the process that backup and restore is part of this process), then pico gapps, and stuck on boot screen.
Found this thread and followed instructions. The first ABD command works flawlessly, but the second one returns the standard printscreen when a command isn't recognized, and lists all the adb options. Possibility it's entered incorrectly?
Boot issue persists
hifiaudio2 said:
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Click to expand...
Click to collapse
Have you found a solution? Mine is doing the exact same thing
Device is corrupt, stuck on google logo
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
wonton9224 said:
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
Click to expand...
Click to collapse
You can push the file via adb or just connect your phone through usb cable while in twrp and drag and drop from pc to your phones storage drive
Yeah I couldn't get the internal storage to mount on xp but it does on win 7, window pops right up after drivers install. I tried flashing cm13 with the correct gapps but it still hangs at Google. I'm using the skipsoft toolkit to try and flash back to stock right now
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Flash kernel for mm and then rom
pctechdroid said:
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Click to expand...
Click to collapse
Read post #10.
Sent from my Nexus 5X using Tapatalk
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
[email protected] said:
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
Click to expand...
Click to collapse
try flashing the newest 7.1.2 vendor i was having the same issue when i tried going back to 7.1.2 from android O
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
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!