- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So Froyo has been out for about four months now. Every time I try to update to Froyo I get "SERVER UNAVAILABLE Check for software update when server is available", does it really take four months to roll out the froyo update to all the fascinates or is it just my phone.
Hardware ver. i500.04
Model Number. SCH-I500
Firmware ver. 2.1-update1
Baseband ver S:i500.04V.DL09
Kernel ver. 2.6.29
Build Number SCH-I500.DL09
This is the most up to date my phone is. I want Froyo, I am tired of waiting, of tech support giving me the run around and store managers telling me to keep trying the OTA.
Can anyone help or point me in the right direction?
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If wildmans suggestion does not work....
Have 3 fascinates. 2 would OTA just fine. one would not.
Kept getting 'Server Unavailable' Code: 500.
Tried soft resets, factory resets, battery pulls. Nothing fixed it.
Called Verizion customer support, had them transfer me to 'tech support'.
Told them the problem, they wanted to send a refurbed phone. Told them.. "no thank you".
Told them first...Please 'deactivate' my problem phone on your network...
then once done... tell tech to 'reactivate' my probem phone.
They seemed unsure, but did it for me anyway. Tell them this solution is on verizons customer
support forum and had worked for many Fascinate owners..
Took 2 minutes. When they are done I turned on phone, did the *228 Option 1 to program.
Then went back to about...system updates..Check new and VOILA Phone updated just fine !!
Verizon tech was amazed and said he would share with other techs. Guess he did not....
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Uses complained about this when Droid X update was released and it was learned that the update was blocked by apps that was installed, some could boot into safe mode and get update to work... The only other working method was a hard reset.
Try Booting into Safe Mode and then check for update by....
- Press and hold the Power button.
- Select Power off.
- Press the Power button.
- When the Verizon logo appears, press and hold Menu.
- Safe Mode will display in the lower-left.
- Press and hold the Power button.
- Select Power off.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If wildmans suggestion does not work....
Have 3 fascinates. 2 would OTA just fine. one would not.
Kept getting 'Server Unavailable' Code: 500.
Tried soft resets, factory resets, battery pulls. Nothing fixed it.
Called Verizion customer support, had them transfer me to 'tech support'.
Told them the problem, they wanted to send a refurbed phone. Told them.. "no thank you".
Told them first...Please 'deactivate' my problem phone on your network...
then once done... tell tech to 'reactivate' my probem phone.
They seemed unsure, but did it for me anyway. Tell them this solution is on verizons customer
support forum and had worked for many Fascinate owners..
Took 2 minutes. When they are done I turned on phone, did the *228 Option 1 to program.
Then went back to about...system updates..Check new and VOILA Phone updated just fine !!
Verizon tech was amazed and said he would share with other techs. Guess he did not....
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree with Herbb623. After the same problem, and much message board research, I did the same thing. Visited my local verizon store, told them to deactivate and reactivate phone first before they tried anything else. It worked. The guy who helped me said he would have tried that, but probably not right away. Anyway, helped them out, they helped me out. Happy ending for everybody.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone tried clearing the System Cache for device through recovery to see if this worked also?