Develop Bugs

"Un-brick" Imate JasJar After Failed ROM Update

First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick

Did like u said.
Still country id error

works now
thanks

my device t-mobile mda pro jasjar bootloader nope
rsteel1 said:
First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick
Click to expand...
Click to collapse
this method how?my jasjar can open normal ?

help me
error 101 problem

error 150 problem
MaUpgradeUt_noID trying in my jasjar error problem 150 .whats saying ? problm where? usb dont recognize xp .what must ı do?

please help me im using Vista and cant get connection with my imate to my pc... and what is a radio update if you can help me add my msn!
i dont want to update anymore i just want to get my wm5!

Have a look here:
http://wiki.xda-developers.com/index.php?pagename=FlashVista
Hope it helps,

Help A Newbie once A Day with An MDA

Hi All
Have a problem with my latest phone. A so called friend told me to upgarde the ROM so as to remove all the T Mobile poop in it. So he gave me the software I started the upgrade all went well stage 1 then stage 2 and finally stage 3. It said Congrats just hit reset and the power button at the same time and its done. Easy Me thought..... Not Easy....... Its now just booting up and screaming at me. The screen wont lite up and nothing else. I have tries to reset over 10 times now.....Anyone got any ideas, have I shot and killed my new phone...
Ta JG

this is not good. do you know which phone you are having? MDA is all the phoen from t-mobile. First identify your phone. Then, you need to know if you are using the right ROM on the right phone. THEN, you have to know are you using the right phone ROM on the phone (eg G3 or G4).

Its an MDA Copmact 11 does that help....

common.. more info. which rom you've used?

Alpine_Ext-1.11.162_Radio-1.04_stuffstripped_Camera_Fixed.
SORRY i AM NEW TO THIS AND i AINT GOT A CLUE WHAT i AM DOIN...HE HE HE

Oh forgot to mention it all went in ok, stage 1, 2, 3 and even told me on my computer it had worked. It was when I tried the power and reset that it all came tumbling down........

JeanGenie said:
Oh forgot to mention it all went in ok, stage 1, 2, 3 and even told me on my computer it had worked. It was when I tried the power and reset that it all came tumbling down........
Click to expand...
Click to collapse
All I would like to do is get the old stuff back then worry about an upgarde later can this be done without me having to do unspeakable things to the phone????

You've just flashed your Charmer phone with an Alpine ROM. If that doesn't kill your phone, I'm not sure what will.
Ok, try this. Hold down all 3 buttons -> power, camera, record buttons, and poke the reset. See if you can get a 3 colours screen.
If you get that, close active sync (stop the process WCESCOMM.EXE), connect your phone to your PC (when it is displaying the 3 colour screen). Then you ought to be able to run the ROM update file (EXE) from t-mobile (check the Charmer Wiki) and that may fix your problem.

hanmin said:
You've just flashed your Charmer phone with an Alpine ROM. If that doesn't kill your phone, I'm not sure what will.
Ok, try this. Hold down all 3 buttons -> power, camera, record buttons, and poke the reset. See if you can get a 3 colours screen.
If you get that, close active sync (stop the process WCESCOMM.EXE), connect your phone to your PC (when it is displaying the 3 colour screen). Then you ought to be able to run the ROM update file (EXE) from t-mobile (check the Charmer Wiki) and that may fix your problem.
Click to expand...
Click to collapse
I have done what you have said, I think...DUHHHH the screen has not lit up but its now showing USB in the top and V1.02 in th ebottem. I have connected it to my computer but active sync has not cut in yet....... I assume I have done it wrong....

hey
you DONT want activesync to cut in
put it in that 'usb mode' that you managed to get and just run the OFFICIAL T-Mobile rom update utility, but make sure to kill the wcesscomm process in windows' task manager.
good luck!

duke_stix said:
hey
you DONT want activesync to cut in
put it in that 'usb mode' that you managed to get and just run the OFFICIAL T-Mobile rom update utility, but make sure to kill the wcesscomm process in windows' task manager.
good luck!
Click to expand...
Click to collapse
I have just downloaded the t-mobile update as below
RUU_Compact ll_2060227_20602110_021921_T-MobileUK_Ship
I have switched off the file as you have said in the task manager. The update laods then says cannot find MDA Device connection error 274.
Could a system restart help?????
Sorry for all this, maybe stick to things I do know in the future, like washing my car.......

hey
get your phone back into that screen which had 'usb' written on it.
then do this:
download and install a program called 'winrar', you've probably heard of it and in all likelihood already have it!
once its installed, right click that t-mobile update you just download and select the 'extract to.../' option that will come up in the drop down menu, let it extract to the folder it does, open the folder in there will be a few files: you want the file which is called something along the lines of 'upgrateUT' or RUU Upgrade UT, it'll be an exe,
connect your phone up to the computer (with it in the USB mode and activesync disabled) and run that exe, it should go through as normal
good luck
(if you want any help just post back! best bet is for you to extract the files and report back with the name of the files in the folder!)

duke: I think he did that. He downloaded the EXE from http://www.tm-phonedownloads.com/download_manager_mda_com2.html
and it seems not able to detect his Charmer.
JeanGenie: Just to make sure, when you run that EXE, you have the phone connected with it displaying USB?

duke_stix said:
hey
get your phone back into that screen which had 'usb' written on it.
then do this:
download and install a program called 'winrar', you've probably heard of it and in all likelihood already have it!
once its installed, right click that t-mobile update you just download and select the 'extract to.../' option that will come up in the drop down menu, let it extract to the folder it does, open the folder in there will be a few files: you want the file which is called something along the lines of 'upgrateUT' or RUU Upgrade UT, it'll be an exe,
connect your phone up to the computer (with it in the USB mode and activesync disabled) and run that exe, it should go through as normal
good luck
(if you want any help just post back! best bet is for you to extract the files and report back with the name of the files in the folder!)
Click to expand...
Click to collapse
okie dokie...have extracted all th efiles and these are what I have got in a seperate folder
EnterBootloader
nk.nbf
README
ROMUpdateUtility
RUUGetInfo
RUUResource.dll
Thats all the files inside the folder

