Develop Bugs

Upgrade ROM Error

I try to upgrade ROM by SER-v1.2 for my ET180,
When I run XDA-developers-SER-v12.exe,
error occur:
ERROR: GetDeviceData - Unspecific error
error getting devicedata
does anyone know the reason?
thanks

I think the problem is, that the ET180 isn't a HTC Wallaby device.
Never heard this name before......
HTH
Stefan

xiaobaoping1 said:
I try to upgrade ROM by SER-v1.2 for my ET180,
When I run XDA-developers-SER-v12.exe,
error occur:
ERROR: GetDeviceData - Unspecific error
error getting devicedata
does anyone know the reason?
thanks
Click to expand...
Click to collapse
i'm having the same problem. ive got many roms. all of them are showing the same errors. its synced in properly. iam running 1.66 on my O2 XDAII . ive cooked up my own rom which i want to install. or maybe 1.60. 1.66 is not stable, i'm having a lot of problems with sound & missed calles etc.

hyper said:
i'm having the same problem. ive got many roms. all of them are showing the same errors. its synced in properly. iam running 1.66 on my O2 XDAII . ive cooked up my own rom which i want to install. or maybe 1.60. 1.66 is not stable, i'm having a lot of problems with sound & missed calles etc.
Click to expand...
Click to collapse
Are you trying to flash your XDA II with a cooked ROM made for XDA I ??!!

no ... whichever rom i try... i get the same problem...
1. i double click the rom exe file.
2. a small dos window opens up, where i presume its trying to get some data from the phone.. it shows... FAILED TO GET DATA FROM PHONE...
3. the installation window open .... when i click NEXT.. it shows error getting data from phone. please check USB connection etc..
i phone is synced properly before i start the installation. i tried it by disabling the sync as well.
i even tried the i-mate 1.72 rom version . same thing. i even tried the A3.09 cooked rom for wm2003.
whats going wrong? is there a way i can run the exe on the phone itself, by transfering it to the documents file or something???
please let me know.. wierd thing is that i've got my O2 XDA II with 1.66 & not 1.60. i actually want to put 1.60, but when i log onto myxda.com & try downloading it, it says ur phone does not need to download it as it got a latat verion already installed.(obviously ive registered my phone there with my imei no)
any ideas?? please let me know. 1.66 is not stable & im having lots of problems with the sound. & sometimes i get a call, but my phone does not ring.
all this started with SBP's software.. especially Phone Plus II.
since ive removed it, its better but yet not good enough. maybe i should just do a hard reset. But how many times can i keep doing that??
its irritating.

hyper said:
i even tried the i-mate 1.72 rom version . same thing. i even tried the A3.09 cooked rom for wm2003.
Click to expand...
Click to collapse
I 'm totally confused!! ... which ROM you are using to flash which device ??!!!
cooked WM2003 ROMs (like 30.09 and 4.01.16) are made for only Wallaby devices (XDA I) ... the 1.60, 1.66, 1.72 ... etc are made for only Hymalia devices (XDA II) .... now what is the exact error you get when you are doing exactly what ?

.net Errors for Black2.0

