Touch Pro 2 SMS 2016 Issue Official Fix!!![Download Here]

[ziggy471]

Originally Posted by nerdstrap

you can also use dotfred's backup tool to extract the sms, modify them back to 2010, then re-add back to your device.

there was a post from ziggy on this site detailing how to do this!

http://forum.ppcgeeks.com/showthread.php?t=104248


Z

[rlind50688]

Asking a question that I haven't seen asked or answered in this thread yet. Is this a "fix" or another "work-around"? Does this official HTC fix use the time the txt was received by the network, or does this fix now use the time the txt is received by the phone?

Reason I'm asking, is I need the time the txt was sent by the sender, not when my phone receives it. I often am in buildings where I don't get a signal for periods of time, and need the time the txt was sent for trouble ticket handling in my business.

[ziggy471]

Originally Posted by rlind50688

Asking a question that I haven't seen asked or answered in this thread yet. Is this a "fix" or another "work-around"? Does this official HTC fix use the time the txt was received by the network, or does this fix now use the time the txt is received by the phone?

Reason I'm asking, is I need the time the txt was sent by the sender, not when my phone receives it. I often am in buildings where I don't get a signal for periods of time, and need the time the txt was sent for trouble ticket handling in my business.

As Mike already said on the first page, it replaces rilphone.dll, so yes, it's official. It fixes the conversion error from BCD in the carrier supplied date/time last modified, when the message was sent. The reg edit I posted just changed which date/time it used, this one actually fixes the issue.


Z

[treadwayj]

What can I use to replace the rilphone.dll? I have tried using explorer on my PC with it hooked up via USB and I have also tried Total Commander and both ways it comes back with an Access Denied error. Do i need to use the reg edit that is included in Mike's rar file first?

I have tried putting it in Airplane Mode, as well as soft resetting so that it will come up in Airplane Mode. Any suggestions would be greatly appreciated.

I am on MM War 12/30/09 if that makes a difference

Thanks

[ziggy471]

Originally Posted by treadwayj

What can I use to replace the rilphone.dll? I have tried using explorer on my PC with it hooked up via USB and I have also tried Total Commander and both ways it comes back with an Access Denied error. Do i need to use the reg edit that is included in Mike's rar file first?

I have tried putting it in Airplane Mode, as well as soft resetting so that it will come up in Airplane Mode. Any suggestions would be greatly appreciated.

I am on MM War 12/30/09 if that makes a difference

Thanks

Don't bother with War, it won't work, tried that early this morning. You won't be able to receive SMS or MMS with that rilphone installed. We're looking into why right now. Mike is using the USC OEMDrivers in war, and that's probably the issue.


Z

[chevy454]

Well crapola...I'm getting the "incorrect device/version" error when I try to install the official patch? USCC Tp2, stock as delivered WM6.5/2.1man, with just a couple visual tweaks (crystal clock, clear slider, no banners)...and I did *not* install the workaround from Ziggy...?? Any ideas what the problem is???

{Incorrect Version

Incorrect device or version or previously installed. This hotfix will only support HTC Touch Pro 2 ver1.21.651.3 . 0x20}

[BlackDynamite]

Originally Posted by ziggy471

Don't bother with War, it won't work, tried that early this morning. You won't be able to receive SMS or MMS with that rilphone installed. We're looking into why right now. Mike is using the USC OEMDrivers in war, and that's probably the issue.


Z

Yeah I'm pretty sure every cooked ROM has the same result when copying that dll to the Windows directory. It killed my messaging when I tried it on indagroove's Titanium, and I haven't seen anyone post any success stories with any cooked ROMs yet.

Of course I'm on Sprint, so I don't know if it will be different for the Verizon users...

[ziggy471]

Originally Posted by chevy454

Well crapola...I'm getting the "incorrect device/version" error when I try to install the official patch? USCC Tp2, stock as delivered WM6.5/2.1man, with just a couple visual tweaks (crystal clock, clear slider, no banners)...and I did *not* install the workaround from Ziggy...?? Any ideas what the problem is???

{Incorrect Version

Incorrect device or version or previously installed. This hotfix will only support HTC Touch Pro 2 ver1.21.651.3 . 0x20}

Originally Posted by SaltyDawg

Yeah I'm pretty sure every cooked ROM has the same result when copying that dll to the Windows directory. It killed my messaging when I tried it on indagroove's Titanium, and I haven't seen anyone post any success stories with any cooked ROMs yet.

Of course I'm on Sprint, so I don't know if it will be different for the Verizon users...

Since most of the cooked ROMs are probably using the USC OEMDrivers or the newer VZW MR1, it does not work. The patched version for Sprint is from 6.1 21052, and the USC is using 6.5 21864. According to HTC this morning, they will be releasing a fix for ALL phones, to include the Verizon MR1, 6.5, and USC. They just haven't got them done/posted yet.


Z

[treadwayj]

Originally Posted by ziggy471

Don't bother with War, it won't work, tried that early this morning. You won't be able to receive SMS or MMS with that rilphone installed. We're looking into why right now. Mike is using the USC OEMDrivers in war, and that's probably the issue.


Z

Thanks, at least the CorrectSMSDate exe works so I can at least get them fixed when they come in.

[dumpringz]

Wirelessly posted (HTC Touch Pro 2 (Sprint): Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

fix works just as described. gladly i didnt have to hard reset only uninstalled ziggy workaround which after a week of seeing 2016 with NO TIMESTAMP i finally even installed .. also as others have stated the fix indeed shows time of when actual text was recieved through network .. least on my phone