[Q] Unable to launch CM 10.1 after flashing the gapps - Nexus S Q&A, Help & Troubleshooting

Hello everyone,
I flashed CM10.1 and the gapps (gapps-jb-20121212-signed.zip).
When I boot the phone it lets me enter my pin code, but after that I get those two messages:
"Unfortunately the process com.google.process.gapps ended."
"Unfortunately the process setup wizard ended."
And I only may click on "ok" ever and ever and ever again.
The only way to get unstuck from this is to remove the battery and restore the phone.
I flashed many times with different builds and different gapps packages too, I ever get the same issue.
I also did it with and without wiping everything.
What am I doing wrong?
Thank you for your time.
Halavus

Did you wipe data/cache completely?

Zulda said:
Did you wipe data/cache completely?
Click to expand...
Click to collapse
Yes I tried with and without wiping. The issue is the same in both cases.
Sent from my Nexus S using xda app-developers app

Wipe again, flash CM again, reboot, recovery, flash Gapps, reboot. Must works

I tried again many times and I had the same bugs.
But since this afternoon I used TWRP instead of CWM and now it just works perfect.
I'm sure the issue came from CWM.

Hey guys, I am new to the forum. I am glad I found this thread, I keep running into this same problem.
I have been flashing CM 10.1.2 with what I think is the wrong Gapps flash, gapps-jb-20121011-signed.zip. That is the wrong Gapps flash, right?
If that is the wrong .zip, how should I restore back to my Titanium back up from recovery?

this is the correct gapps for 4.2.2 20130301

Related

Do I need to re-install GAPPS every time I dirty flash?

So I dirty flash upgraded LiquidSmooth to the latest. I noticed everything went well, I wiped cache/dalvik and booted up. My google contacts were gone along with my whole account. I re-flashed and installed gapps afterwards. Did I do something wrong? Or is this the process usually?
996 said:
So I dirty flash upgraded LiquidSmooth to the latest. I noticed everything went well, I wiped cache/dalvik and booted up. My google contacts were gone along with my whole account. I re-flashed and installed gapps afterwards. Did I do something wrong? Or is this the process usually?
Click to expand...
Click to collapse
Are your. Apps like play store still there? If they are then just re add google account or just reflashed gapps, better safe then sorry
I've never used that ROM, but the general answer to your question is no. Only flash gapps when starting from nothing.
Tapatalk via CM10.1 Galaxy S3
It was weird. I booted up without a google account. No google apps or anything. So I just reflashed Gapps. I didn't have the option to add an account for Google.
That happened to me once or twice. No issues from flashing gapps though.
Sent from my SCH-I535 using xda app-developers app
996 said:
It was weird. I booted up without a google account. No google apps or anything. So I just reflashed Gapps. I didn't have the option to add an account for Google.
Click to expand...
Click to collapse
did you check under settings? accounts
Yup. No google option was there. So I went into recovery reflashed the rom and then flashed gapps
Sent from my SCH-I535 using xda premium
I've dirty flashed 3 different ROMs multiple times (usually wipe data), and each time gapps were still there. The only issue I've run into was an older market bug so I re-flashed the latest gapps.
All wrong answers, always re flash your gapps when flashing an aosp rom regardless if it's a new install or a dirty update. When dirty flashing your gapps should not be there anymore, if they are they are ghost remnants of the old build. Your data for your gapps will remain on a dirty flash so you need not worry about setting things up again.
annoyingduck said:
All wrong answers, always re flash your gapps when flashing an aosp rom regardless if it's a new install or a dirty update. When dirty flashing your gapps should not be there anymore, if they are they are ghost remnants of the old build. Your data for your gapps will remain on a dirty flash so you need not worry about setting things up again.
Click to expand...
Click to collapse
This. Always reflash gapps after dirty flashing a rom.
I personally clean flash 99% of the time, it prevents so many problems.
check updater-script
maybe the ROM had a line of script to delete factory data...
Some ROMs have that line in their "updater-script" file...I remember flashing an ICS rom that did that..:/
If yes...then you will have to flash gapps again..Check the file(if possible) before dirty flashing the next time..:good:
But as a thumb-rule...always flash gapps after flashing AOSP/AOKP etc. ROMs..
Hope this helps..Don't forget to hit thanks!
Is it OK to just flash the new GApps without reflashing the ROM or doing anything else?
Edit: wrong post

[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!

[Q] Katkiss 4.3 - AOSP keyboard has stopped after flashing

Help, I'm slowing going out of my mind. I've been trying to figure out the problem but no joy here so far.
I think I've successfully upgraded to KissKat 4.3 from EOS 118 . Everything loads, asks me to set up tablet etc but I keep getting the " AOSP keyboard has stopped" so I can't actually finish the set up or see if I've actually upgraded properly.
I use TWRP 2.5 version, all the Gapps and version 20 from the 1st page. I've reflashed and rebooted many times changed the keyboard settings but ended up the same message. I also get the google text to speech has stopped as well and I've disable that as well.
Any suggestions would be appreciated. :good:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
GMTN said:
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
Click to expand...
Click to collapse
LOL. I can tell you I've done that 4 different times with 4 different download all from the 1st page but it worked on this 4th and I'm not sure why.
Now to see tomorrow if this ROM lives up to all the troubles ( 3 hours worth ) and praise . Thanks for your guides by the way.
Glad it is sorted. I hope you find it worth your time.

I think I got the wrong gapps

Finally loaded cm 10.1.3 but now I think I loaded the wrong gaps..my asop keyboard keeps crashing and it only started after I installed it. I tried wiping and it's still doing it. Can I delete the gapps somehow?
JPull07 said:
Finally loaded cm 10.1.3 but now I think I loaded the wrong gaps..my asop keyboard keeps crashing and it only started after I installed it. I tried wiping and it's still doing it. Can I delete the gapps somehow?
Click to expand...
Click to collapse
Which gapps do you have installed? Have you tried clearing data for the keyboard? If you are against wiping and starting over again, then your best bet may be to try deleting the individual Google apps from /system with a file explorer or Titanium Backup then flash the right gapps. You may be able to dirty flash the proper gapps package, may work or it may not.
Failing that, you could wipe data and flash CM and the proper gapps package.

[Q] All Roms force close core apps.

So, I've tried fixing the phone from random cutouts by flashing another Rom, Now, when the rom has been flashed and starts, I get a mass of force close errors on boot, (I've tried this with multiple roms, them being a CM10 and CM11 based roms). I've tried full wipe, and cleared the Dalvik cache. Anybody?
twisted64d said:
So, I've tried fixing the phone from random cutouts by flashing another Rom, Now, when the rom has been flashed and starts, I get a mass of force close errors on boot, (I've tried this with multiple roms, them being a CM10 and CM11 based roms). I've tried full wipe, and cleared the Dalvik cache. Anybody?
Click to expand...
Click to collapse
What apps are FC'd? If they're google's, then consider the gapps package you flash.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
ashkan-khatar said:
What apps are FC'd? If they're google's, then consider the gapps package you flash.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
Click to expand...
Click to collapse
The question should be what doesn't FC. I've seen DSP manager close, process.android.acore close and a few other apps such as themer and then the phone just crashes.
Have you tried to format all partitions using 4ext recovery?

Categories

Resources