yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] dsixda:
Which version of ROM is Udk Beta 5 based on?

Also I tried to cook a 2.00 ROM but it kept freezing at the splash. Hmm.. I guess I have no choice but to stick to 1.93 Rogers ;-)
[Windows Mobile Development and Hacking General] Blazeitup123:
copied from his changelog...

[+] New Official OS CE 5.2.20759 from HTC Quartz

[+] Updated XIP nk.exe from 1.97

[+] Updated Drivers from 1.97

keep trying to get that 2.0 rom working. i would be interested in testing this.
[Windows Mobile Development and Hacking General] nitroblu:
If I manually change the info in my registry myself to this:

will I get the same "no radio" problem others are having with their raphael? The only difference between what's been posted and what's in my phone's registry is the Order=dword:16 instead of 10 as posted above.
[Windows Mobile Development and Hacking General] Blazeitup123:
same as my diamond. but it works for me on 1.9x rom. am i the only one who has this working?
[Windows Mobile Development and Hacking General] dsixda:
Blazeitup, which Diamond do you have? THe AT&T one?
[Windows Mobile Development and Hacking General] Blazeitup123:
unbranded unlocked p3700 dia100

its in my sig.
[Windows Mobile Development and Hacking General] trueg:
So, I had some time to kill this afternoon and I figured I would get Rogers CNAP running on my HTC Fuze (Touch Pro/Raphael).

It took a few tries, but I do believe I have found the key.

Quite simply, the key is that rilphone.dll from the Rogers Diamond must be cooked in to your ROM of choice, it can not be changed afterwords.

Perhaps not so good news for the non-cooks out there. I currently have it running on my Fuze with stock OEM ROM 1.90.405_1. I tested with radio v1.00.25.06 (Rogers Diamond) and v1.02.25.32 (AT&T Fuze). No special registry entries are required, simply rilphone.dll from the Rogers Diamond ROM (or from the CAB dsixda posted) cooked into your ROM of choice. =)

This should work for Diamond, Raphael & Blackstone.
[Windows Mobile Development and Hacking General] nitroblu:
won't the .dll from diamond negatively affect raph or blackstone even if it is cooked into the rom? or are hte rilphone.dll files all the same throughout the 3 phones (in basic "structure")
[Windows Mobile Development and Hacking General] trueg:
All three models use the same phone hardware. The radio drivers are interchangeable once you change the nbh header.

I have not experienced any problems so far using the Rogers rilphone.dll so far.
[Windows Mobile Development and Hacking General] nitroblu:
cool, thanks :)
[Windows Mobile Development and Hacking General] Reignz:
Any luck on getting this to be able to work on a vogue? I tried using total commander and replacing the rilphone.dll file and then my radio would not function so I had to delete it.
[Windows Mobile Development and Hacking General] nitroblu:
i forgot to ask, will i still need to make the registry change after cooking in the .dll file?
[Windows Mobile Development and Hacking General] trueg:
I don't know, I don't think so. When I tested it on the Stock Touch Pro ROM, the registry settings were already the same as what dsixda listed for his Rogers Diamond.

Last night I tried out G_Clean.2.10 for the Touch Pro and by default Rogers CNAP did not work. I rebuilt it using rilphone.dll from Rogers and without changing anything else it worked.
[Windows Mobile Development and Hacking General] nitroblu:
awesome news :)
[Windows Mobile Development and Hacking General] larman:
Rom cooking?

Hi,

Could someone please offer up a link to some Rom Cooking instructions?

I would like to try 'cooking' (for the first time) to get this working with ROM 1.90.707.1 WWE and rilphone.dll that dsixda posted, as TrueG suggested.

Is it difficult to do?

btw, I bought the fuze off of SN Traders and they had put this particular ROM on themselves.
[Windows Mobile Development and Hacking General] trueg:
If you give me a few minutes, I will upload 1.90.405.1 with Rogers rilphone.dll.

Edit: OK, give this a try (note: you must have a Hard-SPL installed before attempting to upgrade the ROM)

http://www.myunspace.com/?d=3FEBDA151
[Windows Mobile Development and Hacking General] Da_G:
I believe you can acheive the same results without cooking or flashing by simply doing the following:

* Rename rilphone.dll to rilphone2.dll

* Copy rilphone2.dll to \Windows

* Change this registry key:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]

"Dll"="rilphone2.dll"

