Database Users

Please help - bricked XDA Orbit II

Hi, first post on the forum so please be gentle with me....
I have an XDA Orbit 2 which was until last Thursday working fine with the last official upgrade from O2 (Win 6.1, no idea about all the other stuff).
Whilst using the phone last week it suddenly died in the middle of a conversation. It wouldn't power on at all. I took out the battery, waited a couple of minutes, put the battery back in and switched it on. All that happened was the phone displayed the 4 colour screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white. I repeated the battery removal exercise a few times, waiting for increasing lengths of time but nothing changed.
I had a fairly long search through the forum and have tried for a few hours now going through the various fixes suggested but I am getting nowhere.
It won't hard reset, all that happens is the message "No Image Found" appears for a very short time and I then get stuck on the 4 coloured screen with the message above.
The same thing happens if I try just putting the thing in bootloader mode.
I can't use any of the official O2 rom upgrades as the phone because all the PCs I've tried connecting to it won't recognise it over a USB link.
I've tried connecting to it using mtty, again on several PCs, but I just get a message "USB port can not open". Just in case I've uninstalled Activesync on one PC and got the same answer.
The "how to flash you polaris using the microSD card" originally looked useful but I have some problems with it.
The first is that I need HardSPL installing on the device, which I can't do because I can't get to it.
The second will be down to me not knowing where to look, but I can't find a ROM to download and copy to the microSD card as POLAIMG.nbh. I did manage to find a Win6.5 one (the HTC Polaris - PDaviet rom wm6.5 manilla 2d (core 23004) by tranminhman one) which I thought I'd try. I guess the idea was that if I could just get something working I could always reflash it again with a different ROM or maybe apply the o2 upgrade. Unfortunately the image was password protected and I couldn't find the password in the thread.
I'm kind of at a loss now so any help would be appreciated.
Cheers

Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan

Did you do soft reset

alanazar said:
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Click to expand...
Click to collapse
Bit in bold er... cant quite understand why in iolite section as the xda orbit 2 is the rebrand htc touch cruise => htc touch find. Its in the right place.
On the side of what to do i the ony thing i can think of would be mtty and if that didnt work then try to reflash the official o2 6.1 release and see what happens when you try to do it.
You cant try to install any 3rd party roms they jsut wont flash as you dont have hard spl installed and cant do that until you have it running again.
Try the above and see what happens...

Hi Nik
I have tried just about every kind of reset, nothing has worked.

Hi Alan
If I can't get it sorted any other way I'll probably send it off somewhere but I'd like to have a go at fixing it myself. It will at least be a bit of fun!
I take then that I've posted this in the wrong forum. Oops, apologies.
Jon

You have not posted in the wrong forum look at my signature!

Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
1a) Extract shipped ROM by WinRAR , take RUU Signed.nbh
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]

Nik Ahmad said:
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Click to expand...
Click to collapse
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon

jonfsharp said:
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
Click to expand...
Click to collapse
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend

