yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] Mjammjam:
Me finally had the time to play around with this as well. Unfortunately, BBC 4 won't work on my Universal either.

So far:

ARTE200, 5.2.1238, 17745.0.2.0, BBC4, PDAVIET.Net - supposedly working (pt-1)

HERM100, 5.2.1238, 17745.0.2.3, BBC4 - not working (anymore) (walshieau)

ARTE110, 5.2.1238, 17745.0.2.3, BBC4 - working (gladiac)

WIZARD, 5.2.1413, 17913.0.3.0, BBC4, nbd.v7.1.touch.ext - working (andy)

WIZARD, 5.2.1413, 17913.0.3.0, BBC4, nbd.v7.2 - not working (bbc4: illegal pin, bbc2: working) (titus)

UNIVERSAL, 5.2.1413, 17913.0.3.0, BBC4, Midget v1.0 - not working (mine)

Now what? bbcservice.dll? Did a quick scan through the BBC install files, "HTC-UNIVERSAL" and "HTC-WIZARD" show up in a number of bbc files, but not other device types. So it's probably pulling the device type string from somewhere else. Does anyone know where those strings might be stored in the OS?

So far, noone is running BBC4 on a Universal, correct?
[Windows Mobile Development and Hacking General] NetrunnerAT:
PM200 5.2.1413, 17212 AKU 0.2.0 or 0.2.3 or 0.3.0 PV4.0.0.0.4 doesnt work -> Status Pending

How i can edit build number?
[Windows Mobile Development and Hacking General] Mjammjam:
To edit the build number (e.g. 5.2.1413), basically follow the previously posted info in this thread.

c0rnholio wrote:

http://xdaforums.com/showpost.php?p=1147021&postcount=23

Short sum up (on universal):

1. Take the ROM you flashed your PDA with.

2. Decode it (with HTC64 Extended ROM Tool).

3. Extract XIP section from .nba/.fat (with rommaster).

3a. RomMaster.exe nk.nba -w 5 -x -o xip2.nb

4. Extract coredll.dll from xip section (with dumpromx).

4a. mkdir xip2 \ dumpromx.exe xip2.nb -f coredll.dll -d xip2 -5

5. Disassemble coredll.dll (ida pro 5.1 demo is sufficient).

6. In Disassemble: Search Function "GetVersionExW", determine relevant Version String Bytes.

6a. To do this: http://xdaforums.com/showpost.php?p=1147257&postcount=25

7. Flip Version String Bytes to resemble another build string.

7a. To do this: http://xdaforums.com/showpost.php?p=1150039&postcount=64

7b. Correction to 7a: http://xdaforums.com/showpost.php?p=1276121&postcount=152

8. Write the flipped bytes back into the .nba/.fat with your favorite Hex Editor (UltraEdit / WinHex / XVI32).

9. Re-encode the .nba/.fat into .nbf.

10. Re-Flash your PDA with the ROM you just whacked a little.

You will need to use other rom tools for other devices.
[Windows Mobile Development and Hacking General] liay:
How about the new Kaiser's coredll.dll?

I know it's CE OS 5.2.???? Build 17938.0.3.1

but I cant disassemble it correctly with IDA5.0

would u like have a try with 5.1demo
[Windows Mobile Development and Hacking General] Mjammjam:
I cannot work Kaiser's coredll.dll either, on IDA Pro 5.1 Demo.

Maybe there is some guru around who can? Are you sure you extracted it right from the xip?
[Windows Mobile Development and Hacking General] beginner:
yes, it is totally true. It is happening to me in my country, Spain, by Vodafone. I cannot connect with BB 2 or BB4, but I know people with same device running perfectly with BB2 over Movistar. After reset my user on my exchange server, generating new codes, it still not working. I asked to Vodafone who told me that they couldn't scalate to BB due my device is not supported by Vodafone, but they were seeing my line was correct, or in other words, the line from my pda to bb server is correct.

Maybe I move to Movistar shortly, due the cost using GPRS for pushing mail.

I have to say that after 3 hard reset and cancel for a while the service with the mobile provider and later reactivate, the bb 2.1.2.54 is running fine...

let see if found some solution for bb4.
[Windows Mobile Development and Hacking General] Mjammjam:
Well, after flashing back to c0rnholio's old wm6 + bbc2 combination, all works fine. So it looks like RIM is not blocking specific devices.

Old state works fine:

