[Touch Pro2, Tilt 2 Themes and Apps] chicago_steve:
Success story

Well, it works and worked first go too, so that was quite a surprise after the issues some people have encountered. No need for multiple installs / uninstalls either.

Just thought I’d take a moment to add some feedback. I did the BlackBerry Connect install a week back and should have done a better job of documenting the steps at the time. I hope some find this helpful.

Here’s my setup:

Carrier:

T-Mobile 3G, Chicago marketplace.

Phone:

HTC Touch Pro2 1700/2100 version for US T-Mobile, no mods or other changes – phone is mostly in an “out of the box” state

Service:

Existing, working BlackBerry Enterprise account (I was previously using this with a Nokia E70)

Note:

You must have a BlackBerry Enterprise account enabled; just BlackBerry Internet Service (BIS) will not be adequate

Install Process and Notes:

I had initially downloaded and installed the 106 version of the BlackBerry client without the SetModelID patch and true to form, I was unable to connect to the BlackBerry Service. It basically sits there dumb and unhappy.

With my old Nokia E70, which ran Symbian 60, use of the BlackBerry Desktop Connect Software was essential to provision the phone. For those unfamiliar, Provisioning is the act of the BlackBerry network sending you the required Service Books – I’m a little unclear whether these actually come from BlackBerry, or the corporation to which you connect. Either way, this is an essential part of the Enterprise Activation process, as we shall see later.

I did initially install bb_desktop_4.0.0.22 version of the Desktop Connect software prior to installing c0rnholio’s patch and it successfully gave me back a PIN. At this point I was wondering whether this was going to work without the patch. I then called my company’s IS department and give them the new PIN and had them reset my BB account. Not sure if they needed the new PIN, but I suspect resetting the account is important. At this point an interesting event occurs – a good deal of my contacts and my calendar are miraculously present in my TP2, even though the BB Client on the TP2 is showing no service. I don’t know if this happened over the air, or through the USB cable connected between my laptop and the TP2. Either way, with the TP2, this software is _not_ necessary as all the Provisioning is done over the air – very nice. In fact, when I tried to run this software for a second time after installing c0rnholio’s patch, it would not give me a pin, as it had first time. Long paragraph short, don’t bother with bb_desktop_4.0.0.22; it is not required.

With all the messing about over, back to the plot. The next step was to uninstall the BlackBerry Connect software from the TP2, which is easy to do. Then:

Copy SetModelID.exe into the \windows folder of the TP2

Using your favorite registry editor – I used CeRegEditor – browse to HKEY_LOCAL_MACHINE (aka HKLM) and then the init folder.

Create an entry called Launch130 (may need a higher number if this is already used) and set the Value Data to SetModelID.exe. Be aware of case sensitivity when you make this change.

Soft reboot the TP2

Install the 106 version of the BB Connect client

After everything is correctly installed, there are few tasks to complete from within the BB Client:

Launch the BlackBerry application (Start -> Settings -> System -> BlackBerry) and choose the About tab. It should show HTC-Raphael as the Device Type. If not, go back and fix what you got wrong with the installation of the SetModelID

Choose the Utility tab. Click Register Now to register this device with the network.

Finally, choose the Activation tab. Enter your corporate e-mail address and the Blackberry password given to you by your IS department. Note, this may not be the same as your regular corporate e-mail password.

Check the Status tab shows Connected.

The Identity tab should show a populated PIN, IMEI and IP address.

Full Activation and synching over the air took about 15 minutes.

There is some additional commentary by c0rnholio on problems when the device is soft reset and the SetModelID patch not being fast enough to occur before the BB software goes running. The supposed result of this is having to then manually terminate the three BB services running on the TP2. I have had none of these issues and can soft reset the device with no problem.

I have been running my corporate e-mail, calendar and contacts through the TP2 and the BB Client for the last week with no issues. None. Both the phone and the client have been rock solid.

Cheers,

Steve