yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] stepw:
I was able to make it work on 2 Vista32 PCs after installing older drivers.

Can you make sure different drivers are indeed installed and loaded?

Thanks!
[Touch HD Windows Mobile ROM Development] stepw:
No, you can flash original SPL regardless of what ROM you are running if you have HSPL. You can install original ROM before or after restoring original SPL, doesn't matter. If you already have HSPL, you don't really need USPL.
[Touch HD Windows Mobile ROM Development] DaveShaw:
I merged this with the Correct thread. Please don't create new thread when there is already a discussion.

Thanks

Dave
[Touch HD Windows Mobile ROM Development] Nikos2k:
Stepw thank you for your reply

Could you please let me know of the version of these older drivers ?

I checked the drivers' version both on Windows Mobile Device Center>Help icon>About and in Device Manager>Mobile Devices>Driver Version

I tried first with the 6.0.6783 I had installed, and then installed the latest (6.1.6965) which uninstalled the previous ones
[Touch HD Windows Mobile ROM Development] cmonex:
yes when relocating SSPL I do pay attention not to reloc MMU table.

splxploit - I think it was originally your work :) , but I see what you mean
[Touch HD Windows Mobile ROM Development] cmonex:
yes the original spl is posted here on the forum, do not worry about that (for example i posted it in hardspl thread but if you use USPL you can build your own spl nbh for USPL. of course the original spl nbh's i posted will also work with USPL).
[Touch HD Windows Mobile ROM Development] Black Antitoon:
Hi, I have 2 questions:

When will the USPL exactly be removed? When turn the phone off? When I remove the battery? When I do a hard reset?

Ok, I have flashed a cooked ROM with the USPL. What happens if one day I press the power button and the phone does not wake up? I will have to send it to warranty service without being able to reflash it. Will they really notice that the ROM is not the original stock one?

Thanks. :)
[Touch HD Windows Mobile ROM Development] Eraser85:
nice questions black antitoon.. waiting with you the answers..

I suppose, however:

1. When you reboot your phone after flashing the .nbh..

2. If you have an unbootable device, which you have bought from TIM (so it' supposed to be italian) and is actually an English WWE version, the warranty serivice should complain about it.. HSPL just tell them you have modified your device, but if an ITALIAN device has an ENGLISH OS, well.. they don't need to check for HSPL in order to say that you have modified it ;)
[Touch HD Windows Mobile ROM Development] Black Antitoon:
This is only true if they boot the device, but if they don't because it won't boot what happens then?

By the way, I have read the warranty booklet which also lists the situation when the warranty is not valid, and altering the pre-installed software is not among them. Who says that the warranty is void?
[Touch HD Windows Mobile ROM Development] Eraser85:
microsoft, it's in the os' eula
[Touch HD Windows Mobile ROM Development] Black Antitoon:
So actually the real problem is not a broken warranty, but a broken EULA, which is not exactly what you want HTC to find out, right?
[Touch HD Windows Mobile ROM Development] stepw:
These are all WMDC drivers, unfortunately you have to use Activesync drivers available in this thread:

http://xdaforums.com/showthread.php?t=291723

Driver version will be:

DriverVer=10/06/2004, 4.0.4232.0
[Touch HD Windows Mobile ROM Development] stepw:
Thank you for the questions...

1. USPL resides in RAM, when you reset/reboot your device, it's gone. After a ROM is installed, RUU resets it automatically. You can remove the battery and unplug USB for a minute or two to make sure there are no traces remain in RAM.

2. I don't know what exact procedures they have in place to determine if warranty is void. As far as I can tell based on the service manual and this forum postings, they would follow these steps to determine if software was altered:

1. Boot OS, check version/language

2. If OS doesn't load, hard reset and try again

3. If OS still doesn't load, boot SPL, check SPL version

4. If SPL doesn't load (this is the case you are asking about), they don't have any reasons to turn it back

