yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] c0de:
Problems with flashing

Hey man i followed ur steps every step of the way and now my fone is completly wreaked i installed duttys 3.4 XT rom and now i cant get a service provider on my fone it wont come of airplane mode and im getting no signal at all ive tried going back to the stock rom but i cant get it sorted it keeps saying sumthing about an update error when i use the USPL program :S any ideas as to wat i should do?? i only got this fone last week and now i cant even use it :( please help
[Touch HD Windows Mobile ROM Development] morethansunshine:
I dont get STEP 1f..

maybe its because my phone was already 1.56+ when I got it.

can you please explain how to do this?

I see 2 files from Dutty's 3.4 rom but I dont know what to do next.

EDIT: I saw Dutty's post:

SAFEST WAY TO FLASH YOUR ROM IS THROUGH STORAGE CARD METHOD ALSO WITH USPL:

Now I dont get the "Now run USPL." part.

Anyone help?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Reason why your phone didn't work after you used duttys 3.4 is becasue you never followed guide correctly and most likely USPL wasn't successful rssulting in a green screen issue and no reception.

What does your bootloader say i.e. SPL 1.54.000 or 1.14.000 etc?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
If you already had 1.56+ (HSPL) on your device you do not need to use USPL and you can flash straight to duttys rom. I've flashed many roms using SD Card method but I feel personally that using USB can be quicker and easier for noobs. Have you downloaded duttys rom? you should have a .nbh file and a ruu file. Put these both in same folder and put your phone into bootloader. Connect usb cable from pc to phone and double click on ruu file to flash phone.
[Touch HD Windows Mobile ROM Development] rocklovelive:
Ready to scream and then throw my phone through a window and give up.

Keep getting error 262.

Really need someone that can get on MSN and give me a step by step talking through it because I'm extremely frustrated.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Check your PM's.
[Touch HD Windows Mobile ROM Development] jpsst38:
KUDOS

It took me about 7 hours and lots of trials and errors but thanks to your little tut i finally figured out how to change my ROM. Thanks a million. Now to sound like the newb I really am... I have been trying a few different ROMs and was wondering with all of your infinite wisdom or any one out there really, what and where could I find the best suited ROM for AT&T. Before I get, if I do get, the "use the search" theme, I have and am having trouble. (sorry, newb), finding anything. You have been a huge help thus far CrackWhore, got any more to offer I would greatly appreciate it. Thanks to any and all input.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
The thing about custom roms is they are all about personal preference. They are all different. Some have different features, more applications included, etc. Some have more or less bugs than others. Unfortunately I really can't give you a concrete answer. The best advice I can give you is to play with them all now that you've figured out the hard part. When you find one you like, stick with it! :D

I am biased towards Dutty's roms but that's because I've been with them for several years now on multiple devices and am now working with him.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
All roms should be well suited for AT&T. It would be the reception coverage you would need to look at, i.e. the radio. Would start with latest version 1.14, then 1.13 and so on. cRaCKwHoRe & myself are big fans of Duttys roms (partly because we work with him), though Miri's, Davideuck's, Laurentius and kwbr's roms are also awesome. Would depend on what your looking for and whether or not you want WM6.1 or WM6.5. Best advice and I'm sure cRaCKwHoRe would say the same is to try and test each and make your own opinion on each.

EDIT

I see cRaCKwHoRe already responded!!
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Aye, but I forgot to mention the radios, durrr... Thanks for covering that! :p:rolleyes:
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Thats why we make a good (beta) team!! Obviously with the other beta testers as well ;)
[Touch HD Windows Mobile ROM Development] mylove98765:
Update Error "The image is corrupted"

I have updated offical rom to spl 1.54. With USPL, i can update other cooked rom like "Miri WM65". However, I have never succeed to update any dutty rom (both v.3.4 & WM6.5 R1). After updated 100%, I got the update error "The image is corrupted" and SPL message "Update ROM code error Please try again". Same error with both versions.

There are thousands of peopel out there loaded Duttys rom. Is there something special that i have to do? Please help.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Unfortunately you seem to be doing everything right. I have seen other people that have the same issue you do and have not really ever figured it out. Few and far between but I have seen this 3 or 4 times now.

