Database Info

[Q] Will I still get updates?

I got an Omnia 7 on Virgin Mobile. Once I got it connected to Zune it updated to 7008 (pre-NoDo). Since then there have been no further updates.
I then put my Vodafone sim in it as this is my main account so I'd rather use that. The phone must be sim/network unlocked as it worked straight away with my Vodafone sim. I notice that Vodafone have released the latest update but my phone still isn't picking up any updates.
So, even though Vodafone don't currently sell the Omnia 7 (the do have a couple of other Windows 7 phones), will I still get the update or will I only get it if I put my Virgin sim back in?

You'll still be able to update even without a SIM. Microsoft is currently holding back the update for Samsung phones (again) to fix issues with updating.

day2die said:
You'll still be able to update even without a SIM. Microsoft is currently holding back the update for Samsung phones (again) to fix issues with updating.
Click to expand...
Click to collapse
Ok, that explains it. I went into the diagnostic menu to check if anything was locked but they are all set to disabled.

sparkymark75 said:
Ok, that explains it. I went into the diagnostic menu to check if anything was locked but they are all set to disabled.
Click to expand...
Click to collapse
ye.... i am waiting for the update

ICS Update = Late/Delayed Incoming Texts

1st post so Hello to everybody
Phone: HTC Sensation (not rooted)
Provider: 02
Platform: 4.0.3
HTC Sense ver: 3.6
Shoe size: 9 (UK)
Updated to ICS recently and started to notice I was receiving texts late, usually 10 mins after they were sent to me. This is intermittent and there seems no reason as to why that I can find.
Uninstalled Handcent and installed Go SMS Pro and seemed to do the trick for a few days but then it happened again.
Uninstalled Go and used stock SMS and again worked OK but I noticed it again a couple of days ago.
Rang O2 and did Sim wipe, reentered SMS centre no and still got delay. Also tested SIM in another phone and works fine, no delay. They said it is a phone fault then.
Called HTC and they advised that I had a corrupted update and that I needed to factory reset, which I have done. Unfortunately the problem still persists.
Spent the afternoon sending myself texts and some go through and some do not.
I do have poor service at home, 1-2 bars, but this was never a problem before the update.
Other than that I had the "Android is Updating, Optimising Applications" issue but his has now cleared.
Sometimes I do not receive messages at all and have to restart phone, once or more, to get messages.
HTC want me to send the phone in for repair but thought i'd see if can get any help from you lovely people first!
HELP PLEASE!!!

To update: Got a new SIM yesterday and thought/hoped it had sorted it but no joy.
Anyone got any tips? I'm wondering if it could be an app clashing with ICS?

Had the same problem, went into the Of store thinking it was a sim problem, replaced my sim card with a new one. But still had the problem. I switched from ICS rom to rom, radio to radio, but no luck. So I gave up and called HTC, they told me to do a factory reset which was just a waste of time and eventually sent it off for repairs.
Got it back, upgraded to the OTA ICS and all is well.
So to sum up, just call HTC and tell them your problem, tell that you've done a factory reset and they should schedule a repair for it.
Sent from my HTC Sensation Z710e using XDA

Well mate, I don't think it's an app clashing with ICS. If that's the case it should have worked when you installed GO SMS..
So my suggestion would be that as you are on stock ROM, the most astute option for you will be to send the phone to HTC, and they will figure out the problem for you!

Interestingly I popped Wifes T-Mobile SIM in and factory reset and factory reset and updated.
So far with her SIM in all is good, Texts going through in seconds.
Gonna keep it in there for a bit and then put mine back and see what happens.

PJBXDA said:
Interestingly I popped Wifes T-Mobile SIM in and factory reset and factory reset and updated.
So far with her SIM in all is good, Texts going through in seconds.
Gonna keep it in there for a bit and then put mine back and see what happens.
Click to expand...
Click to collapse
Why don't you try your SIM in another phone and see how it goes?

Put the O2 SIM back in and back to late messages so definitely something to do with O2.
Looks like gonna have to send it in Mon/Tues and revert back to me Wildfire which i've just unlocked. Over to the Wildfire forum to see if there are any decent ROMs available and for an idiots guide to rooting it!

Good luck!
Sent from my HTC Sensation Z710e using XDA

It seems that it is a fault at O2s end after all.
I'm fuming, spoke to them twice last week and they fobbed it off and sent me to HTC so had to do factory reset etc, taking hours and causing untold grief. Where if the she'd of done her job and looked at he fault properly the test message report she sent me would of told her that the fault was with the network. Not to mention the work i've lost out on!
Had to switch phone to 2g and messages come through fine and they've raised a fault for an engineer to check at local mast(s) and get back to me in 5 days.

can't get service on htc one s

so i have been attempting to get service to return on my one s for about 8 hours now, and cant figure it out for the life of me, i bought it on ebay a little while ago and its been sitting in a box since, i just opened it up tonight and before i did anything i put cm 9 on it which worked fine for the most part, but there was no service, and it wouldnt register with the network (tmobile usa) so i reverted to stock, but still no signal, so back to cm, nothing, reflashed it 3 times but still no luck. so i tried flashing different versions of radios to see if that would help, did stock tmous version and the most current EU version, but nothing. i just flashed miui through clockwork manager hoping for some luck but im still facing the same issue, anyone have any thoughts? could it be a possible blacklist?

It could possibly be black listed... However, that might not be the case.
On my HTC One X I had no service when an incompatible RIL was used with a new radio. RILs and radios change depending on what ROM is flashed.
Is your phone unlocked? (Can you use it on multiple networks?)

no it isn't unlocked, and so a general radio update for cm wouldnt work then? how would i go about finding which version is specific for my phone?

