yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] hidefguy:
For those of you that have the Cingular 8525 and still cant get the blackberry connect to work, vodafone released a new blackberry client and desktop manager,

under VPA Compact III

Blackberry Client 2.1.2.54

Desktop Manager 2.1.2.21

you can find the link here http://support.vodafone.de/index_l3_2z.html

I just bought this phone a week ago and I read on another forum site that it might have to do with a range of imei number range? I was also on a company BES with the the blackberry tethered unlimited data plan. anyways, im so happy that it's finally working.

my phone:

Cingular 8525

XDA Live .20

OS 5.1.195 build 17217.2.3.0

thanks again C0rnholio
[Windows Mobile Development and Hacking General] beginner:
new universal rom Jwrightmcps Crossbow ROM Update 2.02.00 WWE

Hi C0rnholio: did you have time to check what changes to be performed to have bb running in this version?

thanks.
[Windows Mobile Development and Hacking General] KarmaNP:
Beginner:

Use the same string that you were using for .08 rom. Here it is (originally from c0rnholio's post)

4F 3F A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 02

4. Change it to:

C3 30 A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 01
[Windows Mobile Development and Hacking General] moisha:
cant get the blackberry connect to work

But one still have to reflash with modified .dll

Correct ?
[Windows Mobile Development and Hacking General] hidefguy:
Yes. You will still have to make the hex changes and reflash to your phone.
[Windows Mobile Development and Hacking General] KarmaNP:
Hex String for new Wizard Rom by Faria

C0rnholio,

Faria has come up with a new WM6 ROM for wizard and the hex value for other rom doesn't match up with the ones that we have used before. Since looking for the APN string is too much over my head (I tried but it's just beyond me), I was wondering if you could look into that for us. It will be a great favor to fellow wizard users.

Thanks in advance
[Windows Mobile Development and Hacking General] c0rnholio:
Lokk at this post: http://xdaforums.com/showpost.php?p=1150039&postcount=64

Search for 5.2.318 in this post and you get what you want :D

This new ROM you are talking about has version 5.2.318. The Universal WM6 ROMs have the same version. So if you change the values to the posted one, you will have it changed to OS version 5.1.461. This should allow you to run bbc version 2.1.2.52.

As allways, to find and change the hex-values you have to decode the nk.nbf first with the command "perl typhoonnbfdecode.pl -x nk.nbf".

Cheers
[Windows Mobile Development and Hacking General] beginner:
Problems with BB

Just to confirm if this is happening to you. Some times the mail I write in the jasjar, by bb, goes empty.
[Windows Mobile Development and Hacking General] caleymac:
Windows Mobile 6 - Black Edition - No Blackberry connection

I was wondering if anyone had success (or advice on) modifying the WM6-Black Edition ROM to change the OS identification from CE OS 5.2.968 (Build 17217.3.3.0) to one that will work with Blackberry Connect .31, .52. or .54...

I did try just modifying the AKU to .2.3.0 and .3.3.0, but this didn't help.

I've spent a few hours going through the various posts and wiki's on modifying the os.nb, but the process is still not clear to me.

I found RUU_signed.nbh by looking in a temp directory created when you start up Windows_Mobile_VI_-J_Black_Edition_v1.1.exe. I then extracted 00_OS.nb by running NBHextract.exe on the RUU_signed.nbh. I'm not certain of the next steps here...

I really like the WM6BE, lot's of free memory, faster, but not having Blackberry connect for my work email is a deal breaker.

TIA
[Windows Mobile Development and Hacking General] hidefguy:
blackberry connect for hermes cingular 8525

Instructions:

1. Extract the files. After downloading OS i.e black edition, lvsw, wxda etc... right click and select extract. I like to use winrar for extraction.

2. Use NBHextract to get the 00_OS.nb file. open a command prompt and navigate to the folder with the extracted files (NBHextract must be placed in that folder). and type "NBHextract 00_OS.nb" without quotes and press enter.

