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....
Related
I've installed the latest Cyanogenmod, the latest CWM 3.0.2.4, fixed permissions in the rom manager, and I still cant get the gapps to install. I attempted to install the suggested gapps for cyanogen 7, and no luck.
When I attempt to install it reads:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
When I select to enable signature verification, it then reads it failed signature verification.
The process I use to attempt to install the gapps is, I open the Rom Manager, select reboot into recovery and then install zip file from sd.
I've tried several different versions of the gapps, and still no luck.
I have researched this for the past few hours and I can not get this to work at all. I do have it rooted, everything else installed fine, with no complications. But I am very much stuck at this point. Any help is greatly appreciated.
I figured it out on my own. When you use CWM3, just go to download rom instead of manually doing it.
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!
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
Hello,
I've been trying to install CM13 with gapps using TWRP (using fastboot boot, because my device is S-ON), and though cm goes through ok, flashing gapps returns Updater process ended with error: 2 and I can't seem to be able to google this problem out. Anyone knows what that means or where I can find TWRP error code meanings?
nvm, was wrong platform gapps