Database Info

"Invalid or missing SIM card" - did I cause this?

I upgraded to a Prophet from a Magician.
When I first got the phone, everything worked fine. I updated to the latest Jamin rom and installed all my apps, didn't notice a problem.
It was only after I started to install custom roms did problems start to occur.
Firstly, as mentioned, registry changes wouldn't stick after a soft reset. SMS messages would mark themselves as unread on a soft reset. Soon after, my phone intermittently stopped reading sims. Now it doesn't read them at all.
I've chalked this up to a coincidental hardware fault, but I just want to check that this isn't some standard issue problem to do with upgrading that I've missed, because when I get my phone fixed, I'm just going to upgrade the rom again and I don't want to make the same mistake again, if I made one.

I have never seen a sim fail after a rom upgrade.....
JD

big problem PLEASE HELP

my phone can no longer make or recieve calls, cant get to the phonce section of the phone no matter what, says i have no connection, yet can go online, has 3g icon, and can send and recive text. can anyone solve because the silly geese at AT&T said the only way to fix is to exhange and said thats not fixing it bub! so can anyone help

which ROM?

Try hard reset.

Are you running WM6.1 without a compatible radio?

no rom
i have every thing factory, all i did was tried to hard spl and i kept getting the white screen so i was unable to even get a new rom. i went to sleep woke up and boom no calls or phone feature, but everything else. so any clues

i had this problem too,when 3g icon appear on bar,i can't make any phone calls,receive calls,and data connection.but when the G icon appear,i can make phone...etc.i tried all solutions change the radio and roms,but still no luck.
i send my device to the warranty returns,and they changed it to a new one
i think that it is the tytn II problem.
my friend have a PDA store,and 3 customers complaining about this...
so send back your device for warranty
cheers

Hard reset first of all then let us know if it still doesn't work.

How do you make sure there's no evidence that you ever rooted your G1?

So earlier today I decided I wanted to take my phone off root because it had become really buggy so I followed these instructions from another thread:
"download this http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip unzip it and load it to the root of your sd card and reboot the phone holding down the camera and power key then follow the instructions in screen then reboot and wait for the update. how many more times must i type this? can you people not see the search button."
SOURCE: http://forum.xda-developers.com/showthread.php?t=478856&highlight=original+firmware
After doing this, my phone was working fine. Everything worked. For some reason like 2 hours later, my threaded txt messages started showing up in the wrong order. I called T-Mo and they had no solution so they're going to sen me a new one. I wanna make sure there is no evidence on the phone that it was ever rooted. How do I make sure? Thank you so much!

just make sure you updated to original firmware after you changed your fastboot images... that is... if you changed the fastboot images... then you are good to go.

I never messed with fast boot and all that, after I rooted it, I updated JF1.41 with auto rotate and multi touch. thats it. when I went to original firmware, literally I did exatly what he said with the DREAIMG.nbh file, and rebooted. ( Copied the DREAIMG.nbh file to root of SD, restarted with camera+power, ran the update, rebooted) Was there a step I missed?
The problem now is, I dont wanna change much at this point bc if it fixes the threaded txt issue, then theyll prob charge me for the new phone if the txt problem is fixed.

find the SPL thread(sticky) and make sure that your bootloader screen looks like the stock one and you should be fine as well, RC29 already wipes everything else

my threaded txt messages were going in a crazy order last night. but i assumed it was cuz of daylight savings time lol. my g1 to g1 messages would show up in correct order. but everyone else' messages were in screwy order.

yeah its because of DST. T-mobile changed the clocks to early lol. Either that or the g1 screwed something up.

we will see what happens
I posted this in another thread so ill be brief ...
due to a hardware error I returned a white g1 which I had rooted and tricked out with JF's RC33 a theme and the dev BL... I was feeling lazy so I just wiped it and made sure it was back to the stock theme and sent it off with a flat battery, I dont think they will scrutinize them much, we will see, most of the time you play stoopid say you took it to a store and they did some stuff, whatever, PROVE IT, pry my replacement from my cold dead hand.
ill post if I get some response to my tricked out g1 returned due to a bad bt radio
bhang

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