Hey guys, Im a bit of a noob but I have been doing a lot of reading and researching prior to my upraged. I started the upgrade (follwing mrvanx's guide) and made sure I installed .net 2.0. However, when I installed the SPL upgrade I got a .net error (which I ignored). Then When I upgraded the radio (1.40.30.00) I got another .net error (both of these on my PC of course). The rom upgrade utility for the radaio did not automatically detect my spl, so I chose the suggestion in the dialog box to "force sspl". I went though the radio upgrade and it completed succesfully, when I check my radio settings on my device it says its 1.40.30.00. I feel a little weary about going through the uprage with these two microsoft .net 2.o errors.
any suggestions?
should I continue?
Thanks in advance for your help.

BTW, After all of this I made a call and my phone still works. I cant verify my SPL version because when I press ok+power+reset it does not go to the boot loader screen, it just does a soft reset.

peezy said:
BTW, After all of this I made a call and my phone still works. I cant verify my SPL version because when I press ok+power+reset it does not go to the boot loader screen, it just does a soft reset.
Click to expand...
Click to collapse
Then you release "power" and "ok" to soon. Keep them a little longer pressed and your fine.

peezy said:
I started the upgrade (follwing mrvanx's guide) and made sure I installed .net 2.0. ...
any suggestions?
should I continue?
Thanks in advance for your help.
Click to expand...
Click to collapse
You may want to try upgrading to .net 3.0. Th devs constantly keep their machines updated. At least worth a try. You using an XP machine?

yes im using xp

ok I held doown the power button a lil longer and verified spl-1.40. I guess even though I got errors its showing my SPL and Radio upgrade so Im gonna try to continue.
Thanks again for your help

peezy said:
ok I held doown the power button a lil longer and verified spl-1.40. I guess even though I got errors its showing my SPL and Radio upgrade so Im gonna try to continue.
Thanks again for your help
Click to expand...
Click to collapse
I got a fatal .Net error on the 1.40 Hard SPL package, after the install was all done. The result was that it didn't get a chance to clean up the temp files in the folder. The flashing worked ok.
When did it crash for you?
Rob

my .net error was never fatal. i just went through with the ROM upgrade and everything seems to be working ok

My XP is doing the same. Has .net 1+2+3. BUT the fatal ONLY comes when flashing BLACK 2.5. AND I dont get BLACK graphics when booting - just white screens. Today and phone - same white.
Have you found a solution?

The message that I got was not fatal. I just kept continuing and everything seems to be working fine. Both my radio and spl show that they upgraded, and I have not seen anything out of order. Is this your 1st rom upgrade or did you upgrade from 2.0?

peezy said:
The message that I got was not fatal. I just kept continuing and everything seems to be working fine. Both my radio and spl show that they upgraded, and I have not seen anything out of order. Is this your 1st rom upgrade or did you upgrade from 2.0?
Click to expand...
Click to collapse
I had several previous roms, but this one I update from B 2.0 (just tried LVSW).

Yeah I saw your other post. Seems like the lsvw rom is working except for the splash. Good LucK!

Error 202 Hard-SPL Update

I am very frustrated with my HTC Touch Diamond as I am trying to update it to Hard-SPL yet when it's plugged into the computer (with active sync running) and I follow all the directions very closely, I go to update the phone and it doesn't show any activity on the phone, the progress bar on my computer screen shows 0%, then it eventually pops up with a message saying Error 202. This is a connection error, yet I am positive that the phone is plugged into the computer. Please HELP!

Hello, Did you run SSPL first? You can only flash hard spl when sspl is active it is a black screen.

I have a Telus HTC Touch, does that make a difference on whether or not this will work?

your diamond is cdma. these only work with gsm.

so by the word 'these' in the last post, you mean that the Rom updates won't work?

I don't think SPL has to do anything with CDMA or GSM. Some ROMs have an option in the phone settings to choose either GSM or CDMA.
ryanseyz: Make sure you have a factory ROM ready before trying the cooked ones here so when things happen unexpectedly, you always have a choice. Next, there are 2 versions of SPL here, try both. Make sure you install EnableRAPI.cab and CertSPCS.cab installed on your device.
Regards,
Carty..

anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax

Phyrax said:
anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax
Click to expand...
Click to collapse
The same here with my mda compact iv. I've tried all versions of the RUU of hardSPL with no result (error 202). When I update the official rom of t-mobile (1.93) with the RUU, there isn't a connection problem and everything goes well.
My device is not simlocked, but i suspect it has a security lock or something like that.

Hello, I have the same problem with a HTC Diamond : error 202 and everything is connected, hotsynched, etc.
Did anyone find a solution ?

anyone??? im having the same problem..

I'm having this issue as well, any solutions?

The same problem
I have a HTC Touch Diamond and have the same problem.
I don't know what i have to do to fix this problem.

I have got the same problem. Add I have problem with align screen, so I can't run any cab on device. Looking for any advice..

i have a htc mda basic ....same problem...any solution...please help....

I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.

Dudubai said:
I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.
Click to expand...
Click to collapse
Thank's..., this solution work for me...!!!

For me too !!! working now !

Thanks it work!

Thanks !!! It works !!!

8525 Dead-End

PLEASE ASSIST: I'VE RECENTLY UPGRADED MY CINGULAR/ATT 8525 HERMES UNIT TO WINMOB6 AND NOW CAN'T GET PAST THE INITIAL WINDOWS MOBILE SCREEN WHERE IT SAYS "TAP THE SCREEN TO SET UP YOUR WINDOWS MOBILE BASED DEVICE." (THE TOUCHSCREEN SEEMS TO BE DISABLED) ALSO, NOW ACTIVESYNC WILL NOT CONNECT TO THE DEVICE. I'M AT A LOSS AS TO WHAT ELSE TO DO (TRIED HARD RESET SEVERAL TIMES WITH SAME RESULT). IF SOMEONE COULD POINT ME IN THE RIGHT DIRECTION - I'D SURE APPRECIATE IT.

ETUMON said:
PLEASE ASSIST: I'VE RECENTLY UPGRADED MY CINGULAR/ATT 8525 HERMES UNIT TO WINMOB6 AND NOW CAN'T GET PAST THE INITIAL WINDOWS MOBILE SCREEN WHERE IT SAYS "TAP THE SCREEN TO SET UP YOUR WINDOWS MOBILE BASED DEVICE." (THE TOUCHSCREEN SEEMS TO BE DISABLED) ALSO, NOW ACTIVESYNC WILL NOT CONNECT TO THE DEVICE. I'M AT A LOSS AS TO WHAT ELSE TO DO (TRIED HARD RESET SEVERAL TIMES WITH SAME RESULT). IF SOMEONE COULD POINT ME IN THE RIGHT DIRECTION - I'D SURE APPRECIATE IT.
Click to expand...
Click to collapse
hmm no need to scream.
Push the OK on left and power on right, and stick stylus in all at the same time. Re run the exe file while it is plugged in to active sync, and see. Which WM6 did you use?

Sorry I'm new at this. I used WM6.1. Which exe file do you want me to re-run. ActiveSync is offline....I can't get it to connect to the unit. Thanks for your assistance.

ETUMON said:
Sorry I'm new at this. I used WM6.1. Which exe file do you want me to re-run. ActiveSync is offline....I can't get it to connect to the unit. Thanks for your assistance.
Click to expand...
Click to collapse
Ok, since you're on ATT I suggest you follow my instruction above, get into tricolour screen (bootloader), and download this
from the post above you will get the shipped ATT rom. Don't worry if activesync is saying is not connected, just run the file. You will then get back to a WM6.

The phone originally came with WM5 and I was upgrading to mess around with the thing. I'm at the tricoloured screen and now downloading the files from RapidShare. Will this get me back to WM5 or to the upgrade. If there is a way, I like to try the HardSPL flash I've been reading about today - will this work on either WM version? Txs & Rgds.

ETUMON said:
The phone originally came with WM5 and I was upgrading to mess around with the thing. I'm at the tricoloured screen and now downloading the files from RapidShare. Will this get me back to WM5 or to the upgrade. If there is a way, I like to try the HardSPL flash I've been reading about today - will this work on either WM version? Txs & Rgds.
Click to expand...
Click to collapse
After you have flashed this WM6.0 you really need to flash hard SPL first, I thought you would have done that already.
Really please read this first before you brick your phone.

No that's the thing. I'm just finding out how I went about this all wrong and maybe shouldn't have been messing this in the first place. Anyhow, my bootloader screen reads like this:
HERM100
IPL-1.04
HERM100
SPL-1.40.Olipro

ETUMON said:
No that's the thing. I'm just finding out how I went about this all wrong and maybe shouldn't have been messing this in the first place. Anyhow, my bootloader screen reads like this:
HERM100
IPL-1.04
HERM100
SPL-1.40.Olipro
Click to expand...
Click to collapse
Well follow mrvanx guide, that's all I had to get on with few months ago.

Many thanks for the advice. So just to be clear I should first run the file I downloaded from RapidShare to get me back to a working WM version, then follow mrvanx guide to flash Hard SPL or viceversa...

ETUMON said:
Many thanks for the advice. So just to be clear I should first run the file I downloaded from RapidShare to get me back to a working WM version, then follow mrvanx guide to flash Hard SPL or viceversa...
Click to expand...
Click to collapse
I have not tried to hardspl a non working phone sorry so I have no experience with that. Give it a go first, and report back.

Still Stuck
zocster said:
I have not tried to hardspl a non working phone sorry so I have no experience with that. Give it a go first, and report back.
Click to expand...
Click to collapse
Nope, didn't work. Here's the report:
ERROR [260]: UPDATE ERROR
The update utility cannot connect to your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA phone.
Check the following:
1. The PDA Phone is connected to the USB cradle/cable.
2. The USB cradle/cable is connected to the PC.
Is there another way to establish comunication with the PDA other than through ActiveSync? Somekind of emulator box or binary software???

ETUMON said:
Nope, didn't work. Here's the report:
ERROR [260]: UPDATE ERROR
The update utility cannot connect to your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA phone.
Check the following:
1. The PDA Phone is connected to the USB cradle/cable.
2. The USB cradle/cable is connected to the PC.
Is there another way to establish comunication with the PDA other than through ActiveSync? Somekind of emulator box or binary software???
Click to expand...
Click to collapse
hmm weird, so have you got .net framework installed on your PC? try it again one more time while in bootloader, plug the phone to USB as long as you can hear the 'ding' sound you should be OK. I have 'bricked' my phone a few times and this always work. What are you trying to flash? the hardspl or the ROM?

Yes, today I upgraded to .net framework 3.5 when ActiveSync failed Microsoft Error took me to their website and offered me the option. I had been running 2.x .net framework and never had a problem would also use same ActiveSync with my old Axim X30.
Yes, I can hear the 'ding' sound and I was trying to run the file RUUWrapper.exe (Hermes ROM Upgrade w/ the option Force using SSPL).

well that shows the other way around doesn't work, so you need to get your phone to a working WM6 state, how is your download going from rapidshare? get it to boot loader mode again and flash that exe file.

Just completed that route - I ran the PDA Phone ROM Update Utility 3.12.3.7 - the process took about 10 minutes to go through 100%, then it restarted and stayed at the Window Mobile screen for little over minute (crossing my fingers), but then just showed the same message "Tap the screen to set up your Window Mobile based device." Please let me know if you have other avenues to try – It’s close to 4am here in Miami, but I'm not sleeping. I’m really glad you are able to assist with this mess – thanks a lot!

ETUMON said:
Just completed that route - I ran the PDA Phone ROM Update Utility 3.12.3.7 - the process took about 10 minutes to go through 100%, then it restarted and stayed at the Window Mobile screen for little over minute (crossing my fingers), but then just showed the same message "Tap the screen to set up your Window Mobile based device." Please let me know if you have other avenues to try – It’s close to 4am here in Miami, but I'm not sleeping. I’m really glad you are able to assist with this mess – thanks a lot!
Click to expand...
Click to collapse
so did you follow it through? and it didn't fix it? you have some bad blocks?
Unfortunately, you need to have some sleep, and read these when you wake up
http://forum.xda-developers.com/showthread.php?t=296722
http://forum.xda-developers.com/showthread.php?t=369434

zocster said:
so did you follow it through? and it didn't fix it? you have some bad blocks?
Unfortunately, you need to have some sleep, and read these when you wake up
http://forum.xda-developers.com/showthread.php?t=296722
http://forum.xda-developers.com/showthread.php?t=369434
Click to expand...
Click to collapse
what does bad blocks mean?
Okay, looks like I've got a Type 2c Brick Situation in my hands.... I think I will take your advice and get some rest and tackle this again later on. I really appreciate your assistance - will you be around again later?

Okay good day, I'm back on the trail. Found shipped ROM on WIKI for HERMES in the following thread - http://forum.xda-developers.com/showthread.php?t=277664
Downloading now...According to pof(moderator) it's a "new rom from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular"
My only question then would be that this appears to be made for WM5 and I performed the WM6 upgrade which is what got me into this mess in the first place - so will there be any conflicts or issues I should now about? I'm about to go ahead with it - if anyone is out there and thinks otherwise, please advise soonest. Thx & rgds, Ed

ETUMON said:
Okay good day, I'm back on the trail. Found shipped ROM on WIKI for HERMES in the following thread - http://forum.xda-developers.com/showthread.php?t=277664
Downloading now...According to pof(moderator) it's a "new rom from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular"
My only question then would be that this appears to be made for WM5 and I performed the WM6 upgrade which is what got me into this mess in the first place - so will there be any conflicts or issues I should now about? I'm about to go ahead with it - if anyone is out there and thinks otherwise, please advise soonest. Thx & rgds, Ed
Click to expand...
Click to collapse
Sounds good man!! Flash it!! oem WM6 roms usually fix allot of issues.. Don't be scared everyone else is busy flashing WM6.1 roms all the time now!

Thanks for the words of support <joshkoss>! Just attempted several times to flash the Shipped ROM I found from <pof> (PDA Phone ROM Update Utility - R:31300 D:51000 U:31101 P:0) and keep getting ‘ERROR[260]: UPDATE ERROR’ message. While instead I went back again to flashing the ROM that <zocster> suggested last night (PDA Phone ROM Update Utility 3.12.3.7) and it does go through the entire 10 minute process until it shows 100% completion both on the PDA and on the PC and then tells me congratulations….etc. I even flashed it twice back-to-back as I read to do in one of the threads – but just keep getting back to the dreaded Window Mobile screen with the same message "Tap the screen to set up your Window Mobile based device."
My next question is this: Why does the PDA Phone ROM Update Utility 3.12.3.7 connect to the PDA, but the PDA Phone ROM Update Utility - R:31300 D:51000 U:31101 P:0 (which I read is the Shipped ROM that I need to get the PDA back to) gives me an error message. Obviously, there is a connection since I’m able to get a 100% completion on the other ROM??? Please kindly advise…..

[TOOL] Task 29 (format internal Memory) without drivers, without mtty-It's about time

Hi all, for all the people like me who do not have the patience or knowledge do adventure themselves in the mitty thread.
This program already exists for X1, HD2, TP2 (for what I know) and I have tested it and it works.
After some search on this forum I have talked to agent_47, who was kind enough to make a task29 program for our HTC Diamonds (GSM version).
Agent_47 or me do not take any responsibility for ay damage done to your device. Use it at your own risk, and only after you have HSPL already installed on your device.
Do not know what a HSPL is, check here:
http://forum.xda-developers.com/showthread.php?t=415191
agent_47 said:
it will flash radio 1.09.25.23
replace the radio if u want to use other version
Click to expand...
Click to collapse
agent_47 said:
now we can mtty our "HTC Diamond" without having the need of MTTY and its drivers
INSTRUCTIONS:
- download and unzip
- run then ROMUpdateUtility.exe and wait for it to finish.....
- device will reboot but will neva go past the bootscreen coz there is no OS to boot
- take our batti and then flash a rom using mSD card or by taking device into bootloader and using customRUU to load ur favorite ROM
DOWNLOAD:
http://rs604.rapidshare.com/files/407049148/task29-diamond.7z
WHATS TASK29\MTTY
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
but the thing is, mtty is and can be hard to use for new users. ... for me,, i was having the worst time installin the drivers needed to run mtty on win7 x64. so u i made this tool for me and for all
CREDIT:
all credit goes to doloop for coming up with the idea
Click to expand...
Click to collapse
and I would add to agent_47, as he adapted this tool for the HTC Diamond

Did anyone tried this?
What's the verdict?

mmm. interesting.

Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also

wapvirus said:
Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also
Click to expand...
Click to collapse
I do not understand how this is possible, I am using Vista and this is as easy as flashing a ROM with a computer. You just connect the device via USB to the Diamond, let active sync finish. Then you just need to run "ROMUpdateUtility.exe" and follow the instructions.
I have tested this, and I can confirm this is working for the European HTC Diamond (bought in Portugal).
This was not made by me, but I do think that more people will benefit with this program. Hopefully people will overcome the initial resistance to change.

Great idea!
I used to MTTY through VMWare Windows XP x86 within my host Windows 7 x64. It was a pain in the ass to get though but it always worked for me. This is a great time saver!
Regards to both of you Johev and agent_47!
Willing to test on my next flash.
Best regards,
Cina.

INSTRUCTIONS:
- take our batti and then flash a rom using mSD cardor by taking device into bootloader and using customRUU to load ur favorite ROM
Click to expand...
Click to collapse
What do you mean? take out battery?
Gonna try this with my next flash

Yeah, the sentence is a bit odd to me to
i asume it means take out battery but still..
i'm not gonna try it until i know it for sure!
--edit--
i couldn't help it and used it anyway..
i assumed "take our batti" means take out battery cuz it worked for me!
my diamond was clean (i guess) and i'm now enjoying a new rom!
Thanx guys!!

I would never post something that I did not test first.
I am glad that you liked it, and I really think it is much simpler then the mitty thread.
Good luck flashing.

rapidshare
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????

character said:
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????
Click to expand...
Click to collapse
http://www.mediafire.com/?jabdu2n968xa9uk here you are

I LOVE THIS TOOL
this isn't good for my ORD.. i'm flashing the hell out of my diamond now!
Getting a HD2 in about a month.. can't wait for it ;D

I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula

to get into bootloader you have to reset your device while holding the volume down button!
then you will get the tri-color screen,
connect your diamond to your pc and flash a rom with a RUU!

fibula said:
I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula
Click to expand...
Click to collapse
To get into bootloader with my diamond:
1) Turn Diamond off, take out battery for 5 seconds.
2) Put battery back inside, and press and hold the centre button (circle) and turn ON the device (hold both buttons) until you see a 3 colour screen
If step 2 does not work, try pressing holding volume down while turning the device on (hold the ON button too). Remember to take out the battery before you do this.
Hope this helps.

Hi!
Does this work by simply copying any ROM's nbh file (instead of radio*.nbg) to folder and executing ROMUpdateUtility.exe? Will it MTTY before flashing the ROM?
Currently I'm trying this method out. It is around at 50% of flashing progress.
I'll report back.
Cina.

thanks a ton dude.... magnificent work...

Now if there were only a way to do it directly from Internal Storage, without RUU...

It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.

cina said:
It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.
Click to expand...
Click to collapse
I remember to see that post on xda developers front page short time ago, but I was not sure if it would work for HTC Diamond.
A universal task29 that would format and flash the device in one single process.
Ironically it was developed a few weeks after I have found an alternative way to mitty that I posted here.
So far I did not hear that it was compatible with Diamond, so I will not risk it.
It's nice to have all these options, because when I searched for something like this a few months ago, I could only find the mitty threat that has more than 80 posts.
For me it was strange as newer devices with very similar hardware and software already had something like this, but Diamond users had to use mitty.
Well I am glad that you like it, and hopefully I helped someone that was not able or willing to do it manually.