Related
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.
I've found a few threads about this, but they all seem to be a bit misleading or outdated. I'm struggling to install the unofficial LineageOS on my Pixel XL from herehttps://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893.
Here are the steps I followed:
1. Unlocked Bootloader (Successful)
2. Flashed to NJH47F because that was what was recommended based on the GitHub page.
3. Fastbooted twrp-3.1.1-1-fastboot-marlin.img
4. Wiped Dalvik / ART Cache, System, Data
5. Flashed lineage-14.1-20171019-UNOFFICIAL-marlin.zip
6. Flashed twrp-pixel-installer-marlin-3.1.1-1.zip
7. Reboot
TWRP gives me a message that there is No OS Installed and on reboot one of two things happens of either a constant bootloop ( I never see the LineageOS boot screen) or it just hangs forever at Google.
I know that there is an A/B Partition Layout, but I'm still confused at fully understanding it and maybe that is the source of my problems?
If anyone could help me I would really appreciate it as I'm pretty clueless with the Pixel XL even though I've installed LineageOS on my Galaxy S5 and Nexus 7.
Flash twrp.zip after fastbooting to twrp (have a look also what slot you are currently using). Then boot to bootloader, change slot (fastboot --set-active=x, where x is the opposite slot you are currently in) (or use twrp that can change the slot, it was broken some time ago). Boot to recovery wipe system etc. Boot to bootloader and change slot again. Boot to recovery and flash lineage (reboot to recovery and flash the vendor and magisk if needed). So if you started with the A slot then lineage will be in the B slot (custom roms seem to flash to the opposite slot).
Oh my god, thank you so much. I have lineage booting correctly on my phone now. This whole partition thing was screwing me up, but now I have it sorted thanks to you.
If I decide to turn off my phone, and turn it back on, sometimes it changes boot slots and boots the default pixel os, which then causes the other os to become corrupted. How do I solve this?
Hi everyone not sure where to start but I'm having issues.
Since last year I was using DU v13.1 along with twrp, no problems. I decided to update to DU v13.5. I wanted a fresh install, so I flashed the August pie stock rom, then proceeded with the usual.. Boot in temporary twrp, install rom and twrp, reboot etc. Something went wrong somewhere.
Now it seems like only one slot is working, and it only boots into stock rom. I have reflashed the stock factory image and tried dueces script several times. Each time I get the exact same thing
To try and explain exactly what's happening, Twrp will temp boot up if I have one slot set active, but if I manually set the other slot active through fastboot and reboot, Twrp will hang at it's logo screen and not boot. If I am on Twrp on the working slot and try to switch active slots within Twrp and reboot, it says no OS installed and gets stuck. I've seen the 'your device is corrupt' message a few times as well which never happened before. So I switch back to the slot that boots, flash stock, temp boot Twrp, wipe system/data/cache, install DU 13.5 and the Twrp zip, reboot to recovery and hit the problem where it won't load Twrp on the opposite slot. I go to bootloader, switch back manually to the opposite slot and it won't load the custom rom. Switch back manually to the working slot and it'll boot onto stock rom and work fine.
I have rechecked if my bootloader is unlocked by trying the fastboot commands and both standard and critical come back as saying already unlocked, however if I look at 'getvar all' it says 'oem unlocked_no'. I don't know if this is something of note? In developer settings it says bootloader is already unlocked but is greyed out. Obviously I've lost root at this point too.
So at this point I'm going round in circles trying to reflash stock and repeating all the next steps but nothing is fixing.
I'm stumped at this point, don't know what else to try, so if anyone could help it'd be very appreciated!
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.
Last night I clicked the "update crDroid" button - intrigued by a custom ROM with OTA updates.
This morning it had downloaded and I absent-mindedly clicked "install"
An hour later it asked for a reboot and once clicked I got, in retrospect, the inevitable failure to boot. It just got to the crDroid logo and stopped there forever (or at least an hour).
So, into TWRP, but as it turns out, TWRP has been replaced by a crDroid recovery. Fine, root around, see I can sideload an image or look at logs. Notice I can "Switch slot".
Never having done that before and slightly riskily, I click it and change to slot B. The phone boots with no problem. Everything seems to be as it was just before the update.
Now, the problem - I don't really understand what I've done.
Is there anything I need to do now? I'm booted into a working phone, just unsure what happens if I even try to go to recover - will it be back to TWRP? Does Slot A have to be fixed?
Any advice appreciated!
This is the main advantage of A/B Partitionlayout = System Updates without risk of unbootable system.
While Android is still running, the System Update gets installed to the inactive Boot-slot and sets that Boot-slot as active (your next reboot is to Boot-slot _B).
What happened is that your bootloader detected that Android can't be booted, so it reverted to Boot-slot A (which is the old OS).
As to why the Update failed, I'm not sure. I don't know the exact details, but I think this procedure requires cooperation with the Recovery, however you had replaced crDroid's Recovery with TWRP, this may have caused the problem. I think it needed crDroid Recovery to finish the System Update.
You can manually download the ZIP and install it in TWRP.
Also: TWRP got replaced with crDroid Recovery, because System Updates replace the Boot-partition (which contains the Recovery). If you had previously patched the Boot-partition with Magisk, this also needs to be done again.
Have a nice evening, hope this was helpful