Develop Bugs

XDA EXEC Upgrade problem

Hi,
I was updating my o2 xda exec with new rom upgrade when my PC crashed causing upgrade to unexpectadly stop. It is now stuck on a grey screen with the word serial on top and v1.00 down bottom. I have tried hard reset but to no avail. My pc wont recognise it at all now. Any suggestions or will i have to leave in to be fixed
Thanks for any help
Bily

This happened to me the first time I flashed my Alpine. Just put the device in the cradle, load up the flashing program on your PC and just start over, it *should* just see the device and carry on fine. It did for me, and I did nothing special except reboot and cross my fingers.

done that but it stops saying problem with country ID error. It is unlocked but is a UK model

Someone else on the forum was experiencing the same problem... To be quite honest, I haven't the foggiest idea as to why this is happening, it never happened on my Alpine but I've had nil experience with the Exec so I can't proffer any tidbits of advice. Sorry :/ (You might want to go browsing the Exec forum though, see if there's any info relating to this problem on there, if you've not already done so of course.)

Hello Billy G
Put ur exec in bootloader mode.Use MaUpgradeNoId.exe to upgrade yr device since u r getting contry id error.The above file can b searched in forum..put it in the same folder where the upgrade files are there.
u will get back yr device alive...

Done that, but get a cant find RUU.dll. No idea how to extract the ROM/Upgrade. Installshield seems to do it automatically. Not exactly a whizz on PC

First of all, you have connection between your device and PC, this is really good.
1. Get flashing program - ROMUpdateUtility-NoVendorID.zip
2. Get the correct flash for your device. I will repeat - CORRECT flash file for your device. If your will flash with incorrect version, bootloader could be overwritten, than your device is really in a bad shape. Not every service center will be able to recover.
3. Normally rom update/upgrade is .exe file it inclides binaries and flash rom itself. Get winrar. Instead of executing .exe update/upgrade, open it with winrar and extract it to temporary location.
4. In one of the folder will be file ROMUpdateUtility.exe. Replace it with ROMUpdateUtility-No.Vendor.ID
5. Start ROMUpdateUtility-No.Vendor.ID.exe
6. Perform flash.
7. Process may slow down at some stages, don't warry, just be patient.
8. Make sure you understand that downgrade process is not always possible. Other words, if you decide to go back to your previous flash or original flash, you may have problems.
9. Buy UPS.
good flashing

Cheers, managed to get it done. Was afraid i was going to have one expensive brick here :?
Thanks for all the help.
Great resource here. Keep up good work

fdp24 said:
9. Buy UPS.
Click to expand...
Click to collapse
That is a SOUND piece of advice, from one UPS owner to another

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

WLAN ERROR NOW FIXED!!! Thanks to gruptnt

Thanks to gruptnt over at this thread: http://forum.xda-developers.com/showthread.php?t=490681
WLAN IS NOW FIXED!!!!!! Flash without worry anymore.

my wifi work great again
That is perfect solution !!!
thank !!!

complimenti....
penso proprio che questo tread sia
sticky
eng: sticky for ever

binht611 said:
my wifi work great again
That is perfect solution !!!
thank !!!
Click to expand...
Click to collapse
I also have the same problem... i visit the above post but the post is very big... can you please tell me what steps you follow....
Thank you.... i also have trinity and after this error my trinity hangs frequently.....

These two posts should help:
http://forum.xda-developers.com/showpost.php?p=5313622&postcount=340
http://forum.xda-developers.com/showpost.php?p=5314726&postcount=345

WLAN IS NOW FIXED!!!!!! Flash without worry anymore.[/QUOTE]
Dear Supersport....
thanks for update...
but after the complete procedure (all report was ok), the phone dont restart.
i can see the rom number...etc etc, but remain the htc logo on the black screen.
How can resolve this ?
Thanks a lot for your help.
Vito95

