Database Develop

Cant change my rom on my 8125

Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks

ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
do you have a G3 or G4?
What are your IPL/SPL?
Which other ROMs have you had installed on this wizard?

ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
My answer to you is the same one I posted to you before --
READ THE STICKY ABOUT UNLOCKING AND FOLLOW IT STEP BY STEP!!
Then -- and ONLY then -- will you be able to flash to a custom ROM.

newbie2 said:
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
Click to expand...
Click to collapse
Yep, I've replied to ecomajor's various posts in various threads and have basically given up. Very little info each time and having a problem that nobody else that has followed the steps has had.
Sorry ecomajor, don't know what else to tell you that hasn't already been said numerous times.

One Last Try -- Then, I Give UP!!
Read the following post on how to flash ANY Wizard (yes, that includes the 8125) --
http://forum.xda-developers.com/showpost.php?p=1177659&postcount=1
Now, follow the directions in that post WORD FOR WORD and STEP BY STEP. The only reason it wouldn't work is that you're NOT READING and/or NOT FOLLOWING THE INSTRUCTIONS STEP BY STEP.
If you CAN'T read and follow directions, then don't be trying to flash different ROMs to your phone. If you're not willing to do what's necessary to help yourself, then noone else is willing to help you, either. . . especially when your problem has already been replied to with the same information over and over in 2 DIFFERENT THREADS now.

Let me detail you the exact steps I have taken. I have read through those posts, many times so I am certain I took those steps
1)device starts normally goto step 3.6 since unsure if unlocked.
2) read farias thread
3) download buttons rom
4)attempt to downgrade rom - failed
4a)tried 1.08 rom instead of button - failed
4b)tried wizard love- failed
5)download lokiwiz
6)followed all directions -failed - since was not able to downgrade rom.
Obviously these directions are not 100% foolproof - I know that the first time I tried installing WM6, I did not read through all the threads and after much effort I discovered that if I installed the official cingular 225 rom then I could get my ppc back working but since then I have had no luck getting flashing to work. Please tell me what I am doing wrong because noone has had my exact situation. there is no need to act all holier than thou and accuse me of not reading because since I screwed up the first time I have read through all these threads numerous times.

Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?

And I've attached the ROM Update Utility Readme.doc that describes the error messages and how to fix them.

The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
mfrazzz said:
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
Click to expand...
Click to collapse

ecomajor said:
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
Click to expand...
Click to collapse
I've never tried it in safemode so I don't know if that will work or not, it was just an idea as we are grasping at straws here. But if you boot to safemode, and with the phone at the bootloader screen (hold down the camera button while you turn it on to get to the "rainbow" bootloader screen), if it shows USB above the left softkey then the computer and phone are communicating and Activesync does not matter. BTW:You can try the safemode way there at work as you will have no network connectivity in safemode so you don't have to worry about violating security policies.
You still have not answered my one question directly... Have you tried flashing the button rom to your phone on multiple computers? Or have you always done it from the same PC? And are the PC(s) that you are using running Windows XP?

What DOC chip does your device have? G3 or G4?
If you have a G4 then i guess you ruined your bootloader since G4 devices don't have and don't accept 1.xx IPL versions!!

I have tried button from multiple pcs. This time it gets up to 98% on button and then dies and it gives error 302 - update error for the button. This is a problem that I was having before.

Did you read the document I posted?? If you're getting Update Error 302, you're not going to be able to recover with anything other than the stock Cingular ROM.
Chances are that you did indeed ruin the bootloader when you tried using the ShellTool to flash a G3 phone. And I doubt seriously that you'll be able to do a warranty exchange if you can run the stock ROM successfully, so I'm afraid you're stuck now with the stock-shipped ROM.

So you are saying there is no way to fix the bootloader (like flashing it or soething) I was figuring I had screwed something up. I actually had read the document before but thanks for your help. Why is it that you can fix many other issues with the 8125 but not the bootloader?

I'm not saying it CAN'T be done. What I AM saying is that in the year I've been registered and active here, I've not seen any posts/threads about recovering from a bad bootloader. But that doesn't mean that there ISN'T a way to do it.
You might want to do a search of the Wizard section for bootloader error or recovering bootloader to see what might come up.
Good Luck!!