"Unable to send message after multiple attempts" MMS error with OrDroid

First the details:
Sensation XE
OrDroid 8.6.
S-on
HTCdev unlocked
4ext recovery
Smartflash enabled
and formatted all partitions except SD Card before flashing
_____
The problem is that none of the MMS messages will go through if containing a photo that was taken with the flashed ROM. However, if I try to send a photo that was taken prior to OrDroid ROM, it goes through without a problem.
Doesn't matter if I send it directly out of the message app or going first to Gallery and share it. After about a minute I get the error in the notifications saying "Unable to send message after multiple attempts" and "Generic network failure" or "Service denied" written below.
The MMS settings and Mobile Data are all fine, considering it works with old images. Plus I can't notice any difference in the images' details between the new ones and the ones taken prior to flashing OrDroid.
One more thing, I also cannot receive MMS messages. I get a message with a download button and nothing happens if I click it.
Any help would be greatly appreciated. Oh, and I'm not looking for a ROM changing solution.
Edit: Ok, after about 30 new attempts of sending out photos, I see the problem isn't with newly taken images, but it's completely random. Now, about 1 in 10 attempts goes through. By the way, the signal bar is full. I really don't get it...

No one has any ideas? That's rather sad.

Hi I'm running Ordroid 8.6.5 and I'm able to take pictures and send them immediately, new pictures. I just tested it. It works perfectly for me. Perhaps do a full wipe and re flash the newest rom. I can say it's NOT ordroid because its working perfectly for me.maybe the download got corrupted somehow. I would definitely do a full wipe, download a NEW download to the computer then place NEW download to root of SD card and flash. Don't use old download as it is likely corrupted in some way. See if this solves the issue. Please do full wipe before flashing NEW download. This should do the trick. I'm hopeful this will fix the issue. Let me know. Because we know its NOT a issue with ORDROID, so give that a try . Good luck! Hope this helps out!
Also check and make sure settings are correct, if so do the new download of ordroid, see if it fixes the issue.
Sent from my Sensation 4G using xda premium

Thanks for replying, realsis.
I did a full wipe again and reflashed. I didn't bother downloading the file again, because the md5 matches and the file's fine. The MMS still doesn't work though.

So sorry, I can't think of another possible fix. Perhaps someone else has one ? Very strange because I'm using the same rom as you are and I can use mine without issues. I really hope you find a fix soon. Take care.
Sent from my Sensation 4G using xda premium

Thanks realsis.
Anyway, apparently ROM really isn't the issue. I've just flashed InsertCoin Evolution v1.91 and the MMS still won't go through.
I truly am baffled.

Check the apn settingd for your carrier...sometimes they get goofy ...ive had this happen before and I had the wrong settings..even though I never touched them...i googled for the settings and fixed it instantly

I've also tried that. Manually typed in proxy and port, and sadly it did not do the trick. Almost none of the MMS will go through.

I would call your carrier and see if it's goofed at their end, maybe they can help.one time I had to call for something and even though I'm using custom rom (they don't know this) they were able to fix my issue. Cannot hurt to try?
Sent from my HTC Sensation 4G using xda premium

I called them just now, and we went over the APN settings again, and she told me to change the authentication type to PAP (was 'none' before). Of course that didn't do the trick, and we parted without resolving the issue. She told me it should work and that was basically it.
It's getting really annoying because I know it really SHOULD work! Poop.

I've been having same problem. I'm using sensation running energy ics ROM. The work around i use is i have to use quickpics (app) and crop the image before sending... Almost as if Android isn't resizing the image correctly when "converting" to mms. This almost always works.

Thanks billybag, but that didn't do the trick.
The thing is, the problem is the same with the incoming MMS. It says download and after I click it, it says downloading for a minute or two and just pops back to download.
I tried really cropping the image with Quickpic (to about a pixle or two ) and it still didn't send it.