O2 XDA II->WM2003SE->Extended ROM->Sin.AU.v3.5

[Sin]

INFO: New version is here! (http://forum.xda-developers.com/viewtopic.php?t=16916)

[darren_the]

Great 8)

[Sin]

See 1st post

[recrem]

Sin,

FTP and gmail failed... but downloading now from the link you placed to xda-dev!

Great work!

Recrem...

[letsfish]

BUGGER! have to go to work. will download tonight and give it a try. SIN'S original upgrade from Friday still working perfectly. It's going to be a slow day!!!!

[Believer]

thanks alot, ill give it a go

[Believer]

got a country error, I have an Imate and not an XDA II. What are the steps for changing it. Thanks.

[Believer]

worked it out

for anyone else

1. Get GetDeviceData from http://wiki.xda-developers.com/index.php?pagename=HimaGetDeviceData and run it on your device, check the "\Windows\DeviceData.txt" file to find out what operator name you have (imate is "CDL")
2. Get the "xda2nbftool" from http://wiki.xda-developers.com/index.php?pagename=xda2nbftool to change the code in the rom
3. Then I got the "OperatorUpdate.zip" from this thread http://forum.xda-developers.com/viewtopic.php?t=13588&highlight=imate+2003se
4. and with all that stuff in the same directory as the rom update typed "OperatorUpdate CDL" to change the operator to CDL
5. then run the "HimaUpgradeUt.exe" from the 2003se rom at the start of this thread.

it worked 2003se! (note this may not be the easiest way, but it worked)

[haveric]

Yes believer I did the same thing as you
very happy though no media player??? must have failed somewhere :evil:

will try reflashing will keep posted

[brian_bunny]

Hi Sin,

Mate! What a great effort! However, I am suffering a strange problem on my XDA II. Aftrer I upgraded the ROM and selected the "Authentication (passkey) required" in the Bluetooth settings, the phone just frozen after a soft reset. I kept doing the soft reset but I still can't wake the phone up. Have encountered this problem before? I am using the Ver. 2 of your extended ROM.

Thanks for all suggestions!

Cheers!

[Sin]

selected the "Authentication (passkey) required" in the Bluetooth settings, the phone just frozen after a soft reset. I kept doing the soft reset but I still can't wake the phone up. Have encountered this problem before?

The only issue with BT I've had, turned out to be my mistake when trying to ActiveSync with another newly installed ROM. Couldn't connect then remembered that I needed to remove a previous pairing to my device from my workstation.

I've toggled the passkey checkbox multiple times with resets in between and can't replicate the problem here. Anyone else?

[angry_shot]

When running operatorupdate.bat i get WARNING: checksum is not ok, possibly you provided the wrong password.

What is the password on the *.nbk's?

James

[Sin]

What is the password on the *.nbk's?

Hi James,

The passwords are as follows:

NK.nbf Password: 0x20040304
ms_.nbf Password: 0x20040305
Radio_.nbf Password: 0x20040306

:idea: For anyone using ER2003Edit, first select the specific file type (not auto).

[angry_shot]

ignore that last one - i don't think it has a password ;-)

[Demon]

What is the password on the *.nbk's?

Hi James,

The passwords are as follows:

NK.nbf Password: 0x20040304
ms_.nbf Password: 0x20040305
Radio_.nbf Password: 0x20040306

:idea: For anyone using ER2003Edit, first select the specific file type (not auto).

It doesn't recognize the password for ms_.nbf
Any idea?

[melv]

i download the file from the first post and installed it onto my XDAII
but now when i put the xdaii into the cradle the screen says something about activesync being the old version ?
does anyone know where i can get an updated version of it to get it to sync again ?

[Believer]

Im logged in and registered, but cant see any download link for v3. Can anyone else? or is just me

[Sin]

Im logged in and registered, but cant see any download link for v3

The latest version has just been uploaded - Have Fun :lol:

[FredS]

I dont think its been uploaded yet.

XDA-Developers went down over the weekend.


Freds

[henrylim]

i download the file from the first post and installed it onto my XDAII
but now when i put the xdaii into the cradle the screen says something about activesync being the old version ?
does anyone know where i can get an updated version of it to get it to sync again ?

Get it from MS 2003 Mobile website. Just search for ActiveSync. It will allow you to download the version 3.7.1 software.

regards,
Henry

[foxnolds]

This is my version of SINs WM2003SE_AU_v3.zip

First of all I'd like to thank everybody for their efforts which finally allows the Himalaya devices to run WM2003SE.

I've personally installed ROM 2.06.00, ROM 2.02.t1, Radio 1.18.00 and Extended ROM 2.06.100a from information obtained here at XDA-DEVELOPERS.

As I have found conflicts with Commercial Applications and there are Applications in the supplied Extended ROMs I will not use (E.G. BlackBerry due to Running Costs), I've decided to cook my own Extended ROM...

I have looked at all WM2003SE Roms on this site including in no particular order, SIN, ZeroXtreme, DCS, Dr.Stein, Skuld and Mystery_Man. This is my choice from that bunch so far.. today...

Note that in my Config.txt file, the touch panel is not disabled at all.
I have since "Touched" all the CAB files so their minimum support version is 4.21 so the "display maybe incorrect" warning dialog no longer appears.


As per SINs notes..

This english version of WM2003SE is only for the Australian or Asian Pacific model O2 XDA II.

:!: NOTE: It is supplied as is. Use it at your own risk!!!
:idea: TIP: First backup your data and settings using either ActiveSync, SDBackup, XBackup or better still, Sprite Backup and follow the instructions in the ROM backup folder.

To install:

1. Download the attached WM2003SE_AU_v3_#(option).exe and extract it to a new folder - Note these are self extracting RAR archives.
2. Insert your O2 XDA II into it's USB cradle and confirm that a sucessful USB connection has been made with your PC
3. Run HimaUpgradeUt.exe and follow the onscreen prompts.

Details:

The ROM image file (nk.nbf) version is: 2.06.00WWE or 2.02.t1WWE (ver 2.21.1088 build 14132)
The Radio image file (Radio_.nbf) version is: 1.18.00
The Extended ROM image file (ms_.nbf) version is: 2.06.100a


The Extended ROM contains the following:

Touch Panel Enable
Set Button Lock
ExtROM Unlocker
ExtROM Viewer
Camera 2.5
Album 2.5
Video MMS 2.1
CallerID 1.17
ClearVue 2.4.381a
XCPUScalar 2.85
ClearType Tuner
IntelliDialer 1.0 - with BlueSkin
MMS Composer 1.6.0.8
Socket WiFi 1.08 - supports SanDisk
Version info + O2 splash, Dialer skins & theme
Australian Carriers - Optus, Telstra & Vodafone
Asian Pacific Carriers - 1O1O, 3-DUALBAND, AIS, Celcom, ChungHwa Telecom, DiGi, DTAC, Globe, IM3, M1, Maxis, New World Mobility, One2Free, ProXL, Satelindo, SingTel, Smart, SmarTone, StarHub, StarHub Prepaid, Sunday & Telkomsel

Sadly, no room for the following from the previous Ver2:
Removed - Blackberry Client & GPRS Monitor

VERSION 3 FIXES:
MMS Compatibility. Restored original "non Outlook integrated" MMS Composer version 1.6.0.8

Available in separate download is an archive of CAB files found in other cooked ROMs I did not include..

Removed CABs for various reasons - usually due to conflict with better commercial products...
Battery_Task_Icon.cab - Conflicts with SPB Pocket Plus v2.2
Contacts.0.9.cab - According to ocp WinCE CAB Manager, this is corrupt
DialerSkin_Landscap_091104.sa.CAB - Not required
DialerSkin_Portrait_091104.sa.CAB - Not Required
InDialSkin_Blue.CAB - Made this but didn't replace the indialer* files SO I patched IntelliDialer_1.0.cab instead
IntelliDialer_1.0.cab - Original version pre-patch
IntelliPad_1.0.cab - Conflicts with PhatWare CalliGrapher v7.4
Java_MIDlet_Manager_1.5.11.cab - Possible conflict with NetFront v3.1 with JV-Lite2
MS_Reader_2.3.cab - Why boot with this? Just add it later..
Sandisk_WiFi_3.01.cab - Replaced with better Socket version that also supports SanDisk SDIO WiFi card
Truefax2_2.08.cab - Only install it if you are going to use it!
UltraProfiler_1.5.cab - I use Zen Phone and OOZ Cell Profiler...


KNOWN ISSUES:
BlueTooth Headset Today Status disappears - This was someones bright idea to only show the Today BlueTooth Headset status when BlueTooth itself is enabled - See Icon on bottom right corner. As a result, when BlueTooth is off, the BlueTooth Today screen Headset status can't make up its mind whether to display or not...
No Windows Media Player version 10 - yet. This is in the Chinese v2.20 release but I have not seen it anywhere else.
MS IE Browser is still at v4.0 - I have read that some Pocket_PC releases are at version 5.0! I personally need version 5.0 as a minimum for Sites I use.
Delays/Hang on reboot - included a pre-configured XCPUScalar 2.85 which seems to stop the hangs when auto-run.

:idea: NOTE: if you wish to test only the ROM & Radio, simply delete the ms_.nbf file.

:arrow: INFO: The zip file includes all 3 image files with backup & editing tools + instructions. (Only logged in registered users will see the download link below)

I know SIN will be releasing another version soon so if you are impatient, try one of these... :wink:
Oops, SIN has just posted his as I write! :roll:

[Greg-C]

Sin. well done. 10 out of 10. Even a newbie to upgrading XDAII was able to follow your guidance successfully...

On question though, where did "Explorer" go?

[Sin]

where did "Explorer" go?

They've limited it to 7 apps on your start menu popup (I usually untick help & tick "file explorer") otherwise it's under programs.

[mmemme]

can i use it for imate?

[johnk1973]

Any chance of a UK version? I've been waiting for this for ages and i'm gutted i can't use this version in the UK!! :? :?

[jaykumarr]

Hi Foxnolds.
i have already installed 2003SE.
rom ver :2.06.wwe
date 06/14/04
radio 1.14.000
ext rom 2.06.100a
i would just like to know that if i update it with only
WM2003SE _AU_V3_1ROM ONLY EXE.
will the xda 2 upgrade to 2003SE_v3_1.
or do i have to flash it again fully.
and can you tell me who's rom to flash it with your's or sin's.
which is better.
thanks in advance.

