• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Verizon] Unfortunately, the process com.google.process.gapps has stopped.

P

php111

Android Enthusiast
Hey, I tried flashing Carbon ROM, and I tried flashing gapps. I'm using TWRP recovery. I'm on a rooted Verizon Galaxy S3.This is what I did and I get an error.

Before I begin. Here are the links Mikestony provided me in PM to download, and than I did a copy/paste from where I saved them and pasted them one at a time to Phone on my S3

Carbon ROM: https://carbon-rom.com/downloads/?device=d2vzw&type=release

Gapps:
Goo.im Downloads - Downloading gapps-jb-20130812-signed.zip

OK, so now hold power and turn off the phone
Hold power+volume up+home until phone vibrates with the blue in the upper left corner and than it will boot into recovery

Now, click backup. Everything is checked except cache by default, so I checked cache and slide to confirm backup

Than go to wipe and slide to confirm a factory reset
Than go to wipe than advanced wipe and check off cache and slide to confirm
Than go to advanced wipe and check off dalvik and slide to confirm
Than go to Install and find the ROM and confirm to flash it
Next go to Install and find gapps and confirm to flash it
Finally reboot the phone

And than the Carbon logo comes up and shortly after this gapps error comes up Unfortunately, the process com.google.process.gapps has stopped.

I click OK and the error still comes up. So, I have to do a battery pull and restore from back in order for my phone to go back to normal.
 
I don't think its a problem with the touch cause I have had the same problem with CyanogenMod kitkat roms the last 5 builds . funny it didn't happen in the stable version only them nighties . but its something to do with the memory cause if it get to high that darn pop up . watch it cause it will end your call in a second I was confused thought it was the ss I have as recovery .
 
BRAINZ2013 said:
I don't think its a problem with the touch cause I have had the same problem with CyanogenMod kitkat roms the last 5 builds . funny it didn't happen in the stable version only them nighties . but its something to do with the memory cause if it get to high that darn pop up . watch it cause it will end your call in a second I was confused thought it was the ss I have as recovery .
Click to expand...

How am I fixing this?
 
The dev told me its certain devices and they working on a fix . now my patch to fix my device was a minor build.prop edit to the phone network and add a line to the prop about the vold . aka external swap . but it pops up less not much . also one has a problem with gapps .
 
CM is AOSP, so it requires gapps, yes.

A little birdy told me to try this.....after the Carbon rom and gapps flash, but before rebooting, wipe cache/dalvik/factory reset, then reboot.

If that does not work, then try another rom with gapps.

I'm am out of ideas, so I'm just throwing out some thoughts that I would try if I had this issue. :(
 
How about flash the ROM first wait a few then flash the gapps .if the problem don't happen before you flash a gapp . but happen after you flash the gapp you have the wrong gapp . so do one at a time .
 
Which one of these options am I doing this?

Option #1: Do wipe cache/dalvik/factory reset and than install Carbon than install gapps and after installing gapps and go do a wipe cache/dalvik/factory reset and than reboot?

Or option #2: don't do wipe cache/dalvik/factory reset first, but instead install Carbon than gapps and than do wipe cache/dalvik/factory reset last only?

Now which in order to wipe first, second, and last? Cache/dalvik/factory reset?

Mikestony said:
CM is AOSP, so it requires gapps, yes.

A little birdy told me to try this.....after the Carbon rom and gapps flash, but before rebooting, wipe cache/dalvik/factory reset, then reboot.

If that does not work, then try another rom with gapps.

I'm am out of ideas, so I'm just throwing out some thoughts that I would try if I had this issue. :(
Click to expand...
 
Sorry for the delay. I apologize, Im sorry.

Anyway, no luck. I have been trying gapps 20130812 with both ROMs which are CM, and Carbon. I believe its the wrong gapps. The correct one should be 20130813, I am going to try, but I'm waiting to charge up my phone.

I tried CWM recovery because some or most of my downloads in sdcard was not showing up in TWRP recovery.

And the CWM nandroid backup really screwed up my phone last night. I had to flash in Odin low ship no data wipe in order for my phone to go back to normal.
 
php111 said:
Sorry for the delay. I apologize, Im sorry.

Anyway, no luck. I have been trying gapps 20130812 with both ROMs which are CM, and Carbon. I believe its the wrong gapps. The correct one should be 20130813, I am going to try, but I'm waiting to charge up my phone.

I tried CWM recovery because some or most of my downloads in sdcard was not showing up in TWRP recovery.

And the CWM nandroid backup really screwed up my phone last night. I had to flash in Odin low ship no data wipe in order for my phone to go back to normal.
Click to expand...

Just want to chime in here - I found this thread via googling and have the EXACT same issue, difference being I'm on an earlier Galaxy S variant (1st gen, T-mobile Vibrant).

Trying to work with gapps-jb-20130813 and a port of Jellybean CarbonROM (dated 20131114-1356-vibrantmtd), sourced here as a port to Vibrant: [ROM][4.4.2][4.3.1][PORT][UNOFFICIAL] Speedy CarbonRom_20140305-0813 [05/03/2014] - xda-developers

Same exact problems/behavior as described here. I'm coming back to Jellybean after getting fed up with KitKat headaches (primarily my Google Voice going from difficult to defunct). Plan is to migrate back to KitKat once the Google devs get those wrinkles sorted out, or else after I physically destroy my current phone in frustration and finally move on to a more current piece of hardware.

One suggestion in the OP of that linked thread above is to use slim minimal gapps - I might try that next.

Have you had any luck?
 
You must log in or register to reply here.
Back
Top Bottom