Develop Bugs

error [260] message every time

Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)

Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2

I am assuming you mean flash with the new ROM, sammy's in my case?

yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)

No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.

the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.

What operating system en activesync are you using?

On the PC I am using XP and Activesync 4.5

Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.

deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.

BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.

Vista
Using Vista? if so which version?

Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard

It works
Now to discover the joys of WM6 after only having WM5 for two weeks....

/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone

sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?

This seems to be on any rom bar the Dopod roms
and it says 260 connection error

Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.

I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps

htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help

Brick Hermes, stuck at WM6 Screen, help!

Recently tried upgrading my SPV M3100 from WM5 to black WM6. Everything was going fine and I had installed the following
SPL (Bootloader) version 2.10.Olipro (HardSPL v7)
Radio version 1.43.00.00 (optional)
Was updating to ROM version: Windows Mobile 6 LVSW 160607 when USB cable was disconnected before installation ands I am now left with WM6 screen only
Can anyone help?

If you stuck in the wm6 boot screen and have flashed HardSPL 2.10 already you can just enter the bootloader and reflash your ROM again. Why do you use nearly 6 months old ROM (LVSW)?

Did you try to reflash the ROM?
Just switch to the bootloader and run the update again.
If the updater is complaining about "Not able to do so" you might need another ROM, but that method worked to or three times for me.
Cheers,
Jago

tried raflashing but activesync won't pick up phone

you do not need active sync to pick it up. Just enter the bootloader and run RUU.

how do you reflash without activesync?

Read this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick

richard_g_johnston said:
how do you reflash without activesync?
Click to expand...
Click to collapse
Simply - flashing process itself is not done by the Active sync (its icon is grey when flashing). I have tried to flash a ROM this way and it works. You just have to input correct values to the RUU yourself. Bootloader is the tri color screen. You can access it by holding power and ok button while using the stylus to soft reset the device. Hermes will pick up the usb connection.

Please read the WIKI and flash an original WM6/WM5 rom before attempting to flash a cooked rom.. then make sure you know what you are doing before flashing the cooked.

tried both
http://wiki.xda-developers.com/index...Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=286755
still no joy
my device
IPL-1.04
SPL-2.10.0lipro
how do u run RUU in bootloader mode?

richard_g_johnston said:
tried both
http://wiki.xda-developers.com/index...Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=286755
still no joy
my device
IPL-1.04
SPL-2.10.0lipro
how do u run RUU in bootloader mode?
Click to expand...
Click to collapse
Put your device into bootloader mode.
Connect it via USB to your PC.
Run the RUU on your PC (like if you had Active sync working).
Flash the ROM.
(should work with all cooked ROMs)
Update: I tried it now with the Schaps 4.20 - it is working.

When you run ruu it should create ROMUpgradeUt.exe if it says it fails to find the device just run this. I usually take a copy before clicking to close the error box.

where do u locate RUU.exe
sorry I'm not an expert in this

RUUWrapper.exe should be in the folder with the image you are flashing. Sorry if I confused you saying ruu.

When you download the cooked rom it comes in rar or zip containing 2 files - one with extension .NBH and the second one is RUUWrapper.exe (resource upgrade unit), unpack them to one folder and run RUU.exe Be sure to flash only ROM for your device otherwise you will kill it for good.

tried running RUU but get error 260, i.e. cannot pick up phone on USB

See post 12

yeah, tried running ROMUpgradeUt.exe, but still no joy

markafreeman said:
See post 12
Click to expand...
Click to collapse
If this does not work for you - then you can use flashing from the SD card (no USB needed for this kind of flashing) . But try what markafreeman suggests first.

Lets try some troubleshooting:
Whne you connect your device in the bootloader (red green blue screen) to your pc what does it say?
In the white part of the screen on your device it should say USB - then it will work.
If not you can still try flashing the ROM from the SD card - you will need a card reader though for this kind of flashing.

