yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] sliv:
i did the troubleshooing but it doesnt show usb when i connect.so i did a soft reset and started again.now the SSPL-Manual-TouchHD.exe wont run so did a hard reset n tried again- the same thing happens.doesnt show a usb conection.
[Touch HD Windows Mobile ROM Development] NightKing:
Update Rom

Afther some much troubles i have a Rom working on my phone, but it was by the GUI of Digital Outcast. The Driver on x64 is not working or me and now it i have fixed the first problem that i can use my phone. Now i have the fersion of panosha (2.24) on my phone but i will install the last version... but when i copy the file to my SD and in my bootloader is only to see the text loading . . . but he will not update the rom, what can be the problem. (okay i'm glad that i can use my phone again, but i look likes there are more problems)..

When i wille align my screen in panosha the screen is flashing bevore i see the align screen and i could not good align the screen, tapping on the cross will be not good react or i have to do many times over, can this be a software problem or a hardware problem?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Some newer roms don't have the align screen after flashing. But you can manually align screen by going to settings > system > align screen
[Touch HD Windows Mobile ROM Development] NightKing:
No this is by first used and it have a align screen, but it is does not worked good as earlier this year... When i use the align screen it will be very slow and most from the time i can start the align test over and over ... The panosha 2.4 is only a beta i see.... and i can not set the date op this day... when i do that then i see only the text that it is beta but update wil succes.

But i have now the date on somewhere 2008 now i can the Rom only i have some shortcut target error when i startup the phone ... The text in the error is: "Error opening the shortcut or location the target filename"

Afther trying to setup my contact persons from outlook the time will be reset to time from now... but i can nu understand when i wille in stall a new rom where i have the BLACIMG.nbh on my SD card no working. when i do my device on and hold in thedown volume button there will be a grey screen and the tex loading is standing, but i can not forward to a next step with installation

The only function what i van use is to restore the ROM what i have and that is panosha 2,4 only that is be a beta version ...

I try now with My Mobile, look of it then will be worked.. it look likes that the system will be freesed or some thing, when i will tap with my mouse in My mobile the system react not too :S
[Touch HD Windows Mobile ROM Development] rhyre:
have same issue sliv and1 can help us?
[Touch HD Windows Mobile ROM Development] KLPFL:
could anyon let me know why i can't update the rom...it's showing my HD connected to PC. I tried all the step. it gave me an error when i tried to run sspl-manual-touchd.exe on my HD. Please advise. Thanks.
[Touch HD Windows Mobile ROM Development] rhyre:
ok tip for u. go to other PC :) it helped for me.
[Touch HD Windows Mobile ROM Development] KLPFL:
I tried multiple PC, same issue. connected but it doesn't install.
[Touch HD Windows Mobile ROM Development] sliv:
i also tried with 2 pc's.its still not working. :( can anyone please help us with this?
[Touch HD Windows Mobile ROM Development] KLPFL:
plse ignore my previous posting. i got it to work.. thanks.
[Touch HD Windows Mobile ROM Development] sliv:
i guess its true that third time a charm. :D just flashed to dutty's 6.5 R6.thanks guys for all ur help
[Touch HD Windows Mobile ROM Development] Sonarok:
hi all,

short question:

i want to flash my german HD from (1.14.0000) to a custom one (L26 3.55) with USPL... could i also use the 1.56 german rom from HTC instat of the 1.54 SPL rom out of this guide or is the 1.54 needed for some special reasons?

because if i need to upgrade my spl anyway why not to the newest version...
[Touch HD Windows Mobile ROM Development] cvchetan:
u cannot use ur german rom on sp 1.54 because as u mentioned ur german rom is a 1.14 base.

1.54 spl is not backward compatible and ull have color and screen issues..

neways u can always downgrade ur spl...
[Touch HD Windows Mobile ROM Development] LITANG:
thanks！en！evry good！
[Touch HD Windows Mobile ROM Development] NightKing:
Okay I have finished the upgrade tot panosha 3,4 and that is a start... For the rest i see when i push my phone on the i first see a green text of smart bla bla of HTC (normaly it is white). I'm Running: SPL-1.14. OliNex

