yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] Black Antitoon:
Well, maybe it is for UPX compression... Some exes are compressed with UPX, and AntiVirus don't like that, since this can also be used to create viruses which are more difficult to detect... But this is just a guess. ;)
[Touch HD Windows Mobile ROM Development] jaypeev_9:
Thank you very much for this guide!
[Touch HD Windows Mobile ROM Development] feryox:
10. How to use it?

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.

If everything goes well, your device will restart and SPL version label should read "1.14.USPL" indicating that USPL was loaded successfully.

If SPL version does not include "USPL" or if the screen is black, soft reset and try again. If "USB" label disappeared and did not reappear, reinsert USB cable.

You can then start RUU update to flash RUU_signed.nbh. Once RUU update is completed, device will restart using regular flashed SPL.

If you want to flash from SD card instead, make sure your SD card is not inserted when you enter the bootloader originally.

SPL will try to install it and would fail if blacimg.nbh is not signed by HTC. Insert the card after "USB" label comes up in SPL but before running USPL.

You can run "blac_uspl.exe ?" to get command line parameter help. Only 1 parameter is accepted and that is the name of an SPL file you want to load. You can load an MFG SPL or HSPL. USPL automatically takes care of allowing unsigned/cooked ROM flashing with any SPL you use.

Hi, I've follow your steps but it still cant work.

My current SPL is 1.14.0000

My OS is Vista.

I've tried all the steps, it doesnt restart as what u've said. So, I manually soft reset it, but the bootloader still show SPL 1.14.0000

What went wrong?

Thxs.
[Touch HD Windows Mobile ROM Development] HDuser:
Well lets look at this pal

Wiki has a page for USPL

This page has a comment about Virus warnings

This Commnet points you to this post

http://xdaforums.com/showpost.php?p=3111901&postcount=78

The next post has a comment that WIKi Has been updated.

http://xdaforums.com/showpost.php?p=3111958&postcount=79

The first post of the thread has comment on Virus

This commnet points you to this post

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

So both sources in fact point you to

https://www.virustotal.com/analisis/d87a314caf4da880a5935bbb1df0f121

The top of that page reads

Virustotal is a service that analyzes suspicious files and facilitates the quick detection of viruses, worms, trojans, and all kinds of malware detected by antivirus engines.

I would say it is fair to assume that your question of " WHY!!" is in fact answered by the fact that it seems that Most virus software do not see this file as a threat.

Now on top of this we could also presume that if it was a virus then somebody in the thread would have made a comment which again if read would point you to:

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

http://xdaforums.com/showpost.php?p=3111901&postcount=78

Which would mean we have come back to our starting point.

Now is the question of "why" infact answered as it does not say anywere that USPL does in fact have is a virus only that some Virus detection software sees it as having a virus....

but there again it also says does not say anywere that you need to use USPL in the fist place.

So myslelf I pass on this "Why" in the same way as I have given up working out "what came first the chicken or the egg".

On the lighter side of things:

As always I feel if one uses software that is based on mircosoft systems and one feels unsafe with this the best choice is to buy an "apple" ..............(and eat it), But thats me.
[Touch HD Windows Mobile ROM Development] HDuser:
What went wrong? ----> My OS is Vista.

Did you read the wiki flashing with USPL of vista and Windows 7 users, could it be that you have a problem with your drivers as you have made no comment of ever beaing able to ever flash a rom. Its a thought and could be wrong.
[Touch HD Windows Mobile ROM Development] mglancy23:
just flashed my device using the software

worked a treat, great piece of software
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Agreed. The culprit is most likely your drivers. This can be easily determined by the following:

1. Put your phone into bootloader and connect it to your computer .

2. Run USPL from a command window so after it runs it does not disappear. This way you can read the application / error text. I would recommend running the command window as administrator as well.

3. If it says something to the effect of: "Error opening USB port" when you have it connected and showing "USB" in the bootloader on your phone then you need to update your drivers. If you need instructions on this follow step (0) of the guide in my signature.
[Touch HD Windows Mobile ROM Development] FutureCow:
What does this error mean:

HTC Blackstone USPL version 2.5, Apr 5 2009

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

-b54c2b4fc835}...

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&a5e925&0&6#{25dbce51-6c8f-4a72-8a6d-b5

4c2b4fc835} parameters could not be set

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&a5e925&0&6#{25dbce51-6c8f-4a72-8a6d-b5

