yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] ilj:
*sigh* One more having problems here. I can't seem to install drivers for USB for Vista x64. I do the F8 thing, select the "disable digital driver signing", Windows boots up, everything goes as normal. But two problems occur:

1) I follow the instructions in the guide, but when I go to Activesync center and uncheck the "allow USB connection", Touch HD isn't in the list in Device manager anymore, so I can't select it and go to the "update driver" tab.

2) Even when I try and do this while HD is normaly connected, and go to the "update driver, have a disk, blablabla", and select the file in the "Vista x64 driver" from Zip Crackwhore posted, the Windows says that the selected file isn't supported for x64 system. Better yet, let me quote. "folder you selected doesn't contain a copatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."

In short... help :( How did other people with Vista x64 make these drivers work?
[Touch HD Windows Mobile ROM Development] tnyynt:
Stuck this thread!

At least till users learn how to do things...
[Touch HD Windows Mobile ROM Development] golgautier:
Hello guys,

I have a problem with 1.56 rom upgrade.

I had a cooked rom with HardSPL from Olinex. I have done each step of this tutorial, but after I go back to the 1.14.0000 SPL, my blackstone stay (hang ?) on a white page with "loading...".

Note : I can load 1.14 ROM and use my phone normally. But I can't access at upgrade page of SPL

I can't put the new official ROM on my Touch HD beacause of that :-(

If you have an idea... :confused:
[Touch HD Windows Mobile ROM Development] Yarie:
Morning Golgautier, did you followed exactly followed the steps to downgrade your spl, there are two files to use before you run hspl : you have to open first the hspl (a) but without clicking anything and unzip the "restore stock spl" file (b) in order to copy the RUU_signed.nbh from (b) to (a)

Only after that, you must launch the HSPL... have you done that?
[Touch HD Windows Mobile ROM Development] golgautier:
Hello Yarie,

Yes, I put the nbh file found ine the Restore_Stock_SPL_114_2.zip file. It replaces a same-named file in the directory and i follow the next steps of the GUI.

I was surprised because upgrade time was very short (5s max), but all progress bar was at 100%

I have en french phone, is the Restore_Stock_SPL_114_2.zip the good original SPL file ?
[Touch HD Windows Mobile ROM Development] luckyuser:
@cRaCKwHoRe

Fisrt I wonna thank for this great guide!

Appreciate commitment to the community!​

Here is my prob/question:

I would like to upgrade my Original shipped HTC ROM 1.14(see my signature) to Orginal shipped HTC ROM 1.56.

I would like to do it with SD-card flash!

procedure I read (WIKI): rename extracted file RUU_signed.nbh to BLACIMG.nbh, put it in the root of a FAT 32 formatted SD-Card, keep the Touch HD in boatloadermode and flash!

But:

Say if the shipped HTC ROM 1.56 isn't very satisfactorily at the end, can I flasback Original shipped HTC ROM 1.14 without intervention of installation of USPL/HSPL or some other stuff?

In other words can I flashback from (Original)ROM 1.56 to (Original)ROM 1.14 just the same easy way (SD-card flash) like I did before?

boatloadermode i get following info:

SPL-1.14.0000

MicroP-Blackstone

(LED) v6

I need an expert, reliable answer for it!;)

THX in advance!​
[Touch HD Windows Mobile ROM Development] Yarie:
Yes it is, i have used the same one , now you have to check if your spl version is installed : press vol down + power and see what is written

You can PM me if you want me to explain in french?
[Touch HD Windows Mobile ROM Development] golgautier:
My SPL was 1.14.0000

I have found the solution : I hada BLACIMG.nbh file on the root of my SD Card. I deleted it and upgrade procedure will pass the "loading..." phase...

Thanks for your help !
[Touch HD Windows Mobile ROM Development] abu.khalifa:
Hey,

ive followed ur instructions down to a T.

I've been able to get to this step:

(6) Run USPL. For instructions on how, read steps (5b) through (5e). If you are at this point and have already flashed the new HTC 1.56 rom your SPL version will show 1.54.0000 at step (5b). This is ok and is correct.

how ever when i try and flash any of the new roms 2.8 or 2.9 it basically stays on 0%

help?
[Touch HD Windows Mobile ROM Development] Yarie:
OK ! glad you found the solution :D good luck with the rest, you're half way there :o
[Touch HD Windows Mobile ROM Development] ClydeB1:
Did you flash straight to the Energy rom from spl 1.14? If so that is the start of the problems, but the more serious issue is that you say you can't get to bootloader.

