Please remember to add a category to the bottom of each page that you create.
See categories help for further details, but most will probably be [[Category:HTC ModelName]].

RUU Errors

From XDA-Developers
Jump to: navigation, search

A list of the Common ROM Upgrade Utility (RUU) update errors and their common solutions / explanations. Originally taken from this post by P1Tater

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. If the problem persists try removing and re-installing ActiveSync.

ERROR [206] : MEMORY ALLOCATION

When you see this error message, 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 [226] : FILE WRITE== file) is corrupt, re-download the image. (thanks ?DupinBJK) ;)

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. Check that the contents of the folder is a CustomRUU.exe file and an .nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up. Thanks ConfusedSTU. Also this occurs due to permission problems. Try moving the RUU folder to the root Hard drive directory, and ensure you are an administrator. Running RUU from a briefcase rather than an ordinary folder gave me this error, but it was fine when I moved th RUU foler out of the briefcase(XP OS.

ERROR [242] : INVALID LANGUAGE

The device has another language than the ROM that you are trying to flash. Example: The device is GER, so flashing a WWE ROM is not allowed. This can often be bypassed by CID-Unlocking or Soft-SPL / Hard-SPL.

ERROR [244] : INVALID MODEL ID

You're trying to flash an Image to a phone it wasn't designed to run on, i.e. a Kaiser Image on a Polaris.

ERROR [246] : DEVICE NOT RESPONDING

This error message indicates that RUU cannot start the update process. This usually indicates something is wrong with your device. If it continues happening after several attempts, try putting your phone into the bootloader before running the RUU. If you still cannot get it to work, please contact your service provider for assistance.

ERROR [248-259] : UPDATE ERROR

This error occurs when there is an "open port error" before upgrading the CE ROM image. You can soft reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again.

ERROR [260] : CONNECTION

This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use SoftSPL before attempting the RUU again.

ERROR [262] : UPDATE ERROR

This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.

ERROR [280] : UPDATE ERROR

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

ERROR [294] : INVALID VENDOR ID

Every device contains a short string that identifies the operator who sold it. Because the same device is sold by different operators, this prevents users from flashing a T-Mobile ROM to a device that was sold by Orange, for example. You probably need to Install a HardSPL or CID Unlock your device.

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 [300] : INVALID UPDATE TOOL

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

ERROR [264, 274] : CONNECTION

ERROR [302-318] : UPDATE ERROR

ERROR [320-328] : INVALID COMMAND

These errors seldom occur. However, if one of these errors occurs, it usually is not recoverable and the device needs to be sent back to the customer service center. In this case, you have to flash a new ROM code. You can retry the RUU to see if it recovers.

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 and make sure the image file is correct to upgrade. This can also happen when you have unlocked bootloader,Relock and flash again