I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
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.
So two days before Android Oreo update released (RETEU channel). I tried to flash Magisk cause i needed root access but then i realized that the Bootloader was locked and i unlocked it. Everything was ok until i tried to flash a custom recovery (TWRP) but after that everything was way too complicated. I flashed TWRP but everytime i was trying to restart my phone and get there it was replaced with the stock recovery. I tried to find something online and i did here in XDA. Everything was working and i said that is time to flash Magisk, i rebooted my phone in recovery mode and after that i flashed Magisk, but after that my ROM was destroyed and i didnt even had a backup (yes i know i should have done that, but i totally forgot about it). I said ok, the phone was released almost a year ago and there should be a Stock or Custom ROM online, i did find a couple of them but everytime i tried to flash them i was getting an error, i found the problem, my TWRP was a 32bit version and i changed that to a 64bit, but no other ROM except Lineage 15.1 was working. After flashing Lineage Os I found out that my fingerprint sensor wasn't working, my flashlight too and the camera was awful. I went back online and tried to find a stock ROM but i couldn't find anything, i tried a stock 7.1.1 and stock 8.0 but none of them was working. The last thing that i did was trying to flash it with ADB and after that my phone was working for 10 min until i got a security update that after the installation my phone didnt even boot again, i cant boot it, it isnt showing anything, no vibration, no sound, nothing Please help!
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 guys,
Not sure if it's the right place to ask for help, but I really hope it is.
TLDR: been using an Android 8.0 custom ROM for ages (3 years now), thought I'd update to 10, but I couldn't through TWRP 3.5.4; after that I've read that I should install Oxygen OS 9.0 first, and then I'll be able to update to custom ROM 10.0.
So here I am, trying to flash an official ROM based on XDA (which should be working as it did work for lot of people) - it does work, although when I'd try to boot the system, it's stuck on the OP logo for a min, and then I'm dropped in the bootloader.
So going back to TWRP (yes, it did not overwrite TWRP for some reason) - doing the exact same stuff, nothing happens. Tried the unbrick tool too, but it's stuck on Param Preprocessing for 30 mins. Still have TWRP on my phone, and I can boot into TWRP.
Question: what the frick should I do now?
Hoping for some helpful answers! Thank you in advance. <3