Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

Javulticat 2016 Fix for Touch Pro

Install this .cab to make your Touch Pro stop thinking texts are from 2016. It will work on custom ROMs, as well as stock ROMs (though I recommend you try the official fix first if you are running a stock ROM).

This fix works the same way as the official fix. That is, it corrects the root of the problem, which is that your phone misinterprets the SMS timestamp it receives from the network. This is in contrast to Ziggy471's popular fix, which makes your phone abandon using the network timestamp, and instead use your system timestamp. The main downside to this approach is that if a text message is delayed due to no reception, your phone being off, etc., the timestamp will be the time your phone receives the text message, even though it may have been sent hours, or even days, ago.

Currently verified to work on:
Sprint Touch Pro
Alltel Touch Pro

Should work on:
Any CDMA Touch Pro
(Not likely to work on a GSM Touch Pro, though those not afraid of having to hard reset can try.)

The .cab WILL NOT fix messages that already have an incorrect 2016 timestamp. To do this:

1. Download CorrectSMSDate (CorrectSMSDate.zip, below. Made by HTC, not me) and try running it on your phone.
2. If it works, great, you're done! If it doesn't work, continue with the rest of the directions:
3. Install PIM Backup on your phone.
4. Backup your texts, making sure that "Binary Backup (faster)" is UNCHECKED.
5. Transfer the resulting file (with extension .pib) to your computer.
6. Download the Javulticat Timestamp Corrector (JTC.zip, below), extract it and run it. Requires .NET Framework 3.5
7. Select the .pib file you just created with the "Import PIB File" button, then hit "Correct".
8. When the file is corrected, the program will exit. You will see a .pib file with "_JTC" appended to the end of its name in the same folder as the original .pib file. (The original .pib file is left unaltered just in case something goes wrong.)
9. Transfer this "_JTC.pib" file to your phone.
10. Run PIM Backup and restore the "_JTC.pib" file, selecting to overwrite existing texts (should be selected by default).
11. Done!

Click "Thanks" if this helped!

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

Awesome, Been waiting 3 months for this lol

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

All you had to do was copy the rilphone.dll from the Official HTC cab to /windows on your device. Or you can create a cab like javulticat to do the same thing :D.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

Thanks!!!

If he meant what I was thinking - it is a way to fix your 2016 messages. HTC recommends a hard reset after the fix, and if you do the restore of your message, your 2016 messages will still be there, even though your new incoming messages will be 2010.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

your post is a little vague, so does this now show the time sent or the time received?

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

Yes, the Javulticat 2016 fix.cab will make all new incoming messages be 2010. You must use either CorrectSMSDate.zip or JTC.zip (instructions and download links in original post) to fix existing 2016 messages. A hard reset is not required, and it may in fact undo my fix (untested).

After using Javulticat 2016 fix.cab, your texts will be timestamped with the time that the network's servers record the text being sent. So, it will work just like it did, except your phone will now be able to correctly interpret the year being reported as 2010 instead of 2016.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

doesnt work for VZN.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

the .cab file just creates rilphone.dll in Windows. works awesome on vzw.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

maybe for the stock rom. didnt change a thing on my custom rom.

Re: Javulticat 2016 Fix for Touch Pro - Works on custom ROMs
 

Your JTC Program did not work for me. It came across an exception when correcting the .PIB file, threw an exception and froze, saying Correcting.... It was a waste of my time but the fix.cab file worked well which I guess it was really counts. Javulticat 2016 fix.cab