So, I attempted to upgrade to 1.72 today and during the process, it failed and ask me to re-run the setup. But, I can't since all I get on the I-Mate screen is Serial v1.06. Once docked, it shows USB v1.06. ActiveSync will no longer find it.
Please someone point me to the right direction. Any help will be appreciated. I do own a SD card and can fix/upgrade this way if possible.
First one that can help me get me back up - hopefully to the latest Imate's firmware 1.72 and its own bootloader, etc - I will send you $10 paypal for your time. Sorry I can not give more since this unit got me broke!
Thanks all!
I had this problem and was able to run the upgrade to 1.66 without an issue. Just try docking and starting the RUU. It didn't require ActiveSync to see it for mine to run. When I docked it, it had the "bootloader" message on the screen. Try that and let us know how it goes.
http://forum.xda-developers.com/viewtopic.php?t=8606
http://forum.xda-developers.com/viewtopic.php?t=9047
Thanks all! Dadarkmcse, it worked with your instructions... strange part was, it didn't work on my work computer but i was able to upgrade on my laptop. All is well and everything is up and running again!
Send me a PM with your paypal ID... thanks!
Related
i was doing something while trying to update - basically im stuck with a phone that dont boot and has 2 operations
Serial - v1.06 [not connect to cradle]
Usb - v1.06 [connected to cradle]
i have no idea what that mean, if some one could help me, it dosn't connect with active sync.. but you new that.
Take a look at my post here. It may help you.
nah mate its v1.06
i head that i can load a new/rom from sd/mmc cause i can't connect it to active sync but the usb in my pc picks it up i need to find out what com..
anyone encounted and got this problem sorted please help
Version 1.06 of the bootloader will not allow you to downgrade to a ROM version less than 1.66. However, you should be able to re-install your original version or later. Just reset your device, put it in the cradle and run the upgrade. Activesync is not needed, as the upgrade process looks after its own connection. It is still worth following my post in order to avoid future problems.
Dear friends
I was tring to upgrade my iMate Pocket PC also know as Himalaya with windows2003 SE , while upgrading I faced problems, the upgarde failed and now I am just getting no display and OS too. The only message displayed is
Serial
v1.03
nothing is working please help
bye with regrads,
your unit is still okay; even better that the usb version is showing on the screen. it's simply stuck on bootloader mode. what kind of problems did you encounter resulting in the failed upgrade?
one suggestion i can give before you downgrade is to try and proceed with the upgrade to se. put your unit back on the cradle but don't expect activesync to "recognize" the device. just put it back on the cradle and rerun the upgrade to se.
same thing happened when i upgraded but to wm2005. the screen showed error and the only thing on the screen was the usb version. i simply cradled back the unit and ran the upgrade. worked.
cheers
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
oh, it appears that you have the "wrong country" id issue. i'm not entirely sure as to how to avoid this but i believe it has something to do with the correct rom version (guys, correct me if i'm wrong). where did you get the rom you used for upgrading to se? downgrading might be the only trick if there is no rom for saudi-based users...but if any chaps presently living there and were successful in upgrading their units perhaps you could share the rom version/s you used?
cheers
yasirirfan said:
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
Click to expand...
Click to collapse
To overcome the Country ID Error, first you need to install this tool...
ftp://xda:[email protected]/Tools/ER2003Edit_1_4_26.zip
Open the ROM file you want to upgrade, then change the appropriate 'Operator ID' code, after this click 'Save ROM image'.
Upgrade ur device. You will no longer face the error message.
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 !!
I will paypal someone 50.00 if they can help me revive my dead 8525.
Thanks
whoah....talk about a lurker.
But if you want us to help. we must know the systems
It is an 8525 (Cingular)
I did Pof's upgrade to unlock it. I guess it did not take. (I did not know it was still 1.06) Did the upgrade to unlock and then I tried the following update:
Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship.exe
Now when it boots it I get a background of Rainbow-like noise then the windows mobile screen comes up and stays there. I have tried doin the various updates (Cingular ones) and always get the Vendor ID Error.
Ask any other questions anyone has.
Thanks
Can you put the device into bootloader mode by pressing 'Ok' & 'Power Off' buttons together and resetting the device??
you should try to re-install the cingular 1.34 rom...if you get the vendor id error, run it again ...see the wiki regarding vendor id error
I can go into bootloader. I have done the 1.34 but, it says Invalid Vendor ID. I do it again. (Like the Wiki says but same thing happens).
No one has any ideas?
See if you get the same error with the I-Mate 1.20 ROm.
Have you tried leaving it in bootloader mode and updating it with a TMOBILE rom??? i noticed on your profile that your with TMOBILE... try one of the JASJAM roms....
i am gonna go on a limb here. maybe try to run the step listed to downgrade the bootloader in this thread http://forum.xda-developers.com/showthread.php?t=284401 maybe it will work from boot loader. can't hurt to give it a shot...
I'm Cooking a special cake for you
Hi
I'm cooking a new special ROM edition to you right now, please send me an email with the subject (CAKE) and I'll return you the link for the ROM Upgrade ,I hope it fix your problem
my email is [email protected]
SORRY,,Problems faced, I can't finish this
I sent you the email. Yell back when you have it.
Thanks
Are you in Illinois by chance?
Nope, in Dallas, TX.
Hi,
I've had a good search and can't find any info and have been pointed in this direction for advise.
I've got a spv m3100 and wanted to upgrade to black 3.0.1. I've followed the details given by MrVanx and installed hardSpl 2.10.Olipro first. I checked that this has installed using the ok, start and reset combo. (the installation did seem to be quick thoughm took about 2 secs from the screen on the phone changing to install being complete).
Then wanted to install the latest radio version and this is where the problems started, I ran the .exe making sure the other file was located in the correct directory and that the phone was sync'ed. I got a message saying that could'nt contact the phone and then the following message
Error, unknown version! you should pick sspl
This also happened when trying to install black 3.0.1.
If anyone could help I would really appreciate it. I bought the handset from Ebay and have unlocked it and installed hardspl 2.10 and thats it.
I also want to change the flash load screen to get rid of the orange display as I will be using O2 sim.
Once again, I thnak you in advance for any help.
James
You need to choose force using sspl, you will be ok as you have hardspl 2.10 installed so you should not brick it as you have some protection, it is just that autodetect is not recognising the rom version already installed. Try the rom upgrade first. You need to refer to mrvanx guide as this explains how to change your splash screen to a custom version, post back if all was ok
EDIT:- Black 3.5 is now available!
jamesx10 said:
Hi,
I've had a good search and can't find any info and have been pointed in this direction for advise.
I've got a spv m3100 and wanted to upgrade to black 3.0.1. I've followed the details given by MrVanx and installed hardSpl 2.10.Olipro first. I checked that this has installed using the ok, start and reset combo. (the installation did seem to be quick thoughm took about 2 secs from the screen on the phone changing to install being complete).
Then wanted to install the latest radio version and this is where the problems started, I ran the .exe making sure the other file was located in the correct directory and that the phone was sync'ed. I got a message saying that could'nt contact the phone and then the following message
Error, unknown version! you should pick sspl
This also happened when trying to install black 3.0.1.
If anyone could help I would really appreciate it. I bought the handset from Ebay and have unlocked it and installed hardspl 2.10 and thats it.
I also want to change the flash load screen to get rid of the orange display as I will be using O2 sim.
Once again, I thnak you in advance for any help.
James
Click to expand...
Click to collapse
Thanks BOZ.
I appreciate your response, So I should attempt the black ROM upgrade before the Radio using force SPLL?
I won't now be able to try this until at least next week so I'll have to wait before I can report if all works. Thanks again for your advise. Its all new to me and I'm learning from helpful people like yourself. I've been really lucky that I've found a couple of forums with very helpful members that are happy to advise and assist.
Thanks Again.
jamesx10 said:
Thanks BOZ.
I appreciate your response, So I should attempt the black ROM upgrade before the Radio using force SPLL?
I won't now be able to try this until at least next week so I'll have to wait before I can report if all works. Thanks again for your advise. Its all new to me and I'm learning from helpful people like yourself. I've been really lucky that I've found a couple of forums with very helpful members that are happy to advise and assist.
Thanks Again.
Click to expand...
Click to collapse
You've got it, cheers boz.
If its any help - I had the exact same problem with "unknown version" error. Before I upgraded, I did a hard reset on the M3100 - not necessary I know but I felt happier.
As I had already installed the HardSPL 2.10 Olipro - I simply chose the option:
SPL-2.02/2.10 New Bootloader (rather than 'AutoDetect')
on the RUUWrapper - Hermes ROM Upgrade opening screen and upgraded as per mrvanx instructions (as this offered good protection from bricking my phone)
Upgrade went fine and its fast and so far stable.
Incidentally, I didn't change the radio version, as by all accounts 1.38 is a better version.