[Q] unfortunately settings has stopped on full reset - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hi
first of all I would like to say that I'm a complete noob on android. I just switched over form IOS. I did have my device rooted and running the original stock rom.
I did a full reset this morning so that I can give my phone to my brother. When I was finished and went through the whole initial set up of wifi and google accounts, I clicked Finished and the "Unfortunately, settings has stopped" came up and there's nothing else I can do.
I tried doing a hard reset with the home,volume, and power button. Same problem persisted.
What else must I do to get this phone running again?

If you have a nandroid of the original stock after rooting and installing custom recovery I would restore that, if not you might want to install a new rom. Either way if /data is wiped and you're not worried about saving anything on the phone you have no worries.

Related

[Q] Can't wipe or factory reset encrypted phone

I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!

[Q] MyScript Resource Manager Stopped Working

Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
The only way was to reflash from Odin, fresh firmware. Download different version of your firmware, other than the one you stated. And reflash back with Odin, make sure your steps using Odin is correct.
Thanks for the reply. I finally got it working after my third time flashing it and formatting the cache a few times. Scary stuff!
Alas, the sporadic reboot still continues, so I'll have to work out how to fix that problem again now.
Thanks again.
Simpler fix from at&t device support center
c0dewana said:
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
Click to expand...
Click to collapse
I just had the same problem, spontaneously, from an unidentified source. Went to my carrier's, AT&T, local Device Support Center on a Sunday at noon, and one of the techs fixed the problem in under 3 minutes, impressively simply.
You will have to keep clicking OK when the error message repeatedly appears to continue with this process. That is normal.
Go to Settings > Application Manager > (scroll right to: ) ALL > (scroll down to: ) My Script Resource Manager (which should not be running) > Turn Off
Problem solved without Factory Reset. She impressed me and saved me a lot of time.

[Q] Galaxy S5 android 5.0 and recovery

Hi guys
I'm using samsung galaxy S5 (4.4.2) and recently upgraded to 5.0 using custom rom which I found here. It was working just great. I created 2 Nandroid using TWRP. One after a fresh installation another one after restoring my file contents from Helium and Titanium backup..
However something went wrong and i decided to restore my nandroid backup to revert back my changes. To my surprise both nandroid backup failed. I got a success message (using recovery mode) however when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
When I reflash the custom rom, it works fine, however i couldnt recover my system from nandroid backup.
I repeated several times but both nandroid gave me this same error. I even tried fixing permissions but no use. Then I used odin to flash a stock rom (BOA3) and rooted that using TWRP and most recent SU binaries. Its working great now, however I just wanted to know what is the best method to take a nandroid backup now? I'm afraid TWRP will bail out on me once again.
All the while I used CWM and it was great however 5.0 requires latest binaries and only can be rooted via TRWP recovery. Any suggestion? I just want to take a complete nandroid backup and save it in case if something goes wrong.
Thanks
sam20e said:
when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
Click to expand...
Click to collapse
I'm being plagued by this problem since I updated, flashing stock Lollipop using odin.
The problem first appeared after trying to restore my app+data using Titanium.
I went back to the beginning and flashed again but my phone is still unstable and I still occasionally get the '"System failed to start" "process failed to start" wait or press ok' issue that you have. A reboot generally sorts it out but the update has made my phone very unstable.
I also have big problems entering recovery and download modes using the buttons.
Cleaning my cache/davlik hasn't solved it either.
Hopefully someone can help us.
Anyone?
Got "Reactivation Lock" disabled?
Settings > General > Security
*Detection* said:
Got "Reactivation Lock" disabled?
Settings > General > Security
Click to expand...
Click to collapse
Yes. Thanks for the suggestion though.
Trouble in Galaxy town
Hi, I'll try make myself short.
1) Back when I had an Galaxy S2 i modded it a little bit but I haven't done it at all since then.
2) Now a few years later I got bored/sick of the stock ROM that comes with the S5 so I wanted to install something I knew had a good reputation, Cyanogenmod.
3) Getting a new recovery was an nightmare itself but eventually I got it working and made an backup so I could roll back if needed to.
4) Now, 24 hours of using CM12 I can only say one sentence: "What kind of crap is this?!" It's so unstable it's almost ridiculous. Bluetooth hangs up all the time thus requiring a reboot which leads to most-annoying-thing-ever-#2. The clock resets itself upon EVERY boot which makes WhatsApp go bananas. Doesn't matter if I previously set the time/date manually or let the phone do it automatically. Then there are the random hang ups that occur all the time and one third thing. Hardware acceleration in BS Player doesn't work AT ALL!
5) Said and done I reversed to the back up but oh man the phone wasn't happy about this (yes I made a wipe before recovering the backup). Nearly every basic service malfunctioned and were forcibly shut down. A factory reset made no difference...
6) For some reason I opened KIES and found out that an update with android lollipop was available so I (in a moment of despair) installed that hoping for salvation.
7) The phone boots properly and everything seems to be going wonderful until I realize that my network connection is high on something. Loses connectivity to my provider all the time thus the phone is totally useless.
8) I HAD to have a working phone for work and since no support is given on Sundays from Samsung I again installed CM12 just for the day.
Now to the good part!
9) When trying to recover the backup once again it's gone corrupt! Can't recover so now I'm stuck with buggy-as-h*ll-cyanogemmod12 with no means of reverting.
What-the-actual-****-do-I-do? Been trying to make some sense from the thread "Galaxy S 5 Original Android Development" but I feel so lost. So if someone could point me in the right direction I would be very grateful!
EDIT: What I want is to reverse back to original stock ROM. Screw the bloatware. I just need the phone stable and working!
EDIT2: After some more googeling I've figured out I need a stock ROM with the right CSC. I use a swedish carrier other than 'tre'. Shall I look for ROMs with CSC 'HTS' anyway? Can't find any info about other carriers in sweden.
EDIT3: Now I've found what I think is right on sammobile.com/firmwares/database/ (search query: 'g900f', first hit 'Sweden' CSC 'VDS'). Worried thou as it's Android Lollipop which made my phone go nuts. Can't find the KitKat version on that site...
EDIT4: Found the KitKat version on samsung-updates.com. The download speed is sooooooo slow (~6 hours)! Download limits should be illegal...
Thanks! //R

[Q] Help! Stuck trying to upgrade my wife's phone!!

Help! I'm trying to upgrade my wife's 9505 and I'm stuck.
She was running Stock (rooted) kit-kat, and I went to upgrade her to CM12.1
First, being a good boy, I took both a TiBu backup and a nandroid backup.
I did then manage to upgrade to CM12.1, but found a few issues (some missing phone numbers, etc that weren't sync'd with google), so I took a nandroid of CM12.1, wiped, and then restored the stock kit-kat nandroid.
That kinda worked, but some things are playing up - Waze doesn't work, SwiftKey comes up with an error trying to save the language file, the Daily Mail app and Gallary don't show any pictures, etc. Basically, not very usable.
So, I copied off the missing phone numbers, etc. and then thought that I'd wipe and restore the CM12.1 nandroid to get back to where I wanted to be - but it's just stuck at the CM12.1 animated boot logo and has been for ages.
So, I can't go back to kit kat, and I can't get back to CM12.1
Any suggestions/ideas?
It smells like some kind of file-system protection issue type thingy, but I tried the usual Fix Permissions, etc - all to no avail.
Someone please help (I'm really in the dog-house at the moment!!)
Thanks
Sorted! I had to basically wipe everything! Data, Media/photos, the works. Something really got screwed up, but I think I've got it going again now...

When WiFi is turned off I get 'Unfortunately System UI has stopped'

This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)

Categories

Resources