I would call T-mobile to see if the phone have been blacklisted.
I see a lot of these on Ebay and Craiglist getting blacklisted because peoples buy it on an installment plan, sell the phone and don't make the payment.

called up tmobile today, the phone hasnt been blacklisted from what they see, so im assuming the issue is with the radio? a lot ive people ive seen have had this issue, but no solution seems to be working for me

Try running a stock ruu from fast boot
Sent from my HTC One S using xda app-developers app

Return it and get your money back....simple.
Sent from my HTC One S using xda app-developers app

just ran stock tmous 1.84, no luck, it says there is an error with it, also tried the europe version, same result, and i would return it, but i doubt theyd take it back since its been tampered with

TheExpeditionary said:
just ran stock tmous 1.84, no luck, it says there is an error with it, also tried the europe version, same result, and i would return it, but i doubt theyd take it back since its been tampered with
Click to expand...
Click to collapse
Have you tested the phone when you bought it on ebay? Also user that sold you the phone on ebay, won't know anything about the phone, so you could just get your $ back, unless seller knows phones well.

i tested it to an extent, the phone turned on ok and such, didnt try making a call though unfortunately =( should i still just attempt to return though?

Issue with 1.25.617.4 update

I don't know if anyone else has noticed, but after I updated to the latest OTA update (1.25.617.4) I can no longer access call forwarding settings nor call waiting settings. It gives me error saying 'Network Error or sim card error' when trying to view either. I thought it was an issue with my sim cause I just used the one from my HTC 10 so went to AT&T and got a new one only to have same issue. Did a factory reset and same issue. After that I figured it could have possibly been the update, so I used the ROM exe from HTC to get back to 1.21.617.3 and can access those settings again. It was nice to get VoLTE, but I don't want to lose some settings access to get that.
If anybody has had the same issue, have you found a fix other then going back to 1.21.617.3 or staying on 1.25.617.4 and not being able to access call forwarding and call waiting?
Thanks

Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804

holz75 said:
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
Click to expand...
Click to collapse
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.

Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I used AT&T.
Click to expand...
Click to collapse
I know, but it's just instructions (from T-Mobile) on how to do it on your HTC 10.

No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.

I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.

mr_salvador said:
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
Click to expand...
Click to collapse
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.

Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Click to expand...
Click to collapse
Yusuke14 said:
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Click to expand...
Click to collapse
I don't know if I mentioned it before but I'm on AT&T, and everything is normal.

I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...

I get the same error message as well. But im on T-mobile. Really doesn't matter to me personally as i don't use settings in there.
But you're not the only one that gets the error.

turbo jjjang said:
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
Click to expand...
Click to collapse
Hadn't done anything to phone at the time, was completely stock, nothing done at all as of yet. Only thing i have done now after going back to 1.21 is unlock the bootloader and so far that's all. Going to try taking the OTA to 1.25 again and see if it wasn't just some fluke of nature.
Will update afterwards.
Edit: went back to 1.25, getting same error and can't access call forwarding or call waiting settings.

JWhetstone02 said:
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
Click to expand...
Click to collapse
I'm still on the original firmware (no rush to update as of yet) and I get the same situation when accessing those settings.

1.25 RUU is available. I'm on T-Mobile with an Unlocked boot loader and custom kernel however everything works on this end.

I have the 1.25 update and I'm on ATT, and I apparently have the issue as well. No bother, though, since I don't use call forwarding.
And, this is the sim card from my 10.

I am on AT&T and my firmware 1.25.617.4 and everything working fine here

I realize this thread is a a little old but I am having the same issue. I am on AT&T. The only tweaks I have made is to unlock the bootloader and disabled tethering guard. The problem existed on 1.25.617.4 and persists on 1.30.617.2. I thought the problem was a provisioning issue with AT&T. After multiple calls with them and a couple with HTC, I found this thread. Of course I should have stopped here first. I actually need call forwarding and calling AT&T to have them manually provision it every time I need it just won't cut it. Has anyone been able to figure this out?

"No signal" after applying official security update

Bought new Pixel 4a (model G025J) a few months ago. It worked well for a few weeks until I installed March security update. After reboot the phone stopped detecting SIM card and lost cell signal. Even emergency numbers like 911 doesn't work.
I already tried:
Change SIM card to eSIM and back to new physical.
Flash almost all official ROMs and one unofficial.
Check debugging menu *#*#4636#*#*.
Right now i bring phone to local unofficial repair service. Unfortunately they still don't have a result.
What can I do to fix it or at least diagnose the problem?
I still hope it's a software error and can be solved without replacing the phone.

Totally forgot to mention: Pixel was bought in US and I'm located in Europe

You might need to reflash your phone using google's latest images.

JohnC said:
You might need to reflash your phone using google's latest images.
Click to expand...
Click to collapse
Already tried it. Still no signal.

I'm out of ideas

get the phone replaced.
you're gonna get the same issue after any and every update you apply.
time (unpredictable) eventually returns your phone to working, though. but no software fix for it.
it's a weird problem, but you're not alone. thankfully my phone was still under warranty so I just sent it in and had it replaced. even though the replacement is a refurb, better that than never being able to confidently take an update.
I had the same exact problem.
First time, I took the andoird 11 update. I ended up leaving my phone with ubreakiFix (google's official authorized repair service) who had it for about a week and literally replaced every part and worked with google's service to deem the phone unrepairable. had an RMA for it and was ready to send it out, but gave it a shot stciking in my SIM card and it was working.
then the same thing happened again a few weeks later after applying a security update. this one returned to normal after a few hours
then last week had the same thing again with another security update. this time I quickly hopped on chat with google and sent my phone out and just received replacement yesterday

Found out that water somehow got inside the phone and kill radio chip.