[Q] I want to factory reset - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

My phone is constatly freezing/rebooting andf the only option I see to fix this is to factory reset it. My question is this: I have a AT&T S4 MF3 with safestrap running a custom ROM. I am rooted obviously. Is there anything special I need to do?

skateman274 said:
My phone is constatly freezing/rebooting andf the only option I see to fix this is to factory reset it. My question is this: I have a AT&T S4 MF3 with safestrap running a custom ROM. I am rooted obviously. Is there anything special I need to do?
Click to expand...
Click to collapse
Nope. Factory reset won't affect safestrap or root, just boot into safestrap and factory reset which ever slot you're running.

Related

com.android.phone has stopped

Hi guys ino this problems has been posted before bui cant find the answers none of them work.
Basically this is note my phone its my grandads i updated the Firmware from Gingerbread to ICS last week and when people phone him this process stops. Now ive tried going into reject messages settings and having less then 5 and it does nit work. The phone is NOT rooted and will not be as I don't want to screw upp their warenty.
I would normally wipe permissions but I cant since CWM is not installed.
I also cant replace phone apk as I need Root access.
Please any help would be great.
Firmware version. : PDA:LQ2 /PHONE:LPT / CSC:LP4 (CPW)
Stock ICS 4.0.3 ROM
Guess first thing to try would be to wipe cache and data on the dialler app.
Every time ive had this problem though, the only tying thats worked has been a factory reset. Id watch out doing this on an ics rom though, samsung have now admitted the emmc issue and are working on stable kernels but they will probably be out a month or so.
Alternatively you may be able to use an alternative dialler from the play store.
Sent from my GT-N7000 using xda premium
Apologies, i think you'd need to be rooted to install an alternative dialler.
Sent from my GT-N7000 using xda premium
Wiping/factory reset will do the trick, I was having the same problem, coming from pre rooted Gingerbread to flashing non rooted stock ROM ICS through PC Odin.
After wiping problem no more force close on phone.
dio62000 said:
Wiping/factory reset will do the trick, I was having the same problem, coming from pre rooted Gingerbread to flashing non rooted stock ROM ICS through PC Odin.
After wiping problem no more force close on phone.
Click to expand...
Click to collapse
i wouldnt advise a factory reset with all the info we now know,would you like to be responsible for his bricked phone
i would wait til your in a position to install root safely and use a safe kernel then wipe
What I meant was a wipe after stock ROM was flashed through Odin, doesn't that remove CWM? It IS safe to do factory reset without CWM installed is it? And if you can't use your phone without well, having com.android.phone running and you do just a factorey reset it needs to go back to Samsung anyway. Hard resetting your phone doesn't seem to break warranty to me, does it?
Any advise will be appreciated, I'm still trying to figure out what to do and how to root ICS.
Thanks.
Do NOT factory reset in ICS as it could initiate the superbrick. Only wipe in CM9 or gingerbread.
Ok. Thanks. Already did it though . I was lucky to not brick the damn thing
Rolling back to Gingerbread doesn´t work, unfortunately, I get errors/fc on at least 3 important processes.
Edit: Well, I managed to get Gingerbread working again after all; flashed back to GB through PC Odin and then do a full wipe/factory restore.
wipe cache and dalvik cache will do the trick.
Guys I said that I do NOT have CWM installed nor am i rooted so little of these options will work. But I factory reset it went into reset area of setting and restored to stock and everything works fines now so THANK you also another note my granny's Galaxy s3 had the same problem after fixing the Galaxy note about 3 days after had to reset hers as well and its fine now. I wondered if it could be because i brought both phones from Carphonewarehouse ?
Thanks for your help

[Q] Factory reset a rooted, wifi mod verizon - cause reset issue?

May need to reset to see if bootloop issue is a hardware problem as last resort
Verizon 4.2.2 11A stock, build JDQ39B, rooted, wifi tether mod, OTA been blocked by Titanium for months, no custom recoveries or rom.
Can I do a factory reset and wipe with the phone in the above condition or will the root and mod cause an issue?
Thanks

[Q] Bricked encrypted S4!?!?

My 2 year old pushed the wrong pin 5 times and locked up my encrypted S4. Now when it asks for pin after restart and I put in the right one, it says it's wrong. I tried to Odin a fresh mk2 stock rom, but I kept getting errors. Write being enabled might be the problem, but, I don't know. Thanks!
sether52 said:
My 2 year old pushed the wrong pin 5 times and locked up my encrypted S4. Now when it asks for pin after restart and I put in the right one, it says it's wrong. I tried to Odin a fresh mk2 stock rom, but I kept getting errors. Write being enabled might be the problem, but, I don't know. Thanks!
Click to expand...
Click to collapse
Hate to say it but I think trying a factory reset might be your best best. Good luck..
BIGSAMDA1ST said:
Hate to say it but I think trying a factory reset might be your best best. Good luck..
Click to expand...
Click to collapse
Wish I could. I keep getting the "restart kies" screen. The one time I was able to get into recovery mode and tried a factory reset/wipe, cache wipe I thought I was successful. When it booted up I thought I was golden and then realized my wifi wasn't working and neither was bluetooth. So, I went back into ODIN download mode and tried to flash the MK2 at that point and it failed and failed and failed. Any suggestions on factory resetting it?
I used to have my S4 encrypted but I don't anymore because I have heard it creates issues. I don't have a suggestion outside what you have tried, when you are flashing a new ROM, there should not be any issues once it has been completely wiped. Another option is to wipe and try flashing a custom ROM instead. Good luck let us know what happens.

Cant disable extreme power save mode or boot anymore..

Okay so i think i bricked my s6 edge plus... I debloated it and i must of disabled the touchwiz launcher since i didnt use it..So now i cannot disable it ..i rebooted in recovery and cleared cache thinking maybe that would fix it but now when i boot it just stays at the tmobile splash screen..any help? i know i can factory reset but i dont want to lose my data so is there anyway i can fix it like reflashing stock firmware ? It is non rooted and stock recovery.
jordy787 said:
Okay so i think i bricked my s6 edge plus... I debloated it and i must of disabled the touchwiz launcher since i didnt use it..So now i cannot disable it ..i rebooted in recovery and cleared cache thinking maybe that would fix it but now when i boot it just stays at the tmobile splash screen..any help? i know i can factory reset but i dont want to lose my data so is there anyway i can fix it like reflashing stock firmware ? It is non rooted and stock recovery.
Click to expand...
Click to collapse
just flash stock firmware over it. you wont lose data.
jer0o1 said:
just flash stock firmware over it. you wont lose data.
Click to expand...
Click to collapse
will i lose my data?
Nope you won't lose data.

Unfortunately the process com.android.phone has stopped

I factory reset it and it stay pops up constantly!
Does anyone have a solution to this problem?!? Im willing to try anything. Ive tried all the ones on youtube with the "solution" but it does not work.
I am also running stock too
I also have this problem. Phone is stock, no mods
Is there a way to restore the phone without the built in factory reset?
I think the recovery files built into the phone may be corrupt...
Tried a factory reset and it didn't work
gtmaster303 said:
I also have this problem. Phone is stock, no mods
Is there a way to restore the phone without the built in factory reset?
I think the recovery files built into the phone may be corrupt...
Tried a factory reset and it didn't work
Click to expand...
Click to collapse
Hey there! I fixed this problem by actually rooting my phone! It went away right when I rooted it. It seems that it cleared the cache.

Categories

Resources