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.
To preface, I can boot into download mode and access hard reset but cannot boot into the ROM as it just shows the "Broken Android" symbol
I've been trying a lot of steps.... So many guides... To fix my phone. I've chalked it up to an issue with my IMEI/ESF being corrupted as LG Flash Tool shows it as NULL" and fails after 3 seconds consistently. LG UP also fails at 6% spitting out generic errors. I've even tried LGMobile Support Tool and it downloaded the correct firmware but failed to apply it at 2% consistently.
I'm assuming this has to do with my ESF being corrupted. I've been looking up guides on how to "fix" it but keep coming up short as ALL of them require a back up or at least being able to boot into a ROM. However, no ROM will flash. The bootloader is locked and the device has no root options. At this point I'm drawing a blank. I've been going at this for 11 hours straight (no joke, been sitting here for 11 hours searching the forums for different fixes because I know how people feel about the same thing popping up repeatedly.
What caused this issue was trying to roll back the firmware to an earlier version using LGUP so I could unlock the bootloader. I've only been attempting with stock roms (both KDZ and TOT)
Any help would be appreciated.
The phone is still detected in DLMode and all the programs can find it and know it's a D852 but just wont take any firmware.
Hello!
Today I finally received permission to unlock my bootloader, after waiting a long 15 days (360 hours). After solving some MiFlash Unlock issues, I finally unlocked my phone. I flashed TWRP and Magisk, and then afterwards I flashed Xiaomi.eu's stable whyred ROM, which worked (including camera sensors), but was terribly slow and clearly very unoptimized. For this reason, I decided to flash the leaked official Global ROM, 9.5.6 from Xiaomi. All was well, and I was presented with the initial set-up screen. After selecting my language (English [United Kingdom]), I was forced to select China as my region on the next page. Seconds after selecting it, my phone reboot and opened the system again, only to reboot within seconds. This process would probably repeat endlessly if I didn't have it in fastboot mode. I can still access TWRP recovery, and my phone still shows that it's unlocked on the boot screen. I've tried doing another clean wipe, and then installation of the global ROM with no success (same error occurs, even when I tried English (United States)).
I've tried to use the MiFlash tool (2017.4.25) but my device isn't detected when I click Refresh, and the fastboot mode displays "press any key to shutdown...". I've tried many different drivers as I thought it was a driver issue, but now I'm not sure.
Any suggestions? Thanks!
Flash with fastboot rom. Follow my thread
devcon69 said:
Flash with fastboot rom. Follow my thread
Click to expand...
Click to collapse
I tried that, same issue. Also tried with the new 9.5.11 global rom update.
FIrst Flash MIUI Nougat Rom
http://bigota.d.miui.com/V9.2.7.0.NEIMIEK/miui_WHYREDGlobal_V9.2.7.0.NEIMIEK_b6ab1f7b5b_7.1.zip
after flashing this Rom and setup complete then flash the leaked official Global ROM, 9.5.6. Otherwise you won't be able to pass the setup screen in latest Oreo Rom.
Trewyy said:
I tried that, same issue. Also tried with the new 9.5.11 global rom update.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.
devcon69 said:
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.
Click to expand...
Click to collapse
Ah thank you, I was flashing through recovery. With that being said, MiFlash doesn't detect my phone in fastboot, even if I can normally flash to it through fastboot if I were to open a terminal. Clicking "Refresh" in MiFlash Tool just disables fastboot. I realize its unrelated to your own tutorial, as its probably some fault on my computer. Thanks for your replies!
I've owned my A5 2017 (SM-A520F) for about 18 months now. I rooted it and pushed a slightly modified rom to it pretty much as soon as I got it.
Up until a few days ago the battery drained and it turned off. I expected it to boot right up after charging it but the device now is FRP locked and won't boot.
I've searched far and wide and it seems that the only reasonable solution to do is to flash the phone with stock firmware and the issue should resolve but I'm having troubles with this.
Finding stock samsung firmware is not easy. The first FW i tried resulted in an error about some version mismatch, which lead me to believe that i need a marshmallow rom instead of nougat as the phone had marshmallow on it when i bought it. The second firmware didn't result in an error - but the flash (in odin) finished in 0.2 seconds and was a "SUCCESS" but AFAIK nothing was done to the device.
I'm OK with losing the data on the phone, i just want it to be operable, so i can keep it as a backup device.
What are my options?
Finding an official firmware is not hard at all. Open this link: https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ , find your country and download the latest firmware. After you have downloaded the firmware, extract it and put all the necessary files in Odin (be sure to have the latest running version). The flashing should take about 5-10 minutes, I don't know why or how your flash finished in 0.2 seconds... I hope I helped you
I guess the title already says it all, but just in case:
I tried to put LineageOS on this used XZ2 I bought a few days ago, everything went fine until side loading the Lineage image. Appaerently there as some data corruption and the installation failed halfway through... unfortunately the phone dropped out of recovery mode and has been stuck in a boot-loop ever since.
I can still access the phone via fastboot after the battery runs out and before it goes into its bootloop again, even managed to flash the recovery image (in boot_b if that's important) - but somehow seem unable to actually boot into recovery... given that I have still access via fastboot, the situation might still be salvageable?
also tried booting the phone-specific twrp via fastboot boot <twrp>.img but that sadly also sent me back into the boot loop.
fastboot reboot recovery also sends me to the bootloop
any other ideas?
Did you format (not wipe!) /data before booting LOS?
Thanks for the reply!
I followed these instructions but something failed at the end:
Install LineageOS on xz2c | LineageOS Wiki
wiki.lineageos.org
but later yesterday I was able to find somewhat of a work around. Since from browsing this forum many people seemed to have had similar issues, here is what worked for me:
- break out of the reboot-loop and shut down the phone by pressing and holding volume up + volume down + power button
- the phone should vibrate about 3 times to confirm
- download your phones standard firmware via xperifirm
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5] NOTE: This thread is the only official source of XperiFirm! Websites like xperifirm.com and xperifirmtool.com were not authorized to redistribute my software! XperiFirm... Allows you to...
forum.xda-developers.com
- download new flasher
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
- put the phone into flashmode - press and hold volume down, connect the usb cable, and then also press and hold power, the phone should go into flash mode indicated by a green led
- follow the instructions (basically put the newflasher executable into the firmwarefolder created by xperifirm and execute
if everything goes well you should recieve a functioning (but wiped) device. still better than a paper weight
---------------------------------------------------------------
edit: tried to flash LOS again, but same error as first time (Error applying update: 28 (kdowloadoperationexecutionerror)
which prevents me from successfully installing LOS... I only found this:
[GUIDE][HOW TO FIX] 28 (ErrorCode::kDownloadOperationExecutionError) | 5 (ErrorCode::kPostInstallRunnerError)
In this short guide, I will explain to you how to easily fix the recovery error, the name of which can be found in the title. This guide is only a collection of information found on the Internet and a simple explanation of the problem. It was...
forum.xda-developers.com
which kinda explains the issue, but not how to fix it in my case on my device... any suggestions?
edit2:
tried over 10 different firm wars ranging from the latest 18.1 to some older 17.1, tried via the official lineageos recovery image and also via twrp.. always the same result... installation failed
I have been trying for over 3 hours now... but I just can't find (nor fix) the issue)
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
iitzzMalice said:
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
Click to expand...
Click to collapse
Hmmm.. I just realized you're using a different phone than me. My bad. Hopefully it helps that i had the same issue and resolved it by using oxygen firmware. Good luck to you!
thanks for the response
I think I identified the issue, which might be very much firmware related.
Essentially because my phone has the wrong stock firmware and LOS refuses to install on that despite being the same hardware as the "supported" firmware.
so what I probably need is a way to install H8314 firmware on an SO-05K model... there's a thread about that, but so far I have not been successful
(alternatively altering the LOS firmware itself to install on the SO-05K...)