Re: texts from 2016???
 

There is an AllTel hotfix on the HTC site here http://www.htc.com/us/support/touch-...tel/downloads/

Re: texts from 2016???
 

No they don't. They still don't have a fix for US Cellular...

Re: texts from 2016???
 

Well, the official fix worked for me and without a hard reset. I am running the newest Sprint ROM and uninstalled Ziggy's temporary workaround, then installed the official one. I was ready with a backup in case anything happened, but so far looks like it did what it was supposed to. :)

Re: texts from 2016???
 

I saw someone else ask this already, but nobody had answered their question. I'm wondering if I should even upgrade to the new stock ROM. I too have heard bad things about the new ROM. The only good thing I heard about the new stock ROM by sprint was that it screws up the phone and they end up giving you a new TP2, lol. Since the hotfix doesn't work for the old ROM, I'm wondering what to do here. In order to install the hotfix I'd have to have the new ROM. Ugh! :(

Re: texts from 2016???
 

Yeah that would be me, I just got done flashing over. In the process of trying to do the Sprint Picture Mail Enhancment or whatever and it's not working, kind of strange, but whatever. I did send a guy an E-Mail who did it and he said
"I like the official ROM but it's only because I have no patience to experiment with the cooked ROMs and want to have official support. The ROM has its issues but I've learned to live with it. It's certainly better than the original shipped ROM from fall of 2008."
I asked him what kind of problems he has or seen, but have not got a reply.

Re: texts from 2016???
 

I flashed it, then added all the cabs I had on it before, haven't really noticed anything. But the 2016 isn't fixed, I swear I installed the cab, unless I messed up or not. About to do it again and I'll report back.
I have noticed a few things different with the new Rom, but not completely sure they're even new. I don't know what I'm saying, I'm hella tired.

Edit: So far it's good, I did a test with the phone being turned off to see if it will come in with the correct time or when the phone is turned back on and it's good, correct time. Pretty sure it's fixed. But the reason why it didn't work the first time is because I didn't put it in AirPlane Mode like it said too.
That's what I get for being a dumb*** and not fallowing/reading the directions. haha doh

Re: texts from 2016???
 

Actually I didn't put it in airplane mode either (guess I'm a "dumas," too) and yet it worked fine. Wonder why.

Re: texts from 2016???
 

I've got to get around on this if it works, this crap has been annoying

Re: texts from 2016???
 

Ok .. so I skimmed through this thread, read the links about this HUGE known bug, but I've got a couple of possibly stupid questions.

Ok ziggy's fix : (can't link) (thanks btw) and every other fix seem to change the received time to pick it up from the phone and NOT the server, fixing the problem - sort of. This doesn't fix old dates, you need to backup with PIM backup, export and edit in Excel, right ?

Now Telus FINALLY released a hotfix after every other carrier (also can't link) and it says it will fix old dates .. but won't work on my non-stock rom.

SO basically .. WTF .. are the carrier fixes doing the same thing and switching the date to the phones time, plus a little added editing of old messages ? AND if I use a custom rom am I stuck to a fix like Ziggy's that's not picking up the actual time messages were sent ? Not that that's a huge deal, but it would be nice to get actual real times.

Re: texts from 2016???
 

1) you don't need to edit the dates with the PIM backup anymore, there is an exe attached to this post that will fix the date/time of old texts for you. be sure to read the whole post, it has plenty of good information in it.

2) the patches released by carriers (or alteast sprint's, i cant vouch for the telus one) will do something with rilphone.dll or something geeky like that and actually use server time/date, but you need to be on the latest stock rom and not have the ziggy fix implemented.