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 own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.
Flash correct stock firmware in sptools
arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.
Hi Everyone,
I would gladly accept any help that is being offered. Thanks in Advance.
So I am not new to flashing my phones but Xiaomi has been one of the most frustrating experiences that I've ever had. So I flashed my phone with the Pixel Experience Rom but I wasn't getting 4G with it and I couldn't recall if I was getting 4G with the original MUI so i decided to flash MUI firmware .
So, Not really sure what I did wrong because i believe I could flash the firmware without any problems but guess not. So it flashed successfully and my phone rebooted into Fastboot and will not load into the phone. So booted into recovery and Red Wolf TWRP is asking for the encryption password which I normally enter and I do it again and behold it's telling me that the password is wrong which is am sure it isn't.
So I am unable to use Red Wolf TWRP to flash anything since i can't mount the storage section because of the encryption and tried flashing the phone with MiFlash but doesn't seem to work. It is telling me that the image and device is a mismatch which I don't believe since I've flashed those ROMS before.
So any helpful advice would be appreciated.
I guess you need to flash stock firmware in fastboot mode. Download fastboot rom from mi website. Power on your phone while pressing volume down keep pressing power button for some seconds to enter fastboot mode. Connect it with your pc and upon connection you will heard plugin sound from pc. Extract downloaded fastboot image and double click on flashall. Wait for process to complete. Your device will auto reboot upon completion
Sent from my LINQ X70 using Tapatalk
bcat00 said:
Hi Everyone,
I would gladly accept any help that is being offered. Thanks in Advance.
So I am not new to flashing my phones but Xiaomi has been one of the most frustrating experiences that I've ever had. So I flashed my phone with the Pixel Experience Rom but I wasn't getting 4G with it and I couldn't recall if I was getting 4G with the original MUI so i decided to flash MUI firmware .
So, Not really sure what I did wrong because i believe I could flash the firmware without any problems but guess not. So it flashed successfully and my phone rebooted into Fastboot and will not load into the phone. So booted into recovery and Red Wolf TWRP is asking for the encryption password which I normally enter and I do it again and behold it's telling me that the password is wrong which is am sure it isn't.
So I am unable to use Red Wolf TWRP to flash anything since i can't mount the storage section because of the encryption and tried flashing the phone with MiFlash but doesn't seem to work. It is telling me that the image and device is a mismatch which I don't believe since I've flashed those ROMS before.
So any helpful advice would be appreciated.
Click to expand...
Click to collapse
So just format storage, it will be no longer encrypted. Then mount storage in twrp, paste your rom of choice from pc and flash it. Unless im missing something here
A mismatch you say? hmm I have had this before and I managed to flash the rom without issues deleting some lines in a rom package. It's quite simple, just follow this little tutorial: http://en.miui.com/thread-178314-1-1.html
Thanks for the responses. I followed this guide here to resolve the issue.
https://forum.xda-developers.com/re...-to-unbrick-redmi-note-5-pro-bricked-t3840455
Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!
Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!
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.