Google apps on Motorola Xoom running cm-10.1-20131007

[c_dunne]

Last week I brought a Morotola Xoom on ebay, it had 4.0 installed but I wasn't that impressed with it having got used to stock 4.1 on my phone.

I came across the great guide at http://forum.xda-developers.com/showthread.php?t=1477024 and used this along with http://wiki.cyanogenmod.org/w/Install_CM_for_wingray to unlock, root and install cyanogenmod 10.1 on it.

It was mostly a stress free install (although I managed to miss renaming the stock files that the post says causes Stock Recovery to overwrite CWM but it seems to still work OK.

My issue now is that I don't seem to have all the Google apps. It has gmail but not maps or market. I assumed that gmail isn't part of cyanogenmod so the 'gapps-jb-20130812-signed' file has installed (I think that file is the correct version).

It's not too clear from the instructions they read to me that you install the main CM zip and then Google apps without needing to re-boot in between, is this correct? I've tried a completely fresh install and also wiping the cache partition but no luck. But have not tried re-booting after installing the CM then installing Google Apps in a second boot, worth a try I guess.

Am I just making a simple noob error here? Thanks in advance for any advice.

 

[c_dunne]

A update, I've just tried formatting and re-installing again, only this time allowing a reboot into android prior to trying to install Google apps. One thing I've learnt is that the gmail app is part of the base install. Installing google apps appears to go ok but upon rebooting they aren't there. My next test is to try yet another clean install and an old version of gapps (gapps-jb-20120719-signed).

Chris

 

[c_dunne]

Motorola Xoom issues with 'Motorola fast-boot' replacing 'clockwork-recovery'

A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).

I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.

However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.

However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.

I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.

 

[c_dunne]

Hmm a fun morning, I've lost times now at how many times I've had to reroot it. I've managed to get the Google play store apk and have tried using that (in addition to installing the gapps zip) it is loading but complaining of no network connection.

With regard to renaming the files ' /system/recovery-from-boot.p' and 'system/etc/install-recovery.sh' I've not managed this, when the tablet reboots into clockwork recordery its connection with adb is dropped. I've also tried doing them in terminal when booted and they don't seem to be there.

There doesn't seem to be anyone else commenting on this so I'll just plod along blindly :silly:

A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).

I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.

However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.

However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.

I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.

 

[miraidensetsu]

Well, I'm with this problem too. I'm trying to solve this problem by myself, but no success at all. It do FC on google play every time it try to update. Every Google App (besides GMail) is doing FC with this CM build.

I tried to:
- Reinstall google apps
- Install another version (compatible with Android 4.2.2)
- Do the wipes again
- Install google play from an outside source (it doen't come with it).

But no success.

Any ideas?

 

[c_dunne]

miraidensetsu sorry for my delay in responding, I'm surprised that no other responses to this tread have been made. An update I've now resorted back to the stable release cm-10.0.0. Given it's nearly a year old I'd hope there'll be a stable release of 4.2 out soon.

Initially I had issues with the stock keyboard crashing all the time. But after searching about this I've installed the Google keyboard app and disabled the stock one.