have u tried this?...
turn off, pull out the battery, then put it back, charge ur phone till the battery indicators shows green (which mean it's already fully charged) then... power on ur device.
it looks like a dumb suggestion , but... i have had a same situation
(HTC KAISER, not Polaris).
if it doesn't work, then try to upgrade with a POLAIMG.nbh (take it from official HTC ROM)
in a 2G FAT32 microSD root directory.

Nik Ahmad said:
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
Click to expand...
Click to collapse
Thanks Nik
Much appreciated.
Downloaded the ROM as suggested, unzipped to the SD card, renamed the image to POLAIMG.nbh, stuck it in the phone and things got slightly more interesting.
In bootloader mode I now get a bit further. I get a grey screen which says "Loading ..." then "Checking...." then "00028002 Not allow". It then goes back to the four coloured screen as before.
However, does the fact that it is trying to read something mean that I have just got the wrong file?
I'll try a few more and see what happens.
Thanks once again, your help is greatly appreciated.
Jon

Hi oza
Yep tried all the battery pulling out stuff but got nowhere.
The ROM thing on the SD card gets further. I extracted the ROM from the official O2 upgrade, stuck it on the card and renamed it POLAIMG.nbh.
If I put the phone in Bootloader mode I now get even further than before. I get a grey screen with:-
POLAIMG.nbh -
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
OS -
Press power button to start update image
Press action button to cancel update image
If I press the power button
I get an "Update In Progress" message and a progress bar.
After about 4 minutes I get a full progress bar and :-
POLAIMG.nbh - OK
RADIO_V2 - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
Update complete
UPDATE SUCCESS
And that's as far as I've got so far.
If I take the SD card out and try a hard reset I just get stuck on the 4 coloured screen I got before, but with no No Image Found message.
I get the same thing with bootloader mode and when I just remove the battery.
If I put the SD card back in I can go through the update process but I can't do anything
else.
So, have I actually made any progress? I'm not actually sure what I have updated and what state the phone is in at the moment. Is the fact that this didn't work an indication of a hardware failure and I should send it off somewhere.
Any advice on next steps would be good.
Jon

what is ur bootloader screen says now?
IPL...
SPL...

Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?

Try this one M-AMINES if the radio you had was a 1.59.xx radio as it has the radio included.
if it was a 1.65.xx radio then try the VLIT naked rom.

oza_crazy said:
what is ur bootloader screen says now?
IPL...
SPL...
Click to expand...
Click to collapse
Hi Oza
Exactly the same as it did when it first broke. I get the 4 coloured screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white.
No idea what the IPL is or was I'm afraid.
Jon

bally3 said:
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Click to expand...
Click to collapse
I've not been a big modifier in the past so it was just using the bog standard O2 software from the O2 website. The name of the file is "RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe" so I presume that there can be information gleaned about things like the SPL, ROM and radio versions?
Not a complete nunce, no, but so very far away from being comfortable with all this. This post was a result of a good few hours trawling through the forums looking for help. Anything I have done has been the result of a post on this site and I am very grateful that there are people willing to share their knowledge.
Anyway, as for hard spl, nope it isn't installed. I'd never needed anything like it before the phone died and now that it has died I can't get onto it to install anything.
Yes, this happened right in the middle of a conversation after a good year or so of normal day to day use. As I said, I haven't needed to make any changes to the phone so the only thing I've ever done is upgraded it with software from the O2 site.
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon

jonfsharp said:
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
Click to expand...
Click to collapse
Well whatever you do dont bin it, we can always use it on the Android project if you decide to go that way.
Ok.. so lets see.. the phone is not picked up at all in windows?
If that is the case, if even a serial connection cant be made then theres issues. At this point, I would disregard all the other advice as it only applies to a hard spl device unfortunately. SD card flashing and all other radio rom flashing will only work with hard spl as far as I know - definitely safer for certain and you dont want to wreck a repairable device.
I take it, its not under warranty, for your mention of costly repair.
The important thing at this stage is a serial or usb connection from a Windows PC. I think I have heard of forcing this connection by opening the device but this would really be in the realms of profficient repairer or enthusiast.
I'll have a look but also do some searching yourself for making a connection to a Windows PC and forcing an SPL onto a phone.
I dont know whether anyone's ever managed to HardSPL a phone using a memory card? Just a thought...

Who would have known.. have a read of this and see if you can follow it up regarding the spl through sd card ..
http://forum.xda-developers.com/showpost.php?p=3273438&postcount=7

[Q] Need Help - Android snag

Hi all - I'm in a bit of trouble.
Tried changing the OS to Android and must have made a mistake somewhere along the line.
Was using ROM update utility MAGDLR V1.13 and got as far as updating the ROM Was told that the screen should go black and if it didn't, then I needed to perform a reset.
I did this and now the screen just shows the htc logo on white background.
Irish phone - got it august '10. recently upgraded ROM from HTC site to version 3.14.405.2 but not sure now whether I've wrecked it completely.
Was just sick of WinMo and wanted a change - can anyone help please?
ND

boot into bootloader and start again. do you have hspl? right radio?
get into bootloader. flash magldr. then flash nandroid.

you probably need to downgrade the rom to get to hspl 2.08

Thanks - I got the correct HSPL and installed it on the phone, that part was fine. The problem now is that the handset isn't even acknowledging when it's plugged in. And when I connect via USB, the computer isn't registering any connection to it.
I think it's toast! The only thing I can see is a white background with green htc lettering i.e. welcome screen
Thanks for getting back to me, any other ideas?
Will I be able to reload original windows back on by myself?

Try windows 7 XP sucks doing this kind of stuff
Sent from my Nexus One using XDA App

ndonovan said:
...The only thing I can see is a white background with green htc lettering i.e. welcome screen...
Thanks very much for the response. As above, the handset is completely unresponsive - it's not even showing a "charge" when plugged in.
Any help greatly appreciated
Many thanks
Signed,
Cracking up
Click to expand...
Click to collapse

Can you get to bootloader?
(power on while holding vol. down)........
If so, get to bootloader then connect via usb. The word serial at the bottom of the screen should change to USB. This sometimes takes a few minutes (for me anyway)
Once it reads "USB" flash a WM6.5 Rom in the usual way.......
If you cant get to bootloader then theres a good chance you've somehow borked your device......

Thanks everyone and in particular jsmmcabe and conantroutman
I got into bootloader and I'm trying to reinstall the windows os from there.
will let you know how I get on,
thanks again guys - lifesavers

I should have mentioned that flashing a stock 6.5 rom will wipe HSPL.
If you flash a stock rom then you will need to reinstall HSPL before attempting any MAGLDR/NAND shenanigans... (sheNANDigans?? see what I did there )
If you flash a custom ROM from XDA then your HSPL will be ok......
Also should have mentioned the age old "NO .51. radios on a tmous" advice.........
Good luck.......

Well after all of that I went to Pirate Bay, downloaded an Android 2.2 file, copied it onto my SD card and ran it.
Hey presto, I have an Android Phone!
I cannot begin to tell you how much better it is. It's fast, it doesn't freeze, the whole interface is much cleaner and easier to use.
SNAG ITEM:
Tried doing the same with a friends phone and when activating the copied files from the SD card, the thing just hangs and I have to reset the phone.
Any idea why it worked on mine and not his?
Same phone, bought in Ireland, a week apart. Different mobile operator networks though..... I'm Vodafone, he's O2 - weird, no?

ndonovan said:
Well after all of that I went to Pirate Bay, downloaded an Android 2.2 file, copied it onto my SD card and ran it.
Hey presto, I have an Android Phone!
I cannot begin to tell you how much better it is. It's fast, it doesn't freeze, the whole interface is much cleaner and easier to use.
SNAG ITEM:
Tried doing the same with a friends phone and when activating the copied files from the SD card, the thing just hangs and I have to reset the phone.
Any idea why it worked on mine and not his?
Same phone, bought in Ireland, a week apart. Different mobile operator networks though..... I'm Vodafone, he's O2 - weird, no?
Click to expand...
Click to collapse
Could be its not booting because of an incompatible radio....
must be above 2.08.50..... you can find this info in settings about phone...
Also, why download android from the piratebay???
Everything android related you could possibly need is here on XDA.
Personally Id be suspicious of anything from a site like that. Theres no way of knowing whats in that Rom. I would change to a well used and trusted build from XDA if I were you.
Theres no exact science to getting this running on different phones, what works for one may not work for another......

[Q] can I flash a non-US ROM to a US HD2?

I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?

Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.

flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.

Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.

Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.

hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.

Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.

gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.

samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.

@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!

gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.

[Q][Nov. 16]upgrading my htc hd2 TMOUS

Good day to all esp. to the masters of XDA,
First off, I'd like to apologize if there's already a thread like this or a kinda sorta thread like this. I've tried searching but haven't found answers really pertaining to my inquiry. If you do know a thread please point me to it, sorry for the trouble.
On to my question: I have an HD2 TMOUS with stock rom ver. 2.10.xxx, I would like to upgrade to stock rom ver. 3.14.xxx. I would like to know if I could upgrade directly to 3.14.xxx or do I have to go through upgrading to the versions in the middle of 2.10.xxx and 3.14.xxx before going to 3.14.xxx.
Currently I have SPL-3.03.0000 which I've installed using HSPL4. Do I have to uninstall this and go back to 1.66?

Hey ralfkof119, this topic have been discussed several times. Since I'm in a good mood today I will point you out to the right direction. Yes you can download directly from 2.10.xxx to 3.14.531.1
1) http://dl.htc.com/ruudownload/t-mobileUS/DeviceDownloads.aspx?pid=leo2
2) type in your 15 digit IMEI number then press SUBMIT.
3) download the file to your desktop.
4) connect your phone to the computer and let it synchronized
5) backup all your personal information because it will factory reset your phone.
6) double Tap on the file you just downloaded follow the steps and VOILA'.
your phone should bow be Tmobile official 3.14.531.1.

