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.
Related
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
FamousCarpet said:
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
Click to expand...
Click to collapse
uninstall any drive for g4 from pc and reinstall again and lgup. now reboot phone to download mode when lgup is open first check upgrade opsion and when open kdz check refurbish opsion and start. good luck
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
The best way to flash stock image is to use official LG Bridge app. Download it, turn off your phone, connect it to PC while holding volume up button - phone will go into download mode. Then there is option for software restore in LG Bridge but i won't tell u where exactly. If it won't work i would try on another PC. If it won't work maybe you would be able to flash stock image trough send_command but i won't help you with it.
FamousCarpet said:
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
Click to expand...
Click to collapse
open lgup torn off the phone press volume up insert usb cable wait to see download mode on phone release up button and see if everything go fine
Thank you a lot Avantu, the LG Bridge did the trick! I now have a factory rom!
Hi there, I have the above device with unlocked bootloader. It was rooted but I had a problem where the tablet kept rebooting but only after it loaded Android. No amount of following guides fixed it and Recovery and Fastboot were throwing g up problems whenever I tried to flash anything.
Eventually, I managed somehow to switch it on to Chinese update cycle I think and update the ROM with the latest official Chinese EMUI through multiple reboot loops (it downloaded about 10% of the update each time before crashing and getting the next chunk of download next time).
So I'm currently on the latest Chinese ROM running android 5.1.1 and it started working again. However the ROM came without gapps included so I flashed TWRP and installed gapps and I'm back to the reboot cycle. It lasted a long time before restarting again though so I'm guessing it's to do with gapps trying to update.
So I'm back to square one again. Any ideas? Is there any kind of log I can provide to help diagnose? I still have TWRP and have access to that without the bootloop starting again..
How did you rooted it?
LG G4 815
S/N=511
tl;dr: Bootloop, did a lot of fiddling, finally ended up with installing a "somewhat" working setup in this order (Everything installed via TWRP, TWRP was via fastboot):
1. TWRP (SteadfasterX's) /O version
2. V29a Firmware, keep TWRP
3. Disable big cores kernel (From above V29a firmware thread, first reply by kessaras)
4. LineageOS 15.1
5. Mindthegapps
Having troubles getting it to boot past the LG bootscreen (Once it boots completely, it seems to work fine).
---------------------------------------------------
So yesterday I was browsing my phone when it suddenly restarted. It had done this before multiple times and it always has gotten back to working just fine. Only this time was different, after the LG bootscreen went away, it appeared again. I'm aware of the bootloop issues the device has and was hoping I would get lucky but apparently not.
Configuration when bootloop happened:
-LineageOS14.1
-Stock kernel
-TWRP (3.1.1?, cant remember exact version it was 3+ anyway).
I noticed I could still access TWRP (Although it did crash few times back to LG bootscreen), so I first tried wiping caches etc (No luck). Anyway, I was quite close to just giving up at this point, but decided to fiddle around with the thing. I found out about the issue with one of the "big cores" heating too much and that it was possible to disable those. I decided to give it a try, and while I was at it, wanted to try out the newer LOS15.1. Downloaded titan kernel (no big cores), installed and went onto install LOS. First issue, my TWRP wasn't new enough to install the LOS15.1 (Error code 7). Did some searching and found out about "unofficial TWRP" installations that allowed me to install LOS15.1 (Used SteadfasterX's TWRP, O/ version).
After this I got a few kernel crashes (Green screen with a lot of text, different error codes each time), all searches pointed to my own error during installing stuff (I had older firmware while LOS required newer), and I believe these crashes had nothing to do with the actual bootloop issue. To fix this I went and grabbed the V29a firmware and the big cores disabled kernel which is in the first reply of that v29a thread. After this I managed to install LOS15.1+Mindthegapps (Also rooted it) just fine and it booted up past the LG bootscreen. I grabbed Kernel Auditor to check if the big cores had been disabled and I could only see 4 cores (max 1,44ghz).
Now the phone seems to run fine when I actually get it booted up. I tried restarting the phone and I was stuck in the loop again (Did multiple restarts). I tried booting into recovery (I got into the "factory reset" dialogs just fine which takes you to TWRP) but after that instead of TWRP it went back to the LG bootscreen (Tried again like 3 times). After this I plugged in my phone to my computer and got into TWRP first try(I wonder if there's an actual reason for this, I know it could be just pure luck). Then I went onto the reboot options in TWRP and booted into system. First time I got past the bootscreen but it crashed when asking for my SIM pin code. Second time after booting the same way, I got it working just fine and now the phone seems to be working happily again.
Is there anything I can do myself to trace this issue and improve the chances of booting up the phone or am I forced to just rely on luck and hope it boots completely without crashes (In the case of a crash/I need to restart the phone)?
I recently dug out my old G4 to see if I can repurpose it for anything or just have it as a back up.
It's an H815 European variant with unlocked bootloader. When I last used it I had it running a custom ROM but when I got a new phone I wiped it somehow with TWRP (this is a few years ago so I can't remember).
Now whenever I turn it on, it boots into TWRP. If from TWRP I choose reboot to system, it boots to TWRP.
I tried to install a ROM but it wouldn't, giving the error "this ROM is for P1,G4,H815 (or something like that), your device is .".
So, I edited the ROM metadata and took out the device requirements and it installed fine, as did GAPPs & SuperSU, but still it only boots to TWRP. I've flashed bootloaders, kernels, god knows what else, but it only boots to TWRP. That's it.
I also tried to return it to stock using these: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 but it had errors connecting to servers and never installed anything.
I'm aware that I won't be able to recover anything on the device and that's fine! I just want to boot it with ANY ROM, and I'd be grateful for any help! Thanks!
mrmrchoice said:
I recently dug out my old G4 to see if I can repurpose it for anything or just have it as a back up.
It's an H815 European variant with unlocked bootloader. When I last used it I had it running a custom ROM but when I got a new phone I wiped it somehow with TWRP (this is a few years ago so I can't remember).
Now whenever I turn it on, it boots into TWRP. If from TWRP I choose reboot to system, it boots to TWRP.
I tried to install a ROM but it wouldn't, giving the error "this ROM is for P1,G4,H815 (or something like that), your device is .".
So, I edited the ROM metadata and took out the device requirements and it installed fine, as did GAPPs & SuperSU, but still it only boots to TWRP. I've flashed bootloaders, kernels, god knows what else, but it only boots to TWRP. That's it.
I also tried to return it to stock using these: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 but it had errors connecting to servers and never installed anything.
I'm aware that I won't be able to recover anything on the device and that's fine! I just want to boot it with ANY ROM, and I'd be grateful for any help! Thanks!
Click to expand...
Click to collapse
Go to thw official TWRP thread and flash the latest preview TWRP version.
Sent from my OnePlus 6T using XDA Labs
Try latest rom and one by one different rom. It's rom related issue. Don't worry, it'll be okay.
Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyedphase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.