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.

Problem with MMtaskmanager

Hi,
I just uninstalled MM taskmanager, and everytime I boot up my device I get an error say "File 'MMTaskManagerHook' could not open.", how do i fix this? tried a search in registry for MMtaskmanager, and could only find a .lnk to it also tried a reg-cleaner.. how do I remove this annoying thing?

Check in Windows\Startup

Futher information... by deleting 'MMTaskManagerHook' , you only delete the popup error window, not the actual program.

p00ltergeist said:
Futher information... by deleting 'MMTaskManagerHook' , you only delete the popup error window, not the actual program.
Click to expand...
Click to collapse
He did say he uninstalled it!

ai6908 said:
He did say he uninstalled it!
Click to expand...
Click to collapse
oops, my fault .

MobclickAgent and umeng.com

Have something on my tablet that appears to be collecting location and device data and uploading it to umeng.com.
How do I make it stop?
EDIT: Apparently File Expert is the culprit.

I see this in a log file. How did you determine the application which called it?

qu1nn said:
I see this in a log file. How did you determine the application which called it?
Click to expand...
Click to collapse
in logcat the number between ( ) is the pid of the process, you can check to which application belongs in ddms or a ps from console

[Q] Bugs in the Linux version of "Root MANY ANDROID!" v31 script

Sorry if I have to put my bug-report here but:
1) I tried to reply in the appropriate thread (http://forum.xda-developers.com/showthread.php?t=1886460) but I receive such message
stragnagn, you do not have permission to access this page. This could be due to one of several reasons:
Click to expand...
Click to collapse
2) I tried to send a PM to Bin4ry but the system replies:
Bin4ry has chosen not to receive private messages or may not be allowed to receive private messages. Therefore you may not send your message to him/her.
Click to expand...
Click to collapse
Here comes the bug report.
There are some errors in your linux script:
1) lines 218, 221, 240, 243, 317, 326, 361, 385: command "wait" should be replaced with "sleep"; on Linux, "wait" is used to monitor processes state changes;
2) line 229: "stuff\RootMe.tar" should be "stuff/RootMe.tar";
3) line 124: same as above "stuff\busybox" -> "stuff/busybox"
4) line 388: "stuff\su" -> "stuff/su"
There were some other typos but have to find them again

Someone could answer me please?

[APP] [ROOT] [4.0+] Andy Log: Spare Yourself Logging Scenarios

Description:
Andy Log is a small tool that dumps necessary logs for bug reporting without hassle.
Just choose what you'd like to include in your log file and click on LOG.
Supported (so far):
1. Logcat
2. Buildprop
3. CPU info
4. Sysctl
5. Kmsg
6. Last kmsg
7. Dmesg
8. Uptime
Logs are saved to /{MAIN STORAGE}/Android/data/{PACKAGE NAME}/Logs folder.
Download:
Andy Log (ROOT)

Change log
Reserved for change log:
v2.0
Fixed crashes on Android 6+
v1.4
Android N support (please work)
Fixed log folder chooser on Android 6
v1.3
Added:
Last crash option, useful for extracting the minimum required data for crash reporting.
(PRO) Logcat:
radio & events buffers.
Formating.
Filtering ( tag:level ex: AndroidRuntime:E )
v1.2
Fixed:
1. Problem with Italian date format.
Added:
1. Confirm and show log files' names before clearing them.
2. Share log option.
3. An option to change default logs folder.
v1.1
Fixed:
1. CLEAR LOGS bug.
2. Force close when no option is checked.
3. Force close during dumping logs due to DOCUMENTS field being undeclared in some devices' framework.
v1.0
Initial release.

@deeplyyoung try out this app bro , its just awesome. @Bassel Bakr good handy app which saves time. It also helps a lot of noobs around here to provide proper logs

Great work. :good:

Great!!! This is the most awaited app for newbies.

Nice, I'll have to try this out. I currently have SysLog & Logcat Extreme installed for their various functions. This might be a replacement for SysLog.
EDIT: Trying it now, it's been sitting on "Dumping KMSG" for about 5 minutes. I checked them all, by the way. Shall I use one of the aforementioned apps I use to record a logcat while it happens? Seems a bit ironic, I know.