When the ROM is started i see first some text in the green colour (look like it is working on 8-bit or something...) and when i have press on the power button i see the normal colour. But i for the rest tapping on my screen for align screen will not good work, look like that the system is be frozen. When i unplug the USB cable and replug again i will see the align screen, but i can not normal tab on the cross... there is some times before i can press on the next cross some times i have to replug the USB cable before i can go to the next cros.

And it will not help to hold the tab on the cross or much time after the last tab..

But i'm the most worried about the green screen, self i think that it by some update or something ... Hope some one know this problem and have some solution for it...
[Touch HD Windows Mobile ROM Development] Sonarok:
hi cvchetan,

thx for your fast replay... but this guide discribe that i need to upgrade to 1.54 spl if i want to use a 1.56+ custom rom flashed over USPL... i want to flash L26 3.55 what is a 1.56+ rom so i need to upgrade the spl anyway... the question that i have now is if i could start with flashing the newest rom from HTC ( 1.56 ) and than use USPL to flash some custom rom such as L26 or if i need to follow this guide and patch 1.54 spl because its needed instat of a newer one such as the 1.56 from htc...

or did i mixed up something with bootloader, romversion and so on?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
To flash any cooked rom your will need USPL on device first.

You can use either HTC 1.54 or 1.56 rom
[Touch HD Windows Mobile ROM Development] Sonarok:
hi Fallen Spartan,

exactly what i need to know...

i would start to upgrade my spl to 1.56 and after this load USPL and than flash some custom rom like L26...

i was just confused a bit because this guide discribte that you need SPL 1.54 and there is a newer version than this.. so i thought maybe you need exactly this 1.54 version for some reason... but ok so you need a 1.54+ SPL and not exactly the 1.54 maybe the guide could get some small update for this step

thx!

EDIT:

hhmmm ok now i saw something about the SPL version in the USPL thread... the 1.56 version is missing under the "supported" versions.. so maybe thats the reason why this guide use the 1.54 spl version
[Touch HD Windows Mobile ROM Development] mariog:
Same SPL after loading ROM

Hi,

I have update my device from the branded ROM to WM6.5r8 by dutty

Before it was SPL 1.13... I have start USPL (spl 1.15) and i have loaded the rom with BlackStoneCustomRuu.exe because the other method didn't work.

Now (I already do two hard reset) I have poor color on startup and I can't enable phone.

Now the bootloader is still SPL 1.13

It's ok?
[Touch HD Windows Mobile ROM Development] andersh2:
Flashing gone wrong - please help

Hi all,

Please forgive a newbie for asking about this - I'm sure it's already explained somewhere in the forum - but here goes:

I recently installed the Olinex 1.56 hard SPL and flashed a custom ROM - no prob.

A few days ago my touch screen suddenly completely stopped responding, I have no idea why. I would like to send the phone back for service but of course I have to restore the default SPL and ROM before doing that.

I first reflashed the latest shipped ROM. That went alright.

I then tried to figure out how to restore the SPL using this page:

http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Flash3

I downloaded the Restore_Stock_SPL_114_2.zip and flashed the .nbh file using the Blackstone CustomRUU v 1.0.