In some cases it's possible to locate the traces of cooked ROM in flash, even if you flashed the original ROM over. This requires forensic investigation though, which may as well cost more than 2 new units, so it's easier to replace it than to turn it back.
[Touch HD Windows Mobile ROM Development] DaveShaw:
Patching things such as the SPL can break hardware components, such as the USB port; although this is more common in development of the SPL's rather than in using the finished HardSPL / USPL. Although 99.9% of the time the problem will be caused by faulty HW, that 0.1% chance is why some companies reject the device (that's if the tech guys even know how to check :)).

Ta

Dave
[Touch HD Windows Mobile ROM Development] Nikos2k:
Thank you Stepw, it worked w/ that version
[Touch HD Windows Mobile ROM Development] Black Antitoon:
Thanks for your answers. :)

Now I'm going to read the full WM EULA, by the way, and tell you what I find out. ;)
[Touch HD Windows Mobile ROM Development] DaveShaw:
Enjoy :D

And don't make nukes using your phone :) (It's in apples EULA somewhere, I know that much)

Dave
[Touch HD Windows Mobile ROM Development] edge540T:
Hi, looks great this thread.

Some questions..

Can work, or someone have tested the xp version runing in virtual machine with xp over vista32?

And can be possible to load uspl with a inbuild method, like blacimg.nbh flash, would be the finish for the vista problem.

Someone have tested last dutty's rom 1.2 with uspl?

Nice work stepw, many thanks

Edit: uspl works fine changing vista driver for me.

One more question, will work an unsigned rom with BLACIMG.nbh? i am having problems to bootloader find the img file after boot with 1.14.uspl (dutty's 1.2)
[Touch HD Windows Mobile ROM Development] nanoo-eg:
Happy new year

I am try to download the USPL file but my antivirus found this: "Win32:Trojan-gen {Other}"

Its something serius?

Can you tell me if it secure to continue?
[Touch HD Windows Mobile ROM Development] HDuser:
If you got it from here

http://xdaforums.com/showpost.php?p=3070260&postcount=2

Its clean and your ANTIVIRUS is giving you a hard time.
[Touch HD Windows Mobile ROM Development] DaveShaw:
Question and Answer :)

Dave
[Touch HD Windows Mobile ROM Development] HDuser:
Added above to Wiki under point 12
[Touch HD Windows Mobile ROM Development] UserN1:
Thanks for Vista support ;)
[Touch HD Windows Mobile ROM Development] nanoo-eg:
@HDuser Thanks for your reply. I was sure that it is something like this but it better some times to ask.

@Daveshaw this is the subject? use or not use?
[Touch HD Windows Mobile ROM Development] DaveShaw:
Use. stepw has been around a long time and I trust him.

The program exploits a bug in the SPL to cause a stack overflow on your phone. Stack overflow bugs are not something some AV products aprove of, that's why you get the messages.

Ta

Dave
[Touch HD Windows Mobile ROM Development] stepw:
USPL is safe for your PC. Lately many AVs consider any packed exe's a threat in accordance with the "better safe than sorry" paradigm.
[Touch HD Windows Mobile ROM Development] Matterhorn:
stepw,

