Database Users

Cyanogenmod 12.1 Google Play not working

Hello, I've flashed cyanogenmod 12.1 onto my galaxy S4 and installed gapps, but getting a Google play has stopped along with other Google services. Can anyone let me know what I'm doing wrong? Steps I did:
1. Go into recovery
2. Wipe data/factory reset
3. Installed cm-12.1-20150927-NIGHTLY-jfltexx.zip from download.cyanogenmod.org
4. Install gapps from opengapps.org (ARM/5.1/Nano)
5. Wipe cache partition
6. Wipe dalvik cache
7. Fix permissions
8. Reboot
Thanks!

Maybe it's the fix permissions part.

GDReaper said:
Maybe it's the fix permissions part.
Click to expand...
Click to collapse
Yes I also tried without that step but unfortunately the same errors.

After switching over to TWRP, everything works! So if anyone is having the same issue, switch to TWRP.

Yea twrp is recommended for flashing cm rom especially latest version

Soft bricked when updated to CM 14

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.

Can't flash oreo roms

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

Most custom roms dont work for me - Am i doing something wrong?

Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!

Arthur King said:
Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!
Click to expand...
Click to collapse
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs

Wolfcity said:
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c

Arthur King said:
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c
Click to expand...
Click to collapse
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs

Wolfcity said:
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do

Arthur King said:
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do
Click to expand...
Click to collapse
Best may be to ask a ROM developer by PM what could be the problem. I'm still on stock so my knowledge about it is more theoretical.
Sent from my Mi 9T using XDA Labs

edit : nvm wrong thread

OS corruption? Can't seem to format to start with a fresh install.

I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob

bdushok said:
I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob
Click to expand...
Click to collapse
It's very likely caused by TWRP, I said multiple times to NOT use TWRP for installing OTAs exactly because of things like this.
TWRP is now discontinued anyways