Thanks for the reply. I read in the link you gave me that I can update directly to 3.14 so I tried it but upgrade doesn't go successfully, I always get error 262. So I searched the forums for error 262.
Although there wasn't much about 262, the threads gave me an idea to use task 29 before installing 3.14. So I installed HSPL 3.03 with HSPL 4 and tried task 29 and then run the 3.14 ROM downloaded from your link and it went successfully.
I just want to know if I did it right. Although it is working now, I might've messed something up to cause a major bad later. Please do confirm. Thanks again.

Yes you did it right.

Error 262 is because you were running the update with winmo running, so step 1 when you run the .exe is the phone restarting into bootloader, by which time the USB connection has timed out.
the method you ended up using, you entered bootloader manually and then established the USB connection, so no timeout.
when you received the 262, had you simply run the .exe again without touching the phone (which had already entered bootloader) the flash would have worked.
Summary, when flashing rom/radio/hspl, put the phone into bootloader manually first.

Ohhhh.... Thanks samsamuel. But it is still good practice to do a task 29 just to clean things up ^_^.
I'll be sure to remember that samsamuel.

ralfkof119 said:
But it is still good practice to do a task 29 just to clean things up ^_^.
Click to expand...
Click to collapse
well, kinda, in theory. i've never done one (well, once, two yrs ago) and ive never had any probs . Flashing a stock rom performs a task 28 anyway, which covers most of the areas a task 29 covers, , plus, there are increasing numbers of people reporting what appear to be bad blocks, especially now we are flashing nand android a lot, and to my mind a task 29 seems like unecessary extra wear and tear on the nand memory.
Im not saying task29 is useless, i'm sure it does help in certain circumstances, , but i'm also sure 99% of task29's that get performed every day are wasted.