3. Use a Hex editor to change hex values. I use HexEdit (google search and download trial version).

Start HexEdit and then go to file open and open up 00_OS.nb

go to Tools - Find Hex

Select the Replace tab

Under Find copy and paste:

05 20 A0 E3 02 10 A0 E3 F2 EF A0 E3 03 40 A0 E3 00 50 A0 E3 00 30 80 E5

Under Replace copy and past:

05 20 A0 E3 01 10 A0 E3 73 EF A0 E3 03 40 A0 E3 00 50 A0 E3 01 30 80 E5

click Replace All, click OK to turn off read only, Hex Edit should have replace 2 occurences. Click OK. Save file as OS.nb

4. read wiki first http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG

Flash OS

Put hermes in bootloader mode (side ok + power button + softreset)

Connect Hermes to computer using USB cable.

Open mtty.exe, select "USB" from the dialog box, then hit Ok.

Hit enter twice and you'll see the "USB>" prompt.

Then type these commands: (note the use of 'lnb', without 's')

USB> task 32

USB> task 28

USB> lnb OS.nb

USB> task 28

USB> task 8

5. Changed HKLM\System\Versions and edit the Aku string from .0.0.0 to .2.3.0

6. Restart Hermes (holding power button)

This should result in OS Version 5.1.195 (Build 17217.2.3.0)

Install blackberry connect. I use version 2.1.2.54 and desktop version 2.1.1.21.
[Windows Mobile Development and Hacking General] KarmaNP:
Thank You

I apologize for not looking around harder. It's working smoothly now.

Thanks
[Windows Mobile Development and Hacking General] caleymac:
blackberry connect for hermes cingular 8525 on WM6BE

hidefguy: great instructions, very clear and easy to follow. Unfortuately I went through the process twice from the beginning. Each time the OS booted, but my today screen was flashing, and no program loaded in ROM would run. The OS description was blank on the About screen.

So I went back a few posts and changed the hex string to:

05 20 A0 E3 01 10 A0 E3 C3 E0 A0 E3 03 40 A0 E3 00 50 A0 E3 00 30 80 E5

instead of:

05 20 A0 E3 01 10 A0 E3 73 EF A0 E3 03 40 A0 E3 00 50 A0 E3 01 30 80 E5

