I keep getting : Google Play services has stopped, after installing official CM12.1 nightly for vs980. Did a wipe of cache,system,data, dalvic. Flashed xdabbebs 12b bootstack. Reboot into recovery. Installed 20150609-nightly-vs980, gapps-5.1.x-minimal-edition-signed.zip. Reboot system. I have been running AICP 9.0. I haved tried going to apps after booting up and clearing cache for Google play services,no help. Also tried gapps-5.1-2015-06-02-15-19.zip from wiki.cyanogenmod.org (arm vers.). Any thing I am doing wrong?
Related
Just recently wiped my phone, cache and dalvik cache, installed the latest CyanogenMOD 10 Nightly, Seeder, Gandalf Kernel and the V10K Baseband patch on my phone along with the 4.1.2 Gapps and for some reason I am unable to access the Google Play Store, giving the message "Unfortunately, Google Play Store has stopped." Sorry I can't go into further detail but that's about all I know, I tried restoring to the last Nightly I was using that worked with the Play Store, but as far as I can tell, it's still hosed, any help would be greatly appreciated.
Maybe you did it wrongly.Boot into recovery mode..wipe data/cache/dalvik..
1)flash cm10 latest rom..
2)flash 4.1.2(!) Gapps
3)flash v10 baseband..
Reboot..
(This worked for me)
Edit
When you finish this,wait for your phone to boot,and set it up.After that,you go again into recovery and:
1)Flash Gantalf kernel
2)Wipe cache/dalvik
Sent from my LG-P700 using Tapatalk 4 Beta (VIP)
I had the same problem, only google play didnt work. I just downloaded google play.apk from internet and installed it on the phone. Thats it
I decided to multiboot my device with CyanogenMod 10.2.1 and after realising it didn't come with the google play app I did my research and found out how to go about installing it.
I booted into recovery mode and installed the Gapps.zip from SD but it still doesn't show up at all in CyanogenMod.
I multibooted using Patcher App.
With CyanogenMod Nightly 10.2.1 into the first multiboot slot.
The gapps i tried to install should be the correct version for the cyanogenMod - Gapps.
and i'm using the ClockworkMod recovery to install gapps.
I believe it is probably installing it for my main OS.
Any ideas on what I can do to get the Google play store onto the OS?
I'm having the same problem, after updating my S4 I9505 to the latest stock Samsung 4.4.2 ROM, I installed the CM11 with the appropriate Gapps, but the apps are not working, after installing the Gapps only Gmail appears, and it doesn't even open the app, and also no option to add a Google account.... tried several different CM versions and several different Gapps version also.
I'm currently trying to update my phone from CM11 to CM12 using TWRP. In TWRP, I factory reset my phone, then flashed the latest CM12 nightly build. However, when I try to flash gapps, TWRP says that I have a status 7 error and it fails. If I try to run my phone normally, I get errors saying that Google Play Services has stopped, Setup Wizard has stopped, etc. I have no idea where I'm going wrong, how can I fix this?
hruweg said:
I'm currently trying to update my phone from CM11 to CM12 using TWRP. In TWRP, I factory reset my phone, then flashed the latest CM12 nightly build. However, when I try to flash gapps, TWRP says that I have a status 7 error and it fails. If I try to run my phone normally, I get errors saying that Google Play Services has stopped, Setup Wizard has stopped, etc. I have no idea where I'm going wrong, how can I fix this?
Click to expand...
Click to collapse
What gapps package did you download? If it is a larger set of gapps, sometimes there isn't enough space in /system to install everything, so you have to use a more minimal package, and download the additional apps from the Play Store.
Hey guys! So I just flashed cm13 on my zen5. And I'm having a problem with gapps. I have downloaded the x86, 6.0 pico version of it. The rom flashed fine i suppose. The issue is with gapps. As soon as I started to flash gapps, 3 lines of error came and went immediately. After that once again I tried and it showed it was done. I booted the rom after clearing dalvik and cache.(I'm dumb and I forgot to clear system data and all). So now, as soon as the OS boots, it gives me force close. For every single app. What to do? Please help.
UPDATE: UPDATE: The error was with TWRP it seems. None of the files are flashing through TWRP. Can you give me the latest/stable TWRP link for it? For the time being, I have no google play services whatsoever in my device. The rom is from dgadelha I think. CM13.1 20161205
TWRP 3.0 links
https://www.androidfilehost.com/?w=files&flid=52033
TWRP 2.8.x links
https://drive.google.com/file/d/0BzMGgN-tWY2zQnVucDdIUFlQdHM/view
https://drive.google.com/uc?export=download&id=0B05UM2q8MdJFb0VrV2oxTG5rTzQ
While I was on XOSP I faced the same problem so I had to go to 2.8.x version.
I have problem with flashing LineageOS second time.
I used LineageOS before. And I've decided to flash the updated nightly build. And I do the clean flash, wipe system, and data. Flash ROM, and then flash GApps again. (I knew after that I don't have to clean flash to update my nightly because it will erase your previous google account settings)
After installation I rebooted into the system. In the first setup wizard, At Google account login, it says "checking info..." and then crashed with the message "Google Play services has stopped". I've tried many flashing methods, and also flash ROM without GApps. But it same in the system. I can't add google account and can't open the playstore either. I tried with different build and different GApps packages and it went fail and fail again. Please tell me if you have any ideas so I could run 7.1.1 again. I would appreciated it. Anyway I'm at CloudyG2 3.3 right now and using TWRP blastgator 3.1.0-1.
Thanks.
That's why it's called "nightly".
http://wiki.audacityteam.org/wiki/Nightly_Builds :
Nightly builds are alpha builds from the latest development code. By their nature these builds are likely to contain bugs or might even cause data loss.
Click to expand...
Click to collapse
Sorry to say, but you got to deal with it till the next build shows up.