Database Info

fuze video pop up issue

been flashing roms for a while now and everything was great until recently. i have this annoying video pop up problem that i cant seem to figure out if its the phone or what. what happens is randomly the tv/video out pops up and the screen turns to landscape mode. then all sound is lost. ive flashed original stock rom but the problem still happens even running stock. i cant figure out if its the phone and i need to do a warrenty exchange or if its something else. i am hard spld and security unlocked. if anybody else has this problem or had this problem and know of a solution id greatly appreciate it. i dont think its the way i flash roms. i flash with sd card thats formatted fat 32. sim card out and hard reset after first boot.

Sounds like you are describing the TVOUTPopup feature.
Usually, the TVOUTPopup only appears when the A/V Cable (extra cable) is physically connected to the device.
At first guess, I would be inclined towards a faulty USB connector.

yes it is the tv out pop feature. whats wierd is that its the new look from a different rom build. whatever rom i run (right now stock). when the screen comes up it turns landscape and has 4 colorful icons to choose from. internet,youtube,photos,and powerpoint office. once i hit the x button or hit close then it will keep repeating and keep the screen in landscape even though i havent slid out the keyboard. after multiple times closing the app it will stop doing it for a bit but then do it again few hours later.

Since you've tried different ROMs and are seeing the same behavior, I'm inclined to think it's hardware related. Assuming you have nothing connected to the device at the moment except for the SIM, examine the USB connector very closely for signs of damage.
If all looks ok, perform a hard reset and flash the Official HTC 5.05.405.1 ROM/Radio (should eliminate possibility of garbage in ROM) to the device and confirm that the behavior still occurs. If the problem persists, that would confirm it to be hardware.
HTH,

well i flashed the new att fuze rom. so far so good. no popup yet. this happened before though when i thought i fixed the problem. but after running a new rom for about 4 days it came back. if it is a hardware issue then my fuze needs to be exchanged right? thanks for all your help.

I have same issue with my FUZE (constant "Video Out" pop-up message, often switches to landscape mode, sound is off). Have you found any solution to this?
P.S. ...

[Q] Error Code: 80072EFD

I have HTC MOZART, NODO Build, unbranded in indonesia.
Now my question is, once every 2-3 weeks, I got his kind of error. Basically The internet connection is gone when this happens, and I cannot update anything, unless of course I connect to zune in my laptop and use usb for internet connection shared from the laptop.
The only way to fix this AFAIK is by restarting the device (or remove the battery, and put back in)... hold the on button until off and turn on again is suffice though....
I dont mind restarting the phone within that interval, it is just weird and I tried to google and looked it up everywhere, I have not got the right explanation. Restarting the phone WORKS every time btw.
Anybody knows what this error is?
UPDATE:
I see that many others experience this and still no answer
http://answers.microsoft.com/en-us/...83cf0108/95bb01b5-9357-e011-8dfc-68b599b31bf5
Thanx

Samsung Focus stuck on Omnia ROM

So let's start this thread by saying I was stupid.
In my desperation to upgrade my ROM I went and flashed my Focus with the new Omnia engineering rom. Stupid yes but it flashed. The reason I did it was non of the Samsung focus retail Roms would flash with the WP7 flashing tool not even the jK2 ROM. Which is suppose to be the basic 7004 ROM.
Every time I flashed it would say "This Rom does NOT match the device" or "this device is NOt retail."
So let me just state I had the "RTM Mango" flash on my device already flashed and worked. I was trying to upgrade the firmware and radio stacks. The phone aways worked and was NOT a demo device.
I have tried to flash:
1. jK2 stock Rom same error as above
2. Rom for v1.4 won't work same error as above
3. Rogers Rom on my AT&T focus same error as above.
Basically the only rom that flashed was the engineering rom for the Omnia.
Now the phone boots (with a Omnia splash screen ) I can get it to download mode I can even use the phone just none of the buttons work! I really just want to get a Samsung focus rom back on don't care if it's not Mango at the moment.
My questions:
1. Anyone got an engineering rom for the focus seems to be the only Roms that can load on my device
2. Anyone got some advise to get it back to a Samsung focus rom?
I know I shouldn't have but it's done and can't cry over spilt milk.....
I would really appreciate the help.