[Anonymous]

Hi guys, just wondering if anyone else has noted that the bluetooth quality is quite a bit lower with this ROM. Callers are complaining they can't hear me properly.

[dchalmers]

Hi Sin,

Great work- thanks. I have installed your latest version (SIN.AU.v3) and all works well except for the blackberry client. I have been unable to establish a connection and get the blackberry icon that indictaes that "another application has been using the device radio"

Any ideas on a work around?

Thanks

[ardarby]

Sin. well done. 10 out of 10. Even a newbie to upgrading XDAII was able to follow your guidance successfully...Good for you, but this 'newbie' is having trouble getting past A/S Backup.

I don't have enough fingers to:
Hold Power Button + Directional Pad + Reset Button and put my XDA II into its USB cradle.

Where am I supposed to be when I run "romupdate.exe"?

How do I connect to port: \\.\WCEUSBSH001 ??

What screen am I in when I type:
d2s 80000000 02000000. etc. ?

I guess, if I can't decipher the instructions, I shouldn't be contemplating the upgrade, but it is a tad frustrating not having a single clue. :cry:

[Sin]

Perhaps this will help:

For more details and screenshots, please view: http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=62

[ardarby]

Thanks Sin,

Will check it out shortly.

[Sin]

I've updated this post (http://forum.xda-developers.com/viewtopic.php?p=71272&highlight=#71272) with information on how to merge the 2.02.t1WWE ROM with the 2.06.00WWE ROM, if anyone's interested :wink:

[xlr8]

Hi there, I gave this a go on my new XDA II and I am having a problem with the upload util "HimaUpgradeUt.exe".

Basically it IDs the XDA ok and brings up the dialogue to flash and seems to erase the ROM before the software locks up and says "there has been a problem".

I must then exit the software and use my backup ROM stored on my SD card to restore the XDA back to original.

My XDA II came with boot-loader v1.06, could this be a part of the problem?

Other version info:
ROM: 1.66.00WWE
ExtROM: 1.66.165
Radio 1.08
ActiveSync v 3.7.1 on PC

BTW - I have a very nice IIs here on my desk - I would say the major upgrade of it over the II is probably the SE OS!!!

[recrem]

I have bootloader version 1.06, and have re-flashed mine a few times now. I only use the cradle with power attached, and use a fast WinXP machine. Some people have had troubles using various Sync cables, and slower machines...

Don't know how to help yet, but my set-up works great...

Recrem...

[dinoignacio]

thaks Sin. This works perfectly.
One thing i miss from my old version is access to running programs. I used to have an icon that i place in my start menu for it. now the only way yo get to it is to go to settings and click memory then, go to the running programs tab.
can you put this feature back?

thanks for the great work!\

Dino

[xlr8]

I have bootloader version 1.06, and have re-flashed mine a few times now. I only use the cradle with power attached, and use a fast WinXP machine. Some people have had troubles using various Sync cables, and slower machines...

Don't know how to help yet, but my set-up works great...

Recrem...
I am running WinXPon a XP3200+ PC with 512MB RAM, O2 Cradle on power as well.

I assume that HimaUpgradeUt.exe requires Active Sync to be running as it wont run without it installed.

