Hotfix to enhance the internal GPS capability: Installation fails - Touch Pro2, Tilt 2 Windows Mobile General

Hi,
when i try to update my TP2 with the hotfix from here http://www.htc.com/de/SupportViewNews.aspx?dl_id=624&news_id=215 I get an error message saying
"ERROR [294] : INVALID VENDER ID"
PS: Contrary to what is stated on the HTC home page I have of course NOT
copied the exe file to the device, but started it from my Vista desktop.
HTC should take more care of their instructions

Refer to this thread:
http://forum.xda-developers.com/showthread.php?t=542699

OMG...
Sorry and thanks.

Related

ERROR [260] After upgrading wtih the "official" wm6

I upgraded my 85' with the "official" wm6 rom and now I cannot go to other roms. The process was solid, meaning I was fully charged, no power loss, and it was synced. I've tried every version of rom available and get the same results. I went through the "brick" thread and I'm affraid I don't quite fit into any category. I can get phone calls and everything works, I just happen to like all of the great ROM's everybody is cooking and want to try them to see which one I favor. I tried using the Hard-SPL and all of the other bootloaders out there and I always get that ERROR [206]. I've tried to restart the machine, and hard reset the 85'. Any good idea's.... Maybe I need to search more? I'll try that.
==============================================================================
UPDATE:
What I should really do is rent a gun, and buy a bullet...
I'm not saying I'm some sort of season veteran of flashing... but I've never had to touch anything after I accept all terms. For some reason, when it came down to the last "Next" form, my phone flashes "Accept" super fast. So what to do?... I push "Yes" soft key fast as I can and it runs like grease lightening... I had to choose SS for the boot loader because it couldn't figure it out... Maybe next time around.
Have you tried to flash a coocked ROM using the microSD card?
Hi,
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?
I did not try to do flash it woth the MicroSD card... I just found out that I could flash it with the MicroSD card about 2 seconds ago. And I wanted to Hard-SPL at the tri-color as a last result in fear of bricking but everything is okay now. As I said before, I've never had to touch my 85' while flashing the rom, it just did it on it's own, but that "official" rom was not about being neglected. And then when I saw it flash something and say "yes", I pushed it and never looked back. It's alllllllllllllllllll good.
I do have one question, is the SSPL preferred over the other choices? Or is there one that is recommended?
Hi joshkrajnak,
How did you solve this problem exactly cos I dont understand what your saying:
http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
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 [260] : CONNECTION
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 [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.
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 [262, 276, 284, 302] : 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.
Click to expand...
Click to collapse
To Clarify: Whenever I went to upgrade my 85' to a different ROM, it wouldn't recognize my bootloader, and then after selecting any of the options, it would give the "ERROR [206]" message and fail miserably with any rom.
What I did to correct it was this: On the "official release" whenever I went to upgrade the ROM, the 85' would show a message at the bottom, the same as any "Notification" would giving me the option to either "confirm" or "dismiss". I did not notice the messages up until it caught my attention out of the corner of my eye on the very last attempt. The messages would quickly appear and disappear, so when the time came and it stated:
Current Rom: 3.25.###.###
Upgrade: 1.##.###
I had to press a confirm notification to continue on or I would get the "206" error message. The quote posted by Binyo is correct, but it does not apply in my situation.
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.
Although that may be true that some applications may interfere with the upgrade process, I had turned off all applications and killed any services during this process.

ERROR 294 while trying to upgrade to WM6

i tried to upgrade to WM6 after installing hard SPL 1.20.
ive got the message:
error 294: invalid vender ID
what can be the problem?
you must use update no id and u can find here.
http://www.sendspace.com/file/878i9b
overwrite the .exe in your folder and try again.
i hope it's usefull. Robert

Live Search problem

i downloaded livesearchWM6.com from the official website and when i loaded it, it gave me an error saying its unexpected, error cannot be displayed then i hit details and it says argumentexception, an error message cannot be displayed because an optional resource assembly containing it cannot be found
at system.IO.path.checkinvalidpathchars()
at system.IO.path.internalcombine()
at system.IO.Directory.getdirectories()
at microsoft.search.mobile.storageobjectbroker.loadindexfrompath()
at microsoft.search.mobile.storageobjectbroker.saveentries()
sorry for the long post, i just didnt know how to explain what was wrong
bump please help
I, too, am getting a LiveSearch error. However, mine was working just fine until I had to reestablish the partnership with my desktop.
Unexpected error in LiveSearch.exe
File or assembly name 'Core,
Version=3.03047.24749,
Culture=neutral, PublicKeyToken=null',
or one of its dependencies, was not found.
I would suggest to uninstall it and then try to reinstall it again and see if this happens again.

Error [294] : invalid vender id - excalibur s620

hello every1
while upgrading the Excalibur i get the following message on the update utility:
Error [294] : invalid vender id
the update utility cannot be used for your smartphone. please check your update utility.
I did run the SDA_ApplicationUnlock & USPL-CIDBYPASS . and procedure completed successfully.
my phone currently shows the following msg when i power it on with a non-accepted sim card 'THE SIM CARD IS NOT VALID.PLEASE INSERT THE CERTIFIED SIM CARD PROVIDER BY YOUR SUBSCRIBED OPERATOR.DEVICE WILL SHUT DOWN IMMEDIATELY'
any insight on this would be greatly appreciated.

List of ERRORs, update firmware

I can't post in developer forum yet....
u 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.
u ERROR [260] : CONNECTION
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.
u ERROR [206] : MEMORY ALLOCATION
u ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
u ERROR [208] : FILE OPEN
u 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.
u ERROR [212] : FILE CREATE
u ERROR [214] : FILE WRITE
u 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.
u 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).
u 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.
u 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.
u ERROR [242] : INVALID LANGUAGE
u ERROR [244] : INVALID MODEL ID
u ERROR [294] : INVALID VENDER ID
u 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.
u ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
u ERROR [262, 276, 284, 302] : 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.
u ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
u 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.
well,thanks man for the sharing
valuable information may be usefull just in case
I always end up with 270 error.

Categories

Resources