I'm not sure what you mean by Jk2's rom, but have you tried the 1.3 version, not rogers?
http://forum.xda-developers.com/showthread.php?t=1131022
this thread has rogers, att 1.4 and att 1.3, all for focus. Ive successfully flashed my 1.3 focus several times. Also, in this thread they talk about how flashing 1.4 is always iffy.

Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.

GoodDayToDie said:
Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.
Click to expand...
Click to collapse
Firstly thank you for the time you took to reply.
Yes the history of this device is quite a lengthy one. I did do a NODO hack to get it to NODO. I then used the internal MS bits leaked to the net to force it to Mango. I was picking up some funnies like no matter how quick or soft I pressed the back button it would go into multi tasking making the phone impossible to use.
So I looked and researched and found my firmware, bootloaders etc were way out of date. I flashed the Omnia rom onto the Focus in hope that it was the same phone but alas its to late now......
Ok so when I connect it to the PC Zune picks it up all dandy but as a new phone - Omnia not my old focus. Is there a way to trick it into thinking its my Focus?
The phone functions in the sense that it boots, I can use it just don't have any buttons to use it with. All the screen functions work perfectly.
I will download Walsh tool to un Walsh the phone and try again...
I really appreciate the help!

I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.

GoodDayToDie said:
I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.
Click to expand...
Click to collapse
Thank you for the reply!
So looks like I am screwed. I looked for the backup and nothing on my machine even tried volume shadow copy and nothing in the Windows Phone Update folder.
I might have to try create a USB JIG to force a flash onto the phone. That should work right? That should flash which ever ROM I like regardless of the checks that things like WP7 Downloader do?
I would appreciate the guidance before I go ahead and build the USB JIG.

PS _ Anyone know what files are inside the backup folder maybe I can search windows for those and find the back up folder somewhere

The updates are usually stored here:
"C:\Users\%YOUR_USER%\Local Settings\Microsoft\Windows Phone Update\"
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files

EnderPsp said:
The updates are usually stored here:
""
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files
Click to expand...
Click to collapse
THANKS so much I FOUND a backup C:\PreMangoState
This is when I did the Mango upgrade using the "MS internal leaked" files.
Going to try this.

I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968

day2die said:
I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968
Click to expand...
Click to collapse
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?

myphonerules said:
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?
Click to expand...
Click to collapse
So as soon as I plugged it in Zune found the phone and upgraded all the upgrades all the way to mango
Thank you once again. Do you know what the latest GSM firmware is?

I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?

neibl said:
I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?
Click to expand...
Click to collapse
Have you tried the retail roms (check the general forum there is a sticky with the retail roms) if you getting the error "This device does not match with the selected binary" with the flasher it could be one of two things:
1. Your device is not an engineering device and you need to use the right retail rom.
2. Which version of the WP7 Downloader tool are you using 7.05, 7.21 or 7.41?
For the retail ROM you should use 7.05
For the engineering ROM you should use 7.41.
7.41 comes with the new leaked Samsung OMNIA 7 ROM (Do a search for that rom) DO NOT FLASH (like I did ) the OMNIA ROM onto your focus it will not work.
The other question is if your phone is stuck on the "SAMSUNG" screen can you get it into DOWNLOAD mode (Turn the phone off, then hold CAM + VOL DOWN and POWER) It should then turn on and go into DOWNLOAD MODE. The WP7 tool will only see the phone is in DOWNLOAD MODE. From what you telling us with the error above you are getting into DOWNLOAD MODE but just confirm.
IMO if you can still get into DOWNLOAD MODE not all is lost.

I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.

neibl said:
I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.
Click to expand...
Click to collapse
Ok so you need to download the latest Samsung Omnia 7 ROM it will have the WP7 Downloader 4.21. Thats the only one that will flash the engineering ROM onto the device.
Zune will not pick up the phone till it completely boots so Zune wont help you in this case. You have to try and fix it using your WP7 downloader(s).
This is the link I used to get the Downloader: http://www.mobiletechworld.com/2011/10/15/update-your-samsung-omnia-7-to-the-latest-i8700xxki3-firmware-now/
Good luck!

Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.