xda mini s installing rom from sdcard

hello all.
I'm trying to install a new rom but having great difficulty. The problem is that i cannot connect through activesync. The wizard comes on after 5 mins or so but is very tempremental and slow. I can start the boot loader screen and "USB" is in the Right hand corner. I've tried xda os tool but to no avail, I keep getting message unknown file format for the nk.nbf file.
Please could someone help me out here. I have another means of getting files onto sd card if that helps.
Thanks alot

Wich rom are you trying to install?

Any Rom. I've tried a few. Crossbow etc. Got any ideas? Which one is best to use?
Thanks

you mention that you can get to the bootloader and get the USB in the lower left. If you are there, then you can flash a rom (Activesync will not connect in this mode, but thats fine).
IF you haven't already, read and check this thread:
http://forum.xda-developers.com/showthread.php?t=298613
Personally it sounds like you should flash an official rom (you haven't mentioned if you are a G3 or G4 but since you are saying flashing and not using shelltool I'm assuming G3) to get a stable base. Then move on to a custom rom for performance, features, etc...

Yeah Its a G3. The link you gave me sounds more like it! I'm not home just now but i'll try this first thing.
Thank you very much for your time.
Well apprieciated.
Richard

Hello There. Well i've downloaded all the tools needed after waiting 70 odd minutes on rapidshare!? tried to install button rom and after 10 seconds error comes up with program not responding. I have enabled rapi on the device.
So whats the next step??
I'm using vista. could that be an issue??
Thanks

Yes, Vista can't install to a phone in bootloader mode. You have to use XP SP2.

Thought so. I'll get to a mates for this.
Thanks again.
Richard

Updating to WM6 ROMs on Vista

Hey All-
I'd appreciate any help anyone can offer. I am having problems updating to any of the WM6 ROMs out there (up here). One of a few things is happening:
1) Either RUU crashes just after it successfully sends my PDA in to bootloader mode, or
2) RUU is able to stay up, but for some reason, does not like the update file:
I either get an error: "This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.", or
it suggests the nbf file is "corrupted", I think indicating the RUU util I am running is out of synch with what the PDA is expecting.
I'm using a T-Mobile MDA (Vario?) and Vista.
I've tried all of the solutions I have been able to find:
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
* various flavors of the update utility to get around the crash, which do not let me upgrade to the ROM of choice!
* hard reset of the device
* I even tried pulling down one of the ROM upgrades from the T-Mobile dowloads site and dropping that in with a WM6 ROM nbf file. That was a huge flop.
I know people have done this! I've seen it over and over again. So what in the world stupid thing am I doing to not make this work?
Thanks.
Joel Niemeyer
Seattle

RUU doesnt work on Vista. Use shelltool.

Thanks for the advice. I'm sure it was good advice, but I am three hours in to it running now, and I don't have a good feeling about it. I think it says it would take at least 15 minutes. Not 180! Ugh, now I wonder what I should do?
Joel

