yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] eyeofthetiger:
Dutties ROM has now been installed!

Thanks to everyone who helped but big thanks to crackwhore!:)
[Touch HD Windows Mobile ROM Development] stefan063:
USB problems...

After installing this ROM,driver for BOOT LOADER aren't good anymore...I tried to install Lost in Asian 5.0,but I couldn't because I have triangle on HTC Mobile In Device manager...I tried to reinstall but no success...Can I still enter Lost in Asia with generic HTC usb drivers not those modified that I used to install this DUTTY v.?

Regards
[Touch HD Windows Mobile ROM Development] Digital Outcast:
I'm not sure what Lost in Asian is... but you're saying you can't put your phone in the bootloader now? If you put your phone into the bootloader and attach it to your computer via USB, does it show "USB" at the bottom of the bootloader screen? Also, once you do does it show in the Windows device manager as HTC USB Sync? Is that what you're talking about that shows up with a "triangle"?" :confused: You need to use the drivers attached to the first post of this thread.
[Touch HD Windows Mobile ROM Development] 007K:
LOL, I'll stay online today, i'll keep messenger on. Hopefully we'll meet finally
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Am also online atm :D
[Touch HD Windows Mobile ROM Development] Dad Pee:
Hi Greetings everyone

I am sorry did not know where to post, well i am a new member and a new windows mobile user having read much on this forum i decided to join the forum, technically i wish i could help in any way but not savvy in this area.

that said i just bought a new Htc Touch HD phone and will like to undertake some exploits in Rom customisation and need some help from you guys if anyone can help out pointing me to the thread thanks.

To do

1. Change my device Rom 1.56.406.1 (43972) French to English

The radio 1.54.0000

2. Change from WM Professional 6.1 to 6.5

If any kind one can walk me through to achive this a big thanks and a good Day

Pee
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Your just need to follow guide mate. Your SPL is 1.54.0000 yes? (BTW this is not your radio. Your radio would be something like 1.14.25.24)

If you already have SPL 1.54.0000 all you need to do is run USPL V2.5 and then flash whichever 6.5 rom you want. It tells you in guide which step to go to depending on what SPL you have, i.e. in your case if you have SPL 1.54.0000, you would go to No.6
[Touch HD Windows Mobile ROM Development] xX SPION KOP Xx:
cRaCKwHoRe is the MAN

Just a quick note, this guy is awesome, he has helped me, step by step, patiently, through this guide, cheers cRaCKwHoRe, I will be donating to you....have a beer on me mate! ;) YOU ARE A F**KING LEGEND !!!!!! Make this man a MOD! :D:D
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
I'm sure he'll be glad to hear you say this.......and a Liverpool Fan!! Excellent
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Thanks guys :D I don't know about Liverpool though :p ... just kidding!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Update to "Dummies guide to flashing 1.56+ roms [v 2.0]"

I just posted a massive edit to the first post. The guide should now seem more intuitive to follow and also includes explanations and instructions allowing users to select a route for either HSPL or USPL. Also, all relative downloads are now attached to the post, minus the rom of course. :D

Fitting it into 10,000 characters was hard, to say the least. :p
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Well done mate. Looks like all that hard work paid off. Do I hear a new mod???

EDIT

Removed text
[Touch HD Windows Mobile ROM Development] Digital Outcast:
It is sticky :P
[Touch HD Windows Mobile ROM Development] peterkling:
HTC Driver Update Error in Win XP

Thanks for this explanation.

But maybe somebody with Windows XP experinces following problems, too.

In step (USPL2c) "USPL2 - Updating HTC USB Sync driver" there is just an explanation for Vista. - OK, seems not very different from XP except the services-thing.

when updating the Driver manually I get an Error (code 10) ("Device cannot be started")

What now?

I use wceusbsh.inf

Do I have to stop any processes before updating? (Stopped USB connection in ActiveSync)

Seems as this is also the problem in step (USPL3d) with the result in an connection Error [262].

Correct?

How to solve this?

I solved my problem temporarily out by using method 1.0:

-USPL+flash ship-ROM 1.56