Which phone do you have? T8282 or T8285? Is it branded (i.e. Orange)?
[Touch HD Windows Mobile ROM Development] mylove98765:
It is T8282. Not branded but from the sp (HK CSL) directly.

Really disppointed that i cannot load any dutty rom :mad:
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
With cRaCKwHoRe on this as I've also heard others having this problem. I cannot see any fault and see no reason why using USPL wouldn't work. Would possibly suggest trying HSPL instead of USPL and see if this makes any difference. :confused:
[Touch HD Windows Mobile ROM Development] mylove98765:
I really have some hesitation to use HSPL to void the warranty. May have to run for other rom with no choice. :(
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Your call mate though you are able to restore original SPL etc after using HSPL
[Touch HD Windows Mobile ROM Development] sa2am:
Hi, I need help,

I installed Arabic language pack by mistake and now my most of my phone is in Arabic.

I want to go back to English so...

Ive read n read, ive attempted to flash but cant figure out where im going wrong.

1. I have a 'Orange' branded phone.

2. I placed 'Blackstone_WWE_1.56.405.1' onto the storage card.

3. placed phone to bootloader mode 'SPL version shows 1.14.0000'

4. ran program 'USPL 2.5' and 'blac_uspl' then in boot mode i got message

'1.54.0000'

5. this is where i went 'doolally' i then ran 'unsigned HardSPL_wrapper'

6. now i have 'SPL 1.14.Olinex'

7. and still Arabic text.

Plz help its doing my head in. need to get back to English. tia.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Sounds like all you have done is flashed the old HSPL. If you want to flash the new rom Blackstone_WWE_1.56.405.1 to your phone you will need to flash the new HSPL 1.56 first or you will have lots of issues with your phone afterward.

My recommendation is to download and flash HSPL 1.56.olinex, then flash Blackstone_WWE_1.56.405.1.
[Touch HD Windows Mobile ROM Development] sa2am:
sorry to be a pain, but im a complete 'newbie'

I done a flash in bootloader mode it says 'SPL-1.56.Olinex' but now i have 'colour issues' and text is stil in Arabic.

is it possible for u to put a link to the files i need.

maybe that way i will have a better chance of getting it right. tia.

***Never mind my itchy fingers got it, had to read the 'dummy instructions carefully' ty for help finally got it working with 'dutty 3.4'.

ty again for advice, all i needed to do was download 'dutty 3.4 and run blackstone wrapper (which comes with it) wait for update then a hard reset, as it say's in the guide.

easy when u know how. lol i can goto sleep now its only 2.30am.
[Touch HD Windows Mobile ROM Development] jpsst38:
Thank You

Crackwhore, Spartan, thanks for the quick replys and helpful info. I am looking at radios now. Hopefully I can find one that will hook me up with 3G on AT&T. Thanks again
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Do you have the T8285 (Telstra) model Blackstone? If not you won't be able to receive 3G service because the T8282 does not support the correct frequencies for US AT&T 3G.

If you do have the T8285 any radio you put on it will receive the 3G service. You should just test different radios to see which ones give you the best combination of signal, GPS strength/lock speed, battery life, etc.
[Touch HD Windows Mobile ROM Development] Xerx3sxbl:
I've been through the tutorial on the first page several times now but it just doesn't seem to work.

Every time I try it and at the end of installing the USB driver update it gives me this:

I can't figure out what I'm doing wrong, I'm following the tutorials (this one and several others on this site) to the letter. :( Any ideas?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
That's actually normal. You have updated the driver properly. All you need to do is unplug the phone and plug it back in. Windows will use the new driver the next time it is plugged in.
[Touch HD Windows Mobile ROM Development] eitreach:
I'm having some trouble understanding all this.

I have been wanting to flash my Blackstone now for a while, but I keep reading different instructions wherever I go.

Just yesterday I asked on another site, whether it was nescessary to flash the new official HD 1.56 ROM before flashing other roms, and I was told that it was not - yet here it says that it is.

Who is telling the truth?

For someone entirely new to flashing, these instructions are very hard to understand.
[Touch HD Windows Mobile ROM Development] alex160:
okei, I tried following step 5, but the flashing part is what is confusing me.. I had 1.14 to beginn with, so I jumped straight to step 5. updated drivers and I can connect to the computer from bootloader... ran UPSL.exe and it did as supposed too... but at the beginning of step 5 it says: load the room from step 1d.. how do I load it? I have it downloaded and everything, but how do I flash the phone, or get it to update from 1.14 to 1.15? I am really stupid here? :P
[Touch HD Windows Mobile ROM Development] Xerx3sxbl:
/facepalm

Cheers! It didn't reboot but just gave me a black screen. For a moment it didn't want to turn on either but when it did it gave me the boot screen as said and now it's loading the rom.

Exactly how long will it take? It's been at 0% for some time now...
[Touch HD Windows Mobile ROM Development] alex160:
If I got it right, I am supposed to put the RUU file, the rom from step 1.d into this program: BlackstoneRUUwrapper, but when I did, it started the upgrade process, got to 1% and then says that the program can't be used with my pda? :S
[Touch HD Windows Mobile ROM Development] blackice168:
I had trouble flashing the original 1.56 rom I kept receiving a Connection 202 error.

I realized the whole process can be done off the memory card if you flash all the nbh files in the correct order..

It seems like a much simplier way to go through with the process
[Touch HD Windows Mobile ROM Development] jpsst38:
T8285

I do have the T8285. using the .14 radio now. Now just for tweaking it with photos and such. any tips on where to start with editing that. So far I have found out if i want to put my own photo on the home page I can not use TouchFlo. Whats up with that
[Touch HD Windows Mobile ROM Development] mama888888:
Hi I was just doing everything said in the guide.

When I reached point "Flash new HTC 1.56 rom"

and there in point 5d i normaly ren USPL.exe and had my phone in bootloader mode but it said that i need to(...) update my HTC USB Sync drivers(...)

So I did it. But i still have the same thing.

PS. I have windows XP

Please does someone know what to do??
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
What your SPL say in bootloader?
[Touch HD Windows Mobile ROM Development] Mett:
Need flashback help

Hi,

Firstly I hope Im posting in the right area, If not i apologise.

I falshed to Duttys Rom, after awhile decided the original rom would be better for me.

To flash back. I followed steps 2 to 3D. However, Duttys rom is still installed & now it has very bad colour/graphics.

Actually my HD has become useless. :(

when im in bootloader mode it shows as 1.14

I cant flash duttys again or flashback!! (if i try it gets up to the progress bar stage and it will stay at 0%)

edit: after awhile error 262: UPDATE ERROR (it states there was a communication error)

Can someone please help me?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
You flashed an older stock SPL version (1.14.0000) back to your phone. This is why you were getting the distorted colors and such, and also why when you try to flash a custom rom it sits at 0%. The stock SPL blocks unsigned / custom roms from being flashed.

You need to download the stock rom package that you are looking to run on your phone. Is your phone branded (i.e. Orange)? Was the original rom that came on your phone a WWE rom? Since you have a stock SPL on your phone now you have to make sure you get a rom package with the matching CID that your phone has unless you plan to flash it via USPL or HSPL.
[Touch HD Windows Mobile ROM Development] Mett:
Thankyou for replying.

I have downloaded a "RUU_BlackStone_HTC_WWE_1.14.405.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe"

however, I now can't use USPL, I need the drivers for USB Sync.

Edit: & HSPL gives me error 262: Update error

I have XP and am unable to update the drivers (it says they are older than what i have, therefore cant update)

-Blackstone is not branded

-original was a WWE

Anything else i can try?

ps. when i turn on the phone on bottom right it says:

R 1 14 25 24

G 52 64 25 34h

D 1.59 dutty

When I try flashing "RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe" I get a "ERROR [294] INVALID VENDER ID" message

Thanks again.
[Touch HD Windows Mobile ROM Development] Gatoroz:
RUU 1.56 comes up "No Image file"

Hey Crackwore this is greatwork.

I pretty much have it worked out that you have to have spl 1.56 now to make the 6.5roms work properly. Is that it?

Anyway I get to (1d) Original HTC 1.56 rom (based on 1.54 SPL) - For example: Ruu_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship

All the links on this came up with 2 that were just rar's of "RUU_signed.nbh"

They were titled Blackstone_WWE_1.56.405.1.rar

This wouldn't work with an sd card load with my normal spl (1.15-Telstra)

It said after it started loading- "No image file"

So then using USPL 1.15 it came up with the same error.

Is it just that I need to get the RUU exe file with the radio combined and run it from USPL2.5 GUI.Can I run a nbh file from the GUI?

Anyone still have this file??

thanks
[Touch HD Windows Mobile ROM Development] Digital Outcast:
The invalid vendor ID message means your phone has a different CID than the rom you are trying to flash. Therefore you need to use either HSPL or USPL as you have tried.

You can force Windows to use the drivers included in this thread, even if they are older. During the driver update process, you need to tell Windows not to search automatically for drivers but to let you pick from a list. When the list appears there should a button that says "Have Disk." Click that button and locate the drivers you downloaded from this thread. Once you select it finish the process and unplug your phone. Once the phone shows "Serial" at the bottom of the bootloader screen just plug it back in. Now it will be using the updated driver and USPL should work.

If you still cannot get it to work PM me and we can discuss this over instant messaging.

If you want to flash it via SD card you need to rename the .NBH file "BLACIMG.NBH" and make sure it is on the root of your SD card. However, if you are not using HSPL or USPL and the rom is a custom or CID-mismatching rom, the SPL on your phone will prevent you from flashing it.
[Touch HD Windows Mobile ROM Development] mama888888:
Spl-1.14.0000
[Touch HD Windows Mobile ROM Development] Mett:
Problem solved

I even went to 'C:\windows\system32\drivers' & replaced the drivers manually.

The problem was (for anyone else having same problem) you need to untick the 'Allow USB Connections' in ActivSync.

When USPL tells you to update drivers it actually tells you this

cRaCKwHoRe, thank you for your help and contribution to this awesome forum.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
If your SPL is 1.14.0000 and you want to run the new 1.56+ roms then you need update your SPL to either 1.54.0000 or HSPL 1.56.olinex. This guide leads you through the steps to do this.

Yes, you are right. Sorry I forgot to mention that earlier. Slipped my mind ;) ... but glad you got it solved! :D
[Touch HD Windows Mobile ROM Development] luka car:
thank u

i am an average wm user, so i had a problem with hspl, uspl and im still not really sure what does what... ;) and i still managed to ged RUU_Duttys_V3.6_XT_5.2.21051.1.6.4_1.59.709.0_Radio_52.62.25.34_1.14.25.24_Final to work on my touch hd!!!! thanks a bunch, i couldnt have done it without this post.
[Touch HD Windows Mobile ROM Development] 007K:
Dude, How do i flash manually as you suggested, i've place the .nbh file in the memory card then entered bootloader then what?

