Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?
I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader
Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.
Hey, guys. :victory:
I had the ROM LineageOS on my Zenfone 2 (ZE551ML), but I was factory reset by setting the cellphone instead of using the recovery mode. With that, my cell phone looped through the TWRP. I tried everything, clean the cache, clean the system, reinstall Lineage, finally tried to reinstall the ROM stock. But I thought it was taking too long (more than 10 minutes in the same process), so I hung up and tried to call the cell phone again, but it was on the black screen, just vibrating. :crying:
I was able to solve this problem by reinstalling the firmware and stock ROM using xFSTK and ADB Fastboot (I could not use the Asus Flash Tool, I did the whole process manually).
Now, I have another problem, for a change. The stock ROM is Android Lollipop, on the Asus website has update for Android Marshmallow, including already managed to upgrade before migrating to Lineage. But now, when I restart the system to upgrade, it goes into fastboot mode and when I try to get into recovery mode it goes back to the fastboot or when I put in normal boot it starts without updating. I tried to install TWRP again but it is looped in Fastboot and I need to do all the procedure I did before to recover the phone.
Has anyone had a problem like this or do you have any idea how to solve it?
P.S. Sorry for any English error. Google translator. :B
Hay Guys,
I have a German(Vodafone) Samsung Galaxy S9 SM G960F and I am stuck on the Samsung Startup Screen. I succsessfuly installed TWRP recovery and Magisk 17.1 after that I noticed that my phone froze on the lockscreen, after I let it sit for a while. So i decited to install a custom ROM. At first Lineage OS and the Problem accured for the first time. After that I tried a few others.
At this point i even downloaded the stock ROM and tried to flash it with Odin. And for some reason, Odin will always get stuck ether on recovery.img or System.img. Now I am out of Ideas and desperately reaching for help:crying:.
I am able to reach twrp and the downloadmode.
Make sure you're not trying to downgrade the bootloader (Check in Download mode for B:1 or B:2)
Firmware shows BL version here
G960FXXU2BRGA
You cannot downgrade from 2 to 1 for example, flash the same or higher
Not sure what is going on or if anyone else has this problem, but since I got the Moto G power I've had a problem booting into the system after flashing stock ROMs in fastboot. Everytime I try my device doesn't go past the blue Moto logo. I'm no stranger to rooting/flashing ROMs/or anything like that. I probably flash more than necessary always switching up my phones. Ive flashed fastboot ROMs for years with no problems. I've got used to just using LMSA and it never failed to fix my issue. Now, LMSA won't recognize my device in terms of matching firmware and I can't use it without validation. I can flash everything fine and start to boot but nothing after that. I've tried formatting, factory reset in both stock and twrp to no avail. Even restored my Omni backup countless times in twrp which usually did its job no problem. Tried flashing vbmeta etc.. am I just experiencing tunnel vision and missing something obvious or what? Any help would be appreciated I'm not the same without my phones working device is US retail unlocked 2041-4 Sofia on what I assume is the latest firmware. (lolli Moto)
You've been trying to boot it with the stock kernel and not a magisk patched one after restoring however? / Have you tried booting without a magisk patch kernel (stock) and userdata formatted?
I had the same problem updating the firmware and i had to first boot it with the non rooted kernel and userdata formatted to first boot.