Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Related
It happened with me twice on Lg F220 & LG G2Ls980, stock lollipop firmware and TWRP Recovery was installed on both devices, i just rebooted the device to recovery mode to see which version is installed and explorer the different setting(i didn't activated anything) and reboot back to the system, now every time the device starts, the brightness level go to 100% and screen off time to 2mins. this happened on both of the devices, can some tell me what caused that problem.
Now i have bought an LS980 for myself, i have successfully rooted it and now its time to install a recovery, personally i love 4ext recovery but unfortunately it is not available for this device, i have only option to install TWRP, but now am afraid that if i installed it same problem will occur to me :crying:
""My device has Stock LS980ZVA installed""
Insert sim card or use custom rom. Its not a recovery deal
Librastar said:
It happened with me twice on Lg F220 & LG G2Ls980, stock lollipop firmware and TWRP Recovery was installed on both devices, i just rebooted the device to recovery mode to see which version is installed and explorer the different setting(i didn't activated anything) and reboot back to the system, now every time the device starts, the brightness level go to 100% and screen off time to 2mins. this happened on both of the devices, can some tell me what caused that problem.
Now i have bought an LS980 for myself, i have successfully rooted it and now its time to install a recovery, personally i love 4ext recovery but unfortunately it is not available for this device, i have only option to install TWRP, but now am afraid that if i installed it same problem will occur to me :crying:
""My device has Stock LS980ZVA installed""
Click to expand...
Click to collapse
Never experienced that, after installing a version of TWRP, upgrade to Blastagators TWRP 3.0.2.1 bumped & signed. I don't have the link handy, but searching should find it for you. But i agree, i have never had this happen on any version of TWRP recovery -i thinks it's un-related.
Agimax said:
Never experienced that, after installing a version of TWRP, upgrade to Blastagators TWRP 3.0.2.1 bumped & signed. I don't have the link handy, but searching should find it for you. But i agree, i have never had this happen on any version of TWRP recovery -i thinks it's un-related.
Click to expand...
Click to collapse
Is there any difference between normal TWRP & Blastagators TWRP ??
First of all, I had a LG G3 (D855) with cyanogenmod 13 on it.
Since my twrp didn't work and i had a pretty old cm13 version on my G3, I wanted to flash twrp again and I used the AutoRec apk from this post (http://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268), because I couldn't flash anything in my old twrp.
After flashing the new twrp, my G3 could only boot into the twrp recovery, so I searched for a solution and fount this post: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I did everything like the guy said in the post and it didn't work, so I used the last command in his post. After trying to boot into sytem it didn't work, but this time I got into the "cyanogenmod recovery" in which im stuck now.
So the first thing I did in cm recovery was looking for the possibility to flash an image, which just isn't there. So I tried flashing the newest cm13 nightly through the "Apply update" option in the cm recovery, which didn't work because I needed Baseband version 21C.
After that I obviously tried to flash Baseband 21C, which again didn't work, because the footer is wrong.
So I surfed through the internet, when I had to notice, that ADB (and fastboot) doesn't work in cyanogenmod.
Now I'm stuck here with this ****ty cyanogenmod recovery, where I can do nothing.
I hope that anyone of you can help me with this problem
Can't you go back to stock with a KDZ flash? Just boot into download mode.
A similar thing happened to me, but it was a TWRP boot loop. I tried the LGUP flash of a .kdz file, but that failed, so then I tried an earlier version of Android using LG Flash Tool 2014 and it was fine after that. Then I just updated to latest stock Android and rooted with Kingroot. Can you at least boot into download mode? (power off while not connected to PC, then press vol up I think at the same time as plug in USB cable).
hey'
every time i boot my phone it bootloop into recavery
what to do?
mega unbrick guide...
timrock7 said:
mega unbrick guide...
Click to expand...
Click to collapse
but in the guide it's you see nothig but a black screen i have recavery https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
it hapen when i exedantly press the istall update of the ota (i had OxygenOS 4.0 and i perss on the update of 4.0.3)
You should never install an update through the phone's update setting while using a custom recovery. The updates are designed to work with the stock recovery only.
If you can still boot into and use TWRP, use it to flash the full ROM of OOS 4.0.3.
If you can't boot into TWRP, try to see if fastboot works and manually sideload a working ROM in.
Otherwise, you're going to have to use the unbrick guide. Your phone doesn't have to be completely bricked to use it. It simply reverts the phone to a truly factory-fresh state (relocks bootloader, wipes everything, etc. - At least method 2 does anyways).
I got stuck in the same situation some time ago, and in order to solve it I had to flash the stock recovery, let it restart, it tried to update (and failed) and then it booted to system again. Hopefully that way you can avoid installing everything again. Once the device boots you can try to update with the stock recovery and revert to twrp if you want.
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs
so... you don't tried enter to recovery via key-combo? (Vol Down+Power).
If you can enter to Download Mode, try to flash a KDZ with LGUP.
I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help
fijuu said:
Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs
Click to expand...
Click to collapse
ebusuhejbi said:
I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help
Click to expand...
Click to collapse
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).
solved
sdembiske said:
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).
Click to expand...
Click to collapse
Thanks a lot. i finally got it done with the lg bridge software.