Hi guys,
Jelly Bean OTA > Factory reset.
Exchange config not working. After entering correct details and clicking next, it force closes, every time.
Any ideas?
Cheers,
TD
thedynamix said:
Hi guys,
Jelly Bean OTA > Factory reset.
Exchange config not working. After entering correct details and clicking next, it force closes, every time.
Any ideas?
Cheers,
TD
Click to expand...
Click to collapse
It would appear this isn't the only thing a factory reset messes up, another user had problems changing wallpapers and saving app settings. He managed to get around the issue by flashing a 4.0.4 ROM, the updating, and not doing a factory reset. I suggest you try the same tactic, if you need to wipe the phone, use the wipe functions in CWM (or other recovery you use).
What does flashing to a 4.0.4 ROM mean and how do I do it?
Sorry if it sounds like a stupid question.
Bloody Android! Why doesn't it just work!? So many issues, after issues, after issues!
Related
Let me first start off by saying that I have been flashing ROM's since the D1 days but haven't posted enough in the past to ask for help in the specific developer forums. I have tried to find answers but can't seem to get any resolution.
Since Thursday, I have been attempting to flash JB on my Verizon Nexus. All of the ROM's I have flashed work, except for one key feature, Google Now. It doesn't matter if I flash Vicious 2/3, JellyBelly, or Vanir, the results are the same.
When I try activating Google Now, an error message will state that "Google Search has stopped". The only way for me to get Google Search to work from this point forward is to either Wipe in Boot or kill the data and force stop Google Search in the Settings Menu.
The first thing I tried was revert back to ICS and then go back to JB.
Next I tried to go into Boot, FR about 4 times, clear the Cache about 4 times, wipe the Davlik, flash Superwipe, and then reflash JB and Gapps.
Next I went as far as creating another Google account from scratch to see if it was a settings issue.
Finally, I made the decision to unroot and relock my device, and then unlock and root.
None of these things fixed the Google Now issue.
If anyone has any direction I would really appreaciate it. Google Now is the only thing that won't seem to work at all.
^_-
I have this issue too.
P1raten said:
I have this issue too.
Click to expand...
Click to collapse
This post is pointless and spam, if you want answers describe your problem exactly cause he may have something different, and it is 2 months old. But try reflashing gapps for your device, or a wipe. It usually works for me on my phone.
Sent from my SGH-T959 using xda app-developers app
Hi there, I'm not too sure where to post this, I'm new here. I had downloaded the spirit ROM for my galaxy s3 and loved it. It's awesome and I love all the features...one problem though. Whenever I restart the phone it resets all my defualts...like my default messenging app, it would continue to reset my launcher (until I disabled all the others) and for my Cerberus anti theft app. This is a bit of an issue as I have device administrative options that keep being reset. It's a pain in the ass...I was wondering if anyone has any suggestions as to what I can do to keep my default settings and enjoy this amazing ROM at the same time. Thanks for your insight!
hey10103 said:
Hi there, I'm not too sure where to post this, I'm new here. I had downloaded the spirit ROM for my galaxy s3 and loved it. It's awesome and I love all the features...one problem though. Whenever I restart the phone it resets all my defualts...like my default messenging app, it would continue to reset my launcher (until I disabled all the others) and for my Cerberus anti theft app. This is a bit of an issue as I have device administrative options that keep being reset. It's a pain in the ass...I was wondering if anyone has any suggestions as to what I can do to keep my default settings and enjoy this amazing ROM at the same time. Thanks for your insight!
Click to expand...
Click to collapse
Did you perform a full wipe before flashing the rom?
Not used any backups?
Just flash it again and if the error persists, ask in the rom hread for help.
BTW a really great and totally stable rom for S3 is CandyKAT
***SOLVED***
LS.xD said:
Did you perform a full wipe before flashing the rom?
Not used any backups?
Just flash it again and if the error persists, ask in the rom hread for help.
BTW a really great and totally stable rom for S3 is [Link to CandyKatRom deleted due to new user regulations]
Click to expand...
Click to collapse
So it turns out my Cerberus App was conflicting with the SPIRIT ROM. I found that whenever I tried to have the app automatically take a photo the phone would restart (I assume because the software isn't compatible with that function of Cerberus) and reset the defaults of the App and turning off the Administration function. I didn't realize that I had the app set up to automatically take a photo of someone if they got the password wrong more than twice....see where this is going? this explains the random resets, and the resetting of the defaults! after turning off that function of Cerberus the problem has not persisted since!
Thank you all so much for your help!!
PS I will also try out that CandyKat ROM
Hello guys, I have this s7 duos (gt-g9305fd) (UAE), I rooted it about a week ago and everything was going okay, but yesterday while I was playing with developer options I turned on OEM lock/relocked it, and then after the phone restarted I got this message "Custom binary blocked by FRP lock", I searched for solutions online and I read that I have to flash the stock rom to fix the issue, so I did (Indian Stock Rom). After that, I booted it up and got several "x is responsive messages" (android.process.media, my files, Google x, Google y, Google z) so I thought it's a permission issue so I rooted it again, but that doesn't seem to fix the issue .. Is there a way to fix this?
AndroNueb said:
Hello guys, I have this s7 duos (gt-g9305fd) (UAE), I rooted it about a week ago and everything was going okay, but yesterday while I was playing with developer options I turned on OEM lock/relocked it, and then after the phone restarted I got this message "Custom binary blocked by FRP lock", I searched for solutions online and I read that I have to flash the stock rom to fix the issue, so I did (Indian Stock Rom). After that, I booted it up and got several "x is responsive messages" (android.process.media, my files, Google x, Google y, Google z) so I thought it's a permission issue so I rooted it again, but that doesn't seem to fix the issue .. Is there a way to fix this?
Click to expand...
Click to collapse
Hi
Try factory reset...
Factory Reset..
MAX 404 said:
Hi
Try factory reset...
Click to expand...
Click to collapse
Factory reset is my last resort - I'm just trying to avoid installing all the apps again..
AndroNueb said:
Factory reset is my last resort - I'm just trying to avoid installing all the apps again..
Click to expand...
Click to collapse
Did you clear dalvik and cache from recovery? maybe it helps
AndroNueb said:
Factory reset is my last resort - I'm just trying to avoid installing all the apps again..
Click to expand...
Click to collapse
Try to go in and force stop android.process.media and cmlear its data and reboot. If that does not work jreinstall stock firmware with odin.
MAX 404 said:
Did you clear dalvik and cache from recovery? maybe it helps
Click to expand...
Click to collapse
I did clear dalvik cache/cache, that doesn't see to fix the issue
jdoggawesomex900 said:
Try to go in and force stop android.process.media and cmlear its data and reboot. If that does not work jreinstall stock firmware with odin.
Click to expand...
Click to collapse
How can I force stop android.process.media, what app is that? Also, I did flash stock firmware and that's the only reason I'm getting these errors.. I'm guessing it has to do with Google * apps or some stock app(my files gets unresponsive too, also can't see anything from gallery/my files)
AndroNueb said:
I did clear dalvik cache/cache, that doesn't see to fix the issue
How can I force stop android.process.media, what app is that? Also, I did flash stock firmware and that's the only reason I'm getting these errors.. I'm guessing it has to do with Google * apps or some stock app(my files gets unresponsive too, also can't see anything from gallery/my files)
Click to expand...
Click to collapse
Maybe try to reflash gapps. It wont reset your phone
The problem appeared after upgrade to nougat. I tried factory reset, it was ok for the first hours and now, the problem returned.
Anyone facing the same problems?
Phone not rooted, running on official rom and problems occurs even in safe mode....
alexpen said:
The problem appeared after upgrade to nougat. I tried factory reset, it was ok for the first hours and now, the problem returned.
Anyone facing the same problems?
Phone not rooted, running on official rom and problems occurs even in safe mode....
Click to expand...
Click to collapse
Hi
How did you upgrade?
OTA , flashing??
If OTA did you upgrade al your apps , maybe one of them is making trouble
If flashing , how? and also did you upgrade your apps
Hey, thanks for the answer. It was OTA. I suppose all apps are up to date since I restored to factory settings and re-installed them.
The problem is still there even in safe mode...
alexpen said:
Hey, thanks for the answer. It was OTA. I suppose all apps are up to date since I restored to factory settings and re-installed them.
The problem is still there even in safe mode...
Click to expand...
Click to collapse
Hi
yeah is odd , i would think it has to be app related .....
When you get the error ..after you introduce the password? what about if you ask your phone to forget your old connection , it allows you to connect to the new one then?
I would try to wipe dalvik and cache from recovery and /or reflash stock rom again..maybe something went wrong at least the modem
MAX 404 said:
Hi
yeah is odd , i would think it has to be app related .....
When you get the error ..after you introduce the password? what about if you ask your phone to forget your old connection , it allows you to connect to the new one then?
I would try to wipe dalvik and cache from recovery and /or reflash stock rom again..maybe something went wrong at least the modem
Click to expand...
Click to collapse
It happens right after when I tap on the network I want to get connected to...
alexpen said:
It happens right after when I tap on the network I want to get connected to...
Click to expand...
Click to collapse
Did you try the other suggestions I mention?
MAX 404 said:
Did you try the other suggestions I mention?
Click to expand...
Click to collapse
I tried to wipe the cache with no success. I am on a trip right now, and I cannot wipe the dalvik for the moment.
I figured out a walkthrough though using a third party app called "WIFI manager". I even managed to install a certificate and use it for a connection to an "eduroam" network...
Hey all,
I have a used SM-R890 that I'm struggling to go through the setup process.
It has been completely software reset and I believe the previous owner has run the good old debloat (https://forum.xda-developers.com/t/debloat-galaxy-watch-4.4324147/)
I have tried running the recovery to factory from the boot menu as well as clearing cache.
The setup will show on my phone and let me get as far as about 87% of the setup process then try and re-pair the watch on Bluetooth.
Can anyone think of another way that I can get this back to complete factory or any other work arounds?
SneakyStevie said:
Hey all,
I have a used SM-R890 that I'm struggling to go through the setup process.
It has been completely software reset and I believe the previous owner has run the good old debloat (https://forum.xda-developers.com/t/debloat-galaxy-watch-4.4324147/)
I have tried running the recovery to factory from the boot menu as well as clearing cache.
The setup will show on my phone and let me get as far as about 87% of the setup process then try and re-pair the watch on Bluetooth.
Can anyone think of another way that I can get this back to complete factory or any other work arounds?
Click to expand...
Click to collapse
Try doing a factory reset on the watch
2nd example in video
louforgiveno said:
Try doing a factory reset on the watch
2nd example in video
Click to expand...
Click to collapse
Thanks,
I've given that ago and even with that and resetting the cache it still does the same thing
SneakyStevie said:
Thanks,
I've given that ago and even with that and resetting the cache it still does the same thing
Click to expand...
Click to collapse
Were all the "debloated" apps restored?
Also did you try force closing galaxy wearable app and clearing data?