XDADeveloperWiki - Hermes_Upgrade Problems

Common Upgrading Problems in HTC Hermes

This page explains how to recover your Hermes if something goes wrong with it.

Problem 1: solid white screen, phone doesn't boot

First try to hard reset: hold the Left and Right SOFT KEYs, and at the same time reset with stylus.
If all you get is same white screen, remove the battery for some time (about 20 min should be enough) and put it again.
If doesn't solve the problem try to remove the battery, microSD and SIM card, and turn on the device while it is plugged into the USB charger (without battery!).

Problem 2: stuck on windows mobile screen

Try to soft reset with stylus and wait 5 minutes on the windows mobile screen to see if OS boots
If all you get is same windows mobile screen, remove the battery for some time (about 20 min should be enough) and put it again.
Again, if all you get is same windows mobile screen do a hard reset.
If doesn't solve the problem do a hard reset, but do not press spacebar to reboot after. Instead, do a soft reset with stylus when the device asks you to press spacebar.
Check if you might have the NO GSM Problem (might be hard to see if you have a red background image like the original Vodafone does)

The following worked for me (sirjohnnyboy) when I was stuck in bootloader mode (while installing new ROM -stuck on 3%)

I followed the first set of directions for problem 4, (using command set 16 0) however the phone didn't become OS functional, instead it went to problem 2 (stuck on Windows Mobile Screen).

I then followed the instructions for problem 2, and ended up with problem 4 again. For the hell of it I just decided to try to install a different ROM and see if that worked.

I tried to install Schaps_WM6Pro_WWE_4.00_Full (followed all the directions) and the whole thing worked like a charm. I now have internet and SKYPE -Yippee!

I had already upgraded the radio and SIM and CID unlocked, and I guess the problem was that the first WM6 ROM I tried to use (3DES.3.5) just wasn't compatible with my phone.

Problem 3: Invalid Vender ID error

You get this error because your device is CID locked, this means you can only install ROMs from your operator/vendor and in the original language of your device. You can CID Unlock your Hermes if you are willing to use ROM upgrades from other operator/vendor or in any other language that the original rom shipped in your device.

If you see your device reset and go into a ROM flash screen at 0% and the flash software states Vendor ID error

A) If your bootloader version is 1.04 or below:

Do NOT disconnect the device or reset it.
Close the Flash software.
Click on ROMUpgradeUT.exe again and go through all steps. This time it should start flashing the ROM.

B) If your bootloader version is 1.06 or above: You MUST downgrade to bootloader version 1.04

Note: If you don't know your bootloader version, try "A)" if you get the same error again, try "B)" without disconnecting your device.

Problem 4: Device is stuck in bootloader mode (tri-color screen)

Important : Windows VISTA users need to make a change to their system to successfully use many ROM packages. See Mr. Vanx's guide here
If you are using Windows XP or Windows 2000, you MUST have the Microsoft .net framework installed on your computer.
1. Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
2. Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
3. Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
4. Open mtty.exe and select "USB" from the dialog box, then hit Ok.
5. You should see a white screen, hit enter and you should see a prompt like this: "USB>"
6. Type set 14 0 (do not copy and paste!!!) and hit enter
7. Soft reset with stylus
8. OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
9. if it doesn't unbrick, repeat all the steps but with the command set 16 0
I want to add something here that worked for me. Tried steps above but it didn't work. So what I did to get mine going again:

1. Disable Activesync: connections -- settings -- uncheck "Allow USB Connections"
2. Take out battery, sim, and sd card
3. Look at your phone for SPL version. Mine was 1.40.
4. Run RUUWrapper.exe on a ROM that you know would work. I used LSVW VP3G. Choose 1.40 bootloader option on the phone bootloader option.
5. Wait, don't hook up USB cable to your phone yet. Check the box where you're agreed to upgrade then hit Next
6. Now hook your phone to activesync and let RUUWrapper picks it up.
7. That's all. I guess if it didn't recognize your device at step 6, then I would try again if i were you.

This alternate procedure worked for me, using SPL 2.10. I did not re-install SIM card or memory card while I re-flashed the radio. Problem was caused by corrupt radio (1.48) image, which stalled at 41%.

The following worked for me (sirjohnnyboy) when I was stuck in bootloader mode (while installing new ROM -stuck on 3%)

I followed the first set of directions for problem 4, (using command set 16 0) however the phone didn't become OS functional, instead it went to problem 2 (stuck on Windows Mobile Screen).

I then followed the instructions for problem 2, and ended up with problem 4 again. For the hell of it I just decided to try to install a different ROM and see if that worked.

I tried to install Schaps_WM6Pro_WWE_4.00_Full (followed all the directions) and the whole thing worked like a charm. I now have internet and SKYPE -Yippee!

I had already upgraded the radio and SIM and CID unlocked, and I guess the problem was that the first WM6 ROM I tried to use (3DES.3.5) just wasn't compatible with my phone.

Problem 5: Device shows NO GSM when booting

The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)

Here is how to fix it:

METHOD 1

Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
Put your Hermes in bootloader mode
Connect device to computer using USB cable.
Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt.

Type the following commands (do not copy paste!!!)

USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0

If the password does not work, try password BsaD5SeoA
Reset your phone and put it back in bootloader mode
If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (if you can't flash the bootloader version 1.04 (for what ever reason) and you have KITL enabled Rom, then there is final solution - PB_KITL_HERMES))
Flash the patched radio used to simunlock the Hermes
Your phone should be alive again :)

