Hi, I'm currently running CM12.1 on my LG G2 D802 and I'm planning to upgrade it to CM13. I did some research but since I'm a newbie I would like to ask for some confirmation that following steps are correct:
Download and store following files in device memory:
TWRP BUMP Recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Hybrid Bootstack: http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Latest CM13 Release: https://download.cyanogenmod.org/get/d802-snapshot.zip
GApps for ARM/6.0: http://opengapps.org/
Reboot to Recovery (currently TWRP v2.8.6.1 )
Flash TWRP BUMP recovery
Reboot to Recovery
Flash Hybrid Bootstack
Reboot to Recovery
Create a backup of currently running system (CM12.1)
Factory Reset
Flash CM13 and GApps
Reboot to System
Did I miss something?
It worked.
Thanks for simplified steps... the ones shown in the Official CM13 thread were a bit confusing. Going to try this now myself
Just some feedback, this worked 100%. Thanks again
i perfer to do a full wipe. factory reset then wipe dalvik, system, data and cache but leave internal storage alone.
Update: i Fixed it by myself. Thanks
Hello! i am new here. i have samsung galaxy s3 neo i9300i. updated to android 4.4 with TWRP installed. i wanted to flash cm 12.1 rom by "Rox". but he wrote in order to flash one need to change the partition from ext4 to f2fs which i followed but didn't find in TWRP wipe>advanced>change partition there are others but not f2fs. because of this problem i have flashed the ROM & GApps & they both flashed successfully but when i rebooted the system, download mode appears. did rebooted several times but the problem was still there. plz help me. i want CM 12.1. THANKS
WTF.... Well, guy, you needn't to convert partitions, you only have to wipe data, dalvik and cache and flash ROM & Gapps.
If you want to convert, convert only data and cache... idk why you haven't this options... Well, I never converted this files, and CM12.1 is working fine.
not working
MarcusBS said:
WTF.... Well, guy, you needn't to convert partitions, you only have to wipe data, dalvik and cache and flash ROM & Gapps.
If you want to convert, convert only data and cache... idk why you haven't this options... Well, I never converted this files, and CM12.1 is working fine.
Click to expand...
Click to collapse
i tried but when i flashed, its stuck in the download mode. just like Rox wrote i did that. nothing more.
Did it by myself...
The problem with my phone was the TWRP 2.7.1.0, + due to root ota updates not worked, so i downloaded another rom 4.3, flashed it, updated to kitkat (ota), flashed TWRP 2.8.5, flashed the rom (cm 12.1 by rox), flashed the gApps... now it's working... Thanks...
Hi,
I'm using CM13 on my xiaomi redmi 2. This morning I installed the weekly update from 25th of December 2016 from the update manager, without realising that it was actually a new ROM, CM 14. The installation went well but gapps was giving much trouble. I decided to install gapps for Android nougat, but couldn't get into TWRP. In the end I installed a CM13 version from the update manager, in the hope that everything would go back to normal. As a result my phone went soft-bricked and wasn't even able to connect it with adb/fastboot from my desktop (ubuntu 14.04). Eventually I've managed to get into TWRP and now I have the possibility of wiping out Cache partition and Dalvik Cache, and install a ROM of CM 13, but I would like to investigate the chances of getting back the phone without losing all my data and apps. Is there anyway to do this?
Thanks.
Bro if you have got TWRP working right then you might already have CM 13 Zip files and gapps in the phone too. Try Clean Installing the Rom (ps don't select storage in advanced wipe option in Twrp , only select DATA , SYSTEM , CACHE & DALVIK to wipe). Your photos,videos,whatsapp chat backup will be saved. Try above method and let me know if it work. If not then you have flash MIUI rom using fastboot method to get your device back.
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps
Hi folks,
I need some help. I have had my X820 I ordered from bangood for about a month now. I have tried a variety of ROMs on this device, and twrp-3.2.1-0-x2.img. This morning I tried to give the latest lineageOS a try. I did the typical wipes, and flashed lineageOS & gapps. After reboot google play started to throw all types of errors.
I booted back into TWRP, and this time it would only mount in read only. I tried the trick to change the /data partition fron ext2 back to ext4, did wipes again, installed ROM + Gapp, reboot but still have crashing playstore and google background processes.
I went from an already installed AICP to LOS. I did do a complete TWRP backup of AICP beforehand. The weird thing is that if I do a complete wipe again from TWRP, and do a fresh install of Pixel Experience [AOSP] all works normally. And after I did another wipe from TWRP after Pixel Experience, and restored my AICP backup all is working fine now both in TWRP & AICP. Has anyone had something simular happen like this before?
You have to install the latest unofficial TWRP build in order to use see your /data partition with the latest LineageOS installed. It's indicated on the thread's FAQ.