I will try it again on a new PC with a clean install and see how that goes. :(

[henrylim]

I have bootloader version 1.06, and have re-flashed mine a few times now. I only use the cradle with power attached, and use a fast WinXP machine. Some people have had troubles using various Sync cables, and slower machines...

Don't know how to help yet, but my set-up works great...

Recrem...
I am running WinXPon a XP3200+ PC with 512MB RAM, O2 Cradle on power as well.

I assume that HimaUpgradeUt.exe requires Active Sync to be running as it wont run without it installed.

I will try it again on a new PC with a clean install and see how that goes. :(


No, HimaUpgradeUt requires the desktop to recognize that the USB connection to the device is active, that's all. It runs its own connections to the device during upgrading.

I suppose a by-benefit of ActiveSync is that it provides the drivers to assure of a successful USB connection to the device, that's all.

Perhaps you can post the sequence of events and errors that you've observed here so the gurus might shed some light on how you might resolve them. :)

[jaykumarr]

hi sin i have flashed my xda2
with you're latest rom 2003SE_AU_v3.
and i love it bravo dude gr8 work.
the only problem i face is that when my blue tooth is on i can hear the conversation from the phone too & the quality of the blue tooth is not so good as it use'd to be before.
people can't hear me well they say my voice is too low otherwise its great.
and one more thing i wanted to ask you sin.
what will i get if i merge the 2.02 & 2.06?
any difference?
cus i love you're 2003SE_AU_V3.
great work .
and thank you for the rom.

[Sin]

the only problem i face is that when my blue tooth is on i can hear the conversation from the phone too & the quality of the blue tooth is not so good as it use'd to be before.
people can't hear me well they say my voice is too low otherwise its great.

It seems to vary on the BT devices that you pair with. I use a HBH-35 Headset and a Logitech diNovo hub and have not experienced the above with the Headset.

The outcome shows that there are differences in the way MS have implemented Bluetooth across the 3 different base versions found in this forum.

In 2.02t1WWE, HandsFree profile is available when a new device is paired but as you've noted, it's still buggy depending on the device. Also BT ActiveSync is blocked when the HandsFree icon is visible. Cleartype is fuzzy.

In 2.06.00WWE, Instead of HandsFree, you are offered a Headset Profile which functions much the same but without the ability to redial the last caller through the headset. It is stable and works simultaneously with ActiveSync. ClearType looks good.

In 2.20.00CHS (Chinese Version) HandsFree is again available however I've noticed that the BT activesync profile doesn't work with my diNovo hub. ClearType looks good.

what will i get if i merge the 2.02 & 2.06?
any difference?

2.06.00.WWE suffers from hangs/delays during reboot and doesn't offer HandsFree as a profile. By merging a backup of 2.02.t1WWE over a running 2.06.00WWE using activesync, these problems are eliminated.

You'll still be running the core components of 2.06.00WWE because ActiveSync won't overwrite the files running in ROM, but the Registry will be merged and system files will be overwritten to produce what seems to be a faster operating system that doesn't have hangs/delays on reboot and has a BT HandsFree mode that co-exists well with BT ActiveSync.

My merge is running well beyond my expectations for almost a week now, No speaker Duality or any problems to report.

I even tried it with Pocket Bluetooth Tools (http://www.bluetooth.jazztel.es/guide_e.html) but found that I didn't need it.

Give the merge a go - it worked for me and I hope you have the same experience. :wink:

[kinglee]

Can you post your registry so that I can compare with my current 2.06 registry.

You can use Resco Registry for that.
http://www.resco-net.com/explorer_dwn.asp

[Sin]

Can you post your registry so that I can compare with my current 2.06 registry

Now that I've installed all of my software and applied personal settings, I'm a bit hesitant to do that.

Next time I do a clean merge, I will.


EDIT: Oh Bugger it, I'll downgrade it again without Extended ROM and post backups and registries from each version.

[Looking Glass]

I've been following this threat since the beginning, and I have actually installed this ROM and ExtROM. (original AU one)
I would like to know if the last ExtROM has solved somehow the Hands free profile problems, specially the "stereo" effect.

Has anyone tried yet?

:?:

[Sin]

Can you post your registry so that I can compare with my current 2.06 registry.

I've downgraded the ROM to 2.02.t1WWE and installed with Radio 1.18 but no EXT ROM.

I left the default settings:

Timezone: GMT-8 Pacific US
Regional Settings: English (United States)
Device name: Pocket_PC

Setup an ActiveSync Partnership and ran a full backup. I then installed PHM Regedit and exported the registry.

---------------------------------------

I then reflashed with the ROM to 2.06.00WWE and installed with Radio 1.18 but no EXT ROM.

I left the default settings:

Timezone: GMT-8 Pacific US
Regional Settings: English (United States)
Device name: Pocket_PC

Setup an ActiveSync Partnership and ran a full backup. I then installed PHM Regedit and exported the registry.

---------------------------------------

Finally, I restored the original backup from 2.02.t1WWE, reset the device and used file explorer to delete the following links from the "Windows\Startup":

tFlashMan
NFlashman
CFlashman
AFlashman

Setup another ActiveSync Partnership and ran full backup, installed PHM Regedit and exported the registry.

---------------------------------------

I've tested it with my HBH-35 Headset and get HandsFree.
I've tested it with BT ActiveSync and also works 1st time.

It has perfect ClearType and no reboot Hangs/Delays. Nice & Fast! :wink:

:arrow: Here's a zip file containing all 3 backups and registries + PHM RegEdit:
:idea: Find me the file & registry differences and I'll incorporate it into an Extended ROM

[Looking Glass]

Would you please confirm that this solution solved the dual mic/speaker problem with headsets and carkits?

Everything I read about points out that hands free profile is implemented BUT INCORRECTLY working. This could be the reason why only CHS 2.20 version is considered "official" while there is not an WWE offficial version yet.

:?:

[Sin]

Would you please confirm that this solution solved the dual mic/speaker problem with headsets and carkits?

I can confirm that the Duality problem doesn't exist on the HBH-35.

I can also confirm that with the "Official Release" 2.20CHS (Chinese Version), the BT ActiveSync profile doesn't work with my diNovo hub.

[skuld]

@Sin: Just a question, after restoring the backup from 2.02.t1 to 2.06, does your SMS folder disappear from Messaging? Because mine does! :shock:

[Sin]

On Tools=>Manage Folders, I only see the folders for my Email Account but when I tap the Inbox > drop down arrow, I see folders for my Email account, then Outlook Email and finally Text Messages.

Each have:

Deleted Items
Drafts
Inbox
Outbox
Sent Items

Under accounts, there's:

Text Messages
Outlook E-Mail
My Email Account

[rmercado]

Pleazzze..!

May i know the difference between the WM2003SE_AU_v3_1.exe and WM2003SE_AU_v3_2.exe



Cheers & Good Work,

[Sin]

I'm not sure if foxnolds (http://forum.xda-developers.com/profile.php?mode=viewprofile&u=9048), (the author of those files) has seen your post - for further clarification perhaps send him a pm (http://forum.xda-developers.com/privmsg.php?mode=post&u=9048)

I'd say that his Extended ROM is more his own hard work rather than mine, but here's his file descriptions anyway:

WM2003SE_AU_v3_1.exe

Version based upon OS 2.06 and SINs Extended_ROM.
The ROM image file (nk.nbf) version is: 2.06.00WWE (ver 2.21.1088 build 14132)
The Radio image file (Radio_.nbf) version is: 1.18.00
The Extended ROM image file (ms_.nbf) version is: 2.06.100a

WM2003SE_AU_v3_2.exe

Version based upon 2.02 and SINs Extended_ROM
(nk.nbf) version is: 2.02.t1WWE (ver 2.21.1088 build 14132)
Radio image file (Radio_.nbf) version is: 1.18.00
The Extended ROM image file (ms_.nbf) version is: 2.06.100a

[rmercado]

I've downgraded the ROM to 2.02.t1WWE and installed with Radio 1.18 but no EXT ROM.

I left the default settings:

Timezone: GMT-8 Pacific US
Regional Settings: English (United States)
Device name: Pocket_PC

Setup an ActiveSync Partnership and ran a full backup. I then installed PHM Regedit and exported the registry.

---------------------------------------

I then reflashed with the ROM to 2.06.00WWE and installed with Radio 1.18 but no EXT ROM.

I left the default settings:

Timezone: GMT-8 Pacific US
Regional Settings: English (United States)
Device name: Pocket_PC

Setup an ActiveSync Partnership and ran a full backup. I then installed PHM Regedit and exported the registry.

---------------------------------------

Finally, I restored the original backup from 2.02.t1WWE, reset the device and used file explorer to delete the following links from the "Windows\Startup":

tFlashMan
NFlashman
CFlashman
AFlashman

Setup another ActiveSync Partnership and ran full backup, installed PHM Regedit and exported the registry.



SIN
Based from the steps you provided, pardon me if i miss something, when did you install/flash the EXT ROM???

Cheers Mate...

[Sin]

pardon me if i miss something, when did you install/flash the EXT ROM?

Haha, you did miss something - if you re-read the top part of my post, you'll notice that it includes a quote:

Can you post your registry so that I can compare with my current 2.06 registry.

... it was a reply for those wanting to compare registries & files in the base ROM during a merge.

[van]

Thank Sin

The combined ROM is working
:D :D :D

[henrylim]

Can you post your registry so that I can compare with my current 2.06 registry

Now that I've installed all of my software and applied personal settings, I'm a bit hesitant to do that.

Next time I do a clean merge, I will.

EDIT: Oh Bugger it, I'll downgrade it again without Extended ROM and post backups and registries from each version.

Thanks the effort. :D

Insofar, I've check through the HKLM settings and found these differences:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se ttings]
"IgnoreExternal"=dword:00000001


On 2.06, it has these extra settings (missing from 2.02):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2\Services\0000111e-0000-1000-8000-00805f9b34fb]
"sdprecord"=hex:36,00,4E,36,00,4B,09,00,00,0A,00,01,00,01,09, 00,01,35,06,19,11,1E,19,\
12,03,09,00,04,35,0C,35,03,19,01,00,35,05,19,00,03 ,08,02,09,00,09,35,08,35,\
06,19,11,1E,09,01,00,09,01,00,25,0F,48,61,6E,64,73 ,2D,46,72,65,65,20,75,6E,\
69,74,09,03,11,09,00,1C
"name"="Handsfree"
"channel"=dword:00610002


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2\Services\00001108-0000-1000-8000-00805f9b34fb]
"sdprecord"=hex:36,00,45,36,00,42,09,00,00,0A,00,01,00,00,09, 00,01,35,06,19,11,08,19,\
12,03,09,00,04,35,0C,35,03,19,01,00,35,05,19,00,03 ,08,01,09,00,09,35,08,35,\
06,19,11,08,09,01,00,09,01,00,25,07,48,65,61,64,73 ,65,74,09,03,02,28,01
"name"="Headset"
"channel"=dword:00650001



This allows me to enable my BT Handsfree on HBH65 BT headset without the dual problem.

Only thing is, I couldn't test if it can do voice command. The MS Voice Command software is not working too well on my 2.06 ROM. Any takers?

[kinglee]

Yes, the dual audio appearing on the BT headset and Handset is solved.
However my BT headset tends to power off whenever I press the HangUP virtual button or the hard button.

I do not use MS Voice Command and hence not able to test it out. I am sticking to Headset mode since my BT seems to work best in this mode.

Was wondering, what are the key differences between Headset and Handsfree mode in regards to a BT device?

[foxnolds]

Hi Foxnolds.
i have already installed 2003SE.
rom ver :2.06.wwe
date 06/14/04
radio 1.14.000
ext rom 2.06.100a
i would just like to know that if i update it with only
WM2003SE _AU_V3_1ROM ONLY EXE.
will the xda 2 upgrade to 2003SE_v3_1.
or do i have to flash it again fully.
and can you tell me who's rom to flash it with your's or sin's.
which is better.
thanks in advance.

The ROM_ONLY technique is not an Upgrade Flash method.
The step is to enable EXT_ROM and view it from ActiveSync Explorer.
You delete it current contents then copy over the new ROM-ONLY contents to Phones EXT_ROM.

After performing a backup first, you simply do a Hard Reset to invoke new Extended_Rom applications then optionaly restore from backup.

Having said all that, you are probably better going with Sins combined ROM now. I rebuilt my XDA II over the weekend with even less applications in the Extended_ROM and using 2.06 O/S. This works best for me any my applications, your milage may vary.

[henrylim]

Hi all,

[RE-EDITED - FOURTH TIME]

NOTE: 2nd version of 2.06 registry patch is replaced as there are entries that cause network errors for ActiveSync after cold reset. The entries are now removed for the second version.
Note: 3rd version of 2.06 registry patch is uploaded to fix a couple of issues with Rasbook and BT handsfree. This version has been tested for a 3-4 days now with good results.

Thanks to SIN and LookingGlass, I've compared all the key differences between 2.02.t1WWE and 2.06.00WWE registry file.

I've included
(a) 2.02.t1WWE registry differences with 2.06.00WWE in the attached zipped file 2.02.t1 Reg CAB.zip. It contains more registry entries, as I've
included 2.02 registry entries that will overwrite 2.06 registry entries.

WARNING: Install this CAB only in 2.06.00WWE ROM only!!!


(b) 2.06.00WWE registry differences with 2.02.t1WWE in the attached zipped file 2.06.00 Reg CAB.zip. It only contain 2.06.00WWE registry entries that are missing from 2.02.t1WWE registry.

WARNING: Install this CAB only in 2.02.t1WWE ROM only!!!


I've used WinCE CAB Manager to create the CAB file, and have used the Original CAB structure with support for StrongARM/XScale. You will find that the installation will give you warnings about incompatibility. Ignore the warnings and proceed.


The usual disclaimer applies. Make sure you've backup your files before you install this..blah...blah....use it at your own risks.

Also, please share your experiences!

[kinglee]

Nice work Henry.

Is there a reason to leave out the HandsFreeProfileOn registry?

[xlr8]

Just an update to my scenario. I tried the ROM update on a fresh Win2k SP4/IE6 Sempron 2600+ 512MB PC and it is now updating the ROM as I type. :D

No, HimaUpgradeUt requires the desktop to recognize that the USB connection to the device is active, that's all. It runs its own connections to the device during upgrading.

I suppose a by-benefit of ActiveSync is that it provides the drivers to assure of a successful USB connection to the device, that's all.

Perhaps you can post the sequence of events and errors that you've observed here so the gurus might shed some light on how you might resolve them. :)
On a side note. The HimaUpgradeUT.exe program does seem to require ActiveSync to be installed as it popped up an DLL call error when used without ActiveSync. I installed AS v3.7.1 and the message goes away and the util then works.

[kinglee]

Just an update to my scenario. I tried the ROM update on a fresh Win2k SP4/IE6 Sempron 2600+ 512MB PC and it is now updating the ROM as I type. :D

On a side note. The HimaUpgradeUT.exe program does seem to require ActiveSync to be installed as it popped up an DLL call error when used without ActiveSync. I installed AS v3.7.1 and the message goes away and the util then works.

You are right, the windows USB-PPC/XDA drivers is bundled within ActiveSync.

[henrylim]

Nice work Henry.

Is there a reason to leave out the HandsFreeProfileOn registry?

Since both ROM is not official, I would consider that both ROM are released as beta for fine-tuning and testing all the settings....

I want to check the 2.20CHS registry and compare the differences as well. Reports on 2.20CHS has been favourable, but I don't have the
registry. Can you re-post the 2.20CHS registry in .REG format?

I am also checking the Magician/IMATE-JAM registry & ROM to see if their implementation is superior to the current ROMs we are playing with.

Well, too bad I don't have so much time on my hand each day....I'll try my best...

[henrylim]

On a side note. The HimaUpgradeUT.exe program does seem to require ActiveSync to be installed as it popped up an DLL call error when used without ActiveSync. I installed AS v3.7.1 and the message goes away and the util then works.

Good that it works for you then. :D

[Sin]

On 2.06.00WWE all that's required to enable headset mode is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

... on 2.06.00WWE can disable the headset mic on some models (tested on HBH-35 here)

Would someone else on a freshly installed 2.06.00WWE (not merged) give this a quick try:

[henrylim]

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

... on 2.06.00WWE can disable the headset mic on some models (tested on HBH-35 here)

Would someone else on a freshly installed 2.06.00WWE (not merged) give this a quick try:

I see...good try. :D

Perhaps we need pple with different BT headsets to try as well? It didn't happen with my old HBH-65.

BTW, the handsfreeprofileon didn't require an dword entry? Does that your specific dword value entry is recognize by default?

[Rabia]

can someone list how much of the handsfree is their with this technique, in other words does it:

1) Show the ID caller number on the BT headset screen?
2) Doest it call using Voice command?
3) does it at least route voice to the HeadSet when button pressed to custome make that Voice Command available

in other words is it like the ipaq 6315 BT stack?

thanks in advanced

[Duan]

Ok I realize this is slightly off topic, but I figured that the ppl in this topic is likely to know the answer so here goes.

Does anyone know of an app that records the filles installed and the changes made to the registry when one installes apps on the PPC?

Thanx

[JPS]

