[Q] Sprint Visual Voicemail App won't update - EVO 4G Q&A, Help & Troubleshooting

I have tried several times to update the voicemail app (it notifies me there is an update), but it fails every time. It downloads, tries to install, then says "application not installed." Why? What is wrong? Un-rooted, but still have S-OFF (working on this with a different thread). Stock ROM with all updates to 2.3.5.
Thanks.

Related

Sprint Voicemail Upgrading Application!?!?!

i just recently rooted, now i have a fresh rom flashed, and I have a voicemail notification to upgrade my voicemail app, i press upgrade and it starts downloaing and about half way thru the downloading process, it ALWAYS Fails!!?! Has this happened to anyone else, or maybe some idea's???/
Fresh Updater
You need to go into fresh updater and update your theme server and update the voicemail app from there. He has a special signature on the rom that won't allow you to update normally. There are detailed instructions on this in the fresh evo thread and on the geek for me website, which is the developers own website.
i am having the same problem. i rooted today and then did the unrevoked forever then did the ota. says there is a voicemail update then i try then it fails at about 25%
same here. froze my phone, i reflashed. im using DC 3.5

[Q] Voicemail app update failed...

An icon popped up today informing me that there's an update for the voicemail app. It downloads the update, but then gives me an error "Sorry, there was a problem installing the update".
I am running Calk's latest ROM 2.8.1. My current voicemail version is T.5.2.0.24.
Has anyone else had this issue? Does anybody know where the update is saved?
I was having a major issue with this too. I believe it's a connection speed issue because I finally got it to download the update via wifi. If you don't have access to wifi try updating your profile and prl on your phone if your using a leaked modem

[Q] Weird issue with market today!

So I am having weird issues, not rooted, running latest software. My volume when receiving texts was very low, even though my volumes were all the way up. Also, I keep getting facebook updates, they download but when I install I get an error message, I have to delete apps, even though I barely have any. I figured it was time to re root anyways. So I RUU'd back to the last version, unlocked the bootloader and rooted. I'm on the stock rom, before this latest update that ends in .6 My market now says downloading, but it wont actually download. I've tried restarting, I've cleared the market data and cache. Nothing.
Finally got one of my apps to update, using wifi, only at 19% after about an hour.....

[Q] "Account Action Required" error on rooted 4.3

I recently rooted my stock ATT 4.3 UCUEMJB with CF-AutoRoot which worked like a charm. However I get my work email on this phone which uses Google Apps Device Policy. I now regularly get the "Account Action Error" error constantly, though my email is still working fine. Clicking on the error simply takes me to the download page for Google Apps Device Policy (which of course I have).
Any suggestions on what to try? Thanks!

Unfortunately the process com.samsung.syncservice has stopped...

This is just documenting a question and solution to a problem that took me a long time and a lot of searching to find. My two sons are earch running a Samsung Galaxy S3 with rooted stock ROMs pretty much since the phones were purchased. Out of the blue and just with this latest NJ2 update, one of their phones never received the OTA and would instead get the following error message: "Unfortunately the process com.samsung.syncservice has stopped". This would appear again when I would try to Update Firmware, Update Samsung Software, Update Profile, and Update PRL. After receiving the error, when I would reboot the phone I could update the PRL and Profile, but if I tried to update Samsung software or update firmware, the message would appear again.
Turns out that the solution was just to clear data/cache on the SyncMLSvc app via Application Manager, and then reboot the phone. Now all is well. Hope this helps someone else, and makes the solution a lot easier to find than it was for me.

Categories

Resources