Develop Bugs

HELP!!!!

:?
I tried to make an update with the file JASJAR_WWE_11353_137_10301
Suddenly the Display stop et 99% of the extended Rom Update and on my monitor was an infomation like "an error happend"
After this, nothing else happend .
Yes, realy nothing happens anymore. I cant start the device not with power, not with reset or with power+reset
nothing nothing nothing
What can i do
If i start to try a new update, it schows me no information about what rom etc. is installed or what will be installed. if i then start i get the notice, that it is the wrong device.
Help me please. ist there any way to put the mda back to live?????
I guess i dont only need an update but the complete software

HELP!!!
I have the exact same issue after the upgrade. Nothing will happen. I spent several hours trying resets, combination of button pressed, removed battery, resets, just to try to get back the boot loader mode but nothing is happening.
there has to be a way to do this and I hope someone on this board had that issue before and got it resolved.

I had a similair issue with my old XDA II, it turned out my storage card was corrupted. Use a card reader to check your storage card is OK, perhaps format the storage card (having saved any data first of course) and see how you fare

Have had the same problem wirh a radio ROM update on my QTEK9000. The anly thin that still worked was the hard reset. After the hard reset the device still did not respond. But when i connected it to the PC I could start the updateprocess of the original ROM. I took about 20 minutes for the whole procedure and than the Qtek9000 was back in factory default (Pffff and I could breath again).
So perhaps you can try a hard rest and then connect aganin to the PC.

I allready tried this!
But nothing happens.
Even if i put the power device or the usb into the mda, no LED schows anything. just sometimes the LED is red for not more than a minute. if it then goes out, i get the message "Unknown usb device" in my PC

Are you in bootloeader mode? Do you see the words USB or Serial on the screen of the Universal in Portrait mode. Note: Backlight is off so you have too look real hard, but it should be there

no, i see nothing.

I had quite a hard time yesterday while upgrading. The bootloader is very hard to see, use a torch to lite up your display. In portrait view on the top should be the word serial or usb, on the bottom v1.00.
I also did a hard-reset in this stage, but it just returned to the bootloader menue.
If I connect to the PC and the device is recognized I see the word serial in the display change to USB. For me I do not know the reason but my PC did not want to fulfill the upgrade process. Needed to take another PC (Laptop) to solve the problem. After the upgrade of the ROM, You still need to upgrade the Radio (this was my experience) before a cold-reset will put You back to business.
Good luck.
Ruud

Having the exact same problem as gary_b and having performed quite a few upgrades, I can confirm there is absolutlely nothing on the screen. The unit will not go into bootloader mode or even able to do a hard reset. It is not recognized when plugged in the USB.
When connected to power and the hard reset procedure is done, the red charging light will come up for less than 1/2 seconds and disappear.
I tried all different combination to make it boot but nothing. If I could at least get it to bootloader more, I can revive it.

Feel very bad I cannot help here.
I was wondering Yesterday about one thing. IF, during all this upgrading process, the battery runs out, (as it does not seem to charge during upgrade process) will it show bootloader screen ?
Would it be possible to get a loaded battery from somebody to check yours ?

That is a good suggestion to try out, but I have been unable to find anyone that has that device. It might be simply a drained battery.
Mine got corrupted I think at the end of the upgrade right after I did a regular reset instead of teh power and reset procedure.
However, I would think that even with no battery in, the unit should power back up when plugged in no?

Maybe an idea for somebody who is doing upgrading now, and is in bootloader status anyway.
Take out the battery, but connect with USB to PC with ASync. Does the bootloader state show ?
I am sorry to not do it for myself, if You saw my desperate state Yesterday, You will believe that I am not willing to see that bootloader screen for some time, sorry.
Ruud

now i know what to do:
Nothing!!
I went to a service-point with my mda pro and there was nothing to do with it.
If this happens the complete memory is "killed". Like "format c:" and while format is running you switch out the power.
Thanks god: I got a new MDA pro because i did not tell them (in the store)that i tried an update!
But i called the service-line before anf they told me that there is nothing to do!
But thx

Wow, can't say that this is good informatuin for those with this problem, but very glad it worked out for You.

I ve had this problem 5 minutes ago. Finally a took out the battery. Then connect to AC and Red led is on. Then i put the battery, tried hard reset and message to confirm hard reset in the screen (wellcome to life, jasjar).Then i run radio update again and it's upgrading rigth now....buffffff