[Q] Unable to run RUU

Hi I have an HTC HD2 and decided to try it with Windows 7. I followed instructions and installed a stock Windows ROM (from HTC) - all fine. When I went to install the new ROM, all was well until I got to running the RUU (for MAGLDR 1.13). The process hung on 0%. I tried again, same thing. I tried MAGLDR 1.11 - same thing. After several attempts I got a bit suspicious and decided to re-run the HTC ROM update - it hung on 0%!
It seems like I can't update anything! Has anyone seen this or have any ideas what I can try?

you either don't have hspl installed. look in bootloader, wazzit say?
or
dont try flashing from running windows mobile, , enter bootloader manually, connect USB and THEN run your flash.

Hi, thanks for answering, but I am afraid none of that helps. I have HSPL 2.08 installed and I get the same result whether I use WMDC or USB connection. Do you know how I can remove HSPL? Apart from the WM 6.5 ROM, that is the only other thing I have installed on the phone.

"I have hspl 2.08 installed".... does it say "2.08.0000" or "2.08.hspl"?
I'm double checking because half the people that declare they absolutely, totally and definitely have "hspl 2.08 installed" actually have 2.08.0000 which isn't hspl.

That's fine, yes it is 2.08.0000... I installed it specifically as part of setting up for Windows 7.5 But is says SPL-2.08.000000 !
OK NOW I definitely have it installed and I shall try again before confidently posting anything ;-)
And now of course it all works - thanks!

hehe, you wont be the last to make that mistake,, you probably wont be the last THIS WEEK.
!!Take note, flashing newbs reading this!! always always double check visually in bootloader what your hspl status is. Don't just assume its what you think it is, half the time it isn't. If you get suck at 0% its nearly always this problem.