I use the mtty.exe backup rom to sd card and restore to device, ok,no problem....
But How can I restore the nbf( download from ftp.xda-developer) file to device...
I try lnb and l command, all report error message:
Fail tosynchronize with the host(1)
Why? what means this error message?
My device is Falcon ( WM2003+CDMA2000) .
"HTC Integrated Re-Flash Utility for bootloader Version:1.19 Falcon DVT version:1.06"
i get the message on my hx4700 and i can't work out why. when i use the lnb command with the file that has been modified (.nb0) it says "this application only deal with absolutely image file"... i click ok then it fails to synchronize with host(1)???
When i try the origional (.nbf) same file size... everything fine but the hx4700 does not boot it stays on the HP booting screen, nothing happens. (it says 2.01 at the bottom)
Hi,
I tried to upgrade my MDAc with the rom from TMobile.
During the upgrade my computer asked for this file "wceusbsh.sys".
At that point the upgrade stopped.
No i only see "USB" and "v1.00" on my screen.
The charger led is red.
When trying to upgrade again, i get ether this message:
Error 120, country id error
or
err no device
I located the file "wceusbsh.sys" but still.
After "checking the information on your device" i get the error.
"Error 120, country id error"
How can i solve this problem.
Greg
You're stuck in bootloader. Did you try to upgrade to an other language?
You can try to hard-reset your device 'power & soft-reset' at the same time to boot your magician.
If it doesn't boot, kick it back in bootloader 'camera & power & soft-reset' at the same time for several seconds, till screen turns black & read 'serial v1.00'. When connected to usb it reads 'usb v1.00'
Now get maupgradeut_noid.exe from the ftp. Unzip your shipped-rom file you downloaded from TMO. Put the maupgradeut_noid.exe in the same folder as the unzipped files like maupgradeut.exe, enterbl.exe etc. Then execute maupgradeut_noid.exe instead of maupgradeut.exe this will give the error 120 once more. Just exit & execute it again, now it should proceed upgrading.
Cheers, M
=(
Same problem! Trying to use no id upgrade . I hope it will solve my problem.
P.S. DO NOT upgrade ROM when batt is lo =)
while trying to upgrade with UNI_TMUK_130114_130232_11003_WWE_BL101_Ship giving erro 113: also tryed with JASJAR_WWE_11353_137_10301 and also with UNI_CDL_001_13076_164_10900_A2DP_MSFP_WWE_FINAL
The error is same. What could be the problem?.Now it struct in the boot mode (serial on display)
Also found this instruction in another thread "Now connect woth USB cable and open mtty utility" what the mtty utility?
i had the same problem..
i also read somewhere on this forum
that i could be linked to the bootloader version..
I have 1.01 and it should be 0.64 or something or maybe 1.00.
i dont know for certain..
I almost ****ed my mda pro whith the official Tmobile update(NL)
crap i want to update my machine
but now iam afraid to break my new toy
i had the same problem.. but
Code:
SERIAL" version 1.2
and
Code:
ERROR 112: CE ROM UPDATE ERROR
please help
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.
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.