vito95 said:
Dear Supersport....
thanks for update...
but after the complete procedure (all report was ok), the phone dont restart.
i can see the rom number...etc etc, but remain the htc logo on the black screen.
How can resolve this ?
Thanks a lot for your help.
Vito95
Click to expand...
Click to collapse
Have you tried to flash another ROM to the phone and see if that gets it going again?

First of all thanks to you SuperSport and GRUPTNT for this
But for me, unfortunately, it doesn't works, i'm unable, when running Mtty116, to get the USB connection. I got Vista and i think it's the problem.
If somebody got an idea about it...

kabtv said:
First of all thanks to you SuperSport and GRUPTNT for this
But for me, unfortunately, it doesn't works, i'm unable, when running Mtty116, to get the USB connection. I got Vista and i think it's the problem.
If somebody got an idea about it...
Click to expand...
Click to collapse
yes, confirmed, you must XP

SuperSport said:
Have you tried to flash another ROM to the phone and see if that gets it going again?
Click to expand...
Click to collapse
Hi, after some hours the phone is restarted.
Now the only problem is that in comm manger application, Wlan dont work.
remain in off state (red botton).
can you help me?
regards

narshorn said:
yes, confirmed, you must XP
Click to expand...
Click to collapse
Please see this update.
Now, you can run MTTY in Windows Vista and Windows 7. I've made a Video Tutorial Showing how. It's Step 2b on this page:
http://forum.xda-developers.com/showpost.php?p=5314726&postcount=345

my god, you worked late yesterday on this...
thanks for this and everything else, but again, i think that nothing is going to be easy for me...first, if i disconnect USB from mobile center, it's not in the computer management anymore...so i can't change the driver...next if i reconnect the USB connection, i can find it in the device manager but i can't change the driver because:
On my Vista home premium(32 bits operating system) : ''The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 32-bit systems.
and on my Win7(X64 Home Premium): it's the same message except for X64
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the splash screen

kabtv said:
my god, you worked late yesterday on this...
thanks for this and everything else, but again, i think that nothing is going to be easy for me...first, if i disconnect USB from mobile center, it's not in the computer management anymore...so i can't change the driver...next if i reconnect the USB connection, i can find it in the device manager but i can't change the driver because:
On my Vista home premium(32 bits operating system) : ''The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 32-bit systems.
and on my Win7(X64 Home Premium): it's the same message except for X64
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the splash screen
Click to expand...
Click to collapse
Ok, I think I forgot to mention one step. Before you disconnect WMDC, be sure your phone is in Bootloader Tri-Color Screen Mode. (Also, before flashing any ROM, be sure to be in Bootloader Tri-Color Screen Mode. [Power/Camera/Reset]) Your Computer will Still be able to see the Phone in Device Manager after WMDC is Disabled.
I don't believe this will work on 64bit Windows. I tried and stopped after a couple failures.
I'm sorry your WLAN is not working still. That's not good and we will do our best to get you back to WiFi.
Looking at the Video again this morning, it does appear to go sort of fast. Hit Pause when needed to read the text pop-ups.
Next thing is I believe you may be selecting the wrong option when you browse for the driver. Be sure you are selecting the option: "Let me pick from a list of device drivers on my computer". If you get a warning that the driver is not the correct driver, BUT you have the option to go ahead with the installation, go ahead and install it. It's a Windows XP Driver, so Win7 will not suggest installing it. But when it's all over, you will be removing it again and reinstalling the Win7 Driver.

SuperSport said:
Ok, I think I forgot to mention one step. Before you disconnect WMDC, be sure your phone is in Bootloader Tri-Color Screen Mode. (Also, before flashing any ROM, be sure to be in Bootloader Tri-Color Screen Mode. [Power/Camera/Reset]) Your Computer will Still be able to see the Phone in Device Manager after WMDC is Disabled.
Click to expand...
Click to collapse
That was it...i succeed to install the driver and WIFi works again
SuperSport said:
I'm sorry your WLAN is not working still. That's not good and we will do our best to get you back to WiFi.
Click to expand...
Click to collapse
don't be, you do so much for the community here
Thanks again...

