Database Develop

Bootloader Screen

Hello,
I need some expert help to get my XDA IIs out of bootloader.
I attempted to update ROM and got stuck in Bootloader.
I followed directions posted on this forum to the letter:
Make sure your device or cradle is connected directly to your computer (so no hubs!)
Disconnect the device from the PC, or remove from cradle
Perform a "hard reset" on the device (screen will flicker but nothing will change)
Kill the BaUpgradeUt.exe program on your PC by using Window's Task Manager (CRTL+ALT+DEL)
Kill the wcesscom.exe program on your PC by using Window's Task Manager (this is the ActiveSync application)
Place the device back in it's cradle
Restart the upgrade program from your PC (double-click BaUpgradeUt.exe)
Still No JOY !!! Any suggestions ?

Solution to Upgrade..?
Hi, have you looked at this properly..?
http://wiki.xda-developers.com/index.php?pagename=BA_1.42.00_Upgrade
Or - If you're trying to update to WM5..
http://wiki.xda-developers.com/index.php?pagename=BA_5.1.1700_build_14343_Upgrade
Then you should be ok.. Take a breather, start again..
Let me know how you get on..?
Cheers,

Stuck in Bootloader Screen
Mr Philly,
Thank you very much for your help, however I followed the links you gave me, and still have no joy.
When I run the BaUpgradeUt.exe I get a "connection error" saying check the physical connection between the phone and the computer. Also, BaUpgradeUt seems to close active sync once launched. The program then freezes unless I reopen active sync. I then get the connection error.
When I run the MaUpgradeUt.exe I get to the upgrade screen telling you that you are upgrading from ... to ... however the fields listing the various ROM versions etc.. are blank. If I click on upgrade, I get an error 150 saying "not designed for your device, please get proper ROM upgrade utility."
Any new suggestions for me ?
Missing my XDA very much as I use it a lot.
Thanks

I figured out the problem. It seems that the PDA was not responding to the ROM upgrade because the SD Card was in place. Origionally I thought this to be of no consequence as I only have a "dummy" card in the slot. I was wrong. Once I removed the Card everything went as it was supposed to.
:wink:

Stuck on bootloader
Hi all,
I copyed in fakt i did cut some files from my BA and moved to Storage Card (1Gb), and it restart byhimself and i am stuck on the bootloader. ??? Shall i rom Upgrad it ?
Howlingwolf

Need help recovering after botched ROM flash

I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!

snootch said:
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
Click to expand...
Click to collapse
Well Friend I hate to say it but Using Vista is your problem... The drivers in WMDC are different from those of activesync and thus Vista cannot talk to your phone in bootloader.
Follow this thread here:
Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!
Once you complete the steps in that thread, flash the Official T-Mobile Rom. I will be online for the rest of the night so I will walk you through everything if you would like me to. My AIM, Yahoo, and MSN messenger addresses are all at the top of every one of my posts.

First off, let me thank you for your help, as well as the time you have put in the community helping people like me. I had updated the driver before, but I guess several attempted flashed had overwritten the driver. Just now, I followed the link you gave me, updated the drivers, and flashed the T-mobile 2.26 ROM. The problem still remains. The RUU goes to 100%, shows me the finish/exit screen, mu wizard restarts, but hangs at the white boot screen and does not go any further.

Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.

snootch said:
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
Click to expand...
Click to collapse
If you can manage that, you will be set. All you have to do is create a hard drive partition and install xp to that partition.(from what I know anyway)

OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315