Everything booted up fine. Unfortunately, neither .31 or .54 blackberry connect worked, even with trying .2.3.0 and .3.3.0 for each. Then I reloaded .54 (which didn't work again) and changed the HTC task switcher program (included with the ROM build) to minimize when hitting "X" instead of closing. .54 works just fine now. Success. Don't know if the two are related...don't care...it works.

Thanks again for your quick response and clear instructions...I wouldn't have attempted this process without them.
[Windows Mobile Development and Hacking General] jasjamming:
Version 1.2 of black will be out in a couple days supporting BBconnect.

We hopw u enjoy.
[Windows Mobile Development and Hacking General] hidefguy:
I had trouble initially getting .54 to work also, but once it worked it always worked. even when flashing new roms it works right away with no problems.
[Windows Mobile Development and Hacking General] eznil:
Hi.

I am trying to follow the process, however there is an obstacle I can't overcome.

Everything went fine till using mtty. The program runs, USB prompt is shown, "task 32" and "task 28" are finisfhed successfully, however "lnb" command responds with "Command error!!!".

I use SPL-1.09, IPL-1.01, OS 5.2.968 (build 17217.0.0.0)

Please advise,
[Windows Mobile Development and Hacking General] hidefguy:
In Step 3 did you rename to OS.nb? Also Os.nb has to be in the same location as mtty.
[Windows Mobile Development and Hacking General] eznil:
Yes I did. The problem is not with OS.nb location. Even without file name, or using "lnbs" command brings the same result.

Is it something with SPL version?

Another possible reasons

1. The respond on "task 32" command is "Level = FF". Is that the right one?

2. Step 4 in the description points to "Bootloader MFG" post. It's written there that the device should be SuperCID and SPL 1.01 MFG should be used. I applied SuperCid, but again couldn't execute "lnb". Is SuperCID / SPL-1.01 MFG necessary?

Thanks
[Windows Mobile Development and Hacking General] hidefguy:
Yes. your phone should be supercid and spl 1.01.
[Windows Mobile Development and Hacking General] eznil:
OK.

I tried to load SPL-1.01 MFG using the method described at http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG, but then again lnbs command was responded with "Command error!!!".

Any thoughts on this? Is there a possibility SPL-1.09 I currently have doesn't allow for this? If I manage to change back to SPL-1.01, should I go back to 1.09?

Thanks
[Windows Mobile Development and Hacking General] eznil:
Hi.

URGENT HELP NEEDED!!!

In the process of hacking BBConnect the following happened:

1. I applied AUTO_Unlock_V3 - OK

2. SPL-1.01 uploaded - OK

3. Uploaded a changed OS.nb - OK.

4. Device restarted, however now there was a problem - Autorun doesn't start. Device starts, GSM on (phone calls are OK), BUT the main screen shows "Tasks" and "Calendar" lines swapping. In addition "Device unlocked" line flashes as well.

Tried to flash back to SPL-1.04/1.09 - doesn't help.

During one of the trials the command was misspeled - I missed one 0 in the end of 50020000, so it started with 5002000. Can this cause the following?

Using mtty I ran "info 7", "info 8" command - BAD blocks shown:

USB>info 7

HTC Integrated Re-Flash Utility, Common Base Version : 1.50a

Device Name: H, Bootloader Version : 1.01

Built at: Apr 11 2006 18:29:22

Copyright (c) 1998-2006 High Tech Computer Corporation

CPU ID=0x41129200

Main CPLD version=0x5

Upper CPLD version=0x4

Main Board version=0x5

USB>info 8

Block 0x0(0) is Reversed block

Block 0x1(1) is Reversed block

Block 0x2(2) is Reversed block

Block 0x3(3) is Reversed block

Block 0x4(4) is Reversed block

Block 0x5(5) is Reversed block

Block 0x6(6) is Reversed block

Block 0x7(7) is Reversed block

Block 0x8(8) is Reversed block

Block 0x9(9) is Reversed block

Block 0xA(10) is Reversed block

Block 0xB(11) is Reversed block

Block 0xC(12) is Reversed block

Block 0x3A8(936) is BAD block !!!

Block 0x3A9(937) is BAD block !!!

Block 0x3AA(938) is BAD block !!!

Thought to reload one of the full versions, however ActiveSync can't connect. USB connection is only possible via mtty.

PLEASE ADVISE.

Thanks in advance,
[Windows Mobile Development and Hacking General] Mattie Boy:
Any chance of posting your rom (as per point 7) so us dummies (me) can just flash that straight onto my universal?
[Windows Mobile Development and Hacking General] japester36:
This looks to be exactly what I am looking for. I have been using BBC on the Hermes 1.35 SA ROM with 2.1.2.16, 2.1.2.31 & 2.1.2.52 with no problems and then have upgraded to the 2.11 SA ROM AKU 3.3..... Now, I can get a PIN but the BES refuses to send me email saying it is an illegal PIN in the BES logs.

My question is that now I am on 5.1.465 Build 15673.3.3.1, am I tripping over this issue of needing to hack OS.nb to show the amended version number and associated AKU regedit? or am I experiencing a different problem? (I have tried using 2.1.2.31, 2.1.2.52 & 2.1.2.54.)

IF I do need to do the hack, does anyone know the string to search and then replace for the above ROM? I have the OS.nb for the ROM extracted.

Thanks

John
[Windows Mobile Development and Hacking General] c0rnholio:
Hi John,

since you seem to be able to connect to the bb network there should be no need to hack the OS.nb.

IMO you should try to reregister your new PIN with the bb desktop software.

Is your current PIN shown on the device the same as in your bb desktop software?
[Windows Mobile Development and Hacking General] c0rnholio:
Sorry mate, I've sold my UNI and deleted all ROM from my HD. Maybe there is another kind UNI-BB user who can upload it for you somewhere.

Cheers
[Windows Mobile Development and Hacking General] japester36:
Hi c0rnholio,

Yes the PIN is the same on both hermes and the desktop software (...although my IS hadn't seen alpha characters used before and I now have a couple).

I guess I should try 2 things now 1) Go back to ROM 1.35 to check it works and 2) Escalate through service provider/RIM to find out why the PIN is illegal.