I almost suffered a heart attack when this happened an hour ago. Have found that the update works fine if the SD card is taken out... phew.

Not even stuck at Bootloader :(

Please help!
I just upgraded my ROM to Ivan's latest AKU3.5 from bootloader
This completed successfully (100% successful, disconnect and restart etc)
I disconnected and reset, except it was stuck in bootloader mode
I tried the Mtty method (for the first time ever) and followed the step by step instructions...
...after a few seconds a few command lines appeared with "USB>" on the last line
I took this to mean the process had finished (?), disconnected the device from USB and tried a soft reset
the device just stayed stuck in bootloader
next, i downloaded uni_exitbootloader and ran it (as this has worked for me many times in the past). it didn't work the first few times, but i disconnected and reconnected and this time it worked. It said "data sent, you can now reset your device"
This maybe where i went wrong?
I foolishly reset the device before disconnecting it from the USB. The PC immediately said "USB device not recognised" and the screen of my Universal went blank
Now, if i soft reset, it does nothing, i cannot even put it back into bootloader using the camera, on, reset button combination.
HOWEVER, if i press the two soft keys (as if i was going to do a hard reset) i get the white screen with the black text saying "Press 0 to restore etc"
If i press 0, it says "clearing" but the screen just goes blank
If i press x, the screen just goes blank
Now i am completely unable to try and use either mtty or exitbootloader as my PC just says "USB device not recognised" and neither applications run as they should
QUESTION: Have i totally bricked my Universal?!
If not, what can i possibly do...???
As usual, i will be extremely greatful for any advice or assistance to resurrect my favourite Pocket PC!
Thanks in advance for your help.

Aaagh! I think i just realised what i did...
1. I didn't read the posting "For all those stuck in the bootscreen, try the Mamaich method" carefully enough. I didn't realise that the Mamaich method totally erased the ROM!!!
2. By not flashing a new ROM to the device immediately and instead using exitbootloader to exit the bootloader screen i now have a device that has no ROM and probably has no way of knowing how to get into bootloader mode.
Can someone confirm this?
For one, i feel like an idiot for not reading the posting carefully, but having admitted to being stupid,...
... is there anything at all i can do???
Please help...

cancel that, you already said what i was going to ask above

have you try to flash it again with original ROM? sometimes it helps!

Once in bootloader mode, try plugging it into a different USB port, one directly on the PC.
I have had this where one port says not recognised, even after having been plugged in and used for ages, then I go to flash it and it won't work.
Another port has worked for me.

Since you ereased the DOC, all you've got to do now is to reflash the default ROM.

Thanks everyone...
Only problem is, i cannot get it into bootloader mode. And every port i plug it into (so far) says "device not recognised"...
Nevertheless, i did try to reflash the device, but it just gave me the "Error 150" message. It just doesn't know the device is connected i guess?
I think if i hadn't done the Exitbootloader step then i would have been able to reflash it. However, now that i have... i'm a bit stuck... any ideas of other ways to get the device into Bootloader mode?

try
you already know there is a file called EXITBOOTLOADER but did you know that here is a file called ENTERBL ?
try it .....

Thanks dhob187!
Where might i find this file though? Did you mean to attach it?
Just one other question...
How does ENTERBL work if the PC doesn't recognise my device i.e. "USB device not recognised"? Will the application override this and push commands to my pocket pc anyway?
Or is there a way i can get my PC to stop rejecting the device when i plug the USB in?
Thanks in advance,

I believe this is the file u needed
i don't know how this utility works, but just yesterday i stuck in the bootloader after upgrading my uni to AKU 3,5 and solved with ExitBootloader.exe. CMIIW it works the same way, just plug the USB cable then execute the utility (just simple as that).....
but have u tried my earlier suggestion? my friend got the exact problem like you (blank LCD not even bootloader), he was downloaded the original EXEC ROM and try to flash with it (with original upgrade utility also). and the thing start to blink, enter the bootloader and flashing!.....after he manage to wake the device up, then he tried to flash it again with the newest ROM and succeded........
sorry for my english.....

Please don't apologise for your English, thank you for your suggestions!
I didn't quite understand your initial post... but i do now.
Does it have to be the first ROM that it was shipped with or just an original i-mate JasJar ROM?
I can't try it now, but i'm excited to go home and give it a go later tonight... what's more i'm excited at the prospect that there may be some hope for my currently rather expensive paperweight!!!
If the aforementioned doesn't work, i'll try using your attachment.
Cheers again!

it doesn't have to be the first rom that shipped with your imate, just an original one. try your luck then! never give up, keep the faith!!!

sorry, forgot one thing, just ignore the USB error (not recognized) and go for the upgrade (execute the original upgradeUt.exe)

Hi Rudy173.
Thanks for your help, but unfortunately nothing has worked
I have tried running two official JasJar Roms without success... i always get the connection error message (this is surely because the PC always says "device not recognised" when i plug it in).
Also, when i run ENTERBL.exe i just get a failure saying that ...ENTERBL.exe is not a valid WIN32 application... etc...
So unfortunately, i'm still stuck... any further suggestions anyone?
Can the i-mate service centre help me? Is it likely to be expensive?

Back in business )
Wow, not entirely sure what i did... but my Universal is ALIVE!!!
As per the previous post, nothing seemed to be working so i removed Activesync 4.5 beta and reverted to 4.1. I then tried to reflash to an original ROM and the same "connection error" problem happened.
However, next time i tried to enter bootloader, by pressing light, on/off and reset, it went straight into bootloader and i was able to reflash from there
I didn't even need to reflash with an original i-mate ROM. I went straight for Ivan's latest.
This experience has taught me a few things:
1. I have become seriously attached to my Universal!
2. You should never give up hope of retrieval!!
3. This forum is full of very nice helpful people!!!
Thanks everyone.