Have you tried a hard reset, ie push and hold vol up and down together and then power on. If still nothing happens then I'd pull the battery out and leave it out for a few hours and then try again. The first thing you need to do is to try to get back to the bootloader screen. Once there we can try to get you sorted. If still nothing then you could have a hardware issue and would need to return to your provider.
[Touch HD Windows Mobile ROM Development] Beltic:
nope - 1.56ONelix first, then energy.

returning to provider = yuk. im in the states, bought it from some site in euroupe (forget which) (bought unlocked).

Ill post back shortly.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Hope you come right there.
[Touch HD Windows Mobile ROM Development] WaveyKat:
is there any other way to get into Bootloader mode without Pressing the Voldown Button?
[Touch HD Windows Mobile ROM Development] DaveShaw:
Run the CustomRUU, you'll see it extracts a load of files, one of those files is EnterBootloader.exe. Pop that on your phone and run it.

Dave
[Touch HD Windows Mobile ROM Development] WaveyKat:
thank YOu VERY much it worked! :-)
[Touch HD Windows Mobile ROM Development] myearwood173:
Hi can anyone help me please? I want to flash my rom what is the safest way? USPL or HSPL?

Thanks Matthew.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Both are safe providing you follow the steps. USPL is slightly safer if you are worried about possible warranty issues as it retains the original spl and is therefore easier to return to stock in the event you need to return your device. It is also possible with HSPL, but is a slightly more complicated procedure.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
As stated by ClydeB1, both routes are safe, though USPL route is better if phone needs to be returned under warranty warranty plus its slightly easier to setup first time.
[Touch HD Windows Mobile ROM Development] myearwood173:
Thanks a lot guys i will flash it via uspl. Also i want my phone to look like the new HTC HD 2 Leo what rom will be the best for me?

Thanks Matthew.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Most of the newer roms use Leo, so take your pick. Once you've started flashing it can become additive, but try a few to see which ones suit your personal preferences as when reading the forum you will see that some people are very loyal to a particular chef whereas others feel as strongly about theirs. That is probably due to the fact that certain aspects of one rom appeal to a particular group and other aspects to the next group. So making a suggestion based on what I like may not be the one you will like.
[Touch HD Windows Mobile ROM Development] ziyaadj:
Ok, i got a strange problem with certain ROMS:

When i try to flash EnergyROM leo 21864 manila 2.5 (28oct) i got stuck on smart mobility screen.

I hard and soft resetted multiple times after flashing, and I even flashed the radio to the newest one (1.17) , but still nothing. I also flashed via usb and via storage card. But that made no difference....

HOWEVER, when i try to flash other roms (e.g. Energyrom "photon" 21864 manila 2.1 or miri's latest rom) it works perfectly without problems :S?

How can this be? is there something wrong with the latest uploaded roms? If so, how come most people do not experience the same problem as me with that particular ROM? I am pretty sure the problem is to be found in my device...

I used 1.56 hspl btw.

Anyone who can help?
[Touch HD Windows Mobile ROM Development] ClydeB1:
Have you perhaps tried to download the file again? There may have been an error during the download process which corrupted a small part of the file. If this is still a problem, some people have had success after first flashing back to a stock rom and then flashing again.
[Touch HD Windows Mobile ROM Development] ziyaadj:
I downloaded the file twice from different servers (some ftp server and the hotfile link given by NRG himself), and i even downloaded an earlier version of the same ROM (27oct and 28oct release of Energy Rom "leo" 21864 manila 2.5), but still no succes. I flashed to stock rom and stock radio, but that also had no effect. However I did not flashed back to original SPL.

So what could it be?
[Touch HD Windows Mobile ROM Development] ClydeB1:
I don't know as you seem to be in the minority. Most others can flash without any issues. I would suggest trying to flash back to your original rom and then trying again.
[Touch HD Windows Mobile ROM Development] ziyaadj:
I allready tried flashing to stock rom...

Maybe i will just wait till the newer Energy series come out :)
[Touch HD Windows Mobile ROM Development] will-w:
Used this yesterday to flash Miri's new 1.56 rom to my ancient 1.19 Blackstone...

Was a little daunted at first, but it was a total breeze and written really well!

Cheers :)
[Touch HD Windows Mobile ROM Development] GTDave:
You guys are awesome!