4c2b4fc835} timeouts could not be set

ERROR: No response from device

HTCSBye!>.L.HTCE

I have SPL Version 1.14.000
[Touch HD Windows Mobile ROM Development] Digital Outcast:
What operating system are you running on your computer?
[Touch HD Windows Mobile ROM Development] this_mike:
+1 on the USLP failing in Vista

Hi, I've followed the steps laid out in the guide but am unable to progress past this problem:

"Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&a5e925&0&6#{25dbce51-6c8f-4a72-8a6d

-b54c2b4fc835}...

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&a5e925&0&6#{25dbce51-6c8f-4a72-8a6d-b5

4c2b4fc835} parameters could not be set

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&a5e925&0&6#{25dbce51-6c8f-4a72-8a6d-b5

4c2b4fc835} timeouts could not be set

ERROR: No response from device"

I'm running Vista Ultimate and (even with the enforced driver signing disabled during boot) I'm bring told that my drivers are up to date after pointing device manager at the usbas extract location...
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Did you "force" Vista to accept the driver as instructed in the link in step (0d) of my guide?
[Touch HD Windows Mobile ROM Development] this_mike:
*Smacks self upside the head*

Not exactly, no. When I went back and did it step by step (instead of just browsing to the file location), it worked.

Thanks
[Touch HD Windows Mobile ROM Development] Bisis:
A comment...

Looking at how it works.. I think it's really impossible to brick the phone. No?

If also a rom update goes wrong it should be ever possible to put blackstone in bootloader mode... so it's needed only to change to the right rom!

Am I thinking right?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
For the most part yes. Although if you are loading a different SPL and that goes south, you could potentially run into issues getting back into the bootloader.
[Touch HD Windows Mobile ROM Development] Black Antitoon:
...but consider also that flashing SPL is never 100% safe, no matter if this is done through SSPL, HSPL, USPL or what. Even installing an official ROM which contains an SPL upgrade can be dangerous, the only difference is that this should be covered by the warranty. However I haven't read of a single guy here who bricked his HD when flashing the SPL so far, so it must not be really that dangerous... ;)
[Touch HD Windows Mobile ROM Development] winstonysz:
hahaha, long time to search for this, now get it! Thank you so much.
[Touch HD Windows Mobile ROM Development] Praythai:
I have same problem. Anyone can help me pleaseeeeeeee!
[Touch HD Windows Mobile ROM Development] Black Antitoon:
It is probably looking for the image file on the SD during that stage. I have no idea about why this should ever happen, but anyway If you remove the SD card before entering SPL mode it will probably work.
[Touch HD Windows Mobile ROM Development] riz157:
Originally Posted by stepw

No, you don't need to start RUU before or at the same time as blac_uspl.

There's probably an error message in that command window that you are not noticing. Start command prompt (Start->Run->cmd), then execute blac_uspl from command prompt window to see the error message.

Post the error message and I may be able to tell you more.

sorry but I'm really novice at these things but how do you execute blac_uspl from comprompt window? I have the same problem tru#y to run uspl and nothing happens.
[Touch HD Windows Mobile ROM Development] mancheung:
hello...if I using this uspl...

It show me error message:No image error ..

and then show spl is 1.15uspl..
[Touch HD Windows Mobile ROM Development] Kleriker:
Hi there,

i have a problem right now. Iam running 32bit XP Pro but i am also getting this message:

D:\uspl>blac_uspl.exe

HTC Blackstone USPL version 2.5, Apr 5 2009

Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&1a439df4&0&1#{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.

USB is connected, but it won´t work. Do you have any idea ?

Greets,

Alex
[Touch HD Windows Mobile ROM Development] Kleriker:
Never mind. I had to kill the "wcescomm.exe" in the taskmanager. Now it worked fine.

Greets,

Alex
[Touch HD Windows Mobile ROM Development] A_2:
remove uspl

pls help me for remove uspl .

in run uspl on command prompet not work and after disable allow usb connection work me but not reboot device.

:confused:

------------------------

only wvga htc hd
[Touch HD Windows Mobile ROM Development] Mc S.H.O.:
hello

i have that problem error massege to.....what are you doing execly with that wcescomm.exe i dont understand that can you help me with that
[Touch HD Windows Mobile ROM Development] Bisis:
HSPL 1.56 has been released...

someone explained that using USPL is not safe when ROM include SPL...

