• Announcements

    • PsychoI3oy

      Unsupported devices & future versions   09/03/16

      Unsupported devices posts outside the Device requests forum will be deleted without comment. Posts asking about/for future versions of CM will be locked and/or deleted.   We don't have a crystal ball; we don't know if someone will make CM $version for your deivce or if CM $version+1 will be made for your supported device.
RejZoR

After Cm 10.2, My Phone Is A Disaster

87 posts in this topic

Half of the stuff didn't work, complaining i didn't have root, stuff closing, failed to connect to Google account etc etc, wanted to return to an older build like many times before and it just hangs at the "stargate" rotating thingie on boot forever. Awesome.

What can i do to make the damn phone work again!? I tried erasing cache and delvik, flashed the ZIP again and still just gets stuck on the rotating logo...

Share this post


Link to post
Share on other sites

I have the same problem. Apps did not work after I intalled todays build, tried to roll it back to a build from a few days ago that I had installed and which worked flawlessly. After install it got stuck on samsung logo, then I rebooted it and is stuck on cyanogen "stargate" logo.

Share this post


Link to post
Share on other sites

Only way you can gain access back to the phone is the following:

Hold Volume Up + physical button (middle one) + POWER button, wait for CWM to show up, erase cache and delvik, go to install ZIP option and install this latest broken build again. It will still be broken, but at least you'll be able to make/receive calls.

I wonder if this build was even tested at all. I know it's nightly but god, this one is completely and entirely broken on so many levels it's ridicuous.

Share this post


Link to post
Share on other sites

Thanks Rejzor, I got it working again!

Hvala!! :)

Share this post


Link to post
Share on other sites

I got the same issue ... could resolve it by booting in recovery mode: Hold Volume Up + physical button (middle one) + POWER button, then restoring a full Backup I made and stored in the internal SD card just before flashing the 10.2 zip. The phone was restored just has before, with the last CM 10.1 working as all applications.

Now waiting for a better CM 10.2 .... As it was the first of it's kind, those things happends. After all those are "Nightly/Experimental" ... :)

Share this post


Link to post
Share on other sites

I didn't make full backup, because restoring to old versions worked by just flashing old on top. But now it seems this isn't possible because of the transition from 4.2.2 to 4.3. Ugh...

Share this post


Link to post
Share on other sites

not sure if you guys are talking about the same build, since you didn't mention it, but I installed todays (8-14-2013) nightly and wow, what a crap fest, both my data and wifi would connect, and show as connected, but not work, no calls, no internet, no nothing, nothing.

Then, after a standard reboot, the phone started freezing in random places, first on the samsung splash screen, then again when trying to go into recovery mode, then while in recovery it was giving md5 checksum errors on my backup, which eventually restored and seems to be ok.

I get these are experimental, I get that these are nightlies and we are testers, but seriously, I didn't see anything in the changelog related to DATA / APN / WIFI so how on earth could this update be so borked?

Share this post


Link to post
Share on other sites

if this any help I decide to update to the latest cm10.1 20130813 and the phone stop during the installation luckily when I reboot the phone finish the installation.

Share this post


Link to post
Share on other sites

cm10.1 20130813 isn't the latest, cm-10.2-20130814-NIGHTLY-i9100.zip, and that appears to be causing problems for a few of us. I was able to restore my backup thankfully, but 10.2 pretty much borked my phone up, radios connect but don't, apps won't open, reboots tend to freeze in random locations.

Yeah I'm holding on to cm10.1 20130813 until a reliable build of 10.2. i don't mind jumping through hoops, but when the build literally disables all of my radios, gps, wifi, bluetooth, data, I already have an ipod ;)

Share this post


Link to post
Share on other sites

Did you make sure you flashed the Android 4.3 gapps? The 4.2 gapps don't work in 4.3. I did an update with my Nexus 4 without doing any sort of wipe (and that includes not wiping dalvik and cache which should never be needed). http://goo.im/gapps

And for root, due to the new changes with 4.3, you need to enable Root Access for both Apps and ADB under Settings -> Developer Options.

And anytime you update CM and it includes a major Android update, you should always make a backup... just in case.

Child_Healer and RejZoR like this

Share this post


Link to post
Share on other sites