is "ROMUpdateUtility" an EXE file? try running that.

hanmin said:
is "ROMUpdateUtility" an EXE file? try running that.
Click to expand...
Click to collapse
I have and after a few seconds it says error 274 cannot find device....!!!!

well, it is amazing that you can go into the bootloader at all. I'm suspecting that the bootloader is not the Chamer bootloader, hence the ROM update EXE is not able to find it. Where did you download the Alpine ROM. Give exact link.
UPDATE: Look at the post here
http://forum.xda-developers.com/showthread.php?t=269329&highlight=
by 'windowsceportal'. He is able to flash the phone with 'Prophet RUU 2.5.2 noID check' with the DLL RUUResource.dll of Charmer RUU. I'm not very certain, but the noIdCheck may able to help.
UPDATE: As according to this post
http://forum.xda-developers.com/showthread.php?t=280128&highlight=
the bootloader mode that you are having is that of an Alpine (Charmer's bootloader mode is a screen with 3 colours). So, probably the updating program doesn't work. However, as an idea, you may want to try getting alpine upgrading EXE files to load Charmer ROM into the phone. It is an idea, not sure how can this be achieved.

hanmin said:
well, it is amazing that you can go into the bootloader at all. I'm suspecting that the bootloader is not the Chamer bootloader, hence the ROM update EXE is not able to find it. Where did you download the Alpine ROM. Give exact link.
UPDATE: Look at the post here
http://forum.xda-developers.com/showthread.php?t=269329&highlight=
by 'windowsceportal'. He is able to flash the phone with 'Prophet RUU 2.5.2 noID check' with the DLL RUUResource.dll of Charmer RUU. I'm not very certain, but the noIdCheck may able to help.
UPDATE: As according to this post
http://forum.xda-developers.com/showthread.php?t=280128&highlight=
the bootloader mode that you are having is that of an Alpine (Charmer's bootloader mode is a screen with 3 colours). So, probably the updating program doesn't work. However, as an idea, you may want to try getting alpine upgrading EXE files to load Charmer ROM into the phone. It is an idea, not sure how can this be achieved.
Click to expand...
Click to collapse
This is the link i used to get the original upgrade
ftp://xda:[email protected]_Radio-1.04_O2stuffstripped_Camera_Fixed.rar
Does that help any...

JeanGenie said:
This is the link i used to get the original upgrade
ftp://xda:[email protected]_Radio-1.04_O2stuffstripped_Camera_Fixed.rar
Does that help any...
Click to expand...
Click to collapse
Is there anyway of just deleting the Alpine ROM and reinstalling the correct charmer. I, as you have probably guessed aint got a clue what I am doing never lone saying...he he he
Just a thought.......
Plus my new XDA IIi was delieverd today am I being silly when I say I have been told that I can debrand it with the Alpine rom as listed above, dont want to try anything incase this phone goes belly up also....

Hellllppppp...........
Its me again, can anyone make any other suggestions to my problem please. I have tried in vain to do what has been already suggested but it seems either it wont work or more to the point I have no clue as to what I am doing.

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..

Money ahead: Need serious help with my hx2000 / hx2490

Hi there!
I am in serious need of help with my iPAQ hx2490. Yesterday, I tried to do the
official HP ROM Update. Everything went well, up to about a point when the RUU told me that there is a connection problem with my device.
The update went to just about half way through, and I didn't touch anything, I just left the device in it's cradle.
Anyway, my problem now is, that the device won't start the OS, I can't get past the HP welcome screen. The loading bar fires up, and completes it's way to the right, but after that: NOTHING!
I have tried soft, hard and clean reset, without any help. When I do a clean reset, the display shows "Formattin PS", and the loading bar reaches the right. But after that: NOTHING again!
I tried flashing everything again, from WM 2005 first and second edition, even WM 2003. The result is always the same.
I can get it into Pre-Bootloader, normal E-Bootloader. I do get a "USB Connected" message, and I do get the following "USB" message on the screen.
Now here's the odd thing (and I do hope that all you experts are dying to solve this mystery!): when I do the update again, at either 84,1% or sometimes 85,1%, the iPAQ shuts down, and starts again. But this doesn't stop the RUU from continuing!!
I've tried everything I can, I read all the infos in the forums concerning iPAQ problems, but they're mostly concerning entering bootloader, which is NOT my problem.
Money ahead: I'll donate 10€ to the person who is able to solve this riddle!!
The money can go to either this website or the person's own PayPal account.

oh I forgot: I did try ChrisMRulz bootloader method, but I wouldn't work for me. I managed as far as the MTTY program firing up, and I do get a WCEUSB prompt, but can't enter any commands, and the nbf file doesn't get uploaded!

PROBLEM SOLVED!! Sorry.....

Can you tell us how?
Maybe it will be helpful for others that have similar problems in future.

Sure, I can do that:
I managed to flash the official International English ROM Update to my german hx2490 iPAQ. I just used the trick that you have to start the correct HPRUU.exe for your country-specific device, but just before you hit the last "Update" button, you change the .nbf file with the one you want to flash.
But you have to rename it to according filename the HPRUU.exe originally loaded,
if you don't rename it, the update utility will crash.
By doing so, I was able to flash the above mentioned ROM to my device, and after that I just flashed my country-specific ROM.
Now I'm back and running WM5.
If further explanation is needed, I'll gladly help out someone with the same problem.

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