Need desperate help with possibly bricked Diamond

Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.

Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device

http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work

Try a Vodafone branded stock rom before mtty.
Regards,
Carty..

He already tried a stock rom....

Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.

Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000

Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.

Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again

band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.

Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware

janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.

Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware

u have to only push thoose 2 buttom then it will work because u go to rescue mode

But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.

Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey

Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.

Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!

Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!

Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!

HardSPL + MTTY, an almost bricked HTC Diamond!

I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
blanktruth said:
Ok, first of all I did not think that it was this dangerous to use MTTY!.
I followed everything and came to these lines
---------------------
Cmd>task 8
Cmd>
---------------------
But after Cmd>task 8 my device restarted immediately before the second line Cmd> appears and I panicked and disconnected my device and pushed the wrong buttons while "Touch Diamond" logo was on the screen.
Now, nothing happens. I can not start from the beginning because I can not start the bootloader by pushing Vol Down and the small red reset button...
Is there anything else left for me to try? Or should I throw my HTC to garbage?
Click to expand...
Click to collapse
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?

i have the same probnlem!! with my diam300
my bootloader show not Diam300 64m but only 64M on the first position in 3color mode... plz help

Connect the Diamond and run the customruu.exe from your desktop, this should work.

how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....

blanktruth said:
I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
Click to expand...
Click to collapse
The only thing to do now is to flash back a stock ROM or use a custom ROM with the RUU.

Solved!...
Dom1n8tr1x said:
First of, your device is supposed to soft-reset after the "task 8" command and you should have been holding down the "Volume Down" and "Back Buttons" to begin flashing your new ROM. The whole idea of using MTTY is to format your Main Storage and flash a new ROM. Therefor you should have loaded the ROM that you wanted to flash onto your Internal Storage.
Click to expand...
Click to collapse
Thank you for your reply.
Actually I had uploaded the ROM to my internal storage, but during trying to bring my phone to bootloader mode, I formatted the internal storage...
Anyway, what I did now is, first I opened the USB Connection feature from ActiveSync, and then used CustomRUU.exe to Flash the ROM...
Everything is solved now...
Thank you very much all...

