Related
Hello,
While flashing the SP-JAS computer freezed on 15% of completion and now the device is stuck in BOOTLOADER MODE, I'm not able to flash it normally, I even tried the SD Method, and it hangs on Checking...
Here's the RUU log file.
20:06:19:875 [msg] : Version : [5.10 - 20060412].
20:06:22:937 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
20:06:27:156 [msg] : Disconnect ActiveSync .... [2]
20:06:27:156 [msg] : Start Get Connect Port.
20:06:27:343 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
20:08:47:984 [err] : BL Get Device Data Error.
20:08:47:984 [msg] : START UnInitialization !
20:08:48:500 [msg] : END UnInitialization !
Here are also some results from the MTTY
USB>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: B, Bootloader Version : 2.05
Built at: Jul 12 2006 15:32:49
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x8
Main Board version=0x4
USB>checkimage
IPL CRC checksum = 0x9352B5E9
SPL CRC checksum = 0x42F889A1
CE CRC checksum = 0x3197DD93
ExtROM is None.
Radio Image CRC checksum = <-- There's no result here and it freezes.
Help appreciated...
Not sure if it will help but have you tried using the latest HTC ROM update ? I had a similar problem on my Dopod and eventually got it back with latest HTC ROM update.
Well actually the latest HTC ROM was installed I wanted to revert back to the Imate rom, while the flashing procedure the computer freezed on 15%...
I'm not able to flash the device anymore, it's stuck in the bootloader....
Breeze has frozen after ROM flash
Please help me!
I have done upgrade MTeoR with rom RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR.
After the upgrade my qtec went shutdown and after this froze and have clear white screen.
I did try left+right soft key+power and selected restore to default factory, but the situation is same, phone don't working
I did try jog wheel+camera+power and ran upgrade, USB on PC detect phone as HTC device, but the ActiveSync don't find device and RUU program don't work and waiting to connect.
The Same problem!
I have the same problem! My PC freezed on 3% and now the device stuck in BOOTLOADER MODE! I tried to update after this, update fails! INVALID VENDOR ID I want to try SD METHOD, but i don't know where to find ROM in .nbf format Please Help...
i also have the same problem.. stuck in bootloader... even though i try installing the original rom it says invalid vender id.....
does nobody know what to do?
When you see "invalid vendor id" ignore this error and start ROMUpgradeUT.exe again without changing anything on your device.
Starting ROMUpgradeUT.exe two times often brings this to a solution.
HTH, MrPhoni
MrPhoni said:
When you see "invalid vendor id" ignore this error and start ROMUpgradeUT.exe again without changing anything on your device.
Starting ROMUpgradeUT.exe two times often brings this to a solution.
HTH, MrPhoni
Click to expand...
Click to collapse
didnt work for me....
Try to re-Flash with the same ROM currently installed or down/upgrade using the same vendor ROM.
eViL D: said:
Try to re-Flash with the same ROM currently installed or down/upgrade using the same vendor ROM.
Click to expand...
Click to collapse
didnt work for me..
Just got my Trinity today, and have successfully unlocked it using pof's unlocker. I unlocked the SIM lock and the CID lock, so it's now SuperCID.
I want to put WM6 on it, the LVSW version. I've downloaded the three files in the sticky post. Before I do it, I want to check that I'm understanding it right, because I'm a bit confused with version numbers.
So...
1) First, I need to HardSPL by running the "ROMUpdateUtility.exe" file from the Hard-SPL.zip file, yeah? I ran this (but didn't flash it) and was confused because the new "Image Version" was 1.20 whereas the Image Version shown in the "current image" bit was 1.24.xxx. Usually, going backwards is bad but I may be misunderstanding.
2) I then need to flash the Radio ROM to 1.41 - why do I need to do this? I guess I run the "ROMUpdateUtility.exe" from the GSM_xxx_xx file, right?
3) Finally, I need to flash WM6 - by running the "ROMUpdateUtility.exe" file from the WM6 zip.
Is that right?
Just tried to flash both the HardSPL and the Radio ROM, and the ROM Update Utility always craps out after I select "Yes" to the security prompt on the Trinity.
"ERROR 246 DEVICE NOT RESPONDING" is displayed in the update utility. Any ideas?
Also, if I go to the bootloader manually (holding down the buttons) the version numbers are:
TRIN100
IPL-0.50
TRIN100
SPL-1.07.0000
But when I let the ROM Update program enter the bootloader, these are shown instead:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
What does it all mean? Very confusing! It won't let it update anyway, when I select "Yes" to the security prompt, the screen goes black, the ROM updater throws up the error 246 and then the Trinity shows the bootloader.
GazChap said:
Just tried to flash both the HardSPL and the Radio ROM, and the ROM Update Utility always craps out after I select "Yes" to the security prompt on the Trinity.
"ERROR 246 DEVICE NOT RESPONDING" is displayed in the update utility. Any ideas?
Also, if I go to the bootloader manually (holding down the buttons) the version numbers are:
TRIN100
IPL-0.50
TRIN100
SPL-1.07.0000
But when I let the ROM Update program enter the bootloader, these are shown instead:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
What does it all mean? Very confusing! It won't let it update anyway, when I select "Yes" to the security prompt, the screen goes black, the ROM updater throws up the error 246 and then the Trinity shows the bootloader.
Click to expand...
Click to collapse
SPL by Des is a one time only SPL called SSPL-TRIN.exe, it's somewhere on this board. Sometimes it's baked into a ROM too ... it fakes the SPL.
HARD SPL stays on your phone .... doesn't need SPL by Des anymore.
Windows needs some time to switch from Windows CE to the bootlader driver. This can cause an error ...... just start the exe file again on the PC.
Another common flash error is with Vista, then you need to overwrite the default driver when you're in the bootloader. The driver is in "VistaRUU.zip"
Relaunch the Hard-SPL, then the radio ROM and after that LVSW or mUn's ROM.
There is a file you extract called EnterBootLoader.exe
I copy this to the Memory card.
Then before I run the update I run this on the memory card.
The phone goes to the boot loader and then once windows has re-detected it I run the update.
This seems to have eliminated all problems I've ever had flash updating.
akirainblack said:
There is a file you extract called EnterBootLoader.exe
I copy this to the Memory card.
Then before I run the update I run this on the memory card.
The phone goes to the boot loader and then once windows has re-detected it I run the update.
This seems to have eliminated all problems I've ever had flash updating.
Click to expand...
Click to collapse
I just tried this, but Windows doesn't seem to want to detect the presence of the device when I do. ActiveSync reports that nothing's connected.
Well I've got the Hard-SPL and Radio ROM to flash - instead of leaving ActiveSync connected I just went into the bootloader manually and did it that way.
But now I'm trying to flash WM6 and it gets up to 8% and then craps out with Error 286 - communication errors.
The device now won't boot past the bootloader
What do I do now?
Bloody hell. It's amazing, it really is.
I had it plugged into my USB hub.
Took it out and plugged it directly into the PC, just on the off-chance that the hub was screwed up.
It's all working fine now, I think!
Typical. Thanks for the assistance anyway guys.
Nps. Glad you got it sorted
Is the USB Hub powered? If not that will cause a ton of problems!
It's supposed to be powered, but I'm starting to think that the power supply might be faulty!
hi guys,
2 questions if i can;
1)What is HardSPL?
2) Why are there 3 steps to getting WM6? why can I not use the "ROMUpdateUtility.exe" file from the WM6 zip straight away?
Thanks a lot!!
Same Problem as GazChap
Hey All,
I was having the exact same problem as GazChap with the same configuration to start out with.
This is what I did:
1)plug in my p3600 to the USB
2)let synchronize, and hopefully finish, otherwise stop it
3)run HARD-SPL; this usually freezes after the first go and stalls in the bootloader
4)run HARD-SPL again; this time it will finish. You will have to turn on your machine again after this.
5)run AX3L ROM 2.0.8.2; this ALSO usually freezes after the first go and stalls in the bootloader
6)run the ROM again; This time its gonna work...
Now it works..
brick time
I loaded the hard spl succesfully. I could not get the radio upgrade to load no matter what I did. My instructions said it was optional, so I went directly to the WM6 rom exe load and it has a perpetual communications error after about 8% even though the WM6 loader says each time that recovery is successful. I have a tricolor screen (bootloader?) on my 3600 which won't respond to anything I have thought of yet. Anything I can do other than pitch it? Help! And thanks in advance.
ok, just want to make it short: (P3600 user)
1. I have WM6.1 ROM (FleNover 3.3 Black edition) installed.
2. When I want to downgrade to WM6 official, after 20% it goes error.
3. Now, it only shows 3 colors.
4. Here is my PDA information in 3 colors:
TRIN100
IPL-1.00
TRIN100 MFG
SPL-1.30.Olipro
5. When I want to upgrade with WM6 official, after my PDA shows the progress bar, it restarted and the update screen shows Error 286.
6. How do I fix it?
thank you very much
When I upgrade rom of CHT9110 by P3600i ROM. I got an error Invalid Vendor ID. And screen now is USB Bootloader. How I can restore to the original rom or is there any rom can upgrade for CHT9110 to support English language
up top......................
up up
up up ...............
I confronted same situation as you before. When i tried to flash my 3600i(HK traditional Chinese version) using "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship.exe" found in forum, my 3600i finished with same error as yours "Invalid Vendor ID" and stayed on 3-color bootloader screen after rebooting. however, It restored to the original rom after I tried to flash my 3600i with upgrading software "D810_GPS_HK_TradChinese.exe" which got from download link appeared on software update in my Htc e-club. flashing "D810_GPS_HK_TradChinese.exe" failed with something like "wrong model" then my 3600i rebooted automatically and restored to the orginal state. I hope my case could do a little help to you.
also found the following from readme.doc in "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship"
8. Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It’s normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.
Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!
sergey.ss said:
Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!
Click to expand...
Click to collapse
Have you tried flashing stock rom which came with your device?
I have tried .nbh file from "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE.zip"
if it possible tell me what exactly should I download and how to use it, I'll try. I'll try everything you advise, because I didn't find solution myself and don't know what esle should I try. first of all where should I start? do I need to perform task29 correctly or do I need to restore HSPL to 1.56 version, or flash a stock rom?
* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.
I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.
iamjohno said:
* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.
Click to expand...
Click to collapse
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
xdmcdmc said:
I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.
Click to expand...
Click to collapse
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...
sergey.ss said:
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...
Click to expand...
Click to collapse
Try using a radio nbh for blackstone.
The original package, contains nbh for the LEO
thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?
sergey.ss said:
thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?
Click to expand...
Click to collapse
Hmmm... I want to know, what .nbh file did you include in the task29 folder you have? Remember, you must to copy a radio ROM to your task29 folder and name it as RUU_signed.nbh, don't copy an OS ROM to task29 as this will give problem.
From the information above, seems you had restore to original SPL? Try flash HSPL or USPL. If you have any problem flashing, you can ask in this thread http://forum.xda-developers.com/showthread.php?t=505377
Good luck, my friend. Cheers.
Agree with philrom: you are an the stock SPL. So, flash HSPL, then you should be fine.
Has this been resolved?
Fallen Spartan said:
Has this been resolved?
Click to expand...
Click to collapse
Yes. Sorry I forgot to post the ending of this story...
I didn't understood about flashing HSPL in formated device... I was really tired of using different ways and flashing different roms... I just took my device to a not official service center (there is no Touch HD for my country). There guys said me that I need to flash a stock rom of my HD birthplace country. They found out that it was shipped from Arab Emirates, than they found a required ROM and flash it. It cost me 50$. Now I'm using my HD as usual.
Thank for the replays!!!
Glad you got it resolved
Thread closed
Phone: HTC Touch Diamond 1
I tried hard reset, soft reset, any kind of reset but nothing. i tried to reflash but it doesn't work, stops at 0%, tried different SPL... any ideas?
eu.florin said:
Phone: HTC Touch Diamond 1
I tried hard reset, soft reset, any kind of reset but nothing. i tried to reflash but it doesn't work, stops at 0%, tried different SPL... any ideas?
Click to expand...
Click to collapse
remove the battery from the device and allow up to 10 minutes
replace the battery and ensure that the device go to bootloader
reflash with an official ROM for your device
Good Luck
thanks for your reply
i removed the battery for a night
the device goes to bootloader, red-green-blue-white has a text:
DIAM100 64M
SPL-1.93.3.000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT 0x32
when I try to flash with an official ROM I receive ERROR [294]: INVALID VENDOR ID
when I try to flash HARD SPL, RADIO or Costum ROM i receive ERROR [262] :UPDATE ERROR
another problem i think is that in flashing process guide I update from Image file NONE to another version like in the picture below
It's there any solution? or my phone needs another motherboard
eu.florin said:
thanks for your reply
i removed the battery for a night
the device goes to bootloader, red-green-blue-white has a text:
DIAM100 64M
SPL-1.93.3.000
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT 0x32
when I try to flash with an official ROM I receive ERROR [294]: INVALID VENDOR ID
when I try to flash HARD SPL, RADIO or Costum ROM i receive ERROR [262] :UPDATE ERROR
another problem i think is that in flashing process guide I update from Image file NONE to another version like in the picture below
It's there any solution? or my phone needs another motherboard
Click to expand...
Click to collapse
What are you using vista or W7 on your computer ??
i tried on xp and win 7
-> 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 [294] : INVALID VENDER ID
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.
already tried the solutions u gave me in the previous post
thank u for your patience but it seems nothing works
hey eu.florin , try to find the official ROMs on http://www.shipped-roms.com/index.php?category=windows mobile&model = Diamond
Good Luck
thank u Hakim Rahman , I finally found the ROM i need (RUU_Diamond_HTC_WWE_EastEurope_2.03.479.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship)