Database Develop

HELP:Error 270 when upgrading!!!

I have tried all stickied CID unlocker/Hark-SPL over the last 10 hours today and all ended up with:
Error [270] : Update Error
The image file is corrupted. Please check your Update Utility. (PDA Phone Rom Update Utility 3.1.3.2)
Bootloader info:
TRIN100
IPL-1.00
Trin100
SPL-3.03.0000
I got AUS Versions of HTC - WM6 3.00.707.18
Somebody please help me!!!
Thanks a lot!

During my research on the forum:
1. tried disabling the USB > PC on HTC
2. also tried disabling the USB connection in Activesync
3. tried it via normal activesync connection method running RUU
4. also tried bootloader method running RUU
No matter what I do, I just keep on getting this stupid error 270!!!! Also had some error 260 on the way, saw lotsa post regarding that and got it fix! BUT just this error 270! I don't know what to do now!
HELPPPPPP!!!

jackkkkk said:
During my research on the forum:
1. tried disabling the USB > PC on HTC
2. also tried disabling the USB connection in Activesync
3. tried it via normal activesync connection method running RUU
4. also tried bootloader method running RUU
No matter what I do, I just keep on getting this stupid error 270!!!! Also had some error 260 on the way, saw lotsa post regarding that and got it fix! BUT just this error 270! I don't know what to do now!
HELPPPPPP!!!
Click to expand...
Click to collapse
Ran into that error myself but with s1rl4ncel0t's help managed to do it.
Try not putting your device in bootloader but launch the updater with your device set up normally, connected to/through ActiveSync. This was my mistake, I had the same error but tried updating with the device already in bootloader.

Try this
http://forum.xda-developers.com/showthread.php?t=296722
I have the same problem
it's run fine for me...

Error 101: Connection Error