Many thanks for your work. I've been trying lots of different ROMs and I still have the stock spl thanks to your utility USPL. It works like a charm. :)
[Touch HD Windows Mobile ROM Development] alexwai:
where is the version that can support SPL 1.18 will be released? i am looking forward for it now. :) because seems like my official ROM got some problem on the touchFLO 3D. :(
[Touch HD Windows Mobile ROM Development] stepw:
Do you have a device with SPL 1.18?
[Touch HD Windows Mobile ROM Development] Matterhorn:
I have have been using USPL to load roms, I loaded the new 1.10 radio rom and everything was ok. Now I've tried to use USPL to change roms and it won't run anymore...could radio rom 1.10 be a problem for USPL? I guess maybe I'll have to use HSPL now?

Edit: It's working now it was a conflict on my PC ... Whew!
[Touch HD Windows Mobile ROM Development] edge540T:
I think is other problem, i flash first the new radio over stock rom like you, and after i have flashed two roms right.

May be other problem...with rom :confused:
[Touch HD Windows Mobile ROM Development] matzoe:
Am i correct that if you want to flash a new rom you have to use USPL again before flashing?
[Touch HD Windows Mobile ROM Development] DaveShaw:
Yep, if you don't want to use USPL everytime, use the "Hard" SPL.

Ta

Dave
[Touch HD Windows Mobile ROM Development] stepw:
Yes, if it's a cooked ROM. You can flash official ROMs with regular SPL.
[Touch HD Windows Mobile ROM Development] matzoe:
edit: mistake, have to read better. Thnx for the answer!
[Touch HD Windows Mobile ROM Development] simon1219:
Can I use USPL to flash the htc shipped 1.19 WWE rom to overcome the Vendor ID restriction i.e. I will unzip the original exe file to obtain the rbh file and then use USPL to flash the rbh file?

That is can USPL overcome the Vendor ID restriction of the original shipped rom?
[Touch HD Windows Mobile ROM Development] stepw:
That's what it for. It simulates supercid, so that you can flash ROMs prepared for any CIDs, even if they don't match the CID of your device.
[Touch HD Windows Mobile ROM Development] pap3rone:
i tried to donwload uspl 2.2 but it appears to be a corrupted zip files....anyone can help me please?
[Touch HD Windows Mobile ROM Development] DaveShaw:
Just downloaded fine for, no problems. Try again.

If you are getting virus warning you need to disable you virus scanner, this has been discussed in the thread before.

Ta

Dave
[Touch HD Windows Mobile ROM Development] monzablue16v:
Dude you rock :) was a scary ten minutes but I'm away now, works a treat :)
[Touch HD Windows Mobile ROM Development] Chris Cross:
EDIT: Sorry, I thought it would be better to post my question as a separate thread since it is more of a general newbie question and only in part related to USPL.

For those who want to answer, the new thread is here.

Thanks.
[Touch HD Windows Mobile ROM Development] condorelli:
Thanks for your work.

can you tell me what's happen if i "hard reset" or if i "soft reset" after i use USPL and flashed a rom? it comes back to original rom? I'm newbie and i'm thinking about flashing a TIM branded italian rom.

sorry for my english
[Touch HD Windows Mobile ROM Development] DaveShaw:
I'll break the answer down then :)

At the moment you have the Stock ROM, you use USPL to Flash a Custom ROM, if you then Hard Reset you go back to the Custom ROM. A Hard Reset goes back to the last ROM you flashed.

Ta

Dave
[Touch HD Windows Mobile ROM Development] condorelli:
thanks a lot :)
[Touch HD Windows Mobile ROM Development] simon1219:
Invalid Vendor ID Using USPL

I have extracted the OS.nb for the 1.19 HKCSL_WWE shipped rom. Create the rbh file and try to flash using USPL.

Using the procedure describe for USPL, I am able to flash other chefs' cooked rom. But when I flashed the above shipped rbh rom, after about 1% in the flashing, it failed with the invalid Vendor ID error.

What steps have I missed that I can't use USPL to flash shipped rom?
[Touch HD Windows Mobile ROM Development] stepw:
You should be able to flash any .nbh with USPL. If there's a problem, then your .nbh is probaby invalid.
[Touch HD Windows Mobile ROM Development] simon1219:
I have tested the nbh using the kitchen to ensure that I am able to re-extract the OS from the nbh. It was comfirmed OK before I flashed the nbh, only to encounter the invalid Vendor ID.

I noticed that file size of the kitchen generated nbh file is smaller than the original nbh file that I created from the shipped nbh using the NBHTool. The difference is about 8MB. Anybody can explain why the different in size?

The reason I want to flash original shipped rom is to ensure my warranty.

Anyway I gave up trying to flash the shipped rom and instead flash one of the Chef's cooked rom.
[Touch HD Windows Mobile ROM Development] stepw:
It's not a shipped ROM you are trying to flash, but a repackaged ROM. If you need a hand with properly repackaging it, open a separate thread, this problem is irrelevant to this one.
[Touch HD Windows Mobile ROM Development] Mark1832:
Hi Stepw,