Device Type: HTC-Universal

ROM Version 2.01.08 WWE

ROM: ?

OS Build: 5.1.195

AKU: 15341.2.0.0

Radio ROM: 1.13.0.0

BBC Version: 2.1.2.31

BBC Transport: 2.1.0.75

BBC System Version: 208.108.34.203

Now onto BBC 4 again ;) Where is my bed?

beginner, just read your last post before this one:

Well, looks like we'll have to figure out how to change the device type as well ;-) To sad RIM is being a little narrow-minded (not to call it money-oriented) on this. In your case, I would be speculating, RIM started blocking your device _type_ for vodafone just now (instead of your specific device)? Or maybe the vodafone guys in germany are just slower and haven't seen me hopping OS'es on their network yet.

funny thing that kind of amuses me:

With BBC4, the BBC on the PDA did only get the PIN after being hooked up with BBC Desktop.

With BBC2, the BBC on the PDA did get its PIN without a BBC Desktop connection...
[Windows Mobile Development and Hacking General] moisha:
ARTE200, 5.2.1238, 17745.0.2.0, BBC4, PDAVIET.Net - supposedly working (pt-1)

HERM100, 5.2.1238, 17745.0.2.3, BBC4 - not working (anymore) (walshieau)

ARTE110, 5.2.1238, 17745.0.2.3, BBC4 - working (gladiac)

HERM100, 5.2.1238, 17913.0.3.0, BBC2 - not working ( moisha )

WIZARD, 5.2.1413, 17913.0.3.0, BBC4, nbd.v7.1.touch.ext - working (andy)

WIZARD, 5.2.1413, 17913.0.3.0, BBC4, nbd.v7.2 - not working (bbc4: illegal pin, bbc2: working) (titus)

UNIVERSAL, 5.2.1413, 17913.0.3.0, BBC4, Midget v1.0 - not working (mjammjam)
[Windows Mobile Development and Hacking General] Mjammjam:
Did not do much more, but rechecked with my friend that runs the same Device with BBC4 working:

His Device (BBC4 was working until 23.06):

Provider: Vodafone Germany

Device Type: HTC-Universal

ROM Version 2.20.02 WWE

ROM: Midget 1990 v1.0

OS Build: 5.2.1413

AKU: 17913.0.3.0

Radio ROM: 1.15.0.0

BBC Version: 4.0.0.67

BBC Transport: 4.0.0.70

BBC System Version: 46.145.237.165

HKLM\System\Versions\AKU: exists

HKLM\System\Versions\DeviceVersionInfo: does not exist

My Device (BBC4 not working):

Provider: Vodafone Germany

Device Type: HTC-Universal

ROM Version 2.20.02 WWE

ROM: Midget 1990 v1.0

OS Build: 5.2.1413

AKU: 17913.0.3.0

Radio ROM: 1.15.0.0

BBC Version: 4.0.0.67

BBC Transport: 4.0.0.70

BBC System Version: 46.145.237.165

HKLM\System\Versions\AKU: exists

HKLM\System\Versions\DeviceVersionInfo: does not exist

Even though the BBC System Version is identical, we have one working and the other one not. So, lets go searching what new checks RIM added ;)

Update: My friend's universal was working until 23.06 (bbc4). Thereafter, it did not connect to the rim network anymore. So it looks like RIM is very picky about which BBC4 devices connect to their network. And not that picky with BBC2 devices, since mine started working again with the old c0rnholio wm6+bbc2. I would wonder if they single out specific BBC4 devices. It definitely looks like they kick devices manually, since people are reporting that their device is working at first, then ceases to connect after maybe one or two weeks usage (looks like odd behaviour for a large company like RIM to me... a bunch of clowns bouncing unwanted guests). Then, on what basis do they decide if they allow a network connect or not? And why aren't they that picky about BBC2 devices? Maybe they have introduced new checks they did not have before?
[Windows Mobile Development and Hacking General] beginner:
I think bb is not interesting having us using BB4 because the consume by internet using their connection.
[Windows Mobile Development and Hacking General] titus666:
It should be noted that BB2 works for me by hex editing the rom to 5.1.195 AKU 2.0.0.
[Windows Mobile Development and Hacking General] titus666:
When BB 1.x first came out, I remember that there were no automated checks in place, and people used to find themselves "permanently" banned (illegal handheld pin) after a couple of weeks of use. This changed after a while to an automated check. By the time I (personally) first encountered "illegal handheld pin" (when I tried to use BB 2.x on my Himalaya that already had BB 1.x working), I could always revert to an "approved" version, just like now. Hence I would not be totally surprised if they really were manually locking pins out.
[Windows Mobile Development and Hacking General] wallsj:
BBC + Trinity

