yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] 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://xdaforums.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)
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] 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!
[MDA II, XDA II, 2060 ROM Development] Sin:
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?
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] Sin:
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).
[MDA II, XDA II, 2060 ROM Development] angry_shot:
ignore that last one - i don't think it has a password ;-)
[MDA II, XDA II, 2060 ROM Development] Demon:
It doesn't recognize the password for ms_.nbf

Any idea?
[MDA II, XDA II, 2060 ROM Development] 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 ?
[MDA II, XDA II, 2060 ROM Development] Believer:
Im logged in and registered, but cant see any download link for v3. Can anyone else? or is just me
[MDA II, XDA II, 2060 ROM Development] Sin:
The latest version has just been uploaded - Have Fun :lol:
[MDA II, XDA II, 2060 ROM Development] FredS:
I dont think its been uploaded yet.

XDA-Developers went down over the weekend.

Freds
[MDA II, XDA II, 2060 ROM Development] henrylim:
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
[MDA II, XDA II, 2060 ROM Development] Greg-C:
Awesome

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?
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: Awesome

They've limited it to 7 apps on your start menu popup (I usually untick help & tick "file explorer") otherwise it's under programs.
[MDA II, XDA II, 2060 ROM Development] mmemme:
can i use it for imate?

can i use it for imate?
[MDA II, XDA II, 2060 ROM Development] 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!! :? :?
[MDA II, XDA II, 2060 ROM Development] jaykumarr:
To Foxholds.

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.
[MDA II, XDA II, 2060 ROM Development] :
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.
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] ardarby:
Re: Awesome

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:
[MDA II, XDA II, 2060 ROM Development] Sin:
Perhaps this will help:

For more details and screenshots, please view: http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=62
[MDA II, XDA II, 2060 ROM Development] ardarby:
Thanks Sin,

Will check it out shortly.
[MDA II, XDA II, 2060 ROM Development] Sin:
Merging ROM's

I've updated this post with information on how to merge the 2.02.t1WWE ROM with the 2.06.00WWE ROM, if anyone's interested :wink:
[MDA II, XDA II, 2060 ROM Development] 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!!!
[MDA II, XDA II, 2060 ROM Development] 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...
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] xlr8:
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. :(
[MDA II, XDA II, 2060 ROM Development] henrylim:
ActiveSync not really required....

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. :)
[MDA II, XDA II, 2060 ROM Development] jaykumarr:
great work sin

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.
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: great work sin

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.

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 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:
[MDA II, XDA II, 2060 ROM Development] kinglee:
Post your Registry.

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
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: Post your 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.
[MDA II, XDA II, 2060 ROM Development] Looking Glass:
BT behaviour?

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?

:?:
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: Post your 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
[MDA II, XDA II, 2060 ROM Development] Looking Glass:
"Stereo"?

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.

:?:
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: "Stereo"?

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.
[MDA II, XDA II, 2060 ROM Development] 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:
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] rmercado:
What is the Difference

Pleazzze..!

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

Cheers & Good Work,
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: What is the Difference

I'm not sure if foxnolds, (the author of those files) has seen your post - for further clarification perhaps send him a pm

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
[MDA II, XDA II, 2060 ROM Development] rmercado:
Re: Post your Registry.

SIN

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

Cheers Mate...
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: Post your Registry.

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

... it was a reply for those wanting to compare registries & files in the base ROM during a merge.
[MDA II, XDA II, 2060 ROM Development] van:
Combined ROM

Thank Sin

The combined ROM is working

:D :D :D
[MDA II, XDA II, 2060 ROM Development] henrylim:
Re: Post your Registry.

Thanks the effort. :D

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]

"BTAudioModule"="OEMExtDll.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Settings]

"IgnoreExternal"=dword:00000001

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Device\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\Device\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?
[MDA II, XDA II, 2060 ROM Development] 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?
[MDA II, XDA II, 2060 ROM Development] foxnolds:
Re: To Foxholds.

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.
[MDA II, XDA II, 2060 ROM Development] henrylim:
The 2.02.t1WWE and 2.06.00WWE REG cab file-Merry Christmas!

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!
[MDA II, XDA II, 2060 ROM Development] kinglee:
Nice work Henry.

Is there a reason to leave out the HandsFreeProfileOn registry?
[MDA II, XDA II, 2060 ROM Development] xlr8:
Re: ActiveSync not really required....

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.
[MDA II, XDA II, 2060 ROM Development] kinglee:
Re: ActiveSync not really required....

You are right, the windows USB-PPC/XDA drivers is bundled within ActiveSync.
[MDA II, XDA II, 2060 ROM Development] henrylim:
Perhaps it was all a mistake...

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...
[MDA II, XDA II, 2060 ROM Development] henrylim:
Re: ActiveSync not really required....

Good that it works for you then. :D
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: ActiveSync not really required....

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]

"headset"=dword:00000000

adding the audio gateway:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]

"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:
[MDA II, XDA II, 2060 ROM Development] henrylim:
Re: ActiveSync not really required....

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?
[MDA II, XDA II, 2060 ROM Development] 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
[MDA II, XDA II, 2060 ROM Development] Duan:
Registry and file installation monitor.

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
[MDA II, XDA II, 2060 ROM Development] 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.
[MDA II, XDA II, 2060 ROM Development] Sin:
Re: ActiveSync not really required....

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