-and then USPL flash custom ROM.
[Touch HD Windows Mobile ROM Development] nizzon:
Sorry if this is a stupid question.

Im currently still on SPL-1.14 Olinex.

Can i just follow these HSPL-instructions to convert to 1.56.OliNex?

(I just have to check cuse I have small memory of a specific thread for updating from SPL-1.14 Olinex)
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
If you currently have HSPL 1.14 Olinex all you need to do is flash HSPL 1.56.Olinex and then you fine to flash any 1.56+ based rom
[Touch HD Windows Mobile ROM Development] stefan063:
No matter... It is in boot loader...Doesn't show USB,because there are usb driver problem...I already flashed previous with duttys 3.7 and all worked well from stock...but when I plugged in 2days ago it says usb Conn problem...I did install drivers (if I didn't i couldn't flash with duttys)...Tried to reinstall but nothing! What should I do now?
[Touch HD Windows Mobile ROM Development] Dad Pee:
Thanks fallen and cRaCKwHoRe late to reply been busy. i did check and i had 1.56.01inNex and 1.13.25.24 so i flash it with HPSL Wraper blackstone_156oline then again with RUU Blackstone HCKL WWE 1.57 so my device have the English version good and the radio version is now 1.14.25.24 with Rom version now 1.57.831.1(47324) IT is the correct way of doing it even though it seems to work find and some minor changes. now i can i go directly with 6.5 rom will go back to read the tutos in page 1 again thanks.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
When you get "Error (code 10) - the device cannot be started" this is normal. All you have to do is unplug the USB cable from your phone, wait a few moments, and plug it back in.
[Touch HD Windows Mobile ROM Development] marmin:
Guys, I think I may have stumbled on a good tutorial that explains what I was mentioning earlier. Its nowhere near as comprehensive as Crackwhores instructions, but the piccies are pretty and the instructions seem almost straightforward................

Theres my problem, Cracks seem to contain a hell of a lot more stuff, so is this simplified version, well, too simple and misses important stuff.

http://i.gizmodo.com/5281397/how-to-install-windows-mobile-65-right-now

Heres the cheeky bit.................

All you guys that know what you are doing, Crackwhore, Fallen Spartan etc would you mind casting a beedy over at the link and see if its any good. If its OK could we copy (with permission of course) and sticky, If not could it be ammended and used here either way as a "REALLY DUM dummies guide" in addition to Crackwhores version for the more experienced/problematic ones?
[Touch HD Windows Mobile ROM Development] DaveShaw:
It's lacking a bit on the bootloader flashing instructions. But overall it's sound. However the links are for the Diamond (which has a good Tut by tnyynt) and the Raph (which has an excelent Tut by mskip) - and I've yet to read the 1st post of this thread ;).

Dave
[Touch HD Windows Mobile ROM Development] mwaldi3:
Firstly Thankyou for this Guide It really makes 100% sense to me now!

With the one instruction above I just wanted to say that for me it worked with my Phone on and connected with active sync. It worked perfectly then.:D
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yeah you can run the RUU with the phone connected via ActiveSync as well. I just prefer it via bootloader because ActiveSync can cause some issues ;)

Plus, when the RUU starts it puts your phone into the bootloader anyhow!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Have you read the guide now that I've edited it? I totally re-wrote it earlier today. I read the link you posted and the instructions are very similar to mine. I just don't have screenshots. I am limited to 10,000 characters as well :(
[Touch HD Windows Mobile ROM Development] DaveShaw:
If you want another post, just ask ;)

Dave
[Touch HD Windows Mobile ROM Development] chessergb:
Many Thanks mate worked a treat
[Touch HD Windows Mobile ROM Development] Digital Outcast:
*poke* *poke*

Any chance I can have a follow-up post? Pretty please! :p:D

Would only be useful after the first post, obviously :rolleyes:
[Touch HD Windows Mobile ROM Development] DaveShaw:
Done, bill is in the post :p

Dave
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Awesome thanks! Hate to press my luck but actually it would be nice to split it across three posts if I can get one more?!?!? :eek:
[Touch HD Windows Mobile ROM Development] DaveShaw:
No probs.

Ta