When the flashing was completed I got the green screen problem and the phone could not connect to ActiveSync via USB :(

The 1.14 SPL has been succesfully installed according to the tri-color screen in bootloader mode.

What should I do to re-establish the activesync-connection and resolve the green screen?

I don't know if SPL 1.14 was the right choice of version...

Please help me out

- Anders
[Touch HD Windows Mobile ROM Development] Shoaibz:
Try to connect via boot loader mode. Switch off the BS then switch it on while holding down the volume down key it will bring you to the tri colored screen. Then connect it to your USB cable. Wait for a while eventually the serial will change to USB on the BS. After this you can reflash SPL/ROM. I hope this helps.

Do remember that with 1.14 SPL you should stick to stock ROMS ! So reflash original shipped ROM and it will correct your green screen and active sync problems both. !
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Your SPL is 1.13. You need to get to SPL 1.54 before flashing rom or you will get this green screen issue.

You will need to re-use USPL. After you have used USPL you SPL should change to SPL v 1.15.USPL. You will then need to follow (USPL3d), (USPL3e) and (USPL3f) from this guide and get SPL 1.54.0000. Once you have this you will need to re-run USPL and get SPL v 1.15.USPL. Once you have this you are then able to run your cooked rom (Throys R8)
[Touch HD Windows Mobile ROM Development] Digital Outcast:
What was the latest shipped ROM you flashed? By that, I mean what version? Is it v 1.56 or higher? If so, then you have to have SPL 1.54.0000 on your device to address the screen corruption issue.

Also, I merged this thread with the ROM flashing tutorial thread.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
You flashed the wrong HSPL for the ROM you are using. Please read the guide in my signature.

Also, I merged this thread into the ROM flashing/guide thread.
[Touch HD Windows Mobile ROM Development] fowler002:
after 6-7months yesterday I finally bit the built and upgraded my stock orange rom to dutty's 6.5 r8.

I first tried the hspl method to upgrade the stock spl(1.14) to 1.56olinex but kept getting the 262 error, I didn't go the manual sspl then hspl route as I didn't want to risk it not upgradging to 1.56olinex and being stuck on 1.07olinex so tried the uspl.

had issues updating the usbdriver on my vistax64 pc, first I kept getting the code10 error(can not start drivers or something along that line, according to the updating driver guide this is fine for xp but for vista it says should get driver updated message) then after a number of tries I thought to hell with it I'll update the drivers(as I'd restored the original drivers) and do what it says for xp and unplug then replug the usb cable and hope it works but it gave the code 39 error(corrupted or missing) and regardless of restarting the pc/deleting extracted drivers and extracting the zip file again I keep getting the code 39 error.

so after a couple/few hours of bashing my head against the wall with my pc I went downstairs and tried the pc down there(win7 32bit rc), I first tried the hspl route but got the 292 error again so did the uspl route and it worked fine.
[Touch HD Windows Mobile ROM Development] c0r130n3:
Thank you thousand times...
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
So your up and running then, yes?
[Touch HD Windows Mobile ROM Development] fowler002:
yep got the spl 1.54 and duttys 6.5 r8 rom flashed and running.

just need to figure out why its giving the corrupt/missing error(code39) on my main pc, so inthe future I can use the main pc to flash and don't have to go downstair.
[Touch HD Windows Mobile ROM Development] mv20:
I did everything ok, Im on SPL 1.56 but when i launch the USPL GUI V 2.5. it says that i need to upgrade my driver, i had already done that once. when i go to try to do it again, it says that it found the new driver but it wasnt able to install because the device wouldnt start. Any help i would appreciate
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Have you tried update usb drivers etc on main pc. See first post in this thread for guidance
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Have you tried running USPL itself or HSPL?

Make sure you put your phone into bootloader beforehand and also that bottom of bootloader screen changes from 'serial' to 'usb'. Also after you updated usb drivers, did you restart pc?
[Touch HD Windows Mobile ROM Development] mv20:
USPL, i did have it on boatloader beforehand and it did change from serial to usb. After i upgraded the drivers i did not restart my PC
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Is this working now then?
[Touch HD Windows Mobile ROM Development] mv20:
it still is not working
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
what happens when you put phone into bootloader. Does it change from 'Serial' to 'usb'? No

What error do you get when running USPL or HSPL?
[Touch HD Windows Mobile ROM Development] mv20:
It does change from serial to USB.

I have sucessfully upgraded to 1.56 oliNex, when i try to run these steps and Run USPL.exe, it will say that i need to upgrade my drivers. I try to upgrade it again, it gives me an error "code 10" it says my device was unable to start.

(USPL5b) Run USPL.exe from the download in step (USPL1c). Remember to disable your antivirus for this. Some provide a false positive that it is a virus/trojan. When the application appears click on Run USPL.

(USPL5c) Your phone should reboot and return to its bootloader but saying SPL v 1.15.USPL and USB at the bottom. If it does not show USB after some time, disconnect and reconnect the USB cable from your phone.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
If you have HSPL on device i.e. SPL 1.56 oliNex you do not need USPL. You can flash rom straight away.

Quote from first post
[Touch HD Windows Mobile ROM Development] mv20:
(USPL5d) If the rom you downloaded from step (USPL1d) does not include BlackstoneRUUWrapper.exe then use the download from step (USPL1e). Make sure the .nbh file from step (USPL1d) and BlackstoneRUUWrapper.exe are in the same folder.

