Hi,
I'm completely new to customROMs at all, so please bear with me..
So, first I tried to flash Cyanogenmod 13 nightly on my G3 which failed with "system partition has unexpected contents after ota update". At this point I was unable to get past the "LG powered by Android" boot screen, but I figured that was okay, since the install failed. I was running Android 5.0 beforehand and after a quick Google search I decided to try CM 12.1 first.
So I started again with wiping the device and installing CM 12.1 which succeeded. However, I still couldn't get past the LG boot screen. I tried wiping and reinstalling CM 12.1 several times with no success.
I was following the official guide rooting my phone and using LG G3 AutoRec-Lollipop to install TWRP.
I don't really care about my data (it's all in the cloud anyway), but I'd like to get my phone to work again. Any ideas?
Thanks in advance!
what's your current twrp version?
Related
Hello,
I am brand new to the rooting/modifying process but managed to successfully root and install cyanogenmod 10.2.0 on my device a couple days ago, thanks to a newbie-friendly forum found on this website.
I searched for a cyanogenmod update using the auto-installer and found, today, that there is a newer version available, 10.2.1. Problem is, when I proceed with the installation, the process commences (seemingly without a hitch) but when the phone finishes rebooting, the phone info shows I am still using the 10.2.0 version of cyanogenmod.
I am confused as to why the installation is failing to update my phone and would appreciate any guidance!! I realize there are ways to manually update, but I would rather first understand why the auto-updater is not working before I try to mess with it manually.
Thanks!
Specs for my phone:
Verizon LG G2 VS980
Kitkat 4.4.2
Rooted
Note: You'll notice that I put the names of webpages because I'm not allowed to put the actual links. To find them, just search them on Google
My rooted LG G2 was working perfectly fine. My friends has a Galaxy S III, and installed cyanogenmod successfully onto his phone. Wanting to install cyanogenmod onto my phone, I attempted to download the Cyanogenmod 11 snapshot, the 6th download on the cyanogenmod wiki page for installing onto the LG G2 VS980. I then wiped everything on my phone EXCEPT for the Internal SD using Team Win Recovery (TWRP). Then, I flashed the cyanogenmod zip file onto my phone, and rebooted it. I followed everything this youtube video, called: "Install CyanogenMod 11 / Android 4.4 KitKat custom ROM using TWRP" said to do. However, when I rebooted it, it got stuck in a bootloop, and I the button combinations to reboot into recovery do not work. I have come to the conclusion that I installed a version of cyanogenmod that doesn't work. I want to know if there's anything I can do to get my phone working again, and if so, what.
Any help would be greatly appreciated!
Thanks!
Hello guys,
It's been a while since the last time I visited the SGS3 section, over a year ago I remember updating the bootloader in order to upgrade/flash to 4.4.4 which went very smooth and was a success. I gave the phone to a sibling who has been very happy with it for the last year and a half. Lately, the phone has been very unstable with the 4.4.4 KitKat ROM, WiFi doesn't turn on, Bluetooth is unstable, Unstable apps/Force closes. I tried a wipe/factory restore and re-flashed the ROM but the problems persisted.
I did a little research and liked what CyanogenMod is doing and since they are actively supporting the phone I decided to flash CM12.1 and the provided Open Google-Apps, CM12.1 flashed successfully but Open Google-apps refused to install, CWM displayed (Section 6) error which upon research it is common with CWM and the solution is to flash TWRP. I booted with CM12.1 in order to install TWRP Manager through the APK and flash TWRP but it force-closed when it searched for the device model. WiFi was working but Bluetooth was still unstable.
I would like to know what would be the best way to proceed in this case, I would like to upgrade the recovery to TWRP and flash CM12.1 or any other stable Lollipop ROM.
Thanks,
Oscar
absolute all credit to @audit13.
http://forum.xda-developers.com/showthread.php?t=3313734
perhaps this will help.
"err on the side of kindness"
As title says when I flash or install a recovered LG based rom the handset gets into a bootloop. Lollipop or MM doesn't matter.
I see the BIOS type of screen for a few seconds then 3 seconds of boot animation and back to BIOS.
Cyanogenmod 13 based roms work just fine.
background: After receiving MM ota update rooted and downgraded to lollipop. Installed a modem file in the process as well.
Then I decided that I don't like it either. FLashed cyanogenmod straightaway.
Then flashed genesys rom which is LG based 6.0.1.
Still no problems.
Installed xposed framework and the bootloops started.
Then I run the xposed uninstall script, wipe everything and install LG MM rom. bootloop again.
Sorry for the long post. Didn't know which detail is relevant so wrote it all
Any help would be much appreciated as I am stuck with cyanogen...
Try to go back to stock with lgup
lgup doesn't recognize the handset when CM is installed.
Anyway finally found a solution after trying every trick in the book. Basically flashing modem, boot and bootloader solved the problem.
Now I need to find a way to flash xposed framework without bricking the phone.
Dear Xda community,
i could really use your help.
So i had a working cyanogenmod 14.1 rom on my nexus 5X. I wanted to have cyanogenmod 13.0 on it, because of the theme engine.
So i made a backup using twrp. Then i completely wiped my phone. (twrp>wipe>advanced wipe>chose everything>executed).
Then i flashed cm 13.0. thereafter i booted my phone, but i couldnt get past the "google" screen. Then it booted again, but it wouldnt get past the "google" screen. And so on.
I tried wiping my phone and restoring my backup, but the same issue occured again. This issue keeps coming back no matter what I do.
I dont know how the fix this, please help.
thank you in advance. ~Jens
It sounds like a bootloader mismatch problem. Going from CyanogenMod 14 (Android 7) to CyanogenMod 13 (Android 6). This should theoretically solve your problem, although I haven't tried it. Flash marshmallow (Android 6) Factory image from https://developers.google.com/android/images#bullhead. Pick the last marshmallow release, MTC20K, let it boot once, do a factory reset, unlock bootloader, reinstall twrp and then try CM13.
Sent from my Nexus 5X using XDA-Developers mobile app
The bootloader is rarely a issue. Most likely the vendor is the culprit. Flash any recent MM vendor an it will let you boot.