I flashed the codefirex ROM with android 4.3 to my ltevo.
It worked fine at first but when the google play updates started to install it began force closing the play service and location service stuff.
Dialogs would appear and I'd click ok and it would come up again. Made the phone unusable really. Difficult to even reboot.
Anybody else experience this? I flashed the gapps from 20130813 jellybean.
They seemed to work fine until they updated.
Did you dirty flash? Maybe you should try reflashing Gapps to see what happens.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Will Rickards said:
I flashed the codefirex ROM with android 4.3 to my ltevo.
It worked fine at first but when the google play updates started to install it began force closing the play service and location service stuff.
Dialogs would appear and I'd click ok and it would come up again. Made the phone unusable really. Difficult to even reboot.
Anybody else experience this? I flashed the gapps from 20130813 jellybean.
They seemed to work fine until they updated.
Click to expand...
Click to collapse
Try these, they've been good to me on 4.3 and 4.4 there are separate versions for each: http://forum.xda-developers.com/showthread.php?t=2397942
This is the process I followed. I repeated it last night just to be sure.
Recovery is TWRP 2.6.3.0. The one for CM11 kitkat.
1. I went into wipe and advanced wipe and selected Dalvik Cache, Cache, Data, System, Android Secure.
2. I went into install and selected the ROM zip and installed.
3. I went into install and selected the gapps zip and installed.
4. I went into install and selected the supersu zip and installed.
5. I wiped Dalvik Cache and cache.
6. Reboot.
It then works fine till google play services auto updates.
Then I get closes in gsf.login, location and play services.
If I revert google play services it works again.
Thanks wolfclan68, I'll try those gapps later today.
Right now I'm setting up CM11 deck's build 2014-01-17.
Have you tried unplugging it and plugging it back in?
Related
Hey guys, I tried to flash the HTC One Stock rom ported to my DNA, which “bricked” my phone. I was stuck on the white HTC boot screen when I tried to boot, and was only able to go into the bootloader (CWM recovery would not boot). I have S-OFF, HBOOT, unlocked bootloader, root access. I then tried flashing the team win recovery, which worked, but also would not boot. After continuing to get frustrated, trying to run RUU (failing because my battery was below 30%), I did some more research and tried “fastboot clear cache”, then tried booting into recovery – tada! So now I was in recovery, cleared all my cache/data, flashed the CM 10.2.1 zip and the latest PA Gapps I had stored on the phone. Everything went clean and Cyanogenmod booted up.
Now, however, the Play Store will not open (connection error, “retry”) and Hangouts will not connect. Any ideas? I’ve tried clearing Google Play Services data, Hangouts data, Play Store data, rebooting, toggling airplane mode, removing and re-adding my google account. Also, I’m getting sync errors for my google account. Any help here would be appreciated.
Most of the other Google apps I’ve tried work fine and have all my data, including Maps, Gmail, Keep, Search/Now, Play Music, etc.
It may also be important to note that the phone is currently not attached to a number (I re-activated my old iPhone 4s so I can at least have a phone for the time being). I do have wifi access.
Thanks.
Try This
Everytime that happened to me it always ended up being because it was either an outdated version of GAPPS or it wasn't a minimal gapps install. What i recommend is to look up version of android you're running, google "*your android version 4.x.x* minimal gapps.zip" I always go minimal because having all of the extra play apps and google services isn't necessary and can cause issues with certain roms, plus dat battery drain is rough compared to a minimal gapps install. After this has happened and it still hasn't worked, let me know :good:
WestTexasCoder said:
Everytime that happened to me it always ended up being because it was either an outdated version of GAPPS or it wasn't a minimal gapps install. What i recommend is to look up version of android you're running, google "*your android version 4.x.x* minimal gapps.zip" I always go minimal because having all of the extra play apps and google services isn't necessary and can cause issues with certain roms, plus dat battery drain is rough compared to a minimal gapps install. After this has happened and it still hasn't worked, let me know :good:
Click to expand...
Click to collapse
I tried two different "minimalistic" gapps - one was 15mb and the other ~60mb. For the 15mb one, my keyboard didnt work and I had the same google connection issues with the other one.
The latest pa gapps on 10.2.1? Do you mean the latest 4.3 gapps or did you accidentally use the kitkat ones? If you used the kitkat ones it would definitely cause problems like that. My suggestion: just flash the latest cm11 and pa gapps. I think you'll be much happier with it anyway.
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
The latest pa gapps on 10.2.1? Do you mean the latest 4.3 gapps or did you accidentally use the kitkat ones? If you used the kitkat ones it would definitely cause problems like that. My suggestion: just flash the latest cm11 and pa gapps. I think you'll be much happier with it anyway.
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Hey, been a little to busy to troubleshoot this. My problems began when I flashed a snapshot build of CM11 for the DNA. There is no "Stable" release on their downloads page yet: http://download.cyanogenmod.org/?device=dlx&type=.
I did find this guy though: http://forum.xda-developers.com/showthread.php?t=2714425
Should I try flashing this? Also, I was reading that you need new radio firmware for Kit-Kat. Is this true? I tried to flash the latest radio through fastboot but it gave me an error that had something to do with an unknown device ID.
Let me know your input, thanks.
Update:
I Flashed C-Rom 6.5 (Android 4.4) and the 4.4 PA Gapps and still had the same exact issues as before:
Play Store Connection issue
Hangouts connection issue
Other google connection issues
No 800 MHz cell band connection (device said Voice was Out of Service when I put my phone number back on). 700 MHz LTE, however did work.
Can't get adb to see my device, but fastboot can.
Corrupted model id and serial number.
So with all these issues above, the corrupted model id and serial number are what I've been mainly trying to tackle. I've read about fastboot flashing the ENG HBOOT and changing the model id that way, but I cannot flash zips in fastboot because of the corrupted model id (give the model id check error and fails). I'd be completely satisfied at this point with running RUU and getting onto the stock 4.4 update that came out. However, when I run the RUU.exe, it says it can't see my device and when I try to flash the RUU hboot, radio, and recovery zips, obviously the model id check will fail. I've since factory reset and flashed CM10.2.1 back onto the phone because C-Rom 6.5 was very laggy. The phone is pretty much just a wifi device now and I have to download apps via apk's in the browswer and manually update everything.
Anyone have any ideas on getting the model id and serial number back to normal? Really starting to get tired of my cracked iPhone.
So today i took the leap and rooted my phone. That went well and i rooted my phone succesfully. My next step was install CM11. Heres where the problems start. I used the CM11 installer and followed all of the instructions. The installer went through, it said it was succesful, and i saw the blue CM person on my phone and my phone started. As expected it made me run through all the set up options. But then, every 10 seconds i would get "google play services has stopped working" and my phone was running very slow. Going to settings, my phone was still running jellybean and nothing was new, now i was just at factory settings, google play services was broken, and my phone ran slow. I rebooted my phone. still nothing. I tried custom installing drivers and reinstalling CM11 using the installer. Same thing. Anyone have any ideas?
Android 4.3 T-Mobile Galaxy s3
Sorry for wall of txt and general un-organization. Very frustrated.
SamsungS3helpplz said:
So today i took the leap and rooted my phone. That went well and i rooted my phone succesfully. My next step was install CM11. Heres where the problems start. I used the CM11 installer and followed all of the instructions. The installer went through, it said it was succesful, and i saw the blue CM person on my phone and my phone started. As expected it made me run through all the set up options. But then, every 10 seconds i would get "google play services has stopped working" and my phone was running very slow. Going to settings, my phone was still running jellybean and nothing was new, now i was just at factory settings, google play services was broken, and my phone ran slow. I rebooted my phone. still nothing. I tried custom installing drivers and reinstalling CM11 using the installer. Same thing. Anyone have any ideas?
Android 4.3 T-Mobile Galaxy s3
Sorry for wall of txt and general un-organization. Very frustrated.
Click to expand...
Click to collapse
Install the latest version of PhilZ recovery from here:
http://forum.xda-developers.com/galaxy-s3/development/i93xx-philz-touch-t2002953
Go to this page and download a type of cm rom that you want:
http://download.cyanogenmod.org/
Put it on sdcard, go to recovery, do a full wipe (wipe data/factory reset + wipe cache + wipe dalvik cache) then install it from " install zip "
done!
Hi guys,
i am using a Nexus 10 with the latest nightly of CM11.
The youtube app crashes everytime i click on any playlist (e.g. watch later or other)
On my Galaxy Nexus phone runs also the latest cm11.
Youtube app works fine.
So here is the question: Does anyone of you have the same problems on tablets with cm11?
Its a little bit frustrating. I already did this in despair:
1. Flashed to stock rom 4.4 (youtube works)
2. Flashed stock recovery
3. Re-locked the tablet
4. Unlock, Root, Flash recovery to clockwork touch
5. Flashed rom to "cm-11-20141016-NIGHTLY-manta" and restart the tablet
6. Flashed gapps "gapps-kk-20140606-signed"
7. Play Store gapps update
Youtube still crashed at a click on any playlist.
Normal Youtube videos work
I often click on watch later on my computer to watch them on my tablet.
Please help me
greets seb0p
I would recommend a newer GAPPS package. I use the mini modular from here:
http://forum.xda-developers.com/showthread.php?t=2397942
It's always the latest and it always performs well with CM11.
Lately I have uncovered a few issues with CM11 and switched my N10 to Purity. my wife's N10 has always run Purity ROM and it is rock solid.
I have the same issue. Fixed it by flashing PA gapps, and then refusing the update the app on the play store. Will be going back to stock once 5.0 drops for the n10!
Flashing newer gapps didnt help. ?
Should i wipe cache etc and reflash the hole Rom?
What should i do next?
Sent from my Nexus 10 using XDA Free mobile app
So after reflashing the gaaps didn't work
i flashed back to stock and redo the hole root, flash recovery, flash rom process.
I then flashed the "pa_gapps-modular-mini-4.4.4-20141011-signed" gaaps
and DIDN'T do a playstore update.
Youtube still crashes.
CM11 is so super smooth and has better data security then stock.
After every step did't work i am about to try a new rom with the same features as cm11.
Do you know one?
Hi Guys,
I'm needing a little help. I have my phone rooted and it was flashed with CM11. I switched back to the stock rom to check something and when I tried to reactivate the slot my rom was in, the reactivation failed. So I figured if I have to put a rom back on, I would try something new. After reading some reviews on a couple of roms, I choose the Pacman LP rom 5.1.1. Installed and flashed the gapps. All of the google stuff updated fine. A couple of days later I noticed I wasn't able to use the data to go online. The phone and texts were fine. I thought it was the rom, so I deleted it and reflashed. Again, couldn't go online. Contacted my carrier and the found out the APN wasn't listed. Added it and all was good again. So I thought.
After flashing the rom I again flashed the gapps, only this time google play services will not update. It keeps flashing error code 506. I've wiped the cache several time and have also done a factory reset to no avail. I've also deleted the rom and tried installing it in a different slot, and that isn't working either. I've downloaded newer versions of gapps, but cannot get them to install at all. When trying, I either get error code 40 or 70.
I've deleted the cache from Google Play Store and Google Play Services and I've also gone into data/data and deleted the cache from com.android.vending. Nothing seems to work.
After this long story, my question is, if go into the stock rom and delete safestrap and reinstall it, could that possibly fix my issue?
bethsmith72 said:
Hi Guys,
I'm needing a little help. I have my phone rooted and it was flashed with CM11. I switched back to the stock rom to check something and when I tried to reactivate the slot my rom was in, the reactivation failed. So I figured if I have to put a rom back on, I would try something new. After reading some reviews on a couple of roms, I choose the Pacman LP rom 5.1.1. Installed and flashed the gapps. All of the google stuff updated fine. A couple of days later I noticed I wasn't able to use the data to go online. The phone and texts were fine. I thought it was the rom, so I deleted it and reflashed. Again, couldn't go online. Contacted my carrier and the found out the APN wasn't listed. Added it and all was good again. So I thought.
After flashing the rom I again flashed the gapps, only this time google play services will not update. It keeps flashing error code 506. I've wiped the cache several time and have also done a factory reset to no avail. I've also deleted the rom and tried installing it in a different slot, and that isn't working either. I've downloaded newer versions of gapps, but cannot get them to install at all. When trying, I either get error code 40 or 70.
I've deleted the cache from Google Play Store and Google Play Services and I've also gone into data/data and deleted the cache from com.android.vending. Nothing seems to work.
After this long story, my question is, if go into the stock rom and delete safestrap and reinstall it, could that possibly fix my issue?
Click to expand...
Click to collapse
pac-rom 5.1.1 on the razor xt912 and droid 4 does not work correctly with gapps. Use a different rom.
OGdroidster said:
pac-rom 5.1.1 on the razor xt912 and droid 4 does not work correctly with gapps. Use a different rom.
Click to expand...
Click to collapse
I apologize for taking so long to get back and thank you for your response. Can you please recommend a lollipop rom that does perform well on the xt912 and works good with gapps?
Thanks
Beth
bethsmith72 said:
I apologize for taking so long to get back and thank you for your response. Can you please recommend a lollipop rom that does perform well on the xt912 and works good with gapps?
Thanks
Beth
Click to expand...
Click to collapse
Try mokee, cyanogen, or one of the unofficial roms like resurection remix or something like. I am currently running on my droid 4 and razor resurection remix but based on android M. It all depends on what you like. If you like to customize and highly configurable rom resurection remix based on android M is good to go. I use open gapps projects.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).