So... This is kind of a rant, but it might as well be a valid question: How do you get Marshmallow working?
I've been struggling to get Lollipop to be stable, but this is even worse. I've been using Cataclysm for a while, and it was fine. Then my alarms stopped working. I said OK, I just reflash. Didn't help.
Flashed Chroma, used it for a while, it was fine, until a decided to clean flash an update. It just doesn't work. And if I flash any other MM ROM, the same thing happens. It just doesn't work. Setup wizard force close. Reflash, retry. Activating data connection, stuck for half an hour, I pressed skip. After that, I tried logging in to my Google account, play services force close, try again. No way to press back, not even after reboot, so reflash AGAIN. This time logging in worked, then I pressed restore apps, guess what, no error message, it decided to throw me back a screen, got into a loop, unfixable by reboot, REFLASH ****ING AGAIN. This time I only flashed it AFTER the first boot, play services and setup wizard force close loop.
Decided the gapps package was at fault, except I've been using the same package for a year, so not really. But I downloaded Banks 6.0. Same problems. Downloaded Open Gapps, SAME.
After that, I deleted the setup wizard from the gapps package, since there is no other way to skip it. Booted fine, but couldn't pull down the quick toggles, home button only worked half the time, the usual "when you skip the setup wizard" issues. I was angry decided to flash Lollipop, because that usually works, now I'm stuck at the ****ing Google logo.
I've been flashing **** for years, I know how to do it. I'm also a patient person. If something doesn't work for the first time, I try again, and again, and again. But this is stupid. KitKat is THE last version of Android that works. Of course all the new features are missing from it, so what are you gonna do? Use the newer. What do you do when you can't use the newer? You buy an iPhone? I'm not that stupid, so what's next? Aside from flashing CM13? Half the setting don't work or crash, including GPS, but at least it boots and you can install gapps on it.
Any other ways to get this piece of garbage working?
Have you tried stock? Since mm I've been running rooted stock or close to it on three older devices and haven't had problems. I'll use xposed or a custom kernel if I want an improvement over stock, or a minimalist rom.
lynnux said:
Have you tried stock? Since mm I've been running rooted stock or close to it on three older devices and haven't had problems. I'll use xposed or a custom kernel if I want an improvement over stock, or a minimalist rom.
Click to expand...
Click to collapse
I never use stock, but Chroma is close enough. And these issues are not connected to the ROM itself. It's Google being stupid.
Take a complete backup and do flash all with Google image.
Sent from my Nexus 5 using XDA Free mobile app
Related
Posted this in the CM10 dev thread, but decided I may get some better help by posting here, and here's my OP from the thread:
so yesterday my phone randomly shut off and it seemed to completely reset my phone. It booted up fine with two or three apps missing and all of my settings lost. I didn't think much of it until today when I tried to fix it. I did a fully wipe because some apps had disappeared and wouldn't download from the play store and wouldn't restore from TiBu. I went ahead and did the full wipe, flashed latest gapps and my device started up. I began trying to restore my apps and what not, but at I was navigating the phone my app switch soft key and home key would not function. They vibrate when pressed but don't do anything; only the back key works. I went to settings and remapped the soft keys to see if it was just a glitch and nothing changed. Still no function, only vibration. I then rebooted to recovery and did yet another full wipe and this time tried to install aokp just to see if it was a bug with cm (yes I know aokp i built from cm but I had just downloaded the latest nightly to my phone and deleted the old one so this was a test of the new nightly). Still no cheese. I was then thinking to myself, screw it and at least try to restore some apps, but after configuring my google account and opening he play store i get a constant no connection, retry button. Most of the stock apps will not even open. I flashed a TiBu.zip to restore the app and great, that worked but restoring from in TiBu doesn't work now. I tried reflashing cm and essentially repeated the above steps without any luck. Any ideas? I can't test my data/phone connection other than the fact that after setting up my google account, my email synced and I was able to make a call because the browser won't even open. MY [email protected]$s didn't do a nandroid either
Help a desperate guy in need, please!!
PS redownloading cm and gapps right now on my computer in case of a corrupted download, but to have the issue on cm and aokp is suspicious. I'll have to wait for an hour or two because my internet speed is that slow...
Click to expand...
Click to collapse
Now I redownloaded CM10 fresh from the get.cm page and even did a md5 check and everything matched up, yet still no luck. another strange thing I've noticed is that my power menu, when I verified in the setting that all options for my power menu were selected, the only options that show up are power off, reboot and screenshot. I checked to be sure app permissions were correct and even fixed permissions from recovery. All apps that do open force close upon any activity, for example upon receiving an email in gmail, the gmail app force closes. I don't know if providing a logcat would be beneficial to anyone because I don't know how to read them.
I am currently waiting on a sense rom to finish downloading to verify that it isn't just aosp based roms, but my internet connection is terrible so the 600+mb file still has 2+hrs left. I am also downloading an ruu if nothing else works, but again with a 500+mb file it will take 2+hrs
Any help is much appreciated and I can provide more info if needed.
SOLVED
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
iElvis said:
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
Click to expand...
Click to collapse
Even if it's the stock cm kernel? i never had issues with it before, but I'll flash one now because luckily I have a couple on my phone already
Edit: flashed a different kernel and nothing changed, but thanks for the suggestion
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
I've been running Cyanogenmod 12.1 for a while now, updating to the new nightly versions as they come out. Recently I discovered that Cyanogenmod 13 is now rolling out, but I held off on updating for a bit.
The other night, I decided to give it a go, and it ended up causing my phone to get stuck trying to boot. So, I flash back to the last 12.1 nightly I had been using, installed the latest version of GApps for CM12.1 and went back to using my phone as normal. However, I quickly noticed a problem, but I'm not sure of the root cause...
Nearly all of my apps fail to work properly... They all keep force closing, and I can't update them or anything because every time I try to access the Google Play Store, an error pops saying that Google Play Services has stopped. Now, if you look at the Google Play Services page on the Google Play Store, you'll see a load of negative reviews from people all reporting the same problem. However, it just very suddenly started happening to me, so I'm not sure if I messed something up when I was going back to CM12.1 after CM13 failed to work for me.
Any ideas? I just did a clean install of the latest stable release of CM12.1 and the latest CM12.1 GApps, but it's still not working. I even updated to the newest version of TWRP, thinking that might help. At this point, my phone is useless... My texting app closes. My browser closes. My calendar, contacts, etc. don't work since they're linked to my Google account. Instagram, Facebook and Twitter don't work. NOTHING WORKS!
I'm considering flashing back to stock, but I really don't want to do that. I've finally gotten Nova Launcher configured how I want it (in terms of my home screens), and I don't want to have to redo all that tweaking. Especially if flashing back to stock doesn't fix the damn problem! I just finished making a backup in TWRP and copying it to my computer for safekeeping in the case that I do try to flash back to stock. That way, if it doesn't help, I can go back to where I'm at now at least.
So; any ideas? I don't know if it's Google, or something I did.
The first and easiest thing u could try is reinstalling those apps! Check http://www.apkmirror.com/ for that!
Andus1988 said:
The first and easiest thing u could try is reinstalling those apps! Check http://www.apkmirror.com/ for that!
Click to expand...
Click to collapse
Which apps; the ones that keep crashing? I don't see how that's going to help...
Like I said, I can't do anything that's associated with Google at the moment. Initially I thought removing my Google account would help, as that's what an Internet search suggested would help. Now, since Google Play Services keeps crashing, I can't even add my Google account back onto my phone.
DrumsXO said:
Which apps; the ones that keep crashing? I don't see how that's going to help...
Like I said, I can't do anything that's associated with Google at the moment. Initially I thought removing my Google account would help, as that's what an Internet search suggested would help. Now, since Google Play Services keeps crashing, I can't even add my Google account back onto my phone.
Click to expand...
Click to collapse
Yes u could at least give it a try! Uninstall the apps that keep crashing and reinstall them via their apks!
I just tried to flash back to stock, and it wouldn't work; the GPT.bin kept failing to flash. So, I had to go back to CM12.1 and I'm right back where I started; with Google Play Services not functioning.
This may sound stupid... but have you tried clearing the caches? /data/dalvik and /cache?
I'd suggest making sure you have mfastboot, extracting the stock 5.1 untouched files here and then running the script here. Make sure those lines are adjusted to reflect where you've extracted the stock files to. Ie. mfastboot flash partition C:/Android-SDK/Platform-tools/gpt.bin
What's the failure that's stopping it from flashing? If you can get past that I'd boot the stock firmware once, flash TWRP, clear /system and /data then flash the latest nightly and GApps then clear your caches before booting.
Here's an update.
After flashing back to CM12.1 I discovered that I was still having the same issue with Google Play Services, but my network also wasn't working. This was my own fault though; I forgot that since I tried restoring my phone to stock, I needed to apply the Network Fix that is floating around for the XT1033. Although, my phone is technically an XT1032; it just doesn't have a functional network unless it's using an XT1033 radio...
So, when I got home from work I applied that Network Fix, which got me my network back. However, my Google Play Services still refuses to work.
I've just tried to give another go at flashing back to stock Lollipop firmware, but it's still not working. Just like before, it keeps failing to flash the GPT.bin file, throwing me an error; see below.
(bootloader) Preflash validation failed
FAILED (remote failure)
I've never had this happen before. This time around, I even went into TWRP before starting the flash and used Advanced Wipe to clear the Dalviik Cache, Data, Cache and System, yet it still won't flash properly. Cyanogenmod flashes just fine, but I want to see if using stock firmware will fix my issues with Google Play and its services.
I have no idea what to do.
Well, my phone is officially KIA. I followed this guide to get it back to stock (none of the other guides would work), and once I went to reboot as part of Step 7, the phone shut off and won't come back on. I've tried plugging it in, holding the volume down and power button for as long as three minutes, holding the volume up and power buttons for just as long... it won't do anything. It's hard-bricked.