PPCGeeks - Update Error 262

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- HTC Vogue (http://forum.ppcgeeks.com/forumdisplay.php?f=48)

- - Update Error 262 (http://forum.ppcgeeks.com/showthread.php?t=33949)

Update Error 262

I'm getting the following error recently when I am doing a ROM flash. Any help?

Re: Update Error 262

I can't flash with anything but mtty... With RomUpdate utility, it gives me error 262. The phone has no bad blocks.

Re: Update Error 262

http://www.4winmobile.com/forums/win...uu-errors.html

(for future reference for when others get this...)

Quote:

RUU Errors
Here is a list of error codes and possible resolutions when attempting to flash a rom... I haven't come across all of these error personally, so utilize a bit of common sense when employing these suggestions... As always, remember that we are not responsible should you brick your device...

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 [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 phone 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 [248~260] : UPDATE ERROR

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 [262] : 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 [264, 274] : CONNECTION
ERROR [302~318] : UPDATE ERROR
ERROR [320~328] : INVALID COMMAND

These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.

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.

Re: Update Error 262

Problem fixed by reflashing 2.31 bootloader coKe. It appears it was corrupt for some reason.

Re: Update Error 262

How to fix this is the next issue.

Bootloader Reflash

Re install of active sync(changing usb port/disable firewall/anti virus)

These are the solutions suggested on XDA but for other devices....

Anyone know anything else?

Re: Update Error 262

Cool.. i've seens several ppl with this error 262 but never found an actual answer for how to fix it... mostly those flashing for the 1st time... so i was abit surprised to see the vet also gets this msg :P

anyways glad you found out how to fix it... and thanks for the list of RUU... can come in handy.

Re: Update Error 262

follow the steps in this thread, fixed my 262 problem
http://forum.ppcgeeks.com/showthread...78#post1246978

Re: Update Error 262

i just had this prob, but i just moved to my old computer running windows XP (my laptop is running windows 7) and it worked perfectly. weird. anyways. i'm uploading NFSFAN's V1.00 Rom as i type XD

Re: Update Error 262

Quote:

Originally Posted by NFSFAN (Post 371355)

Problem fixed by reflashing 2.31 bootloader coKe. It appears it was corrupt for some reason.

I had this issue when cooked Verizon ROM and my .rgu had "first boot time zone fix"
;*** First Boot Fixes ***
;================================================= =====
[HKEY_LOCAL_MACHINE\Software\Microsoft\Clock]
"GMT_OFFSET"=dword:00000168
"AppState"=hex:11
"TZIndex"=dword:00000004
"HomeDST"=dword:00000001
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"NITZEnable"=dword:00000001
[HKEY_CURRENT_USER\CONTROLPANEL\PHONEEXTENDFUNCTION \CDMA]
"SyncSystemTime"=dword:00000001

it syncs to pacific

This made a conflict with 1 of the Verizon's provxmls (they had entries to sync to eastern time zone)

That conflict made my phone acting strange (touch responce driver worked strange too),I couldnt flash even shipped exe ROM(same error 262-connection,and there is nothing wrong with connection),and only coke 2.31 ruu helped me
(extracted coke 2.31 to empty folder and ran ROMUpdateUtility.exe of that folder).just like flashing any custom ROM,only this time it was flashing coke 2.31 unlocker.Process takes 3-5 sec to upgrade from 0% to 100% and no more 262 errors.

Sorry if wrote too much.That way first time flashers can understand what I was trying to say...