Yh, figured out needed to rename the nbh file, but then it doesn't allow me to flash for some reason and i followed the path to USPL and unfortunately "USB PORT could not be opened! Verify that device is connected and spl boot mode is active." I havce no idea why its saying such, please help me.

Much Appreciated
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Are you trying to flash a ROM or a SPL? You can't flash a SPL via SD card (unless you have HSPL loaded and are flashing a different version of HSPL). But if you are trying to flash a ROM you have to rename the .nbh file "BLACIMG.NBH" or it won't work. Then you have to place the file on the root of your SD card and place the phone into the bootloader. If it recognizes the file it will prompt you to load the image file. Otherwise, it will say no image file present and stay in the bootloader.

Note- not all SD cards are compatible with this process. There is a long thread about that floating around. Some work, some do not. :( Also, this requires using HSPL or USPL to flash the rom if it is a custom or CID-mismatching rom.
[Touch HD Windows Mobile ROM Development] nirpaudyal:
Perhaps a stupid question.

Hi guys,

this may seem like a stupid question, but people here seem to know how to answer this!

I need to know how to flash this wm 6.5 rom onto my brand new htc hd!

Please do not be sarcastic as I am simple looking to get this thing working without damaging my htc. step by step guide would be amazing.

thank you.
[Touch HD Windows Mobile ROM Development] 007K:
Read the guide on the 1st page thoroughly before posting
[Touch HD Windows Mobile ROM Development] 007K:
Great guide i'm stuck when flashing the new 1.56 and it says not allow
[Touch HD Windows Mobile ROM Development] 007K:
Now the USPL wouldn't allow saying error no response from device, very pissed off with computer right now!!!!!!!!!!
[Touch HD Windows Mobile ROM Development] The_macik:
Crackwhore you are the boss!!!! thx, I thought my HD is completely done.. :)
[Touch HD Windows Mobile ROM Development] Friend of Bill W.:
Hi Marmin & others,