cm10.1 20130813 isn't the latest, cm-10.2-20130814-NIGHTLY-i9100.zip, and that appears to be causing problems for a few of us. I was able to restore my backup thankfully, but 10.2 pretty much borked my phone up, radios connect but don't, apps won't open, reboots tend to freeze in random locations.

Yeah I'm holding on to cm10.1 20130813 until a reliable build of 10.2. i don't mind jumping through hoops, but when the build literally disables all of my radios, gps, wifi, bluetooth, data, I already have an ipod ;)

I know, I meant the lastest CM10.1 (4.2.2) before it gets to CM10.2 (4.3.x)

phishybongwater likes this

Share this post


Link to post
Share on other sites

Did you make sure you flashed the Android 4.3 gapps? The 4.2 gapps don't work in 4.3. I did an update with my Nexus 4 without doing any sort of wipe (and that includes not wiping dalvik and cache which should never be needed). http://goo.im/gapps

And for root, due to the new changes with 4.3, you need to enable Root Access for both Apps and ADB under Settings -> Developer Options.

And anytime you update CM and it includes a major Android update, you should always make a backup... just in case.

Thank you for this info. I will do this asap and see how it goes. I will now also make full backups before updating major versions, just to be sure.

Btw, why isn't Root access set to Apps+ADB by default for this build if it's required as such?

Share this post


Link to post
Share on other sites

And anytime you update CM and it includes a major Android update, you should always make a backup... just in case.

It would have been helpful for them to have included the fact that this was a major upgrade in the changelog, you know, like they always have in the past? They didn't, I only noticed when reading through to the end some references to cm10.2 that's when it clued in. I was expecting "this is the first build of this type for your device" or something, nope, just assumed it was another build and cooked my phone for breakfast.

I'm still baffled as to how it screwed the radios up that much, I'm used to them just being "off" but I've never seen that before, connecting, but not working at all. Icons stayed grey, couldn't even get "emergency calls only" connection.

And anytime you update CM and it includes a major Android update, you should always make a backup... just in case.

It would have been helpful for them to have included the fact that this was a major upgrade in the changelog, you know, like they always have in the past? They didn't, I only noticed when reading through to the end some references to cm10.2 that's when it clued in. I was expecting "this is the first build of this type for your device" or something, nope, just assumed it was another build and cooked my phone for breakfast.

I'm still baffled as to how it screwed the radios up that much, I'm used to them just being "off" but I've never seen that before, connecting, but not working at all. Icons stayed grey, couldn't even get "emergency calls only" connection.

Share this post


Link to post
Share on other sites

Thank you for this info. I will do this asap and see how it goes. I will now also make full backups before updating major versions, just to be sure.

Btw, why isn't Root access set to Apps+ADB by default for this build if it's required as such?

I'm not sure, but this was well known with all the unofficial builds floating around.

It would have been helpful for them to have included the fact that this was a major upgrade in the changelog, you know, like they always have in the past? They didn't, I only noticed when reading through to the end some references to cm10.2 that's when it clued in. I was expecting "this is the first build of this type for your device" or something, nope, just assumed it was another build and cooked my phone for breakfast.