It won't work if the rogers rilphone.dll isn't signed with a certificate in your ROM's trust store, unless xip is modded for no certificate checks.
[Windows Mobile Development and Hacking General] Reignz:
I just read all 27 pages of this thread and I tried truegs cab to get the name display working on my alltel touch. I disabled my s2u2 caller id and everything and it still would only show the number. Has anybody found a way to get the name display working for a alltel touch? I have the rilphone.dll like a diamond and my registry settings (HKLM - DRIVERS - BUILTIN - RIL -

ComPort: COM6:

Dll: rilphone.dll

Index: 1

Order: 5

Prefix: RIL)
[Windows Mobile Development and Hacking General] trueg:
That might explain why it wouldn't work by cab, although I originally tried overwriting the rilphone.dll on a cooked ROM which would have been moded for no certificate checks. I didn't use a cab I simply used Rosco to overwrite the file. Once overwriten the phone radio would not start. Even after replacing the original rilphone.dll it still would not start.
[Windows Mobile Development and Hacking General] trueg:
I believe Alltel is a CDMA carrier. This thread is focused on getting a function working (CNAP) that is currently limited to Rogers Wireless which is a GSM carrier.
[Windows Mobile Development and Hacking General] s_life:
Is it possible to mod xip without flashing the new ROM? Also, have anybody tried trueg's ROM? Is this ROM unbranded english version?
[Windows Mobile Development and Hacking General] trueg:
It's the stock Touch Pro ROM (RUU_Raphael_HTC_WWE_1.90.405.1_Radio_Signed_Raphael_CRC_52.33.25.17_1.02.25.19_Ship.exe) downloaded from XDA, dumped using Raphael ROM Kitchen, then dll replaced and cooked by ROM Kitchen.
[Windows Mobile Development and Hacking General] nitroblu:
would installing and using sdkcerts be a way of allowing rilphone to work via Da_G's posted method?

EDIT: I'm gonna try Da_G's posted method, installing sdkcerts.cab first, and i'll post the results :)
[Windows Mobile Development and Hacking General] nitroblu:
I can confirm Da_G's posted method unfortuantely doesn't work. same problem occurs as posted before, the radio becomes disabled.

luckily it was easily reversible, and i have radio functioning again :)
[Windows Mobile Development and Hacking General] Reignz:
I realize my phone is the cdma version of the touch but before trueg brought it to my attention that y'all are currently trying to get gsm models to enable the Rogers name display, I renamed the rilphone.dll file to rilphone2.dll and used total commander and followed Da_G's method and my radio is still attached. I'm currently receiving calls on the rilphone2.dll instead of my original rilphone.dll file. I hope this information helps out.
[Windows Mobile Development and Hacking General] nitroblu:
i cooked it into the ROM i'm using

I can confirm caller id works on the fuze now :D
[Windows Mobile Development and Hacking General] Marshall07:
Very good news nitroblu :cool:

I'm following this thread and it is very interesting!

Marshall
[Windows Mobile Development and Hacking General] pandaboyy:
Can you show me how to cook this into a Rom that we are using?

I'm currently using NATF's V2.3 on my FUZE

and I'm with Fido.
[Windows Mobile Development and Hacking General] Da_G:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..

Pretty much leaves the only option as cooking it in, unless you are already using a ROM with a modified nk.exe in XIP to disable certificate checking.. then you can just drag and drop rilphone.dll and reboot.. but since stock ROMs are not modified in such a way, you cook it in, as all files cooked into ROM are trusted..

Unfortunatly there is no way to modify XIP without cooking either.

If a ROM is unprotected (still has it's rgu's) - download a ROM kitchen for your device.. extract the rom of your choice.. replace rilphone.dll in \OEM\OEMDrivers.. then re-assemble the ROM.. no registry manipulation needed.

For the raphael ROM kitchen, name your ROM "RUU_Signed.nbh", put it in \BaseROM

Run RaphaelKitchen.bat

select "e" for extract, then "a" for "From RUU_Signed.nbh"

let it go through its motions, when it's done replace rilphone.dll in \OEM\OEMDrivers

again in RaphaelKitchen.bat select "cf" then "b"

click "BuildOS" tab

click "Load ROM" button

navigate to RaphaelKitcken folder (has subfolders OEM, ROM, SYS, etc), press ok

click green "Go" button

when done, close the window

again the kitchen will go through some motions, when it pops up XVI32 and says "Page Pool Changer" in the command prompt window simply close xvi32

now it should prompt to flash to your device.. and you're done :)
[Windows Mobile Development and Hacking General] pandaboyy:
I've tried this with NAFT's v2.3 and it didn't work with Fido

