Related
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
Dear All,
I've tried to upgrade to ROM Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship
and unluckly cable loosen and I reset the phone.
Since it's in the middle and can't success enter the Windows Mobile,
but the bootloader was updated to 1.06.
Now I can't flash any ROM either
HER_DopodAsia_1237074_1060010_WWE_SHIP or the new one.
The tools on "imei check" even can't recognize my phone.
Any one can help me on this issue, please?
Thanks in advance.
Try the steps here, let us know the results:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you don't fix it with the proposed solutions attach USB Monitor capture in text format as explained in the bootom of the page.
I have the same issue, and sent it to service, and now I have the phone back and they could not fix it, so got no radio or imei number, so none of the FAQ will work for me.
So I have an expensive paper weight.
Hi,
ME TOO!!
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
I have also tried imei without any joy.
the PDA part of my M3100 still works but the phone is dead. I have been told that if you can get the latest radio installed then you satnd a chance of the phone part working.
We need a hack to get bootloader 1.4 back on the phones.
Please help.
Thanks
My one now is a photo frame which one show "HTC" or "Windows Mobile",
at least your one is a PDA.
There are nothing in "info 2" and so nothing can be flash into it.
Is it possible to have something written CID and IMEI to phone in mtty
and let the flash rom success?
i am in the same situation like yhlee. Pof, i have reply your pm and ready to upload the result file to FTP. where should i upload to?
Thanks
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Thanks.
rnc1688 said:
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
Click to expand...
Click to collapse
This can be fixed by bootloader commands 'set 14 0' and 'task 8', will reboot your device and boot into OS again (but no GSM yet!)
yhlee said:
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Click to expand...
Click to collapse
Upload it to xda-developers ftp:
ftp://xdaupload:[email protected]/Uploads/Hermes/
USER: xdaupload
PASS: xda
POF, file have been uploaded, file name= rnc1688
Thanks
'set 14 0' and 'task 8' didn't work
@rnc1688: It starts the flashing process, but you get a "CID not allow (255)" error because your CID is corrupted and you are in bootloader 1.06.
Is not booting WM5 after "set 14 0" in mtty.exe? If it's not booting WM5 you'll not be able to flash bootloader 1.04 and bypass CID checking.
so i guess my unit is bricked now.
I've upload the file which named yhlee.txt.
However, I'm going to send the unit for service.
Hope they can fix.
Any way to make it show the bootloader screen on start-up
everytime?
"set 14 1" doesn't work after push the RESET button.
Thanks.
@yhlee: U're getting exactly the same error as rnc1688. Device in bootloader 1.06 which has corrupted CID, however you say you can go into OS, so it would be possible for you to downgrade the bootloader so it does not enforce CID checking.
yhlee said:
Any way to make it show the bootloader screen on start-up everytime? "set 14 1" doesn't work after push the RESET button.
Click to expand...
Click to collapse
Try "set 1e 1" and then "set 14 1", you'll boot stright into bootloader.
@rnc1688: If you want to go WM5 try this:
"set 1e 1" and then "set 14 0", you should be able to boot stright into OS.
no luck either
grrr!!!... command "set 14 [0|1]" is working fine in 1.04 here to switch boot into WM5 or boot in bootloader mode... probably different in 1.06??? I don't have a 1.06 now to test
Mine one is just showing "Windows Mobile" but stuck there,
but seems rnc1688 one is a PDA but my one is nothing.
I've sent to distributor for service.
Thanks you pof.
yhlee said:
I've sent to distributor for service.
Click to expand...
Click to collapse
Let me know when they fix it... i'm curious about if they will fix it with 1.06 or they will downgrade to 1.04 first.
I got a correct message back from the service company, and they will not fix a bootloader 1.06 unless the original rom has been release with it, I was told that is HTC policy on this.
Hi all,
I have just bricked my hermes (twice) and I need some help. It's a SoftBank version, flashed with a Dopod ROM (the earliest version I think), with sim and CID unlocked. This is what happened:
0) Unhid and unlocked extended ROM using POF's cab. Restarted, can read/write to the ROM on the device, and via activesync + explorer. Installed programs there, played with it for a couple days. No problems.
1) Played an mp3 file with japanese ID3 tags, in TCPMP. Characters displayed as weird symbols (expected on enlighs rom), so I tried installing LetsJapanNo5.zip to have the characters display correctly. LetsJapanNo5.zip is mentioned here: http://forum.xda-developers.com/archive/index.php/t-281617.html
2) On restart after installing the cab, device freezes on Windows Mobile splash screen. Followed instructions here to fix, and only hard reset works:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem2
NOTE: if I just leave the device frozen on WM5 splash screen, LCD powers off after around 2 minutes (my own config before brickign it, IIRC), and device powers off after another several minutes (my own power-saving config again).
NOTE 2: I have a feeling LetsJapanNo5.zip is the one causing problems. And I probably shouldn't have tried installing it on an English rom.
3) After hardreset, I tried to unhide and unlock the extended ROM again, using fit4cat 2.1b. Unhiding worked no problems, but unlocking doesn't work: the unlock option in fit4cat always stays unticked after saving and restarting the device, and attempts to create a new folder in the extended ROM gives write permission errors. info 2 command in bootloader says the device is still CID unlocked:
HTCS00000000jR*¥HTCE
And the bootloader itself says:
HERM200
IPL-1.01
HERM200
SPL-1.04
4) Unable to unlock extended ROm with fit4cat 2.1b, I reverted back to pof's unlocking cab, which installs OK, but on restart, WM5 freezes at its blue splash screen again.
At this stage, I am able to hard reset again, but the device will always freeze again after I install the extended ROM unlocking cab (not using fit4cat because it still doesn't work).
Any suggestions on what I should do, to unlock the extended ROM, as well as clean up the mess made by installing LetsJapanNo5.zip?
And if a full reflash is the best course, any suggestions on what english ROM to use?
cheers.
After flashing my XDA2 to WM5 3.5a, i've tried merging storage & extended rom to gain memory by following a thread on Airfagev. After doing a hard reset, i found out that my phone is not responding and all i can see are black horizontal lines on the screen w/out backlight. I tried soft resetting it but still it stays the same.
Though i can still put it on bootloader mode, it also wont finish reflashing and an error message appears that goes like this:
ERROR 100: Model ID Error
The ROM image you are trying to use is not designed to work with your Pocket PC.
Is there any way for me to fix this problem? I really need help from anybody who's knowledgeable enough in solving this problem coz' i am new in this field.
Pls. help.
Thanks in advance!
Yoo can use NOID utility for flashing
HimaUpgradeUt_noID.exe
bootloader
Thank you. I can now reflash my device to WM2003 but not to WM5.I think it's because of the bootloader which is v 1.06.Is there any way to change this to v 1.03?
Help pls.
i am following mr vanx guide found here:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=59&Itemid=27
to downgrade my device to SPL1.06 and IPL1.01 using file HERM_SPL1.06_Only_CustomRUU.rar
however, once i flash my device, it lists that I have SPL1.06 and IPL1.00, not 1.01. I have tried the flash using 'SPL-1.04/1.10 - SPL - 1.09 Bootloader' and also 'Force using SSPL' with no luck.I am running a hermes 100 but I still have WM6. i just thought about this, but do i need to downgrade to a signed cingular/att signed ROM before this will work? I need to be running IPL1.01..any help or ideas please?
*edit*
now the device boots and connects toactivesync fine, but when i try to flash a radio rom, WM rom, ipl/spl update (2.10, 1.06 doesnt matter) the device reverts to the tri-color screen after verifying the information on your hermes, but then is not able to update. it is saying that the connnection can be made to my device, is this because of ipl 1.00??? please help!!!
**LATEST**
ok the problem now is that it willnot update anything anymore... as i try the update process the phone goes into the bootloader mode and shows
HERM100
IPL-1.00
HERM100
SPL-1.06
while the computers says 'verifying the information on your device.' I have tried complete packages such as 'RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe', and also packages with seperate ruu wrapper such as what is found in 'Hard-SPL-V7.zip.' I donot know why the update process freezes at this step...please this is really killing me.
chapter 2
moving on... I found the 'fix' for this in the wiki, however when using the 'mtty.exe' file it says to "select USB" from the dialog box but I cannot get an option for anything else except COM 1-4 in the diag box... what do i need to do to enable the USB option???? and yes i disabled activesync like it says obviously.
its like the device cannot be recognized by usb while [the device is] not actually running windows... argh!!!!
Sometimes you need to restart your hermes and than run the mtty.exe.