Related
I'm hoping you folks can help me out. I have tried to upgrade my XDA2 using the Himalaya_WM2003SE_Upgrade but it keeps coming up with:
"Error 150:ROM UPGRADE UTILITY ERROR.
This ROM upgrade utility does not design for your device.
Please get the proper ROM upgrade utility and try again!"
I've got:
FCC ID: NM8HIMALAYAS
IMEI : 351938002885560
Now the unit just gets to the bootloader "SERIAL, v1.06" until I put it in the cradle and it goes to "USB, v1.06". I ran the upgrade following the instructions to the letter but no joy! Am I using the incorrect upgrade utility as the error message says or am I missing something? Any help to restore my XDA2 will be gratefully received!!!
Thanks again!!
which rom are you tryin to upgrade to and provided by who ???
regards
jeetz
I'm basically trying to upgrade my O2 PH10B XDA2 to anything that works! It seems whatever I try, it stays on the bootloader screen with either "Serial or USB" on the display depending whether it's in the cradle or not. I can't do anything with it. I've tried to use the "Himalaya_WM2003SE_Upgrade" utility but as I said, it just tells me that this is not corrrect for my device.
HELP!!
Thanks :roll:
try to reset your device and run himalaya upgrade again
I tried it soooo many times but I still get:
"Error 150:ROM UPGRADE UTILITY ERROR.
This ROM upgrade utility does not design for your device.
Please get the proper ROM upgrade utility and try again!"
I've even tried the O2 Xda_II_172181_Final utility but I still get the same thing. Why does it say it is not designed for my device when I have an O2 Himalaya? If anyone can help I will pledge my undying admiration and possibly even lay down my life for them if required! (sorry, that should have read "wife", not life!) :lol:
glt56 said:
I tried it soooo many times but I still get:
"Error 150:ROM UPGRADE UTILITY ERROR.
This ROM upgrade utility does not design for your device.
Please get the proper ROM upgrade utility and try again!"
I've even tried the O2 Xda_II_172181_Final utility but I still get the same thing. Why does it say it is not designed for my device when I have an O2 Himalaya? If anyone can help I will pledge my undying admiration and possibly even lay down my life for them if required! (sorry, that should have read "wife", not life!) :lol:
Click to expand...
Click to collapse
http://forum.xda-developers.com/viewtopic.php?t=15382&highlight=
try mysterman rom from here dont go for himaupgrade and stuff try to run the setup direct with default radio ....
Success!!!!!
Finally managed to get my XDA2 back to life after some severe CPR & Mouth-to-mouth, and WM2003SEO2UKv2.rar. Thanks for all the suggestions and help.
I also now have a dead M1000.
Where did you get your rom that worked from?
Can you post it please?
Thanks
R
plsssssss help me i also have same problem plsss tell me how u get that pls
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.
Japanese ROM from DoCoMo hTc Z has been uploaded to XDA-Developers FTP and added to the Hermes wiki, you can find it under the Available Original Shipped ROM Versions.
Notes on this ROM:
ROM Version: 1.23.731.2 06/24/06
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
As you can see this is nothing new, but I guess it will be useful for people with this CID to be able to downgrade to bootloader 1.04.
Enjoy
Hi pof,
Thanks for that. I tried this to flash my X01HT after unlocking it with imei-check but with no luck. RUU went successufully till the last screen and I hit the upgrade but it returned an error saying something like this RUU cannot be used for the device. Bootloader is now 1.04 and the device should be SuperCID with imei-check. The only thing I can think of is that I upgraded the radio to your 1.2. Would that screw SuperCID? I appreciate your advice in advance.
Thanks,
harryk
harryk1372: If you are in 1.04 bootloader just run the upgrade utility again without disconnecting the device or start the upgrade in bootloader mode to bypass CID checking.
If it is really SuperCID then you shouldn't have seen this error.
Hi pof,
Thanks very much for getting back to me so quickly.
I ran the upgrade in the bootloader mode. I thought that I don't have to run it twice if the device is already at the SuperCID state and didn't run the update twice. I'll try it again when the device is fully charged as the battery is now down to like 30%.
I'll post the result again when I am done. Thanks again for your prompt advice. You're the man and I really appreciate your efforts taking us thus far in cracking Hermes.
Regards,
harryk
Hi pof,
The device looks like it was not in the SuperCID state and RUU went fine with the second run with no error. However, the upgrade failed when it hit exactly 47% no matter how many times I tried it. Lucky that I did not brick my device but of course it seemed to lack some of the components and it did not even have the Connections setting to set up the Internet access. Also, AutoRun and cabs in the ExtRom didn't take any effect either although the cab files were there.
I decided to flash the TyTN ROM instead and that was successful. That is fine as I only use Japanese occasionally and I didn't really want the Japanese MUI so I will keep it as is. Perhaps I will tweak it a little to be able to use Japanese with loading the Chinese nls, Japanese font, Japanese IME and so forth just like I did with my Universal.
Thanks again.
harryk
Does anyone succeed in flushing Docomo ROM to X01HT?
After unlocking my X01HT,
the annoying message http://forum.xda-developers.com/showthread.php?t=282073&p=1048193
appears again and again, even if I use SB_USIM.
Especially when I write SMS message, it will disturb me over and over.
I try to flush the Docomo ROM to my X01HT and hope to receive your help.
s2k7 said:
Does anyone succeed in flushing Docomo ROM to X01HT?
After unlocking my X01HT,
the annoying message http://forum.xda-developers.com/showthread.php?t=282073&p=1048193
appears again and again, even if I use SB_USIM.
Especially when I write SMS message, it will disturb me over and over.
I try to flush the Docomo ROM to my X01HT and hope to receive your help.
Click to expand...
Click to collapse
fyi...
http://forum.xda-developers.com/showthread.php?t=283177&page=2&highlight=qtotter
I always downgrade my JASJAM using I-Mate shipped ROM
s2k7 said:
Does anyone succeed in flushing Docomo ROM to X01HT?
After unlocking my X01HT,
the annoying message http://forum.xda-developers.com/showthread.php?t=282073&p=1048193
appears again and again, even if I use SB_USIM.
Especially when I write SMS message, it will disturb me over and over.
I try to flush the Docomo ROM to my X01HT and hope to receive your help.
Click to expand...
Click to collapse
i use the docomo rom on my x01ht. it's ok. i have no problem with it at all.
a friend of mine uses a sim-unlocked x01ht (/w the original s/b rom) with sb_usim, but she does not get such a msg at all. do you use a s/b sim?? if yes, i suppsoe you did something wrong...
X01HT Unlocking Problem
I've got this X01HT a few days ago from S/B shop but when I tried unlocking it the result was no good using my cable. I read from other site that X01HT released from December 2006 cannot be unlocked. Please give me some clarifications on this and also, is FLASHING on lower rom version even in english version can resolve the problem...? Your response will so much appreciated.
Thanks in advance.
At the moment it's not possible to unlock X01HT devices wich where bought after 12/1/2006 and have bootloader version 1.09 and RadioROM version 1.14.0.10! Please be patient.
To the experts, I need some advice. I intend to get a X01HT, already unlocked and flashed with the dopod 838 pro firmware. However, I intend to flash back the Japanese shipped rom :
RUU_HER_DoCoMo_1.23.731.2_1.06.00.10_JPN_SHIP.zip
What are the requirements esp where :
Bootloader (SPL)
Latest Radio Bootloader (HTC_BOOT)
Or since its unlocked, do I just go to the bootloader mode and flash direct? Any side effects if I do so, since its changing from an english rom of another clone (Dopod 838 pro, WM6)?
I am not even sure if the RUU_HER_DoCoMo_1.23.731.2_1.06.00.10_JPN_SHIP.zip rom is WM5/6. Please advice, thanks..
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 !!
Hey guys.
Yes, I'm new here, but not new to phones or computers by any means - trust me.
In any case, what happened was I downloaded the XDA Live version of Windows Mobile 6 for my Hermes (originally Rogers branded) and installed it.
Then, I discovered the actual forum here, and saw Schaps' version of WM6 pro and I want that badly. Regardless of which version I'm trying to upgrade to, I get the same issue.
Here it is:
When I connect the phone normally with ActiveSync and try to upgrade to Schaps' ROM (or Dutty's, or the official one, or the T-Mobile one, or the Qtek one, anything), I get a 260 error saying that my USB cable isn't properly connected. Now I've seen and tried the fixes for that error with no luck. The other error I occasionally get is one saying that my device code isn't correct or something or other. And another one is that my image file is corrupt and that I should check my update utility.
What do I do?
ANY HELP would be greatly appreciated!
Thanks in advance!
P.S. My bootloader version is 1.11 (I think) as per the following screen during bootloader:
HERM200
IPL-1.01
(The following part is in yellow below the above part)
HERM200
IPL-1.11
I had the same problem.
I then upgraded the boot loader with hard-SPL:
http://forum.xda-developers.com/showthread.php?t=296722
Now it's working fine and I can load any ROM.
Cheers
Pat
I successfully upgraded to SPL-1.10, with the same result (no change).
I'm really unsure of what's going on with this...but I really need to upgrade to Schaps' TouchFLO ROM - and should be able to easily...
When you upgrade the rom, chose hard-spl (safe).
Good luck
Patric