Upgrading ROM crashed...think it's fried...please help! - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

Firstly, let me thank everyone for their help in advance.
Tonight I tried upgrading my ROM to the newest Cingular ROM. I'm on Cingular in NYC and have been having radio problems so I hoped Cingular's optimizations would help. Anyway, I was running the i-mate ROM previously. I have done this many times. During the ROM upgrade, it gave me the usual Device ID error so I restarted the upgrade utility and evertything was good. Well, at 19% progress it stalled, eventually crapping out citing a communications error. The device won't reboot now.
I got the device in tri-color mode and began the process again. The upgrade stops with Device ID error, but now the restart trick no longer works! I also tried updating it with both the original TyTN ROM and the i-mate ROM I was previously using. They all crap out with a Device ID error! Now I have a paper weight because it also won't boot with what was loaded previously, hanging on the Windows Mobile splash screen.
Does anybody have any advice or solution???
Thanks...I'm desperate here!

---

See this page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Connect to your device bootloader using mtty.exe and issue the commands "set 14 0" and "task 8". This will (hopefully) boot the existing imate rom.
If this does not work run the commands "checkimage" and "info 8" and paste the output here. For more info read the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Alternatively, you can try to flash it using HERMIMG.nbh on SD card:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing

---

Thank you...I'm going to try this in just a few minutes. Needless to say...I'm sweating!

---

OK guys, this is what I got running "checkimage" and "info 8". What do you think?
USB>checkimage
IPL CRC checksum = 0x24C42773
SPL CRC checksum = 0x9382C208
CE CRC checksum = 0x5D6A925D
ExtROM CRC checksum = 0xFFF79D19
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3FB(1019) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19C00
Partition[3], type=0x4, start=0x1CC00, total=0x1DC00
CE Total Length(with sector info) = 0x3A66000
CE CheckSum Length(without sector info) = 0x3980000
USB>

---

Any clue on what this data means?
Thanks

---

CJNYC said:
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Click to expand...
Click to collapse
Your radio is screwed. Format your microSD card and copy the NBH file contained in a rom upgrade (if possible use one that matches your CID). Rename the NBH file to 'HERMIMG.nbh' and put the microSD card on the phone. Power on the phone in bootloader mode and you should see the flash confirmation, press the power button to confirm and wait 30 min. This process is described in more detail here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Good luck

---

Thanks POF...this will be the first thing I do tonight. I'm keeping my fingers crossed and will report back as soon as I'm done.
Thanks!

---

OK, that didn't work either. When the bootloader went to load the ROM from the Micro SD card I got the following message...
0028002
Not Allow
Any other suggestions??? Thanks

---

CJNYC said:
0028002
Not Allow
Click to expand...
Click to collapse
The NBH file you used doesn't match your CID. Use a NBH file that matches your CID.
You can see your CID by issuing bootloader command "info 2".
If you have an HTC branded Hermes (HTC TyTN) your CID will be QTEK_001, then you need an NBH file with this CID, for example "hermimg_QtekNOR_1.18.255.3_Ship.nbh" contained on HTC TyTN WWE rom.

---

pof...
That's the exact ROM I used and I do have an HTC branded TyTN. When I issue the "info 2" command all I get back is an "HTCSUSB>" prompt. Am I missing something?
Thanks

---

Probably mtty.exe doesn't parse the output of "info 2" correctly and that's why you can't see the CID, but if it is an HTC TyTN then your CID must be QTEK_001 and there should be no problems with the NBH you used... it is very weird that you get this error.
Did you try the "set 14 0" command to start OS after reset? If you can boot WM5 again you can run GetDeviceData.exe from your device to see your CID, otherwise you can use USB Monitor and look for the output of "info 2" there.
Another thing you can do is to start the TyTN 1.18 ROM upgrade using the normal procedure (RomUpgradeUt.exe), but capture the output of all the upgrade process using USB Monitor, and then export it to text file and attach it here. We will be able to see the error from bootloader and where exactly it stops the flashing process:
1) Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2) Put your device in BootLoader mode
3) Connect device to computer using USB cable.
4) Start USBMonitor.
5) File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6) In the upper part there are two tabs: basic and complete. Click on "Complete".
7) click on RomUpgradeUt.exe and start the Rom Update Process, if everything went fine you should see all the USB traffic output on USB monitor window.
8 ) when rom upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9) Save the file and zip it.
10) Upload the zipped file here or put it on xda-dev FTP if it is too big.

---

OK, I used USB Monitor and recorded the results of the upgrade attempt, which of course failed. Please see the attached file.
What do you think? Any hope?
Thanks...
-Craig

---

When the flash utility tries to get the CID from your device it gets this error:
CID: Wait interpreter timeout..
Click to expand...
Click to collapse
Info 2 should return:
Code:
"HTCS" + 8-byte CID + 4-byte checksum + "HTCE"
In your case the output of "info 2" shows this:
Code:
48 54 43 53 00 01 09 8C 5C 30 08 8C 66 17 09 7C HTCS...?\0.?f..|
48 54 43 45 HTCE
Your CID: 0x0001098C5C30088C (...?\0.?)
Output of "info 2" for HTC TyTN should show this:
Code:
48 54 43 53 51 54 45 4B 5F 30 30 31 D6 00 3D 07 HTCSQTEK_001.=.
48 54 43 45 HTCE
Normal CID for HTC TyTN: 0x5154454B5F303031 (QTEK_001)
I don't know what caused the CID to change, and it is not possible to change the CID on a NBH because signature will not be the same and you'll get a signature error. We don't know how to change the CID on the Hermes yet, probably someone will come out with a solution but now I don't know what to do....
Are you able to send back your device under warranty?

---

I'm going to try to ship it to the HTC repair center in Germany and see what they can do for me. Who knows how long this will take. I might pick up a Cingular 8525 when they are supposedly released on Friday and see how that goes. I'm not happy. I really like this device and simply wanted the Cingular network optimizations.
pof...I really appreciate the help and effort. In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones. Oh well, back to the drawing board.
Thanks again!

---

CJNYC said:
In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones.
Click to expand...
Click to collapse
Are you refering to user fun_key, not being able to downgrade after flashing cingular's 1.31 rom? He has checked and his CID remains the same, and I haven't heard of anyone having his phone locked for upgrading a ROM.

---

I've investigated into it, see my post here:
http://forum.xda-developers.com/viewtopic.php?t=63355&start=25
I guess your problem is that the rom upgrade flashed your bootloader and you cannot use the HERMIMG.nbh from the TyTN rom because it contains a lower bootloader version (1.04) while you have an higher bootloader version (1.06).
You can check your bootloader version by issuing the command "info 7".
Now you have tree options:
- wait for a rom upgrade with bootloader >= 1.06
- send your device to repair center
- wait until some xda-developer finds out how to downgrade the bootloader

---

I definitely understand this issue with the newer bootloader. Would it not stand to reason that I'd be able to re-run the Cingular ROM that failed or is this simply an issue now with the CID needing to match the original TyTN ROM?
Thanks again!

---

The TyTN has "flash from microSD" option much like the Wizard. On my 8125, IIRC, an SD based reflash ignored everything and put the base image + bootloader + ROMs back on; completely restoring the device to original factory specs.
I'm not sure if this is the same on the TyTN or not but it may be worth a try. The Wiki on this says that using the HERMIMG.NBH method to restore from SD may or may not ignore CID. At very least you could update the Wiki if it doesn't work

---

@CJNYC: I'm not really sure if your problem is related to bootloader version, CID or both.
@Sleuth255: He already tried sd-card flashing, if you follow the whole thread.

---

oops, now I see it. My bad...