Database Info

[Q] Latest gapps not installing on latest cyanogenmod

I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.

I have xoom wifi. the version of gapps I have is:
gapps-unified-jb-20130220-signed.zip
it should be somewhere in the portal as that's where I downloaded from. see it may work for you too.
hadji369 said:
I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.
Click to expand...
Click to collapse

hadji369 said:
I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.
Click to expand...
Click to collapse
Not sure if this is an option for you, but have you tried running gapps-jb-20130105-EOS-XOOM-ONLY.zip?

atloops said:
Not sure if this is an option for you, but have you tried running gapps-jb-20130105-EOS-XOOM-ONLY.zip?
Click to expand...
Click to collapse
I did try this, just for the sake of trying something as I am having the same issues as the OP.
I flashed the latest nightly cm-10.1-20130330-NIGHTLY-stingray.zip on my Xoom and then tried the EOS version of GApps. It just bootlooped numerous times. I flashed the ROM, then flashed GApps. I cleared cache/data/dalvik with no luck, it just brought me back to recovery.
Any ideas? I know it is a nightly, so I am not too worried about it. I am just playing around.

You should try the new unified gapps for Cm, the link is listed in the OP of the cm 10.1 thread. Also, if you are using cwm recovery, try twrp. Your recovery could be causing issues
Sent from my Xoom using xda premium

Thanks! I will give that a try when I get home. Went straight to the CyanogenMod site to get GApps so I missed that.

Well, I made a very simple mistake. I only read the directions partially, assuming everything would work like flashing my phone or Nexus 7. I wiped data, wiped dalvik, installed the ROM and then installed GApps. I booted my Xoom and of coarse, even with the unified version of GApps, it still did not work.
I repeated the process but did not install GApps. I let the device boot and then went back in to recovery. I flashed GApps and rebooted and it works perfectly. I did not try another version of GApps this time.
Lesson learned.

groggie said:
WelI, I made a very simple mistake. I only read the directions partially, assuming everything would work like flashing my phone or Nexus 7. I wiped data, wiped dalvik, installed the ROM and then installed GApps. I booted my Xoom and of coarse, even with the unified version of GApps, it still did not work.
I repeated the process but did not install GApps. I let the device boot and then went back in to recovery. I flashed GApps and rebooted and it works perfectly. I did not try another version of GApps this time.
Lesson learned.
Click to expand...
Click to collapse
Download Google appstore zip file by itself.. After flashing gapps, flash the appstore by itself as well.. Worked for me

Latest Nightly issue Camera+Gallery
I'm using the 20130609 nightly in my Everest, but re-flashing the Unified Apps from CM 10.1 official thread doesn't work. On the 20130601 nightly it works like a charm!.
Any help would be appreciated.
P.s: As an advice, I tried formatting system partition in CWM, reinstall nightly and gapps. All works fine now!

HELP

So I haven't used my Xoom (wifi) in literally 2 years or so, I grabbed it from the basement today thinking I'd update it and see what I could do.
I jacked it up pretty good as fsr as I'm concerned and not knowing what to do since its been so long.
I was running eos rom and running their nightlies like (46) or something.
I realized I didnt have my gapps (no playstore etc). I booted into recovery and realized I had twrp 2.3.3.0. I went into the dev section and found twrp, the bigpart one and was going to flash cm11. I downloaded the newest twrp like 2.6.3, booted into recovery and flashed the new twrp version. I had already out cm11 on my sd card and was proceeding to wipe everything as it said to do, I wiped my stuff and it kept saying failed. I went ahead and flashed cm11 thinking it was just saying failed and it cleared everything.
When it xomes up it says it needs to be reset, I hit reset it takes me to recovery and the twrp blue welcome screen is stuck, wont let me into do anything
What do I need to do, can anyone please help me?

[Q] [REQUEST] Nexus 5 flashing problem

Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks

visclo49 said:
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
Click to expand...
Click to collapse
stop using toolkits, learn something for a change
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

I want Ivanich's CM12.1 ROM 😞.

Hello.
Recently I returned my HTC Sensation XE arranged, and seeing that it had no guarantee I decided to root it. After two days in which I almost lost the mobile after having bricked, I finally managed to unlock the bootloader (although I'm still S-ON), install the latest version of 4ext Recovery Touch and give root permissions.
What happens is that looking for an Android Lollipop ROM I saw there was only one type of ROMs developed by Ivanich, and others called UnoROMs but at the end also belonged to Ivanich. Both unofficial version of CyanogenMod 12.1.
Overall, I started to download and install CM12.1 ROM with GApps and entering in recovery, but nothing was installed. I deleted cache, dalvik, data and reset to factory, but all attempts were in vain. Or almost.
When I realized that something was wrong, I looked in the ZIP of the ROM, I entered in the "/system" folder and presto!: no sign of apps, data, or other things that I think should be to make it work, only was the 'build.prop'.
Finally I gave up and tried to install Ivanich's CM11 with the corresponding GApps, and everything was great (although WIFI, that is unusable). It turns out that this ROM itself had all the appropriate files in the '/system' folder.
I thought then that Ivanich's CM12.1 ROM would be an update of his CM11 ROM and I tried to install it with CM11 as the system at that time, and I got it, but it starts out a sign saying that I had no data on the phone and to make it work I need to reset to factory. I did it and nothing happened. The recovery remained caught in the process of reseting to factory. And so over and over again. At the end I reinstalled CM11 and tried to repeat the installation process of CM12 this time making an erased of dalvik, data, cache and factory reset (which I not did at the previous), but it didn't installed, and 5.1 GApps either. As usual.
Currently I have CM11 by Ivanich (KitKat 4.4.4) with GApps, but I can't use the phone because WIFI practically doesn't work. There is a ZIP to fix WIFI that I flashed and that was fine, but it didn't fix anything.
Please can someone explain to me why I can't install CM12.1 and 5.1 GApps and why this ROM has the '/system' folder empty. There are people that have been able to install this ROM, and I can't understand how they have succeeded.
Thanks to all who help me in advance.

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!