Originally Posted by tw3ak
Hey guys, new owner of the Verizon Note 3.
Love the phone and everything is fast and great.
I'm on 4.3 MJE and rooted. Safestrap installed with no slots, just the stock. Wanted to be able to make backups and have the recovery option.
Just this morning my Note 3 stopped letting open the settings from any angle. From notification panel or anywhere else.
It immediately closes and shows the message "Unfortunately, Settings has stopped"
I tried rebooting to safestrap and wiping cache and dalvik cache.
I have some system apps frozen with Titanium backup, but have defrosted the ones I very recently froze to see if that helped. And still not able to get into settings.
Any advice? I'm sure you all appreciate how much of a pain in the butt it is to factory reset or flash and start over! I hate reconfiguring my apps and settings! So if that can be avoided in any way I'd be soooo happy!
I'm pretty sure you need to reboot after unfreezing; you didn't mention if you did that.
The best way to avoid this kind of situation is to make Nandroid backups before you start tw3aking. Sure they are huge, but look at your situation now. You can always delete them after some time after it is clear they are not needed, but you can't create them out of thin air when it is too late.
So, before you make things even worse with further experimentation, make a Nandroid right now of your semi-broken setup. If you break things even further trying to fix this current problem, at least you can go back to where you are right now. You might want to make an TiBu market app/data backup as well and get the TiBu backups onto external media in case you need to go all the way back to Odin.
Dump your logcat after the "Settings" crash. There will be further clues there (possibly undecipherable, but hey.) Post that up to pastebin.com for others to look at if you don't grok it. (but scrub any personal data in there first). If you don't already have USB debugging turned on, you can use a terminal emulator or a Logcat capture app.
# logcat -c (to clear the log)
( force the settings crash)
# logcat -v threadtime > /sdcard/my_logcat_after_settings_crash.txt
There is a chance that it is something simple, e.g. one of the sqlite databases in /data/data/com.android.settings is corrupted, but the various Activities that are launched from underneath "Settings" touch stuff all over the /data partition (e.g. /data/misc and elsewhere). From where you are right now, there is no way to know whether your problem is due to:
(1) a problem in /system
(2) a problem in /data