jniemeyer said:
Hey All-
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
Click to expand...
Click to collapse
How do you do that? Thank you because when i try to downgrade my ROM or w/e so that i can unlock it when i gots to bootloader the fred green blue thingy it doesnt reconnect to active sync and maybe thats my probelm...=[

chaos, just look around for the RUU with Vista instructions- they are everywhere!

hey mate,
just follow this instructions http://www.modaco.com/index.php?showtopic=252977 to falsh every official ROM under MS Vista. Surely, when it comes to WM6 you gotta use the Shelltool.
regards
irm

Answer for Vista
My question is why don't people just dual boot vista with xp or 2000/etc...that would solve a lot of issues about the problems with vista.. just boot to xp..
I figure if you have the $Funds$ to spend on a $250+ phone you could shell out $50 for a 150gb 16mb cache HDD for your pc and dual/tri/quad/etc... sheeet son i've been doing this for years with linux/m$/mac.
Gotta face it, some software just runs better on one OS over another. peace out.

can someone confirm shell tool work

ANTC said:
can someone confirm shell tool work
Click to expand...
Click to collapse
I tried it, took like 6 minutes then it was completed, knowingly it wasnt flashed right, but did the hard reset on the phone and was stuck at the SPL screen, so just loaded up VMWare to reflash.

It worked for me...
I flashed one of the WM6 ROMs using my Vista Ultimate computer. One of the main parts in making the thing work is remembering to put your computer in bootloader before doing it. On post #7 in the MoDaCo thread, it says this.
Once more, here is the link: http://www.modaco.com/RUU-on-Vista-It-can-be-done-the-ultimate-guide-t252977.html

so your saying witht hat tut you flash a custom rom??

Yes
Yes I was able to. I don't remember which, but I think i was Core 2.0

Yeah, I was able to use shelltool to make this happen. Thanks for the feedback, folks. Only hang up was that it had appeared to have seized up (was seemingly stuck before the "End" portion). I waited for like 3 hours before I finally threw up my hands and hard reset the unit. Low and behold my wizard booted up in to the new ROM and I have been good to do since!

unable to revert to O2 rom

Hi Guys,
i consider myself relatively experienced at flashing HTC devices having been using and upgrading for a few years but i've run into an issue on my CID locked G4. i upgraded to WM6 without issue and i tried to revert back to my O2 rom, the flash failed and i'm now stuck at the splash screen. I've tried to flash the original ROM from boot loader but i get a 101 error unable to connect(can see it in device manager). as i'm using vista i did a search and found some instructions and driver files but i get the same result. the only thing i can think of now is to CID unlock but i'm not sure it will help (unless it allows me to do the SD card restore). any ideas guys?
IPL:2.21.001
SPL:2.21.001
GSM:02.25.11
OS:10.1.0.811

OK., what you need to do is use a PC with XP, because i have read that vista PC's can get you into a lot of trouble. When you are at an XP PC, follow the instructions in my previous post
( http://forum.xda-developers.com/showthread.php?t=313354 ).
When you flashed the original ROM, and you succeeded in doing so, think real hard if you still want to upgrade to a new ROM.
If you still want to do that, stick to a PC with XP installed (no vista!).
If you did reflash a good ROM into your HTC you'll be one step closer to upgrading your ROM.
Read this post thourougly :
http://forum.xda-developers.com/showthread.php?t=298613
as this will help you in case you didn't CID unlock your device.
(thanks vippie; this is the clearest walktrough i could find!)
If you are really sure you CID unlocked your device, you can flash your device to any ROM you think is useful to you.
If your device is really CID unlocked, you should be able to flash any ROM that is posted on this forum.
I know that it is that easy, because i have tried every WM6 ROM that is posted on this forum
good luck, and i hope in the end you will have the ROM that you want....

thanks. my device IS CID LOCKED and i've tried to flash it from 2 XP machines so it is looking like its a brick thanks anyway.
for sale wizard with pretty 3 colour screen - sold as seen!!!

One thing you can try is use another USB to mini USB cable, i have had one cable that didn't connect really well.
Sometimes it worked but if i moved my phone the connection went down.
I just thought of that because it was a while ago that this happened - I threw away the faulty cable and had no problems after that.

tried 3 different cables too

knownuser said:
tried 3 different cables too
Click to expand...
Click to collapse
How much do you want for it? I need a new screen and body shell!

jabreu203 said:
How much do you want for it? I need a new screen and body shell!
Click to expand...
Click to collapse
was actually kidding i'd like to fix it but i'm open to offers PM me.

ok .....HELP
i've paid for the CID unlock which went well i then tried to flash the O2 default rom failed error 101 (connection) i then tried wizard love failed error (300) in italian.
so stage 2 was to use the sd card recovery i ran the utility and then followed the instructions r2sd all etc..all seemed fine i restored the image to the wizard and rebooted it still won't go past the splash screen i've tried re-flashing and hard reset still no go....please guys any help???

If you have a memory card take it out. Right click on ActiveSync and go to connection settings. Uncheck allow usb connections then try to flash. With windows XP...

tried to flash on a win2K machine (4 pc's thats the only one thats not vista) still get error 101 on the original O2 rom and 300 on the wizard love rom.
still no joy anyone have any ideas???
http://www.t-mobile.hr/mdasw/RUU_Pro...R_WWE_Ship.zip fixed i'm on a tmobile rom i'll try downgrading again.

[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