Guys
I just got my TyTN (unlocked, stock TyTN, HERM200, HT636 series) yesterday. Device info as follows:
ROM version: 1.18.255.3
ROM date: 07/22/06
Radio version: 1.03.03.10
Protocol version: 32.34.7010.01H
ExtROM version: 1.18.255.106
I am on Cingular and in the Washington DC area.
I was trying to flash the Radio only to 1.16 because I am having issues connecting to the Cingular UMTS network, as per the wiki site (http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms). Here's what happened:
a. I ran the upgrade file.
b. The device got into the bootloader mode (tricolor screen) successfully
c. Then the upgrade utility gave me the following error:
ERROR 120: COUNTRY ID ERROR
The ROM image that you are trying to use is not designed to work with your device. Please check the vendor website and download the correct ROM update.
Click Exit to quit
(attached screenshot)
d. I clicked Exit. The device remained in the Bootloader mode (tricolor).
e. I then removed the battery and restarted it.
Thankfully, the device started working properly after starting up.
Any thoughts regarding what's going on? Why was I not able to update my Radio?
I will really appreciate any help in this regards.
JoKer
tried to run the upgrade twice when you get the error? without disconnecting the device from usb...
No pof ... I haven't .. I disconnected it before restarting it. What exactly should I do this time?
gravejoker said:
a. I ran the upgrade file.
b. The device got into the bootloader mode (tricolor screen) successfully
c. Then the upgrade utility gave me the following error: ERROR 120: COUNTRY ID ERROR
d. I clicked Exit. The device remained in the Bootloader mode (tricolor).
e. I then removed the battery and restarted it.
Click to expand...
Click to collapse
Everything ok until "d", don't do "e". Go to "a" again.
I followed all of above steps with my stock TyTN. Fired up the upgrade again after the country ID error, I get the white screen indicating a radio upgrade is being performed. After a while I get the 114 error, I reset the TyTN but the radio is still 1.03. Anything else I need to consider?
check your bootloader version. Radio upgrades can only be done with bootloader 1.04, if you have bootloader 1.06 you don't have the 'rtask' command needed to go to radio bootloader.
pof said:
check your bootloader version. Radio upgrades can only be done with bootloader 1.04, if you have bootloader 1.06 you don't have the 'rtask' command needed to go to radio bootloader.
Click to expand...
Click to collapse
Ok, I have 1.06 bootloader. I was interested in a newer radio ROM to figure out whether my old ROM prevents me from having a simultaneous voice/data connection...
Any suggestions what to do next?
Flash a ROM matching your CID with bootloader 1.04.
Read this wiki page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Howto_Bootloader104
Related
Dear All,
I've tried to upgrade to ROM Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship
and unluckly cable loosen and I reset the phone.
Since it's in the middle and can't success enter the Windows Mobile,
but the bootloader was updated to 1.06.
Now I can't flash any ROM either
HER_DopodAsia_1237074_1060010_WWE_SHIP or the new one.
The tools on "imei check" even can't recognize my phone.
Any one can help me on this issue, please?
Thanks in advance.
Try the steps here, let us know the results:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you don't fix it with the proposed solutions attach USB Monitor capture in text format as explained in the bootom of the page.
I have the same issue, and sent it to service, and now I have the phone back and they could not fix it, so got no radio or imei number, so none of the FAQ will work for me.
So I have an expensive paper weight.
Hi,
ME TOO!!
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
I have also tried imei without any joy.
the PDA part of my M3100 still works but the phone is dead. I have been told that if you can get the latest radio installed then you satnd a chance of the phone part working.
We need a hack to get bootloader 1.4 back on the phones.
Please help.
Thanks
My one now is a photo frame which one show "HTC" or "Windows Mobile",
at least your one is a PDA.
There are nothing in "info 2" and so nothing can be flash into it.
Is it possible to have something written CID and IMEI to phone in mtty
and let the flash rom success?
i am in the same situation like yhlee. Pof, i have reply your pm and ready to upload the result file to FTP. where should i upload to?
Thanks
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Thanks.
rnc1688 said:
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
Click to expand...
Click to collapse
This can be fixed by bootloader commands 'set 14 0' and 'task 8', will reboot your device and boot into OS again (but no GSM yet!)
yhlee said:
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Click to expand...
Click to collapse
Upload it to xda-developers ftp:
ftp://xdaupload:[email protected]/Uploads/Hermes/
USER: xdaupload
PASS: xda
POF, file have been uploaded, file name= rnc1688
Thanks
'set 14 0' and 'task 8' didn't work
@rnc1688: It starts the flashing process, but you get a "CID not allow (255)" error because your CID is corrupted and you are in bootloader 1.06.
Is not booting WM5 after "set 14 0" in mtty.exe? If it's not booting WM5 you'll not be able to flash bootloader 1.04 and bypass CID checking.
so i guess my unit is bricked now.
I've upload the file which named yhlee.txt.
However, I'm going to send the unit for service.
Hope they can fix.
Any way to make it show the bootloader screen on start-up
everytime?
"set 14 1" doesn't work after push the RESET button.
Thanks.
@yhlee: U're getting exactly the same error as rnc1688. Device in bootloader 1.06 which has corrupted CID, however you say you can go into OS, so it would be possible for you to downgrade the bootloader so it does not enforce CID checking.
yhlee said:
Any way to make it show the bootloader screen on start-up everytime? "set 14 1" doesn't work after push the RESET button.
Click to expand...
Click to collapse
Try "set 1e 1" and then "set 14 1", you'll boot stright into bootloader.
@rnc1688: If you want to go WM5 try this:
"set 1e 1" and then "set 14 0", you should be able to boot stright into OS.
no luck either
grrr!!!... command "set 14 [0|1]" is working fine in 1.04 here to switch boot into WM5 or boot in bootloader mode... probably different in 1.06??? I don't have a 1.06 now to test
Mine one is just showing "Windows Mobile" but stuck there,
but seems rnc1688 one is a PDA but my one is nothing.
I've sent to distributor for service.
Thanks you pof.
yhlee said:
I've sent to distributor for service.
Click to expand...
Click to collapse
Let me know when they fix it... i'm curious about if they will fix it with 1.06 or they will downgrade to 1.04 first.
I got a correct message back from the service company, and they will not fix a bootloader 1.06 unless the original rom has been release with it, I was told that is HTC policy on this.
Alright, so im trying to superCID my Dopod 838 Pro. I've read the wiki and all the threads that i can find, and everything seems to go according to plan. Except i cannot verify SuperCID status.
I downloaded pofs http://pof.eslack.org/hermes-unlocker/
I flashed the radio, and received the "Upgrade Error 114" as expected.
I then ran HERM_Unlock_v2a.exe on the device, and after a minute i get a "Your device was SUCCESSFULLY unlocked and changed to SuperCID." message.
From mtty (after booting the device into the bootloader) i get the following results from the suggested commands.
USB>task 32
Level = FF
USB>info 2
HTCSDOPOD001Û<wHTCEUSB>
From what i understand, my device is still CIDlocked.
I want to make sure that superCID is enabled before i go flashing the ROM.
I've gone back and reread the instructions and repeated this procedure three times now.
Any suggestions as to what i might be doing wrong?
In the bootloader i see the following:
HERM100
IPL-1.01
SPL-1.04
thanks/Richard.
What radio version do you have currently installed? When you run the downgrade to radio 1.16 (attached to the unlock v2a) and get a error 114 you have to rerun it till the red progress bar appears and the radio is flashed to 1.16. Only then can you run superCID.
I have radio version: 1.06.00.10 installed.
Other versions are:
ROM Version: 1.23.707.4
ROM date : 07/21/06
Protocol version: 32.37.7010.01H
I see. Is the red bar to appear on the computer or the device? I received error 114 every time.
edit: when updating i see "Upgrade. Radio Stack. Please wait..." on the device. This message doesnt go away, even after error 114 , until i soft reset the device.
I've rerun it now an additional 5 times. I get no red bar.
Also, it wouldn't be a downgrade of the radio, as im trying to go from 1.06 to 1.16, but im not sure thats relevant.
does nobody have any insight to share?
littlenarf said:
does nobody have any insight to share?
Click to expand...
Click to collapse
I see you tried the unlocker v2a, have you tried the new version 3...just a thought.
Using XP, I am trying to upgrade from radio 1.16.00.00 to radio 1.20.31.10. I have followed the instructions in the Hermes Upgrade Guide to the letter. I have tried sever times, but I continue to get ERROR 114. Each time the phone says "Upgrade Radio Stack Please Wait..." and the upgrading process never moves from 0% on the desktop (yes, I closed process wcescomm.exe before starting.) I have also tried doing another upgrade right after the error 114 message, without disconnecting the phone nor reseting, but I get ERROR 150.
Any ideas would be helpful.
Ron
Current Setup:
ROM: 1.34.502.1 Cingular
Radio: 1.16.00.00
BL: 1.04
Task 32: 0
History:
1) Phone came loaded with Cingular ROM 1.34
2) Downgraded to Cingular ROM 1.30 to get BL1.04
3) SuperCID unlock automatically with HTC_Hermes_SIM_CID_Unlock_v3 (GREAT PROGRAM!!!)
4) Used SSPL-HERM.exe to change ROM back to Cingular 1.34
5) UNSUCCESSFULLY tried to upgrade Radio Version to 1.20
Well, I was doing everything right... but my computer was refusing to cooperate with me. Because I did the exact same thing on my wifes computer and it worked!!!
Thanks
Ron
This is becoming a common issue and there are a lot of people with a bricked Hermes devices, usually because of a WinXP crash, bad USB port, USB hub or pulled USB cable while flashing.
This thread is in the aim of finding a solution to all these common problems: if you are the owner of a bricked hermes, please post your comments here instead of opening a new thread.
There seems to be 3 types of bricked (or dead) hermes devices:
Type 1 bricks: Corrupted radio area: No GSM, No CID, no IMEI
Usual reason for that is flashing whent wrong when RUU was flashing the radio stack (GSM.nb). Other reason can be that you flashed radio from another device (universal unlocker run on hermes, for example).
Within the type 1 bricks, there seem to be two variants:
Type 1a:devices which can boot windows mobile but can't use the phone functions.
Type 1b: devices which can't boot windows mobile and are stuck while booting, see also type 2 bricks below.
Type 2 bricks: Stuck in boot process
Usual reason for that is that flashing went wrong when the RUU was flashing any rom part different than IPL and SPL. Symptoms can vary depending on which is the ROM part affected. The most common is OS because it is the bigger part. Radio is the second most common.
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
Type 2b: When the phone boots, it stays in subslpash screen (htc or operator logo)
Type 2c: When the phone boots, it doesn't pass the windows mobile logo
Hybrid Bricks: combinations of both type 1 and type 2 bricks
These usually have a corrupted radio and are stuck in bootloader, unfortunately these are very common too, and the most dificult to repair.
We made a wiki page long time ago whith the solutions that have worked for some people to fix bricks, unfotunately these solutions do not work for everyone, some devices are more bricked than others
First thing you have to do is visit this wiki page and follow the process explained: Common upgrade problems
If you can't repair your brick after following the process, please provide a USB monitor capture in ANSI text format (this is explained on the wiki page too) as this is the only thing that can give us a real idea on what your exact problem is. Please don't come crying and say "help me" because we can't help you if you don't provide useful information, you are in front of a big problem and you will have to loose some hours reading and experimenting before repairing your brick. If you are not willing to loose some hours reading, go and send the device to the service centre for a repair as it is the only valid solution most of the times.
Hopefully after research of everyone in this thread we can find new solutions for some of the bricks
EDIT: Please use axiom's comment below as a template for your comment and attach USB monitor capture: If your bootloader is 1.04 attach capture when trying to flash an extracted radio ROM and when trying to flash a shipped rom update. If your bootloader is 1.06 or 1.09 only attach the usb monitor capture of the shipped update.
EDIT (2007-03-22):
After more than 3 months since this thread started and more than 660 comments, we have now solutions for some bricks, so I compiled the most common on this unbricking guide:
How to unbrick your bricked hermes
Please spend some time reading through the wiki and thread comments before posting desesperately, otherwise you'll get no answer.
The following info may help in isolating the problem and keeping the clutter down.:
I'm including my info.
Model: O2 XDA Trion
ROM Before Flash: Dopod 1.23.707.4
Radio Before Flash: 1.16
Bootloader Before Flash: 1.04
Flash failed at: 6%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
Hi, I've managed to brick my Hermes as well.. First time on any of my HTC Devices....
Model: Vodafone v1605
ROM Before Flash: Voda Launch ROM
Radio Before Flash: Not sure
Bootloader Before Flash: 1.04
Flash failed at: 8%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
You may already know this, as I posted it in all over the other threads of people with bricked hermes, but I'm posting again to make sure every piece of information is concentrated on this thread, and see if finally this can get us somewhere
HTC bootloader returns data encapsulated in a block between HTCS (start) and HTCE (end), before the HTCE there's always a 4-byte checksum of the data. You're getting a timeout when you query the bootloader for the device's CID, so the output you see is "F" which means failure (T means success) encapsulated in this HTCS/HTCE block, plus the checksum. The CID is read from the security area of the device, found on radio, but the wrong flash corrupted the radio area.
As the CID is not returned, the error you get when flashing the ROM is "CID Not allow (255)". The security level depends on CID, as the device has CID corrupted, the security level returned is FF (255), which means you can't bypass CID check in bootloader.
You both have bootloader 1.09 which does enforce CID checking (as opposite to bootloader 1.04 which has a known bug to circumvent this). This bootloader also only allows updates with bootloader version > 1.09 (and no such bootloader exists yet).
Bootloader 1.04 allows to flash unsigned code in radio with radio bootloader command 'rwdata', but radio bootloader is accessed through command 'rtask' and this command has been removed in following bootloader versions.
All the commands to flash code in bootloader 1.06 and above require the code to be signed (the commands are 'wdatah' and 'lnbs'), and bootloader checks the signature before the code is actually flashed on the device. So modifying a 1.04 bootloader to show itself as 1.10 is not possible because it will return a certificate error and will not be possible to flash.
Command 'lnbs' doesn't check CID, but it is only enabled if device has security level=0, and as your radio is corrupted and your seclevel=FF it will not be possible to use this command to fix it even if you had a signed bootloader, so 'wdatah' is the only command that would allow you flashing code, but 'wdatah' requires a NBH header to be sent, which contains the CID of the update and is checked against the missing CID on your device and will never match (even if you could modify the NBH header and have a valid signature after).
In conclusion, my recommendation to you is that you send the device to service centre to get it repaired and don't try to fix this by yourselves, as you will go nowhere.
Many thanks for explaining it so succinctly Pof, much appreciated. With this error I've learnt a heck of a lot more about the ROM flashing process... I guess it may be time to send the unit for repair!
This is the full report after I soft rest my phone while the USB is still connected. Would any one know what the rest of the data means? I did it in the morning then just left it for the day to see what would happen, I just got back from work.
onj: can you use axiom comment as a template to provide information?
radioerror.txt: I see you're using the Himalaya upgrade utility there... rbmc reads data from memory, but I don't know what is at 0x70010000. It would be better if you can provide a log of hermes RUU.
Model: x01ht
ROM Before Flash: i-mate
Radio Before Flash: 1.07.03.10
Bootloader Before Flash: 1.04
Flash failed at: 0%
Flashing ROM: JASJAR_WWE_19096_19505_11300_AKU_3_2_ship
Flashing Radio: 1.13.00
Bootloader After Failure: 1.04
CID Before Failure Super CID: success
CID Corrupt: don't know
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: stalls
Current Device Status: unusable
I will upload the usbmonitor with using
RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP
the upgrading dies after info 3
computer says ERROR [222] Device not responding
that's with all the RUU's that I use and even the full upgrade ROM
Hi, I have a herm 200 an i have a Type 2a bricks (it goes directly to bootloader mode tri-color screen).
But i upgrade with the rom (ME_DT_WWE_1182553_106_10303_Ship) and all run good. but 3 moths later i have the type 2a bricks.
I try with that solution (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems) and others and NOthing.
In screnn say herm200 ILP-1.00 and Her200 SPL-1.04.
ps: sorry my english is very bad.
@onj: Oh ****! You where trying to flash an HTC Universal ROM in your HTC Hermes!! These are different devices, most probably that's what screwed it.
From your attached file I see bootloader does not answer to any command.
@landtd5: please use axiom comment as a template, and attach USB monitor capture when tryng to flash a shipped rom and a radio rom.
Yup, I upgraded with the wrong Rom. After going through the forum for the past 2 weeks I realized what I did. I guess it's time for me to send it to the shop
thanks for you help pof
jash431 Dead Tytn
I had tytn with this rom
"TYTN_me_dt_wwe_1182553_106_10303_ship" which has bootloader 1.04
And I upgraded with
"RUU_HERMES_HTC_WWE_1.35.255.2_1.35.255.102_1.08.00.10_SHIP"
during upgrade stopped and after that I cannot do anything with it
It never answer to any solutions .
Please help me .
USB monitore is attached here .
jash431 said:
USB monitore is attached here .
Click to expand...
Click to collapse
This is not useful: You saved LGS file, please follow instructions in wiki, you need to EXPORT as ANSI TEXT file. Also please use the 1st comment as a template to provide useful information.
Jash431
I exported in ansi text
@jash431: doesn't return anything... when you connect to bootloader on mtty, do you see the USB prompt? does it answer any commands?
Jash431
I'm sorry . this is complete one .
yes I can work with mtty.exe and my info 2 is "HTCSF kEØ(HTCEUSB>"
jash431: hybrid brick with corrupted radio and bootloader 1.09. Send it to repair centre.
jash431
is it theorically possible to fix my tytn . I mean maybe in future someone make a downgrade or SuperCID rom !! .
Because in my country doesn't exist repair center (Iran) . So what can I do ???
then keep it until something is found to fix this, creative solutions to the problem will come to your mind after looking everyday at a $500 brick.
Jash431
Thanks pof for your answer . I'll check my private message every day , for your solution and I remember you whenever I see a 500$ . ( Of course 500$ doesn't exist but you do ).
Hi,
i must sent my hermes to repairs. so i have to restore it to wm5 and old bootloader.
i have some problems with the gsm module. sometimes i get "no gsm" in the bootscreen and after boot no phone functions. Some time i the radio shows up in boot and i get phone functions. the problem did not appear after a flash. the last flash a month ago.
it seems that the hardware that there is a loose connection. when i make a test call and knock the phone (softly) the phone connection is lost. the "end call" button does nothing and after a while the whole os freezes.
has someone another idea than faulty hardware?
OS is restored to original with the help of mrvranx guide.
whats left is the bootloader and the shipped radio rom.
Bootloader screen shows:
Herm 300
IPL-1.04
SPL-2.10Olipro
Radio Rom is 1.47.30.10
Im a little concerned about mrvranx warning: "If your radio version is currently HIGHER than 1.27.00.00 then it is very likely the radio bootloader is version 0108, this WILL NOT allow the radio to be downgraded to a radio containing BL 0106 and will result in a "NO GSM" error"
but on the next page is a guide to flash the bootloader back step by step to the original. is this method save? and does anybody know which one was the shipped one (t-mobile germany).
last the radio. i can't remember which was the shipped version.
and can i flash whithout problems back to the original? somewhere i read about problems because of the bootloader.
and the last question
in what order must i do this. first radio then the bootloader is right?
many thanks in advance.
washi
just today I had to get my old TYTN ready for warranty/repair.
I followed mrvranx's guide to downgrade my bootloader and it worked flawlessly. I did it all from an XP computer as I was having issue on my Vista machine. Follow it to a T and you should not encounter trouble.
As for the order, I don't think it matters. I did my radio last if you just wanna follow my lead.
As for determining the radio and boot loader version - I'm with Rogers in Canada, they send me my replacement device before I send them the faulty one. I just go into bootloader mode (power on the right side+ok on the left side+reset button at the bottom) and verify the version.
just checked my radio bootloader version. its 108.
so i wont be able to flash a radio < 1.3x?
which is unfortunate because the t-mobile germany never actually offered an official update :/
i just hope the handy will pass with the old os and old bootloader but newer radio.
Is this really needed?
I have to send my phone in as well and didn't know if it was really necessary to do all the downgrading and stuff? i guess can't hurt to be safe though huh
Hey Guys,
I am in the same boat as you all, I am with Rogers and unfortunately MRVANX guide is not online at present, can any one help. Also if you can tell me if it is at all possible, my IPL is 1.04, SPL is 2.10.OLIPRO and Radio version is 1.54.07.00 I am using FARIA.32 ROM
please help.
Thanks
Himanshu