I have been using the same old Fresh Evo rom from basically day one since I've had my evo when it first came out... Yesterday I decided it was finally time to upgrade from 2.1 to a 2.2 rom - so I downloaded the latest Fresh Rom 3.5.0.1 which worked fine except that I couldn't add my google account for the life of me. It wouldn't take when phone first booted up, or by manually launching the Market app either, didn't matter if it was via 3G or WiFi (and I checked and double checked and confirmed that data was working on both just fine!).
So I spend an hour googling around & find out about the YouTube app trick, so I sign in through that, and I'm in! Now when I go to Settings > Accounts & Sync, I see my Google account has been added. I can sync my gmail, contacts, and calendar. I thought all was good...
But now when I run the Market app I get the following: Attention - "A server error has occurred. Retry, or cancel and return to the previous screen." ...If I hit 'retry' it just shows the same stupid error & 'cancel' kicks me out to home screen. When I load GTalk it tries to load but just kicks me to the home screen...
Frustrated, I went on a rom flashing spree (before each flash I do a "Wipe data/factory reset" & "wipe cache" & "wipe dalvik-cache")... I installed the previous version of Fresh 3.4.0.1 (also froyo) and no dice. I then flashed the most recent 2.1 Fresh rom which was v1.0.1 (pre froyo) and it WORKED! So then I flashed back to the latest Fresh 3.5.0.1 but still have the same issues. I then flashed Myn's Warm TwoPointTwo RLS5 (which is a dope rom btw) but I am STILL getting the same stupid issues... Flashed back to Fresh rom v1.0.1 and of course that works... but it seems anything with Froyo doesn't work!
The EXACT same thing is happening to another Evo I also updated yesterday as well. So I know it's not a problem specific to just the ONE phone...
I'm stumped. Any ideas? I've tried clearing the cache for the Market app, I've done a factory reset via "Settings > SD & Phone Storage > Factory Data Reset", I've used a completely different & freshly formatted microSD card, I've enabled 'mock locations', I've ensured 'background data' was checked... I've even done the adb commands from geekfor.me/new-release/fresh-evo-3501/ with no luck...
This is driving me nuts!
Dam.
That sucks well did you upgrade from the push that sprint sent? I know that 3. 5.1 work for me. I pick up my evo on june 4th night
Device: HTC EVO 4G OS=2.2 ROM=Calkulin's EViO 2 v1.7.5 [email protected]#15 Hardware=0002 Software=3.70.651.1 BaseBand=2.15.00.11.19 Brower=Webkit 3.1 PRI= 1.90_003/60672
I've always done my updates manually... I have a 3rd evo that doesn't have this problem that I recently updated to Fresh 3.5.0.1 and it's working just fine. But it wasn't a launch phone, and after rooting, the first rom I flashed to it was a 2.2 based Fresh rom anyway...
Still racking my brain on this... I recently tried flashing this blue version of the market update @ http://forum.xda-developers.com/showthread.php?t=888330 - thought I'd give it a shot but I'm still having the same issues.
I've also flashed latest MIUI, EViO, SteelROM... no luck. If I don't do the YouTube trick, the Market will give me the following error: "Can't establish a reliable data connection to the server". But the funny thing is I am able to load webpages both prior & after trying to sign in with my google account. And then if I do the YouTube trick, again I am able to add my google account, but whenever I access the market it shows the error I mentioned in my first post...
I'm having this same problem..I haven't flashed a new market yet so I'll be trying that next.
Did you ever solve this issue?
Edit: Flashing new market didn't work, said instalation was aborted...I'm thinking cause it's for 2.3 GB and I'm on Froyo
Also, just to note, I had to do the youtube login trick in order to get my google accounts to sync
Same problem. This sucks.
I don't know if this would have much to do with it, but have you upgraded your radio? I know that most of the 3.70 based roms (the majority of newer roms) require a minimum radio version. I believe there is a post in the development section with all the radio files. Be sure you have your wimax partition backed up before you flash though, just to be in the safe side.
Sent from my PC36100.
i had a similar problem a while ago and what helped me was uninstalling the market with titanium backup, then going to settings/apps/manage apps/ and clearing the data from the market, then i downloaded the stock market, it was a while ago so i don't remember where i found the thread to the stock market download. but after doing that my market began working again
What's going on with the market? I literally downloaded ClockworkMod about 15 minutes ago and tried flashing something, the file wasn't there so I didn't end up flashing, turned the phone back on and the market just will NOT download. Has it gone down?
Also just quickly, if I flash RUU 1.32 or whatever it's called, will I lose root?
LeeRiley said:
What's going on with the market? I literally downloaded ClockworkMod about 15 minutes ago and tried flashing something, the file wasn't there so I didn't end up flashing, turned the phone back on and the market just will NOT download. Has it gone down?
Also just quickly, if I flash RUU 1.32 or whatever it's called, will I lose root?
Click to expand...
Click to collapse
You will lose root, yes
And market is working fine for me
Obivously something I've done along the way, http://zantekk.de/~desire_hd/offici....140e_26.03.02.26_M_release_155891_signed.exe this is the latest version we have root for, correct?
I just installed Android RevolutionHD 2.0.15 (and after a reboot 2.0.16) for the first time and trying to get my apps on the phone through the market and it seems that i have the same problem:
If i want to download any app with any connection it tries to start and soon it sais "unable to download... plz try later blabla"
Was wondering if the problem was related to the Custom Mod AR HD because someone in the mods thread had the same problem. But when you're saying you're on stock rom i think something is going on here^^
[e] Now its working again. Seems it was related with the store and not the rom.
I did correct permissions through Rom Manager (installed with apk) though im not sure if it is related to the market now working again.
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
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.
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.