so is it better for us to use HSPL? And to revert back to original SPL if neceassary?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Many people have used USPL to load the stock HTC 1.56 rom (which includes SPL 1.54.0000) for mismatching CID's have had no issues so I would disagree here. It really depends on your preference if you rather have a stock SPL and run USPL to flash every time you want a new cooked rom, or to have HSPL and just flash whenever you want.
[Touch HD Windows Mobile ROM Development] Bisis:
Also I upgraded my HSPL with stock 1.14 SPL and then using USPL I flashed new HTC 1.56 rom and then some other roms..

So I love USPL and for me it's not a problem to use it. I'm happy to have stock SPL so...

But I was referring to someone that wrotes in this thread that USPL is not safe for SPL flashing! If it's not so... I fully agree with you.
[Touch HD Windows Mobile ROM Development] cmonex:
X1 memory layout does not make it possible to use this specific hack. (maybe other kind of exploit but not the one the blackstone USPL is based on.)
[Touch HD Windows Mobile ROM Development] cmonex:
if you pull USB, while wdata is downloading the SPL binary, cert checking function will return with a processed size in bytes that mismatches the size specified in NBH header, thus the NBH flashing function will reject the image.

same for SD download.

I dunno about crashes however :)

only specific problem I can see if the ROM contains SPL not supported by you yet and then the OS flash (inside same ROM file) gets interrupted and device has no matching CID rom for it publicly.

still there are solutions (other than starting to support that SPL version), as we can make goldcard :)

EDIT: in the case of USB download, forget the thing about cert function not fully processing the stuff. the execution of wdata will stop much earlier when checksum of downloaded stuff will not match. also I think (my memory is a bit rusty here) HTCE is needed before it even goes on with checking the downloaded stuff.
[Touch HD Windows Mobile ROM Development] cmonex:
if stepw has no time just contact me on IRC. :) (stepw didn't seem to mind it when I checked out how the exploit works. :) )

PS: trinity exploit is not based on the same stuff, even though that's also by stepw (before pof reimplemented it). kaiser is incompatible with that though, memory layout issues regarding USB stack.
[Touch HD Windows Mobile ROM Development] stepw:
Hi cmonex, good to see you back!

Thank you for the comments, you are absolutely right.

I prefer to exaggerate the problem a tad to keep people aware and careful.
[Touch HD Windows Mobile ROM Development] poohpoohguy:
hi

i m currently flashed with dutty v3 rom using uspl 2.5, but i wanted to reverted back to energyrom, can i use uspl2.5 again to flash the eneryg rom ? please note dutty v3 is 1.56 while energy is not.

can some one help ?
[Touch HD Windows Mobile ROM Development] Black Antitoon:
If Dutty's ROM was working fine (no strange colours) it probably contained the 1.54 SPL. In this case, before flashing back to the energy you'll first have to reflash the official stock ROM, which will restore the stock SPL. Then you can use USPL.
[Touch HD Windows Mobile ROM Development] biladze:
Damn, I've got a problem.

I flashed to Dutty's v3 and had this green screen thing.

So I tried getting back to 1.14 using USPL, but the window just closes at "Starting USPL..."

I really don't know what I should do now.

When I try flashing using RUU(official 1.14ROM), it shows "Invalid Vendor ID"

Duh :/ Help appreciated
[Touch HD Windows Mobile ROM Development] ducatisto:
sorry stepw, THAT's not the point. I trust YOU, but not an account... ;-)) accounts can be hacked. So I just asked...and I guess that's fair. THX
[Touch HD Windows Mobile ROM Development] Laurentius26:
Forgive me but I think you forgot one step here.

If the screens says "1.14.USPL" it means USPL is correct loaded.

But you need to take usb cable out and put it back in, in order to flash the rom isn't?

I like to tell you this to avoid convusion, I hope you don't mind!

Thanks for USPL, I tried today, awsom work! :)
[Touch HD Windows Mobile ROM Development] batista70:
I tried it too, it worked flawlessly :)

Thank you, now i've a ROM ITA NO BRAND !!!!!
[Touch HD Windows Mobile ROM Development] superfuffo:
Vista version...

Hi,

i vote for a vista version of USPL... hopefully that will work with vista64 also...

Anyone else?
[Touch HD Windows Mobile ROM Development] MDAIII Avdo:
Litle confusion !!