I messed up when i needed to put .nbh file from step (USPL1d) and BlackstoneRUUWrapper.exe in the same folder. The ROM that i downloaded did not have any files in it after i extracted. so i thought i needed to put the BlackstoneRUUWrapper.exe in the same folder. I did and Ran the BlackstoneRUUWrapper.exe followed everything, i did two hard resets. then i turn off the device, Held the volume down button and volume up button while you press the power on button. You should see a message saying "This operation will delete all your personal data, and reset all settings to the manufacturer default settings. Press VolUp to restore manufacturer defaults, or press other keys to cancel." Do exactly what it says...

it didnt show its regular colors and it didnt do anykind of upgrade. I downloaded the standard version ROM without MSVC CVSD ( i dont know what those mean either)

Sorry if i am being complicated I am new at this, thx
[Touch HD Windows Mobile ROM Development] mv20:
Thx, i will do that
[Touch HD Windows Mobile ROM Development] mv20:
HSPL4 - Flash new 1.56+ rom

(HSPL4a) Place your phone into its bootloader.

(HSPL4b) If the rom you downloaded from step (HSPL1b) does not include BlackstoneRUUWrapper.exe then use the download from step (HSPL1c). Make sure the .nbh file from step (HSPL1b) and BlackstoneRUUWrapper.exe are in the same folder.

I do not have a .nbh file from step (HSPL1b)

Which ROM do you suggest i download?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
I'm not going to suggest a rom as there is so many out there and my tastes and yours may vary. Decide on whether or not you want wm6.1 or wm6.5 and then choose a rom to try. I am biased towards Throy as I've used his a lot and beta test for him, but most used roms are generally Duttythroys, Miri's, NRGZ28's & Laurentius26
[Touch HD Windows Mobile ROM Development] mv20:
I get error 240 : file open

The update utility cannot open the requested file, im using HSPL
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
ERROR [240] : FILE OPEN

When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. Check that the contents of the folder is a CustomRUU.exe file and an .nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up.

Basically if you have HSPL installed which you seem to have as SPL is correct. Download rom you want and place .nbh & ruu file into same directory. Put phone into bootloader and then connect to pc using usb cable. Bottom of bootloader changes to usb. Then click on ruu.exe file and follow on screen instruction which follow
[Touch HD Windows Mobile ROM Development] mv20:
(USPL5a) Place your phone into its bootloader.

(USPL5b) Run USPL.exe from the download in step (USPL1c). Remember to disable your antivirus for this. Some provide a false positive that it is a virus/trojan. When the application appears click on Run USPL.

(USPL5c) Your phone should reboot and return to its bootloader but saying SPL v 1.15.USPL and USB at the bottom. If it does not show USB after some time, disconnect and reconnect the USB cable from your phone.

(USPL5d) If the rom you downloaded from step (USPL1d) does not include BlackstoneRUUWrapper.exe then use the download from step (USPL1e). Make sure the .nbh file from step (USPL1d) and BlackstoneRUUWrapper.exe are in the same folder.

(USPL5e) Run BlackstoneRUUWrapper.exe and follow it as normal.

(USPL5f) Hard reset afterwards. Once or twice- up to you. Twice has been recommended. Turn off your phone. I personally do it right after flashing completes and I see the "Smart Mobility" screen. I just yank the battery out instead of waiting for it to boot up all the way and go through customization process just to hard reset Hold the volume down button and volume up button while you press the power on button. You should see a message saying "This operation will delete all your personal data, and reset all settings to the manufacturer default settings. Press VolUp to restore manufacturer defaults, or press other keys to cancel." Do exactly what it says...

You are done!

i followed the process and it worked but when i load the phone i dont see anything different. i downloaded Dutty's Wm 6.5 r8. is there something im missing?
[Touch HD Windows Mobile ROM Development] fowler002:
thats just the thing(read my original post), after several times giving the code 10 error when I tried updating the drivers its now giving the code 39 error.

after the code 10 error I did not try running the uspl as in the updating drivers intructions for vista and win 7(have vista 64bit on main pc) it says you should get the drivers updated, restart pc etc message, I rolled back the drivers and tried again then again.