neibl said:
Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.
Click to expand...
Click to collapse
You sure you don't have a DEMO phone? Has it ever worked on a GSM network?

No its not a demo phone, i used the phone with my AT&T SIM card for few days. Then i put in a 32mb microsd card and after 24 hours it reset into a gimped mode with only 15 mb where i couldn't do anything and had no at&t apps on it strangly also. I flashed the samsung omnia 7 ROM onto the phone and would not load past the omnia 7 load screen. Then I flashed the focus ROM (it wasn't available originally) back and it would not load past the samsung screen. By this point I really just think the phone is completely done.
Any suggestions? or think its garbage?
I'm debating buying a focus with broken screen off ebay and using the screen from this one to replace it and bam pretty much new phone.

Is there a way to get a convert a non retail focus to retail? Is there a retail ROM available for the focus that can be flashed on the non retail version?

OTA update to Andriod 2.3.5 bug

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

[Q] Motorola Atrix 2(MB865) doesnt detect mobile network

Hi,
I have a Motorola atrix 2. All of sudden it stopped detecting mobile(sim) network. It was working fine , in the morning when I woke up , when i tried to call it was showing flight moded is on and when i tried to to disable flight mode I could not do it , I did a factory reset , it didnt not resolve the issue. I thought it was sim problem , i changed the sim , that also didnt work. I tried recovery it also did not work. Sometimes it detects network but i could not make any call.Most of the times it doesnt detect network(it shows red plus sign).When i try to search for networks , it lists networks after 3-4 minutes(Vodafone , airtel , idea etc) ,But i fails to register with the network.
COuld you please suggest a solution. Is it hardware or software issue?
Thanks,
Hairsh

harish13 said:
Hi,
I have a Motorola atrix 2. All of sudden it stopped detecting mobile(sim) network. It was working fine , in the morning when I woke up , when i tried to call it was showing flight moded is on and when i tried to to disable flight mode I could not do it , I did a factory reset , it didnt not resolve the issue. I thought it was sim problem , i changed the sim , that also didnt work. I tried recovery it also did not work. Sometimes it detects network but i could not make any call.Most of the times it doesnt detect network(it shows red plus sign).When i try to search for networks , it lists networks after 3-4 minutes(Vodafone , airtel , idea etc) ,But i fails to register with the network.
COuld you please suggest a solution. Is it hardware or software issue?
Thanks,
Hairsh
Click to expand...
Click to collapse
There is a file called "radio.img" it's the software part concerned with cell network so probably if the problem came from software it (would) be that file, so please answer this Q first:
have you played and flashed some ROMs and Kernels?? is your phone rooted?

No I have not flashed or played with ROM or Kernel. What I did was my phone was attached to my laptop as USB storage and I removed directly(not safe removal , did not do safe detach). My phone is not rooted , Initially I had Gingerbread(when bought) after that I got official ICS update.

harish13 said:
No I have not flashed or played with ROM or Kernel. What I did was my phone was attached to my laptop as USB storage and I removed directly(not safe removal , did not do safe detach). My phone is not rooted , Initially I had Gingerbread(when bought) after that I got official ICS update.
Click to expand...
Click to collapse
glad to hear that your phone is clean from mods..etc
Now is your Atrix is AT&T version or asian version?

I am located in India..It should be an Asian version.

harish13 said:
I am located in India..It should be an Asian version.
Click to expand...
Click to collapse
good..so the last question, please go to settings>>about phone and tell me your firmware version (it will be like that 672.1.18.MB865.AsiaRetail.en.03)

رامز said:
good..so the last question, please go to settings>>about phone and tell me your firmware version (it will be like that 672.1.18.MB865.AsiaRetail.en.03)
Click to expand...
Click to collapse
System version : 672.1.18.MB865.AsiaRetail.en.03
Same as whatever you have mentioned.
Firmware configuration version : GAS_ASIA_EDISONICSRTSEA_P018

