Related
Hello.
I recently got a Sony Ericsson XPERIA X1 (with Windows Mobile 6.1), and I set a password on it.
Sometimes when it would ask me for my password, the shift or fn keys wouldn't work, so I couldn't enter it. I would have to soft reset the device to be able to type in my password.
Frustrated, I decided to disable password protection entirely. I then found that after leaving the device alone for a period of time (while sleeping, for example), it would lock and ask me for a password - but since I no longer had one, I couldn't. I would have to soft reset the device to bypass the password screen.
I searched around, and found that this was a bug in Windows Mobile, and the only solution was to hard reset and never enable password protection. After a while of putting up with it, I flashed my device to use itje's Touch-IT v7, and I performed a hard reset. It was fine for a while, but now it's doing it again: it's asking me for a password when I leave it alone for a period of time, but I don't have one. I never set a password this time.
Is there any real solution to this? It's incredibly frustrating. Thank you in advance.
you mean the security password that is enforced when using exchange email? there is ap app that will enable you to turn it off, but you should read this thread (the app is listed here but you should take heed of the warning from deedee). I leave it up to you.
http://forum.xda-developers.com/showthread.php?t=358695
Try "hard reseting" it
I'm not using Exchange email, and the checkbox to disable password protection isn't greyed out (like it is in that thread). Thanks for the link anyway though, I'll have a look around the registry.
Anyone else know anything about this?
Edit: As I said in my original post, I already tried a hard reset when this problem originally appeared. I hadn't touched the password protection settings at all since my hard reset, but it's happening again.
Does nobody have a solution for this?
are you sure someone isn't messing with your phone and setting a password? I've been using windows mobile for 6 years and never had that problem.
And you said something about a bug.... can you link me to whatever you found?
Thanks for the reply, I appreciate it.
I just tried searching for that again, but unfortunately I can't find it. It was a thread with somebody saying that they have no password set, yet the device asks for one so they can only bypass the screen by soft resetting - and that's the exact problem I'm having now. There was no solution posted so I didn't bookmark it or anything.
I am the only person that has had access to my phone, so nobody has messed with it. The password setting is definitely disabled, and the HKLM\Security\Policies\Policies\00001023 registry value is set to 1 (disabled). My phone doesn't ask me for a password when I first start it (so I can get past it each time via a soft reset), it just seems to happen after 10 hours or so - I'm not exactly sure what triggers it.
Edit: I'm not sure if this is what I read before, but it seems to describe the same thing.
http://forum.xda-developers.com/showthread.php?t=291567
nuclear said:
Thats the question: is it really time for WM6?
So far i believe that the device cannot digest what we have so far of WM6. Too many non-functional things or bugs if you would like to say =_=
Device auto-locks and asks for password and if you dont have a password you cannot get into the device other than by soft reset. Asks password even for activesync! PDAViet has problem with activesync in vista as it disconnects after 5 minutes. WiFi only turns on from Comm center. Hang up's on 25MB free RAM. A lot of memory leak! 10MB to run SPB Time -_-...
Click to expand...
Click to collapse
Edit 2: Here's another one... No real solution posted.
http://social.microsoft.com/Forums/en-US/windowsmobile/thread/88834ba5-b64a-45c3-8dc4-378ffc3a40d6
seckin38 said:
I have recently purchased HTC Touch with WM6. 2 days ago, it suddenly locked. I couldn't unlock because it asks for password. Because I didn't set a password, I couldn't unlock.
Click to expand...
Click to collapse
This is really wierd, i have been using wm since 5 was on the scene and ive never come across your issue. I appreciate that your not using exchange but did you try the zeynee unlock app? It might stop the lock screen, you never know. If it doesnt work then nothing lost huh??
I didn't try it, no. I was concerned about the posts saying the application used up too much battery power, and thought checking the registry would be good enough (since nothing should be changing the value). I'll install it now and see if the problem still occurs. I don't have much hope that this will help though.
Okay, it just happened again. The application didn't help.
Ok, worth a try...
Have yoyu considered flashing to a different rom to see if this works? Is there a new stock Rom available?
Ill have to look more into this, maybe msdn has something on it.
Well, I had this problem with both my original Vodafone ROM and the custom one I'm using now. I'm reluctant to flash it again due to the hassle of reinstalling everything again.
I think it may be related to notifications. It just happened again as I got a text message, and last time it happened just before I received a Skype call. When I'm away and come back to find it locked, there tends to be a new icon in the notification area. It definitely doesn't happen every time I get a notification though...
Hi,
several persons in our company (including me), who are using WM 6.5 (cooked ROM) and connecting to company's Exchange server via Exchange active sync (e-mails are on server) reported that suddenly this message appears on the phone:
"All information on this device will be erased after the next unsuccessful password attempt"
It is not possible to enter password and do anything with phone (just reboot). Funny is, that nobody did any attempt to enter password before - phone was just lying on table and this happened.
After reboot hard reset on device is performed and also memory card was wiped.
If somebody has same experience - just write here, maybe there will be some solution in future.
And note - if this happens to you, before reboot remove your storage card - it will be erased
Info:
IPAQ 614c, ROM WWE 21215(5.01) from here:
http://forum.xda-developers.com/showthread.php?t=496283
Company policy - forced password.
This has happened to me twice now, once when i was about to go on holiday, of course wiping the 8GB's os music on my card, and again last night.
It really is a problem, at first i thought it was some malicious b*stard at work, but now i think it's an issue with the rom.
I'm going back to 6.1, can't handle this happening every other week.
Artemis P3300 running different 6.5 cooked roms.
Cheers!
There is possible solution - when such message appears, do not press anything just remove batery - we have simulated it once and phone remained unerased.
If anybody can confirm this just give me a message.
z
I can confirm workaround - it worked for several my cloeqes.
Why is this happening still remains secreat.
Maybe solution to mysterious "...unsuccessful password attempt"
I was having this issue exactly as described in the first post frequently. I may have stumbled across a solution. Turn-off Showaco's TitaniumWeather.
Go to TitaniumWeather Options;
- check "Use On/Off Time:" set "On Time" and "Off Time" to 0
- uncheck "Enable Auto Updates"
- Save/Exit, then soft reset
It's been 3 days and I haven't experienced this issue since. It could be a coincidence, but worth a try... maybe others can help verify.
Hi,
this may be a solution for you, but not for us, because nobody is using Showaco's TitaniumWeather. We (3 phones) are using SPB Weather and there is no such settng.
z
I've been experiencing this problem on almost every cooked 6.5 rom I've tried on my Raphael/Touch Pro. As far as I know the exchange server has to be configured for remote wipe and enforce hard security for this to happen. Unfortunally most of the chefs arent working for companies which are as paranoid as mine (and yours) which meens they are quite unaware of the problem.
This problem might be connected to the Activesync "85010013" error when trying to sync for the first time. The "85010013" problem has to do with some security registry settings that are wrong in most 6.5 roms used by the chefs.
Mine has happened twice in the last three days. I'm syncing with a BETA Exchange 2010 server which is pushing typical security settings (wipe threshhold, mandatory screenlock...) Both times occured after the phone was lying around locked (auto screen lock set at 15 minutes) for a while. When I attempted to unlock the first time, the PIN keypad would only take two digits then I'd get a wrong PIN message before entering the reaminig digits or even hitting enter. After 8 attempts at this, the device wiped. The second time, the phone wouldn't even let me enter in the PIN, but said it was going to wipe because I had exceeded the maximum incorrect entries. I'm starting to think the TF3D2 keypad is part of the problem when the device wakes and asks for the PIN. I've set the PIN keypad to classic as opposed to default and set the auto lockout to 24 hours. Once I finish backing up the Exchange sync settings and setting up my spare SD card, I'm going to set the lock time back to 15 minutes and see what happens.
Any solution to this problem?
Is there a solution to this problem? I am getting this about once a day. Thankfully it still allows me to enter the 10th password attempt, so I haven't experienced any data loss yet.
I am running a cooked rom with TitaniumWeather integrated and Exchange forced password. I disabled TitaniumWeather updates; it didn't have the On Time/Off Time options.
KriekV said:
I was having this issue exactly as described in the first post frequently. I may have stumbled across a solution. Turn-off Showaco's TitaniumWeather.
Go to TitaniumWeather Options;
- check "Use On/Off Time:" set "On Time" and "Off Time" to 0
- uncheck "Enable Auto Updates"
- Save/Exit, then soft reset
It's been 3 days and I haven't experienced this issue since. It could be a coincidence, but worth a try... maybe others can help verify.
Click to expand...
Click to collapse
Twice this has happened to me. One time it happened in the middle of me using the internet, the second time it was just laying on the table. I believe the issue is a 6.5 issue, since it never happened before I upgraded. I also use Microsoft Exchange. That also seems to be part of the issue. PLEASE HELP!
Not sure the best place to post this but since I'm more into development, I figure getting this information out to the community should allow us to develop a fix/patch before Sprint/HTC get around to it.
Leaked news from internal Sprint technical support regarding known issues with the EVO. Im linking to the original source of the leak for the full original information and any updates which might also be leaked.
Known issue: HTC EVO 4G - Front screen lens panel not flush near "Home" button
Known issue: HTC EVO 4G - WiFi Signal Indicator Shows Low Strength
Known issue: HTC EVO 4G - Qik Video Chat Update Available
Known issue: HTC EVO 4G - Browser could slow when using bluetooth and WiFi
Known Issues: HTC EVO 4G - Monitor doesn't support video out
Known Issues: HTC EVO 4G- Proximity sensor still active when in hands-free call
Known Issues: HTC EVO 4G - 720p Video Recording
Known Issues: HTC EVO 4G - MicroSD Card Permissions Issue
Known issue: HTC EVO 4G - Google Search Bar Widget Displaying Incorrectly
Found another.
If you have device security enabled on an Exchange server that forces devices to create a device password to sync, it will not allow the EVO to reboot after creating the password.
1. Set up ActiveSync Exchange account on EVO
2. Authenticate with Exchange server
3. Create device password as you are forced to do with the Exchange policy
4. EVO will sync and download content
5. Reboot EVO and it will not boot beyond 4G animated boot logo screen, gets stuck in a loop.
Just got off the phone with Sprint. This is a known issue in their build of 2.1 that should be fixed in 2.2
Soupskin said:
Found another.
If you have device security enabled on an Exchange server that forces devices to create a device password to sync, it will not allow the EVO to reboot after creating the password.
1. Set up ActiveSync Exchange account on EVO
2. Authenticate with Exchange server
3. Create device password as you are forced to do with the Exchange policy
4. EVO will sync and download content
5. Reboot EVO and it will not boot beyond 4G animated boot logo screen, gets stuck in a loop.
Just got off the phone with Sprint. This is a known issue in their build of 2.1 that should be fixed in 2.2
Click to expand...
Click to collapse
Ahh this is horrible! I wish i had known this b4 i got this phone, not using exchange server is not an option for me.
I'm going to try this option and see if it works:
http://www.zdnet.com/blog/cell-phones/touchdown-exchange-android-app-updated-to-version-30/1149
TripFlex said:
Ahh this is horrible! I wish i had known this b4 i got this phone, not using exchange server is not an option for me.
I'm going to try this option and see if it works:
http://www.zdnet.com/blog/cell-phones/touchdown-exchange-android-app-updated-to-version-30/1149
Click to expand...
Click to collapse
Let us all know if it works or not, please.
Maybe this will help
I think I found a solution, at least for my evo... When I first made a password, I made it just 4 digit number because I was annoyed I had to have a password everytime I turn on my screen. That's when I first couldn't reboot. I coincidentally put in a longer one the next time and didn't have any problems. Long story short, I had to ensure I had a combination of letters and numbers/symbols.
It won't let you set your password to only letters but it won't stop you from putting only numbers which what caused my evo not to boot.
My current password is 'nnn.' because it has letters and a symbol, and it's fast as hell to put in. Try something like that. I've successfully booted 4 times with exchange running in the background.
Warning: My experience with Android is about 7 hours right now. I'm afraid I won't be able to help much more than that.
Any ideas I did the FOTA update with a Exchange Server password of all numbers and cannot reboot the device - it's caught in a loop of some sort - please help
I use LockPicker to help with the forced password issue. I set up a lock pattern on my EVO, and downloaded LockPicker from the market. Set up my exchange account, and created my password. I then started lock picker, and it overrides the exchange password and uses the previously set pattern instead. I have no problems booting up the phone, and the lock pattern still gives me a certain level of security on the phone.
FatFrosty said:
I think I found a solution, at least for my evo... When I first made a password, I made it just 4 digit number because I was annoyed I had to have a password everytime I turn on my screen. That's when I first couldn't reboot. I coincidentally put in a longer one the next time and didn't have any problems. Long story short, I had to ensure I had a combination of letters and numbers/symbols.
It won't let you set your password to only letters but it won't stop you from putting only numbers which what caused my evo not to boot.
My current password is 'nnn.' because it has letters and a symbol, and it's fast as hell to put in. Try something like that. I've successfully booted 4 times with exchange running in the background.
Warning: My experience with Android is about 7 hours right now. I'm afraid I won't be able to help much more than that.
Click to expand...
Click to collapse
Sprint called me back to tell me this workaround.
I FOUND A FIX TO EVERYONE'S ISSUE
Here's what you have to do to get exchange server hooked up normally and not have a constant reboot!
Follow these steps and you will not have any problems.
1.) Hard reset your phone (VOLUME DOWN + POWER with the phone off)
You will have to go down to "CLEAR DATA", it will ask you to confirm.
2.) Let the phone reboot, everything will be erased. Setup your exchange and google account.
WHEN YOU CHOOSE A PASSWORD, USE A NUMBER AND A LETTER
3.) Go to the market place and search for "No Lock". Download it. Install it. Run it.
4.) Press the middle button to make the phone no longer require a lock.
Voila! I just did this and it works perfect!
OP you might want to put this in the first thread you posted so other people know about it without having to go through all these pages.
TripFlex said:
I FOUND A FIX TO EVERYONE'S ISSUE
Here's what you have to do to get exchange server hooked up normally and not have a constant reboot!
Follow these steps and you will not have any problems.
1.) Hard reset your phone (VOLUME DOWN + POWER with the phone off)
You will have to go down to "CLEAR DATA", it will ask you to confirm.
2.) Let the phone reboot, everything will be erased. Setup your exchange and google account.
WHEN YOU CHOOSE A PASSWORD, USE A NUMBER AND A LETTER
3.) Go to the market place and search for "No Lock". Download it. Install it. Run it.
4.) Press the middle button to make the phone no longer require a lock.
Voila! I just did this and it works perfect!
OP you might want to put this in the first thread you posted so other people know about it without having to go through all these pages.
Click to expand...
Click to collapse
Using spaces for your password also works.
I had A time Issue Today At 9:00pm my phone was still saying it was 3:42am On the time in the top bar but the lockscreen time was correct. Just rebooted it and everything was fine
Odd I didnt have any issues using Exchange Activesync on my EVO.
Badious said:
Odd I didnt have any issues using Exchange Activesync on my EVO.
Click to expand...
Click to collapse
+1 I never had any problems with mine either. my password is a cd key and it only has letters and its 5 letters. hmm.. weird.. glad i never had a problem with exchange seeing as this is my work phone! im sorry to everyone that did!
Anyone having problems, contact your IT Manager and ask them if they will add you as an exception to the Mobile Services security requirements. They won't open it up to everyone, but might make an exception or two. I do it for certain people in my organization.
Having problem with EXCHANGE "Failed to create the account Please try again later"
I am having problem with my EVO and connecting to exchagne server. It was working fine, however I have to hard reset the phone. Now when i try to setup my exchange account, it goes through and take me to the page "Finish Setup" when i choose finish setup, it just sit on processing and failed with error "failed to create the account please try again later"
It looks like the OP was just pimping that website, sdx forums. No updates have been made at all and there are many other forums and websites out there with noted issues and fixes. For example, why is there not one single xda forum post?
Thanks to everyone for posting the Exchange workarounds!
webs05 said:
It looks like the OP was just pimping that website, sdx forums. No updates have been made at all and there are many other forums and websites out there with noted issues and fixes. For example, why is there not one single xda forum post?
Thanks to everyone for posting the Exchange workarounds!
Click to expand...
Click to collapse
the title is "known issues from internal sprint support" which means these posts are based on a leak from inside sprint's technical support.
obviously there are quite a few known issues Sprint has acknowledged internally and i've just updated the list with a few more. not sure its possible to solve all of them here in this thread, but at least propagating the knowledge from sprint's internal technical support to our devs will give us greater knowledge going forward in our development work. the alternative is we could all call sprint and hope they are willing to tell us everything their internal techs acknowledge to be wrong with our phone...
if you know of any internal sprint support acknowledged issues with the EVO, please post and i will update the main post. i will look forward to your contributions of internal sprint leaked information or solutions!
if our internal sprint leak stops posting, and nobody leaks any known EVO issues from sprint here, the updates will stop.
TripFlex said:
I FOUND A FIX TO EVERYONE'S ISSUE
Here's what you have to do to get exchange server hooked up normally and not have a constant reboot!
Follow these steps and you will not have any problems.
1.) Hard reset your phone (VOLUME DOWN + POWER with the phone off)
You will have to go down to "CLEAR DATA", it will ask you to confirm.
2.) Let the phone reboot, everything will be erased. Setup your exchange and google account.
WHEN YOU CHOOSE A PASSWORD, USE A NUMBER AND A LETTER
3.) Go to the market place and search for "No Lock". Download it. Install it. Run it.
4.) Press the middle button to make the phone no longer require a lock.
Voila! I just did this and it works perfect!
OP you might want to put this in the first thread you posted so other people know about it without having to go through all these pages.
Click to expand...
Click to collapse
Seems to be a bug with No Lock, if you restart the phone and press the home key twice it will not bring up the screen that shows all 7 active screens and also when in another program if you hit the home button it will not take you back to home, the work around I found is after I reboot I have to restart the No Lock program again and then everything is back to normal.
Hi guys,
It seems that after receiving the new OTA update I ran into some issues.
My problem is that after installing the update my phone started to occasionally refuse to unlock the screen after pressing the power button.
If I connect the charger the screen unlocks but otherwise I have no option to unlock it.
I did a Factory restore (of course I lost every bit of apps I had installed - even tough I had the Backup settings activated-) and it seems that I'm seeing the same problem a few times a day.
Has anyone encountered this issue?
The phone is bought from Vodafone and original software installed.
Haven't rooted or S-off it.
Thanks
if ur phone is s-on and have same issue like s-off phones thats actually good news..seems that HTC messed up something...maybe is good advice for u to give phone to repair service if is s-on and see what thay can say about that.
I actually had that bug BEFORE the update, but not after. Instead of that, HTC Locations stopped working after the update and still is refusing to start even after factory resets and reinstall.
I have tried to contact HTC through their website to ask wheter something can be done about the issue, but the "Email Us" form doesn't seem to be sending anything after pressing submit and the "Chat with Us" form just shows blank white... I tried them on IE, FF and on my phone but they all show the same kind of behaviour.
It's really beginning to get irritating...
Clearly a software issue if it really happened after the OTA.
Wiping your Cache, Dalvik-cache partitions along with your Data (Factory Reset) should be able to refresh your phone as a "brand-new" one. That is if you can.
Stock recovery has an option to wipe Data and Cache.
If these still doesn't work, shove it to HTC's arses.,
Just kidding..
Send it for repair or maybe show it first to them.
some more bug.
-> live wallpaper sometime hang.
Starting yesterday I disabled the new feature "Trace keyboard" and since then the phone unlocked everytime.
Has anyone else kept this option activated and working ok?
2.3.5 OTA suxxxxs
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Wait for fix from HTC. They messed up something.
~Swaypovano sa Desire S BRE!~
I was finally able to get in touch with HTC regarding the Locations bug. The service agent said that he has never heard of such a problem before. His advice was that I should try the factory reset once more without the SIM card and without logging in to my Google account. I did that but the Locations still won't work. Only advice after this was to send my phone in for service... I'm really not happy with sending it in just to get an app (that was broken by their own update) to work again. I'm also pretty sure there was something wrong with the update to begin with considering all the new bugs being surfaced all the time.
This is really frustrating...
Would the people that have updated please tell wheter their Locations works perfectly? And if so, where are you from?
Bmw_m6 said:
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Click to expand...
Click to collapse
Try to disable the "Trace keyboard" feature. I did that and it seems that for the last ~18 hours I didn't encountered the unlock bug once.
Trace keyboard...
My "Trace keyboard" was off and the problem also present.
I tried to switch on, it hasn't any effect to the problem.
I hope the HTC will soon cede to this OTA full with bugs...
But as I known them, they not soo fast.....
Since the OTA update my Desire S crashes about once a day, and after it reboots it tells me it has recoverd from an error and asks me if i want to send the report to HTC. Seeing as how it reboots without any problems, and it works perfectly except the crash once a day, i suspect it has something to do with the flashing to 2.3.5.
Should i try a factory reset, or could there be another solution (seeing as how i really want to avoid a factory reset).
Oh and I have not rooted or S-OFF'ed my DS before the OTA update, so it's totally stock (as it has been since I got it)
I was able to fix the bug with Locations not starting up by changing my phone's language to English, then starting Locations, then changing the language back to Finnish again and voilá, it worked. One less problem for me.
I think that the Locations bug is limited to Nordic language versions (or even only to Finnish versions).
Hello
After update i have also the issue with the screen impossible to re-activate by power button after call is ended.
howto reproduce the issue: it happens only when screen is locked by security lock (PIN) and I receive a call. I pick up the call, screen is automatically turned off during call. After the call is finished, I'm unable to get the screen active again by pressing the power button!
Only working workaround is to attach phone to charger or connect to USB. Then the screen is activated and I can unlock it by PIN and working normally...
I need to have security lock enabled to be able to sync corporate email ( this is the security policy enforced by corporate Exchange server).
Ferro
Sent from my HTC Desire S using XDA App
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Sent from my HTC Desire S
hamedunix said:
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Click to expand...
Click to collapse
I'm sure you're right. HTC must have got a whole load of their people committed on new phones, others working on the recent security issues, so updates to our DS must be fairly low-priority. It smacks of the way that Microsoft beta-tested new OSes (perhaps still do) - Deploy many different public beta versions, don't bother actually reading the feedback but just simply measure how many complaints come in on each version. Finally, make official the version that got the fewest complaints.
I wouldn't be surprised if it goes quiet again for a week or so now.
The reply from HTC regarding the power bug:
Thank you very much for your cooperation and please be informed that we will get into this issue and we will try to determine what could cause these problems and what can be the solution. Please be patient with us because the investigation process itself it may take between 2 weeks and 4 weeks.
Have a nice day!
Disappointing
Hello,
After investigating further on my issue about "unable to resume screen by power button after call is finished" I described in my previous post I found it is most probably not related to OTA update but to HW problem...
I found my Proximity sensor is possibly dead. How the phone behaves (regarding screen on/off) during making or pick-up the phone is non standard. I also tried several android apps that are checking all sensors available on the phone and I see activity from all sensors except Proximity .
Talked also with HTC support... I'm going to sent my DS to HTC service center
Wish all getting the OTA update to enjoy it - I will certainly do so after I get my phone is repaired.
cheers
Ferro.
Pressing the power button during call or afterwards should light up the display.
At least that's what happened with the previous software version.
I'm still convinced HTC messed something in the update.
I have the exact same issue.
Has there been any work arounds how to fix this problem.
Mine's is on O2, never been rooted. Just stock.
If all fail looks like I will have to wipe phone and start again
I've got this Samsung Focus on AT&T, the other day I decided to force the newest update. I made sure I had all the correct languages and everything. The update went through and most of the phone works. (cellular connection is indeed corruption, and I know about the fix for that.)
Basically what's happening is, the Phone liveTile shows the accumulated missed calls but when I tap on it, the animation freezes then goes back to the homescreen. I can call people through the People app or by using TellMe, and people can call me. I suppose the only thing I can't do is check to see who has called me.
Is this a known issue? Is there a fix? please let me know! as for the backup...
Apparently the backup I did got corrupted in some way, so there's no going back to that (the currently existing back up for some reason is after the update, though I haven't tried using it yet).
restart it. if doesn't work. reset the phone
Yeah, I definitely tried restarting it. I even ran the Samsung tools and that didn't fix anything (including my data issue... I tap on "cellular" in the settings and it doesn't open. ****e.) To modify a classic Bill Gates quote... "I guess that's why they're not shipping 8107 yet."
I think I have an old mango back up from the fall, but oh jeez, that's a lot of backtracking.
I'll keep refreshing this thread to see if any experts have any ideas for a little bit, after a while I'll just reset the phone I guess.
The phone app thing isn't a huge deal at the moment, but no cellular data?! How am I supposed to win arguments without a cellular data connection?
read the thread more carefully, and apply the correct updates - core os update is not enough...just read...please!
Bad update, you need correct language file, i had the same problem on my Titan... Phone live tile, in settings Mobile network etc doesnt work after bad update.
I had the following in my cab sender folder:
- diff-7.10.7720.68-7.10.7740.16-armv7-retail-microsoft.pks_2cb1bfdd82133914239b8ee1a78e61e9000d124a.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0c0a.pks_97df86b81a40df06bb2b15c6739e2ee772e53bbf.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_040c.pks_2d74e8c5f6a835f1fe4c62b488c96ac2d7f01c29.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0407.pks_b50019ef50d52090d408d854c0708ddbf520706c.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0409.pks_bfd9c047a7b27c28208c8a717f8d7511fb2586f1.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.lang_0410.pks_9ecf9b052b6cc3161462e998dac8204a0f754556.cab
- diff-7.10.7740.16-7.10.8107.79-armv7-retail-microsoft.pks_c9b7f3bc5bb340ba30473b566b4557de0cf3322e.cab
Will simple reapplying work perhaps? I mean, I'm pretty sure those are the only ones I needed, I did read the thread quite a few times.
Update reapplied and now it's working!!!!
Now I just need to figure out my internet sharing issue.