snootch said:
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
Click to expand...
Click to collapse
Although,many have successfully flashed using vista,but I'll suggest in your condition flash through WinXP. Download the official carrier's Rom from it's website.
1. Disconnect your phone from the usb cable,shut down any firewall,disable any Anti virus,Reboot your PC.
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. On your PC Open windows Task Manager...>Tab Processes...>wescomm.exe...>End process
4. Power off the phone completely (Not stand-by,shut off completely),or you may take the battery out for few seconds
5. Make sure your phone is not Connected to the PC via USB cable and remove the dummy Sdcard or mini-Sd card
6. Get your phone into Bootloader mode (Multicolor screen) by pressing camera button + Power on button
7. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Be sure that your battery is charged over 70%)
8. "USB"will appear on the bottom of the screen of the Bootloader (Multicolor screen)
9. Run the Upgrade again and it will work fine without any problems.
10.Never use Bluetooth sync for the Upgrade
While upgrading, the ActiveSync program will not go on, however the upgrade is running.Please be patient when you're flashing your device, even if 98%. It can wait a little bit, 5 ~ 7 minutes.
Don't cancell the flash or get the phone off the usb cable till it confirms "Congratulations" or stops with an Error!!!
Hope it'll recover back to it's default status,good luck

I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.

snootch said:
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
Click to expand...
Click to collapse
As long as you are going to keep T-Mobile 2.26 on your device or are restoring T-Mobile 2.26, you do not have to CID unlock but should you decide to change to another Rom, you will need to CID unlock.
Good luck on the dual boot. There is a detailed tutorial in my Signature if you would like to take a look at it. After I can restore my crashed laptop, I am going to take care of the dual boot also.(I have to do it again... )

I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.

snootch said:
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
Click to expand...
Click to collapse
It's better if you use 'PartitionMagic' software to create partition and install WinXp,as it has much advanced features as compared to built-in Disk Management.It also has the option to create a partition in the same one partition to install new OS.

I tried that first, too bad it doesnt work in Vista.

Woo Hoo!!! Success!!
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.01
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)

snootch said:
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.05
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
Click to expand...
Click to collapse
Congrats ! that's the easy way.....

Yeah, I got tired of screwing with it, and I did it all in Vista!

Apologies - complete noob - loading Miri's 6.5 ROM

Hi
I'm following Crackwhore's excellent guide to try and flash my Blackstone to WinMo 6.5. So far I've succesfully dealt with the whole USB driver problem (I'm running 7 x64), and I can get my phone to load USPL, but I can't seem to get the next bit right. I've downloaded Miri's 6.5 ROM, what do I do next? I tried running the BlackstoneRUUWrapper.exe with the phone connected in bootloader mode - it didn't work. Neither did the HSPLWrapper_Blackstone_156OliNex.exe file suggested by the guide. It says in the program that I should be connected with ActiceSync, is this actually the case? Sorry for this confusion, I'm sure it's simple when you know how...
Thanks
Fredley

Have you disabled the active sync in the PC ?
You have to go to the Windows mobile device center and disable allow USB connection i think. Then when your screen says USPL (the color screen) connect to the PC, it should display USB on the display, after that execute the BlackstoneRUUWrapper.exe. Don't forgot the Hard Reset after flash (power up with both volume buttons pressed).

I think I'm fine now, sorry for that. My problem was not going through the whole USPL process before trying to flash a ROM. I am loading the ROM now, fingers crossed!

fredley: Glad to hear it's sorted.
In future, please use the sticky guides to post questions. You actually get better exposure there. Crackwhore and Fallen sparten (and even me sometimes ) follow those and reply quickly.
Thread Closed
Dave

Problems flashing Touch HD

Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell

I had same problem.
Change usb cable, change usb port you are using and make sure antiviruse turned off.

rgtuit said:
Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell
Click to expand...
Click to collapse
You're using sticky guide yet you created a new thread instead of posting in sticky....why? no need for this
Thread closed
p.s. for your info
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.
If this doesn't work, try resetting your device, put it in bootloader and then connect it to usb cable

[Q] This is depressing, stuck on SPL [email protected]! Trying to flash to a HSPL ROM

