This post is intended to save those who are experiencing the country code error on a Siemens SX66 / Cingular Wireless device the 5 hours of headache it took me to figure out how to upgrade to the latest ROM available directly from Siemens (1.33.110).
1.) Download this file.
http://communications.siemens.com/c...1774_rArNrNrNrN_prodId:76051,00.html#Firmware
2.) This in an exe, but DON'T run it immediately. It is an installshield package - open it with Winzip or Winrar and extract it to a folder of your choosing.
3.) In that folder, you will find several nbf files, a few exes, and a file named RUU.conf.
4.) In RUU.conf you will find the following:
[PLATFORM]=667685
[RADIO_TYPE]=1
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=1
5.) Add this line:
[CHECKCEID_TYPE]=1
6.) Save the file. Make sure your unit is connected to the USB cradle, is fully charged, and is on. Run BaUpgradeUt.exe out of the folder you're working in. You'll see that on the first run, you don't get the country code error. It will show you the old version you're upgrading away from, and the new version you're upgrading to. Proceed with the upgrade.
7.) You'll see the device go blank as it goes into bootloader mode. A few seconds later, you'll see the country code error. THAT'S OK - DON'T PANIC. Just close the application, and restart BaUpgradeUt.exe again.
8.) You should experience a successful ROM upgrade at this point - you're done. Hard reset the unit per the instructions and you're good to go.
9.) I can be contacted at josh [AT] pinwheeltech [DOT] com.
Hello,
I try to update my Blue Angel to new 1.40 ROM from post “New Rom Qtec BA_WWE_14000_147_11200_Ship” I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf files to my setings:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB009 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
and I miss some warning message, then I run BaUpgradeUt.exe and update ROM successfully.
But when I restart after update I see:
No GSM
D 1.40.00 WWE
My Device Information is:
ROM version: 1.40.00 WWE
ROM date: 03/10/05
Radio version: [empty]
Protocol version: [empty]
ExtROM version: [empty]
Now I can't load any kind of ROM, always I see message:
ERROR 120: COUNTRY ID ERROR : No-No-42-42-42 (last three numbers change)
I already changed the RUU.conf ([CHECKCEID_TYPE]=1) - but before MDA switch to “USB 2.05” no COUNTRY ID ERROR and then setup making one more checking and display COUNTRY ID ERROR.
I try all of ROMS from ftp.xda-developers.com – 8( always error.
DeviceData.txt before wrong update:
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
now my DeviceData.txt is as in attachment for this message
(I can connect with ActiveSync and run GetDeviceData.exe).
PH20B 0 B WWE 1.40.00 0 0
Please help me, I’m going crazy and spend on that problem last 48 hours, read and try everything on forum, wiki.
Go to the thread http://forum.xda-developers.com/viewtopic.php?t=16953
It is the Wiki: Help me! And yes I have read getting started
There are nice people who will help you surely!
mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).
HappyGoat said:
mariusz said:
.... I download type II ROM and converted to type I, then I change with tool xda3nbftool.exe nbf ....
Click to expand...
Click to collapse
1. How did you convert a type II to a type I...?
2. Upgrading a type II to a device that does not allow it will give you the Country Code error.
Have you tried to reinstall your ORIGINAL ship ROM...? This should work. See the FAQ link in my sig for more prob solving (red one).
Click to expand...
Click to collapse
1. I don't convert type II to type I. I download converted type I from:
http://forum.xda-developers.com/viewtopic.php?t=20770
2. YES 8)
3. I don't know my ORIGINAL ship ROM. 8(
4. I read all of the FAQ at your link - nothing help, I can't find my qtek with T-MOB009.
I have now wrong DeviceData.txt and I think is the main problem. Can't set nbf files to settings from my DeviceData.txt file. 8(
You took a tpye I CE Rom and Type II radio and Ext Rom.
Flashed your device and got stuck, no point explain how or why you did it, lets move on.
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
2) extended rom. You now need to get any extneded rom on your device so that you can then unlock it and copy the 1.40 one over.
So following the wiki getting started download the I-mate 1.62, extract and remove all *.nbf BUT the ms_.nbf, fix the file, run the upgrade.
This will now put a 1.22.162 EXt rom on your 1.40 rom with radio 1.12. Sorry you will have to live with the i-mate splash screens, you can fix that in another thread.
Now unlock, unhide that (also on wiki) delete all and replace it with the extracted 1.40 Ext Rom out of wiki (were else) avalible Extended roms. Lock and hide, hard reset and you should be up and running.
Oh Yes and please if it says extract or download what ever files please do it so that you dont get a version problem.
Have fun
MDAIIIUser said:
...
1) Radio rom, go to wiki, download the radio 1.12 and the tools, fix it with fix.bat, run the upgrade.
This should give you 1.40 rom and radio 1.12
Click to expand...
Click to collapse
U la laaaa...
I can't update radio ROM as in step by step instruction at wiki becouse I ALWAYS STOP on ID COUNTRY ERROR.
My DEVICEDATA.TXT is wrong. I don't have in this file some versions numbers and somthing like T-MOB009.
8(
If you know how I have set fix.bat for my DeviceData.txt please send more details.
DeviceData.txt :
PH20B 0 B WWE E 1.40.00 0 0
so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa
MDAIIIUser said:
so try the Country Code error hack, its for type II but it might work on type I, You have a type I rom so the file is called HTCRUU.conf
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
What happens if you try to flash the I-mate 162 with out the fix.bat, its a clean Type I install and you don't have a Operator code to check against, its also a wwe rom.
La laaaa
Click to expand...
Click to collapse
1. Hack dosen't work.
2. When trying I-mate 162:
ERROR 120: COUNTRY ID ERROR: NO-No-12-12-12
8(
Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.
HappyGoat said:
Hmmmm....ok, I think the problem is T-MOB009. Are you sure that was your original config? Was your operating system German to start out with (G)?
Here's an idea (perhaps):
Try the Type II Ship ROM (1.40) complete, but with country code hack.
You probably have tried that already, not sure.
Last alternative I can think of, is to put PDA in bootloader mode, and use mtty.exe to remove everything from your PDA.
See also itsme website for such rapi tools: http://www.xs4all.nl/~itsme/projects/xda/tools.html
I have never tried this procedure, so not sure if it will work for ya.
Perhaps my Boss MDAIIIUser has another great idea...he's good at this stuff...so await his reply.
Click to expand...
Click to collapse
1. Yes, I'm sure T-MOB009 is my ORYGINAL setting - 8)
2. Yes, I try type II with hack - it dosen't work.
3. Could you send more detail instruction how remove everythink from PDA using mtty.exe (link or description step by step)?! - now i have this tool but I don't know how I can I use it.
...and I waiting for replay from Boss and Master of Raster MDAIIUser.
Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )
MDAIIIUser said:
Please confirm that you can connect to your device with acticve sync.
Thus that you are able to browse your documents on your device form your pc.
Next check your dont have that pc issue that is in the wiki getting startted last section of the thread.
I am going to tell you the same as what is in that thread so read it. before I tell you.
@ HappyGoat ,
I must be sick I turned very Green <Grin>,
so can't be your boss no more, will never get that respect now will I? (don't answer )
Click to expand...
Click to collapse
1. Yes I can connect via ActiveSync and browse file from desktop PC.
2. I don't know what are you asking for ?! PC issue, last section... hmm...
If you are asking for:
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted
but I can't find anythink about pc issue at last section, please send it here.
Ok the thead started here.
http://forum.xda-developers.com/viewtopic.php?p=112036#112036
The porblem was that the guy could not get his radio to flash which is some what the same as you at the moment, his solution was to move to an other pc.
Anyway there are a few steps that I think you should try.
On the i-mate 162, did you use the upgrade tools from the extracted ship.exe and did you run the fix.bat.
PH20B 0 B WWE G T-MOB009 1.06.00 0 0 1.06.135 1.00.00 00.00
Click to expand...
Click to collapse
Were did the "G" come from should be "E" ?
Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.
Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz
TheLastOne said:
Hrmm... I would attack this as follows (don't actually expect this to work, you've probably already even tried it, this is just the first thing I'd try).
Download this rom:
ftp://xda:[email protected]_139_10600_SHIP/Xda_IIs_v131139_upgrade.exe
Then do this, since we know that this method works with that rom:
Edit the RUU.conf file
Add the following line
[CHECKCEID_TYPE]=1
Save changes
Now run BaUpgradeUt.exe
It will say that it will upgrade to this version.
However when the device enters bootloader mode the upgrade util gives a country error. (Don't panic)
Simply restart BaUpgradeUt.exe while the device is still in it's cradle.
Now it will install without a country error.
I hope that this trick works with other BA devices and not only with the XDA IIs.
Hopefully it will install. I'm betting that the bad upgrade messed up your country code, so instead of getting the country code it expects (as you enter with xda3nbftool) it receives something else, or null characters. I'm hoping a rom change can fix this.
Click to expand...
Click to collapse
Dosen't work... 8( I add [CHECKCEID_TYPE]=1 and run it one more after recive coutry id error.
My log file HTCRUU.log :
23:57:25:802 [msg] : Config Info : [667685],[1],[0].
23:57:30:409 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
23:57:34:835 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
23:57:36:988 [msg] : Get Device Backup ID.
23:57:36:988 [msg] : Device BL VER : [2.05 ] [].
23:57:36:988 [msg] : Device ID Is Incompatible.
23:57:36:988 [msg] : START UnInitialization !
23:57:36:988 [msg] : END UnInitialization !
23:57:37:008 [msg] : IsBL. BL : [1]
Now my sytuaition change some:
1. After change PC I try to install qtek ship 1.40 and update hold for 30min with no meesage.
2. Now My CE don't start only program mode (Serial/USB 2.05), hard reset don't help. ONLY PROGRAM MODE START.
lukjod said:
Hi Mariusz
Have You suceeded, if no and You have mda3 bought thru era
i can send You my version of rom which is working well without problem on my era mda3
its 1.40 rom 1.12 radio and 110 extrom
i've upgraded it from original era 1.20 rom
rgds
lukasz
Click to expand...
Click to collapse
Oooo, No I'm still in truble... If you can please put your ROM on FTP and send link. 8(((
Wait for any solution... 8(
8( still at same point... only bootloader, and always Country ID error...
Pleaseee, help... 8(
I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?
MDAIIIUser said:
I am lost, Thelastone tells you to install the o2 rom, you say that you have installed the qtec.
So what have you done?
What rom are you trying?
Click to expand...
Click to collapse
I try everything from XDA-dev ftp, with all known hacks and without... still only COUNTRY ID ERROOR.
I try backup to SD card but it is impossible:
Add record error... 8(
I can't find any image file to send it to SD by ntrw.exe, try send .nbf files from shipped ROMs but after insert card into MDA III and restart, ROM restore from SD don’t start.
I just bought a BA and want to upgrade it to use either the AKU2.6 or AKU3.2. I got to setp 3 below:
3. Modify the operator in the ROM as needed:
Determine your operator Information e.g.: "T-MOB101", or "Vodafone", or O2. See GetDeviceData.
(I did this the operator is "XGULA001")
*
Open a command prompt, go to the folder where the ROM file resides (nk.nbf) and execute: SetOperator ???
(where ??? is your operator)
(I used the Microsoft command promp and went to where the nk.nbf file is located. After the C:\> I typed "\cd\Documents and Settings\John\My Documents\WM2k5_AKU2.6_32mb_v1.1.2\" as this is where the nk.nbf file is. Then I typed the command SetOperator XGULA001.
I get the following error:
"Set Operator is not recognized as an internal or external command, operable program or batch file."
What am I doing wrong?
Any help would be greatly appreciated.
I figured it out. There's a few mistakes in the instructions. The nf.nkb file has to be moved to the file where the appropriate rom is found before running the setoperator command prompt.
Also, one must fully reboot after the hard reset and connect to the PC via Active Sync before running the rom upgrader.
Whoever made these WM5 ROMS for the BA should receive a reward. They're awesome.
Thanks
Hi all ,
at this day , it don't exist any official rom of the S300+ (trinity branded by SFR in France) and so , i can't dump the splashscreen .....
is exist a way to do that in my trinity ? (i have of course this rom inside)
cause soon ,this evening i hope , we will able to create his own extrom so with the splashscreen of the S300+ , i can create a FULL rom for anybody
Thanks for your answers positive or negative
I look at the Wiki and don't see anything about that ...
perhaps a cool french guy could create these not me i am too lazy for that but NO lazy to make the else things to do
you have to patch an SPL to allow you to rbmc at any address, i did this on hermes, not on trinity, but I guess should be very similar:
search for this hex string on the SPL: 0532A0E30E3883E3
Replace it for 0532A0E30000A0E1
Make sure the string is found only once, and load the resulting SPL.nb with SSPL.
Then you can do:
Code:
Cmd> task 32
Level = 0
Cmd> set 1e 1
Cmd> rbmc splash1.nb 500e0000 40000
Cmd> rbmc splash2.nb 50140000 40000
ok Pof ,
search for this hex string on the SPL: 0532A0E30E3883E3
can you give me some help about that ? i don't know where i have to begin
Use an hex editor
lol , that was not exactly what i mean
OK, I don't put links to anything so you make a bit of reading / research yourself... and is faster for me to write
Download HardSPL for trinity, use nbhextract to get SPL.nb from the NBH file.
By default the SPL will only allow you to "dump" a small region of the NAND flash chip, you want to dump the splash screen, so we have to patch it. To patch it, take any hex editor of your choice (radare, winhex...) and find this hexadecimal string: "0532A0E30E3883E3", then replace it for "0532A0E30000A0E1".
Now you have to load this SPL on your device using SSPL (read the SSPL readme.txt file, advanced instructions), you have to pass it as a parameter so you have two options: either create a .lnk file or use itsutils:
Code:
pput.exe patchedSPL.nb
pput.exe SSPL-TRIN.exe
prun.exe SSPL-TRIN.exe patchedSPL.nb
After prun, you have to quickly press the bootloader buttons, and you'll see the tri-color screen with your patched SPL
Disable activesync from now on
Connect to bootloader and issue the following commands:
Code:
Cmd> task 32
Level = 0
Cmd> set 1e 1
Cmd> rbmc splash1.nb 500e0000 40000
Cmd> rbmc splash2.nb 50140000 40000
mtty is very fishy with rbmc, so probably you will see no output, if this is the case you have 3 options:
Use unix command 'cu' (inside uucp tools), it works fine with rbmc.
Use mtty and capture the output with usb monitor, then use unix command 'xxd' to create the binary files.
Try with putty (I never tested, but probably works).
The output of the two rbmc commands are your first and second splash screens.
Thanks a lot Pof , you are very kind to did this !!!
but i have no success yet but i continue ...
@pof
what do you mean with "Use mtty and capture the output with usb monitor"
i think i did the right things before rbmc but like you said : i see no results i look at the options in mtty and i don't see "usb monitor"
can you help me (again) please ?
Regards
edit : is is the good result of the prun command ? ERROR: CreateProcess failed with Errorcode = 0
- Une connexion existante a d¹ Ûtre fermÚe par l'h¶te distant. (an exist connexion was closed by the host)
extenue said:
what do you mean with "Use mtty and capture the output with usb monitor"
Click to expand...
Click to collapse
ftp://xda:[email protected]/Hermes/Tools_and_Programs/usb-monitor237.exe
Capture in "complete" tab, export as ANSI text file.
extenue said:
edit : is is the good result of the prun command ? ERROR: CreateProcess failed with Errorcode = 0
Click to expand...
Click to collapse
yes, it's normal cos the SSPL kills the OS.
ok ! i finally success in export as ANSI text file the two files
i have not unix at home (i have only windows) , so before i ask my friends to create the binary files , how can i be sure that my dump is correct ?
Thanx again
extenue said:
how can i be sure that my dump is correct ?
Click to expand...
Click to collapse
The dump should have 262144 bytes (size of a splash screen).
1. Glance through Faria's original thread on this (he wrote the book!!)
2. Download button's 1.05 ROM
3.. Downgrade your ROM to the Button 1.05. Let it go through the whole setup please...
Note: If your device fails at 98% with a 302 error follow Vippie's advice and try the Xda_MiniS_LaunchROM_v154102 instead.
4. Download lokiwiz - HTC Wizard Unlocker UPDATE Version 0.2b
5. Extract the afore mentioned file to the root of your C drive. Do NOT extract to a folder with spaces...
6. Open Activesync WITH YOUR DEVICE NOT CONNECTED! and delete your partnership.
7. Connect your device and cancel the partnership. (You're a guest )
8. Open ActiveSync, Explore and copy enablerapi.cab from your PC's C:\ (remember that's where you extracted lokiwiz to...) to you device, I don't care where.
9. Pick up your PDA, File Explorer, find the enablerapi.cab and click it.
10. (Back to your PC) ... <Start> <Run> <cmd> <Enter> to give you a most wonderful MS Dos prompt (be afraid, VERY afraid!)
11. In the MS Dos box (mouses not allowed!!!) type "CD\" <enter> (no quotes)
12. Type "lokiwiz.bat" <enter> (Actually, if you have XP, type lok then <tab> it SHOULD complete the filename, YMMV.
13. You will see a screen that has ...
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
14. Hit the U key on your PC and press <Enter> ... your PDA WILL REBOOT upon completion !!!!!!!
15. Wait for your PDA to reboot, rerun the lokiwiz batch file (if you hit the up arrow key twice on your keyboard it will retype "lokiwiz" then hit the C key on your PC and press <Enter> ... YOUR PDA WILL REBOOT UPON COMPLETION !!!
(if your Pocket PC Phone does NOT reboot each time, you didn't do it right! Stop and make that work, trust me!, then go on)
16. Watch the rebooting of your PDA, if BOTH IPL and SPL are 1.xx then great. Quite probably your IPL will be 1.xx and your SPL will be 2.xx. Rerun the button 1.05 ROM downgrade a second time and it will become 1.x on both IPL and SPL. You don't need to redo the unlocking.
17. My suggestion, take for what it's worth, is to download and install the T-Mobile 2.26 ROM
This will give you a strong 2.26 IPL and SPL to work with.
Now you SHOULD have a IPL and SPL of 2.26 to work with. If not, you screwed up! Don't attempt to install someone's hard work and ***** before you do these steps!
EDIT for Step 17 - Download and install the 3.08 IPL/SPL rather than the 2.26, your choice! (I suggest doing the T-Mobile 2.26 first but that's me
Click to expand...
Click to collapse
i've done thru step 13 and when i run .bat i have this :
Unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
CopyTFFSToFile(0x0, 0x10000, lock_backup.bin)
_
Click to expand...
Click to collapse
and it doesn't do anything more!!
what i may have do wrong?
how many time it's supposed to be?
other info :
-when i plug my pda i have a msg like "backup your parameters" and it doesn't disapear but activesync is green and i can see my phone on my pc!
-i can't get WST to work, whatever the button i click the tool bug and crash
please help me!
thank you in advance
wolf69 said:
how many time it's supposed to be?
other info :
-when i plug my pda i have a msg like "backup your parameters" and it doesn't disapear but activesync is green and i can see my phone on my pc!
-i can't get WST to work, whatever the button i click the tool bug and crash
please help me!
thank you in advance
Click to expand...
Click to collapse
if you have followed the procedure correct than there's no way that you shud stuck at step 13 as you say.you are supposed to complete the procedure only once and it takes only a couple of minutes to finish.
error: stuck up at...
Unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
CopyTFFSToFile(0x0, 0x10000, lock_backup.bin)
the only catch in it as where guys usually go wrong is placing of EnablRapi.cab file in the phone,check if you have done this step correctly,secondly where did you execute the Lokiwiz.bat file ?
i've found my problem sygate don't let the .bat access to my pda!
so i've upgrade my pda with NBT (i think its the name...)
but i can't syncmy pda with my computer it says me that i need activesync4.5 but when i install it i have an error that says me that the programe can't install cause of a dll (without name it!)
wolf69 said:
i've found my problem sygate don't let the .bat access to my pda!
so i've upgrade my pda with NBT (i think its the name...)
but i can't syncmy pda with my computer it says me that i need activesync4.5 but when i install it i have an error that says me that the programe can't install cause of a dll (without name it!)
Click to expand...
Click to collapse
lol !
glade you found what was not letting it complete.But, my dear,its been stressed upon in many threads and alot of times to disable or close if any anti virus and also temporary disable or close any Firewall,even Windows own Firewall.
You mean WM6 Rom NBD 9.2 ? if yes, CONGRATS!!!
NBD Rom has nothing to do with not letting it sync,it just that Active sync downloaded file might be corrupt,download again and install,i'm sure it'll be alright