HTC HERM200 Failed Flashing now has Bad Blocks

[darkoverlord]

Hey folks got a HTC HERM200 (TyTn) and the unit will not connect with activesync, so it will not do a rom upgrade, and I can connect in Bootloader using MTTY and if i do a info ? it tells me it has a lot of BAD BLOCKS, this is what it shows,

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 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!
Block 0x3AB(939) is BAD block !!!
Block 0x3AC(940) is BAD block !!!
Block 0x3AD(941) is BAD block !!!
Block 0x3AE(942) is BAD block !!!
Block 0x3AF(943) is BAD block !!!
Block 0x3B0(944) is BAD block !!!
Block 0x3B1(945) is BAD block !!!
Block 0x3B2(946) is BAD block !!!
Block 0x3B3(947) is BAD block !!!
Block 0x3B4(948) is BAD block !!!
Block 0x3B5(949) is BAD block !!!
Block 0x3B6(950) is BAD block !!!
Block 0x3B7(951) is BAD block !!!
Block 0x3B8(952) is BAD block !!!
Block 0x3B9(953) is BAD block !!!
Block 0x3BA(954) is BAD block !!!
Block 0x3BB(955) is BAD block !!!
Block 0x3BC(956) is BAD block !!!
Block 0x3BD(957) is BAD block !!!
Block 0x3BE(958) is BAD block !!!
Block 0x3BF(959) is BAD block !!!
Block 0x3C0(960) is BAD block !!!
Block 0x3C1(961) is BAD block !!!
Block 0x3C2(962) is BAD block !!!
Block 0x3C3(963) is BAD block !!!
Block 0x3C4(964) is BAD block !!!
Block 0x3C5(965) is BAD block !!!
Block 0x3C6(966) is BAD block !!!
Block 0x3C7(967) is BAD block !!!
Block 0x3C8(968) is BAD block !!!
Block 0x3C9(969) is BAD block !!!
Block 0x3CA(970) is BAD block !!!
Block 0x3CB(971) is BAD block !!!
Block 0x3CC(972) is BAD block !!!
Block 0x3CD(973) is BAD block !!!
Block 0x3CE(974) is BAD block !!!
Block 0x3CF(975) is BAD block !!!
Block 0x3D0(976) is BAD block !!!
Block 0x3D1(977) is BAD block !!!
Block 0x3D2(978) is BAD block !!!
Block 0x3D3(979) is BAD block !!!
Block 0x3D4(980) is BAD block !!!
Block 0x3D5(981) is BAD block !!!
Block 0x3D6(982) is BAD block !!!
Block 0x3D7(983) is BAD block !!!
Block 0x3D8(984) is BAD block !!!
Block 0x3D9(985) is BAD block !!!
Block 0x3DA(986) is BAD block !!!
Block 0x3DB(987) is BAD block !!!
Block 0x3DC(988) is BAD block !!!
Block 0x3DD(989) is BAD block !!!
Block 0x3DE(990) is BAD block !!!
Block 0x3DF(991) is BAD block !!!
Block 0x3E0(992) is BAD block !!!
Block 0x3E1(993) is BAD block !!!
Block 0x3E2(994) is BAD block !!!
Block 0x3E3(995) is BAD block !!!
Block 0x3E4(996) is BAD block !!!
Block 0x3E5(997) is BAD block !!!
Block 0x3E6(998) is BAD block !!!
Block 0x3E7(999) is BAD block !!!
Block 0x3E8(1000) is BAD block !!!
Block 0x3E9(1001) is BAD block !!!
Block 0x3EA(1002) is BAD block !!!
Block 0x3EB(1003) is BAD block !!!
Block 0x3EC(1004) is BAD block !!!
Block 0x3ED(1005) is BAD block !!!
Block 0x3EE(1006) is BAD block !!!
Block 0x3EF(1007) is BAD block !!!
Block 0x3F0(1008) is BAD block !!!
Block 0x3F1(1009) is BAD block !!!
Block 0x3F2(1010) is BAD block !!!
Block 0x3F3(1011) is BAD block !!!
Block 0x3F4(1012) is BAD block !!!
Block 0x3F5(1013) is BAD block !!!
Block 0x3F6(1014) is BAD block !!!
Block 0x3F7(1015) is BAD block !!!
Block 0x3F8(1016) is BAD block !!!
Block 0x3F9(1017) is BAD block !!!
Block 0x3FA(1018) is BAD block !!!
Block 0x3FB(1019) is BAD block !!!
Block 0x3FC(1020) is BAD block !!!
Block 0x3FD(1021) is BAD block !!!
Block 0x3FE(1022) is BAD block !!!
Block 0x3FF(1023) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19E00
Partition[3], type=0x4, start=0x1CE00, total=0x1DA00

