PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Touch Pro 2 (http://forum.ppcgeeks.com/forumdisplay.php?f=97)
-   -   Fix/Workaround for 2016 Issue (http://forum.ppcgeeks.com/showthread.php?t=104248)

psycho_maniac 01-18-2010 04:41 AM

Re: Fix/Workaround for 2016 Issue
 
ziggy471. i would like to thank you for that cab on the first post. i looked in it and you already set \oem\sms\ to 0 and also the other one to 0, i figured i would have to intsall this cab, then set \oem\sms to 0 but you already did the work for me. nice way of thinking!!!

AboveTheBULL 01-18-2010 04:54 AM

Re: Fix/Workaround for 2016 Issue
 
Quote:

Originally Posted by psycho_maniac (Post 1498144)
this shows up on our touch pro2's usually meaning that its time to hard reset. im pretty sure your ****ed

Yeah man, did a little research on XDA about "rilphone.dll hangs when device booting"... and looks like the rilphone.dll included in this rilphone.cab is not signed... at least not appropriately for my stock Sprint phone. Looks like running a simple file before (a patched NK.exe) would've saved me all this headache. But now....

I'd research further, but I am still kicking myself for not saving my nephew's first steps video -- he just did it last night... So sad... :(

crwilling 01-18-2010 01:05 PM

Re: Fix/Workaround for 2016 Issue
 
Had the same problem, installed the rilphone.cab and the phone (Touch Pro running raidzero's now discontinued 6.5 rom) would not boot past the "Touch Pro" splash screen.

Hard reset. Searched xda and could not find a "patched NK.exe" file. Can you post a link or file?

Thanks.

ziggy471 01-18-2010 02:01 PM

Re: Fix/Workaround for 2016 Issue
 
Quote:

Originally Posted by psycho_maniac (Post 1498165)
ziggy471. i would like to thank you for that cab on the first post. i looked in it and you already set \oem\sms\ to 0 and also the other one to 0, i figured i would have to intsall this cab, then set \oem\sms to 0 but you already did the work for me. nice way of thinking!!!

I try not to think much, the wife says it's bad for me. However, this was one where I used my 'once a day good idea'. lol


Z

EGOvoruhk 01-18-2010 07:02 PM

Re: Fix/Workaround for 2016 Issue
 
Is there a suggested method for those running stock ROMs and your fix? I know the official HTC patch fixes messages already received, and that's what I'd like to do. I always have a 2016 message showing up in Manilla

Judging by what I read, it's not safe to uninstall the ziggy patch? Can we just install the official fix over the ziggy patch? Meaning they're both installed at the same time

AsItLies 01-19-2010 08:18 AM

Re: Fix/Workaround for 2016 Issue
 
Quote:

Originally Posted by EGOvoruhk (Post 1499678)
Is there a suggested method for those running stock ROMs and your fix? I know the official HTC patch fixes messages already received, and that's what I'd like to do. I always have a 2016 message showing up in Manilla

Judging by what I read, it's not safe to uninstall the ziggy patch? Can we just install the official fix over the ziggy patch? Meaning they're both installed at the same time

where did u read it's unsafe to uninstall ziggys patch? Sorry if it's mentioned in this thread, did read most of the msgs in the beginning because I've a palm treo pro that needs a fix too.

but I've installed (then uninstalled through programs, uninstall) ziggys patch probably 5 times... no issues at all. That patch is just registry modifications...

regards,

EGOvoruhk 01-19-2010 08:35 AM

Re: Fix/Workaround for 2016 Issue
 
I guess I misread AboveTheBULL's post. He said he uninstalled ziggy's new patch, which incorporates the DLL from HTC's official fix. I was thinking he meant the original regedit patch

I guess I'll uninstall ziggy's original regedit patch, and then install HTC's official patch and hope for the best :D

malibu_23 01-19-2010 03:01 PM

Re: Fix/Workaround for 2016 Issue
 
so for those running legacy MightyRoms (IE. 1230) are we just supposed 2 keep using the original ziggy fix?

Zap! 01-19-2010 11:18 PM

Re: Fix/Workaround for 2016 Issue
 
I'm using MightyROM Impact. I have HTC messaging disabled, and a Verizon TP2. New messages say 2016. Which cab do I install to fix that?

Scientific 01-19-2010 11:53 PM

Re: Fix/Workaround for 2016 Issue
 
Quote:

Originally Posted by Zap! (Post 1502635)
I'm using MightyROM Impact. I have HTC messaging disabled, and a Verizon TP2. New messages say 2016. Which cab do I install to fix that?

Use the Ziggy471 USCC Rilphone.cab file...


All times are GMT -4. The time now is 02:55 PM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0