on 03-11-2012 15:08 - last edited on 03-11-2012 15:18 by Toby
Looks like there has been another foul up on JB 😞 Some people may be recieving the error above when trying to open messaging. I called o2 who said they have had multiple reports and the only known fix is to backup with kies and then restore.
Solved! Go to Solution.
on 14-11-2012 10:30
@Anonymous wrote:
@micklep wrote:
Quick update. After a factory reset everything worked for a week... then it died again. I attempted to open through s-voice and no joy.
Then I downloaded go sms pro, installed it, used it then restarted. After a restart I opened messaging again and it worked!
It looks like the problem is the messages o2 send. When you get it working you should notice two threads from o2, delete them both then enjoy.
To summarise:
Install and use go sms pro (free from play store)
Send one message using it
Restart
Open messaging (twice if it crashes the first time)
Delete o2 messages (should be two from different numbers)
Enjoy
Please let me know if this works for anyone else
This fixed the issue for me on my S3. And after I was told by the chap in the O2 shop that a factory reset was the only way to fix it as it was a (sudden) common problem.
Just out of interest, did you also have a push message from o2 when you got it working again? and one from your own number (minus the last three digits)?