When I run it on PC (NB also) nothing happen !!! only quick blank DOS screen and nothing else.

I have XP with SP3 ,does the SP3 makes a problem or something else? I unchecked allow conections in activesync,put device in boot loader mode and run black_uspl.exe......and nothing happend.

Please explaine procedure step by step.!

Do I have to run only black_uspl.exe or some other programe like "CustomRUU for Blackstone" together?

I have

BLACK100 32M

SPL-1.14.0000

MicroP-BlackStone (LED)v6

thanks,
[Touch HD Windows Mobile ROM Development] batista70:
Did you put off microSD ???
[Touch HD Windows Mobile ROM Development] kolokas:
why not for vista?please......
[Touch HD Windows Mobile ROM Development] stepw:
Thank you for your feedback. This is part of the instructions in first post:

If "USB" label disappeared and did not reappear, reinsert USB cable.

This should not be necessary, but sometimes it has to be done.
[Touch HD Windows Mobile ROM Development] stepw:
I'll see what I can do. I definitely won't be able to test on vista64 though.
[Touch HD Windows Mobile ROM Development] stepw:
No, you don't need to start RUU before or at the same time as blac_uspl.

There's probably an error message in that command window that you are not noticing. Start command prompt (Start->Run->cmd), then execute blac_uspl from command prompt window to see the error message.

Post the error message and I may be able to tell you more.
[Touch HD Windows Mobile ROM Development] MDAIII Avdo:
Alow USB conection

My fault in comm prompt line error:disallow USB conection (Im only disallow conections )and then everyting be fine.

Thanx
[Touch HD Windows Mobile ROM Development] Laurentius26:
Well.. I did already succesvol loaded USPL and flashed a new rom. ;)

The thing is once USPL is succesvol loaded (It shows in bootscreen) on the device it disconnect's automatic and I'm not able to flash.

Once I disconnect and reconnect the usb cable I'm able to flash.

That's what I'm trying to tell you. :)
[Touch HD Windows Mobile ROM Development] MDAIII Avdo:
Excellent

Excellent job!!

Bravooo Maestro :)
[Touch HD Windows Mobile ROM Development] Nikos2k:
would be very interested in that too
[Touch HD Windows Mobile ROM Development] asci:
Please may you build a Vista version?

THX so much!
[Touch HD Windows Mobile ROM Development] zeer:
can't auth?

Opening USB port \\.\WCEUSBSH001...

Authorizing...

ERROR: Current SPL version is not supported

QUAR100

SPL-0.45.0000

MicroP-7

is there hope?
[Touch HD Windows Mobile ROM Development] stepw:
Definitely not, unless I can get myself a Quartz (HTC Touch MAX 4G).
[Touch HD Windows Mobile ROM Development] Laurentius26:
I need to correct myself about what I've writed earlier in this thread.

No clue why it disconnected the first time but it works fine now. :)

Again thanks for your work Stepw!

Leo :)
[Touch HD Windows Mobile ROM Development] anomalos:
I'm interested!!

:)
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Have you run USPL from a command prompt or used the GUI so you can see the error text? Have you updated your drivers for the HTC USB Sync in Windows device manager?
[Touch HD Windows Mobile ROM Development] biladze:
Thanks for your answer. Well uh I thought that the USB drivers were for Vista(I'm on XP 32bits)

For USPL I used the command prompt. There was no error text, the window just shut itself down after "Starting USPL...", my HD's screen also went black for a second, returned with the Windows sound meaning Disconnected/Connected.

I'll try using the GUI.

EDIT2: Oh what a bloody noob I am, didn't read the whole thing :/ Yeh I didn't install the USB drivers, Jesus.

Working when tired isn't worth it :D I'll keep you updated, thanks!

EDIT3: IT WORKS, I LOVE YOU MAN (homoway)
[Touch HD Windows Mobile ROM Development] Black Antitoon:
This is fine. Does the phone reboot and load USPL when you see that message?
[Touch HD Windows Mobile ROM Development] tararura:
Thank You the Creator

This is the only thing which saved my phone. refer to my thread.

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

thank you thank you thank you!!!:):):):)
[Touch HD Windows Mobile ROM Development] rhoerbe:
Black!!! Man YOu Are Great! I find myself lost but your post clarify everything...

I Just Flashed my room for the first time and I Loved it, thanks to you!