I was just in the middle of doing a more "simple" guide for flashing but I realized that

Cracky's guide might seem at first fed with too much information but its actually the safest guide you can find

If I or someone else would come up with an "easy" guide we would need to make several individuals due to the fact that many users might be on older ROMS with SPL 1.14 which requires a slightly different procedure than if you have a newer ROM with 1.54 or above.

As I am on WIN XP this might once again differenciate to WIN Vista users

Fallen and cracky ( who once again hijacked a thread :p ) correct me if I'm wrong ( otherwise I would stop learning) ;)
[Touch HD Windows Mobile ROM Development] marmin:
Although I can see your point, I cant help feeling that there are a huge number of Orangeys out there who will mostly be on the older ROM as Orange are sh1t at providing new ROMS. Seeing as the HD only comes "officially" on Orange I think it would answer a huge amount of people even if doesnt help everyone.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
What stage are you at? What does your SPL say in bootloader?
[Touch HD Windows Mobile ROM Development] timmymarsh:
flashing official 1.56 when hardspl 1.14?

HD only offically available on orange? thats not rite is it?:)

Anyway, correct me if im wrong but can you flash official 1.56 rom when the hd has been hardspl'd 1.14 (older duttys rom 3.1 i think) ? from what i have read i think this is ok?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
To flash 1.56+ based rom you will first need HSPL 1.56 flashed. You will need to upgrade your HSPL to version 1.56 or you will experience green screen issues. Just flash HSPL 1.56 and then flash your rom
[Touch HD Windows Mobile ROM Development] timmymarsh:
Great, thanks for clearing that for me, i wasnt too sure as id be flashing back original 1.56.

