Database Develop

Lokiwiz.bat problem,plz help!

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

The solution to the GPS problem

I'm confident I found the solution to enable GPS on production model Wings !
Check this out!
Now someone should test it!
See this post for info about dumping NV items.
or read on for a short manual:
0. search and download QPST (this is a qualcomm product suite, i believe someone put a link in this thread)
1. install HardSPL (see sticky)
2. download drivers on your PC (installation will be triggered after step 5.)
3. uncheck "Allow USB connections" in Activesync
4. restart phone in tri-color bootloader mode and start MTTY 1.42 (attached)
5. press return until you see Cmd> prompt and type: rtask c (if you never installed the diagnostics drivers before the installation of three drivers will be triggered (modem, diag com port diag and nmea com port)
6. now exit MTTY and start "QPST RF NV Item Manager" and select Read from Phone from the File menu
7. search item 0148 [NV_RF_CONFIG_I] on a production model is 11 (hexadecimal 0xb) and on a pre-production model it is 17 (hexadecimal 0x11)
8. if you have a production model change the value to 17 and click the button "NV Write". To veryfy if the value is sticky Read from Phone again
These are the steps. Unfortunately on a production model the value 17 is not written and stays 11. This is due to some kind of security mechanism and I'm quite sure this can and will be h*cked soon.
On a pre-production Wings and also on production Kaisers the value can be modified.

jockyw2001 said:
I'm confident I found the solution to enable GPS on production model Wings !
Check this out!
Now someone should test it!
See this post for info about dumping NV items.
Click to expand...
Click to collapse
You are God!!!!!!!!!!!!!!!!!!!!!!!
Regards

Is it working?

Jocky, sorry, didn't see your new thread. I replied here : http://forum.xda-developers.com/showpost.php?p=1847311&postcount=106
What do you think

i'm kinda new with smartphones ^^;
would you mind to write a little summary in a post or in a pm with the procedure?
sorry to ask that , i just dont want to do anything wrong ^^;
thx

el_lo said:
Jocky, sorry, didn't see your new thread. I replied here : http://forum.xda-developers.com/showpost.php?p=1847311&postcount=106
What do you think
Click to expand...
Click to collapse
Bad bad news
Regards

sat_ana said:
Bad bad news
Regards
Click to expand...
Click to collapse
Not at all, this problem has been solved already. See the solution here: http://forum.xda-developers.com/showpost.php?p=1847405&postcount=107
But there is a new problem here http://forum.xda-developers.com/showthread.php?t=361322&page=12 @ post #112

Just to summarize the current status:
el_lo attempted to change the NV item #148 value from 11 to 17. However, the new value isn't stored. The same happens on Niki (they also cannot activate GPS) and a friend xperiences same as el_lo. Perhaps a wrong driver version or NV item manager version causes this problem.
On Kaiser I can both read and update NV items.
So it's time to get back to the drawing board

thanks a lot jocky!!!!!

jockyw2001 said:
Just to summarize the current status:
el_lo attempted to change the NV item #148 value from 11 to 17. However, the new value isn't stored. The same happens on Niki (they also cannot activate GPS) and a friend xperiences same as el_lo. Perhaps a wrong driver version or NV item manager version causes this problem.
On Kaiser I can both read and update NV items.
So it's time to get back to the drawing board
Click to expand...
Click to collapse
How can I read the NV Item?

jockyw2001 said:
Dump NV Items
The configuration of radio are stored as NV items. It is possible to dump these as foolows:
1. Restart in tri-color bootloader mode and start MTTY
2. Type: rtask c
3. Exit MTTY and start "QPST RF NV Item Manager" and select Read from Phone from the File menu followed by Write Only listed Items to .QCN file
Click to expand...
Click to collapse
Taken from hxxp://forum.xda-developers.com/showthread.php?p=1813156

Yes, but how now to read the Item 148 from that file?

Dumdidum said:
Yes, but how now to read the Item 148 from that file?
Click to expand...
Click to collapse
Open the file in "QCNView" (part of QPST suite)

I'll try and see what I can do with mine this week-end, work's crap as no admin on PC.
Really wanna help to get this going

17 on my PreProd Radio Rom...

Btw: I could successfully change it to 11... (checked it)
Dont have a fix since 10 minutes... but up to 13 (!) satelittes in view still....

Dumdidum said:
Btw: I could successfully change it to 11... (checked it)
Click to expand...
Click to collapse
Thx for testing this Dumdidum, that is very helpful information.

Dumdidum's last test makes me very pessimistic.
It almost seems that before the item value is written to NVRAM the device checks if the hw is available
Anyhow, we will know soon, because I think I have a method to write NV which bypasses all checks

jockyw2001 said:
Dumdidum's last test makes me very pessimistic.
It almost seems that before the item value is written to NVRAM the device checks if the hw is available
Anyhow, we will know soon, because I think I have a method to write NV which bypasses all checks
Click to expand...
Click to collapse
I can't wait! Hope this will help.
By the way. Did you play around with the QXDM software? I found a testing utility for the GPS. I only could test it at work and we have no gps signals inside the building. Maybe you can try?

I don't know if this link is of any use in this, but every little bit helps (I hope)
Qualcomm MSM7200 Specs
On the last page is a picture of the architecture

Noobs Definite Guide to Himalaya Updating [XP/VISTA]

Hello All, many of you just keep asking how to do that and this, you do not use search, so im making this Guide which will help you
Things You Should Know:
Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :
Htc Himalaya Backpack (read below)
STK will Not function
There is no SDHC Drivers for any Version of ROMS for HTC Himalaya Yet
To Have 30.53 MB of storage Go here
Upgrading:
Windows XP :
Requirements :
Windows XP
Microsoft ActiveSync 4.5
Minimum of 256 MB of RAM
and some patience
Start your device in bootloader mode by pressing and holding down:
DPad + PowerButton + ResetButton
After a second release Reset Button, then release the rest of them.
Your screen will show word "Serial" at the top.
You are in bootloader mode now.
Place your device in the cradle/USB Cable, ensuring that the cradle/USB
is plugged directly into a USB port on your PC and not to a hub
and that the power supply is connected to the cradle/USB.
It is also a good idea to disable any screensavers on your desktop PC.
Once your device is cradled, the text on the screen will change to "USB".
Run HimaUpgradeUt_noID.exe and follow the instructions
Sit back and wait for the Congratulations screen to be displayed
on your PC.
Your device will still be displaying 'Upgrading radio stack, please wait' but as long as the PC says it is done, then its all OK.
Detach your device from the cradle/USB.
Now you have to hardreset your device :
Press Reset Button and hold down Camera Button + Record Button.
Hold them pressed until the "Boot Options" menu appears on the screen.
Select the options as follows:
(for selecting use Record Button, change values with Camera Button)
Enable KITL -> NO
Clean Registry Hive -> YES
Format Storage -> YES
When done, press DPad/Action Button and wait until OS starts.
Click to expand...
Click to collapse
Windows Vista 32-Bit :
Requirements :
Any Version of Windows Vista 32-Bit
Windows Mobile Device Center (Latest Version)
and a little computer knowledge
Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.
Step 1 of 16: Extract the attached zip file to a memorable location on your machine (e.g. the desktop). This is the Activesync 4.5 RTM USB driver.
Step 2 of 16: Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Step 3 of 16: Uncheck the 'Allow USB Connections' box, and select 'OK'.
Step 4 of 16: Run 'Services' by clicking the Start Orb and typing 'Services', and ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'play' button on the top bar.
Step 5 of 16: Load 'Device Manager' by clicking the Start Orb and typing 'Device Manager'. Expand the 'Mobile devices' section and click the 'HTC USB Sync' (or similarly named) item.
Step 6 of 16: Click the 'Action' menu and select 'Update Driver Software'.
Step 7 of 16: Click 'Browse my computer for driver software'.
Step 8 of 16: Click 'Let me pick from a list of device drivers on my computer'.
Step 9 of 16: Click 'Have Disk'.
Step 10 of 16: Click 'Browse', and browse to the location where you extracted the ZIP file in Step 1.
Step 11 of 16: Double click 'wceusbsh.inf'.
Step 12 of 16: Select 'HTC USB Sync' from the list, and click 'Next'.
Step 13 of 16: Wait while your driver is installed.
Step 14 of 16: Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item, and click 'End Process'
Step 15 of 16: Install your update! Everything should now run fine! You just need to bear in mind the final step when you want to start syncing normally again...
Step 16 of 16: In 'Windows Mobile Device Center', re-enable the 'allow USB connections' checkbox you disabled in Step 2.
Click to expand...
Click to collapse
If MODS find this Helpful, Please Sticky This
muckelmaus Wrote :
As I tested some ROMs with my himas. Only the CF-slot will not work, 'till someone will write a working driver for it.
There are no probs to use the backpack battery and the vga-video funktion, so far. Two out of three, thats not bad, I think.
Click to expand...
Click to collapse

Backpack problem
Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :
* Htc Himalaya Backpack
As I tested some ROMs with my himas. Only the CF-slot will not work, 'till someone will write a working driver for it.
There are no probs to use the backpack battery and the vga-video funktion, so far. Two out of three, thats not bad, I think.

thanks for the info, i havent tested it my self thats why i didnt knew, edited the First post with this info

Im a noob
Hi I am a noob and followed this guide but it did nothing...
Basically I have a 02 XDA II - it is locked and I want to upgrade it to windows 6/6.1 - I have been reading through the forum for a couple of hours now covering the wiki for himalays and other things.
I followed the steps on this - but nothing has been upgraded. So I guess this isn't how to upgrade to wm6?
So frustrating cos I can't seem to find the instructions on how to do it.
I believe its a rom i need right?> how do i put it on?
Should I unlock the xda first? (havent worked that out yet) or upgrade to wm6 and then it will be unlocked anyway?
Please please help I have been reading loads and trying to not ask obvious thigns.

i donot know if its SIM locked or not...try givinf xda2unlock a try
second, to upgrade you need a ROM, there are MANY roms in this Himalaya WM6 Forum...many of them have detailed instructions
it wont be any harm if you upgrade first...try giving it a shot and tell me
Ather

I have also performed 'Unlock Wiz/Himalaya' but all I get is 'The phone seems unlocked already' - but it is not unlocked - any advice with this also?

try to upgrade the rom simply, if u get stuck, we all are here

I am struggling through trying to work out how to unlock my sim and then flash WM6 onto my 02 XDA ii which therefore is a himalya - says PH10b in model no.
Anyway Im following one of the guides (http://wiki.xda-developers.com/index...0for newbies) and it says I have to establish whether it is a G3 or G4 or else Ill brick it and probably throw myself out of my window.
So I performed a soft reset and got the following information in red letters when I do it.
R 1.10.00
G 1337. 18
1.60.00WWE
I just don't know if it is a G3 or G4 and can't afford to brick this phone - so please could someone help me so I know which intructions to follow?
I will send best reply a stick of rock from Blackpool (famous for rock - its like sugary concerete).

Sorry to be unclear - it is sim locked - it has horrible 02 logos all over it.
Bastards.
Anyway it is sim locked and wm 2003 i think.
Im not clear about how to install a rom - i did update the drivers putting it in boot and then updating driver from what i downloaded - which I think was to resolve and issue with vista/xp as i am using vista.
Right now im trying to work out G3/G4 because i found what seemed to be a good instrucitonal post

lol, the xda2 doesent has g3 or G4 ... so flash away

So how do i unlock it and then install WM6?
Is there a step by step guide?

It is sim locked and i want to unlock it and install wm6

the Branding has nothing to do with the Simlock, my Himalaya is from O2 too, and all it had was Branding, no simlock.
I'm currently using E-Plus as my Provider, and i did not have to circumvent any simlock before flashing WM6.1 onto the Device.
Also, if it DID have a Simlock, it has probably worn off by now, since the Device is already older than 2 years...

I have managed to unlock the sim now thanks to the wonderful people here but still have no clue how to install wm6?

congrats , just download any ROM and enjoy flashing it

do i just download a wm6 file and put it onto my pda and then execute it? double click it? is it that simple?

Can u spefically tell me how to implement a rom?
i assume i download it but then what?
I am thinking I'll just brick it - then spend months on here asking for help... Id rather just ask beforehand and find out how to do it.

it's exactly like ather said, you downloaded the ROM, now you can flash it to your XDA.
Just do it like it says in the Readme and you should have no Problems whatsoever

Strange
I had an old Qtek 2020 and flashed it successfully to WM6.1 No problems exept...... the phne does not conect to the correct provider. The SIM is for the Belgian BASE provider whereas it connects always to ORANGE. When I put the SIM in my new Diamond or in my very old Nokia phne it connects to BASE as intended. I reflashed to the original Qtek WM 2003 SE and same thing. Reflashed again to WM6.1 ans still it only wants to connect to ORANGE ??? What am I overlooking?
BTW if I donload the list of providers there isno BASE provider. If I download the list on my Diamond it appears whithout any problem.

it could be because of the Network Manager has old settings, try setting it up manually

Clicdiag

I've come across a ClicDiag bootloader. I believe it's a custom HBoot that runs the Diagnostics suite for the Clic. I had hoped this was an Engineering Bootloader, or a Ship S-OFF
To boot it, extract clicdiag.nbh from the .zip file bellow, and copy it to the root of your sdcard. Reboot into HBoot and it will shortly boot into the Diagnostics mode. The most usefull command is the "F/T1 Test" that enables the USB port to be used as a serial port (I believe, can't confirm this yet).
In F/T1 Test mode, if I plug my Tattoo to a Linux box, I get a ttyUSB device, but, so far, I haven't been able to talk to it yet. Maybe someone more familiar with minicom will be luckier ? Under Windows, it asks for Qualcomm CDMA drivers, but I haven't been able to set this up either.
To the best of my knowledge, this will not brick your Tattoo, but use with extreme care.
RUNNING CLICDIAG WILL RESET ALL YOUR TATTOO SETTINGS, you have been warned.
Report your findings
Download:
http://www.megaupload.com/?d=27NLIDXC

well done
dude this is progress!!
where did you get this?
i would try this out! if a had a tattoo...

@mainfram3: I need a goldcard or try normally?

Chusen,
Good question.. I have converted my SD to goldcard, so I don't know if you can boot it without one. But, if I recall correctly, the HBoot always checks for those files, even without a goldcard, so it may work (without one).

I tried but does not detect clicdiag.zip in a goldcard mode an normal mode
CLICDIAG.nbh No image file or wrong image

You have to extract it from the zip file and place the clicdiag.nbh in the root of the sdcard.

mainfram3 said:
You have to extract it from the zip file and place the clicdiag.nbh in the root of the sdcard.
Click to expand...
Click to collapse
no rename??ok jeje i try it
same result: no image or wrong image
thanks for you job

Chusen,
Can you try renaming it to CLICDIAG.nbh (clicdiag in uppercase). I just checked and that's how mine is named, maybe this makes a difference ?

I've tried in all caps, may be problem of my SD that is not properly check goldcard?

Yes, that's what I was about to suggest, maybe a goldcard is needed and yours is not setup properly
Apart from try to flash a WWE rom to a CID locked phone, I only know of one way to test the goldcard:
After booting into HBoot, hit the green button (send) for Simlock. If the goldcard is OK, it will react differently.
If the goldcard is OK it should end with something like this:
Code:
0: SD FAT32 init OK
0: Key-card
Wait for AMSS ready...
4: Unlock NV with SPC code
Pass/Fail/NoResponse: 0/0/0
Write PRL to Nam0 (0/0/0)
Write PRL to Nam1 (0/0/0)
4: Set Dynamic NV
Process done, reboot device?
<MENU> Reset Device

I tried in another SD and same result Why???
mainfram3 said:
Yes, that's what I was about to suggest, maybe a goldcard is needed and yours is not setup properly
Apart from try to flash a WWE rom to a CID locked phone, I only know of one way to test the goldcard:
After booting into HBoot, hit the green button (send) for Simlock. If the goldcard is OK, it will react differently.
If the goldcard is OK it should end with something like this:
Code:
0: SD FAT32 init OK
0: Key-card
Wait for AMSS ready...
4: Unlock NV with SPC code
Pass/Fail/NoResponse: 0/0/0
Write PRL to Nam0 (0/0/0)
Write PRL to Nam1 (0/0/0)
4: Set Dynamic NV
Process done, reboot device?
<MENU> Reset Device
Click to expand...
Click to collapse
This is ok

Here's the exact file I downloaded, just in case the one I uploaded in the first post is corrupted somehow. It's archived in .rar format.
http://www.megaupload.com/?d=27NLIDXC

ok downloading and trying..one question: have you a rooted tattoo?

worked!!!, i need some drivers.. sdk drivers???

ok sorry I did not read well, do not quite understand English, I can not help you, sorry

I think it might be interesting in the show menu puts secu_flag gsm info: enable

@mainfram3 I don't suppose you could let me know were you found this at? Or you could check to see if you can find one for the Eris it should be PB00DIAG.nbh or PB00****, any help would be great. Thanks pm me if you don't want that info public. Thanks

Now, we're cooking with gas!
So going to try this out. Hopefully we could get root via this or using this in conjuction with something else.

binny1007 said:
@mainfram3 I don't suppose you could let me know were you found this at? Or you could check to see if you can find one for the Eris it should be PB00DIAG.nbh or PB00****, any help would be great. Thanks pm me if you don't want that info public. Thanks
Click to expand...
Click to collapse
Hi.
I found it over a Chinese board. Had to login with bugmenot, to get to the files.
Here's the link:
http://www.hiapk.com/bbs/attachmentList.php

Dude, you found engineering Hboot !
I viewed nbh with notepad, it contains
0.47.2000 7225 SPL ?бENG ?б ?б ?бHBOOT-7225

Upgrade to Windows Mobile 6.x

Dear XDA Members,
I have now read the official Wiki five times, and I still haven't understood how to upgrade my BA to a Windows Mobile 6.
The Wiki "HTC Blueangel WM6 Home" links to a Wizard Style Wiki for this, however that link only returns a 404 Error. I also haven't found any information about this in the FAQ or orther threads. Maybe it's just me?
Where can I find a WM6 image for the BA (T Mobile MDA III)?
What software do I need to flash it via USB to the BA?
Thank you in advance.
Chris

Please refer to http://forum.xda-developers.com/showthread.php?t=630416
The instructions are there in Posts 1-6. Good luck.
Sunny

hi and welcome to the forum
as stated by sunny, my tutorial thread should cover all aspects of the upgrade process, including links to most of the recent roms.
the blueangel wiki suffered from the transfer to the new mediawiki project, which is why it should not be used for tutorials anymore.

Thank you both for your fast and helpful support.
I am running a non-english Windows Mobile 2003SE (GER) and executed the steps from your Guide to downgrade it to a WWE version. On xplode.tk I downloaded the latest T-Mobile UK Version and extracted the files mentioned in step 1b from the Temp folder while executing the .exe file. I also copied the files into the RUU folder.
When I open the task manager in step 6 i can only find and kill "wcescomm.exe"; "WCSEMgr.exe" isn't there. I am running WinXP SP3, logged in as administrator.
When I start Maupgradeut_noid anyway, I doesn't show me the rom versions.
Where am I going wrong?
Edit: I forgot to mention I have read the thread "Cant' Downgrade from Win2003 SE GER to ENG", but renaming the folder and then trying it didn't work for me either.

if you can't see those processes, you are probably not running activesync. install the latest version (a link can also be found in that thread in the 2nd post) and create a temporary partnership. just connect the device in normal running mode and set it to sync something small, like notes or favorites, after syncing go to the connection settings and untick "allow usb connections" then you should be fine and you can continue with the next step, connect in bootloader mode, make sure the display changes from serial to usb. at that point, a new driver will be installed and then running the ruu should get the upgrade process working, meaning, then there will be numbers in the 2nd window. if not, please post the RUU.log found in C:\

I have already installed ActiveSync 4.5.0.
I created a temporary partnership syncing favourites and after that unticked USB syncing in ActiveSync.
Then I connected in bootloader mode, making sure the display changed to USB V2.07. No new driver was installed, but I guess that already happened in my earlier attempts.
The HTCRUU.log (no RUU.log there) i found on C:\ contained a "Image Radio Checksum Error", so I downloaded another image from another mirror, but got the same problem.
Here is the log from the 2nd attempt:
11:50:02:843 [msg] : Config Info : [000000],[0],[0].
11:50:02:875 [err] : Image Radio Checksum Error.
11:50:02:875 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [0]
____
I HAVE however been able to flash a WindowsMobile 6.5.3beta image to the device without formatting, so thank you for helping me with that!
I reverted back to Win2003SE, because I would still like to get the 60MB if possible.

ah, ok, apparently the radio rom is damaged and shows a crc error, since you are planning on downgrading and then upgrading, just delete the radio_.nbf from your update folder and try again.
no worries, obviously, you did nothing wrong, but there have been a lot of corrupted radio roms around lately, xplode's rom archive has them and so mine and d-two's have them as well.
in general, a first indicator for corrupted roms is the file size, a nk.nbf rom must always have 32,769kb (1kb more than 32mb) and a radio has 4,097kb (1kb more than 4mb)
you can ignore (delete) all radio roms in the process of upgrading, frankly, it has nothing to do with the operating system itself, it is just the bridge between the operating system and the hardware. if you are not running radio 1.15.00 yet, which is the latest and according to most users, the best version, you can upgrade it any time you want, so i'd suggest: try and upgrade to wm6.x first and then, when you got used to flashing, flash the radio, or, if you are satisfied with your phone's in-call sound quality, bluetooth and wi-fi performance, don't flash it at all.

Ah, ok.
I deleted the radio file and tried again. This time it showed me an ms_.nbf Checksum Error. I deleted that one as well and got this:
09:51:05:968 [msg] : Config Info : [000000],[0],[0].
09:51:05:968 [msg] : RadioFile Not Exist !
09:51:05:968 [msg] : MSystemFile Not Exist !
09:51:06:171 [err] : Image CE Checksum Error.
09:51:06:171 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [0]
I also redownloaded the MaUpgradeUt_noID.exe right from your signature to ensure I didn't use an old one. Still the same problem.
My radio file DOES have 4,097kb; the nk.nbf has 32,769kb as well...I have to admit i'm still puzzled.
I also downloaded the two most recent radio files from your tutorial thread. Same problem: Checksum error. But I do not get a checksum error when I try to flash one of d-twos os-images.

i'm changing the radio roms, i will only provide radio 1.15.00 from now on, and i will post the entire package, as it came from htc (including the original RUU).

Thanks.
Where can I find them? Your tutorial thread seems untouched.

flash
hi WeissenbornC,
are you flashing with vista or win7??
if yes read please d-two´s tut for flashing with vista/win7.
http://forum.xda-developers.com/showthread.php?t=622768
hope it helps
cheers scudo

Hi scudo2709,
I am using Windows XP. Flashing a ROM is no problem, I have now had 5 different ROMs on my BA. However, I haven't been able to flash a shipped english rom (WM2003) in order to format the flash drive. I keep getting Checksum Errors with all of the ones I've been able to try so far.
Thank you for trying anyway.