Database Info

-[Sticky] maybe - Flashing RUU Error/Solution & Explanation List-

I realize this information is on the HTC website but I have seen alot of questions lately regarding these errors. I decided that maybe, just maybe it might help someone with an error when flashing a rom, radio or splash and they can't quite figure out what the error is referring to. I also figured that this might lighten the load that GSLEON3 has been seeing lately with all of the "HELP, I think I BRICKED my phone" threads that keep popping up. Maybe it will help and maybe it won't but I thought it might be worth a try. I'd like to say thanks to OLI, Jocky, all of the rom cookers, GSLEON3 and XDA. You people make this fun.
I hope this helps someone.
? 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 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 KaiserCustomRUU.exe file and an RUUSigned.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.
? 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 [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 [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.

Nice one mate, at leat this will give people who flash some idea what to do when or if they get errors flashing.

great find thanks for posting this will be useful for everyone.

Obligatory "thank you" post.

haha ok ok mistake now i see the solutions xD!

edit...............

Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!

I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!

Confused Stu said:
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
Click to expand...
Click to collapse
I'll add this to the post. Thanks Stu.
_Alex_ said:
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Click to expand...
Click to collapse
I thought so to but I have had to answer a couple of these lately and was hoping that this might help to clear a few things up.

Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.

RPG0 said:
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
Click to expand...
Click to collapse
I can make that change.

Thanks for the info pal

helpful! thankx

Wiki
Ported to the Wiki
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Ta
Dave

Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?

iXiR said:
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
Click to expand...
Click to collapse
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave

DaveShaw said:
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
Click to expand...
Click to collapse
That's similar to my own schedule. P1 got to have a secret in finding time for this kind of things

ERROR 200
I got this error 200 "get newer update utility" I am using windows vista 32 bit.
where can i get a newer update utility? thanks

I-mate JasJam upgrade error
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh

rumjar86 said:
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
Click to expand...
Click to collapse
Try resetting the phone and the computer to make sure that no other processes are running. Then try putting phone into bootloader, and when sync'd try flashing from there.

[Q] Help in the search for bootloader [FS Loox 720]

I would highly appreciate any advice as to where I can find a bootloader for
fuji-siemens pocket loox 720. I was updating a firmware when a blackout
happened due to storm. I was able to access flash memory using JTAG interface,
but was unable to locate the bootloader itself.
According to the info I've found, after deleting 41 start bytes in original
*.nbf firmware, next 512 bytes are supposed to hold the bootloader. Using
hex editor I have removed that number of bytes, then tried to upload via
JTAG flasher. Upload itself was fine, but the device still doesn't work.

[Q] No internal memory. Free memory, 0.00 bytes. What happened?

At first, my phone was soft bricked and i let others fix my phone. Theyve installed it with a new firmware, more like they put it back to stock eclair, a bit different than the original. But when he did that the memory become 0 bytes free. Why is that so? Is it about the kernel or something? What can i do?

Dannahsaur said:
At first, my phone was soft bricked and i let others fix my phone. Theyve installed it with a new firmware, more like they put it back to stock eclair, a bit different than the original. But when he did that the memory become 0 bytes free. Why is that so? Is it about the kernel or something? What can i do?
Click to expand...
Click to collapse
Do a factory reset (data wipe) or reflash a new rom

Dannahsaur said:
At first, my phone was soft bricked and i let others fix my phone. Theyve installed it with a new firmware, more like they put it back to stock eclair, a bit different than the original. But when he did that the memory become 0 bytes free. Why is that so? Is it about the kernel or something? What can i do?
Click to expand...
Click to collapse
a. reflash a New ROM, if it does not solve
b. Format Phone memory and SD card
c. goto Step a. It should most probably solve the issue. Pl take a backup of whatever you desire before this attempts!!
It appears that your memory partitioning is not correct. I had the same issue in my G3 some time back!!
Now running Cm7.1

Uhmm, how can i flash a rom on my phone if i cant even root my phone through z4root? Manual root?
I have flashed cyanogenmod before, but the features are not complete so i will try a new one. Is kyrillos compatible for eclair? If not, any suggestions?

I cant root my phone through superoneclick.. this shows up.
SuperOneClick v1.8.0.0
Checking drivers...
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
OK
Pushing psneuter...
459 KB/s (585731 bytes in 1.244s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
1522 KB/s (1062992 bytes in 0.682s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs rw 0 0
FAILED

No need to root to flash. Just flash a custom rom straight to your phone. Just follow the flashing instructions and you'll be fine
Cheers
Sent from my i9003 powered by Cyanogenmod 7

Thanks now im gonna flash my phone through Odin, my phone is already detected by odin but the Reset time is not checked, and the checkbox is disabled. How did this happen? :\

Dannahsaur said:
Thanks now im gonna flash my phone through Odin, my phone is already detected by odin but the Reset time is not checked, and the checkbox is disabled. How did this happen? :\
Click to expand...
Click to collapse
No need to reflash
extract the .zip and flash the .tar as one package in odin
for info on odin, go here: forum.xda-developers.com/showthread.php?t=1372414

0.00 bytes also happened to me, at june 14 2022 8:00 PM UTC, and then i cannot open apps, please give how to increase memory without uninstalling apps or files, videos, my phone storage is dead, cannot install ANY app

Can't get to ClockworkMod

I installed Flashback 10.1 a while back. Today I wanted to install 10.3 and found out that I couldn't get into ClockworkMod at all. It would do a normal reboot instead of going to the recovery mode.
Any help is appreciated.

Just to be sure, you *are* holding the volume + button when you press the power button and keeping it held down until you see "recovery key detected" in the upper left corner?

Yes, I see
recovery key detected
Booting recovery kernel image
But it would stay there with the birds and "View Sonic - See the difference" forever, never go further than that.

Use nvflash and reload only ClockworkMod. Use the commands in this thread.

rajeevvp said:
Use nvflash and reload only ClockworkMod. Use the commands in this thread.
Click to expand...
Click to collapse
Hello rajeevvp,
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Thanks,
ssummerlin

ssummerlin said:
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Click to expand...
Click to collapse
That's a very strange error. What led to it?
Try these suggestions one by one.
1. Use a different USB cable and port on the PC. Bad cables and USB ports have been known to cause problems.
2. Open the gTab up and use the reset button, then disconnect and reconnect the battery.
3. Do the nvflash on Linux.

Did you ever find a fix for this, cub2000?
I ran into the same thing, when I attempted to update to CWM 5.5.04 (via flashable zip) using the procedures outlined in the [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH thread.
After doing so, I figured my best bet was to roll back to bekit's original image, so I followed the procedures outlined in the [STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions) thread to roll back to TnT 1.0-2638.
I can't remember the specific ROM I was on before -- it's been ages since I last powered up my gTab. It may have been TnT Lite. Whatever it was, I'm fairly certain I was running Bootloader v1.1.
After nvflashing back to 1.0-2638, TnT offers an update as soon as I connect to wifi, but the update fails in the same way that CWM fails. It hangs here:
recovery key detected
Booting recovery kernel image​
The awful, original TnT still runs on my tab, so it's not a true bricking (or even a soft-brick), but now I'm stuck with... well, I'm stuck with the awful, original TnT.
If I find a way around this, I'll let you know. If you've already found one, please let me know!
Thanks.

See this thread.

Thanks, rajeevvp. I actually found a different solution before I got your recommendation; just hadn't had a chance to update this thread yet.
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
I'm up and running now! I may have chosen a different path, but I appreciate the help.

colbymulkey said:
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
Click to expand...
Click to collapse
You mean you flashed AOKP and then booted into AOKP?
BTW, did you expand "system" to more that 250MB for AOKP?

rajeevvp said:
You mean you flashed AOKP and then booted into AOKP?
Click to expand...
Click to collapse
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch). (I found it in a thread on these forums, but I can't seem to find that thread now.) I'm pretty sure this is what got my bootloader and CWM back in sync...
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
rajeevvp said:
BTW, did you expand "system" to more that 250MB for AOKP?
Click to expand...
Click to collapse
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.

colbymulkey said:
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch).
Click to expand...
Click to collapse
That package would've made your system partition 256 MB in size.
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
Click to expand...
Click to collapse
That's what I thought: You booted directly into AOKP after flashing it.
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.
Click to expand...
Click to collapse
Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now, but, that will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.

rajeevvp said:
That package would've made your system partition 256 MB in size.
That's what I thought: You booted directly into AOKP after flashing it.Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now
Click to expand...
Click to collapse
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet. Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
rajeevvp said:
That will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Click to expand...
Click to collapse
Face detection is of little interest to me on this device; not too worried about that. Still, I don't really see a problem with upping my system partition a few MB -- especially if it'll help future-proof the system. I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
rajeevvp said:
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.
Click to expand...
Click to collapse
I'll give the factory reset a shot and let you know if it works; may even attempt to repartition the system partition, just to make sure everything's kosher.
Thanks for recommendations!

colbymulkey said:
I'll give the factory reset a shot and let you know if it works...
Click to expand...
Click to collapse
The factory reset didn't fix my Play Store issues. I was going to settle on the Amazon AppStore as a work around, except I can't even seem to install the APK for the Amazon AppStore. It downloads, but I can't launch it directly from my notification tray, and it's not listed in the "Downloads" app.
I love AOKP on my SII, but I may flash another ROM to see if I find something that works a little better (for me) on my gTablet.
Thanks, again, for your help rajeevvp!

colbymulkey said:
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet.
Click to expand...
Click to collapse
In CWM or in the ROM, run this dmesg command right after the system boots:
Code:
$ [B]dmesg | fgrep -i 'Kernel command line'[/B]
<5>[ 0.000000] Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100908 btmac=6037cf131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[B][email protected](system)[/B],[email protected](cache),[email protected](bootbmp),[email protected](logodata)
In APX mode, use the ``--getpartitiontable'' flag and look through it for the APP partition:
Code:
C:\> .[B]\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
Multiply the NumSectors and BytesPerSector parameters.
Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
Click to expand...
Click to collapse
Well, that depends. If critical bits have not been written then you will have immediate crashes or bootloops. OTOH, if unused files have not been written then you won't notice any problems until something attempts to use them. Going by what the AOKP ROM installation script does, the last thing to be written is the face-detection stuff as I said. This would account for your not noticing any major problems.
If you look at the /tmp/recovery.log file right after you install AOKP you'll be able to see precisely which files have not been copied owing to lack of space.
I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
Click to expand...
Click to collapse
Go for 270 MB.

CWM restore issues (large data backup file)

I am not sure whether anyone else encountered this, but I am having an epic failure restoring a backup made with Rogue XM Recovery 1.3.0 (CWM-based v5.0.2.7).
The backup proceeded without errors.
The symptom is a beginning of restore followed by this error message:
Code:
Error restoring /data!
Under the hood: tar is complaining that the file is too large (my /data backup weighs in at ~3GB) with the following error from the recovery log:
Code:
tar: seek failure: Value too large for defined data type
I saw remarks here and there that 2GB is the size limit for the version of tar included in busybox (i.e. large file support is missing). Can anyone verify whether this is true?
If so, anyone relying on CWM for backups is screwed if their /data is too big.
I verified that the backup did, in fact succeed (i.e. I have a data.ext4.tar file). At the moment I am trying to restore by re-tarring it piecemeal.
Will see how it goes.
In the meantime: does anyone successfully use a different recovery for large-file backup?

feisty_noodle said:
I am not sure whether anyone else encountered this, but I am having an epic failure restoring a backup made with Rogue XM Recovery 1.3.0 (CWM-based v5.0.2.7).
The backup proceeded without errors.
The symptom is a beginning of restore followed by this error message:
Code:
Error restoring /data!
Under the hood: tar is complaining that the file is too large (my /data backup weighs in at ~3GB) with the following error from the recovery log:
Code:
tar: seek failure: Value too large for defined data type
I saw remarks here and there that 2GB is the size limit for the version of tar included in busybox (i.e. large file support is missing). Can anyone verify whether this is true?
If so, anyone relying on CWM for backups is screwed if their /data is too big.
I verified that the backup did, in fact succeed (i.e. I have a data.ext4.tar file). At the moment I am trying to restore by re-tarring it piecemeal.
Will see how it goes.
In the meantime: does anyone successfully use a different recovery for large-file backup?
Click to expand...
Click to collapse
I have used TWRP to restore 650mb system+3gb data (including movies n songs).... restoring worked fine but at the same time one of my attempts failed n I was stuck at Asus screen.. so very rarely everyone is bound to hit recovery error issues I guess... but mostly it works like a charm...
Sent from my Transformer TF101 using xda app-developers app