http://www.geocities.com/s_k_s_k_s_kru/util.html#ss (System Snapshot) program allows you to create a file which holds the entire registry as well as file and database listings to allow for easy comparisons.

[Sin]

BTW, the handsfreeprofileon didn't require an dword entry? Does that your specific dword value entry is recognize by default?

The dword is just a null value so that the registry path can be successfully imported into the cab. :wink:

[rmercado]

I did SIN's version on the first page about merging two versions.

after the last flash and Cold Reset I received this message.. "KSE FAX Tools was not Installed successfuly. Please run setup again"

...

After the restore of the original Full Back-up I received this:::

::: Dont know if it is an error or a normal process..

What shall I do... Skip or Retry..?

[Urinalcake]

Hey i have to thank you for this rom.. it all works great except for one small thing :P

I realise you have picked up something wrong with the Bluetooth profiles thing on the today screen, but my Today screen has "841900098 Active Tasks" (theres actually only 1) and under that it sayas "7755656445 High Priority".. And it just has some of the Today screen tasks, etc overlaping some calendar entries.....

thanks for your help in advance

[[Krueger]Dr.Stein]

On 2.06.00WWE all that's required to enable headset mode is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

... on 2.06.00WWE can disable the headset mic on some models (tested on HBH-35 here)

Would someone else on a freshly installed 2.06.00WWE (not merged) give this a quick try:

I get the first part Bro but may I know what the second regkey is for please and how do I create it?

[jaykumarr]

Hi.
Sin I Just Had A Look At The xda 2 mini today.
and it had window media player_10.
was wondering if you could post the (mini's) rom.
and will it work in xda2?
i had seen in this forum
a link to the xda2 mini's rom
but can i flash it to the xda2?
thanks in advance

[Sin]

I did SIN's version on the first page about merging two versions. After the last flash and Cold Reset I received this message.. "KSE FAX Tools was not Installed successfuly. Please run setup again". After the restore of the original Full Back-up I received (retry or skip files)... Dont know if it is an error or a normal process..

What shall I do... Skip or Retry..?

Run the TrueFax setup again (manually from your unhidden Extended ROM using file explorer) and if the error persists, try using "add/remove" from settings for TrueFax before re-installing.

With the "retry or skip files" message when restoring your backup, if you haven't already - skip is fine, those files obviously exist and are in use.

...my Today screen has "841900098 Active Tasks" (theres actually only 1) and under that it sayas "7755656445 High Priority".. And it just has some of the Today screen tasks, etc overlaping some calendar entries.....

It sounds like an activesync problem. Download & install the latest version from MS (3.7.1 (Build 4034).

Delete the old partnership & create a new one with no items initially ticked for synchronisation. Slowly introduce items - Calendar, Contacts, Favorites, Notes & Tasks and see how you go.

Dr.Stein]I get the first part Bro but may I know what the second regkey is for please and how do I create it?

The second part is unique to the 2.02.t1WWE ROM's BT registry. When I import it to the 2.06.00WWE ROM, it deactivates my HBH-35 headset's mike and enables only the XDA's mike when in HandsFree mode.

To create and import any of these reg key's, create an empty text file & add:

REGEDIT4

to the first line, then cut & paste the reg key below it. When complete, simply save the text file with a .reg extension and exectute on the XDA.

Another method is to use a WinCE cab file editor & import the registry key directly into it.

was wondering if you could post the (mini's) rom.
and will it work in xda2?

I haven't had time to download or play with the mini's ROM but it may be worth looking into :wink:

[kinglee]

To create and import any of these reg key's, create an empty text file & add:

REGEDIT4

to the first line, then cut & paste the reg key below it. When complete, simply save the text file with a .reg extension and exectute on the XDA.


Does the reg file method work? I had tried and all I get is that there is no application associated with the file...

[Sin]

Sorry, you're right - I keep forgetting that I have PHM RegEdit installed.

[skuld]

Hi all,

[RE-EDITED - THIRD TIME]

Thanks to SIN and LookingGlass, I've compared all the key differences between 2.02.t1WWE and 2.06.00WWE registry file.

I've included
(a) 2.02.t1WWE registry differences with 2.06.00WWE in the attached zipped file 2.02.t1 Reg CAB.zip. It contains more registry entries, as I've
included 2.02 registry entries that will overwrite 2.06 registry entries.

WARNING: Install this CAB only in 2.06.00WWE ROM only!!!


(b) 2.06.00WWE registry differences with 2.02.t1WWE in the attached zipped file 2.06.00 Reg CAB.zip. It only contain 2.06.00WWE registry entries that are missing from 2.02.t1WWE registry.

WARNING: Install this CAB only in 2.02.t1WWE ROM only!!!


I've used WinCE CAB Manager to create the CAB file, and have used the Original CAB structure with support for StrongARM/XScale. You will find that the installation will give you warnings about incompatibility. Ignore the warnings and proceed.


The usual disclaimer applies. Make sure you've backup your files before you install this..blah...blah....use it at your own risks.

Also, please share your experiences!

:arrow: NOTE: 2.02tl registry CAB is replace as there are entries that cause network errors for ActiveSync after cold reset. The entries are now removed for the second version.

Could you provide a list of entries contained in each cab? Although installing the cab makes it easier to import the entries, knowing what is added to the registry allows easy removal later on and test which entries works for the handsfree profile. Thanks in advance.

[skuld]

Insofar, I've check through the HKLM settings and found these differences:

...

On 2.06, it has these extra settings (missing from 2.02):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2\Services\0000111e-0000-1000-8000-00805f9b34fb]
"sdprecord"=hex:36,00,4E,36,00,4B,09,00,00,0A,00,01,00,01,09, 00,01,35,06,19,11,1E,19,\
12,03,09,00,04,35,0C,35,03,19,01,00,35,05,19,00,03 ,08,02,09,00,09,35,08,35,\
06,19,11,1E,09,01,00,09,01,00,25,0F,48,61,6E,64,73 ,2D,46,72,65,65,20,75,6E,\
69,74,09,03,11,09,00,1C
"name"="Handsfree"
"channel"=dword:00610002


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2\Services\00001108-0000-1000-8000-00805f9b34fb]
"sdprecord"=hex:36,00,45,36,00,42,09,00,00,0A,00,01,00,00,09, 00,01,35,06,19,11,08,19,\
12,03,09,00,04,35,0C,35,03,19,01,00,35,05,19,00,03 ,08,01,09,00,09,35,08,35,\
06,19,11,08,09,01,00,09,01,00,25,07,48,65,61,64,73 ,65,74,09,03,02,28,01
"name"="Headset"
"channel"=dword:00650001



This allows me to enable my BT Handsfree on HBH65 BT headset without the dual problem.

Only thing is, I couldn't test if it can do voice command. The MS Voice Command software is not working too well on my 2.06 ROM. Any takers?

I think these extra settings from 2.06 are just registry entries for the bonded headset device?

[EDIT] I did a double check and these entries describe the profiles supported by the bonded headset device ...

If you check, I am sure you will have these keys as well

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\De vice\0006c5096ea2\Services] [End EDIT]

[Rabia]

i don't seem to be able to change my rom back after i installed the chinies rom it gives me error country id although i changed it to CDL, anythought?

[chris_khho]

On 2.06.00WWE all that's required to enable headset mode is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

... on 2.06.00WWE can disable the headset mic on some models (tested on HBH-35 here)

Would someone else on a freshly installed 2.06.00WWE (not merged) give this a quick try:

I tried that file on a 2.06.00WWE (not merged) rom but not fresh (with applications).
The connection is great but the listener on the other side keep complaining that she can only hear my voice occasionally.
Is it only my problem??

[Rabia]

On 2.06.00WWE all that's required to enable headset mode is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

now do i actually put the quotation marks ""? like in "Headset" or not?

[Sin]

The connection is great but the listener on the other side keep complaining that she can only hear my voice occasionally.
Is it only my problem??

On 2.06.00WWE, when you add the following reg key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

...it enables the built in BT HandsFree profile along with the already existent BT Headset profile, so when you re- pair your Headset (after adding the reg key), you'll notice that you are offered both profiles.

I suggest that you only choose either BT HandsFree or BT Headset when re- pairing and then test which works better with your mic.

Some people have reported no problems using BT HandsFree on 2.06.00WWE but I feel that it depends on which headset you combine it with.

