Help... my Trinity stuck during ROM updating

[signal-x]

Hi,

During one of the ROM update, the proccess has stopped at 20% for a long time so I had to stop it and restart the update.
The next time I run the update, it stuck at 1%, the device restart itself and I got "ERROR [294] : INVALID VENDER ID".

I tried to update to the dopod ROM again but I got the same error.
Now my Trinity is dead and I realy need help.

My device is HTC 3600, CID unlocked.
I aslo noticed that the bootloader has been updated from SPL 1.06 to SPL-1.07.

Thanks

VIC

[_onoff]

did you still have the files you used to CID unlock it?

[signal-x]

Yes I still have it

[_onoff]

you have a new PM see it please

[signal-x]

I also tried to use the CID unlock program again and now I get "Device identify Error"

I think the problem is that the bootloader is 1.07 and if I will find a way to install an earlier version, my trinity will live again.

[wishmaster82]

I also tried to use the CID unlock program again and now I get "Device identify Error"

I think the problem is that the bootloader is 1.07 and if I will find a way to install an earlier version, my trinity will live again.

where did you get the "original ROM" ???

[signal-x]

From the xda's ftp

[signal-x]

I asked IMEI-CHECK Team about the problem and here is what they wrote:

"It sounds like your ROM update went wrong / stopped / you cancelled it. In this case the device lost the radio rom (shows NO GSM at startup) and can not be used or updated anymore.

This is a common problem with all HTC Hermes and Trinity devices. If a ROM update is stopped/canceled in the "middle" then the device gets unusable. Unfortunately you have to send the device in for fixing (either to HTC service center or to us). The device needs to get opened and flashed via (expensive) JTAG tool. We offer to our customers to fix the devices for free but customer has to pay for full shipping costs."

Does anyone have other solution without sending the device over the sea??

[neofix]

I asked IMEI-CHECK Team about the problem and here is what they wrote:

"It sounds like your ROM update went wrong / stopped / you cancelled it. In this case the device lost the radio rom (shows NO GSM at startup) and can not be used or updated anymore.

This is a common problem with all HTC Hermes and Trinity devices. If a ROM update is stopped/canceled in the "middle" then the device gets unusable. Unfortunately you have to send the device in for fixing (either to HTC service center or to us). The device needs to get opened and flashed via (expensive) JTAG tool. We offer to our customers to fix the devices for free but customer has to pay for full shipping costs."

Does anyone have other solution without sending the device over the sea??

Nice to see that the people at IMEI-CHECK offers this service for free... This will actually make me reconsider paying for getting my P3600 unlocked...

Paying for good service is always nice :)

[tobyanscombe]

Nice to see that the people at IMEI-CHECK offers this service for free... This will actually make me reconsider paying for getting my P3600 unlocked...

Paying for good service is always nice :)


I'll second that!

My unlock did not go smoothly and I have now helped them further develop the code. Unfortunately it bricked my P3600 in the process but as mentioned, they have offered to fix it FOC.

If anyone is having doubts over their service then based on my experience dont worry....

[Dubi]

Hi,
I updated my HTC 3600 to the new dopod 1.23 test ROM.
It all worked great but because it's a test ROM, I decided to go back to the original 1.15 ROM.

During the ROM update, the proccess has stopped at 20% for a long time so I had to stop it and restart the update.
The next time I run the update, it stuck at 1%, the device restart itself and I got "ERROR [294] : INVALID VENDER ID".

I tried to update to the dopod ROM again but I got the same error.
Now my Trinity is dead and I realy need help.

My device is HTC 3600, CID unlocked.
I aslo noticed that the bootloader has been updated from SPL 1.06 to SPL-1.07.

Thanks

VIC
Can you try to run the monitor commands through the TTY... i.e. info commands and see what CID it reports? that can help to determine which RUU you need to flash with. Dubi

[signal-x]

Can you try to run the monitor commands through the TTY... i.e. info commands and see what CID it reports? that can help to determine which RUU you need to flash with. Dubi