Hello.
Im new here, first of all sorry for my english, and second thanks for this forum.
I have problems with upgrading my Siemens SX66 WM6.0 pro to a WM6.1
The ROM upgrade software tells me there is an Error 101: Connection Error
exactly like this
bilbo--baggins
Every time I try to do the rom upgrade for my PDA2K the device does a soft reset (when it's reset it then reconnects to activsync, and the green logo reappears) and after a while the ROM upgrade software tells me there is an Error 101 Connection Error. It's driving me nuts, I've tried all sorts of variants, soft reset first, hard reset first, USB port, USB2 port, Activesync 3.7.1, activesync 3.8, Windows XP, Windows 98. I don't understand why there is a connection error, because I can connect to activesync correctly, it even reconnects after the ROM upgrade causes it to do a soft reset. Please help! I've even tried following directions to copy the temporary files and running those directly but the result is the same.
Click to expand...
Click to collapse
can anyone help to solve this problem.
i have no problem with active syn connection, its synchronized with out any problem. my OS is winXP sp2.

This is a well known issue, I am sure its addressed in the Wikki on this site. The solution is don't reset your device when the on screen instructions ask you to do so, just continue with the upgrade.
Enjoy your new device once you have upgraded.

ok
i run upgrade program, the i like in instruction i put sx66 in to the cradle, active sync starting to synchronize well. then i push the next button in the upgrade program, the active sync is turning off and after couple minutes there is a message 'bout Error 101
p.s. the upgrade file i download from this thread http://forum.xda-developers.com/showthread.php?t=372485

plz help, tryin to use button rom-> error 260

i did the thing with active sync to make sure im a guest, and when i start the RUU button thing it starts then stops saying error 260
is there anything i can do to not get this message, i want to upgrade my 8125 to WM6

Error 260 is an open port error,its usually resolved by resetting the device and the pc. Try again after resetting 'SoftReset' the phone and 'Restart' your comp.
Secondly,which is your device,is it G3 or G4 and on which windows pc are you trying to flash winXP or winVista ?

i've restarted and reset the device, i have a G3 and my windows ps is running winXP
still no luck, when i run the rom downgrade program it crashes active sync and then gives me the error message

Then you should first disable USB connection of your ActiveSync (or kill wcescomm.exe in Task Manager yourself) before running RUU.

RE: Error 260
greatunclebob said:
i've restarted and reset the device, i have a G3 and my windows ps is running winXP
still no luck, when i run the rom downgrade program it crashes active sync and then gives me the error message
Click to expand...
Click to collapse
did you get it to work?

yeah i got it to work, the problem was that i forgot to take out the memory storage card, after i did that everything went well

[TUT] Dummies guide: recovering from RUU errors

Flashing roms doesn't always work out perfectly. So what do we do when we get an error during the Rom Update Utility (RUU) update process? Read this!
I have searched several times for explanations of error codes. I finally came across something quite useful. I couldn't find it anywhere in the Blackstone forums nor on the Wiki so I thought I would share it. This is a copy/paste from a thread I found by debonairone and modified slightly.
Here is a list of error codes and possible resolutions when attempting to flash a rom with the RUU:
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 VENDOR 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. This can also be caused by a mismatch between the CID of the rom you trying to flash and your device.
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~259] : 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 [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically only happens when you try to flash a new SPL to your device.
Solution: Use Soft-SPL before attempting the RUU 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.

Reserved for future use.

You know there's a wiki page for this
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Dave

DaveShaw said:
You know there's a wiki page for this
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Dave
Click to expand...
Click to collapse
Damn it! I couldn't find it... LOL! Can you delete this thread then?

Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks

HDuser said:
Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks
Click to expand...
Click to collapse
If that was directed to me, sure I can compare them and make this thread a solid combination of both. But I cannot update the wiki, that I know of at least

cRaCKwHoRe said:
If that was directed to me, sure I can compare them and make this thread a solid combination of both. But I cannot update the wiki, that I know of at least
Click to expand...
Click to collapse
Anyone can change the wiki, just click the "Edit" button at the bottom of the page.
Dave

Wow I feel dumb. I'll take care of it then

Where is the problem ?
sorry wrong threat

HDuser said:
Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks
Click to expand...
Click to collapse
I updated the wiki. You can trash this. Thanks!

Excellent addition mate to this site. Very informative

Crack can I ask a question? Finally took the plunge and had a go at flashing new rom. got stuck at the first hurdle, Got hit with an "error 262". Not sure if I follow the solution though as I took battery out as it suggested in the RUU and restarted. Same result, even tried the USB driver thingy but it gives me errors when I update the driver. Shows USB on the phone though.

marmin said:
Crack can I ask a question? Finally took the plunge and had a go at flashing new rom. got stuck at the first hurdle, Got hit with an "error 262". Not sure if I follow the solution though as I took battery out as it suggested in the RUU and restarted. Same result, even tried the USB driver thingy but it gives me errors when I update the driver. Shows USB on the phone though.
Click to expand...
Click to collapse
So did you have an issue flashing the actual ROM or the SPL? What SPL do you currently show in your bootloader? How were you trying to flash the ROM?

cRaCKwHoRe said:
I updated the wiki. You can trash this. Thanks!
Click to expand...
Click to collapse
Rmeoved sticky and will let this thread just move down the line.
Thanks for your Input (as always).

I got the same problem...
Error [262]
i just followed the recoffery of the RUU and after i pulled out batery and i whent back to my normaal device start-up it was recofered according to RUU.
but i still had the same error after i tryed updating again my ROM.
my SPL on my Bootlouder = 1.14.0000
i was flashing my ROM with ur Dummies guide and i whent for the HSPL flashing.
ive done the "Drivers updating HTC USB Sync " before with succes.
plz help me

i got the same problem error (262) when im trying to update my SPL to 1.54, that was started the 0% screen and just hold on that screen...
anyone can help me?

javahuan said:
i got the same problem error (262) when im trying to update my SPL to 1.54, that was started the 0% screen and just hold on that screen...
anyone can help me?
Click to expand...
Click to collapse
Used this tips,,, goodluck
Troubleshooting - manual SSPL
Boot up your phone.
Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.
Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.
When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
Go to step HSPL3 if successful.

Error message [270]
I'm getting this error message which says its a corrupt image, check utility and try again.. I can't find anything about this on the forum. Does anyone know anything about this?

markzladz said:
I'm getting this error message which says its a corrupt image, check utility and try again.. I can't find anything about this on the forum. Does anyone know anything about this?
Click to expand...
Click to collapse
ERROR 270 (Update Error - The image file is corrupted):
Your device is still CID locked while trying to flash a cooked/custom ROM. Flash the USPL or Hard SPL if you have not already done so! If you were using the temporary USPL (white screen) method when you encountered this, you have to wait for the screen to go completely white before flashing a ROM (reset and try again if the screen did not go white).
Click to expand...
Click to collapse
You need to first install hspl or uspl. Read the Dummies Guide to Flashing (link in my signature)

ClydeB1 said:
You need to first install hspl or uspl. Read the Dummies Guide to Flashing (link in my signature)
Click to expand...
Click to collapse
Thanks, will try that and see if it works. The problem at the moment is when I'm flashing the ROM after I've installed USPL it goes to about 100% before failing and giving me that error message.

[Q] Can't Flash new phone

HTC Touch Pro2 (Boost) I put a Sprint TP2 on Boost mobile with the newest Energy ROM. Two days later, the screen went bad (not b/c of the ROM). I got a replacement phone and I cannot get it to unlock. I get errors (262 and 240) I have read for hours and tried several resets and still can't unlock the phone or maybe my terminology is incorrect? I cannot get the phone unlocked. I can't get Energy ROM to flash on this phone? Also, this phone runs out of battery power overnight without using it. HELP!

Johnhcfllc said:
HTC Touch Pro2 (Boost) I put a Sprint TP2 on Boost mobile with the newest Energy ROM. Two days later, the screen went bad (not b/c of the ROM). I got a replacement phone and I cannot get it to unlock. I get errors (262 and 240) I have read for hours and tried several resets and still can't unlock the phone or maybe my terminology is incorrect? I cannot get the phone unlocked. I can't get Energy ROM to flash on this phone? Also, this phone runs out of battery power overnight without using it. HELP!
Click to expand...
Click to collapse
error 262 means a USB connection problem - see Hard-SPL thread 1st and 2nd posts for USB connection troubleshooting tips.
http://forum.xda-developers.com/showthread.php?t=550131
I'm also curious...can't remember what error 240 means - what is the error text that goes with it?

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.
Q: During the upgrade, the progress bar is moving. If the error message (ERROR [262] : UPDATE ERROR) appears, what should I do?
A: This may occur when the connection is lost, without power supply, computer host is down, or due to other unexpected cases. You will see that there’s still one progress bar displayed on the device but it is not moving any more. The device cannot get into the Wince screen, so you cannot connect with ActiveSync. This problem usually can be recovered. You just need to follow the instructions in the error message box, reset the device, and run RUU again. RUU will re-flash the whole image again.
Note: You should remove the battery and reset the Mobile Device.

Well I did that several times and keep getting the same error.

Johnhcfllc said:
Well I did that several times and keep getting the same error.
Click to expand...
Click to collapse
same? 240 or 262? for 262, did you check out the first two posts at the link?