I don't often post comments, but I make an exception here because flashing a ROM is a truly daunting experience bearing in mind all that can potentially go wrong.

I was getting fed up with my Touch HD's inability to see all the music files, and to freeze from time to time, so decided to take the leap in to the unknown and upgrade it.

I read the instructions and discovered that what I had was version 1.14 so I needed to follow the whole process as described. I found all the files I needed and now I'm running on Duttys latest ROM which also upgraded the phone to WM6.5 - a real bonus.

Now the graphics are greatly improved and it's like I've got a new phone.

So thanks to you all. you've proved that, clunky and old though WM is it can at least be developed and improved unlike the iPhone. I'm addicted now....can't wait until my next upgrade!
[Touch HD Windows Mobile ROM Development] j1978:
Hey

I usually flash using uspl and the sd card.

I now have hspl installed on the device since i unsimlocked it.

Can i still flash from the sd card?

if yes can anyone tell me the exact steps?

Thanks alot

Jay
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Yes, you can still flash from SD card. Just use same method as before by copying BLACIMG.nbh file to root folder of your SD card. Go to bootloader mode. Push and hold Vol Down + press Power button. The device will display a message and offer you to flash.

Just no need to re-use USPL before each flash now.
[Touch HD Windows Mobile ROM Development] j1978:
ok thats what i thought :D

Thanks.

Jay
[Touch HD Windows Mobile ROM Development] tommypdas:
Sspl dont find USB connection

Hi everyone!

I run sspl-manual.touchHD.exe and my phone reboot into its bootloader but, my Blackstone dont detect the usb connection :confused:

Any suggestions?

Tommy
[Touch HD Windows Mobile ROM Development] ClydeB1:
Remove the usb cable and wait about 20 - 30 seconds and then put it back. It should work then.
[Touch HD Windows Mobile ROM Development] will-w:
What OS are you using?

Windows 7 x64 appears to not work with this process :(
[Touch HD Windows Mobile ROM Development] tommypdas:
Dont works.... but finally, after a hard reset, it works!!:D

XP SP3

Thank´s for all friends!

Tommy
[Touch HD Windows Mobile ROM Development] morpheo1321:
hi guys.It's the first time i'm trying to flash my phone.does it have to be sim unlocked?

Otherwise it's a great tutorial.Thanx
[Touch HD Windows Mobile ROM Development] DaveShaw:
No it doesn't need to be SIM unlocked.

Dave
[Touch HD Windows Mobile ROM Development] morpheo1321:
i did it.It's great.it felt like i got myself a new phone. :)
[Touch HD Windows Mobile ROM Development] virtualx:
BLAC100 32M

SPL-1.14.0000

MicroP-BlackStone (LED) v6

inside my stone are :

1. branded rom orange 1.19.61.1 WWE (phone is not sim-locked , i am on cosmote - working)

2. radio version 1.09.25.14

i've read those posts , i've read all of it to say , i know how to , i dont know if matters the order like : first the spl , after that the rom , and last the radio , this i dont know for sure

my logical answer is

1st upgrade spl to 1.54+ (and then if i do that, my phone will run my branded rom also?? or do i have to go next on new cooked rom?)

2nd upgrade rom 6.5

3rd upgrade radio

can someone aprove or deny my order?

thank you for your feedback
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Answer to your queries

1. Correct SPL first to 1.54+

2. Then upgrade to rom 6.5

3. Then upgrade radio (some roms contain latest radio so check bottom on splash screen to check version of radio installed after flashing rom)
[Touch HD Windows Mobile ROM Development] Rochen1:
I cannot download SSPL-Manual-TouchHD

for flashing another ROM, because of my RTT LEET R5 is very buggy I need SSPL-Manual-TouchHD (since I read information for troubleshooting, when I have USB and activesync connection before Starting, but it stops after bootloader).

I tried to download several times but it doesnt work, i just get 120Bytes of the .zip.

all my other downloads an web-connections work.

can somebody send the file to

rochen1@gmail.com
[Touch HD Windows Mobile ROM Development] tori007:
error 262 tried every thing not working

it gets to the screen and say 10 min to but the bar does not move then it show the error code after 20 mins

helpppppppppp
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Just tried it again and download works fine. Try one I've attached
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
ERROR [262] : UPDATE ERROR

This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.

Hope this helps
[Touch HD Windows Mobile ROM Development] 5fiori:
ottima spiegazione complimenti

excellent manual , with the compliment
[Touch HD Windows Mobile ROM Development] Silvercoat:
USPL.exe Problems

USPL.exe doesn't run anymore on my Desktop! When I start USPL V2.5 and click on "Run USPL" Windows comes back telling me that USPL.exe has encountered a problem and needs to close. I used USPL before, last time when I installed Duttys 3.9, following your guide and had no problems. Any ideas what could cause the Windows message?
[Touch HD Windows Mobile ROM Development] ClydeB1:
If it still does not work after trying again as suggested by Fallen Spartan, you will need to use the manual sspl method.

Possibly try to redownload uspl, it may have gotten corrupted. Also try switching off your anti virus when running it.
[Touch HD Windows Mobile ROM Development] Silvercoat:
Ok, downloaded USPL V2.5 again but unfortunately no change. And I had the AntiVirus off when I tried running USPL. That didn't make any difference either. Running Win XP SP3 and .NET 3.5, all updates.
[Touch HD Windows Mobile ROM Development] DaveShaw:
Are you using an Administrator account?

Dave
[Touch HD Windows Mobile ROM Development] ClydeB1:
Did you get any virus warning when downloading the file? If so, try turning off av before you download it as perhaps av is corrupting the file on purpose so as to protect you from a potential virus. If all of that still doesn't work you will have to go the hspl route.
[Touch HD Windows Mobile ROM Development] Silvercoat:
I didn't get any Virus warning during down load at all and I have Administrative rights on my sign in. I used USPL V2.5 less that 2 weeks ago and it worked fine. That is why I'm now so surprised about getting the Windows Message. I just can't figure out whats wrong.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Have you perhaps changed pc operating systems in the interim? If you are using Vista, you may need to downgrade your usb drivers. You can also try to Run the program as Administrator (right click on exe and select from menu).

Otherwise as suggested earlier use hspl ;)
[Touch HD Windows Mobile ROM Development] ClydeB1:
You could also try using USPL GUI which could give a little more information regarding the error.
[Touch HD Windows Mobile ROM Development] Silvercoat:
No, I haven't changed the Operating system apart from Windows Updates, perhaps. And I have administrative rights on the PC.