Then tried it with NAFT's v3.0, I almost killed my phone :p

NAFT suggest me to use PPCKitchen instead of Raphael Kitchen. Will try it again.
[Windows Mobile Development and Hacking General] chgrbt:
rilphone.dll overwrite attempt reversible

I tried overwriting rilphone.dll...rebooted and the radio was disabled and wouldn't start up. So, I copied the old rilphone.dll back but the radio is still disabled.
[Windows Mobile Development and Hacking General] pandaboyy:
The rilphone.dll file has to be cooked into the ROM you're flashing to. However, it doesn't work for me. I'm with Fido

I was wondering if there is a rilphone.dll file for Fido.
[Windows Mobile Development and Hacking General] pandaboyy:
Has anyone successfully got this to work with Fido?

If so, please please show me some light... it's kinda grinde my ear when I know it work for Rogers but not on my phone.

I'm having a Fuze
[Windows Mobile Development and Hacking General] trueg:
Ya, I had the same problem while figuring out how to get it to work. I had to do a hard reset to get the phone functions to work again.
[Windows Mobile Development and Hacking General] trueg:
It works fine on my Fuze with Rogers. I can't imagine it would be any different on Fido.
[Windows Mobile Development and Hacking General] pandaboyy:
Can you repost the rilphone.dll file that work on your Fuze?

Also, did you change the background or do anything else than replacing the rilphone.dll in the ROM?
[Windows Mobile Development and Hacking General] trueg:
Well I use my own custom ROM. I tested the Rogers Diamond rilphone.dll on a stock Touch Pro ROM, stock AT&T Fuze ROM and Da_G Clean Fuze ROM. They all worked with the Rogers Diamond rilphone.dll.

Before attempting to get Rogers CNAP working I tried NATF's ROM (so I never tried the Rogers dll with this ROM) and it was fine, but no one ROM was perfect for me, I had to make my own the way I like it. One annoying thing that I have noticed with all of the custom Touch Pro/Fuze ROMs is that they don't have SD encryption removed completely, so you end up with a menc log file in the root of your SD card. Encryption doesn't work, but I hate having loose ends, so I fixed it in my own ROM. :D
[Windows Mobile Development and Hacking General] pandaboyy:
I am trying to replace the rilphone.dll file with Da_G Rome for Chefs now... if it works, I think I'll have to learn how to cook ROM for myself. If it doesn't work, I'll keep trying and I'll ask for your rilphone.dll file.

edit: I've tried it with Da_G Clean Rom and it worked. But My phone is very empty now.

I have no touchflo 3D nor any update. Is there a way to make this work with with NAFT's v3.2? I guess is time to learn how to cook
[Windows Mobile Development and Hacking General] pandaboyy:
After 33 hours straight non-sleep, and plenty of pm to Da_G and NATF, I can proudly say that we've found the perfect answer for this problem and finally we can put an end to this question "how to make Rogers/Fido Call display to work?"

I've tested this and can say that this solutions may work for any ROM. (So far I've tested with 2 of NATF's ROMs, but I need someone to test this on Kaiser) and other device as well. You don't need to test it on a Shipped ROM, but any ROM would be fine.

Solution posted here
[Windows Mobile Development and Hacking General] jentech:
Success!! I can now confirm that by cooking in the Rilphone.dll from the Rogers Diamond, I now have my Touch HD with Rogers Name Display. I just need to get my ROM tweaked and add some packages.
[Windows Mobile Development and Hacking General] pandaboyy:
Should we start to collect the bounty now?

There is more around the forum, but I'm too lazy to go around... hahaha I'm kidding, the pleasures are all mine

Enjoy it guys. It's a happy New Year :p ...

I'm so happy when I found this, I was about going to open a champagne, but I'll save it for tomorrow night

PS: Did you guys know that Rogers's Iphone (Iphone from Rogers itself) is having the same problem?
[Windows Mobile Development and Hacking General] Blazeitup123:
good work pandaboyy, i'm going to test this out in a few days, after i get more familiar with cooking.

well, actuallly it really depends on udK's upcomming rom, if it is based on 1.93 or 2.0 for my diamond. i have a cab by dsixda that works on 1.93 but i have to cook it in on 2.0 roms. your tut in the raphael section will be a big help.
[Windows Mobile Development and Hacking General] trueg:
I wouldn't recommend blindly replacing the entire OEMDrivers RGU. There are a lot of settings that are managed in this registry file. If you have a ROM that you like and you dump and replace this file there could be several changes that the cook added that you will be removing. The only section that pertains to rilphone.dll is this....

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone.dll"
"Prefix"="RIL"
"Order"=dword:10
"Index"=dword:1