after a few times(not sure how many it was) I decided I'll update the drivers and just try running uspl to see if it works even if it gives the code 10 error(as by the time I thought of that I'd already rolled back the drivers), at that attempt it gave the code 39 error and has been giving that since.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Restart phone, it should say 1.59 Duttys at bottom of splash screen. Also, go to Start > Settings > System > Device Information and it should also state which rom your using
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
What rom do you have at present on device? What is your current SPL?
[Touch HD Windows Mobile ROM Development] mv20:
Up and running Dutty WM6.5 R8, thx for your help
[Touch HD Windows Mobile ROM Development] sphinxrider:
HTC Touch HD

Dear Moderator,

Last year I purchased this kind of mobile phone and device info was;

ROM version: 1.14.488.3 (22273) WWE

ROM Date: 25 October 2008

Radio Version: 1.09.25.14

Protocol Version: 52.49a.25.26U

WM 6.1 Professional CE OS 5.2.20757,

I found it very powerful this device. Now that WM 6.5 version is available, my query was, can I update my ROM to latest version and WM to 6.5? can you please provide step by step to perform it?

Thank you and best regards,

anthony
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Yes mate, of course you can. If you follow this guide you can flash to any cooked wm6.5 rom and should have no problems. This guide is as basic as it gets when it comes to step-by-step procedure.

As it states you need to check your SPL, then decide on whether or not you want USPL or HSPL then follow procedure for whichever you chose
[Touch HD Windows Mobile ROM Development] gururaj9:
Complete noob need help in updating to windows 6.5

Okk i hav just got my htc touch hd and want to update it to windows 6.5 all the stuff here is damn confusing like in a nutshell

BLAC100 32M

SPL-1.14.0000

MicroP-BlackStone (LED) v6

this is wat i get wen i switch on the mobile by pressing the volume button.

I hav gone through the "[TUT] Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL]"

for starters which method is better for me HSPL or USPL also to wat i cud understand HSPL seems better but i dont get wat this means in the procedure "A 1.56+ based rom- Dutty's latest rom" 2nd step in the guide why is this done i wanna update to 6.5 so which file shud i select frm tht post there r so many.

Am so condused this is nothing lik hacking and modifying psp i dont wanna brick ma htc touch hd so not takin any rash deicisions and goin wid the update

Plzzz tell me how shud i go about this.
[Touch HD Windows Mobile ROM Development] lunakirb:
you will learn more of you phone by going to the blackstone wiki here

before u can flash/update your phone to any kind of Cooked Rom u have to Read THIS

just follow the instruction posted on the tread

1. HSPLWrapper_Blackstone_156OliNex.zip - is good for rom based 1.56+

2. Unsigned_HardSPL_for_Blackstone_OliNex.zip - use this is u want the older version of ROM

after the HSPL and verified that you have the right SPL ver. comes the flashing/updating part of your OS which you said you want to update to 6.5

most of the roms now are based on 1.56 higher so i personally choose the first one.:)
[Touch HD Windows Mobile ROM Development] jagdipa:
Microsoft My Phone not working

I decided to try out 6.5, but I didnt want to lose my sms and contacts. So I used the microsoft my phone service to get a backup.

So I used USPL to get 6.5 on my phone. The OS works great. But when I try to get my contacts back using My Phone, it fails saying "Unable to connect to My Phone service".

I was wondering whether this was a known issue.
[Touch HD Windows Mobile ROM Development] gururaj9:
Yo thanks guys installed 1.56 olinex and got the windows 6.5

weird thing is after i did tht 1.56 update the screen kinda got funky if i switched of the screen and turned it back on it seemed to be fixed but everytime i restart the phone this problem persisted.

Now tht i am on 1.56 olinex can i try any rom etc new ones tht is i got it is not backward compatible old roms might not work but new one any and every one will work right.

Any chance of bricking the phone.

Tell me about this radios wat are they and wat do they do lol i am a noob if i update to windows 6.5 wont the radios be updated still.
[Touch HD Windows Mobile ROM Development] ClydeB1:
You have to make sure that the time and date are correct on the phone first before accessing Microsoft MyPhone. If this still fails, you can delete the linked phone on the MyPhone site from your pc.
[Touch HD Windows Mobile ROM Development] jagdipa:
Brilliant, thank you.

On another note, I started restarting my phone to see if I get my 6.1 version back. It seems that I must have HSPLed it instead of USPLed it. I have no idea where I went wrong, but I dont really mind. As long as I have a phone that works.