kabtv said:
That was it...i succeed to install the driver and WIFi works again
don't be, you do so much for the community here
Thanks again...
Click to expand...
Click to collapse
That was FAST , good work! Happy to hear it worked for you.
Also, be sure to delete the XP driver from Device Manager, and re-scan the system to install the original driver. And then, re-activate your USB Connection in WMDC.

kabtv said:
my god, you worked late yesterday on this...
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the 3G Asia splash screen
Click to expand...
Click to collapse
did you experience that...?

kabtv said:
did you experience that...?
Click to expand...
Click to collapse
Did you use SSPL_TRIN.exe to enter Bootloader Mode before flashing? I think that is necessary for a full flash of OEM.

SuperSport said:
Did you use SSPL_TRIN.exe to enter Bootloader Mode before flashing? I think that is necessary for a full flash of OEM.
Click to expand...
Click to collapse
i used the sd card method...

kabtv said:
i used the sd card method...
Click to expand...
Click to collapse
You would still need to use SSPL_TRIN.exe to put the phone into a special Bootloader Mode because the OEM ROMs overwrite the HardSPL on your phone. This special mode allows that to happen.
Copy SSPL_TRIN.exe & your TRINIMG.nbh to your phone's SD Card Root. From your phone's File Explorer program, browse to your SD Card and tap SSPL_TRIN.exe to run it. If asked, go ahead and say "Yes". This will enter a special Bootloader from which you can flash the OEM's.
Only use this method to flash Back to OEM ROMs and NOT for Normal Flashing. You want to use the HardSPL's Bootloader to flash Cooked ROMs to protect your phone.
Download SSPL_TRIN.exe
And, remember, after flashing an OEM ROM, be sure to flash a HardSPL back on your phone BEFORE Flashing Custom ROMs again.
Sorry everyone for getting off topic. kabtv, if you need more help with this, PM me, I'd be happy to help.

SuperSport said:
You would still need to use SSPL_TRIN.exe to put the phone into a special Bootloader Mode because the OEM ROMs overwrite the HardSPL on your phone. This special mode allows that to happen.
Copy SSPL_TRIN.exe & your TRINIMG.nbh to your phone's SD Card Root. From your phone's File Explorer program, browse to your SD Card and tap SSPL_TRIN.exe to run it. If asked, go ahead and say "Yes". This will enter a special Bootloader from which you can flash the OEM's.
Only use this method to flash Back to OEM ROMs and NOT for Normal Flashing. You want to use the HardSPL's Bootloader to flash Cooked ROMs to protect your phone.
Download SSPL_TRIN.exe
And, remember, after flashing an OEM ROM, be sure to flash a HardSPL back on your phone BEFORE Flashing Custom ROMs again.
Sorry everyone for getting off topic. kabtv, if you need more help with this, PM me, I'd be happy to help.
Click to expand...
Click to collapse
Hi,
I have moved to hd, so I didn't come to this forum since then...
I will try to explain a little better the HSPL and official roms.
First, there are several HSPL for trinity. The best one is olipro 1.30, so this th eone we want to get into the trinity.
First the theory, in a .nbh file we have several parts: ipl,radio,spl,splash,os,extrom In an official rom contains all parts, a custom ROM normaly nowdays contains os only. Whith older kitchens contains splash+os
The HSPL of olipro is protected so it is not overwrited by the roms. So it is safer, and you can't get a brick if you don't flash the ipl part.
The SPL is the tricolor program, so when flashing you should view the spl that you have in the trinity.
Whith the customruu of the trinity there is a file called enterbootloader.exe which is transmited to the pda and executed to display the spl. This file is SSPL_TRIN.exe renamed.
Ok, so this are the scenarios:
1) you launch the romupdate whith as/wmdc connected:
Enterbootloader is transmited and executed -> Special SPL 1.07
So when flashing you will flash every part of the nbh (all for oficial, os for custom)
2) you enter manually in boot loader
The SPL in your device -> olipro 1.30
So when flashing you will flash only (ipl,splash,os,ext)
The safer method is to put manually the bootloader mode and flash. You can have the HSPL whith an offical ROM whithout worries. Though there is an exception: you want to update the radio.
If you want to update the radio use method one so you run the other SPL.