Dave
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Thanks Dave. Now it's split up better and I have more room in the first post to explain stuff. Will probably expand into updating drivers as well ;)
[Touch HD Windows Mobile ROM Development] DaveShaw:
Nice one mate ;)

Dave
[Touch HD Windows Mobile ROM Development] Noodled24:
ok, really wanting to give this a go now. the rewrite seems much simpler to follow, cheers for that crackwhore.

i have a stock uk orange blackstone at the moment. In bootloader SPL is showing as 1.14.0000 and i am able to connect to the PC in and have "serial" change to "usb" - am i right in thinking that i can just follow the guide from (HSPL1) on post 2 of the guide? I dont have to do anything differently because of the orange rom?
[Touch HD Windows Mobile ROM Development] mwaldi3:
Exactly 100% like me, With the new guide which is spot on I did a full flash of my Phone last night. I am on Orange too, with spl 1.14.0000

The only thing I did was I used the HSPL route to do my phone as this seemed less complicated. A windows XP machine. And I Started the HSPL program with the Phone ON and NOT in the Boot Loader. This seemed to work. I am now running Duttys windows 6.5 Rom and everything has been working! I can say it was well worth it.:D

Thanks again to the guys who pass on all this Knowledge!:)
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yeah, Orange really doesn't have anything to do with the process ;)

HSPL or USPL takes care of everything :D
[Touch HD Windows Mobile ROM Development] Noodled24:
When I try to do this (not in the bootloader) i get "Error [260] connection". When trying to run HSPLWrapper_blackstone_156OilNex.exe.

If I put the phone in Bootloader, the phone gets as far as a grey screen with a white "loading" bar, but never gets further than 0% before I get another connection error.

This is in Vista 32bit, and after running HSPLWrapper_blackstone_156OilNex.exe as administrator.

I'm a bit stuck as to what to do. Can anyone help? I've never had any problems connecting via USB to my PC.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Download and extract the attachment. Copy "SSPL-Manual-TouchHD.exe" to your HD. Run it on your HD (when your HD is booted up and in Windows), wait until 1.07.OliNex tricolour screen appears and says "USB" on it, then run the HSPLWrapper_blackstone_156OilNex.exe on the PC again.
[Touch HD Windows Mobile ROM Development] marmin:
Cheers Crackwhore, I hadnt noticed you had totally rewritten it all, looks cool, gonna go for it now when I get a mo.

Might put a post on the other sections to highten awareness to Orangeys, now it looks tons easier.
[Touch HD Windows Mobile ROM Development] Noodled24:
Cheers, that seems to have worked, tricolour screen now shows SPL-1.56.Olinex

During a normal boot however the screen now has some wierd psycadelic distortions on the colour. Is this normal?... if I move to the next step in the guide and flash a new rom, will this sort it? or do I need to redo something at this stage?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Yes, that is normal because the rom you have on there originally is not compatible with the newer SPL. Once you flash a 1.56+ based rom to your phone it will return to normal ;)
[Touch HD Windows Mobile ROM Development] robrauy:
USPL 3d

Hi,

Great guide - Many thanks for all the hard work!

I'm stuck at the moment on USPL 3d.

I run HSPLWrapper_Blackstone_156OliNex.exe, replace RUU_Signed.nbh with the one from RUU_Signed_Blackstone_stockSPL154 and start the update.

I get a progress bar on the PC and one on the phone. Neither move from 0%.

After a few minutes the application says that the update has failed and enters recovery mode.

Luckily, I do not need to do much as the phone reboots fine afterwards..

Any ideas ?

Many thanks,

Rob
[Touch HD Windows Mobile ROM Development] robrauy:
So sorry - Just seen the above post :o
[Touch HD Windows Mobile ROM Development] Noodled24:
Sweet, now have duttys 6.5 R1 on my blackstone

The new guide is fantastic. Easy to follow and it doesnt look anything close to as daunting as it used to :)

Thanks so much for your help crackwhore m8. :D
[Touch HD Windows Mobile ROM Development] robrauy:
Fantastic! Now the proud owner of a new ROM :)

Many thanks,