this is driving me crazy.... i have winxp sp2 and activesync 4.5.... when i boot my touch hd normally the HD sync with PC.

downloaded 2.1 spl

then i follow the steps up to having a usb in the white and spl-1.14.uspl in the red... then i run blackstone customrru.exe and i cannot sync the phone even if i plug and unplug again the cable.

Please help
[Touch HD Windows Mobile ROM Development] edge540T:
You must dissable usb connections on active sync, maybe you have done this..

Why not try rename the rom.nbh to BLACIMG.nbh and place it on microsd root?

It must be uninserted on the first pc connection on bootloader mode, and before run blac_upsl.exe it have to insert the microsd. by this way you do not need use customRUU to flash and it's more secure than usb flash.

Note:Transcend 8gb class4 not works with BLACIMG.nbh, for me works a sandisk
[Touch HD Windows Mobile ROM Development] Mark1832:
Thanks for your prompt reply edge540t....... mate i tried both method and cannot make it work

before doing anything i disable usb on active sync and i have a connection disabled on active sync icon bottom right screen

then i enter SPL bootloader mode connect usb lead and i have usb in the white. ... then i run 2.1 blac_uspl.exe and after few seconds it restart and in the red i have now 1.14.USPL insted of .0000... then i run BlackStoneCustomRUU.exe and on the second screen clear staed that there must be a connection with the HD via activesync.... i open it tick allow usb connection and wont connect.... DAMN! i tried the procedure with the sd card but does not work either!

What i am doing wrong ?

I noticed that my 8gb sd card is not seen by windows so i renamed the file and stored on another small 256m microsd card that is seen immediately by window..

ok so i enter SPL bootloader mode connect usb lead and i have usb in the white... i insert the 256m sd card in the phone run blac_uspl.exe and after few seconds it restart and in the red i have now 1.14.USPL .... while rebboting is sayng loading.... no images files... damn again...

I am going to use my daughter pc now maybe it is my pc.... but if i can sync when the hd start normally then look like it is not!
[Touch HD Windows Mobile ROM Development] stepw:
ActiveSync doesn't work when you are booting into SPL. Just click next in RUU and it will proceed with the update.
[Touch HD Windows Mobile ROM Development] Mark1832:
Many many thanks mate!

It worked! now i need to setup alot of stuff many many thanks again!
[Touch HD Windows Mobile ROM Development] marco899:
Thanks for this software. I have read it several times and now i changed my rom. Thanks.
[Touch HD Windows Mobile ROM Development] pap3rone:
hi all, i use uspl to nove from original rom to dutty 1.5...but if i hard reset my device i still see, entering in bootloader mode, 1.14 spl instead of original 1.13 and i have no original rom ( tim ita) but still dutty....can anyone help me to restore my device to factory?
[Touch HD Windows Mobile ROM Development] DaveShaw:
I'm not sure why it's changed from 1.13 to 1.14, USPL shouldn't change the SPL. So long as it doesn't say "hard", or something like that it should be OK.

But you should be OK to use USPL to Flash your stock ROM.

Ta

Dave
[Touch HD Windows Mobile ROM Development] pap3rone:
i can use uspl to flas my device to rom tim ita but i continue to see spl 1.14 instead of 1.13 so i guess if i'll have problems with my warranty....
[Touch HD Windows Mobile ROM Development] DaveShaw:
I doubt it will cause a problem with a Warranty, but just in case, have a look at the guide in the post by OliNex about Hard SPL. There's some steps on how to revert to the stock SPL.

Dave
[Touch HD Windows Mobile ROM Development] pap3rone:
using hspl instead of uspl right?
[Touch HD Windows Mobile ROM Development] DaveShaw:
No, it's the SSPL you need to use to flash the 1.13 Stock SPL. It might be able to downgrade on it's own if you find a ROM that has the 1.13 Stock SPL. But the SSPL should definatly do it.