wow! glad to hear that!
Happy ending....................

What is this?

Im a new comer. The 1st time I upgrade my XDA exec but not successfully. I couldn't remmember which ROM i used but it suddenly cancelled when it was running (nearly 90%), I pulled out the cable when it hadn't finished yet. Now, my Exec doesn't work, I can't see blinking orange or green light, only red light appears when I plug in the cable.
I don't know which errors I met and don't know how to resolve this, I need your help, please!

oriolemax said:
Im a new comer. The 1st time I upgrade my XDA exec but not successfully. I couldn't remmember which ROM i used but it suddenly cancelled when it was running (nearly 90%), I pulled out the cable when it hadn't finished yet. Now, my Exec doesn't work, I can't see blinking orange or green light, only red light appears when I plug in the cable.
I don't know which errors I met and don't know how to resolve this, I need your help, please!
Click to expand...
Click to collapse
RTFW and reflash using bootloader.

hic hic
I'm still elementary, i cannot totaly understand those words, could them be more clearly?

1st: Download a working ROM like this: Helmi 3.5 v 1.3.1: http://www.megaupload.com/?d=3S300TQ8
Everything is already in there with the exception of the RADIO ROM (radio_.nbf) and the EXTENDED ROM (ms_.nbf). These you can leave alone, in your case your device will use the old existing one. If you want to upgrade to the latest RADIO ROM. Look for Radio 1.18.00 and copy radio_.nbf and add that file to the folder you already have.
2nd: After extracting the files and placing them on one folder. Place your device on boot loader mode by PRESSING THESE SIMULTANEOUSLY:
POWER BUTTON
RESET PIN HOLE
BACKLIGHT BUTTON
3rd: Connect your Universal via USB cable.
4th: Double tap Ma Upgrade NO ID file to run it. Just follow the screen commands.
---

- The only thing seem to be "alive" in my PDA is RED LIGHT
- Everything doesn't work anymore
- Nothing appears on screen when SR, HR
- Cannot get into Bootloader
It's my EXEC

oriolemax said:
- The only thing seem to be "alive" in my PDA is RED LIGHT
- Everything doesn't work anymore
- Nothing appears on screen when SR, HR
- Cannot get into Bootloader
It's my EXEC
Click to expand...
Click to collapse
It might appear that way.
If you check the screen in boot loader mode under a good light. You will notice the screen has version numbers on it. That is normal. The backlight screen DOES NOT turn on when in boot loader mode. So check it under a nice lighted area.
---

Anyone thinks this is a Flash error?