Sense 2.5 help

Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz

I've read all the howtos and I tried flashing a 2.5 rom i found(i think its the right kind) and I keep getting error 262

Did you flash hardspl? What rom are you trying to flash? I suggest trying energy rom leo.

If by flash you mean download and run it on my computer then yes and the energy leo is the one i tried

When I click on the leo customRUU I get "windows cannot acces the specified path device of file. you may not have the appropriate permission to access this file "

http://forum.xda-developers.com/showthread.php?t=550540

I alrdy read that a few times over
"Flashing via ActiveSync with USB Lead (thanks to OliNex)
1. Download HardSPL package from *HERE* and extract to an empty folder
2. Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable and it must not be in Flight/Airplane mode (i.e. radio should be on)
3. NEW: Internet access is required as the program checks online for updates and license
4. Run Rhodium-HardSPL_V2_00R3.exe on PC, make sure it's launched from a local drive (not through network drive, etc.). XP requires Admin logon and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, allow it. If you get an AntiVirus warning please ignore it, it contains no harmful code (just used a packer to compress it)
5. Follow steps as prompted in the HardSPL program. If this is the first run of HardSPL on a device after Hard Reset, you must select Automatic Flash Mode (first button in Welcome Screen)
NOTE: You should usually go for Automatic Flash Mode. The Manual Flash option is only to be used as noted below and you must only attempt the Manual Mode option if Automatic Flash Mode or SSPL-Manual.exe already put device in black screen. Any other errors triggered while running in Autoflash Mode will have to be fixed as instructed in the error message.
6. It will ask you to wait while it prepares for the flashing, press OK
7. Now it should go through without any error messages, if one does pop up then follow the instructions included in the error text. If no specific instruction is shown then ask for help in the thread, but this should not ever occur (as this means a really fatal error occurred)
8. At this point the phone hopefully went to a black screen (reporting version as 1.01.C-SSPL only using "info 7" in mtty), this is the SSPL version, which is temporary. Then RUU will instantly launch
9. NOTE: When RUU says it will Hard Reset do not worry, it is not going to do that. Also when it says the flash will take 10 minutes ignore that, it will only take a minute or so
10. SPL flashes, device automatically reboots, job done"
So im here asking for help

did you download the package from "here" in the directions first and flash that before going onto a custom rom like nrg's?

yes i did.....

never ran into any problems myself so i dont know whats up but have you tried on another computer? flashed through sd card?

Dragonmaster0430 said:
Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz
Click to expand...
Click to collapse
Ok, which device are trying to flash? Does tilt too mean "Tilt 2" or "tilt also"? If you are talking about a Tilt, you are in the wrong forum. This is Tilt 2 (Touch Pro 2/Rhodium).

WillardZ said:
Ok, which device are trying to flash? Does tilt too mean "Tilt 2" or "tilt also"? If you are talking about a Tilt, you are in the wrong forum. This is Tilt 2 (Touch Pro 2/Rhodium).
Click to expand...
Click to collapse
Wow...i mean tilt 2 ... XD

Dragonmaster0430 said:
Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz
Click to expand...
Click to collapse
i had this pb a few time ago, and as I remember, I solved it just by changing the folder where RRU AND NBH files where. try installing from an other folder...don't know why it works for me

Diamond dead?