Dave
[Touch HD Windows Mobile ROM Development] MJRL:
They are both original spl, don't see your problem.

Are you sure that your phone came with 1.13?

I don't know how flashing a rom would change your spl...
[Touch HD Windows Mobile ROM Development] DaveShaw:
When you flash a NBH Image file it can have a SPL included in it (All carrier ROM's do), if you don't have Hard SPL then the SPL is upgraded along with the OS, Radio and Splash.

Dave
[Touch HD Windows Mobile ROM Development] sandresimon:
Hi Guys,

I've been through all the thread, and I couldn't find a solution to my problem: when I run blac_uspl.exe I have the following message:

C:\Documents and Settings\Sandre\Bureau\Telephone\Flash Utils>blac_uspl.exe
HTC Blackstone USPL version 2.2, Dec 26 2008

Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&219d0984&0&2# 25dbce51-6c8f-4a72-8a 6d-b54c2b4fc835}...
Authorizing...
ERROR: Password command timeout

HTCSBye!>.L.HTCE

I've got the following displayed in the bootloader:

BLAC100 32M

SPL-1.14.0000

MicroP-Blackstone (LED) v6

I disabled USB in activesync, and "USB" appears in the bootloader

I'm running winXP pro.

Any ideas ?
[Touch HD Windows Mobile ROM Development] pap3rone:
problem solved....just flash shipped ita tim rom to restore spl to 1.13....anyway you're right...both spl are original so no problem for warranty....thanks all...:)
[Touch HD Windows Mobile ROM Development] stepw:
USPL updated to support SPL 1.19 (found on DOPOD Blackstone model BLAC11000 with CID DOPOD701).

Download USPL ver.2.3 if you have a device with SPL 1.19.
[Touch HD Windows Mobile ROM Development] citrix80:
error

i tried in install USPL version 2.3.

i downloaded and extracted the file. I am using vista x64. when i launch the application, it flash for half a second and gone. i launch the application is command line. i get this error:

HTC Blackstone USPL version 2.3, Jan 18 2009

Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&2e542025&0&2#{25dbce51-6c8f-4a72-8a

6d-b54c2b4fc835}...

ERROR: USB port could not be opened!

Verify that device is connected and SPL boot mode is active,

disallow USB connections in ActiveSync settings and try again.

HTCSBye!>.L.HTCE

i have already disabled USB in activesync and set device to bootloader mode, on bottom of screen, it display USB.

how can get through this?
[Touch HD Windows Mobile ROM Development] stepw:
Read the first post or the wiki, install ActiveSync drivers on your Vista x64
[Touch HD Windows Mobile ROM Development] citrix80:
I already have latest ActiveSync drivers on your Vista x64 installed.

I just tried it in win XP, when i launch the program, it flash one second and gone.
[Touch HD Windows Mobile ROM Development] stepw:
And that confirms you didn't read the instructions carefully.

You need older drivers, not the latest drivers to be able to use USPL on Vista.
[Touch HD Windows Mobile ROM Development] mezolezo:
WOOOOOW

GOOOOOOOOOOOOOOOOOOD JOB Mannnnnnnnn I really appreciate you job you did for me a very big favor

Thank you
[Touch HD Windows Mobile ROM Development] AvocadoBaby:
I'm confused :confused::confused:

I'm trying to figure out how this uspl thing works. I thought i'd figured it out but this post confuses me.

Should it read:

1. u have stock rom

2. use USPL to flash custom rom

3. soft reset = goes back to custom rom

4. hard reset = goes back to stock rom??
[Touch HD Windows Mobile ROM Development] desztan:
I downloaded uspl 2.3, followed the instruction:

Download the latest USPL attached to the second post of this thread and extract anywhere on your computer.

Go to ActiveSync properties and disable "Allow USB Connections" option. Turn off your device (long press "Power" key or remove/replace battery), then enter SPL bootloader mode (tri-color) by pressing and holding "Power" and "VolDown" keys simultaneously.

Connect USB cable and make sure "USB" label appeared in the white portion of the screen on your device.

