And now I'm also stuck in a boot loop. The phone powers on, I get "android.process.media" has stopped and then it reboots right away.
Welcome to CyanogenMod
 |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
1
Cm11 M10 Snapshot - "android.process.acore Has Stopped" - Please Help
Started by
drsaha94
, Sep 16 2014 06:30 PM
2 replies to this topic
#1
drsaha94
-
- Members
- 8 posts
-
Country:
- United States
-
Device Model:
SGH-T999 (T-Mobile) -
CM Version:
CM11 Nightly 09-09 -
Recovery Image:
Cyanogen
Posted 16 September 2014 - 06:30 PM
#2
PsychoI3oy
-
- Administrators
-
- 537 posts
Bugmonkey
-
Country: - United States
-
Device Model:
D2lte(tmo) -
CM Version:
11M* -
Recovery Image:
Cyanogen
Posted 16 September 2014 - 06:48 PM
I'm guessing you updated over a nightly from after 9/9 [ http://www.cyanogenm...1-0-m10-arrives notes that cm11m10 was branched on Sept 9th ]?
Assuming that, I posted this elsewhere:
The problem is that after the M builds (based off cm-11.0/stable) were branched on the 9th, upgrades went into the source code in the last week. Going from a 20140915 nightly to cm11m10 is essentially downgrading by a week, and Android has never handled downgrades well.
Many of the crashes I've seen so far from this (because a lot of people missed that blog post apparently) are in mediaprovider's database:
"java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: Can't downgrade database from version 701 to 700"
You may be able to adb shell into recovery, mount /data and manually delete the database (which will then re-index all your photos and music but shouldn't actually delete anyting). Or you may be able to titanium backup everything but system settings, wipe, reinstall cm (and gapps) and restore the backup.
Assuming that, I posted this elsewhere:
The problem is that after the M builds (based off cm-11.0/stable) were branched on the 9th, upgrades went into the source code in the last week. Going from a 20140915 nightly to cm11m10 is essentially downgrading by a week, and Android has never handled downgrades well.
Many of the crashes I've seen so far from this (because a lot of people missed that blog post apparently) are in mediaprovider's database:
"java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: Can't downgrade database from version 701 to 700"
You may be able to adb shell into recovery, mount /data and manually delete the database (which will then re-index all your photos and music but shouldn't actually delete anyting). Or you may be able to titanium backup everything but system settings, wipe, reinstall cm (and gapps) and restore the backup.
#3
drsaha94
-
- Members
- 8 posts
-
Country: - United States
-
Device Model:
SGH-T999 (T-Mobile) -
CM Version:
CM11 Nightly 09-09 -
Recovery Image:
Cyanogen
Posted 16 September 2014 - 08:26 PM
I just booted into recovery and flashed the 09/15 nightly. Thanks so much for your help though.