The BT HandsFree profile disables the mic on my HBH-35 but the BT Headset profile works fine. The only difference (that would've been of use to me), was the ability to redial the last known caller using the Headset in BT HandsFree mode.

I've also noticed that if you choose both BT HandsFree & BT Headset profiles at the same time, it confuses the poor XDA II and it delays the ring to the Headset. In my opinion, only choose one or the other!

NOTE: The new Sin.AU.v3.5_ExtROM uploaded today on the first page will automatically add the reg key for 2.06.00WWE

[chris_khho]

The connection is great but the listener on the other side keep complaining that she can only hear my voice occasionally.
Is it only my problem??

On 2.06.00WWE, when you add the following reg key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

...it enables the built in BT HandsFree profile along with the already existent BT Headset profile, so when you re- pair your Headset (after adding the reg key), you'll notice that you are offered both profiles.

I suggest that you only choose either BT HandsFree or BT Headset when re- pairing and then test which works better with your mic.

Some people have reported no problems using BT HandsFree on 2.06.00WWE but I feel that it depends on which headset you combine it with.

The BT HandsFree profile disables the mic on my HBH-35 but the BT Headset profile works fine. The only difference (that would've been of use to me), was the ability to redial the last known caller using the Headset in BT HandsFree mode.

I've also noticed that if you choose both BT HandsFree & BT Headset profiles at the same time, it confuses the poor XDA II and it delays the ring to the Headset. In my opinion, only choose one or the other!

NOTE: The new Sin.AU.v3.5_ExtROM uploaded today on the first page will automatically add the reg key for 2.06.00WWE

Sorry Sin,
I am still confused.
I checked the registry and they are there already.
I disabled the headset profile in the today's screen but the mic is still not working with my o2 (i-tech) bt headset.
Thanks for your reply anyway.

[Sin]

No that won't work - turning off headset on the today screen won't improve Handsfree compatibility.

Assuming that you added the reg key successfully to your 2.06.00WWE version, delete your headset from the XDA II and then re- pair it.

If HandsFree mode kills your headset mic, answer "no" when offered HandsFree during pairing & "yes" to Headset instead.

[chris_khho]

Hi Sin,

I just installed your version 3.5 and the compatibility problem of headset / handsfree still existed.

I pressed "no" to handsfree but there is no more pop-up to ask for headset.

Also, do I need to change the registry with your new ext rom?

Thanks again.

[madcat]

Hi Sin,

I was wondering if you can help me me with a problem I have with your new WM2003SE ROMs and SmartST (for Navman GPS) ? I have updated the device using your ROMs (tried both V2 and V3) and basically this is what happens:
- install ROM ok
- install SmartST ok (I do get a message saying the software may not work as it was for an older version of the O/S)
- pair up with the 4400 ok
- run SmartST
After the 1st run, it runs ok. I can set up my favourites, etc. Then I soft rebooted and tried it again but after loading maps, it gets to the disclaimer screen and when I tap "I Agree", it just freezes and all I can do is press the phone hangup button to get back to the OS and kill it in "Running Programs" or have to reboot.

[Sin]

I pressed "no" to handsfree but there is no more pop-up to ask for headset.

Also, do I need to change the registry with your new ext rom?

Hi Chris,

Sorry about the late reply (Christmas silly season here), there's a few things you can try.

When I pair my HBH-35 I get 2 popups, one is HandsFree and the other is Headset - it gives me a choice but perhaps Headset mode on 2.06.00WWE doesn't recognise your device correctly.

To Test:

This is only if Handsfree mode in 2.06.00WWE ends up disabling your headset mic and if when re- pairing you do not get a second pop-up offering Headset profile:

Use the supplied RegEdit in the new Extended ROM to remove the following RegKey & DWord:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
"headset"=dword:00000000

Then restart your XDA II and re- pair once again. This time, you won't be offered HandsFree and should only have Headset as a choice.

Have you tried other Base ROMS with your Headset?

2.02.t1WWE only has HandsFree (Though I have mic problems using my HBH-35 with it) and a few people claim that HandsFree works well in 2.20.00CHS and the English translated one.

Hope This Helps

SmartST (for Navman GPS)

Hi Madcat,

Again - sorry for the late reply. I see that you've had a little help on MTekk
http://www.mtekk.com.au/forums/viewtopic.php?t=4687

Hope you find a better solution soon :?

[dr.Bram]

i live in indonesia....well which one of the version is the best for my xda II right now i've done upgrade to version:
ROM version : 2.06.00WWE
ROM date: 06/14/04
radio version : 1.18.00
protocol version : 1337.38
ext ROM : 2.06.100a
until right now i don't have any complain but when i want to sync with pc xda told me i must upgrade my active synch..and many software from last xda told if u install this software aybe not run properly..
i want suggest from many senior in this thing which software i must download from this site , 2.06 / 2.02/ or something else i want to use it for my self...
i can't load midi files to my ringtones, and must set up the mms config manually please advice from all of u guys...

[chris_khho]

Hi Sin,

Finally, I refreshed my rom back to 2.06.00 without merging this time.

The headset profile come back and there are 2 pop-ups. However the headset pop-up was covered by the handsfree pop-up so that you need to go to Today to find the headset pop-up first before you pressed "no" to the headset profile. Now the mic of my BT headset worked again.

Thanks anyway for your help. Merry X'mas and happy new year!!!

Cheers,

[Anonymous]

I only fell over this thread last night and successfully upgraded to with Sins ext ROM.

Please excuse my ignorance but apart from the landscape view what are the advantages that the second edition will give me?

[jamiesteo2323]

Hi Sin,

I am using HBh 660, and few question to ask..

1. with the rom 2.02t, i am able to see caller's Id on my hbh660 screen, but in 2.06 rom it doenst show caller id.

2. Facing the same problems as Chris_khho, i am unable to have headset pop-up after mersing the 2 roms (2.06 + 2.02t). Do u have any solution for this?
the only way for me to have 2 pop-up selection is just flash the 2.06 rom without mersing. but if i wanna to mersing together, i just left handfree as the pop-up selection. I have read through this post for more than 20 times, i still have no idea to solve..~ hehhe..~ guys pls help ...

anyways, HAPPY X'DAY WO~~~~
HO~~ HO..HO~~~~

[Anonymous]

thanks

[rmercado]

:arrow: INFO: The first zip file contains only an Extended ROM with instructions. Please choose a Base ROM from either of the two other zip files, which also contain backup & editing tools + instructions. (Only logged in registered users will see the download links below)

SIN,

I did your mergimg method using your old ROM and it was successfuly upgraded. It was amazing, seems i am using the Official SE EN for XDA II.

When I saw your version v3.5 I was tempted to re-flash my XDA again following the same procedure as what I did in merging (I added the Sin.AU.v3.5_ExtROM in both folder with base ROM).

And the result:

Some new pgm are now installed in the unit.
The display of EXT ROM version = BLANK
During re-boot I encountered message saying that the ROM version is not compatible.
I noticed that UltraProfiler was not installed
... in short the EXT ROM was not successfuly installed.

Please need some advice to resolve these...!

[theerachai]

Have been read and tried with the registry edit to turn handfree on in my 2.06 rom ,Yes it work

but what is the different between bluetooth headset and bluetooth handfree.

[Rabia]

any suggestion on to how to fix the mic problem on 2.02t? i like the BT of this rom over the 2.06 but the mic is being a problem any fixes?

[rexwrx]

sin and everyone else...

i've got e same BT headset problem-- the listener on e other side of e phone cannot hear me speak clearly. and i've realised that i can still use my o2 to talk TOGETHER with my BT...so it seems to be HEADSET profile.

i'm using jabra 250 bt.

i've merged e two roms together.

question....> do i unmerge the ROM and install only 2.6? if so how do I unmerge?

> any other solution with this problem??
thanks!

[dr_kaan]

Hi all,

I have the dutch 1.72wwe rom and want to try the so called "merged" rom procedure, however i have a question: Will this rom support my Turkish operator, Turkcell?

Thanks

[Sin]

Facing the same problems as Chris_khho, i am unable to have headset pop-up after mersing the 2 roms (2.06 + 2.02t). Do u have any solution for this?

Sure, Follow these steps to re-enable "Headset" mode after merging 2.02 onto 2.06 (http://forum.xda-developers.com/viewtopic.php?p=71272&highlight=#71272):

1. Under your bluetooth icon, in the "Mode" tab - untick both "Turn on Bluetooth" & "Make this device discoverable to other devices"

2. Still under your bluetooth icon, delete any paired devices from the "Devices" tab

3. If you've installed the Sin.AU.v3.5 Extended ROM, you'll have a new shortcut to RegEdit. If not - I've attached RegEdit below - so please install it.

4. Start Regedit and find the following key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth]

Hold down your stylus over the word "Bluetooth" until the popup menu appears, then choose "Delete"

5. Download and run the "BT_Patch_for_Merge_on_2.06.cab" (attached below RegEdit) and reboot your XDA II

Finally, please reacquaint yourself with the advice outlined here (http://forum.xda-developers.com/viewtopic.php?p=75930&highlight=#75930) & here (http://forum.xda-developers.com/viewtopic.php?p=76412&highlight=#76412)

P.S It's nice having a merged OS, no hangs/delays, good looking cleartype, no probs with BT ActiveSync & headset mic now works (even if it's just because I chose Headset mode for my HBH-35) :wink:

[chris_khho]

Hi Sin,

Is it normal that when I tried to backup from the ActiveSync program, at the end there are some errors for several programs? I just pressed "skip" them.

I did some changes in the ext-rom to load some program and network providers.

Cheers,

[Sin]

Hi Chris,

Yes it happens when particular files are in use and can't be copied during the activesync backup. If "Running Programs" shows any program other than ActiveSync in the list, it may be worth stopping those & trying the backup again.

But I'm sure you'll be fine :D

[Rabia]

guys i have merged both roms & the result is my mic being disabled, i can't take the phone 2feet away from me since i still have to use the phones mic & not the Head set, any fixes for this problem?

[Sin]

guys i have merged both roms & the result is my mic being disabled, i can't take the phone 2feet away from me since i still have to use the phones mic & not the Head set, any fixes for this problem?

yes, read this post (http://forum.xda-developers.com/viewtopic.php?p=77208&highlight=#77208) (2 back from yours) :lol:

[Rabia]

ok i did & now i get both options, if i choose yes to handsfree & no to headset i lose mic, if i choose yes to both i get nothing it keeps going crazy but sound don't get directed to bt & if i choose headset i lose bt also

[Sin]

if i choose headset i lose bt

Not sure if I completely follow - try unpairing the headset (i.e delete from devices tab), restart your XDA II and then re- pair but only choose "HeadSet Profile" (no HandsFree)

Does your mic work now?

[Rabia]

this is it, if i choose no to handsfree & yes to heaset it don't work, i hear no sound in my bt heaset :cry:

[Sin]

Did you follow step 4 before applying the patch?

4. Start Regedit and find the following key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth]

Then Hold down your stylus over the word "Bluetooth" until the popup menu appears, then choose "Delete"

If not, applying the patch will give you a "Headset Profile" but if you've not deleted the above key first, it will not work correctly. (mic still disables)

If even after first deleting and then applying the patch you have no luck, may I ask has your BT Headset's mic worked under either English version of WM2003SE?

At the moment you have a combination of 2.02.t1WWE which natively only has HandsFree mode and 2.06.00WWE which natively only has Headset mode.

If neither version of WM2003SE (when not merged) has allowed your headset mic to work in the past, I doubt that merging them will help.

In my case, I was fortunate that my HBH-35's mic worked under headset mode on 2.06.00WWE (didn't under 2.02.t1WWE) and also now works with the merge of the two using the patch.

Sorry I can't be of any more help.

[Rabia]

well in my situation my bt Headset never worked with 2.02 because mic was disabled but with 2.06 on heaset profile it works fine :?: weired :?:

[Sin]

weired :?:

Very - but don't give up, there's bound to be more up to date versions of the base ROM sooner or later :wink:

[tumtum]

Hi Sin,

I follow your Merge ROM method. It's work well no hang on soft reset and work faster and better but still bluetooth problem.

I make an experiment

First, I use only Rom2.02t1 and pair with bluetooth headset and due to ROM 2.02 it can set only HandsfreeProfile. Then my bluetooth not work. no sound on it's mic. and Make full backup with activesync

Second, I do hard-reset and make full backup (i think i can't use your backup file because i use my custom Ext ROM.)

Third ,I flash my device to ROM2.06 and then pair my bluetooth. it's work well in headset profile. I do hard-reset again and restore firstly with ROM2.02 with Bluetooth in fisrt. Then I start to use my bluetooth. My bluetooth not work.

Fourth, I do hard reset and restore with ROM2.02 without any bluetooth pairing before. After complete restoring, I pair my bluetooth and again my bluetooth not work with HandsFreeProfile.

Fifth, I do Hard-reset again and Now, I'm in ROM2.06. I use resco-regostry to export my reg from \bluetooth. I restore from 2.02without b;uetooth. I use registry editor to delete \bluetooth and import bluetooth reg from ROM2.06. Now my bluetooth workwell with Headset Profile.

But something doesn't correct, everytime I turn on my device the blue-light blinking without bluetooth turn-on. Did you found that problem ?

After I search in myxda website I found that XDA2 cannot use as Handfree bluetooth Profile.
----------------------------------------------------------------------------------
this quote from Product FAQ
----------------------------------------------------------------------------------
Category: How-to-use (bluetooth)

Can I put my bluetooth headset to handsfree ?

The Xda II supports bluetooth headset but not hands free. This means you cannot voice activate commands hands free with your bluetooth headset, even if the headset supports hands free. The Xda II does not support hands free bluetooth profile.
----------------------------------------------------------------------------------
on this page, http://www.myxda.com/support/XdaII/template/ProductFaq.vm?faq_id=364&type=faq&id=3#cat
----------------------------------------------------------------------------------

All is satisfy but only one thing that makes me annoyed is the blinking of blue light everytime when I turn my device on.

Thank for all who contribute in this project of bluetooth.

[superperry]

Hi all,

[RE-EDITED - FOURTH TIME]

NOTE: 2nd version of 2.06 registry patch is replaced as there are entries that cause network errors for ActiveSync after cold reset. The entries are now removed for the second version.
Note: 3rd version of 2.06 registry patch is uploaded to fix a couple of issues with Rasbook and BT handsfree. This version has been tested for a 3-4 days now with good results.

Thanks to SIN and LookingGlass, I've compared all the key differences between 2.02.t1WWE and 2.06.00WWE registry file.

I've included
(a) 2.02.t1WWE registry differences with 2.06.00WWE in the attached zipped file 2.02.t1 Reg CAB.zip. It contains more registry entries, as I've
included 2.02 registry entries that will overwrite 2.06 registry entries.

WARNING: Install this CAB only in 2.06.00WWE ROM only!!!


The usual disclaimer applies. Make sure you've backup your files before you install this..blah...blah....use it at your own risks.

Also, please share your experiences!


Do I still need to merge 2.02 and 2.06 ROM to make my XDA/MDA II, boot faster and no hang-up? Or just install this CAB registry and no need to do merge ROM? Does this registry CAB you made replace that merge process?

Thanks!

[henrylim]

Do I still need to merge 2.02 and 2.06 ROM to make my XDA/MDA II, boot faster and no hang-up? Or just install this CAB registry and no need to do merge ROM? Does this registry CAB you made replace that merge process?

Thanks!

I don't know about others, but it works for me. My 1st version had an erroneous RASBook entry that kills ActiveSync, but that has been rectified and the CAB file has been revised.

This cab file enables handsfreeprofile for 2.06 as well, so if you don't need it, you might want to delete the registry entry using PHM Reg Editor or Resco Registry.

Insofar, I've tried BT ActiveSync, Headset, Handsfree. I don't seen to experience the issues faced by others with pure 2.06 ROM anymore for the past few weeks.

Let me know if you do face any problems.

[Sin]

SUMMARY

Thanks to the testing by all the good people in this thread, we now have a method to utilise all the working features in the two English ROM's.


No hangs or delays on boot
Perfect Cleartype
Working non-integrated MMS
Working Headset & optional Handsfree profiles
Working BT ActiveSync
Excellent Speed...

I've constantly updated my first 2 posts in this thread to solve problems as they have arisen. The steps to achieve this have been refined but there's still room for error during implementation. Windows Media 10 & IE5 haven't surfaced, nor has any newer versions of the base ROM.

I couldn't be happier with my current version (merged OS), everything works better than expected - it does feel like an official release! :shock:

So I think it's safe to say that unless a new version or major problems are discovered in the existing procedures outlined in my first 2 posts, it's worthwhile creating a single step installation package that puts it all into ROM early in the new year.

Your thoughts?

P.S See you all Next Year! 8)

[[Krueger]Dr.Stein]

I don't know about others, but it works for me. My 1st version had an erroneous RASBook entry that kills ActiveSync, but that has been rectified and the CAB file has been revised.

This cab file enables handsfreeprofile for 2.06 as well, so if you don't need it, you might want to delete the registry entry using PHM Reg Editor or Resco Registry.

Insofar, I've tried BT ActiveSync, Headset, Handsfree. I don't seen to experience the issues faced by others with pure 2.06 ROM anymore for the past few weeks.

Let me know if you do face any problems.

Bro are you saying you have solved the HandsFree profile issue (no more stereo effect and working headset mic)? How did you do it?


No hangs or delays on boot
Perfect Cleartype
Working non-integrated MMS
Working Headset & optional Handsfree profiles
Working BT ActiveSync
Excellent Speed...

I got all that except a working headset mic under HandsFree profile Bro - how did you get it to work?

TIA

[Anonymous]

Bro are you saying you have solved the HandsFree profile issue (no more stereo effect and working headset mic)? How did you do it?


No hangs or delays on boot
Perfect Cleartype
Working non-integrated MMS
Working Headset & optional Handsfree profiles
Working BT ActiveSync
Excellent Speed...

I got all that except a working headset mic under HandsFree profile Bro - how did you get it to work?

TIA[/quote]

I had a similar issue with the BT headset. I did manage to get it fixed quite simply..I paired my BT250 headset. It asked if i wish to use handsfree...i said no. From here i exited out of the pairing back to the main screen. On the main screen where it said "bluetooth headset mode is disabled" i just clicked on it to enable it. Problem solved.


Sin.......awesome if you could merge the 2 ROMs into 1 to make it a one step process. Might be worth waiting a couple weeks as i am sure that WM10 and IE will surface once everyone is over their Xmas & New Years celebrations.

[Anonymous]

@Sin: Just a question, after restoring the backup from 2.02.t1 to 2.06, does your SMS folder disappear from Messaging? Because mine does! :shock:

I've this problem too!
If I go to Inbox I see only Outlook Email...And the arrow doesn't show me anything.. :(

[superperry]

Do I still need to merge 2.02 and 2.06 ROM to make my XDA/MDA II, boot faster and no hang-up? Or just install this CAB registry and no need to do merge ROM? Does this registry CAB you made replace that merge process?

Thanks!

I don't know about others, but it works for me. My 1st version had an erroneous RASBook entry that kills ActiveSync, but that has been rectified and the CAB file has been revised.

This cab file enables handsfreeprofile for 2.06 as well, so if you don't need it, you might want to delete the registry entry using PHM Reg Editor or Resco Registry.

Insofar, I've tried BT ActiveSync, Headset, Handsfree. I don't seen to experience the issues faced by others with pure 2.06 ROM anymore for the past few weeks.

Let me know if you do face any problems.

@ Henry;

So far my MDA-II with 2.06 ROM with your 2.02*v3.cab and Sin*.3.5 Extended_ROM (customized) works well with my BT-GPS and BT-headset (Bluespoon AX on headset profile). But I experience that I had to install BTPSKeyupdate_003.exe to get my headset work properly. Haven't tried BT-Activesync yet. I don't have any hang-up but my boot-up time when soft-reset cost me around 20-25 secs (is this about right or too long?).

@ Sin;

I tried your Sin*.3.5 Extended_ROM; customized it and it works great with 2.06 ROM (mysteryman) and 1.08 Radio. My MMS is integrated in my inbox and don't have any problem so far. I am using MMS_v2.0.0.13*.cab from my old 1.72 ROM, so far so good. ;)

Thanks to all who made it possible running SE on our Himalaya.

Have a Happy New Year!

Cheers,

[[Krueger]Dr.Stein]

I had a similar issue with the BT headset. I did manage to get it fixed quite simply..I paired my BT250 headset. It asked if i wish to use handsfree...i said no. From here i exited out of the pairing back to the main screen. On the main screen where it said "bluetooth headset mode is disabled" i just clicked on it to enable it. Problem solved.

That's not solving the HandsFree profile problem. That's merely disabling it and enabling the HeadSet profile which already works fine.

[FlashGordon1]

Hi,

I've upgrade ROM per orginal post from Sin on Page 1 as a combined ROM.

Loaded 2.02.t1WWE along with Sin.AU.v3.5 first and then 2.06.00WWE without having Sin.AU.v3.5 in the directory with HimaUpgradeUt.exe.

Machine sometimes hangs and cannot get out of it without a hard rest. This occurred prior to loading any software.

I've reloaded and am now afraid to do a soft reset!

Have also found that activesync sometimes does not sync. May have solved this by macking sure that there are no programs running on XDA prior to syncing.

I'm not running any BT handsets so don't need this feature.

Can anyone tell me a solution or if I do a backup via say activesync and then do a hard reset and just load 2.02.t1WWE along with Sin.AU.v3.5 and then restore will it work or the backup will not be compatible.

I backed up my ROM from original machine using romupdate.exe but when new rom problems occured I tried to do a restore of old rom but got a error so cannot go back now.

Device info is:
ROM 2.06.00WWE date 14/6/04
Radio 1.18.00
Protocol 1337.38
ExtROM Sn.AU.v3.5


Thanks Gordon
PS: Sin Thanks for you great efforts in the ROM and all your comments in this topic. Have been folloing it from start.

PS: I'm a novice (very much so) ay tweaking ROMS so would appreciate laymans jargon.

[p711y]

You are very Smart Sin, thank you... I have loaded 2.02.t1WWE along with Sin.AU.v3.5 and then I got both sounds coming from my PDA and headSet, I also lost mic as well.. I belive many people having same problem (I used Nokia HS-3W), I have read this topic and tried many different ROMs as you've posted, I found out ROM 2.02.t1WWE has better bluetooth connection, I've loaded ROM 2.06WWE before and I use vmobilesoftware to send contact list from my XDAII to Nokia 8910 to make a phone call via bluetooth http://www.vmobilesoftware.com/bluetooth_dialer.htm without sucess and then I go back to 2.02.t1WWE works fine to me.. in my situation what is best solution to solve my headset's problem??

SUMMARY

Thanks to the testing by all the good people in this thread, we now have a method to utilise all the working features in the two English ROM's.


No hangs or delays on boot
Perfect Cleartype
Working non-integrated MMS
Working Headset & optional Handsfree profiles
Working BT ActiveSync
Excellent Speed...

I've constantly updated my first 2 posts in this thread to solve problems as they have arisen. The steps to achieve this have been refined but there's still room for error during implementation. Windows Media 10 & IE5 haven't surfaced, nor has any newer versions of the base ROM.

I couldn't be happier with my current version (merged OS), everything works better than expected - it does feel like an official release! :shock:

So I think it's safe to say that unless a new version or major problems are discovered in the existing procedures outlined in my first 2 posts, it's worthwhile creating a single step installation package that puts it all into ROM early in the new year.

Your thoughts?

P.S See you all Next Year! 8)

