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.

[RESOLVED] HTC HD7 Mango Navigon Select V 3.0 WP7 Inizialization Error BaseStyles

Hello,
I've read the following complete thread and am running into troubles after installation of the application and the following upload of the datafiles via the webserver provided by Kounadisk.
I'm always getting the following error message after starting the navigon application:
"Inizialization Error Missing data file: BaseStyles"
Background info:
1. My phone: HTC HD7 T9292 currently running [DFT Freedom ROM] Mango 7720 Custom ROM for HTC WP7 First Generation with matching RSPL/HSPL.
2. The application itself was installed via Tom XAP Installer.
3. The files according to the filelist40.xml were downloaded in 1 folder according to this post (Link)
4. After successful download of the files via the navigon application the above mentioned error appears.
I may have misunderstood the instructions of the 3rd points post as they are not easy to understand...
Any suggestions?

bobmorane101 said:
I'm always getting the following error message after starting the navigon application:
"Inizialization Error Missing data file: BaseStyles"
I may have misunderstood the instructions of the 3rd points post as they are not easy to understand...
Any suggestions?
Click to expand...
Click to collapse
As you may have read in the thread this error occurs when at least one file is not compatible. Kounadisk provided files to replace some of the ones downloaded from the Navigon server. If you don't replace them you will get an error.
if you know the green demon and you add this to the site's url
/files/details/2715384/6973616/
you will find a package that has all the correct data files that work with Navigon on Mango. If you already got your maps then only download data, poi and sound, replace all files downloaded via Navigoncontent.exe with the ones from the above package and you are good to go.

Thank's a lot!
The package provided above solves the issue. But only the maps in the package can be used if you get the "BaseStyles" error message. All other files from the navigon server will create other errors like <Initialization Error "MapPath" doesn't contain any valid map> with the most recent map files.

bobmorane101 said:
2. The application itself was installed via Tom XAP Installer.
Click to expand...
Click to collapse
Hello, if someone can share the V4.0 .xap file, it will be great
[email protected]

derausgewanderte said:
As you may have read in the thread this error occurs when at least one file is not compatible. Kounadisk provided files to replace some of the ones downloaded from the Navigon server. If you don't replace them you will get an error.
if you know the green demon and you add this to the site's url
/files/details/2715384/6973616/
you will find a package that has all the correct data files that work with Navigon on Mango. If you already got your maps then only download data, poi and sound, replace all files downloaded via Navigoncontent.exe with the ones from the above package and you are good to go.
Click to expand...
Click to collapse
Thanks derausgewanderte.
Can I say that the green demon gives me "The torrent you requested was deleted by its owner or a moderator."
I continue to have the BaseStyle error and am wondering whether the package you talk of may be lurking elsewhere?
Greetings

ajt320 said:
Thanks derausgewanderte.
Can I say that the green demon gives me "The torrent you requested was deleted by its owner or a moderator."
I continue to have the BaseStyle error and am wondering whether the package you talk of may be lurking elsewhere?
Greetings
Click to expand...
Click to collapse
sorry, I removed the torrent because as of yesterday it's outdated. Version 4 of Navigon is out.

I also have one error... (47) Could not calculate route profile

bobmorane101 said:
Thank's a lot!
The package provided above solves the issue. But only the maps in the package can be used if you get the "BaseStyles" error message. All other files from the navigon server will create other errors like <Initialization Error "MapPath" doesn't contain any valid map> with the most recent map files.
Click to expand...
Click to collapse
I have 'Mappath doesn't contain any valid map' after 1) installing navigon v3.0 and 2) update all other files (navigon v3.6 android maps) using navigoncontent.exe. Then when i run navigon, I have this error. How can I correct this problem? How can i find 'the maps in the package'? Thanks.

Thanks very much

[Q] OTA Update Accepted... then nothing? [FIXED]

I've tried installing the new 1.85 OTA update, but it really doesn't seem to be doing anything.
I do "check for updates" then it says a new update is found, so I click download. It says it'll download next time the phone is on Wifi (even though it was currently on wifi). I disconnect from wifi, reconnect to wifi, then it simply said "an update is available for your phone". Then I get the lovable lockout period before I can try again.
Am I doing something wrong?
Any advice or suggestions would be great.
HTC One XL on AT&T
Rooted and locked, running 1.73 from RUU
----------------------------
I finally got the update to start downloading! I'm not sure which step it was specifically that fixed it, but here's the list:
In Titanium Backup, I used the "unfreeze all" option. As a side note, I hadn't uninstalled any of the system bloatware, just frozen using CleanTOOL v1.1 from CleanROM.
Moved the date forward about a month.
Dialed "*#*#CHECKIN#*#*" and waited till it said it was successful.
Ran the system update check, got the standard "new update found".
Waited a bit, got the "Please connect to Wifi" message. Previously, it stopped here.
After ~2 minutes, I got a notification that the download had started.
Hopefully the install doesn't nuke.