Rob
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Awesome! Glad to hear you guys like the re-write! Plus, it's nice to see you figure it out! :D
[Touch HD Windows Mobile ROM Development] DaveShaw:
Meh, it's alright :p

Nah, seriously, nice tutorial, easy to reference the steps and what not :).

Dave
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Gee thanks Dave... what a confidence booster :p

Haha, just kidding. Thanks for the extra posts earlier!
[Touch HD Windows Mobile ROM Development] Crossbowow:
Thanks so much for an excellent, clear HSPL guide. I was daunted at first glance, but your instructions are perfect and the update went like a dream.

I'm extremely grateful for all your efforts!
[Touch HD Windows Mobile ROM Development] winwiz:
Somebody please help!

I was running a 1.56 ROM before my HD decided to pack up! So I reflashed it to a normal ROM and sent to HTC to repair. I have the handset back today and am having problems flashing

I have followed the instructions but keep ketting "Error [260] connection" message. I have tried running HardSPL in bootloader mode and the USB connections disabled and enabled without any luck. Also have tried SSPL-Manual-TouchHD.exe without any luck.

One thing I have noticed when i enter the bootloader is a bar across the top saying SECURITY UNLOCKED. I am running SPL 1.140000

Please advise

Thank you
[Touch HD Windows Mobile ROM Development] Digital Outcast:
You tried running SSPL-Manual-TouchHD.exe from within Windows (on your HD) right? And it brought it back to the bootloader? Does it show SPL 1.07.OliNex at that point? If it does and you still get error 260 when you try to flash, you may want to try using USPL and see if that works.
[Touch HD Windows Mobile ROM Development] winwiz:
thanks crackwhore. i repeated the same process and it is working now. Using USPL!

many many thanks for your help! MOD status for sure :D
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Woot! Glad to see you got it sorted! :D
[Touch HD Windows Mobile ROM Development] attiffe:
i place my phone into bootloader ... everything goes write and when it starts to update rom ( when it says it will take 10 mins time to update and when the install bar appears ) nothing happens it jst stucks on 0 % , and then it goes to recovery mode and recovers normally ( i mean phone starts normaly )

what am i supposed to do Or am i doing sumthing wrong ? if ne One can help plz ! thancs !
[Touch HD Windows Mobile ROM Development] attiffe:
also can any One advice to shud i go HSPL or USPL .. plzzzzz ??
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Did you read the first post?

It is entirely up to you. Most users will find that HSPL is easier because you only have to do it once. USPL has to be done each time you want to flash a custom or CID-mismatching rom.

What are you trying to flash when this happens? It's staying at 0% because the SPL on your device is preventing you from flashing unsigned roms to the device. You need to flash HSPL or use USPL first.
[Touch HD Windows Mobile ROM Development] nadimaj:
Blackstone - Trying to flash NRGs W6.5 ROM but getting ERROR 262.

I'm using HSPLWrapper_Blackstone_156OliNex.exe (3.27.43) (dated 23/04/09) together with NRG's latest W6.5 ROM but am getting ERROR 262 (UPDATE ERROR). What could I be doing wrong?

I'll add to say that I am having to boot the device into it's boot loader manually to even get the tool to detect my phone in the first place. But then the above.

AV disabled, Firewall disabled, can't see any other things that could be inteferring.

Please someone! Dieing to get away from 1.14 :mad:
[Touch HD Windows Mobile ROM Development] tru88:
thanks alot

i checked the bootloader and i got

Blac100 32M

SPL-1.4Olinex

MicroP-BlackStone (LED) v6

so i assume i have to follow your guide

thanks alot ...
[Touch HD Windows Mobile ROM Development] stone1971:
I have been working around for hours now, but I think I'm pretty close now.

I have the 1.56 ROM, I have managed to get the SPL-1.15. USPL in bootload.

But I can't find RUU update to get Dutty's ROM inside my HD.

Can somebody please help?
[Touch HD Windows Mobile ROM Development] johnpatcher:
Are you looking for CustomRUU?
[Touch HD Windows Mobile ROM Development] stone1971:
I don't know?

I read the thread Blackstone USPL, or how to keep your stock SPL and flash cooked ROMs:

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.