[Sin]

The single step installation package that puts the merge into ROM and supplies a preconfigured OS is coming along nicely.

Sorry I don't have a chance to answer any questions - been working around the clock on this in hope of having it completed & ready to upload for the weekend!

Catcha in a few days :wink:

[henrylim]

The single step installation package that puts the merge into ROM and supplies a preconfigured OS is coming along nicely.

Sorry I don't have a chance to answer any questions - been working around the clock on this in hope of having it completed & ready to upload for the weekend!

Catcha in a few days :wink:

Great work! go go go....

hehehe...but i'm greedy...any chance of getting the SDIO drivers and WMP updated? :twisted:

[chris_khho]

Sin,

That's great. Thanks a lot.

Just want to ask since I am already using your merged ROM, any benefits to use the new ROM.....

The drawback I can see is to re-install everything after the hard reset...

Thanks very much anyway.

Cheers,

[madbart]

Awesome......lets home is hits this weekend as i am back to work on monday! :lol: :lol:

[GoldenHands]

when Flashing the 2.02, backing up etc
flahing 2.06, restoring 2.02... etc

did anyone do the above and soft reset before the ext rom autoexecuted of the 2.06? Then after merging... and occasionally hard resetting the device do you have still the merge rom's or do you have just the 2.06 rom?

