Hi all
After upgrading my Xperia M to CM 13.0 Google Play Services stopped working. I realized that only open gapps were supported on v13.0 so I downloaded the ARM, 6.0, pico version. Then I rebooted to recovery, and tried to install with
Code:
adb sideload open_gapps_[...].zip
Installation failed with an error "insufficient storage space", which is obviously not the problem since I have more than a Go free space on internal storage.
Already when I installed CM 12.1, I had to use the other gapps package (here), because it gave me the same error.
I tried to read the install log, but I can't find it (when I type adb logcat it just says "waiting for device" but nothing happens).
Could anyone be of any help?!
Thank you very much
Edit: I managed to install the open gapps .zip after wiping everything (data, cache, media) and reinstalling the latest nightly cm 13.0 build. It works, but it's still a bit annoying to have to do that. So if anyone had an idea what went on, it's still welcome!
Related
Hi, can someone tell me which GApps install on Samsung Galaxy S4 Mini GT-I9195 with CM12.1. I have tried a lot of GApps and none of them seem to work, everytime I reboot I get a message saying "Google Play Services has stopped working".
If I do a fresh install formatting /system and only install CM12.1 everything works just fine. But always GApps crash my phone. I don't know what to do. Please help me.
Hi,
I have almost (unfortunately google partner setup has stopped) the same error today after flashed clean snapshot but i resolved with this method:
Empty the Cache of the system app Google Play services
Navigate in the following submenu:
Menu --> Settings --> Applications --> Application Manager --> tab "All"
Search here for the entry "Google Play services". Tap it once to display detailed information about this app on the screen of your smartphone. In this window, you will now find a button with "Clear Cache". Tap on the button, so that the cache is flushed. Then restart your Android smartphone.
Click to expand...
Click to collapse
I've always used GApps recommended by the developer, in this case i used this:
Open GApps CyanogenMod - use Mini, Micro, Nano or Pico it your choice what app you want installed directly.
Good luck
Hi,
I've got just this problem, following on from upgrading from CM11 (long-time user of this) to CM12.1. I've found huge numbers of posts, both here and elsewhere, with people experiencing GApps crashing constantly on start-up with CM12.1. Most of the responses recommend different sources of GApps, or different orders in which things should be wiped/formatted and then installed, etc. I have tried cm-12.1-20151007-SNAPSHOT-YOG4PAO336-serranoltexx.zip and cm-12.1-20151008-SNAPSHOT-YOG4PAO34N-serranoltexx.zip. I've tried gapps-L-5-1-15, gapps-5.1-arm-2015-07-17-13-29, open_gapps-arm-5.1-mini-20151018, Slim_mini_gapps.BETA.5.1.build.0.x-20151016, tk_gapps-modular-mini-5.1.1-20151004-signed. I've done a full format of /system on each re-install, plus formats of /data, /cache, Dalvik cache (both before and after installs of CM12.1 and various GApps). No matter what, I always have the problem of all GApps crashing continuously as soon as the phone boots.
I'm absolutely stuck. I'm all googled-out. If anyone can offer any more things for me to try in order to get GApps installed and working under CM12.1 on my i9195, I'd be really grateful.
UPDATE
________________________________________
Problem fixed! The issue was CWM Recovery. I had v6.0.3.something (I think) installed from quite some time ago. I found a post where someone stated this was the cause of the GApps installation problem. I replaced it with twrp-2.8.6.0-serranoltexx-f2fs (not easy, since my Linux laptop didn't want to see the phone in fastboot mode - eventually had to boot up a Win7 machine and install Odin v3.09). From there I was able to wipe everything, install cm-12.1-20151008-SNAPSHOT-YOG4PAO34N-serranoltexx and gapps-L-5-1-15, and then everything worked!
I have no idea why one recovery image would work and the other wouldn't. I'd have thought installing a zip was not something that could go wrong. Clearly not!
Hope someone finds this info helpful.
Ok so I got my E980 rooted via towelroot, then used the freegee app to install loki, then I used flashify to install the CM recovery listed below, planning to flash the matching cyanogenmod rom:
snapshot Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980.zip (243.15 MB)
sha1: 9a4773d2fca0658edb2683079ce96307863a9fd0 Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980-recovery.img
sha1: 1095ea774ff2347fb3a2884045aa4a47e6833893 2015-10-07 02:08:36
I rebooted into the recovery and it wouldn't flash the cyanogenmod 12.1 rom at first, saying that I had an incompatible system installed, so I did a factory reset and then tried again and it installed the CM 12.1 ROM without errors, however it wont boot into it. All I can access is the CyanogenMod recovery and the factory wipe screen, I cant seem to boot into a rom even when it installs without errors, I cant get into download mode no matter what combo of keys/plugging in I do, even though it worked fine before.
Any thoughts or Ideas? I am totally lost here.
When turn on the phone it says:
Secure booting Error! Cause : Device Unlock!, so Boot Success!!
When I try to flash the TWRP zip that is floating around (2.8.1 I think) it says:
Finding update package.....
Opening update package...
Verifying update package...
E:Footer is wrong
E:Signature verification failed
Installation aborted.
When I turn on ADB mode through CyanogenMod recovery
Adb devices: Lists the device (99d3b89c sideload)
Adb usb: Error : closed
I have tried CyanogenMod 10.2.0, 11-20141115, and 12.1-20151007, and tried them before and after every kind of wipe available through this recovery, and they all install without error then reboot back to the recovery.
Is there another flashable recovery around for this phone I could try? I just don't see many in zip format.
Finally got it working. Threw every flashable recovery I could find at it, finally got Phillz touch to install and work from the CyanogenMod recovery. Phillz wouldnt install a working rom, but Phillz did allow me to flash CWM 6 something, which allowed me to install 2.8.1 TWRP, which couldnt see my microSD card, but it did allow me to copy 12.1 CM to my internal SD card from my computer via USB and to flash it and have it actually work. After I booted into CM 12.1 I had to fight gapps for a while, the open gapps pico and nano for 5.1 arm didnt work, but I got the Gapps from the slim rom to work after rewiping the system to remove the open gapps.
After that I finally manager to get flashify, supersu, and busybox from the store. Used flashify to upgrade to 3.0 TWRP. I still cant get into download mode, but pretty much everything else is working now.
Hi all, I'm not really sure if this is correct section to post this but has anyone else had issues with installing the latest (2016-03-16) CM13 release on their Nexus 7 flo device?
The steps I used to flash are as follows:
1. I used WugFresh NRT "Root" option with "Also flash custom recovery selected" to root my stock android 6.0.1 install and install TWRP 3.0.0.0
2. I then booted into recovery and copied over the CM13 zip and the (2016-03-16) version of OpenGapps Micro to the device.
3. I then did a factory reset from within recovery and flashed the CM13 zip which installed as expected.
4. Then I tried to flash the openGapps zip. I selected the zip and swiped to install and it stayed on "no md5 file found" for about 15 minutes. After this it installed and everything seemed to be fine until I rebooted into the OS.
5. When the tablet booted up for the first time and finished optimizing 96 apps* it came up with the CyanogenMod setup has stopped working error.
I know there is a work around for this but, as I had CM13 installed on this device before with no issue, I decided to dig a little deeper...
1. I downloaded TWRP 3.0.0.0 manually and flashed using fastboot. RESULT: Exact same thing with the long pause when installing Gapps followed by the CM setup error
2. I downloaded CM Recovery and manually flashed using fastboot. RESULT: Cannot install Gapps at all this time due to it not be compatible with CM recovery
3. I tried to ADB sideload using TWRP 3.0.0.0. RESULT: CM13 installed normally, but again, the same long pause with Gapps install followed by the CM setup error
4. By this point I'm fairly sure there is some issue with Gapps so I check the MD5 of the file and its fine so I download an older version and try to flash that... RESULT: Same thing as before
5. Next step, different Gapps version... So I download the "mini" version of Gapps instead of the "micro" one, check the MD5 and then try to flash. RESULT: Again huge pause during install follow by "Error 70: Insufficient space"
6. I setup a gapps config file on the tablet to tell the Gapps installer to install the Micro package in test mode so nothing should change. RESULT: This file is apparently completely ignored and I get the same result as before.
7. Finally I decide to fastboot flash TWRP 2.8.7.0 and voila! RESULT: CM13 installs and the Gapps micro install loads straight up installs everything at the expected speed. When the tablet reboots there are no error and everything seems to perfectly okay.
* As an aside I have a LG G3S/Beat which has been flashed with CM13 and OpenGapps Mini using TWRP 3.0.0.0 with no issue as all. When this device booted up it only optimised something like 24 apps. Can someone explain why my nexus 7 has to optimize 95 and the LG G3S only has to do 24?
TLDR; TWRP 3.0.0.0 doesn't like Gapps on the Nexus 7 flo
So has anyone else had any issue like this with their devices?
Regards
Nathan
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Metrotor said:
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Click to expand...
Click to collapse
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
LS.xD said:
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
Click to expand...
Click to collapse
I wiped everything except internal memory. And although it gave me some error, I was able to reflash CM13 and Gapps to get the phone working again. Thank you so much!
Hi, I've been trying to install OpenGAPPS for weeks. I've tried using both Lineage Recovery and TWRP but while both LineageOS and SuperSU seem to install smoothly, I still can't install GAPPS (v9 on ARM64; tried both Pico and Nano) using either method without getting zip errors.
Anyone have any thoughts?
"Error Code 64"
Forgot to mention, TWRP gives me "Error Code: 64" when I try to install Gapps....