Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?
Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks
Only solution back to stock & after install LOS and wait until bug is fixed.
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796
WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.
Related
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.....
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
livebyknight said:
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
Click to expand...
Click to collapse
Very much appreciated.
NevetsDrassel said:
Very much appreciated.
Click to expand...
Click to collapse
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
Within the folder that I have "what" in?
Got the drivers loaded and the system now recognizes an android device.
Started ADB
Copy and paste the code into "what" folder?
Thanks
Sorry I am new to this. Is this is what I was suppose to get?
C:\LG\Root Tools\ADB + Fastboot + Drivers>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/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
~exit
# ←[6nadb rebootdd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fo
ta-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 1.056265 seconds, 30.3MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on devi
ce
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 2.493231 seconds, 12.8MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on devi
ce
32769+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.675348 seconds, 23.7MB/s
~ # exit
C:\LG\Root Tools\ADB + Fastboot + Drivers>
And do I now reboot? or what?
Damn, it worked..... My phone is working again? Was this some type of virus or what?
Thank you thank you thank you for you assistance. You have saved me from the blackness of hell.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
fromc2m said:
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
Click to expand...
Click to collapse
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
fromc2m said:
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
Click to expand...
Click to collapse
You can get the Koush drivers from here.
You can get the script from http://www.photo-cool.com/?p=48043
Can't help you with Windows8. I know nothing about it. The ADB + Fastboot + Drivers is a .zip file. You have to unzip the file and put it on a directory of your choosing. I put my in C:/LG/ADB + Fastboot + Drivers/
Once you unzip the file (you can use 7Zip found here ) you will see the ADB.exe application along with 5 other .dll/applications/files in the folder.
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
This link is dead. Can you please give me another link? It's very urgent.
Just use this Toolkit
http://www54.zippyshare.com/v/29970713/file.html
Download D800 Rom and then add the .zip folder to Toolkit v1,5 - sideload folder
First you need to enter TWRP and then go to Advanced and press ADB Sideload Swipe
It's easier to rename it like rom.zip
Now start the start.bin
Select language
Enter
In my opinion it's 1 , enter
Then press 7) Install ROM/ Unbrick via SideLoad
Enter
and write the rom name that is in the sideload folder ( becouse i renamed it it's rom.zip in my opinion)
Now wait for the rom is pushin trough sideload
The installation process will start automatic .
I hope you got this by now,., had this happen to me...I found the thing to do..
On your TWRP terminal command type this codes.
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 back out of terminal to reboot system
Help me plz same thing im facing with my lg g2
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
mehler said:
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
Click to expand...
Click to collapse
I am also in same situation. I have cyanogen recovery. haven't find any solution by readings in forums. biggest problem is my phone and adb server. adb shell never works. my phone is unauthorized. only work is sideload, but cannot install zip file. stuck every time on 47% and thee phone reboots and back to cyanogen recovery screen.
anybody had really solved this kind of problem.
any help is highly appreciated. there might be guys like me looking for solution.
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'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
I tried all the methods mentioned in the threads already present in the forum, but none of the methods seems to work for me. " no space left on the device " this is the error i get when i execute command "dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc" .
That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run
Code:
#cd /dev/block/platform/soc
#find . -name misc
to verify 7824900.sdhci is correct address.
[email protected] said:
That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run to verify 7824900.sdhci is correct address.
Click to expand...
Click to collapse
I posted this query earlier and all of them stated this solution to the problem. My problem is my device never reboots itself it reboots into bootloader and from there i have to manually press start to boot into rom and also my device is XT1686
As I posted, run the commands to be sure your misc. address is 7824900. If it returns something different, modify the
Code:
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
command to reflect your misc. address. Also I believe those commands need to executed as root.
I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.
JohnSmith8786 said:
I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.
Click to expand...
Click to collapse
Yes, ADB/Fastboot is always preferred, terminal is where you must run as root with su commands, and you must be rooted with Majisk .
Hello, I need your help, if possible.
I have a Galaxy Note 8.0 N5120 (LTE Model), which was running rooted stock rom 4.4.2.
Then, I wanted to update it to a newer Android version, and I found RR (=Resurrection Remix) , which is 7.1.2. I updated Recovery to TWRP and started testing (RR 5.8.4 and 5.8.5).
During testing, I changed versions of TWRP, too.
The main reason for testing is that in the beginning, USB OTG was not working, and with 5.8.5 usb otg was working and I was happy!! However, at some time later, USB OTG started not working, So, I thought it must be a harware issue. Then I noticed I had no baseband, no IMEI!! (I must have lost it sometime in the process of testing, because with 4.4.2 everything was working!!)
SO, I did a lot of search, and I tried the following.
First, I flashed back to original stock rom (4.4.2)
As I had "efs.img" (which I probably made with Philz Touch many years ago). I changed recovery to Philz Touch, but could not restore. So, I searched and I found a way to flash it with Philz Touch. (Before flashing I deleted all the folders and files in efs dirtory, and after flashing, I checked that the folders and files were there.)
But, still no baseband, no IMEI....
So, I searched again and I found out that erasing modemst1 and modemst2 could solve the issue.
First, I tried in TWRP (advanced - Terminal)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "no such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "no such file or directory"
So, I setup adb in my PC (Windows 7 64bit), and started testing.
1) adb devices
gives "xxxxxx unauthorrized"
On the phone, I authorized and, then it gives "xxxxxx device"
So, I presume the connection is establed with the phone.
2) adb reboot bootloader
The phone reboots but in normal android mode (4.4.2)
I searched again, and I found out Samsung phones don't support fastboot...(I can not use fastboot commands...)
Just to check, I put the phone in Download mode (home + volume up and power on). Then I connected it to my PC, but the phone is not detected.
As adb seems to work, I tried the following.
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "cannot open for write: No such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "cannot open for write: No such file or directory"
(So, it does seem like adb works, but maybe modemst1 and 2 are in a different location...)
I have no more idea...
Is there anything I can try?