CE Total Length(with sector info) = 0x3AA7000
CE CheckSum Length(without sector info) = 0x39C0000

Is there any way to fix this?

[battletank]

If it works in bootloader mode, you can attempt a reflash: you don't need an Activesync connection to flash the ROM. Just stick the phone in bootloader mode, switch off USB on your computers Activesync and run the installer. My advice would be to keep trying until it flashes successfully.

[darkoverlord]

Which Rom would you try, I have the following currently,

HERMIMG_CDL-WWE_1.20.305.4_Ship.nbh

HERMIMG_Dopod_1.23.707.4_SHIP.nbh

hermimg_QtekNOR_1.18.255.3_Ship.nbh

Currently on the unit in Bootloader it shows
HERM200
IPL-1.01

HERM200
SPL-1.04

Thanks again for trying to help, I really appreciate it.

[pof]

You can flash whichever you want, complete list of roms is on the wiki:

http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades

Let us know if a rom upgrade fixes the bad blocks. I've seen it on 3 or 4 devices already, so I think it is quite common although number of bad blocks seems to vary depending on the device.

[darkoverlord]

So far no Luck, but I will continue, as I am using HDD USB Monitor, and trying everything up my sleeves,

BTW this is what is on my screen if I just try to start the unit regularly.
http://premium1.uploadit.org/darkoverlord//low-tytn.jpg

[pof]

Very weird... haven't seen anything like that before :shock: :?

Can you do a rom upgrade sucessfully? if not, which error do u get from the RomUpgradeUt and what do you see in HHD USB Monitor?

[darkoverlord]

No Doubt, this one is gonna be a little tricky,

I can not get it to upgrade, it gives me the error 222, or error 260 every time.

HDD Monitor, well have a look at the log from it.

[pof]

Can you attach the log in text format? (export option in menu, then save as text without utf8).

Thanks.

[darkoverlord]

OK here it is

[pof]

mmm... shows almost nothing... is it a "full view" decode (second tab)?

Bootloader is still "safe" i gues... right? cos i can't see any bootloader output on the attached log.

[darkoverlord]

All right this is the full one

[pof]

mmm.... you don't seem to get any output from the device: :!:

- "task 32" command should return "Level = FF"
- "info 2" should return something like "HTCSQTEK_001.=.HTCE"
- "info 3" should return a big block of data encapsulated in HTCS / HTCE strings and starting with "H.E.R.M.2.0.0".

What happens if you put the device in bootloader mode and type those commands yourself using mtty?

Have you tryied running "set 14 0" and "task 8" and let de device boot?

Does this happened after a rom upgrade or where you doing something weird to the decvice? or it just happened without doing anything after normal phone usage?

[battletank]

A silly question, I know, but have you tried flashing the rom without the monitor, or even on a different PC?

[pof]

Try flashing directly from microSD as described here and let us know if it fixes your problem:

http://forum.xda-developers.com/viewtopic.php?t=62596

[darkoverlord]

Hey Pof, or anyone, can you creat just a new bootloader nbh for me, as I am so close right now.