I did a bit of digging around and found a filed called OTAPkg.zip under /cache.
When I delete the file and run another update attempt, it gets replaced with the same contents.
On closer inspection, it's not even a .zip file, it's actually a .xml file with a zip extension.
I'd upload the contents to pastebin, but as I'm a newbie, I can't link externally. I've attached the XML as a .txt instead.
View attachment OTAPkg.txt

http://forum.xda-developers.com/showthread.php?t=1695955
and
http://forum.xda-developers.com/showthread.php?t=1701460

Unable to update Nexus S (I9020a, Rogers[Fido])

Did a factory reset (2.3.6 stock) and tried upgrading to 4.0.4. I get an error about the signature verification failed. Any ideas?

Unbelievable, apparently renaming the zip file to 'Update.zip' prohibits the phone from reading it. So a solution for the future is to leave the name of the update file as it is.

[Q] How to debug OTA update failure?

I got JB OTA update, but it failed after my phone rebooted.
Where do I find the error log? What are the usual troubleshooting steps?
My phone is rooted, but that's the only change I remember making. Can't figure out why update keeps failing.

Couple questions, you didn't install custom recovery did you? I know it says only rooted, but just double checking. Also, did you freeze any apps....any at all?
Sent from my SCH-I535 using xda app-developers app

No custom recovery. No frozen apps.
I haven't had any problems with the previous update (VRLHE).
Is there a log file saved somewhere on the phone with the error message?
kintwofan said:
Couple questions, you didn't install custom recovery did you? I know it says only rooted, but just double checking. Also, did you freeze any apps....any at all?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse

Solved!
Found the solution. After poking around in the file system I found install log in
/cache/recovery/last_log
So, if anyone is having upgrade problems that's the log file you should be looking at for error messages.
Turned out I disabled camera click by renaming the sound file and completely forgot about it :silly:.
In my case this was the error message that pointed to the problem:
"failed to stat "/system/media/audio/ui/camera_click.ogg": No such file or directory"

geneing said:
Found the solution. After poking around in the file system I found install log in
/cache/recovery/last_log
So, if anyone is having upgrade problems that's the log file you should be looking at for error messages.
Turned out I disabled camera click by renaming the sound file and completely forgot about it :silly:.
In my case this was the error message that pointed to the problem:
"failed to stat "/system/media/audio/ui/camera_click.ogg": No such file or directory"
Click to expand...
Click to collapse
I had Odined to stock last night(my phone just seemed off, figured start fresh) so obviously the ota went smooth, but good find! You will probably really help somebody out!
Sent from my SCH-I535 using xda app-developers app

geneing said:
Found the solution. After poking around in the file system I found install log in
/cache/recovery/last_log
So, if anyone is having upgrade problems that's the log file you should be looking at for error messages.
Turned out I disabled camera click by renaming the sound file and completely forgot about it :silly:.
In my case this was the error message that pointed to the problem:
"failed to stat "/system/media/audio/ui/camera_click.ogg": No such file or directory"
Click to expand...
Click to collapse
Thanks this helped me figure out why I wasn't able to get the updates....although it was a for a different error. I had disabled the shutter sound.

geneing said:
Found the solution. After poking around in the file system I found install log in
/cache/recovery/last_log
So, if anyone is having upgrade problems that's the log file you should be looking at for error messages.
Turned out I disabled camera click by renaming the sound file and completely forgot about it :silly:.
In my case this was the error message that pointed to the problem:
"failed to stat "/system/media/audio/ui/camera_click.ogg": No such file or directory"
Click to expand...
Click to collapse
Oh, something silly might be the cause of my issue, as well.
EDIT:
After rooting to view the install_log file contents, it appeared that my install failed because "/system/lib/libjni_emailspellcheck.so" was not on my phone - what a ridiculous error to hold up a major OS upgrade.
I found Incubus' JellyBomb ROM at the VRLHE level and copied libjni_emailspellcheck.so from that to my phone in the proper subdirectory. Re-installed the JellyBean 4.1.1. OTA and everything went fine.
Weatherbug and some other apps are JellyBean-ized, it appears. Cool.
- ooofest

The sneaky bastards at Verizon tried to push the OTA yesterday evening. The phone was in my pocket and it started getting warm. Pulled it out and saw the update failed message. "last_log" showed it couldn't find VzTones.apk. Well, I had deleted that after backing up in TiBackup, but had reinstalled it a week or so ago. Apparently, when ti restored the apk it wound up being named "com.vzw.hs.android.modlite-1.apk", or at least that's my assumption since the icon is the same. I renamed it, but the update failed (dl via wifi this time. Why does it have to download again, by the way?) again because VzTones didn't have the "expected sha1 sums", whatever that means. I gave up and used this method to get the update, root, and unlocked bootloader.
I think I preferred flashing my Moment to this.
Here's a question: Does that 400mb download count against your data plan?