Can you be more specipic what exactly should I do?

[hdubli]

I asked IMEI-CHECK Team about the problem and here is what they wrote:

"It sounds like your ROM update went wrong / stopped / you cancelled it. In this case the device lost the radio rom (shows NO GSM at startup) and can not be used or updated anymore.

This is a common problem with all HTC Hermes and Trinity devices. If a ROM update is stopped/canceled in the "middle" then the device gets unusable. Unfortunately you have to send the device in for fixing (either to HTC service center or to us). The device needs to get opened and flashed via (expensive) JTAG tool. We offer to our customers to fix the devices for free but customer has to pay for full shipping costs."

Does anyone have other solution without sending the device over the sea??


I don't think so..
2-3 times upgrading(Hermes) was stopped due to power cut/fluctuations.But in all the cases I managed to do the full upgrade, by simply putting them back to bootloader mode.

I suggest the same to you.See if u can get to bootloader.If yes then you shd try flashing the matching ROM to yr device..I think it shd b alive..

[signal-x]

Yes, I can see the bootloader and also the update proccess has started.
Nyt as I wrote, it failed after 1% and the trinity restart itself to bootloader screen.

[_onoff]

did you try it on the 2 Roms? HTC and the Dopod ? and you tryed the CID tool in bootloader too ?

[signal-x]

I tried to install all the available ROMs, all stoped after 1%.
I tried to install oly Radio ROM and it also stoped.

I'd like to know if there is a way to downgrade the bootloader from 1.07.
Maybe with other bootloader I'll be able reinstall one of the ROMs.

[signal-x]

No way to downgrade from BOOTLOADER 1.07?

[Dubi]

Can you be more specipic what exactly should I do?

Put the device in Bootloader, run mtty program - you can find it on this ftp, you should be able to get the prompt USB, then run info info 1 info 2 command that will report to you also the device id and cid... according to the information it is easier to debug and understand the reason for refusing to upgrade. right now your device behaves like you are not using the correct cid RRU... if you want you can call me on my mobile :054 7111799 perhaps I can try to help you more.. or you can bring the device and I can try to help you. Dubi

[signal-x]

Well first thank you Dubi....
Now, using "task 32" command in mtty tool, returns "Level = FF" which mean the device is CID locked.

Before the problem, I purchased the CID unlock code and it opened my device.
When running again the CID unlock tool, I get "Device Identify Error"

VIC

[Dubi]

Well first thank you Dubi....
Now, using "task 32" command in mtty tool, returns "Level = FF" which mean the device is CID locked.

Before the problem, I purchased the CID unlock code and it opened my device.
When running again the CID unlock tool, I get "Device Identify Error"

VIC

Vic after get into the USB prompt, try to type "info 2",
Here is the info command details:
---------------------------------------------------------
info
Usage:

info [Type [Value]]

Type(hex) 2: Get info for RUU software autentify for the PPC(16 bytes) and [value] (hex) is ignore.
Returns "HTCS" + CID + (4-byte checksum) + "HTCE"
Type(hex) 3: Get binary information for RUU sofware (2,10Kbytes)and [value](hex) is ignore.
Returns "HTCST "
Type(hex) 4: Returns
IsAllBytesTheSame-: dwLength=8, bResult=0
Returns HTCSHTC__102 Ã;¿HTCE
Type(hex) 6:
Returns HTCST ÚÈÒHTCE
Type(hex) 7: Returns information about the bootloader
Type(hex) 8: Returns information on blocks and partitionsExamples:

USB>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51b
Device Name: TRIN100, Bootloader Version : 1.06.0000
Built at: Oct 19 2006 20:31:29
Copyright (c) 1998-2006 High Tech Computer Corporation

CPU ID=0x41129200
Main CPLD version=0xA
Main Board version=0x5

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

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x18700
Partition[3], type=0x4, start=0x1B700, total=0x1F100

CE Total Length(with sector info) = 0x37BB800
CE CheckSum Length(without sector info) = 0x36E0000
-----------------------------------------------------------------

