Hi, so I have a stock r800x, with Verizon. The phone is fairly new and I've only factory reset it once. I normally check for updates here and there, hoping to get an OTA update.
The issue I'm having is that a couple of weeks ago or so I noticed when I hit Update Now, and the screen then gives the option, Info or Check for Updates, I check for updates, the little blue box pops up to check for a second, then it all closes and it's back at the About Phone screen. Sometimes when I'm sitting at the screen for Info or Check for Updates it just closes. If I have WiFi on it warns that it needs to turn it off first, I say Ok, it turns it off, 3g pops up, then close, WiFi never turns back on automatically.
I know this isn't how it's supposed to act since it used to work properly. It used to say "your up to date" or something along those lines, and if WiFi was on, it would reinitialize it after it checked.
Now this wasn't bugging me before, because I knew there wasn't an OTA out yet. Now of course there is, but I can't get it. I have a feeling a factory reset would fix the issue, and if that's all I can do, that's what I'll end up doing. Though setting up my phone and all my apps and settings and re-downloading everything can be annoying and very time consuming. So I wanted to see if anyone might have any ideas on what I might be able to do, before I decide to wipe it all.
Here's some info:
MobileCare version: 6.1.0_B191_SE
Build: 3.0.E.2.89
Android: 2.3.2
PRL Version: 52363
Thanks for any replies in advance.
I had the same problem and fixed it this weekend pretty easily
Just go to Manage Applications and find "Mobile Care" and select "Clear Data". After it clears go back into update and it should work.
Rogue Leader this is Carlos Spicy Weiner over. lol couldn't help myself but yea 2.3.3 just came out you may just want to keep trying
Awesome it's downloading the update, gave you a thanks. Appreciate it, saved me a wipe, and a lot of hassle.
Related
For anybody who's interested
Has anyone had a successful update, there are a couple of guys on the o2 Forums that are having trouble.
o2 Forum
yes, mines went with no problems
stock O2 desire
bjproc said:
yes, mines went with no problems
stock O2 desire
Click to expand...
Click to collapse
Oh ok, and was there anything special you did? How much free space? which screen SLCD or AMOLED?
Sorry for all the questions, don't need a shiny new paper weight
Can someone confirm the software number and baseband? I'd like to see if it's the same release as before.
teppic74 said:
Can someone confirm the software number and baseband? I'd like to see if it's the same release as before.
Click to expand...
Click to collapse
kernal version 2.6.32.15-gd96f2c0
software version 2.
14.207.1
build number 2.14.207.1 cl233777
This is the info from the o2 Forums
Looks like it's the same release then. Cheers.
matt.tumber said:
Oh ok, and was there anything special you did? How much free space? which screen SLCD or AMOLED?
Sorry for all the questions, don't need a shiny new paper weight
Click to expand...
Click to collapse
no, nothing special, just seen the update today and updated it, as i've said, mines was a stock phone with nothing done to it.
it's an AMOLED
sorry, not sure how much free space i had, but i don't have a lot on it, if this helps
Installed ok here too had to remove some apps as it needed about 28 meg free.
Sent from my HTC Desire using XDA App
Finally! Updated to 2.2 without any problems (have an AMOLED display).
Arite.
Sent from my HTC Desire using XDA App
I'm not touching this update until O2 confirm what the problem is. Apparently, it's exactly the same build released a few weeks ago. You know, the one that bricked about 1/3 to 1/2 of the phones it was applied to. Knowing O2, they'll probably just pull the update again, sulk for a few weeks, then give it another go.
I rely on my phone pretty heavily, and I'm not risking losing all of my data just because O2 can't get their crap together and release a stable ROM. With the popularity of this phone, it's surprising there's not more of an uproar about it. Would really like to know just what the hell's in this ROM that's causing so much hassle.
Will keep an eye on the O2 forum for the next couple of days, see if there's anything resembling some official feedback. This is a joke.
Just update... no problems!!!
Sent from my HTC Desire using XDA App
Please could someone explain step by step how to do the update as i have downloaded the exe. file. Much help needed.
If you're willing to risk it, the standard update procedure should run as follows.
1) Free at least 88MB of space on your phone memory.
You can check your phone memory by pressing the Menu button, going to Settings, then SD & Phone Storage. The value at the bottom (Internal phone storage) is the one you're looking for. The reason for needing such a large amount of space is to accommodate the 87.21MB update file.
If you don't have enough free space, you can start deleting applications from your phone to clear some room. You can do this by going to the Applications section of the Settings menu, then to Manage Applications. Bear in mind that you can also clear the cache / stored data of some applications without having to delete them, but that some applications cannot be deleted at all.
2) Charge your battery.
The update procedure is best done with a full battery, so make sure it's freshly charged if you don't plan to keep it plugged in for the duration.
3) Restart your phone.
Having a load of applications running in the background is never advisable when doing upgrades. The phone will have to restart during the update procedure, so the less it has to shut down, the less can go wrong.
4) Recommended: Plug your phone in to charge.
The update can take a while. If you're fully charged, it shouldn't matter, but it can't do any harm.
5) Check for updates.
This is a simple matter of pressing the Menu button, going to Settings, About Phone, System Software Updates, then hitting "Check Now". The phone will say that a new update is available. It is highly recommended that, if you're in an area that allows it, you use WiFi only. It reduces the risk of the update being split over two different data connections during the download. Once you're happy with the setting, hit OK.
6) Wait.
For a good while. Don't touch your phone unless it asks you to. Don't interrupt the update unless the world is falling apart and/or someone offers you a great deal of money to do so.
If anyone wants to correct me on any of these steps, go right ahead. But assuming that the update file isn't broken entirely, this should allow for a pretty smooth update process. Good luck.
Updated my wife's phone last night - broke all the rules - but it went off without a hitch. Battery at about 70% , didn't reboot first - though she had not installed any apps. Took about 20 mins - never touched it during that time.
Installed the updated gmail afterwards and that worked fine too.
Don't know the screen type.
Good luck everyone else, hope your updates go well - it's well worth it.
Cheers
mine went yesterday, cleared out some apps as it requested more memory and after install the phone went into the sense force close loop that happened the 1st time it was released
online support told me to take it to a o2 retail shop and they would fix it quickly in shop
o2 retail told me they offered no such service and it would be sent away for repair
ended up using this solution found on the o2 forum
1. Shut down the handset.
2. Press the "Volume down" button and (whilst keeping it pressed) press on the power button.
3. You will see some boot up text.
4. Go to the "Clear Storage" option using the "Volume down" button, then select that option by pressing the power button.
5. Press the "Volume up" button to start the process.
6. After clearing the storage, it will restart - hopefully the Sense reload issue should have resolved (mine did!).
PLEASE NOTE: SELECTING THE "CLEAR STORAGE" OPTION CLEARED OUT EVERYTHING ON MY PHONE, set up the active sync and touchdown and it all came back and most other stuff is backed up anyway
R
Did the update OTA successfully. But i noticed that i can browse on my phone unlike before when running 2.1. I took it to my service provider Etisalat for manual configuration, but all to no avail. At Etisalat, they told me that there network can't provide internet service for HTC desire running on android 2.2. I don't know if what they told me is true or not. could someone please help me out. I have an O2 branded desire and updated it to O2 froyo update.
Love my epic, but I've been having problems for a month or more now. Not sure which section this belongs in, but I'm posting it here because I'm looking for answers.
Problem 1-
Phone randomly enters "car mode", doesn't always give me the option to disable it and even when it does, if I click disable it often stays in car mode (all calls go to speakerphone, phone won't rotate). The problem has followed me through 3 ROMs and now to 100% stock, nonrooted gingerbread pushed from sprint. Is there anyway to uninstall this "feature"? I've done some searching but haven't found a solid answer. Its gotten bad enough that now, during a phone call, it will enter and leave car mode multiple times. Enabling and disabling speakerphone during the call.
Problem 2-
For awhile my phone was force closing Everything. Things like "Android Core System Process" and "Google Framework Services" along with any app I attempted to launch. It started while I was running ViperRom(most recent release) and kinda came and went. Would be ok for awhile after I restored from my initial backup. Finally became unlivable so I tried the SyndicateRom(with genocid kernel) and the problem continued to come and go. Finally got to the point that a brand new install of syndicate, after full system wipe wouldn't fix it so I returned to 100% stock and it hasn't come back yet. I imagine it could be corrupt system ram? But I couldn't find a ram tester. Id really like to go back to Syndicate, so any help would be nice.
Thank you
Sent from my SPH-D700 using XDA App
x2 with problem #2 here. wiped and reflashed srf 1.2 3 times now in the past 2 months and eventually the "Google Services Framework (process com.google.process.gapps)" force close message comes back.
WTF?
#1 iis baffling , for #2 you've probably already tried this but "fixing" permissions.usually does the trick with FC's. Good Luck
I know that Verizon has been getting some flak for the 2.3.4 update having a push notifications bug, but it seems the problem might be extending a bit further.
I'm running Android 2.3.3 on my rooted R800x from Verizon, and it too is having push notification problems.
I've had the problem off and on for the past week or two, where my wifi and data connection bars will turn from green to white, and I'll stop receiving notifications for things like facebook, twitter, and email. Every few days it will turn back on, and I'll get tons of notifications all at once.
I can't even update the OS either OTA, or with the PC Companion tool (it keeps telling me it needs to be updated, but can't find the update, even though I downloaded it fresh from the Sony site) and my bootloader isn't unlocked, so I'm not sure if flashtool would work.
I have CWM installed using X-Parts from the market, so I was working a bit with it, and found out that if I clear the cache, and Dalvik cache, that the connection bars will turn green briefly when it boots up, but after a few minutes, will go back to white.
I really love this phone, and I'd rather not have to buy a new one. I'd also like to keep my data, but if it comes down to it, I'll do a factory reset.
sethfoxen said:
I know that Verizon has been getting some flak for the 2.3.4 update having a push notifications bug, but it seems the problem might be extending a bit further.
I'm running Android 2.3.3 on my rooted R800x from Verizon, and it too is having push notification problems.
I've had the problem off and on for the past week or two, where my wifi and data connection bars will turn from green to white, and I'll stop receiving notifications for things like facebook, twitter, and email. Every few days it will turn back on, and I'll get tons of notifications all at once.
I can't even update the OS either OTA, or with the PC Companion tool (it keeps telling me it needs to be updated, but can't find the update, even though I downloaded it fresh from the Sony site) and my bootloader isn't unlocked, so I'm not sure if flashtool would work.
I have CWM installed using X-Parts from the market, so I was working a bit with it, and found out that if I clear the cache, and Dalvik cache, that the connection bars will turn green briefly when it boots up, but after a few minutes, will go back to white.
I really love this phone, and I'd rather not have to buy a new one. I'd also like to keep my data, but if it comes down to it, I'll do a factory reset.
Click to expand...
Click to collapse
White 3G/WiFi/Signal Bars indicates google services have been interrupted. If you have really bad service in your area that may be the cause. 2.3.4 broke Gtalk so all push notifications will no longer work. I would occasionally come across this problem on 2.3.3 from time to time, usually in not so good areas, I fixed it by turning air plane mode on and then off. But that is just a temporary fix. I've been using Cola rom for quiet some time now and I've yet to get white 3G/WiFi/Signal, the only time these are white is when I'm completely out of service (areas @ work) so this leads me to believe that 2.3.3 Verizon Stock ROM is flawed.
I'd suggest Cola.
Xperia Player said:
White 3G/WiFi/Signal Bars indicates google services have been interrupted. If you have really bad service in your area that may be the cause. 2.3.4 broke Gtalk so all push notifications will no longer work. I would occasionally come across this problem on 2.3.3 from time to time, usually in not so good areas, I fixed it by turning air plane mode on and then off. But that is just a temporary fix. I've been using Cola rom for quiet some time now and I've yet to get white 3G/WiFi/Signal, the only time these are white is when I'm completely out of service (areas @ work) so this leads me to believe that 2.3.3 Verizon Stock ROM is flawed.
I'd suggest Cola.
Click to expand...
Click to collapse
The problem is that I've been having this problem even at home, on wifi. Getting full bars on both wifi and data, and they're still white.
I'd LOVE to use a different rom, like Cola, or Cyanogen, but how would I do that with a locked bootloaded? Or is there some way to unlock it now? I haven't really been up to date, but the last time I searched, I found a solution that you needed to pay for to unlock it.
sethfoxen said:
The problem is that I've been having this problem even at home, on wifi. Getting full bars on both wifi and data, and they're still white.
I'd LOVE to use a different rom, like Cola, or Cyanogen, but how would I do that with a locked bootloaded? Or is there some way to unlock it now? I haven't really been up to date, but the last time I searched, I found a solution that you needed to pay for to unlock it.
Click to expand...
Click to collapse
The unlocking method just became free, don't ask me how to do it because I payed to get mine unlocked, cola does not require you to have an unlocked bootloader that is (one of the reasons) why I recommend it.
Xperia Player said:
The unlocking method just became free, don't ask me how to do it because I payed to get mine unlocked, cola does not require you to have an unlocked bootloader that is (one of the reasons) why I recommend it.
Click to expand...
Click to collapse
Ah, thank you so much, I'll look into unlocking soon.
Though, I WOULD like to point out that I think I fixed the problem.
I've been getting the "Low Storage" notification ever since this problem started, so I moved a few apps to the SD card, uninstalled some, and now it's back up, connected, and syncing my emails and stuff now.
Don't really know why storage would matter...but I guess it does.
sethfoxen said:
Ah, thank you so much, I'll look into unlocking soon.
Though, I WOULD like to point out that I think I fixed the problem.
I've been getting the "Low Storage" notification ever since this problem started, so I moved a few apps to the SD card, uninstalled some, and now it's back up, connected, and syncing my emails and stuff now.
Don't really know why storage would matter...but I guess it does.
Click to expand...
Click to collapse
I've never got that notification before...
The title pretty much says it. Anyone have any ideas?
thenewmalcolm said:
The title pretty much says it. Anyone have any ideas?
Click to expand...
Click to collapse
Mine is fine. Are you only checking inside a building?
Try this
Knock on Wood, I think I got the gps problems nipped in the butt!
I had to reset the tablet from system settings after having both updates installed, when setting up tablet (initial boot) enable all location stuff except for the new android 4.3 wifi location while off option.. Also make sure to disable backup and restore options while doing the initial install.
Now so far GPS has been working steadily ever since first initial boot, no need to reset and power up again and after trying it for an hour all gps apps back and forth its still finding signal sometimes instant sometimes 20 seconds or so but no issues like before this time...
Working like it should now! I guess a hard reset after all updates was needed to reconfigure things!
This topic is covered in thread http://forum.xda-developers.com/showthread.php?t=2382355 as well with some more detail.
While hard resetting your device after the updates does improve the GPS situation, there is still a problem that keeps coming back to haunt us. Perhaps a moderator can join these threads together?
My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.