Reusing WM2003SE Widcomm BT stack extracted from dumped ROM image - anyone tried?

[Menneisyys]

Please read the first post in this thread to acquire the latest version of the patch!!!!

For historical reasons, I keep the original post here so that the context of this thread isn't lost. Reading it is NOT needed for anyone; just follow the link above!






The title says it all

Just trying to swap the MS BT stack on my x51v into a Widcomm one, extracted from a WM2003SE x50v upgrade (say, this one: http://support.dell.com/support/down...&fileid=137112 ).

As the BT hardware may be exactly the same as on the (by default WM2003SE) x50v, it may not be impossible to disable the MS stack in the Registry (it's referenced in many, system-level, mainly Servicing-oriented registry entries) and use the Widcomm one instead.

Has anyone tried this? I've run a quick search here for 'dumprom' (the infamous tool ( http://wiki.xda-developers.com/index...gename=DumpRom ) to extract individual files from .nbf files - see http://www.firstloox.org//forums/showthread.php?p=39838 for more info; unfortunately, it seems it can't extract files from Dell's .IMG files) but couldn't find anything.

The IMG file is encrypted. Based on the repeating pattern, it may be a simple 64 byte-key XOR encoded file, which is very easy to reverse.

I don't want to waste some hours on this hack if anyone has tried it before and failed at it.

EDIT (March 24): I've been asked to link in the contest thread in the first post: here it is: http://www.aximsite.com/boards/showthread.php?t=121229


EDIT (March 27):

The links for the files are now:
http://thcgirls.com/BroadcommX51V02.zip
http://thcgirls.com/patchDUN.zip



EDIT (March 30):
A new thread has also been opened to post everything about the development of the project. This one is becoming huge and it starts to become impossible to find anything.

This is the new thread:

http://www.aximsite.com/boards/showthread.php?t=122247

EDIT (Apr. 4):

Files now online:

http://BTfix.thcgirls.com/BroadcommX51V0.35.zip

http://BTfix.thcgirls.com/BroadcommX51V031.zip

http://BTfix.thcgirls.com/BroadcommX51V03.zip

EDIT (Apr. 5):
the latest version (see page 16): http://bt.nokistein.com/BroadcomX51V0.36.zip

EDIT (Apr. 24):

he latest version is 0.37

[The14given]

It sounds very interesting. It would be very cool using BROADCOM on WM5. I didn't see anyone trying to hack this but maybe there are some clever guys out htere, who will manage it.

[Menneisyys]

I'll try to do my best

[makuu]

I never tried it but I found this , is it what you are about to try?

[Menneisyys]

Originally Posted by makuu

I never tried it but I found this , is it what you are about to try?

Yup, but for the i-mate k-jam, which prolly has a different hardware than the x50v/x51v. That is, I'll try to change the BT manager using the x50v WM2003SE version first and if I don't succeed, I give a try to other Windcomm hacks.

[dvmed]

Thanks for the link makuu. I'm going to try it later tonight. I think the difficult part is how to point the registry to use the X51's bluetooth driver. bthcsr.dll is there so I guess its worth a try.

[Li0rE]

Originally Posted by Menneisyys

The title says it all

Just trying to swap the MS BT stack on my x51v into a Widcomm one, extracted from a WM2003SE x50v upgrade (say, this one: http://support.dell.com/support/down...&fileid=137112 ).

As the BT hardware may be exactly the same as on the (by default WM2003SE) x50v, it may not be impossible to disable the MS stack in the Registry (it's referenced in many, system-level, mainly Servicing-oriented registry entries) and use the Widcomm one instead.

Has anyone tried this? I've run a quick search here for 'dumprom' (the infamous tool ( http://wiki.xda-developers.com/index...gename=DumpRom ) to extract individual files from .nbf files - see http://www.firstloox.org//forums/showthread.php?p=39838 for more info; unfortunately, it seems it can't extract files from Dell's .IMG files) but couldn't find anything.

The IMG file is encrypted. Based on the repeating pattern, it may be a simple 64 byte-key XOR encoded file, which is very easy to reverse.

I don't want to waste some hours on this hack if anyone has tried it before and failed at it.

I tried it. Had to hard reset. It set my volume to low and I couldnt stop it even after deleting.

[Menneisyys]

Originally Posted by Li0rE

I tried it. Had to hard reset. It set my volume to low and I couldnt stop it even after deleting.

Originally Posted by Li0rE

I tried it. Had to hard reset. It set my volume to low and I couldnt stop it even after deleting.

Could you please elaborate on this a bit more? Did you took the WM2003SE x50v Widcomm BT-related files and made them work on a x51v? Or, did you mean the indoxda.net stuff linked above? I'd be really interested – it'd be great to have, for example, BT PAN capabilities.

As far as the latter is concerned, I've done what it said. BTTrayCe has indeed shown the Widcomm BT icon on the toolbar. The BT Manager, however, complained about the missing hardware ("insert card") and starting the BT servce itself was impossible (the well-known "Out of memory" error.)

Then, I've started overwriting the indoxda.net files with the WM2003SE x50v BT files I've managed to extract (uploaded them here so you can also give them a try). Also, I've extracted the relevant Registry area from my Pocket Loox 720; it's available here as a registry import file.

It didn't work either. Much as the apps at least start (after overwriting the original indoxda.net files with them), unlike in the case when I just copied them over the PDA and just imported my registry import file.

[kiloviper]

If this could work it would be really awesome!!

[Patrick Y.]

Originally Posted by makuu

I never tried it but I found this , is it what you are about to try?

Be careful about this. I believe a thread about this was immediately deleted by the moderator since it's illegal. It doesn't work for Axims anyway.

[Dermot81]

Originally Posted by kiloviper

If this could work it would be really awesome!!

Yes, yes it would

[coolbre304]

Its an awesome idea, and I would be glad to help if you like. I've just poked at the registry a bit, but some of the stuff for BT is contained in

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BLUETOOTH

Mabey deleting the whole entire thing will get rid of the MSFT stack to go away. Altough like you said getting the ax to look for the widcomm driver might be kinda difficult. Mabey swithcing some of the .dll files in that reg entry we can kinda swap it out.

[computervreak]

Originally Posted by makuu

I never tried it but I found this , is it what you are about to try?

i did that from the site but when i do a soft reset it says "the bluettoth radio failed to turn on due to insufficent driver memory available. You must perform a normal reset before you turn on the bluetooth radio. Please help me

[Patrick Y.]

Originally Posted by computervreak

i did that from the site but when i do a soft reset it says "the bluettoth radio failed to turn on due to insufficent driver memory available. You must perform a normal reset before you turn on the bluetooth radio. Please help me

1. It's for Imate K-JAM
2. It's illegal

[Menneisyys]

Originally Posted by coolbre304

Its an awesome idea, and I would be glad to help if you like. I've just poked at the registry a bit, but some of the stuff for BT is contained in

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BLUETOOTH

Mabey deleting the whole entire thing will get rid of the MSFT stack to go away. Altough like you said getting the ax to look for the widcomm driver might be kinda difficult. Mabey swithcing some of the .dll files in that reg entry we can kinda swap it out.

Yup, I'm just trying to switch "old" WM2003SE x50v (so that I have hardware compatibility) Widcomm drivers with the new WM5 drivers. Hope I'll have success