I'm using USPL GUI v2.5! The application starts and opens its window. The moment I click on the "Run USPL" button the Windows Message "USPL GUI v 2.5 has encountered a problem and needs to close. We are sorry for the inconvenience." appears. Perhaps worth mentioning, I get this error message whether the phone is connected via the USP or not!

I tried to run USPL GUI v2.5 from my Laptop and got the same result! Now, I completely panicky! Need some HELP badly!
[Touch HD Windows Mobile ROM Development] ClydeB1:
Sorry, don't know what else to suggest except - Use HSPL ;)
[Touch HD Windows Mobile ROM Development] tori007:
thanks its working haaaaaaaaaaaaa
[Touch HD Windows Mobile ROM Development] ClydeB1:
Glad to hear that you managed to come right. Did you have to use the manual sspl?
[Touch HD Windows Mobile ROM Development] tori007:
yes i had to
[Touch HD Windows Mobile ROM Development] ALLDAT:
Help on laodind new rom

Help please, this is my first try at this and so far no luck, I went through the dummies guide for flashing

HSPL3 - Check SPL version

(HSPL3a) Place your phone into its bootloader.

(HSPL3b) When the bootloader appears it should show SPL v 1.56.OliNex. If it does go to step (HSPL4). If it does not something happened so repeat step (HSPL2). got this far it and the spl v 156.Olinex does display in bootlaoder

but when i go to try to load this rom "EnergyROM_23081_RHODIUM_25.Oct.2009_StandardM2.5"

HSPL4 - Flash new 1.56+ rom

I get error message: ERROR [244] : INVALID MODEL ID

not sure what to do now

Thanks for the help.
[Touch HD Windows Mobile ROM Development] ClydeB1:
What phone do you have? That is a rom for a Rhodium and this is a Blackstone forum. You can't flash a Rhodium rom to a Blackstone which is what the error code is saying.
[Touch HD Windows Mobile ROM Development] ALLDAT:
I have a blackstone...

Thanks
[Touch HD Windows Mobile ROM Development] ClydeB1:
Then you must use a rom for the Blackstone and not a Rhodium rom. You will find the link for the Blackstone equivalent of the rom you are looking for in my signature.
[Touch HD Windows Mobile ROM Development] T1CODE:
where to download the 1.59 rom so i can flash it to duttys holt grail ro?

