[8525, TyTN, MDA Vario II, JasJam ROM Development] uncle_BBcracker:
Featuring the Master of WM6 ROMs, Mr. Schaps himself, I decided to publish this little recipe, how to patch the Schaps 3.5x ROMS to make them suitable for BB Connect.

WARNINGs:

You do, what you do at your own risk!

I will not maintain or Babysit this thread. It works for me, it may not for others!

I will not upload any patched ROMS or maintain these, because I have no time.

I provide this recipe to others, who need like me a BBconnect for job on a WM6 ROM and since Schaps ROMS seems to become a standard, here it is:

This is a recipe for users, who had BBconnect running before and have some experience. If you never run BBconnect on a WM device before, this is probably not for you to start here! Get it to work on a true Blackberry, then move to WM 5 device with a proven config; after that you might try this one.

BBconnect checks the OS version and the Device ID. In addition you need to have a Blackberry subscription, and your Provider must support BBc and your SIM card must be BB enabled. It works with a wide range of Radio Stacks. The radio stack is also NOT relevant for the BB OS check algorithm.

This patch is ONLY to 'correct' the OS version checking; it will not help for other incompatibilities!

My patch works for the HERMES 100.

I tested on Schaps 3.57a and 3.54b

I used BBconnect 4.0.0.67

To do the patch, you need:

Schaps ROM

an Archiver like WinRar or Powerarchive (tm)

A HexEditor

A Registry Editor

a cab file BBconnect 4.0.0.67

Active Synch BB connect Desktop SW 4.0.0.17

You don't need a Rom Kitchen environment; it's just adding a little bit of cracked Pepper to the perfect dishes the cook has cooked in the kitchen.

How to:

Open Schaps ROM with the Archiver (do not double click); Schaps ROM is a self extracting and running archive.

You will find 2 files in it:

Ruu_Signed.nbh

Ruuwrapper.exe

Extract Ruu_signed.nbh (leave the archiver open)

run HexEdit

Open Ruu_Signed in the HexEditor

Search the following Hex String:

30 40 2D E9 59 3E A0 E3 0D 30 83 E3 45 2F A0 E3 05 10 A0 E3 02

You should find it EXACTLY 2 times in the .nbh file. If you don't find it, or only once or more than 2 times, you can abort the process here, because something is wrong! On the other hand, if you find it also exactly 2 times in the 3.6 beta ROM, you can almost be sure that it will work as well there, but I have not tested it.

If you found it 2 times, search again from the top.

At the first occurence change the following bytes in BOLD:

30 40 2D E9 59 3E A0 E3 0D 30 83 E3 45 2F A0 E3 05 10 A0 E3 02

as following

45 change to C3

2F change to 30

02 change to 01

Search for the 2nd occurence and change the same bytes to the same values as above.

save (overwrite) Ruu_signed.nbh and quit Hexedit

Now replace the Ruu_signed.nbh file in the archive with the modified Ruu_signed.nbh in your directory. It may be good to check the time stamps of the files to be really sure that you will have the modified file in the archive.

Save (overwrite) Schaps ROM.exe and leave the archiver.

You can now flash your device, by double clicking on the modified Schaps Rom.exe. Follow the instructions there. I have encountered an error message at the end of the flash process, but this has no effect, the device will boot properly.

After you have configured your Hermes, check on the Start|settigns|system|about screen the version.

You should see: 5.1.195...

If you dont see that, or if you see 5.2.... you did something wrong in the patch process. In that case, flash again with a ROM of your choice and forget BBconnect.

Load and execute the Registry editor onto your device.

Modify the HKLM/system/Version key

from .0.3.2 to .2.3.0 (don't forget the leading .)

Go again to the Start|settings|system|about screen.

You should see now: CE OS 5.1.195(build 17944.2.3.0)

If you don't, abort the process and re-flash with a ROM of your choice.

If you see EXACTLY this, you have successfully patched the OS to run w/ BBconnect 4.0.0.67

Load the BBC.cab to your device and install.

You'll find 2 new icons

1) in Start|settings|system BlackBerry

2) Start|settings|personal BlackBerry-Security

Run Start|settings|system BlackBerry and follw the instructions (prepare for 1st use). When it asks you, which info to synchronise from PIM, leave all boxes UNchecked. Just let's try to get mail working first; you can later change to synch your cal, contacts etc.

After reset, you'll find the BB symbol :x in the tray. After a few seconds it will change to : and start to try to connect via the radio. Something should move in the Start screen top line above the Radio Strength icon.

After a while you should see the BB icon as :: Click on the symbol and go to the Identity tab. You should see there a PIN (starting amongst others w/ 6...) and more over a valid IP adress. This adress is given to you from the provider network. If you don't have a PIN or IP address, it won't work for you.

If you have a PIN and an IP address, there is hope, but no confirmation, yet.

Make sure, you have MS ActiveSynch 4.5 properly partnered. UNcheck under Options all synch items, like mail, calendar etc.

Disconnect the Device from the Desktop after synchronisation completed.

Install the BBconnect Desktop Software and connect the device, when told so.

Follow the procedure or configuration. Eventually you will see a pop up window saying "Sending provisioning data to Handheld". After that, "Handheld configured successfully". Give it time!

Disconnect the device and it should now connect over the air interface, as following:

The device will lock and prompt you for a new passwd. (The BB security passwd). After that

you'll find the BB symbol :x in the tray. After a few seconds it will change to : and start to try to connect via the radio. Something should move in the Start screen top line above the Radio Strength icon.

After a while you should see the BB icon as :: Click on the symbol and go to the Identity tab. You should see there a PIN (starting amongst others w/ 6...) and more over a valid IP adress.

Go to the e-mail tab and you should see your e-mail adress as provisioned by the Desktop Program.

The typical behavior, if your connection is REJECTED is as follwing:

Click on the BBc symbol in the tray; open the Status Tab.

Stop the service

start the service again.

you'll find the BB symbol :! in the tray. After a few seconds it will change to : and start to try to connect via the radio. Something should move in the Start screen top line above the Radio Strength icon. The status line says:

Network available

Datec Tunnel Available (a fraction of a second only)

and then, instead of going to 'connected' it goes to Not Connected AND THE IDENTITY TAB SHOWS NO IP ADDRESS

In that case, your connection is refused and you can forget about it.

If connected, you are done, read the BBc manual and configure your device as needed.

BBconnect is a complex program, which needs a lot of CPU power and server/network communication. BE PATIENT! In case, wait a few seconds longer, rather than confusing everything!

Good Luck