oriolemax said:
Anyone thinks this is a Flash error?
Click to expand...
Click to collapse
If you are still unable to enter bootloader, remove the battery, wait 10 seconds, re-insert the battery, the hold the backlight whilst pressing the power button. This should get you back into bootloader mode, there is no back lit screen when in bootloader, but if you look carefully you will serial or usb on the screen.
Now re-flash a decent Rom.
Cheers,
Beast
ps, never remove the cable untill the flash utility tells you to!

hic
I removed it for 10... hours. Nothing but "USB Divece not recognized!"

oriolemax said:
I removed it for 10... hours. Nothing but "USB Divece not recognized!"
Click to expand...
Click to collapse
So I assume you can go into boot loader mode now...
On your computer, use the built-in file manager to kill these 3 applications prior to attaching your Universal in boot loader mode via USB:
1: rapimgr.exe
2: wcescomm.exe
3: WCESMgr.exe
Good luck...
---

When it says nothing at all!!!
Hic, I'll kill this EXEC!

I've sent it to many machinists, all of them have no ability to resolve such problem. I put my EXEC on a bed and take them to jungle, waiting for a prince to rescue.
My EXEC still deeply sleeping....
hic...

Upgrade ROM code error

I have flashed many Custome ROM's before. I have HardSPL installed on my phone.
I tried flashing to a ROM (I forget which one now, I think Cloudfa or something) and it stopped at about 15%. The Update utility stopped as well.
I cannot connect to bootloader at all. I tried holding down on Volume down/Reset to enter bootloader, but the thing is that it's already in bootloader with the message "Upgrade ROM code error, Please try again"
ActiveSync doesn't see my phone either. In fact all it does is just sit on the bootloader screen with that error...
Please Help... Thanks You...

A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?

band27 said:
A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?
Click to expand...
Click to collapse
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...

jzalapski said:
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...
Click to expand...
Click to collapse
Have you tried flashing a different ROM while in bootloader?

^^ Yes. It give me an error on my computer...
I would like to try the internal flashing method but I don't seem to have a way of getting at my Storage Card.
I found this thread with a similar problem
http://forum.xda-developers.com/showthread.php?t=480022
I WAS just able to get off of that screen I was talking about, but the best I get is to the Touch Diamond Screen that lists my ROM and such. So no real progress.
I have a feeling that I would resolve my problem if I could Flash from the Interanl Storage...

Have you tried hard resetting the device?
Pull out stylus and Holding....1) Vol. Down 2) Center Round button 3) then press red button aka soft reset with stylus

Nothing...

im stuck
hi all i am very new to this im not sure what i have done or how to fix the problem i download these this morning and they worked
rom version 1.57.831.1(47324)wwe
radio version 1.14.25.24
protocol version 52.64.25.34u
when i bootload in tri colours screen it shows
BLAC100 32M
SPL-1.56.OliNex
MicroP-Blackstone (led)v6
if it shows that i must of done something right i think of what ill read
and i have windows 7 ulitmate and i have Miri_WM65_21815_V19.0_Premium
when i double click on the BLACKSTONE RUU WRAPPER it crashes then i rename a new folder and done it from there and it works but it comes up wit error 208 file open? then i got told to rename to ruu_signed.nbh file to blacimg.nbh and to store it in the root of my sd card done that then somehow i got it to come up to the screen by Turn off the phone, press and keep pressed volume down button and while keeping it pressed turn on the phone then i see a message "Press power to flash your device" and i press power to flash got to 0% and it crashed and come up with Upgrade ROM code error plz try again and stuck in bootloader mode but now it wont even turn on its dead it wont turn on no matter what i do can someone plz help
all i want to do is get windows mobile 6.5 working i cant understand that it can be so hard to do
thanxs blueboys25!

[Q] HTC Desire Dead Screen

I have an A8183 from Telstra Australia. I rooted it using the revoked method, following the Telus Desire HBoot 0.83 Root and Flash guide on these forums. (new member unable to link).
I had the Cyanogen mod installed on the phone but didn't really like it. I wanted the HTC sense ui back so I tried to run a few generic RUU to get it back to normal.
Of course I got the Error 130 (Model error) or whatever it was. So I tried the Telstra RUU. I then got Error 140 (Bootloader error) and read around and found out I needed to downgrade to bootloader 0.80. Obviously did not realise this would affect the SLCD screen and remove the display drivers for SLCD to work.
I now have a phone with no screen, it boots and I hear the noises, but no display - not even in the bootloader or recovery mode. I tried putting the FroYo OTA on my gold card, renaming it "update.zip" but it didn't work, probably because I think I have a custom recovery mod I got from following the thread I linked above. Can someone please give me a noob guide to fixing this?