Great Job! Congratulations.
[Touch HD Windows Mobile ROM Development] jerichos:
Ok Stoopid question time, but I need help

Guys, I need a simple straight answer, although I have looked thru the forum for the last 2hours 15 minutes - I have a small window in which to update the device.

My simple question is this:

Can I go from Dutty's 2.2 to 3.3 using SPL 115 as per normal, i.e. use 115 to get the HD in the mood and apply the Dutty Rom as per usual.

No updates to 156 or anything?

Yay or Nay...

Thanks guys. If you flame me it's because I deserve it, not for a lack of looking...

Jericho
[Touch HD Windows Mobile ROM Development] Digital Outcast:
What is your SPL now, without USPL loaded? If it is less than 1.54.0000 then no. Dutty's v 3.3 is based on the HTC 1.57 rom, which is incompatible with an SPL version below 1.54.0000. You would have to flash an HTC 1.56+ rom first to update your SPL to 1.54.0000 and then flash Dutty's v 2.7+ rom.

If you read the guide in my signature it explains this in more detail.
[Touch HD Windows Mobile ROM Development] jerichos:
Crack, you tha man - OK, so update to htc 1.56, then dutty 3.3 through USPL
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yes, that is correct my friend :D
[Touch HD Windows Mobile ROM Development] wsayed:
Hullo, I just moved from Athena forum to Blackstone forum as I just got new blackstone 2 days ago. I just want to confirm my understanding; If I used USPL V2.5 I will be able to flash all kind of cooked roms including 1.56 roms.

Cheers
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yes. Just make sure you follow the process correctly depending on what you current SPL version is. Otherwise you could have mismatching SPL and ROM versions and have some serious, but recoverable, issues.
[Touch HD Windows Mobile ROM Development] wsayed:
My current SPL is 1.14. Apprceiate your advise.

Thank you buddy
[Touch HD Windows Mobile ROM Development] Digital Outcast:
You will need to upgrade your SPL version if you intend to run 1.56+ roms. You either need to flash the new HSPL 1.56.oliNex SPL or flash a new(er) HTC rom that will upgrade your SPL to 1.54.0000. Once you have chosen either route you can then flash a custom rom based on the 1.56+ HTC rom.
[Touch HD Windows Mobile ROM Development] wsayed:
Thank u so much for the feedback. I read your reply in the other thread & sorry for the inconvenience. I am reading your quide now buddy.

Cheers
[Touch HD Windows Mobile ROM Development] protoism:
cant extract uslp

tired downloading different versions of uslp (2.2, 2.4, 2.5) from 2nd post - but when try to extract just get a blocked by windows msg from win zip - the only thing in the un zipped folder is the disclaimer txt. anybody any ideas why this might be? have windows vista 32 using trial version of winzip. given its a very small fil is there a non zipped version? appreciate any help, thx

protoism
[Touch HD Windows Mobile ROM Development] DaveShaw:
Your AV software will be eating the exe. Disable it and try again.

Ta

Dave
[Touch HD Windows Mobile ROM Development] Felipe Rodriguez:
Noob question

From CMonex comments and yours, the HTC has a more solid flashing procedure than I initially thought, as I am starting to cook for the Touch HD, I would like to know if just by having on the phone an original SPL (SPL 1.54 in my case) and flashing via USPL will I be always able to re-flash the phone even in the case of a really badly cooked ruu-signed.nbh file (even if the OS even boot, just imagine the worst .nbh possible)?, I remember cooking for the T830 in the past and I was always able to reflash it, no matter how bad my cooked ROM was, even if the OS crashed and didn't boot :) .

BTW: what is a goldcard?

Thanks in advance!
[Touch HD Windows Mobile ROM Development] DaveShaw:
Yeah, if you keep the stock SPL you can use USPL whenever you want to flash a cooked ROM, even if the current ROM won't boot. (Or just flash your carriers ROM if you have stock SPL and need to get a working ROM back on your device).

If you are starting to cook, I'd recommend Hard SPL though, I flash my phone 5-10 times a night when trying to fix bugs in my ROMs (I don't have the option of USPL on my Kaiser though :o).

I'm not 100% on a goldcard (so here's my best guess)... It's a method that allows you to flash other signed stock ROM's that don't have region ID protection. So mainly ROM's for other languages... (I'm sure stepw / cmonex will correct me - It's just one of those things I've not looked into :o)

Ta

Dave

Dave