These values were already set in the stock Touch Pro ROM, Da_G Clean Fuze and stock AT&T Fuze ROM (so all you need to do is replace the dll as I previously posted). If these values need to be added in order to work with NATF's Raphael ROM, I suggest you only modify this section instead of replacing the entire registry file. Since NATF based his ROM on the stock AT&T Fuze ROM I can't see why it would be necessary as replacing the file is all that is needed with a stock AT&T Fuze ROM.

Note: The DLL should work on the Diamond, Raphael & Blackstone. I don't believe it will work on any other device. This is a very important low level driver critical for phone functionality. Only devices with a compatible radio will be able to use this driver. Also if you still want to use this RGU in cooking your own ROM, it should only be used on a Raphael, it would very likely cause problems on a Diamond or Blackstone if it even worked at all.
[Windows Mobile Development and Hacking General] pandaboyy:
Damn that 10hr sleep was great... I mentioned it in my thread that it's better if you actually edit the .rgu file, because of all the tweaks. However I didn't write anything about it, because it's a complicate step.

But trust me on this, is not those registry lines... Those are the first lines that I looked at.

It's one of these (I'll actually added to my TUT thread on how to change it)

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ; for HTCmaskW1
"HTCmaskW1"=dword:1871
"HTCmaskW1BitMask"=dword:FFFFFF

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for A5/2, A5/3
"En52"=dword:1 ; A5/2
"En53"=dword:1 ; A5/3

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for remove RX Diversity
"RMRXDiv"=dword:0 ; Enable

[HKEY_LOCAL_MACHINE\Software\OEM\RIL]
"DisH"=dword:2

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableAutoPickupAtSilentMode"=dword:1 ;disable by default

add ---> [HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\69]
"Timeout"=dword:7918 ; 31 sec.

[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\82]
"Timeout"=dword:1D4C0 ; 120 sec.

[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\81]
"Timeout"=dword:1D4C0 ; 120 sec.

[HKEY_LOCAL_MACHINE\Comm\Cellular\RIL\RemoteCalltype]
"CalltypeDLL"=" PTTCalltypeCallback.dll" ; DLL containing the callback routine

[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100c"=dword:800 ;Service Loading (SL) Message Policy

[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801] ;Orange FR
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2

[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20810] ;SFR (Voda FR)
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"BattSuspendTimeoutBackup"=dword:3C
"BatteryTimeoutBackup"=dword:1E
"BattSuspendTimeoutInCall"=dword:30
"BatteryTimeoutInCall"=dword:30
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableIMSIAttachedIcon"=dword:1

I actually don't know which. My big guess would be in these:

HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801

HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801

But perhaps someone who know reg more than I do can help.

If anyone want to play with the dll file, I've noticed that all my call display end with "@" symbol if the display name end with an "a".
[Windows Mobile Development and Hacking General] pandaboyy:
I've just proved that all of our previous cooking theories about this issue are wrong. Read this

Although I found out that you don't actually need to cook in the ROM, I would say reading those theories actually helps a lot. The credits goes to everyone who has contributed to this thread :p
[Windows Mobile Development and Hacking General] trueg:
Sorry, but boldly stating that you have proved all of our previous cooking theories on this issue as wrong is a little extreme.

Now this only applies to current gen HTC devices (Diamond, Raphael & Blackstone), but everything stated so far is correct.

- Cooking the rilphone.dll into your ROM is the easiest way for cooks to add Rogers CNAP support to their ROMs.

- The radio file rilphone.dll can not be replaced in a single step like we were able to do on the ELF.

Assuming you are not a cook and want to add Rogers CNAP to an already installed ROM, Da_G was on the right track, but didn't take it quite far enough. (as pandaboyy found, you can do it in two steps)

The most effective way to accomplish this in two steps, is to make a copy of rilphone.dll (called rilphone2.dll). Change HKLM\Drivers\BuiltIn\RIL\"Dll"="rilphone.dll" to "rilphone2.dll" and soft reset. Once up and running replace rilphone.dll with the Rogers customized rilphone.dll (using Rosco FE for example) and change HKLM\Drivers\BuiltIn\RIL\"Dll"="rilphone2.dll" back to "rilphone.dll"

Using this method provides the benifit of having a copy of your original rilphone.dll (now called rilphone2.dll). This should work for custom ROMs that have certificate checks disabled as Da_G mentioned. It does not work on stock ROMs. If you dump the ROM and then rebuild it, certificate checks are removed automatically by the kitchen.

I have created two cab files that do exactly this. Rogers CNAP part 1 to copy rilphone.dll to rilphone2.dll and modify registry to point to rilphone2.dll. Once running again, run Rogers CNAP part 2 to replace rilphone.dll and change the registry back.

Your original rilphone.dll can be restored by uninstalling my cab files in reverse order (uninstall part 2 first, then part 1).

See next post for details on an additional step required to get Rogers CNAP working on ROMs that have PTT installed.

P.S. if anyone has an idea on how to combine this into one step, let me know. I've already spent too much time on this as I cook my own ROMs and do not require a way to change it after the fact.
[Windows Mobile Development and Hacking General] trueg:
On the Raphael, there is a conflict between Rogers CNAP and PTT, in particular PTTCalltypeCallback.dll. pandaboyy seemed to have stumbled upon it by accident by way of a typo. By importing the following line into your registry....

HKEY_LOCAL_MACHINE\Comm\Cellular\RIL\RemoteCalltype]
"CalltypeDLL"=" PTTCalltypeCallback.dll" ; DLL containing the callback routine