Use your gold card and flash WWE RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
Your screen is going to come back(the above RUU is SLCD compatible) and then download your Telstra RUU and flash with your goldcard(make sure RUU is SLCD compatible)

I've tried lots of RUU's and it takes about an hour to download one. The ones you just linked look similar to the ones I've already tried. I'm currently downloading it, as well as the Froyo one.
Will post back in an hour or two as to what happens.
EDIT: It says there is a problem with the USB connection whenever I try to run the RUU...How do I fix that? My computer recognises there is something plugged in, and the charging light is on my phone.

I tried this:
1. Remove the battery
2. Insert the gold card
3. Hold down volume down then press power
4. Blindly press power again to get into fastboot???
5. Run: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
and/or Run: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
On step 4, windows recognises a USB device but fails to install the driver. I went into the device manager and there is "Android 1.0" listed there. I tried to update the drivers manually by using the ones in the AndroidSDK. I'm assuming this has something to do with what happens on step 5. *UPDATE* Installed HTC Sync with the driver, uninstalled HTC Sync, windows picked it up. Windows required a restart before I was able to flash any ROMs.
On step 5 it gets up to the screen where it says "Gathering information about your android device" (or something). It times out and says Error 170 - Usb connection error.
*UPDATE* restarting the RUU fixes the USB connection error, however ALL of them give Error 130 - Model invalid. The only RUU that works is RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851.exe and unfortunately that has already been flashed onto the phone - so it does not fix the screen. If anyone knows of an RUU that will work with my phone? Or perhaps a Telstra one that actually works and restores my bootloader or something.
Someone pleeeeeeeeease help

From what you say, I think the LCD is bricked but the phone is working otherwise. Just to confirm power on the phone and let it boot normally. You should hear the boot sound and then after 2-3 mins try calling from another number to see if it rings.
Once it is at that stage, connect the mobile to PC via usb. Ensure htc sync software is installed (Not the drivers alone, but the full htc sync software). Then run the .exe that is compatible with SLCD. Your phone should get flashed. You cannot see anything on the mobile screen yet, but you can see the status on your computer.
I am not sure if RUU flashing will work from recovery/fastboot screen..... I am guessing you get the timeout error cos the phone is not booted. Give it a try.

Yes, Yes to all of that. Like I said, the only RUU that works is the Telstra one atm, and that is already on the phone. Like I said, I flashed that after downgrading to bootloader 0.80. All the other RUU's that I have tried to flash give a model id error.
If anyone can point me to an RUU from Telstra that enables use of the screen I would like a link please

I may be giving you a wrong advice, but have you tried to turn the phone on while pressing the back button? (not the volume down, the back button), and flash a compatible RUU?