[signal-x]

Ok, but I cant understand how can this help...

[Dubi]

Ok, but I cant understand how can this help...

That will tell us what is your vendor so It is easier to try to debug anf find a solution..

[signal-x]

This is what I got:

Cmd>info 2
HTCSF kEØ(HTCE
Cmd>info 3
HTCST
Cmd>info 4
HTCS Lœ3ÆHTCE
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 7

HTC Integrated Re-Flash Utility, Common Base Version : 1.51d S025
Device Name: TRIN100, Bootloader Version : 1.07.0000
Built at: Nov 15 2006 11:33:20
Copyright (c) 1998-2006 High Tech Computer Corporation

CPU ID=0x41129200
Main CPLD version=0xA
Main Board version=0x5

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

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x18D00
Partition[3], type=0x4, start=0x1BD00, total=0x1EB00

CE Total Length(with sector info) = 0x387E800
CE CheckSum Length(without sector info) = 0x37A0000

Does it say something that can make us move on?

[pof]

This is what I got:

Cmd>info 2
HTCSF kEØ(HTCE


Your CID is corrupted, you won't be able to flash any ROM. Send the device to repair.

[_onoff]

i got this on mine when running info 2

Cmd>info 2
HTCSSuperCIDHTCE
Cmd>

[pof]

@onoff: Your's is CID unlocked, can install any ROM on any language.

[Dubi]

i got this on mine when running info 2

Cmd>info 2
HTCSSuperCIDHTCE
Cmd>

This looks ok but what happend before you wrote:
This is what I got:

Cmd>info 2
HTCSF kEØ(HTCE

which is correct?
Where do you live? Is it possible that I meet your device? (I am in Herzlia).

[Dubi]

i got this on mine when running info 2

Cmd>info 2
HTCSSuperCIDHTCE
Cmd>

After thinking a bit... it might be that either you got a very marginal USB port or perhaps a bad cable and this could be the explanation for incomplete flash (your original failure to upgrade the machine...) and also garbled data first time of running info2. Can you try to run the upgrade on another computer / deferent USB cable and make sure there is minimum activity while running the upgrade... alternatively you can call me and I can meet your device....

[Dubi]

Sorry got confused .. just ignor my last 2 messages....

[pof]

Dubi... they are 2 different persons: _onoff has a superCID device and signal-x has a bricked device which he will not be able to recover. Read this thread in the hermes forum: http://forum.xda-developers.com/showthread.php?t=286755

On Hermes at least we have 1.04 bootloader, which allows us to flash unsigned radio code and bypass CID checking, but on Trinity you can't do neither of that, so once the CID is corrupted, the device is trashed.

[Dubi]

Right.... I got it too late.... (after writing the message)... it is unfotunatly that Vic's CID got corrupted.. I suspected it is and this is why I suggested he runs info2 so we know what can be done...

[signal-x]

Thank you all guys, so I guess there is nothing to do but sending the device for repairing but I have a few questions.

1. "IMEI-CHECK Team" suggested me to send them the device and they will repair it for free. Can I trust them or should I send it to HTC?

2. Why did that happen? I install many ROMs in many devices in my life, is it the Trinity?

3. I still want to install ROMs in the future, is there something I can do to avoid this problem?

4. Does anyone know about more Trinitys that crashed like mine?

[Dubi]

I would assume that whoever sold the device did not realize that you mass the rom and they may claim that you are resoponsible for the failure and at the best charge you for the repair. While I read in other threads that the chaps of IMEI-CHECK offers this service for free (if I recall correctly you have to pay shipment..) In both cases do not forget to write your IEMI and SN number of the AWB, You may have and requested by the Israeli customs to show that it is the same unit and worse case pay VAT for the Shipment (I had to send my Jasjar a while ago and got anoid by them...).
Good Luck and sorry for the frastration - As for your other questions overall without go deeply into details it is the best PDA/Phone I had so far and I had almost all the the models, It is a great device.

[signal-x]

Thanks, I do love my Trinity and definitely its the best PDA ever.
Decided to send it to HTC, I hope I'll not get any problems.

[Dubi]

Thanks, I do love my Trinity and definitely its the best PDA ever.
Decided to send it to HTC, I hope I'll not get any problems.

Just be aware of it that HTC perhaps charges you extra ... flashing your device and mass with the CID is your resposibility..... in any event good luck.. and don't forget to "leave traces" of "exporting" your device for a repair such as SN.

[JolietJake]

Thanks, I do love my Trinity and definitely its the best PDA ever.
Decided to send it to HTC, I hope I'll not get any problems.

Hi Signal-X,

I'm very curious of your results, because I'm experiencing the same problems. So, did you send yor PDA in yet? And if so, what was the reaction of HTC?

Very curious.....

[signal-x]

I had to send it cause no solution was found.
I sent it to IMEI-Check,
They flashed my device and I should get it soon.

[thinh30]

My device : dopod d810

SuperCID
IPL-0.05
SLP-1.20. Olipro

I use mtty and then see the result

Cmd>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 0x98(152) 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=0x18600
Partition[3], type=0x4, start=0x1B600, total=0x1F200

CE Total Length(with sector info) = 0x379B000
CE CheckSum Length(without sector info) = 0x36C0000

pls explain what happen in : Block 0x98(152) is BAD block !!!

what should i do?

[pof]

what should i do?

type 'task 2a'

[thinh30]

type 'task 2a'

Thank pof

I type task 2a then

Cmd>task 2a
Check block : 152 - Bad

The device : uprom 2 times but stuck at splash , now i install with WM5 origin and are working. but still have : 152 -Bad

after that
Cmd>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 0x98(152) 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=0x18600
Partition[3], type=0x4, start=0x1B600, total=0x1F200

CE Total Length(with sector info) = 0x379B000


what next?

[stepw]

With OliPro's hard SPL you can fix the block marked bad.

[thinh30]

after use

task 2a
Cmd>task 2a
Check block : 152 - Bad

it can not fix the Bad block

"CURRENT FEATURES
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS.nb
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-bad NAND can again be checked for with "info 8"
-version displays 1.20.Olipro"

what Should i do?

1. reinstall Hard-SPL or
2. "flashing an OS.nb"

thank for your help, my d810 is running on original WM5.

[smos]

Originally Posted by signal-x
I asked IMEI-CHECK Team about the problem and here is what they wrote:

"It sounds like your ROM update went wrong / stopped / you cancelled it. In this case the device lost the radio rom (shows NO GSM at startup) and can not be used or updated anymore.

This is a common problem with all HTC Hermes and Trinity devices. If a ROM update is stopped/canceled in the "middle" then the device gets unusable. Unfortunately you have to send the device in for fixing (either to HTC service center or to us). The device needs to get opened and flashed via (expensive) JTAG tool. We offer to our customers to fix the devices for free but customer has to pay for full shipping costs."

Does anyone have other solution without sending the device over the sea??


I have the same problem , but my bootloader was 1.07. I use SIM&CID unlocker http://pof.eslack.org/trinity-unlocker/ from the bat-file , but process was incomplete and after reboot "no GSM" on my screen:(
So here is my idea:
I use http://forum.xda-developers.com/showthread.php?t=308691 this tool , then manual run the fixed 1.16 radio from SIM&CID unlocker and after reboot my trinity is ALIVE:D (but litle problem with sim from russian BeeLine).
Sorry for my english.

[dhborr]

hi
i have a problem with my trinity: after installing a new lasagna 3 rom.. it have a black windows and i can't do anything for changing it. i treid with a soft reset and some hard reset but they didn't work!!
please help me
thank's

[steve_62]

I been reading this thread with interest, as i've also had a bad flash with my trinity , it seem's the easiest soloution to send the phone off. How do i contact the Imea-team , and do Htc have service centre's in the uk ? . Regard's Steve