ilijan said:
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....[/QUOT
bootloader is all you need to revive the phone
connect it to usb in bootloader mode and just install an oficial diamond rom from an windows xp pc.
it's easy
Click to expand...
Click to collapse

plz write here step by step guide how you solved

How it was solved...
ilijan said:
plz write here step by step guide how you solved
Click to expand...
Click to collapse
Actually the most crucial part was to bringing phone to boot loader mode. And I think I managed that by pushing the Volume Down and Back (the arrow pointing left) buttons immediately after restarting my phone. And I had to do this after taking out the battery and putting it back after 5 sec.
When I pushed these buttons at the start up the phone tried to install the ROM from my internal storage, but as I explained I had deleted it by mistake. Therefore it could not find the ROM. I disconnected my phone from my PC and the screen started to say something like Retrying USB connection or waiting for USB connection, something like that.
I restarted my PC in Digitally Signed feature disabled by pressing F8 during start-up. Reconnected my phone to PC (the screen of the phone was still blinking as waiting or retrying usb connection). And voila the phone screen changed to boot loader mode...
The rest was easy. I opened the USB connection feature from ActiveSync and used CustomRUU.exe with a ROM to flash my phone...
That is all...

1. plug phone in to computer in bootloader
2. run customruu or stock from rom update on computer
3. wait for rom to flash to device
4.???
5.profit

but my booloader dont show model ID: DIAM300 64M what i had befor
and show me only: 64M
and any flash error with invalid model id, i canot flash, rom, stock rom, or hardspl...
understand me.. im not totaly noob... i used mtty X times... but now have this probles

can somebody help me?
my diamond dont have model id...
before i had in bootloader mode DIAM300 64M model id, but now i havent got... its show only 64M,
every rom flash stopped at 1% cose model id error,
every hard spl falsh finished 100% but after flash when device restart write model id error...
i cant do anithing... can somebody help me?

For everyone facing problems after flashing his/her device, take a look at the link in my sig.
There you can find a guide to restore your diamond.

you dont understand me..
i canto flash any rom any hard spl becous my diamond dont have device ID...
in bootloader dont show DIAM300 64M but only 64M
after all flash say error mobile ID...
i try mtty, hard reseted, soft... and nothing
after start its show me only first stock screan, the red text on the right bottom sight dont start: 1.17.25.14
2.100000
geny d2x
its maybe wrong but i forgot what waz here...
how can change device model ID? form 64M back to my stock DIAM300 64M?

Try another version of Hard-SPL, some people report that 1.40 not fully works.
I suggest you try 1.94 Olinex.

my diamond is death... if somebody know how can heal it... plz write me...
my device ID is missing... so i cant flash any rom, any hard spl, any radio...

try this? http://forum.xda-developers.com/showthread.php?t=409425&highlight=invalid+model+id

im not sure but i dont think one can brick his/her phone after hard spl, thats the reason of hard spl in the first place that u dont brick it. boot loader is always present

Guide
if you are using Windows XP try the following steps:
Connect your device to your PC
In Active Sync > connection settings > check Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.

Guide
if you are using Windows XP try the following steps:
Connect your device to your PCIn Active Sync > connection settings > check
Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.

[Q] Touch Diamond not booting and ROM update not working

Hi all,
I wanted to put a new ROM on my Touch Diamond p3700, and managed to bust it.
I followed the MTTY guide from here
http://forum.xda-developers.com/showthread.php?t=416211
I got through the steps OK, but at some point, after restarting the device I noticed that it stop booting.
It would display only TOUCH diamond, and that's it. No other red numbers with RGD.
I tried a hard reset. Nothing. I also did a hard reset with a moviNAN format, and nothing. (though I think this might have made matters worse)
I tried a RUU, and it stays at 0% for a couple of minutes and then gives an error on the PC.
I tried an original ROM, but it says Not allowed for this Vendor ID (goes up to 1%).
I tried Hard SPL 1.24 a couple of times but this also stays at 0% for a couple of minutes and then gives an error.
I am totally out of ideas, but I'm only an extreme beginner, so I do hope there will be a solution.
Any help would be greatly appreciated.
Thanks.

try with HSPL 1.93

hspl 1.93
Hi.
Thanks for the reply
I assume you're talking about this
http://forum.xda-developers.com/showpost.php?p=9246383&postcount=2
I downloaded the archive, extracted it.
As I said, the phone doesn't boot, so I can't connect it to activesync,
but I did go to bootloader (red green blue screen), inserted the cable and showed USB.
Reading your steps I saw that I might have missed the hspl step inside the MTTY tut. So basically I did the mtty part without the hspl.
I connected the phone to the PC, it sais USB, I ran ROMUpdateUtility.exe, the grey screen appeared with 0%, stayed like that for 5 minutes and program gives an error that it can't communicate.

hexer4u said:
Hi.
Thanks for the reply
I assume you're talking about this
http://forum.xda-developers.com/showpost.php?p=9246383&postcount=2
I downloaded the archive, extracted it.
As I said, the phone doesn't boot, so I can't connect it to activesync,
but I did go to bootloader (red green blue screen), inserted the cable and showed USB.
Reading your steps I saw that I might have missed the hspl step inside the MTTY tut. So basically I did the mtty part without the hspl.
I connected the phone to the PC, it sais USB, I ran ROMUpdateUtility.exe, the grey screen appeared with 0%, stayed like that for 5 minutes and program gives an error that it can't communicate.
Click to expand...
Click to collapse
there is no HSPL step to perform in mtty mode. go to bootloader and report back the SPL version you have.
there is no reason you shudnt be unable to format. maybe you might need a jumpSPL if ur previous spl is hard spl-ed

In bootloader is says:
DIAM 100 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x32

hexer4u said:
In bootloader is says:
DIAM 100 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x32
Click to expand...
Click to collapse
you are still having the stock SPL...
lets get you HSPL...give me a few minutes while i come with attachements and instructions

download+unzip to C:\ (recommended)
- connect ur device in bootloader mode
- dont do mtty at this stage
-run the DiamondCustomRUU.exe
report back

ruu err
I get this
Code:
ERROR[262]: UPDATE ERROR
The ROM Update Utility has encountered communication erros during the update porocess.
The program will guide you step-by-step to recover fomr the errors so you can continue witht the update

hexer4u said:
I get this
Code:
ERROR[262]: UPDATE ERROR
The ROM Update Utility has encountered communication erros during the update porocess.
The program will guide you step-by-step to recover fomr the errors so you can continue witht the update
Click to expand...
Click to collapse
did u try flashing this HSPL?
whats ur current location so i can recommend a flash of stock rom.

I'm in Romania. My phone was locked on Vodafone.
What do you mean "flashing this HSPL"? This error I get when running DiamonCustomRUU.exe in the archive you posted. It starts the progress bar on both PC and phone, stays at 0% and after 5 minutes, it gives that error.

okay. download this. and run the diamond-sspl.bat
if it runs successfully and ur screen turns black...then run DiamondCustomRUU.exe again to flash SPL 1.93
if the batch file does not run let me know...
btw i wil be here till we can sort this out

I connected the device in bootloader. Shows USB.
I ran diamond-sspl.bat
and says:
Warning: no device connected.
Waiting for device to connect...
A window pops up, and says if I want to retry. Hitting yes just pops again.
So basically it says that it can't copy whatever it needs on the device because it's not connected. But the device is connected in bootloader and says USB.

okies....lemme make a cross check of the HSPL on my device and report back
in the meantime, do you have your STOCK ROM? the original rom that came with your device.
if you dont, but still know the rom version to download, check here....
http://shipped-roms.com/index.php?category=windows mobile&model=Diamond
in the event we cant proceed any further, atleast we can recover ur device to start up again with batch file...

Try this version of HSPL which allow a temporary SSPL on ur device in order to allow a transition of SPL..
as usual report back. this is the last step...after this if there is no progress we may have to resort to stock rom and then start at step 1.
btw HSPL 1.93 confirmed working on my device.

The same issue. Error 262.
Isn't the problem somewhere in the communication between the PC and device?
When I run ROMUpdateUtility.exe the device does go to the grey screen with progressbar at 0%, but that's about it.
I don't have my original ROM, and I don't know the version,
but I think this should be it
RUU_Diamond_HTC_WWE_EastEurope_2.03.479.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe

You can try restarting your PC and then try to confirm any USB conenction problems.
But if on the device it appears USB in the bottom half of the bootloader screen it means the connection is okay.
Now this is a flash (see attachement) i only use as a last resort. If this doesnt flash, consider downloading the rom file you jus mentioned and flash it...
Download the attachment and run the .exe file. Follow the steps...if it works...try flashing any HSPL u have downloaded.
also try this link from htc.
http://www.htc.com/ro/SupportDownload.aspx?p_id=133&cat=2&dl_id=483
input ur device serial (which is under ur battery) and see if u can download. this is more direct approach to download the correct rom file for ur device.

YES!
Fixed it.
I switched USB ports, left the default driver (2007, not 2004 as was said in MTTY), used the ROM I said above and it worked.
Thanks a lot for your assistance.

good!
and if ur up for another try. then start with the attachement HSPLwSSPL
dont do any mtty. jus try to see if u can flash HSPLwSSPL...
but if ur done for the day, i wish u a rest well earned.... hehe...
anyways feel free to drop a PM in my inbox shud u decide...