Yea I've tried that with most of the RUU's that I've downloaded. It just gives model ID error. The only compatible RUU that I've come across is this one Telstra one that I've found on this forum. None of the other generic ones seem to work. I can't seem to find another Telstra RUU that will work. I have no idea if the phone is even still rooted, or what version the bootloader is (My guess is still 0.80 - even though it needs to be 0.83).
I'm unable to re-root the phone with a method like unrevoked because I can't enable USB debugging (can't see anything) and unrevoked doesn't find my phone.
At the moment I'm just playing around with flashing different RUU's remaking my gold card, installing/uninstalling HTC sync, flashing RUU in what I think is the bootloader screen, what I think is the fastboot screen, and when the phone is fully booted. (This would be a whole lot easier if I could see what was happening).
The only luck I've had is re-flashing the original Telstra RUU which does nothing to the screen...
(not the volume down, the back button)
Click to expand...
Click to collapse
- What does that do?

Turning the phone on with the volume down key pressed takes you to HBOOT menu
Turning the phone on with the back button pressed takes you to the fastboot menu directly, if I'm not recalling bad you need to be there to flash a RUU, It's worth the try...

I tried it with the back button - Same deal Error 130 - Model ID Error.
Apparently you can fix that with a new gold card. I read somewhere else to remake your gold card step by step. One of the steps requires USB debugging to be on your phone to record the serial numbers listed in the command prompt with the phone plugged in. I already have goldcard.img and have tried putting it on multiple microSD cards, I now have no more to try out.
Anything else I can try?? This is my only phone :S

I am not an expert on flashing, but I had bricked the LCD on my desire before. But mine was unbranded and flashing a unbranded RUU that got my phone and display working again.
What I would suggest is you can try flashing an unbranded WWE Froyo RUU that is compatible with the SLCD desire. If you have the gold card, you can flash any RUU to your phone (That is my understanding)
If you are not able to flash any other RUU, maybe the gold card is not proper. As far as I know, you should use the .img only on the sdcard which was in the mobile when you executed the commands. using .img generated with one card on another sd card will not work I think. At least it didnt for me.
Also the RUU is not bothered about the Hboot version on the phone. An RUU will have it's own bootloader and it will flash it onto the device over the existing bootloader
And above all, do not panic. The device can be recovered and restored. It is just a matter of time and patience and trying out a few things.
Edit: I forgot to ask, Do you have a nandroid backup done immediately after rooting?? If you have done it you could save yourself a lot of time by just restoring it.... If you have not backed up, then Lesson No 1 in rooting -> ALWAYS do a nandroid backup before you do things.

I think I have to agree. After about 20 hours of trawling forums I am 90% sure that I screwed up the initial gold card. (unrevoked doesn't require a gold card - so I thought it worked).
Is there a way to create a new gold card without an android phone? If you could point me to a guide that would be awesome. Obviously I'm prepared to buy a new microsd card to fix my $900 phone :S

Do you have USB debugging enabled?? If it is enabled, you just need the phone to be booted to create goldcard. Insert a formatted sd in the phone and boot it up, connect via adb and generate the CID numbers and try to make one.
If usb debugging is not enabled, then you can play "blind" game and try to enable it without the screen. It's tricky but certainly possible.

It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome

lordmitchell14 said:
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
Click to expand...
Click to collapse
If you search for lcd brick fixed, you should find a step by step guide to turn usb-debug on.
To flash a ruu, your phone needs to be booted in android normally, the ruu reboots it in fastboot itself. If you get an error flashing the ruu, try updating the android phone drivers. Even if Windows said it didn't update, try the ruu again. It worked for me with a friends phone.
Sent from my HTC Desire using XDA App

Well here are the steps..
1.Power on the phone and after 2-3 mins, press the power button to load the lock screen
2.Swipe down to unlock.
3.You should be in homescreen if device just booted. Press menu and then press the spot immediately above the search button. This should take you to settings screen
4.Now swipe long strokes with your finger "down to up" 4-5 times on the screen.. you are now swiping down the list.We need to make sure we reach the end of it.
5.Once you reach the settings list's end, the "Applications" link will be located just below the volume "+" key. about 5-7mm below the + mark. press the spot.
6.Now you should be inside the applications. Now keep swiping down on the trackpad. Do it for 10-15 times no problem. There are only 4 items in the list and doing it many times will ensure the selection is now on "Development" which is the last item in the list
7.Press the trackpad. The development should now get selected
8.Wait for a second. Press the trackpad again(No up/down). USB debugging will get selected.
9.Wait a second. Press the trackpad again. The popup "ok" button will get selected.
And you are good to go
Connect to PC and see if you can connect via abd.
This is assuming that Debugging is turned off. If it is already ON, then doing this will turn it off. So first check if you can connect via adb before attempting this.

I followed all the steps in this guide: http://forum.xda-developers.com/showthread.php?t=750852
I even spent an hour getting the debugging to turn on.
I managed to root my Desire again and got down to step 35. Unfortunately that RUU gave a model ID error. Just like all the rest.
Thanks for all your help guys, although this is driving me insane :S

*BEGIN DANCING*
thanks to the awesome guys at http://code.google.com/p/androidscreencast/
After playing the blind game and turning on USB debugging, I was able to use my computer as a screen which made things a whole lot easier.
After following the guide linked in the post above:
- I bought a new microSD
- re-made the gold card
- Followed steps 30 onwards...
- ran the RUU several times (it finally worked whilst in boot mode)
- AND MY SCREEN TURNED ON F*%K YEA!

Great to hear!!!
Now do a Nandorid backup and then you can go about trying out any mod/rom you want and you can always get back your original state with a simple nandroid restore.
And that ScreenCast looks interesting... will give it a try