Anyone got any known good versions that work with a Trinity?

I got OS 5.1.465 (15673.3.3.1)

Tried BBC 4.0.0.67; 2.1.2.54; 2.1.2.45 and some others - none work.

Vodafone UK have said it's all ok at their end although BBC isn't supported; RIM have said 'only phone provider can suggest right version of BBC to use'!

Know there's a working version on the cooked WM6 ROMs but don't want to flash those until they've been out a bit longer.

John
[Windows Mobile Development and Hacking General] NetrunnerAT:
I have talk with my provider ...

I think, the Provider buy the licence to use a BBC Version and RIM only alowe this Version. Like a Provider base Lock with Hardware ID etc ...

RIM is Stupid!

MS is the direct Enemy for Mobile PIM and they use so strange protections ... they only what they got are less customers!
[Windows Mobile Development and Hacking General] anonamouse:
I was using Black Shadow, Blackberry Connect 4 stopped working a couple of days ago with Illegal Device PIN. Flashed back to Black Dymond and BBConnect is now up and running again.
[Windows Mobile Development and Hacking General] beginner:
I suppose rim try to sell anyway the stupid bb devices...
[Windows Mobile Development and Hacking General] titus666:
Can you provide the device type, OS version (eg 5.2.1413), AKU & BB version please?
[Windows Mobile Development and Hacking General] walshieau:
correct as ive been saying there is something going on with the 17745 builds and Hermes devices...
[Windows Mobile Development and Hacking General] nonexxx:
My Trinity only work now with dopod Rom.

