Re: Fix/Workaround for 2016 Issue
 

yeah i just hard reset. i was with friends earlier and didnt want to have all my attention on my phone. why do you want all the files from the cab?

Re: Fix/Workaround for 2016 Issue
 

The issue here is that the rilphone.dll is from the OEMDRIVER package from the original Stock Sprint, so unless your ROM is using that OEMDRIVER package, it will not work. With that said, you should just be able to uninstall the cab, soft reset, and it should be back to normal. I haven't tried that myself, but have been playing around with multiple rilphone's for awhile and that's all I've had to do.

I will look into the differences today to see what they changed, and see if I can patch the rilphone from VZW MR1.


Z

Re: Fix/Workaround for 2016 Issue
 

Psycho......what Ziggy just said....lol. He beat me to it.

Re: Fix/Workaround for 2016 Issue
 

I just called HTC and asked when they were planning on releasing an update for the Verizon phones, preferably the MR1 release. I was told it is in the works, just no ETA yet.

I also tried just the rilphone, with the associated settings from the cab, everything works, except receiving of SMS and MMS, so it might just be a registry setting or two.

The only suggestion I have right now is that EVERYONE call HTC, 866-449-8358, and ask when the VZW MR1 SMS update is going to be released. Once that's done, the cooks will just add the update to their OEMDRIVERS, assuming their using the MR1 drivers like Mike. Or those of us with TP2s can just run the update and wait for the fixed ROMs to come out.



Z

Re: Fix/Workaround for 2016 Issue
 

By the way, I was you, lol. I never got a chance to reply because I was busy reconfiguring my device after a hard reset. But I had copied the dll file to my Windows directory and it killed my SMS too.

Re: Fix/Workaround for 2016 Issue
 

Just rename the file to something like rilphone.bak, soft reset, and the rilphone.dll from the original ROM build will be there.


Z

Re: Fix/Workaround for 2016 Issue
 

Running Sprint stock rom.......
Downloaded the TP2 fix from HTC for Sprint. Uninstalled Ziggys fix (thanx again for making the interim bearable), did a SOFT reset and followed HTC's direction. Works perfectly so far.

3. Place the Touch Pro2 in Airplane Mode by navigating to Start > Comm Manager and tapping on Airplane Mode

How to install the hotfix on the device

1. On the device, tap Start > File Explorer
2. Locate the hotfix file and single tap on it to install
3. Follow the onscreen prompts to install the hotfix
4. Reboot the device per on-screen instructions to finalize installation
5. After the device reboots, take the device out of Airplane Mode by navigating to Start > Comm Manager and tapping on Airplane Mode

Sent test message from Sprint site online sms

Re: Fix/Workaround for 2016 Issue
 

Interestingly enough, the techs in the Sprint stores don't have the .cab internally yet. I had to pop an e-mail out to get the link from HTC to everyone in my area. Love their communication. From what I've seen so far, the fix works great on the stock ROM. If it doesn't, I'd blame weird WinMo errors that crop up every now and then.

I'm not entirely sure how this stuff works, but the forum post I saw said that the issue came from a hex field being written to as a decimal so that 0x09 was interpreted as 2009 but 0x10 came to 2016. I'll check for more info from there tomorrow but that was the gist of it. Don't know if that helps at all, but I'd love to see the fix figured out to be put into custom ROMs.

*Note: If this was already in the past 30 pages, my apologies... I didn't have a burning desire to read through all 30 pages of bitching. ^_^

Re: Fix/Workaround for 2016 Issue
 

Check the first page for an update. I extracted the rilphone from the USCC update, and it does work on War 12-30, and should on other ROMs based on USCC OEMDrivers.



Z

Re: Fix/Workaround for 2016 Issue
 

I don't mean to hijack this thread but you are the group that can best answer this time stamp question. I have loaded the US Cellular hotfix for the 2016 issue on my USCC Touch Pro 2 (Win Mobile 6.5) and continue to have an issue that has been a problem from the beginning. I live in the Eastern time zone, yet still in USCC's Chicago switching area. Every text message I receive is stamped on my phone in Central (Chicago) time, or one hour behind my time. The texts I send appear on my phone with the correct time stamp. This, they say is due to the fact that USCC's switch is located in the Central time zone. Is there a registry edit or some other fix that I can apply to rectify this? Thank you all for your help.