gixxer_751
Member
Updated firmware a couple days ago & now notice while on a call, an error box code 98 comes out, the phone still works normally while on the call but have to click ok on the error box in order to hang up. Any info?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Updated firmware a couple days ago & now notice while on a call, an error box code 98 comes out, the phone still works normally while on the call but have to click ok on the error box in order to hang up. Any info?
To it's customers!!!
This is not an isolated issue, it's network wide. There's another post on cricketusers.com that I'm on...
www.cricketusers.com/cricket-network-issues-discussion/31119-mms-not-working-properly-since-ota-upgrade-huawei-mercury.html
Their idiotic firmware update has messed up Mercurys all over the US and they're lying to their customers telling them it's not the update, it's an outage, it's your settings blah blah frickety blah... They've even got employees in the forums spreading misinformation. I've been with Cricket for almost 12yrs but I'm beside myself with the lack of customer care they're giving this issue.
Welcome to the forum. Early adopters of updates like this end up being the beta testers. That's why I wait to hear all of the feedback and make sure all of the bugs are worked out.To it's customers!!!
This is not an isolated issue, it's network wide. There's another post on cricketusers.com that I'm on...
MMS not working properly since the OTA upgrade for Huawei Mercury
Their idiotic firmware update has messed up Mercurys all over the US and they're lying to their customers telling them it's not the update, it's an outage, it's your settings blah blah frickety blah... They've even got employees in the forums spreading misinformation. I've been with Cricket for almost 12yrs but I'm beside myself with the lack of customer care they're giving this issue.
Never understood ringback tones, especially paying for them. I would never even pay for a ringtone lol. It's crazy that Cricket won't even admit there is a problem, but unfortunately can't say i'm surprised. There have also been reports of the MMS issue in this thread:Yeah, I discovered I was being charged for ringback tones... I despise ringback tones!!! Thanks for the welcome. I'm like a one man crusade to find as many Mercury owners having this issue... Cricket needs to own up to their mistake. Hell, I'd be happy just to hear one of their associates say "Yes, we know about the issue and are working on a solution." that would make me absolutely giddy at this point. But instead it's a bunch of lies and misdirection. I had one employee at a local store bald face lie to me b/c he assumed I'd be too stupid to know what he was talking about. Told me he fixed my phone, and sped it up, by enabling content filtering. Do you know what content filtering is??? Parental controls. I kid you not. I was livid.
Glad to hear you got satisfaction. By all means, people, complain if you are unhappy. You know what they say about the squeaky wheel...So cricket just called me and offered me a $30 credit... $20 to cover an in-store exchange for a new Mercury w/o the Muve Music Update on it and $10 for the inconvenience I've suffered. I WIN! MUWHAHAHAHA!!! Of course they still denied that there was any issue with the OTA update, or that anyone else had complained about the same issue... Which really would have made me giddy... But they admitted defeat, b/c if they'd really not been at fault I seriously doubt they would have made that offer to me... So I'll take that as an admission of guilt. =-D
So if you're one of the people being affected by this I urge you to contact customer service, or go into a corporate store, and reference this post... Hold them accountable and get your phones replaced and accounts credited. Or just root/flash and go on with your bad selfs... Either way, there's a couple of options for you. I have to say I was getting pretty pissed at Cricket over this issue... But the guy that called was nice, helpful, and perfectly willing to make the situation right. Regardless of whether or not that was genuine or them trying to fix a situation before it got out of hand... Either way, they probably just saved me as a customer.
Did the recent update*228.....seemed to have fixed error 98.....just fyi...muve update did mess up the quick boot thou
I'm willing to bet it came back though, didn't it? Hopefully not though!
I went and exchanged my phone today... It was a hassle b/c the CSR at the store was determined to find some reason to not do the exchange but he eventually caved, albeit reluctantly. And, ironically enough, it was the *****ebag that bold face lied to me the first time I brought it into the corporate store for this issue. The new Mercury's already have the 2.3.6 Android operating system and the 2.6.35.7-perf kernel... Which is what the update was supposedly supposed to do to the one's carrying 2.3.5... If they ever did, I'm beginning to wonder... So if you've bought a phone with the up to date firmware and you don't want Muve Music then there is NO reason to risk doing the update. He said *maybe* my update got screwed b/c I did it over Wifi and not on the Cricket 3G network, but whatever... I'm not risking the update a second time, especially since it apparently offers nothing other than Muve which, especially for someone like me that listens to obscure European electronic music, is a huge waste of time and money. Anyway, there ya have it. My saga is over. Ta da.