[jaykumarr]

yeah babe go go go waiting for the merged rom.
desperately.
keep up the good work bud.

[noviur]

I have MPX300 on my hands and I was told that it has built-in voice-dialing functionality.

If somebody can direct be how to port this from the existing device - I agree to contribute my time for it.

Paul

my mistatke - i have mpx300

go to
http://forum.xda-developers.com/viewtopic.php?p=79439#79439
for detailes and already extracted files.

[steverae]

Hi guys

I have tried the BT test patch on a standard 2.06 rom and it gave me hands free mode (which didn't work) but diasbled headset mode

i only get the choice to enable hands free now

gonna try the merge tonight... see what happens

EDIT *

Having removed the reg key for handsfree, my mic thing now works...

gonna wait for the single step install packge from sin.

SIN > Will we be able to change the country and operator codes in this single install package ?

[timpulse]

hi everybody, i had done the merged rom and everything works perfectly except for one small thing the word completion is not working, i dont know about you guys. I tried going to start>setting>Input then at the word completion tab everything is checked i dont know where to fix this problem, anyone can help?

[henrylim]

hi everybody, i had done the merged rom and everything works perfectly except for one small thing the word completion is not working, i dont know about you guys. I tried going to start>setting>Input then at the word completion tab everything is checked i dont know where to fix this problem, anyone can help?

strange. its working for me. I typed an message in SMS, and there are pop-up word suggestion.

What is not working for you and where is it not working?

[timpulse]

everywhere, in the compose new sms it wont auto complete so its hard to look for contacts, in pocket word its also not auto completing i wonder where the problem could be, but i manage to follow SIN's merge ROM guide step by step.

[madcat]

everywhere, in the compose new sms it wont auto complete so its hard to look for contacts, in pocket word its also not auto completing i wonder where the problem could be, but i manage to follow SIN's merge ROM guide step by step.

I find that on rare occasions autocomplete will just stop working, but for me this is solved by just doing a soft reset. I think I also has this once or twice on my 1.60 ROM.

[GeeZuZz]

Could someone please answere a few simple questions?

1. Does this only work on australian XDA? How can i find out where mine is from? (it's not sold in my country - i bought it used from someone who bought it in an other country)

2. Is the first posts updated? (should i follow the guide - or do i need more info from the rest of the thread?)

3. Could this solve my XDA's problem with reading my SD card? I have a 1GB corsair SD card it doesn't recognize... :(

[pole_vaulter1]

GeeZuZz -
1st question: The upgrade should work on any Himalaya. it is only the network settings and possible additional cell provider software that will differ. You will need to manually set your operator details (GPRS, Mailbox, Etc.) outside of Australia. To find out what your Country ID is copy the attached file to your pocket pc, Run it, and copy the DeviceData.txt file generated under Windows to your desktop to open. For a better description follow this link http://forum.xda-developers.com/viewtopic.php?t=12101
2nd Question: The first page is updated but I normally at least browse through the posts to see if anyone has any additional suggestions other than a file change.
3rd Question: Sorry can't help but hopefully someone with a 1GB card can help (mine's in the mail :D )
Travis

[GeeZuZz]

Thanks for your reply.

U S B 3 2 1 . 0 3 . 0 0 U S A P H 1 0 O 2 A S I A W W E 1 . 0 3 . 4 3 1 . 0 5 . 1 4
I assume it's from USA?

[rmhtoh]

Hi All,
I have just upgrade to:
ROM version: 2.0600.WWE from Sin dated 06/14/04
Radio Version 1.18.00
Protocol version 1337.38
ExtROM version Sin.Merged.v1.0

Some problem and questions after upgrade:

1. When I add a new contact number, the country ID is (+425). How to change it to (+65)?

2. How can I add the Singapore Operator to the AutoConfig?

3. Can I just upgrade the ExtROM only? How?

4. How can I edit the ExtROM and load it back to the XDA||?

5. When I try to install Chinese software for SMS, i don't seem to be able to use pingyin.

Thanks in advance.
Ric

PS. Great job all.

[rmhtoh]

One more issue:
Don't seem to beable to see the CallerID display for incoming call. But in the missed call list, it show (123) 456-78. It should show 12345678 or +65 12345678

Thanks
Ric

[smoothunit]

rmhto

just change your regional setting and apply an area code if applicable

[Anonymous]

Thanks, SmoothUnit

[rmhtoh]

Hi SmoothUnit,
Caller ID issue solve. I load the ExtRom V3.1 with Singapore telco profile and it ok now. Only sometime it reset to default profile. But it ok if I do an Autoconfig again.
Thanks
Ric

[scarper]

Error 120: Country ID Error N-O-1-1-1

I get this error when I try to update using files from first post.

I had recently updated my Aussie O2 with 1.72.126 from DCS thread and even changed all codes to 02 and WWE etc but for some reason still gives me this error.

Any Ideas? Have I missed somthing?
Cheers

[rmhtoh]

Hi,
Just found out another problem. The contact list don't work properly, the tap #abc is in small cap and my contact name in big cap, example when I tap k to look for name. It goes all the way to the bottom. If I change the contact name to small cap, it work.
Any help to solve the issue?
Thanks
Ric

[hydronic]

Help please. I have followed Sins instructions and achieved a working system fo


ROM: Merged 2.02.t1WWE & 2.06.00WWE
Radio Version : 1.18.00
ExtROM version : Sin.Merged.v1.0

I have also deleted the registry Bluetooth settings with the intention of applying the "bt_patch_for_merge_on_2.06.cab". I have clicked on the link and downloaded a file called "000TOOLS.000".

Is this the correct file and if so what do I do with it"

Thanks

[psytech]

Facing the same problems as Chris_khho, i am unable to have headset pop-up after mersing the 2 roms (2.06 + 2.02t). Do u have any solution for this?

Sure, Follow these steps to re-enable "Headset" mode after merging 2.02 onto 2.06 (http://forum.xda-developers.com/viewtopic.php?p=71272&highlight=#71272):

1. Under your bluetooth icon, in the "Mode" tab - untick both "Turn on Bluetooth" & "Make this device discoverable to other devices"

2. Still under your bluetooth icon, delete any paired devices from the "Devices" tab

3. If you've installed the Sin.AU.v3.5 Extended ROM, you'll have a new shortcut to RegEdit. If not - I've attached RegEdit below - so please install it.

4. Start Regedit and find the following key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth]

Hold down your stylus over the word "Bluetooth" until the popup menu appears, then choose "Delete"

5. Download and run the "BT_Patch_for_Merge_on_2.06.cab" (attached below RegEdit) and reboot your XDA II

Finally, please reacquaint yourself with the advice outlined here (http://forum.xda-developers.com/viewtopic.php?p=75930&highlight=#75930) & here (http://forum.xda-developers.com/viewtopic.php?p=76412&highlight=#76412)

P.S It's nice having a merged OS, no hangs/delays, good looking cleartype, no probs with BT ActiveSync & headset mic now works (even if it's just because I chose Headset mode for my HBH-35) :wink:

i have tried both handsfree and headset but with handsfree the mic is disabled and with headset it just doesn't work, and ideas on how to fix this?
my i-tech bt headset worked fine before i upgraded to WM2003SE (using a merged rom)
please help me out guys i'm lost without my headset... had to go back to using my sony ericsson t630 till i solve this BT problem.
p.s.- pairing works fine

[Burnie]

The single step installation package that puts the merge into ROM and supplies a preconfigured OS is coming along nicely.

Sorry I don't have a chance to answer any questions - been working around the clock on this in hope of having it completed & ready to upload for the weekend!

Catcha in a few days :wink:

Hi Sin,

How have you gone with this single step installation??? I am turning blue holding my breath in anticipation!

Cheers, Burnie.

[snorbaard]

Error 120: Country ID Error N-O-1-1-1

I get this error when I try to update using files from first post.

I had recently updated my Aussie O2 with 1.72.126 from DCS thread and even changed all codes to 02 and WWE etc but for some reason still gives me this error.

Here's how I fixed it:
* First I checked my Devicedata.txt file (after using the Mysterman update, it had been set to O2, even though I have an i-mate).
* I downloaded the operatorupdate.bat file (found elsewhere on the site) and changed the .nbf files to O2.
* Then I ran the upgrade - was told I'm ready for the upgrade, and halfway through received a message that I'm using the wrong update. At this point I had a dead i-mate.
* Now I re-ran the operatorupdate.bat file, and changed the operator to CDL (code for i-mate), and tried the update application again.

Note: I *did* try to change the Operator by using the ER2003 edit utility, and this apparently didn't do it correctly. The batch file worked for me.

[Cyber-mate]

Download and extract either one of the attached Base ROM's (WM2003SE_AU_2.06.00WWE.zip or WM2003SE_AU_2.02.t1WWE.zip) to a folder on your PC.

Thanks Sin. My iMate couldn't be any faster :) The new ROM installed referred above is xtreamly stable, fast and bug-free (YET) :wink:

Pal, the OS suits my xda super well.
At least the hide n' seek BT icon on Today screen is no more there.

Regards.

[madbart]

Is there anyway that one of you guys would be able to post the single Blackberry 1.2.4.19 cab file.

I have recently upgraded to a Mini and cant seem to find the file anywhere else.

[srg]

You can get the individual cabs including the blackberry in this post http://forum.xda-developers.com/viewtopic.php?t=16916

[philbourne]

Any chance of a UK version? I've been waiting for this for ages and i'm gutted i can't use this version in the UK!! :? :?

Here here... I am a new user... may need to sell my headset on ebay...

[iandg]

Not sure what I'm doing wrong here. Searched high and low re-read page after page but I can't find "BT_Patch_for_Merge_on_2.06.cab". I have difficulty getting my BT Headset to work. Can answer and hear but the mic won't work. If any one can help?

Ian

Rom: 2.06.00WWE
Radio: 1.18.00
ExtROM: Sin.Merged.v2.0

[hello22y]

Hi Sin,

Finally, I refreshed my rom back to 2.06.00 without merging this time.

The headset profile come back and there are 2 pop-ups. However the headset pop-up was covered by the handsfree pop-up so that you need to go to Today to find the headset pop-up first before you pressed "no" to the headset profile. Now the mic of my BT headset worked again.

Thanks anyway for your help. Merry X'mas and happy new year!!!

Cheers,

Hey chris

i had the same problem when i installed 2.06.00. and i tried to do as you said... and it worked.

Good work Chris
and thanks a lot

[hello22y]

Facing the same problems as Chris_khho, i am unable to have headset pop-up after mersing the 2 roms (2.06 + 2.02t). Do u have any solution for this?

Sure, Follow these steps to re-enable "Headset" mode after merging 2.02 onto 2.06 (http://forum.xda-developers.com/viewtopic.php?p=71272&highlight=#71272):

1. Under your bluetooth icon, in the "Mode" tab - untick both "Turn on Bluetooth" & "Make this device discoverable to other devices"

2. Still under your bluetooth icon, delete any paired devices from the "Devices" tab

3. If you've installed the Sin.AU.v3.5 Extended ROM, you'll have a new shortcut to RegEdit. If not - I've attached RegEdit below - so please install it.

4. Start Regedit and find the following key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth]

Hold down your stylus over the word "Bluetooth" until the popup menu appears, then choose "Delete"

5. Download and run the "BT_Patch_for_Merge_on_2.06.cab" (attached below RegEdit) and reboot your XDA II

Finally, please reacquaint yourself with the advice outlined here (http://forum.xda-developers.com/viewtopic.php?p=75930&highlight=#75930) & here (http://forum.xda-developers.com/viewtopic.php?p=76412&highlight=#76412)

P.S It's nice having a merged OS, no hangs/delays, good looking cleartype, no probs with BT ActiveSync & headset mic now works (even if it's just because I chose Headset mode for my HBH-35) :wink:

i have tried both handsfree and headset but with handsfree the mic is disabled and with headset it just doesn't work, and ideas on how to fix this?
my i-tech bt headset worked fine before i upgraded to WM2003SE (using a merged rom)
please help me out guys i'm lost without my headset... had to go back to using my sony ericsson t630 till i solve this BT problem.
p.s.- pairing works fine

hi

it's very simple to make your headset mic work
all you have to do is:
pair you headset, click NO when you got Hands-free, but don't close the bluetooth window... now click Start, then Today. you'll see a message for Headset, so click YES

now go to Start, Settings, Today, Items
make sure that "Profile" is selected, so it can be at your desktop to enable or disable the headset.

Good luck

[iandg]

Thanks Hello, Here is my problem reading the instructions to get the BT headset working I used regedit and deleted the bluetooth so now I need to install the BT merge cab before I can follow your instructions. However, as per my original request the cab file is not easy to find. Hopefully, you can assist in this matter first.

Ian

[latino]

thanks for the info and the upgrade went find just one problem thou now the user id on the phone is a bit stuffed

Before I upgraded the incoming calls would appear fine as ( )0423685374

but after the upgrade they appear as (042) 368-5374

How can I fix this problem please let me know

[hello22y]

Thanks Hello, Here is my problem reading the instructions to get the BT headset working I used regedit and deleted the bluetooth so now I need to install the BT merge cab before I can follow your instructions. However, as per my original request the cab file is not easy to find. Hopefully, you can assist in this matter first.

Ian

Hi Ian
you are talking about merge, but i didn't merge anything.
i had rom 1.72, i did upgrade to 2.06, no merging or editing the registry necesary...

just do the following:
pair your headset, enter the pin, click finish
when you are asked "Would you like to designate JABRA 250 as a hands-free device?" click No
don't close the bluetooth settings... click on Start Menu, then click Today
you'll get another pop-up message: "This bluetooth device supports headset profile, would you like to set it as your bluetooth headset?".
click Yes twice.

but please make sure that you have "Bluetooth headset mode is enabled" in your Today Screen.
if you don't have it, click on Start Menu, Settings, Today, Items and select "Profile" so you can enable or disable your bluetooth headset.

Good luck

George

[hello22y]

Thanks Hello, Here is my problem reading the instructions to get the BT headset working I used regedit and deleted the bluetooth so now I need to install the BT merge cab before I can follow your instructions. However, as per my original request the cab file is not easy to find. Hopefully, you can assist in this matter first.

Ian

Hi Ian
you are talking about merge, but i didn't merge anything.
i had rom 1.72, i did upgrade to 2.06, no merging or editing the registry necesary...

just do the following:
pair your headset, enter the pin, click finish
when you are asked "Would you like to designate JABRA 250 as a hands-free device?" click No
don't close the bluetooth settings... click on Start Menu, then click Today
you'll get another pop-up message: "This bluetooth device supports headset profile, would you like to set it as your bluetooth headset?".
click Yes twice.

but please make sure that you have "Bluetooth headset mode is enabled" in your Today Screen.
if you don't have it, click on Start Menu, Settings, Today, Items and select "Profile" so you can enable or disable your bluetooth headset.

Good luck

George

[iandg]

Hi George, (nice to know your name)
I appreciate your replies and have no doubt that this will solve my problem. However, I have one problem to solve first. When reading the earlier post one of the steps was to use regedit and remove the bluetooth command from the registry. I did this (stupid, I know, esp. if you don't have all the tools on hand) and now I first need to either restore and install the BT_Merge.cab. That is why I keep coming back to where can I find this file. Because at this time I have absolutely no bluetooth at all.

thanks
Ian

[hello22y]

Hi George, (nice to know your name)
I appreciate your replies and have no doubt that this will solve my problem. However, I have one problem to solve first. When reading the earlier post one of the steps was to use regedit and remove the bluetooth command from the registry. I did this (stupid, I know, esp. if you don't have all the tools on hand) and now I first need to either restore and install the BT_Merge.cab. That is why I keep coming back to where can I find this file. Because at this time I have absolutely no bluetooth at all.

thanks
Ian

Hi Ian

i'm not that expert. but i think if you do a Hard Reset, the registry will return to default, and the bluetooth will be back. if no, why don't you reinstall the rom (2.06.00) for sure it will be back

cya

George

[bla321]

thanks. wondering if anyone knows if this update will work on an Axim X5 device...

[lpsi2000]

Incredible job by Sin, thus far this ROM has been working like a charm for me.

I was using Magneto for a couple of days then I decided to switch back to WM2k3SE.

Thanks a million Sin.

[KT]

hi buddy...

firstly, million thanx for the amazing rom u provided... really enjoyed the wm2003se experience on an xdaII, now am a little jacked...

am buying a xdaIIs(black ppc), which already has a preinstalled wm2003se.... and wanna get rid of my xdaII, but my vendor wont touch ir unless i give him how its supposed to be, with the original o2 wm2003 rom.
now, i know its possible to do this via himupgrade utility itself, all i wanna know is where can i find a original wm2003 (not SE) ROM.

pls help.... anybody... pls pls.... if one of u xdaii users did back up ur original rom, i'd be highly obliged if u could upload or gimme url....

thanx all...

thanx SIN

adios n take care...

PS : wats the deal with wm2005, not to be found for download anywhere... do tell me where i can find. once my xdaII's' comes, i'd like to put 2005 on it...

MANY MANY THANX FOR READING... pls help in any manner possible...

[ccrrazzzy]

http://forum.xda-developers.com/viewtopic.php?p=108696#108696

[yousri]

we come to know from previous question & a proped reply how to remove to O2 sign from the top of the screen, this was realy great , now how to remove the date & time which appear next to the speaker sgin at the top of the screen , any one can solve this PPPPPLLLLLLLSSSSSS
Thanks

[lbctech]

thanks. wondering if anyone knows if this update will work on an Axim X5 device...

Yes, I am really new to all of this, and I would appreciate it if I could know if this works with an axim x5 ppc with WM2003 (not SE of course)

[somnath]

My device is xda IIs . Old version is wm 2003 se.First my device hang problem. Then i tried ROM UPGRADE 2005. UPGRADING is successful .Then after some time again my device is hang. Then i tried soft reset and hard reset at that time the screen shows strips and device booting problem.please give me solution. THANKS

[somnath]

PLEASE post me OS 2003 SE for XDA II s