Execute blac_uspl.exe; current status and any error messages USPL encounters will be displayed in the console window.

My screen still show:

BLAC100 32M

SPL-1.14.0000

MicroP-Blackstone (LED) v6

I got this error in windows:
[Touch HD Windows Mobile ROM Development] DaveShaw:
LOL, you got it mostly right. :)

I'll clarify a few things for you.

1. u have stock rom - OK

2. use USPL to flash custom rom - OK

3. soft reset = goes back to custom rom - Wrong, soft reset, your SPL goes back to the stock one, and your custom ROM remains.

4. hard reset = goes back to stock rom?? - Wrong, Hard Reset, and erase any changes you have made since you flashed the ROM.

USPL replaces the SPL (bootloader) on your phone with one that allows custom ROMs to be flashed until you next soft reset.

Ta

Dave
[Touch HD Windows Mobile ROM Development] DaveShaw:
Are you running as with Administrator priviledges? If not that might be the problem.

Thanks

Dave
[Touch HD Windows Mobile ROM Development] tMantis:
My antivirus went nuts when trying to download v2.2

Win32:Trojan-gen {Other}
[Touch HD Windows Mobile ROM Development] DaveShaw:
That's expected on some virus scanners, just disable it whuilst you use it.

See here: http://xdaforums.com/showpost.php?p=3075291&postcount=20

Ta

Dave
[Touch HD Windows Mobile ROM Development] desztan:
Do I need to run in dos mode? I'm having administrator right on my PC.
[Touch HD Windows Mobile ROM Development] millex:
USPL 2.3 flash splash boot,radio,rom tested!!

I able to flash splashboot, radio 1.10.25.25 and rom dutty 1.7 in order without any problem.

Thanks Stepw:D
[Touch HD Windows Mobile ROM Development] desztan:
Dave, I still have the same problem as b4. I've login as admin with pw, I run the program in my main windows directory. Anyone can advice pls?
[Touch HD Windows Mobile ROM Development] millex:
Install last .NET Framework.
[Touch HD Windows Mobile ROM Development] stepw:
blac_uspl.exe is a native application, has nothing to do with .NET.

desztan,

Your admin userid may not have admin privileges. The error message you are getting clearly points to permission problems. I would suggest to try a different computer at this point.
[Touch HD Windows Mobile ROM Development] AllTheWay:
Worked Perfect!

This thing worked perfect. Thanks for sharing and all your hard work
[Touch HD Windows Mobile ROM Development] Gatoroz:
BLAC120 support?

Would this USPL support the Australian 850/2100Mhz (NextG) model. I know you said it supports SPL 1.13 1.14 and 1.19. If it comes out supporting 1.15 does it matter if it is 100 or 120?

The Telstra version HTC Touch HD uses SPL 1.15 and is BLAC120 while the WWE version from the UK uses SPL 1.14 and is BLAC100.
[Touch HD Windows Mobile ROM Development] jess6217:
Give him time, he's working on it...
[Touch HD Windows Mobile ROM Development] PJ6363:
Works a treat...

Thanks Stepw,

This works a treat...now runing Dutty's 1.7 on my new Blackstone....

I presume we have to run again prior to changing Radios as well as ROM's...just checking to be sure...

Thanks
[Touch HD Windows Mobile ROM Development] DaveShaw:
Yeah that's right. If you want to flash anything not stock then you have to use USPL everytime.

Thanks

Dave
[Touch HD Windows Mobile ROM Development] stepw:
It's done now, USPL version 2.4 has been posted that supports SPL 1.15.

Please report any issues you encounter in this thread.

Thanks!
[Touch HD Windows Mobile ROM Development] stepw:
What you have described seems to be irrelevant to USPL thread. Did you use USPL to flash Arabic ROM at all?

There are threads in Blackstone forum discussing Arabic support without ROM flashing, you may give it a try instead.
[Touch HD Windows Mobile ROM Development] PJ6363:
Cheers Dave...nice to see u in this forum :)