[TUT] Dummies guide: recovering from RUU errors - Touch HD Windows Mobile ROM Development
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.
Related
Update Rom Failed
Hi, I have a problem with my Wizard, my rom update failed because the pc reboots in the middle of the installation and now only the Red Green Blue screen appear with three things, IPL 2.17, SPL 2.17 and in the right top corner RUU. I can't enter in the bootloader (pressing the camera button and turn on) What can i do to fix this and update a new ROM? Thanks in advance.
....... while on that screen plug in the usb cable and re-run the update utility.... Since the RBG screen is the bootloader...
I tried to do it, but i get ERROR[300] : INVALID UPDATE TOOL in the PDA Phone ROM Update Utility 2.00.1 Thanks
is working now. tks anyway
I'm having this same problem... not sure what's going wrong.
msmobiles.com: Q: If I encounter ERROR [300] : INVALID UPDATE TOOL, what should I do? A: This error message will appear when you use the incorrect RUU to upgrade. Please make sure you use the correct RUU version to upgrade. Click to expand... Click to collapse
Normally, you can only flash an official rom to restore from the point you are at. Once the bootloader is the only thing that comes up, a custom rom will not do the trick. Once you have the official rom installed, you can then "cross-grade" to a custom rom.
_Nomad_ said: msmobiles.com: Click to expand... Click to collapse Ok, so using some Italian version is working for me. RUU is the same as the pda phone updater tool right? But something is still going wrong. It says I now have OS 2.26.10.2, which is the molski rom I've been trying to get on here, but neither the ipl or spl change, and the same cingular settings keep loading. Man this is confusing me. I have paid to unlock my g4, and I still can't get it to work the way I want it.
Error 300 while installing Molski
I currently have AKU3.2-1.0RC1. What do I have to do to install RUU_Molski.Biz_AKU2.3-226102_22610105_024711_WWE-30MB-CF2? Also, Molski mentioned I need an Extended ROM - how do I install that? Thanks guys. Tried RomUpgradeUtility_noID .....there was an Error 240 =(
Error 300: Error message will appear when you use the incorrect RUU version to upgrade. Error 240: 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.
_Nomad_ said: Error 300: Error message will appear when you use the incorrect RUU version to upgrade. Error 240: 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. Click to expand... Click to collapse O i got that. that's from the Readme file..... But what does that mean?....like.can you suggest the next step? =)
Well... I'd suggest that you use this ROM to downgrade with. You should be aware that this ROM also downgrades the ipl/spl so make sure that after flashing it upgrade to an official ROM that also upgrades your bootloader. NOTE: You have to make sure that your device is CID-unlocked before flashing a custom ROM. If you don't know how, look here... After these steps you shouldn't have a problem upgrading to the latest molski.biz ROM. Oh, and the extended_rom is, in the case of molskis rom, already included in the download. As it is in almost every ROM available, so you really don't have to worry about that... Good luck and give us a shout if you run in to any problems not answered in the above mentioned thread
_Nomad_ said: Well... I'd suggest that you use this ROM to downgrade with. You should be aware that this ROM also downgrades the ipl/spl so make sure that after flashing it upgrade to an official ROM that also upgrades your bootloader. NOTE: You have to make sure that your device is CID-unlocked before flashing a custom ROM. If you don't know how, look here... After these steps you shouldn't have a problem upgrading to the latest molski.biz ROM. Oh, and the extended_rom is, in the case of molskis rom, already included in the download. As it is in almost every ROM available, so you really don't have to worry about that... Good luck and give us a shout if you run in to any problems not answered in the above mentioned thread Click to expand... Click to collapse I had my CID unlocked using lokiwiz. Very happy - first time everything just went as described in the thread....! However I wasn't able to use __RUU_Wizard_1050412_WWE_101_11210_WWE.exe - It gives me an Error 300 again. (My Wizard is newly hard-resetted so I guess I don't mind hard-resetting it again if needed)
Help needed - Trin won't update with any rom (3.5.2 LVSW Edition)
Hello, I have this rom : RUU_Trinity_LVSW_WWE_1.25.0.8_GPS (AKU 3.5.2) from http://forum.xda-developers.com/showthread.php?t=302198 I wanted to test the new WM6 roms, unfortunately, my trin doesn't update with any rom I tried (Orange, HTC, LVSW Wm6, Mun_Rus Wm6, ...) It tells me : "ERROR 262 : UPDATE ERROR ... communication error during the process" I'm stuck on LVSW Wm5 rom :'( Not sure if Des SPPL is causing this problem... anyway, I tried to update it from Bootloader or synched, on XP and Vista, 5 differents roms... no luck. I would really appreciate some help, thanks
can you list the steps of what happened, in order? also, just to make sure i understand, have you already tried to manually enter the bootloader and THEN run the RUU? *edit* one last question, have you tried this.. after the error, leave your device connected and in bootloader, then restart the RUU.. can you give me your device details too?
Well, when I run the update with normal step (connect AS, then launch update...) when the update is ready to be started (progress bar appears), phone have to switch to bootloader, which it does. However, it seems that the RUU is waiting for that since it return me this error: ERROR 246 : Device not responding And I have to exit. I don't understand ? Progress bar didn't even appear on the phone. At this time boot loader shows IPL-SSPL by Des SPL-1.07.ds So since I'm already in Bootloader mode, i try to launch RUU again. Here is the error I get when the progress bar appears on both phone and PC : ERROR 262 : Update Error And it offer me to recover the device, which I don't need as the current rom has been left untouched and is still functionning after the error. Then I reset the device to enter bootloader this time: IPL-0.50 SPL-1.06.0000 same error : ERROR 262 : Update Error I'm kinda out of option, thanks a lot for your help !
well, it's been a pretty common thing for the RUU to give an error when the device goes in to bootloader (can't detect it for some reason). Most times, simply running the RUU again while the device is still in bootloader works fine. Why don't you put hard-spl on just in case, manually enter bootloader (which will then be hard-spl) and run the RUU again. You shouldn't enter the bootloader manually unless you've loaded hard-spl or sspl on to your device. From what i understand you won't be successful from what you did after the hard reset. When your phone went in to bootloader the first time, it was with SSPL pushed to your device by the updater program to enable you to update safely. After resetting, you're back to your normal bootloader which won't help anything. I know one time it did this to me, and wouldn't connect to my device. I started the RUU about 3 times in a row with my device on bootloader, and for some reason after the 3rd time it suddenly worked.. weird, i know. anyway, hard-spl will make the whole process safer.. let me know if it connects or not, i'll see if i can help you troubleshoot
I wanted to install hard-spl, but it runs as a normal RUU and give me exactly the same errors as a normal run update (error stated above). So I don't see how I could install it Another thing weird, when I run a official HTC rom update, when the udpdate should start (device enter in boot loader, progress bar appear in bot PC an device), the Trin reset itself and boot as normal... of course the RUU gives an error due to this reboot ... Same weird behavior with an official Orange rom... Now I'll try with SSPL... Oh and thanks a lot for your help
simply try to run twice ROMUpdateUtility.exe after error
Please read carefully what I have posted (and the steps I ran into)... Already launched again RUU, it gives me an Update Error and the device is stuck on the screen that show the progress bar. Need to soft reset... I can't launch again the RUU after that since the device is no longer recognised as connected on PC.
I confirm I can't manage to install the Hard SPL, even after laoding Des sspl from the device... Defintly blocked
At last I have succeeded in upgrading the device. Seems like my bootloader was somehow corrupted or something... after doing another Hard Reset it have installed hard spl succesfully... I had already done a hard reset before, so I don't understand what happened. Nevermind, at last i can try wm6 thanks a lot for your help racerx_ anyway
hey no problem.. not sure that i actually helped haha.. but i'm glad you sorted it out. happy flashing!
Might it have been the USB driver on the desktopside ? Did you see XP recognize and install HTC USB device again, after device disconnecting from AS and going into bootloadermode for first time ?... Just a thought...
Not sure what it is, but it's happening again, can't update anything as the bootloader seems somehow corrupted. When i enter bootloader it briefly display the 3 color, then grey screen with "loading" and then the hard spl screen from Olimpo... the only problem I see is that it does no longer display TRIN100, but only little dots (like if it was corrupted)... Very annoying situation, and I have already done some hard reset, but nothing
So more exactly, where I start DES SSPL or when I enter Olipro Hard SPL (that I installed before WM6), it shows the good infos like : TRIN100 xxxx TRIN100 SPL- But after 1/4 of second, it start loading for a very short moment and display again the RGB screen with the infos except the "TRIN100" parts are like this ':':':':':': Anyone has seen this before ???
@cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again. If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case.
pof said: @cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again. If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case. Click to expand... Click to collapse ...... well well, that was simple hahaha (and I feel stupid lol). yes I had my SD inserted (and I remember only now that the last time it worked I had indeed removed the mini-SD). So, thanks to you I have understood this issue at last ! Muchisimas gracias por tu gran ayuda pof
Now the question is, wtf do u have on this SD card? LOL
Errr that's a good question... maybe it is time to clean those 4go of things (which most of those come from the SD I had on my Prophet, in the top of that) Anyway, it's a rare specimen indeed... want a copy to play with heh ?
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...
HELP:More than 20 times up rom to pzzuchel liteheavy 1.17 without success :((
I try to update to pzzuchel liteheavy 1.17 for about 10 times but i got the same error 262 with different computers and different usb ports. On the phone screen i saw a quick message like "no image file". So i wonder if i have to copy the nbh file to the phone or not THank you very much
did you unlock your device with HSPL first?
Yes sure. After i click on this file it extract some other files like RUU.exe ... and i did following the instruction in this forum but then usually i got 262 error
...if you would have posted it in the thread corresponding to the ROM i would have noticed it before... ...Were you able to extract the archive without errors? ...is this the first ROM you are flashing on your device? ...did you use the SD procedure or the PC installation? ...how did you configure activesync (fast/slow)?
mitut said: Yes sure. After i click on this file it extract some other files like RUU.exe ... and i did following the instruction in this forum but then usually i got 262 error Click to expand... Click to collapse what is your SPL version now in tricolour screen?