you essentially disable the driver PTTCalltypeCallback.dll because there is a space before the file name. This has the same effect of deleting the entire registry value. If you use a ROM that has PTT enabled (NATF 2.3), you need to disable this DLL before Rogers CNAP will work. Simply go into your registry and either delete the value or add a space or something to make the entry invalid.

I can make a cab to do this if someone is unable to make the change themselves.
[Windows Mobile Development and Hacking General] nitroblu:
thanks for all your work trueg :)!
[Windows Mobile Development and Hacking General] nitroblu:
doesn't work with lantis or RRE, it just disables the radio :(
[Windows Mobile Development and Hacking General] trueg:
Did the radio stop working after the 1st or 2nd cab? If it is after the 2nd cab, then it sounds like the issue Da_G described. I would guess for these ROMs you would need to cook the rilphone.dll into the ROM.
[Windows Mobile Development and Hacking General] Blazeitup123:
@dsixda and others

i just wanted to inform you that your dsixda rogers name display cab works on udK's new beta 7 rom based on diamond rom 2.03.

however still does not work on 2.00 roms. it disables the radio like others have reported.

i'm very happy about this :D
[Windows Mobile Development and Hacking General] jentech:
Seems like I'm the only one with a Touch HD on Rogers or Fido. I have been able to get Name Display by cooking rilphone.dll into a ROM (after a long and frustrating cooking process. The best I could do is basically just add rilphone.dll to a base stock ROM), unfortunately, my cooking skills lack and my ROM is uninspiring at best :rolleyes: I have tried the two cab approach with several cooked ROMs to no avail. Is there anyone cooking HD ROMs that would care to incorporate the Rogers rilphone.dll in their ROMs for those of us in the Americas that would like to have Call Display....
[Windows Mobile Development and Hacking General] Blazeitup123:
one question...

will this rogers rilphone.dll disable normal call display functionality on other worldwide carriers? can it be added to roms with no problems, or is it only for rogers? or is it a wait and see kind of thing?
[Windows Mobile Development and Hacking General] jentech:
...good question...hopefully the file just contains additional coding. I think it's a wait and see thing. It's wouldn't take a lot to test it out, if only someone would spare a bit of time...
[Windows Mobile Development and Hacking General] anandoc:
As far as I am aware, Rogers CNAP is backwards compatible with ordinary CLI. So if you did not have a Name display subscription from Rogers, you would still be able to see the calling party's phone number. This feature is implemented the same way across all the GSM carriers in the world. And hence rilgsm.dll would still allow you to see the phone numbers if you were using the phone elsewhere with a different carrier.
[Windows Mobile Development and Hacking General] pandaboyy:
seriously?

have you tried to remove your call display option to give it a test?
[Windows Mobile Development and Hacking General] anandoc:
Yes, a Rogers CSR accidentally removed name display from my account. Still the numbers would show up. It doesnt make sense that Name display on a device would not be backwards compatible with regular call display. What about the customers who do not want name display but just want regular call display?
[Windows Mobile Development and Hacking General] pandaboyy:
I'm not sure I understand... so you don't have Name Display, but you still have Call Display. That's why the number still show up, but not the name.

Just get ID display (or call display) don't get Name Display, it's cheaper.