Hello everyone, it's me again...
Please read this first, as it is the reason why I started MTTY. http://forum.xda-developers.com/showthread.php?p=10487426#post10487426
I used this guide to MTTY http://forum.xda-developers.com/showthread.php?t=540290
I did exactly as described in the guide, exept for the "Remove Watermark" thing, as it is for windows x65 and x84. I have a 32 bit system.
I used the Energy.DIAMOND.28244.Sense2.5.Cookie.2.0.Dec.21.7z ROM
I used the "flash from internal storage" method. Again, I did exactly as the guide described. I did change the ROM name to what is described in the guide, and when i did that, my pc warned me if i changed that which was after the .xxx , the program couldnt work properly anymore. I continued anyway because I was pretty sure it would work. I changed the name to DIAMIMG.nbh
Maybe that's what's wrong?
I used the MTTY program, and selected USB.
I typed: set 14 0
I typed: task 29
In the guide, only one file failed to be erased. I had four un-erased blocks.
I typed: task 8
I immediatley disconnected my device and held vol down and back for over 2 minutes. The startup screen came, which displayed TouchDiamond as normal, but this screen stays there forever, no matter what I do.
The only thing I can do is enter bootloader. Then, when i hook my device up to my computer, "serial" changes to "usb". When i check control panel--> device manager, I can see my device is hooked up. When i disconnect, it isn't there anymore. That means my pc still recognizes my htc.
Is there any way to fix this? Was it a wrong ROM version? Was it a Wrong HardSPL version? Please help me.
I've made a backup before I even started with the Hard SPL, but i'm not sure if thats the ROM, or the settings and some files on my internal storage. It's about 30-60 MB.
Please help me.
Also, I have downloaded the original rom from htc, but i'm not sure how to flash this, as activesync doesn't recognize my HTC device.
Again, please help me. There has to be a way.
Thanks in advance

connect ur diamond to pc and flash from PC

btw u can still get ur original rom from htc netherland site....use ur serial number in ur device

I downloaded the rom from the htc site. i just flashed it and it works.
Now how to flash the energy rom? im still not sure which method to use, because it's now working like the htc one. it's a .z7 file. The htc rom was just double clicking and following the instructions. It may sound stupid, but i dont want it to happen again
Happy it's working again tho.

glad ur device is working again. and dont worry if it happens again. becoz you can bring it back with htc rom always.
if i may suggest, how about you try a non-energy rom jus to kick in the confidence in you.
try another custom rom....then you can be sure if its really ur device or the energy rom file that is corrupt.
some users hav had issues with their energy rom files downladed being corrupt

Arthedes said:
I downloaded the rom from the htc site. i just flashed it and it works.
Now how to flash the energy rom? im still not sure which method to use, because it's now working like the htc one. it's a .z7 file. The htc rom was just double clicking and following the instructions. It may sound stupid, but i dont want it to happen again
Happy it's working again tho.
Click to expand...
Click to collapse
Hi there...
File with z7, it's compressed file. You need to extract it first to a new folder. Then you can try to flash again.

Hello again.
I did notice when i first downloaded the energy rom that it was a 7z file. But when i tried to unzip it, there was no such option in the drop down menu. This is my mums pc, so I think it's not installed on this pc.
I'll try to unzip it today after school.
If it doesn't work then, I'll try to flash a few other roms, just to be sure.
I'll keep you updated. Thanks for the fast replies tho^^

It's working! I just used 7Zip and ran the RUU included with the ROM. Ill try several as maxsence 2.5 is a bit sluggish, ive tried two, but the 23699 build doesn't have cookie 2.0
Really happy and thanks for the replies, guys(or gals)

see...i told you so...this is called the "CROSS CHECKING"....
now do you (or everyone else) believe me when i say there are some energy rom files that are corrupt or refuse to flash to diamond.

no, it was not corrupt, I was just so stupid not to unzip it first, that's all.
There may be some files that are corrupt, but i haven't witnessed one.
Now i know how to, i'm one die-hard flashin' mother******
TY^^

Arthedes said:
no, it was not corrupt, I was just so stupid not to unzip it first, that's all.
There may be some files that are corrupt, but i haven't witnessed one.
Now i know how to, i'm one die-hard flashin' mother******
TY^^
Click to expand...
Click to collapse
thank God if you're aware of your shortcomings...
I'm proud of people who really gentleman