Hey guys,
New to this whole world of flashing devices and have been browsing for days trying to learn and understand all the different terms associated, so please forgive me if i say something that doesn't make any sense
Trying to upgrade my HTC Touch HD (Blackstone), Rom version: 1.14 WWE (put my phone into bootloader and the SPL is 1.14), was trying to update my phone which is when i came across cooking roms and updating them via flashing, have read Digital Outcast's Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL], decided i wanted to follow the HSPL which is when i came across
http://forum.xda-developers.com/showthread.php?t=671277
and wanted to install the 'blackSTONEhenge HyPer MaxSense' Rom, said i needed RADIO ROM version 1.14 or above, my stock standard HTC has RADIO Version 1.09, which meant i had to try and flash my devices radio rom.
What im not sure is this HSPL, i dont fully understand if im supposed to try and get/put HSPL on my phone before i do any flashing/ im not sure if HSPL is the 'thing' that allows flashing to become capable...
If someone could help me out as i have been browsing the forums for a few days and its driving me nuts as usually i would have worked it out by now!
Cheers,
Scott

Go to this link
http://forum.xda-developers.com/showthread.php?t=505377
dont get confused
1.just download "HSPLWrapper_Blackstone_156OliNex.zip" from "Attached files".
and unzip in a empty folder.
2.connect your phoneto pc via active sync.
3.run HSPLWrapper_Blackstone_156OliNex.exe, click yes/next/ok(sorry dont remember what was it, you phone will restart in bootloader (three color screen and hspl will be done automatically.
thats it.
now flash any radio or rom of ur choice.

nice explanation, just let me add some newbie information:
basically, what you are facing, is flashing three things:
1. you flash hspl, which means that your device will be unlocked for roms of all carriers and all countries, and you will be permanently ready to switch roms any time you want, as it remains in your phone, whatever you do (hard reset, flashing a stock rom, whatever).
2. the radio rom, the radio is the bridge between the windows mobile operating system and the hardware. this is responsible for the fact, that for example switching on wi-fi is done with the same button on any device, independent from which wi-fi card is actually installed. it controls wi-fi, gsm, 3.5G communications, bluetooth, camera and sound input and output. the latest radio for the blackstone is 1.17 (.25.09 i believe). it offers the best quality in all beforementioned services, but drains slightly more power than previous versions, due to higher performance.
as there is actually yet another stepping stone between the OS and the radio, rilphone.dll, it is advised to use a new radio with the cooked roms offered here. most chefs integrate a new rilphone.dll in their roms and they work best with the corresponding radio rom.
3. in the end, you will flash the actual OS rom that changes your operating system, possibly the language, the manila version and everything else. just like formatting your windows xp pc and installing windows 7, your apps, settings and personal information (in this case contacts, appointments, sms...) will be gone.
for it to work, you must flash hspl first, or your device will be unable to accept actual roms, and then proceed with the radio, and before flashing the actual OS rom (in your case blackstonehenge), you should perform a task 29, either you can flash it (see task 29 thread), or use mtty or use advanced ruu, which has an extra option to do it.
this was just a basic introduction to make it easier for you, to understand, what you are actually doing, when attempting to flash, the rest and all the steps to take are in the tutorials, i just find it easier to do, when you actually know, why you do certain steps, helps you remember for the next time.
regards
Chef_Tony

Ok thanks guys for the responses, and especially chef_tony's, cheers.
P.s. Sorry for the complicated response below, its hell to read
I have tried to follow:
Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL]
http://forum.xda-developers.com/showthread.php?t=505377
And it hasn't worked, when I follow the HSPL steps I get to step (HSPL2c) and it just sits on 0% and give an Error [262] code (this is the section where we try to flash Blackstone_156OliNex to the device.
The tutorial says: run HSPLWrapper_Blackstone_156OliNex.exe, which then tells us to establish an activesync connection, which i think means we have to get the bootloader mode to USB, in order to get the bootloader to USB Mode I have to connect my phone to the pc before running the HSPLWrapper_Blackstone_156OliNex.exe and leaving it connected to the pc to A) establish the activesync connection(Windows device centre doesn't register the phone as connected whilst in bootloader) then B) get the bootloader mode the USB.
So what i have done:
So the phone is connected to the pc, activesync registers the phone(leaving the phone connected i then),
place it into bootloader (shows USB Mode)
Then run HSPLWrapper_Blackstone_156OliNex.exe (i run it as an administrator)
the program tells me to establish an activesync connection (Windows device centre doesn't register the phone while its in bootloader, which dummies guide tells us to do), i dont know how to establish an activesync connection whilst the phone is in bootloader, so anyway i hit next, next and just click update the rom, and it just sits at 0% and give an Error [262]
Im not sure if the reason for this error is because i haven't put HSPL on the device, im still not 100% sure about the whole HSPL, i think all i have to do for this is run the HSPLWrapper_Blackstone_156OliNex.exe ?? then is the HSPL issue sorted?
Thanks again guys,
Scott

Dis-regard this post

easy thing. i had the same issue when attempting to install hspl for the first time. as described in the tutorial post you mentioned, i went to the part troubleshooting:
Troubleshooting - manual SSPL
- Boot up your phone.
- Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.
- Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.
- When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
- Go to step HSPL3 if successful.
with this extra step it worked for me, because installing sspl directly on your phone, it prevents 262 connection errors and unlocks the device temporarily which makes it easier to install hspl.

Thanks again chef,
ok i connected my phone, then copied the SSPL-Manual-TouchHD.exe to my device, run it and it loads into bootloader, shows spl 1.07OilNex, doesn't show USB no matter how long i wait, i unplug it and don't get serial mode either
Tried re connecting it and still no USB or serial mode comes up :\
I had tried following the troubleshooting tutorial before i posted on here for help
Should i try running the HSPLWrapper_blackstone_156OilNex.exe without USB mode showing?
and really appreciate all the help,
Scott

Following with interest
Tony and Scot enjoying the posts and hoping to pick up a few pearls of wisdom before upgrading. I have played around with my Touch HD and had it dual booting with android from SD card. For some reason I can no longer use my camera in wm 6.1.
I can not find camera.exe cab and was considering upgrading to wm 6.5 to see if that solves the problem.

Billy, im just stabbing at the dark here, but im guessing if you do flash your device to wm 6.5, during the installation of the upgrade, you're .exe for the camera will be re installed and should work again. Gdluck

Upgrading to wm 6.5
Probably right Scotty, I just want to make sure I don't brick the phone for the sake of getting my camera to work again. Have you managed to complete the upgrade?

Haven't yet, just waiting for some words of wisdom from tony

I also had Error [262] when tried to apply HSPL last week.
But, I applied USPL path to install HSPL!
So I entered USPL and started HSPL install.
Then process finished without any problems.
And it's working excellent... now on the 3rd ROM since appliing HSPL...

good idea, the most important thing is to get a stable connection for the bootloader, and if uspl makes it easier to install hspl, i would definitely give it a try. as posted before, depending on your soft branding, first installing hspl can be a hassle, however, once it's done, you never have to deal with it again (which is also, why many long term blackstone users including myself hardly remember, how to go about changing the spl).
also, since you mentioned that in sspl, you didn't see serial or usb in bootloader mode, make sure that your connection is actually stable. in bootloader mode, windows needs another driver for the device from what is used to sync the device (when it is switched on). especially, when using windows vista or windows 7, you should have a look at the thread "[tut] dummies guide: updating htc sync drivers".
especially on windows 7 x64 it can be quite a lot of work to get it running, because these drivers are not digitally signed, so you'd have to sign them yourself, which requires permanent test mode and comes with a watermark on your desktop, which, in turns, can be removed again. in that case, i would advise you to try a windows xp pc first to get your device up and running and you can deal with this later.
so, in short form:
1. in case you use windows vista or 7 and haven't dealt with the driver yet, have a look at the link to the tutorial or use a windows xp pc with activesync installed.
2. if you are positive that drivers cannot be the issue, or you successfully updated them, step forward and try the "uspl to install hspl" method, bodisson suggested.

CRACKED IT! dont have time to type how but ill post what happened once i wake up, thanks for all the help guys, you guys are legends!

Many thanks to Chef_Tony for his help in this matter. You've a lot of mod like qualities mate
Scottygrot, I'm glad you got it sorted in the end.
I'm closing this thread now. In future please post all flashing issues in Dummies Guide thread
Ta
Rick