METHOD 2

Also, Ive found that Hard-Reseting the device restores GSM.

Remove the battery
wait 10 second
Re-insert Battery
Turn the device on
Watch for "NO GSM" on boot
if you see it. Return to step 1. (sometimes you have to do it up to 20 times)

If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.

This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.

Related forum threads

Problem 6: Device doesn't turn on, shows red LED only

In this case you can try:

Remove battery
Connect Hermes to charger or USB
Insert the battery while Hermes is connected to charger
Red light should turn Amber
Soft Reset

This may restore your device, or at least let it run enough so that you can get to the bootloader or even Windows Mobile.

It also might be a good idea to try this on any brick, as it might improve the situation (especially in cases when the brick is the result of an apparently 100% successful ROM upgrade). It doesn't cost anything to try at any rate.

Also If you have just flashed boot loader 1.10olipro and the device doesnt even reach the Amber light, all you do is insert the batter and hold the OK and POWER buttons and soft reset it, just like you would to enter the boot loader from inside to OS.

Problem 7: Can't receive calls when upgrade radio to 1.43 or newer

It's a very common problems in China mainland and confused Hermes' fans in China mainland for a long time when radio 1.43 was released,

Now there is a very simple way to resolved this problem,

To exchange a new SIM,

The old SIM seems is not compatible with the radio 1.43 and newer,

Many people around me resolved that problem by exchanged a new SIM,

Maybe you have to spend a little money to exchange a new SIM,

In my city the price is RMB 30 to exchange a new SIM in China Mobile.

Please refer to this thread.

Phone bricked when writing to the Extended ROM

Users have reported bricked devices when the phone stops responding during a process which involves writing to the Extended ROM (once Ext_ROM has been unlocked and unhidden for read/write usage). The specific problem addressed here is when the Hermes will not proceed beyond the white "HTC" splash screen after the device hanging during a write to the Ext_ROM.

One solution to this problem is to write a new Extended Rom to the device using Bootloader 1.01MFG and the mtty.exe console:

Follow the instructions on the above link to flash bootloader 1.01MFG to your device.
Select the extended ROM you wish to flash to the device.
Follow the instructions from the "Hermes Bootloader MFG" page (see above link) to flash the new Extended ROM directly to the device.
Once the task 8 command is selected, the device will reboot and, with any luck, then proceed past the white "HTC" splash screen to boot the OS.
If this still does not address the problem, follow the "Hermes Bootloader MFG" instructions to flash a new copy of your preferred OS to the device.

Errors: List of errors and descriptions

Troubleshooting and Error Recovery

Almost all RUU related errors can be recovered. When an error occurs, the utility will display an error message and provide recovery measures to allow you to continue with the update process.

After errors are recovered, do the following to continue with the update process: 1. Disconnect the Mobile Device from the USB cradle/cable. 2. Reset the Mobile Device. 3. Reconnect the Mobile Device to the USB cradle/cable. 4. Check that the communication cradle/cable is connected properly. 5. Return to the ROM Update Utility to continue with the update.

If errors cannot be recovered, please refer to Q&A section for more details.

ERROR ?202, 204 : CONNECTION

This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.

ERROR 260 : CONNECTION

This error occurs when there is an “open port error” before upgrading the CE ROM image.

Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.

ERROR ?206 : MEMORY ALLOCATION ERROR ?280 : UPDATE ERROR

When you see any of these error messages, close other running programs on the computer and run RUU again.

ERROR ?208 : FILE OPEN ERROR ?210 : FILE READ

These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.

ERROR ?212 : FILE CREATE ERROR ?214 : FILE WRITE ERROR ?222, 224 : DEVICE NOT RESPONDING

These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.

ERROR ?220 : MAIN BATTERY POWER

This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).

ERROR ?238 : FILE READ

This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.

ERROR ?240 : FILE OPEN

When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.

ERROR ?242 : INVALID LANGUAGE ERROR ?244 : INVALID MODEL ID ERROR ?294 : INVALID VENDER ID ERROR ?296 : UPGRADE ONLY

One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.

ERROR ?246 : DEVICE NOT RESPONDING

This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.

ERROR 262, 276, 284, 302 : UPDATE ERROR

This error occurs during the CE ROM code upgrade process.

Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.

Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.

ERROR ?262

This error can also be fixed by using the Free HTC Hermes SIM & CID unlocker found at: http://wiki.xda-developers.com/index.php?pagename=Hermes_SimUnlock

1-Extract files to your computer 2-Run AUTO_Unlock_v3a.bat (Be very delicate to follow this process 3-Go back to the extracted files on your computer, open SSPL folder, and copy SSPL-HERM.exe to your device main memory and run it. On the device, it should change to colours and wait until you get USB at the bottom, disconnect the phone from the computer. 4-Locate your cooked ROM or whichever ROM you're trying to install. 5-Reconnect phone to the computer 6-Start upgrading your ROM and ensure to select 'Auto Detect' at the initial screen, and you will not get Error 262 again.

Remember you will need to follow the above steps everytime you wish to UPG your ROM.

ERROR 300 : INVALID UPDATE TOOL

This error message will appear when you use the incorrect RUU version to upgrade.

ERROR ?330 : ROM IMAGE ERROR

This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.

Back to the Hermes Home Page

Hermes_Upgrade Problems