So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
...and now
senuod said:
So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
Click to expand...
Click to collapse
Now, after wiping/factory reset and re-flashing the rom, gapps, and supersu....still getting no homescreens AND not able to connect to google play services.
Any help would be greatly appreciated!!
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
senuod said:
So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
Click to expand...
Click to collapse
cyril279 said:
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
Click to expand...
Click to collapse
I was able to restore my phone to a point before I flashed any ROMS using CWM recovery. Only issue with that is storage has been eaten up and some apps that were on my sd card aren't working well. I'll take those steps to properly flash OmniRom again in 2014.
Thanks cyril
looks like things may actually be working. thanks again!
cyril279 said:
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
Click to expand...
Click to collapse
Related
EDIT: First I tried installing Codename Android as my first rom from stock rooted gingerbread. OK, I ended up having some problems where I couldn't detect the SD card on my computer, and Android was giving me no option to go into mass storage mode. I had to take the advice on ics.samsung-update.com about the MTP issue going into Terminal Emulator to get it working again.
Now that I got it working I was just going to try to flash teamhacksung's build 5 here: hxxp://rootzwiki.com/topic/11850-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-5-0114/ Read my latest post for my problem.
I'd highly recommend AOKP or THS (find at rootzwiki) ICS roms. Droidstyle's guide in the general section has everything to get you up and running. Sounds like you might've flashed the wrong recovery in odin?
Probably something like that? I dunno, either way, I got a ClockwordMod v4 flashed on there. I then installed the Codenamed Android ROM I had on the sd card and that was appeared to work just fine. It seems strange that the contacts app on this rom seems to only want to let me import contacts from an Exchange account? Kind of strange I can't seem to get my Google contacts on here. I guess I'll try to flash the teamhacksung rom.
It sounds like you forgot to flash gapps. Flash the rom you want to use, then gapps, (then kernel if you want), and reboot.
Aokp m4 ftw! Glitch kernel if you're looking for performance tweaks. Go to Droidstyle's guide in general forum for all your needs.
Sent from my SCH-I500 using xda premium
cant install gapps
I am now trying to install teamhacksungs build. This seemed to go ok, except for I keep getting errors that it can't mount the cache. Also when I try to data wipe it gives me those errors and it seems to skip some of the formats. After I flashed teamhacksung's build 5 I keep getting errors that android.process.media has stopped. Also after the rom begins running I shut back down to flash gapps and this seems to install as well, but when I boot up I see no sign of them. Anyone have any ideas?
It sounds like you may have 3-fingered into recovery after flashing ICS. After you odin the recovery, you 3-finger into it *initially*, but never again after that. Use the reboot menu.
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
CyanogenMod 13.0 : Download
Changelog : Changelog
Open GApps : Download ( arm, 6.0, nano )
TWRP : Download​
CM13 Nightlies, ROM for the Sprint Galaxy S5
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly, now moved to 14.1
UPDATE 6/14: Looks like there's an issue that 5ghz network doesn't work on higher bands, but it works on 36-48 and bluetooth. Hopefully it will be fixed soon.
UPDATE 6/23: There's a fix attempt on boot image. Link. Thanks to @haggertk
UPDATE 6/27: Looks like Bluetooth and Wifi issue have been fixed since 6/25 nightly.
Thanks to @haggertk
Created 2016-05-12
Last Updated 2016-11-29
Reserved
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
alexclang said:
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
Click to expand...
Click to collapse
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
e-j said:
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
Click to expand...
Click to collapse
Excellent!! I'll just install the latest nightly for CM13 just like I was going for 12.1 and hopefully things will go smoothly!
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
UPDATE/PSA: USE THE NANO GAPPS AS STATED IN THE OP. NANOGAPPS INFINITY OPENS THE DOOR.
e-j said:
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
Click to expand...
Click to collapse
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
alexclang said:
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
Click to expand...
Click to collapse
Got it working after I realized the OP specifically mentioned the "nano" GApps variant; booted fine after a clean install of CM13 & the nano zip.
Issues w. CM13 flash
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
lentm said:
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
Click to expand...
Click to collapse
Yeah that was exactly the issue. Reflashed 5.0 then made the jump and it worked perfectly. So much wasted time...
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
e-j said:
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
Click to expand...
Click to collapse
Yeah reflashing lollipop then installing cm13 did the trick.
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
has anyone got themes to work ine keeps crashing
manolze said:
has anyone got themes to work ine keeps crashing
Click to expand...
Click to collapse
Mine works fine with Puzzled UI - CM Theme from Play Store on 5/20 build.
I have no working theme chooser on this releaese
xenokc said:
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
Click to expand...
Click to collapse
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
xpm69420 said:
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
Click to expand...
Click to collapse
Theme chooser works great for me, not having any issues with it. I am having an issue with the time being or of sync when set to automatic... How'd you fix it? Also, what's wrong with the dialer... can't say I'm having any issues there either.
unclejuju said:
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
I little late here, but CM 13.0 did NOT fix the S5 bluetooth issues. Still have the skipping and studdering.
When signing in my google account, I get the error Problem communicating with google server. try again later.
Device LG G3 VS985
Rooted
Newest nightly of cm13
Tried different versions of opengapps
Tried installing google apps from apk mirror
Hosts looks normal
2 step disabled
Cleared cache for google apk's
Disabled and reenabled apps
Fully wiped and reinstalled Cm and Gapps
Cleared davlik and cache
History:
This all worked on a previous phone same model. replaced original device due to a 3000lb crushing incident.
This device, tot back, rooted, TWRP installed, 35b installed, flashed 47a rooted stock version.
Everything works.
Wipe system and install cm as I have done on previous device, and here I am.
I'm missing something but cant figure out what it is.
I have read through forum after forum and tried everyones so called fix but nothing works.
I even flashed my old backup from my previous device but had issues with updating gapps due to being older.
I've learned alot from you guys but this has me baffled.
FWIW I'm running into the EXACT same issue on AOSP/cm13 based roms. I've tried Dirty Unicorn, PAC alpha, and ParanoidAndroid all with the same issue. The official cm13 gets through connecting to googles servers, but I have sms issues on that.
I'm really not sure what could be causing it, as I've been searching the same as you and tried all of the posted "solutions" by other users. Also, it seems that most people are running into this error after they enter their username and password, but for me it won't even get that far.
If you find a solution PLEASE let me know, I had to revert to using stock 47a debloated, and I hate the LG skin.
inexplicability said:
FWIW I'm running into the EXACT same issue on AOSP/cm13 based roms. I've tried Dirty Unicorn, PAC alpha, and ParanoidAndroid all with the same issue. The official cm13 gets through connecting to googles servers, but I have sms issues on that.
I'm really not sure what could be causing it, as I've been searching the same as you and tried all of the posted "solutions" by other users. Also, it seems that most people are running into this error after they enter their username and password, but for me it won't even get that far.
If you find a solution PLEASE let me know, I had to revert to using stock 47a debloated, and I hate the LG skin.
Click to expand...
Click to collapse
I'm still looking. I will let you know if I find a solution. I'm surprised that with all the smart people on this site, that no one has an idea or such to help us work toward a solution.
thebigindian said:
I'm still looking. I will let you know if I find a solution. I'm surprised that with all the smart people on this site, that no one has an idea or such to help us work toward a solution.
Click to expand...
Click to collapse
On some roms it does go through for me (aospb, beanstalk), but then outgoing sms fails. I think it may be my device honestly...
Ok, got cm 12.1 to work with open gapps super. I'm able to setup gmail accounts and such. Did a full wipe. Used a clean SD card with only the files needed to flash.
Gonna try upgrading to cm13.
inexplicability said:
FWIW I'm running into the EXACT same issue on AOSP/cm13 based roms. I've tried Dirty Unicorn, PAC alpha, and ParanoidAndroid all with the same issue. The official cm13 gets through connecting to googles servers, but I have sms issues on that.
I'm really not sure what could be causing it, as I've been searching the same as you and tried all of the posted "solutions" by other users. Also, it seems that most people are running into this error after they enter their username and password, but for me it won't even get that far.
If you find a solution PLEASE let me know, I had to revert to using stock 47a debloated, and I hate the LG skin.
Click to expand...
Click to collapse
Got it working. The route I took was using a clean sdcard with only cm12 snapshot and your choice of open gapps. Wipe internal everything and flash the 2 files on the sdcard. Reboot. After all is said and done, grab the current cm13 nightly and matching gapps package and dirty flash both. from a clean sdcard. This worked for me. Good luck.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2