psl give links

Thanks
[Touch HD Windows Mobile ROM Development] ClydeB1:
You'll find it

here

. You will need to register on the site first though.
[Touch HD Windows Mobile ROM Development] T1CODE:
i mean the base rom 1.59, where can i download it?

thanks
[Touch HD Windows Mobile ROM Development] ClydeB1:
You do not need one. If you have 1.56.Olinex you can flash directly to Dutty's rom. Dutty's rom is based on a 1.56+ base rom.
[Touch HD Windows Mobile ROM Development] cablesguy:
Windows 7

Not sure if this has been asked before, but would installing cooked ROMs be the same under Windows 7 as it is under Vista, and would the USB drivers need to be updated as well.

TIA
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Plenty of people have flashed using Windows 7 with no issues. You only need to upgrade your USB drivers if 'USB' is not displayed at the bottom of bootloader with phone is connected to pc.
[Touch HD Windows Mobile ROM Development] cablesguy:
Thank You Kind Sir!!
[Touch HD Windows Mobile ROM Development] damador:
got problem - my device gort "non responsive touchscreen" affair :)

had miri 29 and hspl 1.5x

first i made hard reset - but further writing point me to think that service is needed so i decided to back to stock

at first flashed 1.56.401 and old radio then made mistake and flashed stock 1.14 since then i have troubles with further reflash

device start to configure screen ( which i cant pass because of non working touch screen) - also have troubles with active sync - it dont want to connect or fast disconect after loading ...

cant reflash - only partyially working method is going to bootloader pluging USB cable and flash ... but problems also start here

no matter what i try it wont start ( stuck at 0 % ) or flash to 1 % and device restart - cant flash hspl or stock roms
[Touch HD Windows Mobile ROM Development] damador:
uh almost fixed it - USPL allowed me to flash stock roms - strange
[Touch HD Windows Mobile ROM Development] Rochen1:
I was successful with flashing ROMs three times, but now I have a Problem

ActiveSync Connection with Mobile Device Center works. When I start BlackStoneCustomRUU the Touch HD changes into Bootloader. I see loading for half a second. Then Connection disconect and I get message

Error 260: Connection

The update-utility cannot connect to your pda-phone

Bootloader shows:

Blac100 32M

SPL-1.56.OLiNex

MicroP-BlackStone (LED) v6

It doesnt show serial and it doesnt change to USB when conneted (as it did before)

Trouble-Shooting with SSPL-TouchHD.exe as recommended didnt work.
[Touch HD Windows Mobile ROM Development] tori007:
no signal from phone

after flashing rom

gone back to original stock orange rom still same issue

get the g for 3g but exclamation mark ! on signal strenght

need help pls cant use the phone
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Getting no signal is one of the signs ofn ot flashing using either USPL or HSPL or having incorrect version of HSPL. Read and follow this guide correctly and you should be fine. What was your SPL before flashing rom?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
ERROR [260] : CONNECTION

This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.

When you get this code and use SSPL, ensure you disconnect device from usb cable, soft reset and then reconnect usb cable again before attempting to flash rom
[Touch HD Windows Mobile ROM Development] LordDeath:
Hi,

are there any news about USPL with Win7 x64? I can't get it to work.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Have you tried downgrading your usb drivers? You can find the procedure here, it should be the same as for Vista.
[Touch HD Windows Mobile ROM Development] tori007:
was on duttys leo cant remember which one then once i changed to lost in asia rom then the signal problem started now am back to oranges official rom and radio downloaded from the orange website
[Touch HD Windows Mobile ROM Development] ClydeB1:
What version and build is the Orange rom? Look in Settings/About. You may also need to change your spl version to match the rom. Did you previously use hspl? What is your current spl if you go to bootloader?
[Touch HD Windows Mobile ROM Development] tori007:
spl 1.56oilnex

windows moblie 6.1

build 20769.1.4.5
[Touch HD Windows Mobile ROM Development] onesreality:
HEY! after i do HARD SPL why my screen become discolour! what happen! omg someone pls help me! i enter to bootloader, the colour is alright but when boot into the os, the colour discolour! pls help ! thanks!
[Touch HD Windows Mobile ROM Development] DaveShaw:
Your SPL ROM versions are mismatched, if you have Hard SPL 1.56 make sure you have a ROM based on 1.56 or greater.

If your Hard SPL is 1.14 make sure you have a ROM based on 1.56 or earlier.

Dave