yochananmarqos said:
Nice, I'll have to try this out. I currently have SysLog & Logcat Extreme installed for their various functions. This might be a replacement for SysLog.
EDIT: Trying it now, it's been sitting on "Dumping KMSG" for about 5 minutes. I checked them all, by the way. Shall I use one of the aforementioned apps I use to record a logcat while it happens? Seems a bit ironic, I know.
Click to expand...
Click to collapse
I'd be grateful if you did. ?
I'll make sure next update less prone to this problem.

Bassel Bakr said:
I'd be grateful if you did. ?
I'll make sure next update less prone to this problem.
Click to expand...
Click to collapse
I let it sit for about 5 minutes, so it's almost 10 thousand lines.
https://dl.dropboxusercontent.com/u/67194527/Log_2014-10-19_23-46-59.txt

Great app. Command lines made handy. Now users can easily submit logs to respective developers and contribute in smoother development :good:

@Bassel Bakr Could you add Dmesg feature?

Great, thank you, logs have always baffled me - this has made them much easier for me to understand.
Problem I'm facing is that I can't find the logs in the file path /0/android/data/com.bassel.andylog/files/documents/.....
When I get to documents there is nothing in that file.
I can see them when I first take the log and open it though?

Great app, just one thing. After taking a Logcat the log says “
Unable to open log device '/dev/log/main': No such file or directory ”. All other logs seem to work fine.

Bassel Bakr said:
Description:
Andy Log is a small tool that dumps necessary logs for bug reporting without hassle.
Just choose what you'd like to include in your log file and click on LOG.
Supported (so far):
1. Logcat
2. Buildprop
3. CPU info
4. Sysctl
5. Kmsg
6. Last kmsg
7. Uptime
Logs are saved to /{MAIN STORAGE}/Android/data/{PACKAGE NAME}/Documents folder.
Download:
Andy Log (ROOT)
Click to expand...
Click to collapse
I couldn't find this app on F-Droid. Is there a github repo or other link to the source?

@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.

iko11 said:
@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.
Click to expand...
Click to collapse
+1
I was thinking the exact same thing

Nice!
Cool App. Could You please include radio log dump (adb logcat -b radio -v time -d)?

filters possible for specific app?

Thanks everyone for your feedback. ?
New update v1.1 check second post change log.
yochananmarqos said:
I let it sit for about 5 minutes, so it's almost 10 thousand lines.
https://dl.dropboxusercontent.com/u/67194527/Log_2014-10-19_23-46-59.txt
Click to expand...
Click to collapse
Check v1.1
Al Arsyadi said:
@Bassel Bakr Could you add Dmesg feature?
Click to expand...
Click to collapse
It's already there but i forgot to include it in the description, sorry. ?
Jimsilver73 said:
Great, thank you, logs have always baffled me - this has made them much easier for me to understand.
Problem I'm facing is that I can't find the logs in the file path /0/android/data/com.bassel.andylog/files/documents/.....
When I get to documents there is nothing in that file.
I can see them when I first take the log and open it though?
Click to expand...
Click to collapse
Strange! Log file can't be opened unless it is already there! ?
Anyway, I'll look into it. ?
p1eter said:
Great app, just one thing. After taking a Logcat the log says “
Unable to open log device '/dev/log/main': No such file or directory ”. All other logs seem to work fine.
Click to expand...
Click to collapse
Do you get the same thing if you executed logcat command in a terminal emulator?
MiyagiSan said:
I couldn't find this app on F-Droid. Is there a github repo or other link to the source?
Click to expand...
Click to collapse
No, it's closed source.
iko11 said:
@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.
ArdnoS75 said:
Cool App. Could You please include radio log dump (adb logcat -b radio -v time -d)?
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.
starbase64 said:
filters possible for specific app?
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.

Bassel Bakr said:
Thanks everyone for your feedback. ?
New update v1.1 check second post change log.
Check v1.1
Click to expand...
Click to collapse
It successfully saves the logs now. However, I noticed it saves them all to one file when selecting multiple. Also, if different logs are chosen using the default filename choice, there's no way to tell which one is which without opening them. Would it be possible to automatically generate the first part of the filename based on the type of log? i.e., kmsg--(Date)--(Time).txt, etc? Thanks!

Bassel Bakr said:
Do you get the same thing if you executed logcat command in a terminal emulator?
Click to expand...
Click to collapse
Logcat command gives me “Unable to open log device '/dev/log/main': No such file or directory ”
When I tried to create the folders /log/main terminal returned “logcat read: Is a directory”