Thank you:D
[Touch HD Windows Mobile ROM Development] 007K:
hey Thanks a lot for responding, I've just downloaded the original 1.56 rom then loaded it into bootloader then message appears saying "0028002" Error, Not allow. By the way i'm on contract with Orange, so its barred right only way to overcome this is with "USPL GUI v 2.5" right?, when I load it up, put my phone in bootloader, disable active sync then click on USPL.exe i get the message no response from device.

Then me thinking the USB sync drivers might be out of date, went in device manager..etc... then found out they are all up to date.

Now totally stuck i don't know what to do from here.

Much Appreciated,

Please Help
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Windows will indicate that your drivers are in fact up to date. The issue lies within the fact that you need to force Windows to use an older driver for the HTC USB Sync. Follow the instructions.html in the Drivers folder form the USPL GUI v 2.5 download and update the drivers. Once you do so, unplug your device from the computer and plug it back in. Then run USPL and it will now work, temporarily unlocking your device allowing you to flash any rom you like.

Edit: And post back your results too! :)
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
EDIT

Was halfway through typing then noticed cRaCKwHoRe beat me to it!!!!! LOL
[Touch HD Windows Mobile ROM Development] HDuser:
Fallen Spartan vs cRaCKwHoRe

Q: Is there a new war going on ???

Q: Who will get more posts in today ???

Guys just like to say in public that you both add huge value to this site, thanks for your time and effort (which has been noticed).
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
I'm sure cRaCKwHoRe appreciates your comments as much as I do. As for the war, I will humbly bow down to the legend that is cRaCKwHoRe as his guide has helped more people than I can ever.
[Touch HD Windows Mobile ROM Development] 007K:
GUI worked perfectly then BLACIMG file got booted but like 25% through its stops and says Upgrade Rom Code Error Please Try again

Why does PPC makers make it so hard just for a dam upgrade. grrrrr
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Are you trying to flash via SD Card or by using the RUU?
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Wow can you make my head any bigger!?!??! :p I happen to think we make a good team buddy! I am far from a legend... and you help just as many people! :D

LOL that was funny! Thanks for making my Monday work day better ;)

And it's my pleasure to come here and help out. I come here enough for information and help myself so anytime I can give back I don't mind at all. Plus, this is one of my hobbies so it's all good!