Few days ago, My BBC 4.0 work fine with the Rom of LSW WM6 but now don´t work.. :(

Today only work my BBC 4 with the Rom Dopod Wm5..:(

Thanks
[Windows Mobile Development and Hacking General] beginner:
I think the key point to use what version you like is to change the file that bbconnect send to rim. Yes, i am not telling nothing but looks the way. Due the program on the pda is not being modificated by rim remotely, they have their decission on what pin accepts or not based on some fields in one of their files.

Unafortunately I am not programmer and not know how to find the file, but what I want to say is do for bbconnect that the pda be the model and os it likes.

sorry because this looks philosopycal...
[Windows Mobile Development and Hacking General] gladiac:
Good Morning.

I just wanted to let you guys know that RIM found themselfs very comfortable in locking me and others out from their bb-network with my current bbconnect setup that worked several weeks until yesterday.

I have to say that this is a really big crap they are doing. Though, I will play aroung and maybe I get bbconnect4 to work again...

//EDIT: Ah, If some talented programmer out there is willing to write a loader for this freaking painful connector it would be a great deal for every bbconnect user that has a non-standard firmware.

cheers
[Windows Mobile Development and Hacking General] walshieau:
they have resorted to IMEI blocking...
[Windows Mobile Development and Hacking General] gladiac:
Where do you know that from? If that is corrent I will have to get a new device and that's something that will not happen. Good to know that we have a BES we pay for...

Whatever, new status:

ARTE110, 5.2.1238, 17745.0.2.0, BBC4 - stopped working (gladiac)
[Windows Mobile Development and Hacking General] edsub:
I may have overlooked it, but I cant seem to find the hex string to be edited in Wizard WM5 (especially the latest AKU 3.3 by Faria/Molski) ROMS in orde to get BBConnect to work.

I am currently on the 2.17 ROM but would be more than happy to upgrade again to AKU 3.3

Since I use the Wizard for my work I'd rather stick with proven WM5 before going to WM6
[Windows Mobile Development and Hacking General] titus666:
Its at the beginning of this thread... OS 5.1.195, AKU 2.0 for BBC 2.1.2.31.

I've run the AKU 3.3 rom you mentioned and now I'm on NBD (WM6) which works better (in general).
[Windows Mobile Development and Hacking General] walshieau:
i have rung them about it...
[Windows Mobile Development and Hacking General] gladiac:
ok, crap :/
[Windows Mobile Development and Hacking General] edsub:
I know what the ruight combnation of OS/AKU and BBC is.

I have the correct BBC

Changing the AKU is no issue either.

Patching the OS version is: What are the exact hex values I have to search for and what are the exact hex values I have to replace them with.
[Windows Mobile Development and Hacking General] titus666:
I *think* the hex string I searched for is: 05 20 A0 E3 01 10 A0 E3

Having a quick look at my roms.. the difference (from original to edited) is I changed 73 3F to C3 30 (twice)

Thats the one I saved and I am pretty sure thats what I used when I went to Faria's WM5 rom. If thats not right, let me know what the OS version is and I'll see if I can find it (if its the same rom as I had). Otherwise you'll need to do what was suggested in the thread and disassemble the rom and find the hex.
[Windows Mobile Development and Hacking General] edsub:
my god i am feeling like a complete noob here.

I found the 05 20 A0 E3 01 10 A0 E3 string twice.

Edit: This is the same string (05 20 A0 E3 02 10 A0 E3 A5 EF A0 E3) as mentioned n earlier post re WM6 ROMS.

Can it be that I just have to do the same as mentioned there

But I cant seem to get the relation with the 'I changed 73 3F to C3 30 (twice)' part you mentioned.

When I search for '73 3F' I find numerous occurrences.
[Windows Mobile Development and Hacking General] edsub:
Another question.

Since Im going to AKU3.3 (WM5) rom, cant I use one of those newer BBC clients (.52 or .54) instead of .31?

If so, the what are the strings to search for and to replace into?
[Windows Mobile Development and Hacking General] walshieau:
version 4.0 of the BBC works with AKU3.3 WM5...
[Windows Mobile Development and Hacking General] edsub:
Are you sure BBC isnt also dependent on the device id?

I have a Wizard

What should be the best BBC client running on a AKU3.3 Wizard.

I know BBC 2.1.2.31 works on the Wizard if I manage to change the reported OS string to 5.1.195 and keep the AKU at .2.0.0

I am currently running the 2.1.2.31 BBC on a true AKU 2.0.0 ROM and am quite happy. Annoying is still that contacts dont sync and that I can't use lookup email adresses when sheduling a meeting with attendees.
[Windows Mobile Development and Hacking General] jimmyz:
Hello- I'm trying to get BB connect 4.0 running on my sprint ppc6800 (HTC titan). It installs without any problems but the client refuses to connect. I'm assuming that the blackberry servers are blocking my device. Any thoughts on how to proceed? I'm assuming it will be more complicated than getting it to work on a gsm device

thanks jz
[Windows Mobile Development and Hacking General] edsub:
I think you would know the answer when you've read this entire thread.

Probably has to do with the combination of device / OS version and AKU level and BBC version.

You wil need to do some hacking (ie change the OS version and AKU level and maybe use another BBC client.
[Windows Mobile Development and Hacking General] Rafael K:
Anyone else with the Wizard?

Anyone else with the wizard been able to cope with this? I had no luck so far. I tried to change the AKU several times and could not connect...

Sorry: should've said I am trying with Not Big Deal 7.4.
[Windows Mobile Development and Hacking General] beginner:
devices with bb4 running

please, could people running with bb4 what device is and rom version and aku please?

I don't know if my bad english causes mistakes. I was asking if people running bb4 and obviously pushing mail can say what device/rom version/aku are using, please.
[Windows Mobile Development and Hacking General] Ratze:
Hacking help for 5.2.1413 needed

First of all great job.

I need some help for my Wizard.

I want to change from 5.2.1413 to 5.1.195 in order to use bbconnect 31 but I don't know how to change the 1413. I want to use NBD7.4 with BB.

Nothing works for me with 5.2.1413.:rolleyes:

Here my code:

.text:03F6AA80 GetVersionExW

.text:03F6AA80 STMFD SP!, {R4,R5,LR} ; GetVersionEx

.text:03F6AA84 MOV R3, #0x580

.text:03F6AA88 ORR R3, R3, #5

.text:03F6AA8C MOV R2, #0x114

.text:03F6AA90 MOV R1, #5

.text:03F6AA94 MOV LR, #2

.text:03F6AA98 MOV R4, #3

.text:03F6AA9C MOV R5, #0

.text:03F6AAA0 STR R3, [R0,#0xC]

.text:03F6AAA4 STR R2, [R0]

.text:03F6AAA8 STR R1, [R0,#4]

.text:03F6AAAC STR LR, [R0,#8]

.text:03F6AAB0 STR R4, [R0,#0x10]

.text:03F6AAB4 STRH R5, [R0,#0x14]

.text:03F6AAB8 MOV R0, #1

.text:03F6AABC LDMFD SP!, {R4,R5,LR}

.text:03F6AAC0 BX LR

.text:03F6AAC0 ; End of function GetVersionExW

And hex:

30 40 2D E9 16 3D A0 E3-05 30 83 E3 45 2F A0 E3

05 10 A0 E3 02 E0 A0 E3-03 40 A0 E3 00 50 A0 E3

0C 30 80 E5 00 20 80 E5-04 10 80 E5 08 E0 80 E5

10 40 80 E5 B4 51 C0 E1-01 00 A0 E3 30 40 BD E8

1E FF 2F E1

Changing 05 10 A0 E3 02 E0 A0 E3-03 40 A0 E3 00 50 A0 E3 to

05 10 A0 E3 01 E0 A0 E3-03 40 A0 E3 00 50 A0 E3 results in version 5.1.1413

Some ideas? Help desired.

HTC Wizard

ipl 2.21.00001

spl 2.21.00001

gsm 2.19

ROM: would like to use NBD v7.4 (5.2.1413)
[Windows Mobile Development and Hacking General] c0rnholio:
Change this:

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

which is: (0x16 * 0x40) = 0x580 + 5 = 0x585 = dec 1413

to this:

1D 3E A0 E3 01 30 83 E3 45 2F A0 E3 05 10 A0 E3 01

which is: (0x1D * 0x10) = 0x1D0 + 1 = 0x1D1 = dec 465

This results in OS version 5.1.465

Now change AKU string to .3.3.1 and you can install BBC 2.1.2.54

If you still want to stick to BBC v.31 use the hex values posted multiple times in this thread.

Tell us if it works or not.

Cheers
[Windows Mobile Development and Hacking General] walshieau:
some versions of 4.0 Floating around are Device Specific EG Hermes..
[Windows Mobile Development and Hacking General] c0rnholio:
Hm...I only know version 4.0.0.67 from vodafone and dopod for PPC and version 4.0.0.76 (if I remember right from dopod also) for Smartphones.

The vodafone and dopod seem to be the same...

Do you know any other?
[Windows Mobile Development and Hacking General] cychiam:
BBC for Universal 5.2.1413 Build 17913.0.3.0

Have read through the entire thread. Have to really salute to all the experts here. In any case, I still believe that by changing my Universal to some older OS version and AKU that are officially supported by RIM, BB will connect and pull the emails.

Presently, I am using the above ROM by Laurentius26 and wanted to get Blackberry work. BBC2 or BBC4 does not matter at this point though it would be much desired for. I hope to get at least 2.1.2.52 or 2.1.2.54 to work on my set.

I have set out to change the OS ver according to steps prescribed by c0rnholio and here's what I got.

.text:03F6AA80 EXPORT GetVersionExW

.text:03F6AA80 GetVersionExW

.text:03F6AA80

.text:03F6AA80 arg_5 = 5

.text:03F6AA80

.text:03F6AA80 STMFD SP!, {R4,R5,LR} ; GetVersionEx

.text:03F6AA84 MOVL R3, 0x585

.text:03F6AA8C MOV R2, #0x114

.text:03F6AA90 MOV R1, #5

.text:03F6AA94 MOV LR, #2

.text:03F6AA98 MOV R4, #3

.text:03F6AA9C MOV R5, #0

.text:03F6AAA0 STR R3, [R0,#0xC]

.text:03F6AAA4 STR R2, [R0]

.text:03F6AAA8 STR R1, [R0,#4]

.text:03F6AAAC STR LR, [R0,#8]

.text:03F6AAB0 STR R4, [R0,#0x10]

.text:03F6AAB4 STRH R5, [R0,#0x14]

.text:03F6AAB8 MOV R0, #1

.text:03F6AABC LDMFD SP!, {R4,R5,LR}

.text:03F6AAC0 BX LR

.text:03F6AAC0 ; End of function GetVersionExW

Hex:

30 40 2D E9 16 3D A0 E3 05 30 83 E3 45 2F A0 E3

05 10 A0 E3 02 E0 A0 E3 03 40 A0 E3 00 50 A0 E3

0C 30 80 E5 00 20 80 E5 04 10 80 E5 08 E0 80 E5

10 40 80 E5 B4 51 C0 E1 01 00 A0 E3 30 40 BD E8

This is pretty different from the examples given and being a total "noob" in disassembly, I have no idea how to proceed.

0x585 hex = 1413 dec

I can guess where is the major (5) and minor (2) versions. The trick now is how to change it. The exact problem now faced by Ratze.

Hope to get some help from here. Thanks.
[Windows Mobile Development and Hacking General] c0rnholio:
Please look at post 253.
[Windows Mobile Development and Hacking General] Ratze:
Now my wizard works with BBC 31 with a 5.2.1413 rom hacked to 5.1.195 and modified AKU reg.

And it works with hack to 5.1.465 AKU string .3.3.1 and BBC 2.1.2.54, too.

Thanks for your support!

HTC Wizard

ipl 2.21.00001

spl 2.21.00001

gsm 2.19

ROM: 5.1.195 formerly known as 5.2.1413 (nbd7.4)
[Windows Mobile Development and Hacking General] walshieau:
yes... there is one from Imate also....
[Windows Mobile Development and Hacking General] beginner:
do you know if it is only for registered users? is there a link?
[Windows Mobile Development and Hacking General] edsub:
OK I am currently looking at the latest official Wizard WM5 AKU3.3 WWE ROM by T-Mobile (HR)

It has OS version 5.1.461

I plan to use the BBC 2.1.2.54 client which needs the OS version 5.1.465

Searching the OS nb file resulted in two occurrences of the string

73 3F A0 E3 01 30 83 E3 45 2F A0 E3 05 10 A0 E3 01 (which represents the .461 part of the OS version)

According to the posts in this thread I should change this string to

1D 3E A0 E3 01 30 83 E3 45 2F A0 E3 05 10 A0 E3 01

to change the utter right part of the OS version to .465

But before trying to apply the changes and to flash my Wizard:

There is one thing that puzzles me however. Does the utter left and middle part of the OS version (which should be 05 20 A0 E3 01 10 A0 E3; also found twice) need to be in the bytes directly left to the string contaning the utter right part of the OS version?
[Windows Mobile Development and Hacking General] cychiam:
I changed the hex string to the above to get OS 5.1.465 and AKU .3.3.1 for my Universal. Unfortunately, it did not work when using BBC 2.1.2.54.

It went "Network Available" to "Data Tunnel Available" to "Not Connected".

Does it really work only for Wizard?
[Windows Mobile Development and Hacking General] titus666:
Sorry I didn't get back to you with the other post, have been a bit busy of late with sick kids. Looks like you found the "73 3F" now..

In terms of the "05 20 A0 E3 01 10 A0 E3", it appears in different places in different roms.. it's a bit clearer if you use a disassembler and look at the getversionx function matched against the hex.

I haven't used that version combination.. I kept on using 2.1.2.31 with OS 5.1.195.
[Windows Mobile Development and Hacking General] titus666:
Was there any real difference between 2.1.2.31 & 2.1.2.54?
[Windows Mobile Development and Hacking General] edsub:
Gr8 to get my findings confirmed.

I will flash this evening an post my findings.

My objective is primarily to use the official AKU3.3 ROM, best BBC version for that is 2.1.2.52.

I dont expect much from the 2.1.2.52 version as compared to 2.1.2.31 but I want to use it just because it seems to be newer (sometimes that means improved)....

BTW what still seems strangte to me that you managed to get to OS version .195 by just changing 73 3F to C3 30 (twice). According to my calculations your version should then be .196!
[Windows Mobile Development and Hacking General] beginner:
did you check bb .52?
[Windows Mobile Development and Hacking General] edsub:
I put my actions/findings together in the Wiki:

http://wiki.xda-developers.com/index.php?pagename=Wizard_version_hack
[Windows Mobile Development and Hacking General] cychiam:
No, I did not. I suppose .52. and .54 are minor revisions and have assumed it probably won't work.

I have changed to 5.1.195 with AKU 2.0.0 and am using BBC 2.1.1.31 on my Universal now.
[Windows Mobile Development and Hacking General] Andy Phillips:
Fantastic!

Good job!

:) :) :)
[Windows Mobile Development and Hacking General] beginner:
It's a very good resume. My problem is my device is an ATHENA. I was trying to find the hex keys you mention but doesn't look same. Maybe is my fault on knowledge how to decode the rom file.