As far as I can remember, previous changelogs never stated that they were moving to a new Android version. Maybe the occasional reference, but never a big announcement (but looking through the changelog for August 13th, I'm seeing a ton of references to 10.2). CM did say on their Google+ that they were rolling out 10.2 nightlies and that it required an update to gapps if you were running them. The problem is that 10.1 upgrades into 10.2 without a problem, unless you are running gapps. CM can't legally include the gapps, so the updater isn't designed to know if they require an update. It is something that you, as a user needs, to be aware of before you update.

Share this post


Link to post
Share on other sites

Tried:

-Wiping Dalvik Cache

-re-flashing cm-10.2-20130814-NIGHTLY-i9100.zip via recovery

-Flashing GApps 20130813 (4.13)

Now I can:

-Make/Receive calls

-Connect to Google Services (Blue signal indicators)

-Use some apps (Facebook, Whatsapp, etc.)

Still can´t:

-Get root access

-Use some Apps (Youtube, Google Play Music, Snapchat, etc.)

-Install/Update Apps from Play Store.

Can´t find "Settings -> Development" to allow Root.

Found "System Settings -> Superuser -> <Menu Button> -> Settings -> Superuser Acces" but it no matter what I select, it doesn't change.

Share this post


Link to post
Share on other sites

Installed Gapps but very little has changed. ANYTHING i try to download or update, just fails horribly, so i can't install anything and neither can i update anything. Not cool... any ideas what now?

Share this post


Link to post
Share on other sites

Can´t find "Settings -> Development" to allow Root.

Developer Settings have been hidden recently. You need to go to the "About" section in your settings and tap on your build version 7 times. The developer settings will then be visible just where they used to be.

My phone has not been a complete mess with 14-08-2013 CM10.2 update since I had done a factory reset in before anyways.

Though I had some minor hardware related problems such as apps telling me there was no access to the camera and a malfunction of the gyroscope.

Both could be cured by restarting my phone.

Also I noticed some new software issues as my lockscreen applications automatically align at the right side of the slider and the apps in my homescreen folders keep rearranging themselves. Some even got uninstalled out of nowhere.

Yet I can use my phone, so no bigger problems...

Share this post


Link to post
Share on other sites

Still can´t:

-Get root access

-Use some Apps (Youtube, Google Play Music, Snapchat, etc.)

-Install/Update Apps from Play Store.

Can´t find "Settings -> Development" to allow Root.

http://forum.cyanogenmod.com/topic/74526-how-do-i-update-cyanogenmod/#entry402538

Share this post


Link to post
Share on other sites

Well i can't use GooglePlay at all. It ALWAYS says "Error downloading X" and taht's it.

Share this post


Link to post
Share on other sites

Have you tried removing your Google account and re-adding it?

Share this post


Link to post
Share on other sites

It was working whit no problems until i rebooted the everithing died, rolllback

Share this post


Link to post
Share on other sites

Have you tried removing your Google account and re-adding it?

That's a lot of "don't work" that should be mentioned somewhere in the changelog so you don't wonder later wtf is going on and have to ask all that on forums. Unless it wasn't known even to CM devs. Though, at least we are getting useful answers here which is a start. Finally getting my phone to work...

Share this post


Link to post
Share on other sites

Hm, Root Checker Basic is still saying i don't have root. Hm. Any idea on this? I seem to have solved everything else except this...

Weird, Superuser doesn't even ask you if you want to allow the root access or not. The setting is there in the menus, but when app request root access, it doesn't popup. I get no toast popup or anything.

Btw, i made a nice list of things you have to do to make the CM 10.2 working:

http://rejzor.wordpr...roblem-solving/

I mostly write stuff there for myself but maybe it will help others as well :)

Edited by RejZoR

Share this post


Link to post
Share on other sites

I too have been having a lot of problems since updating to 10.2-20130814. I'll be honest though and say I didn't even bother reading the patch notes - I flashed blindly and hoped for the best; I didn't even update Google Apps.

However, once apps started throwing up exceptions and \data\logs started filling up with thousands of 1 meg files, I decided to be a little bit more thorough. My phone now seems pretty stable on the new build, and I can update and things like Gmail, Drive, Youtube, etc., as well as update via the store.

Here's what I did:

  1. Downloaded the 10.2-20130814 zip and the 20130813 GApps zip files, and popped them on the SD card.
  2. Rebooted into recovery.
  3. Flashed 10.2-20130814 again (probably a redundant step, but why not?).
  4. Flashed 20130813 GApps (I hadn't done this before, so this was pretty important).
  5. Wiped the dalvik and normal caches. Again, probably unneccessary, but why not? Note that I did NOT perform a factory reset.
  6. Rebooted, and pressed OK a bajillion times to get past the exception popups.
  7. Removed my Google account from the phone.
  8. Went into Settings, Apps, All, and performed a Force Stop, Clear Data, and Clear Cache on the following apps: Downloader, Google Play Store, Google Service Framework. Credit to http://androidforums.com/nexus-7/743895-cant-download-google-play-error-rpc-s-5-aec-0-a.html#1 for the idea.
  9. Reboot.
  10. Re-added my Google account.
  11. At this point I started getting some more exceptions, particularly from Google Drive and Keep, so I uninstalled every app that was throwing exceptions and reinstalled them from the Google Play store. That seems to have done the trick.

Hope that helps!

elFlexor likes this

Share this post


Link to post
Share on other sites
  1. Removed my Google account from the phone

Is there a way other to remove the Google account than deleting the 'Accounts.db' file, since that deletes all accounts. Didn't find an option in phone settings for that.

Edited by elFlexor

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now