I don't know what RUU update is.
[Touch HD Windows Mobile ROM Development] jacquiegardner:
Thank you!

CRACKWHORE, you ROCK!

Worked perfectly. I would suggest you add this to your guide for dummies. Would probably keep you from having to answer the same questions again.

You guys on XDA developers never fail to amaze me. I can't wait to be done with school to be able to get back into to this stuff. I really want to learn to cook. Done with school and board exams next February. I can't wait.

Thanks again,
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Maybe if you were a female ;)
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Correct, and no problem!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
From this point (HTC 1.56 rom already loaded, base SPL of 1.54, and SPL 1.15.USPL when USPL is running) all you need to do is run the BlackstoneRUUWrapper.exe that is included in Dutty's rom downloads and it should flash the rom to your phone!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
RUU stands for Rom Update Utility. It's the program that runs in Windows that flashes a rom to your phone.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Haha, thanks :)

And good point, there was a tiny blurb about it but I added a bit more clarification! Thanks!
[Touch HD Windows Mobile ROM Development] jacquiegardner:
cRaCKwHoRe,

I was hoping it was all down hill from here, NOT! I figured I could return to the process and pick up where I left off, doesn't seem to be the case:

I successfully flashed the 1.14 stock ROM. (Really nice to be rid of the Telstra bloat ware.) But when I tried to Flash Hard SPL for Blackstone OliNex, the next step in the dummies guide, I got the following error:

ERROR [262]: UPDATE ERROR

The ROM Udate Utility has encountered communication errors during the update process. The program will guild you step-by-step to recover from the errors so you can continue with the update.

After recovery...

Error recovery has been successful and the update process is ready to resume. Now your device is ready for TOM update. Please exit error recovery and run the ROM Update Utility again.

Then I get the same error when running the update again.

What's this all about? I was hoping not that I'm back to stock ROM I wouldn't get any more errors. Is this because I had to run the USPL 2.5 to get around the Vender error?

Can you tell me what to do now? Even if I can't make it any further in the process, I have a much better ROM. Thanks to you!

Thanks again. I am definitely making a donation when this is all through.
[Touch HD Windows Mobile ROM Development] Charlie3999:
Hi, I'm having trouble with the final part of flashing. Done everything. Trying to drag nbh into wrapper and this is coming up with an application error all the time, it says this application failed to initialize. Any help please.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Are you actually trying to load HardSPL or are you loading stock SPL? What is your SPL version (not running USPL on it) if you put your phone in bootloader ?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Any chance of a screenshot of the exact error?
[Touch HD Windows Mobile ROM Development] pisiiki:
Problem with the unsigned driver in vista x64

I think the given driver in 0c doesn't work with vista x64 at all. After restarting the system with unsigned driver support and following all the steps in that web the system refused to use the driver telling me that it is not a valid driver. I will try with an xp machine btw.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
I don't personally run x64 so I don't know for sure... but I have been told they work. I will try to look into it.
[Touch HD Windows Mobile ROM Development] rikin:
hi, nice steps, i followed all steps till 6, and all is as per your steps, but when i try to do step 6.A i.e. flashing with dutty 2.9 RTM, all is good till the progress bar stuck up at 0%, i tried all, but still the same. i tried installig drivers agin, hard flashing the 1.56 rom, but no results. the progress bar sticks to 0%, all the SPL and all instructions are perfect as per your guidance. when i do the CustumRUU and the progress bar is stuck at 0% for while [i waited 5 mins or more] and nothing happens but as soon as i take the USB cable out of phone it says 260 , that means the phone is still connected.

what could be the problem?

please help, as i need duttys rom installed, and cannot work without that.

its the dutty's 2.9 RTM without MSVC .
[Touch HD Windows Mobile ROM Development] jacquiegardner:
cRaCKwHoRe,

SPL version is 1.14.0000. I am trying to load Unsigned_HardSPL_for_Blackstone_OliNex. That is the next step in the process after load 1.14 ROM, right?

Seems I'm a really good test case for the Dummies guide :)
[Touch HD Windows Mobile ROM Development] Charlie3999:
that is all that comes up when i drag the nbh into the ruu wrapper, the application error.