I've got a Galaxy Nexus GSM. Downloaded ROM via AFH through paranoidandroid.co. Wiped data, cache, and dalvik cache.
I flashed in 4.41 Final without gapps. I don't think it asked for my Google account info at first boot, but gmail, hangouts, play store, etc. were in the drawer.
Can someone verify?
hawkshot said:
I've got a Galaxy Nexus GSM. Downloaded ROM via AFH through paranoidandroid.co. Wiped data, cache, and dalvik cache.
I flashed in 4.41 Final without gapps. I don't think it asked for my Google account info at first boot, but gmail, hangouts, play store, etc. were in the drawer.
Can someone verify?
Click to expand...
Click to collapse
Did you have Gapps before install PA for example from previous ROM? If you didn't wipe system, your previous Gapps weren't removed.
We don't host the ROM on AFH... What's hosted on AFH is the gapps
#stayparanoid
pianistaPL said:
Did you have Gapps before install PA for example from previous ROM? If you didn't wipe system, your previous Gapps weren't removed.
Click to expand...
Click to collapse
Dirty flashing?
Assistance for gapps
Reboot to recovery
Do a BACKUP!
Format system partition, Data , cache.
Do a install of your rom.
If gapps is not fount download it (The latest version and specifically for your android version)
Install the zip if necessary
Check if the problem is solved
You didn't wipe the system partition from whatever ROM your coming from, which in my guess means they're still in the /app or /priv-app folder.
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
Hey guys,
i recently unlocked the bootloader of my VNS-L31 on B160 Firmware and afterwards rooted it, rebooted, everything ok. Then i did a factory reset in TWRP. Afterwards the SuperSu APP was gone and the Google Play store wasn't working anymore... Anyone with the same Problem?
Pretty strange thing.. I suggest you to install again the stock firmware or to try something like Google Services Installer.
Another thing you could do is to do a backup of the system partition, then flash pico package of Open GApps (Arm64).
Potato997 said:
Pretty strange thing.. I suggest you to install again the stock firmware or to try something like Google Services Installer.
Another thing you could do is to do a backup of the system partition, then flash pico package of Open GApps (Arm64).
Click to expand...
Click to collapse
Just FYO... I solved this by flashing stock recovery, doing a factory reset there followed by booting and instaling the google konto, then flashing twrp and rooting lol...
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
I just got my Nexus 6p running on resurrection remix 8.1.0 (7.2.0 gcc) and flashed the 8.1 gapps onto it. Everything ran smoothly and i can see all the apps, but whenever i try completing the setup or launching a google app, i get "Google play services keeps stopping" just over and over again. Anyone know of a fix?
Did you wipe system, data, cache before flashing? Have any substratum themes installed?
Exodusche said:
Did you wipe system, data, cache before flashing? Have any substratum themes installed?
Click to expand...
Click to collapse
Thanks so much! I just went through and re installed everything making sure to wipe dalvik and cache and it seems to have worked!