Thanks for the quick answer

John
[Windows Mobile Development and Hacking General] Rafael K:
Any Wizard WM6 BB enabled ROMs???

It would be very nice also if someone here could post a link to a WM6 Wizard ROM with BB connect hack done.

Not everybody has the cold blood and sufficient knowledge to do it. :D
[Windows Mobile Development and Hacking General] Andy Phillips:
WM6 rom for Wizard

Hi Guys,

I'm trying to follow these instructions to hack a WM6 rom for the wizard but can only find one instance of;

4F 3F A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 02

in the extracted 80040000-os.nb.

The rom I'm using is;

RUU_mUn_aRTM_10_2_0_8_WWE.exe

Any ideas?
[Windows Mobile Development and Hacking General] gumballsteve:
I'm trying this for the Artemis...

I've been trying to get BB connect working on a Artemis for a week !!!

Will this fix work?

I am currently running the

Dopod 800W rom, 1.28.0.0 wwe

radio: 02.56.90

ext rom PDAmobile.com

OS 5.1.342 (build 15096.3.3.0)

Blackberry version 2.1.2.54

BB Transpotr verision: 2.1.0.91

Blackberry system version: 66.4.22.92

This gives a PIN but will only connect for 3 seconds.

I've read all of this threed, as far as I understand all I need is to change the HEX values.

How can I get the new ones?

Thanks

S
[Windows Mobile Development and Hacking General] liay:
Hi there, I found a new OS kernel: 5.2.1413 (Build 17913.0.3.0)

but seek at the NB file, just found:

16 3D A0 E3 05 30 83 E3 45 2F A0 E3 05 10 A0 E3 02 E0 A0 E3

how can I change the 16 3D ?
[Windows Mobile Development and Hacking General] allway:
where can download the new OS kernel: 5.2.1413 (Build 17913.0.3.0)

thanks.
[Windows Mobile Development and Hacking General] titus666:
It says illegal pin because the combination of rom/bb connect version is not on the "approved" list. You have a pin because you had it working at one point and then upgraded the rom. Downgrade the rom and it will work again. Alternatively, modify the OS version numbers and AKU to be the same as the working rom as described in this thread and it should work again.
[Windows Mobile Development and Hacking General] japester36:
Hi titus666,

Thanks for getting me back on this, as per your advice, I have hacked the latest Mobile 6 Rom from LVSW and it works fine.

No more Illegal PIN. So that is definitely one of the symptoms that this hack cures.

Thanks to all on this thread.

John
[Windows Mobile Development and Hacking General] didaka:
Blackberry Connect & HTCP3600

Hi all

I've been reading the entire subject but my poor tech level, I'm bot able to test some i my device.

I've have WM5 OS5.1.465 Build 15673.2.3.0 and BB 2.1.2.31. I get a PIN (the same one that in my BES Account) but it's disconnect automatically after get an IP.

Could you tell the steps for a new, newbie?

Thanks in advance.

Diego.
[Windows Mobile Development and Hacking General] Marty:
Hello everyone, was wondering if I someone would be so kind to offer some help. Have read through the entire thread and seems need to do quite a few things to get BBC working on the various devices. However, since I have an HTC Apache (Sprint 6700), I don't know which steps are applicable to me or even if the necessary tools exist to flash my device. I am running OS 5.1.195 (Build 15698.3.5.0). Are there any versions of the BBC software that will just work with my device without the need for all the editing (probably not but I figured can't hurt to ask)? If not, I know the steps have been listed several times throughout the thread but since no one in this thread seems to be using my device, would be really grateful if someone could outline which steps are necessary for me to follow as well as which software tools are necessary for me to obtain. Thanks in advance for whatever help you can provide, I really appreciate it!
[Windows Mobile Development and Hacking General] KoolPal:
Hi c0rnholio / Others,