harish13 said:
System version : 672.1.18.MB865.AsiaRetail.en.03
Same as whatever you have mentioned.
Firmware configuration version : GAS_ASIA_EDISONICSRTSEA_P018
Click to expand...
Click to collapse
Great...now you need to fxz (it means flash the original Motorola firmware and restore it's initial state)
so here is what you need:
1) The same firmware (that's why I was asking you about system version)...download from here
http://sbf.droid-developers.org/download.php?device=17&file=351
copy it to desktop
2) Motorola Driver
http://www16.zippyshare.com/v/65297309/file.html
install it.
3) RSD Lite (it's the application used to flash)
http://www16.zippyshare.com/v/85618478/file.html
install it.
>>Now charge your battery to 100% that's very important.
>>backup your important info. from contacts to messages..etc.
>>Turn off your phone.
>>Enter Fast-boot mode by pressing (volume up+ volume down + power button) at the same time..the phone will turn on with a menu...press volume down to move the selector to (AB Fast boot) then press volume up to enter that mode.
>>you now should see "Battery OK"
>> Connect your phone to PC with the usb cable and wait to see connection has changed to "USB Connected" in phone
>>open RSD Lite and follow that video instructions:
https://www.youtube.com/watch?v=AHaEHjSzvQQ
Caution: Don't ever try to cut the flashing operation or your phone will be completely dead...so it's recommended to disable your antivirus while flashing and other services..just leave your PC alone till RSD Lite finishes the flashing.
It's not hard to fxz but please be careful with every step...... HAPPY FLASHING

My internet is slow , its taking time in downloading the firmware image. I will update you once I complete the process , thank you very much for the kind help.

Flashing was successful but for my bad luck the problem still exists. I think its an hardware issue. Do you have any idea? is it repairable? if repairable what would be the cost? Thank you very much for your support.

Good news ,it started working , i rebooted some 4-5 times after flashing firmware ,it started working now.
Thanks for your support. Thank you very much.

Sorry to say that my phone has gone mad. Now it shows network , but I could not able to make call ,if I call anybody it just gets cut and I am not able to receive any calls. Earlier it worked for some time i received 2 calls and I made 2-3 calls. Now calls are not going and not coming also.

harish13 said:
Sorry to say that my phone has gone mad. Now it shows network , but I could not able to make call ,if I call anybody it just gets cut and I am not able to receive any calls. Earlier it worked for some time i received 2 calls and I made 2-3 calls. Now calls are not going and not coming also.
Click to expand...
Click to collapse
I see that flashing original firmware doesn't help....sorry to say but it's now definitely a hardware problem
I guess that when plugging out the USB cable "specially if you unplug it slowly" some current leakage has reversed back and burned a tiny connections on the board.
actually I don't know the repair cost in service center...it depends on how much damage happened on board.
Note: maybe the battery is part of the problem...if your battery isn't genuine it may lead to that crazy behavior specially when making call or receiving calls as battery is required to raise up it's current to wake up some chips and provide more power to the antenna....if the battery was bad or damaged it can't raise it's power suddenly so system will goes crazy and may restart or freeze...etc
Make sure that your battery is genuine and not too old or that generic Chinese bad batteries as they aren't stable and may cause a current spike "extremely bad for electronics" when moving from charging mode to discharging mode and that's exactly what I think it happened to you.

Thanks. I will try to take it a repair centre , Lets see whether they can fix it. Bad part is Motorola no more provides service for Atrix 2 in India. I have to find someone who has expertise in fixing Atrix 2 problems.

harish13 said:
Thanks. I will try to take it a repair centre , Lets see whether they can fix it. Bad part is Motorola no more provides service for Atrix 2 in India. I have to find someone who has expertise in fixing Atrix 2 problems.
Click to expand...
Click to collapse
Dear harish.. did u find any repair center for atrix2...

harish13 said:
Thanks. I will try to take it a repair centre , Lets see whether they can fix it. Bad part is Motorola no more provides service for Atrix 2 in India. I have to find someone who has expertise in fixing Atrix 2 problems.
Click to expand...
Click to collapse
Hi Harish,
Before you go to the service center, try changing your SIM card.
I once had problem with my new MotoZine restarting everytime I clicked a pic. I took it to the service center, they reinstalled OS. That did not work. Then we changed the sim card, and miraculously it worked.
I know its weird, but its worth a try.