Need a bit of a help here.

I am using Fantastic Mobiz XBow v1.1i rom (http://xdaforums.com/showthread.php?t=302158) on my G4 Prophet.

Due to this WM6 upgrade this phone reports itself as a HTC Wizard. (found at Settings - Device Information - Identity - Model No.:)

I have extensively gone through this entire thread and seen:

Your help for Wizard:

http://xdaforums.com/showpost.php?p=1148067&postcount=35

Final outcome for Wizard:

http://xdaforums.com/showpost.php?p=1148393&postcount=45

I disassembelled the coredll.dll to get this:

EXPORT GetVersionExW

GetVersionExW

STMFD SP!, {R4,R5,LR} ; GetVersionEx

MOV R3, #0x114

MOV R2, #5

MOV R1, #2

MOV LR, #0x3C8

MOV R4, #3

MOV R5, #0

STR R3, [R0]

STR R2, [R0,#4]

STR R1, [R0,#8]

STR LR, [R0,#0xC]

STR R4, [R0,#0x10]

STRH R5, [R0,#0x14]

MOV R0, #1

LDMFD SP!, {R4,R5,LR}

BX LR

; End of function GetVersionExW

My understanding is as follows:

R2: Major version - 5

R1: Minor version - 2

LR: Decimal - 968

This I need to change to 5.1.195

Now I hex-edited the OS.nb to the following:

Curent: 05 20 A0 E3 02 10 A0 E3 F2 EF A0 E3

New : 05 20 A0 E3 01 10 A0 E3 C3 E0 A0 E3

! ! !

The items above the ! mark are the ones I changed.

I then flashed this hexed OS into my phone.

Then once phone was setup, I changed the AKU to show as .2.0.0 (HKLM\System\Versions\Aku)

I found the Device showing the desired OS version (Settings - About)

Windows Mobile 6

OS 5.1.195 (Build 17217.2.0.0)

Issues I found are as follows:

1. I found ONLY one instance of this hex string in the ENTIRE OS.nb!! I saw people advising to change this TWICE.....but I could NOT find the second instance at all! :(

2. After doing all as stated above, when I installed BBConnect_PocketPC_BB_2.1.2.16, It would not work. I would start and then show as stopped (within 1 second) :(

Please help!!
[Windows Mobile Development and Hacking General] pdazealot:
OK, maybe we hit this somewhere, but isn't the real question is there some way to

bypass the Version checking? We have been jumping over all these hoops, cooking our own ROM versions to take care of one item: A version validation feature in the application. We all are really looking for one thing, a BB Connect client that works on ALL Windows Mobile Smartphone or Win Mo PPC(Professional) versions. NOT one that is locked to a single machine type, like Wizard, TyTn, Excaliber, etc. Any thoughts on how to disassemble the app or dll's to have it bypass, etc? Cooking your own ROM to give a OS or radio version number seems to be not the best way. If we could get some crack guys on this we could have a single client that works on all PPC's or Win Mo Smartphones. Quite a feat! Thoughts on this?
[Windows Mobile Development and Hacking General] sting0r:
Anyone hack blackberry connect to work on the Dash / Excaliber with WM6 rom? Also, anyone try it with the Vox? Any suggestions on getting it to work would be appreciated. Thanks!
[Windows Mobile Development and Hacking General] titus666:
Now that BBC 4.0 is out for the Hermes (http://xdaforums.com/showthread.php?t=304973&highlight=blackberry) has anyone started collecting "valid" OS version numbers yet?
[Windows Mobile Development and Hacking General] c0rnholio:
This one should work:

OS: 5.1.461

AKU: .3.3.0

This is the ROM info from the official Vodafone Hermes Upgrade. Vodafone states on their BBC 4.0 download page that the Hermes must have this Upgrade in order to work. So I asume that this OS info will do the job. I can't test because I have an Athena and the ROM .nbh files are signed, thus I cannot flash a modified rom and no tools seem to be available to get this done for my device.

Cheers
[Windows Mobile Development and Hacking General] titus666:
Thanks Corn. I'll see if I can find some time and play with this...
[Windows Mobile Development and Hacking General] titus666:
I've changed my OS from 5.1.195 to 5.1.461 as per description.. boot the rom, and the OS number has not changed sigh... any suggestions?
[Windows Mobile Development and Hacking General] titus666:
Hmmm for some reason my device is not flashing.. it goes through the whole flash cycle and is seemingly successful, then boots up and not be flashed. I tried flashing another rom and it didnt change....

Edit: It seems I can flash OS.nb that I have not edited. I've flashed a combination of different roms and radios successfully, but flashing with an OS.nb that I've edited seem to not work. The process succeeds like normal, but the flash does not actually take place...

Edit2: It looks like I've hit the infamous G4 CID-locked flashed but not flashed issue! I guess this suggests that the G4 bootloader does some sort of checksum of the nb file.. Now I'll try Shelltool and see what happens...

Edit3: Success, sort of. I can flash with Shelltool, and I can make the version number to 460, but not 461, because I am using an AKU2.0 (5.1.195) rom, so in the rom, I cannot find the code for shifting, hence I can't add 1 to 460... might have to look for a newer rom to do this with..

Edit4: Finally installed Faria AKU 3.3.. lets see how BB4 likes this..

Edit 5: Sigh. I have 5.1.461 and AKU .3.3.0 and BB4 connects and drops. The system version generated is 44.8.221.254. It looks like this is not an approved combination... where did you get that vodaphone link from corn?

Edit 6: No joy at all for me.. Looking through the Hermes forums, they seem to be able to use their Black 3.0.1 rom edited to 5.1.195 AKU 2.3.0 for both BB 2.x & BB 4.x. I can confirm that this did not work for me. I hex'ed the faria 3.3 rom to 5.1.195 & AKU 2.3.0 and BB 4.x refused to work. To confirm that my account is still good, I went back to AKU 2.0.0 & used BB 2.1.2.31 & BB worked straight away. Looks like I have to keep waiting for some confirmed OS & AKU combinations before I can do this again..
[Windows Mobile Development and Hacking General] Andy Phillips:
Maybe it doesn't just check the OS and AKU versions (?)

Hi titus,

I've been keepin an eye on all the bbc threads as I'm currently using the Core2.0.Blackberry ROM (was on an old 2.17 rom before that!) because I refuse to use a blackberry device - cant stand the damned things!

Anyway...

Do you think its possible that the bbc is checking which device it is installed on;

ie. WIZA200

when the hermes is HERM100 and HERM200

I'm gonna have a go at installing v4.0 over the v2 tomorrow...

Already have the right OS version and have hacked the registry to show AKu2.3.0...next step is to hack the model version...

Will keep you posted...wish me luck!!

:D

EDIT: Darn...the model version aint in the registry...wouldn't know where to start in the OS.nb...will try version 4 anyway!
[Windows Mobile Development and Hacking General] c0rnholio:
http://www.vodafone.de/hilfe-support/technischer-support/97014_110496.html
[Windows Mobile Development and Hacking General] Andy Phillips:
Nope didnt work

Wouldn't connect..

however, when I installed the new client it connected and remained so until I sync'ed with the desktop and sent the provisioning info to the device. I wonder what's in that info!
[Windows Mobile Development and Hacking General] titus666:
Yep, same experience as me. Pretty sure there are more checks in place for BBC 4.x, probably deviceinfo. Corn believes a few other registry keys are also in play (discussion in another thread)...