Dear Sirs,
I'm writing to seek your help in upgrading my Device (Imate) from Imate Rom to T-Mobile Rom My device info. is as follows.
Rom Version :1.66.00WWE
Rom Date :02/20/04
Radio Version :1.10.00
Protocol Version :1337.18
ExtRom Verision :1.66.167
I have the T-Mobile Softwere but everytime I tried it, I recieve a Msg. stating (Country Code Error).
Ahmed Al Awadhi
Bahrain
If the ROM is for a different country based or network based device, it will fail a country check as you run the setup program.
The way around it is not for the faint hearted, as it involves running the update to unpack the files, using a command line tool you have to download to unlock the individual ROM's, then setting the country code for the ROMs using the same command line tool, then re-packing them again with the same tool, before continuing with the install.
Not an easy process for first time users, and also of course, if you do this and then decide you don't like the new ROM, you will need to go through all this all over again to get your old ROM back on, as it will then of course be set for the wrong country as it were...
I-Mate Upgrade Disaster
Dear Sirs,
I highly appreciate your promt reply, yet again I think I have to do it as ever since I did the upgrade to the Latest I-Mate club posting & my problem started as every day I have to (Hard reset) the Device as everytime it goes Off, it does not switch On again & I end up re-installing all the Programs all over from scratch!
I would be greatfull if u could put down the process in steps so I can carry on.
Sincerly yours,
Ahmed AlAwadhi
Bahrain
http://forum.xda-developers.com/viewtopic.php?t=8205
here are the steps for all himalaya devices upgrade
Highly Appreciated...
Ahmed Al Awadhi
Related
my first post and contribution.. hopefully it would be alot of help to other people..
this is the official IMATE 1.72 ROM...except that it was encoded to work with O2 XDA2 units
added the O2 splash screen to retain the O2 bootup image -just load O2.cab into your XDA2
the upgrade utility shouldnt show you any more country ID error for O2 XDA2 units.. if there are problems.. holler me ASAP!!
feedbacks would be nice, coz i would like to make upgrades for other Network providers as well..
Thanks for that.
Can you show me a step by step guide on how to upgrade O2 xda 2 1.60.WWE version to this?
Thanks again.
ok... im not an expert yet, coz i just had my XDA2 for a week, but i do enjoy tweaking and playing with it.. besides, the knowledge i gain thru reading this forum is more than enough..
ok.. here goes..
1. create a full BACKUP your XDA2.. (but i dunno if this is helpful should you fail to upgrade your ROM)
2. download the above file and extract it.
3. you should see it extract 7 files.
4. put your xda2 in the cradle connected to the PC
5. run HimaUpgradeUt.exe
6. wait around 30-60 mins. then follow the procedure as shown on your computer. (a hard reset would be required)
7. after the upgrade is done, you should see the IMATE screen upon booting up (instead of the O2 bubble screen) if you wanne be extra sure, check your XDA2 version.if everything is ok, then you should have upgraded it correctly
8. if you want to revert to the old O2 splash screen during bootup, then copy O2.cab to your XDA2 and run it there. Do a soft reset, and voila, it should be back to the old O2 bootscreen.
I suggest that you contact your NETWORK PROVIDER because you will need to manually configure GPRS, MMS, and INTERNET settings on your xda2 after doing the upgrade.
WARNING: i wont be held responsible or liable for failed upgrade of your unit. Please understand that by agreeing to upgrade your XDA2, you are taking full responsibility of whatever untoward incidents that may occur to your XDA2. Flashing the rom might lead to DATA LOSS, SYSTEM MALFUNCTION, and even DEVICE MALFUNCTION.
but.. the rewards of upgrading it is sweet!
Many thanks for all of these description.
BTW, how do you feel the upgrade?
What you really get from this?
Can you share with us?
Thanks again.
Cheers mate.
i dunno, im just a week old newbie in using XDA2 :wink:
i just enjoy tweaking the XDA..so far, no problems here.
My xda2 currently is 1.66wwe. after upgrade to 1.72wwe, what's the different between it? anything increase? sorry because i'm a new bird
did a lil research.. so far, came to this...
The 1.72 ROM eliminates the majority of problems from the 1.66 ROM such as:
Increased battery drain
Device slows down
Bluetooth GPS devices don't work, even with Pocket Bluetooth Tools
Can it be downgraded back to O2 xda2 1.60WWE Rom?
Many thanks.
i doubt that it can be downgraded... i havent personally tried to downgrade my ROM to a lower version.. but there are other threads related to this, and they claim that when they tried downgrading their ROMS, their XDA2 died....
you can try searching for other topics if there are information about downgrading... .so far, i dont have any problems with my 1.72 ROM...
except that there is no running program application which enables me to switch off any running program in the background.. but i easily remedied it by downloading TASKMANAGER.... its quite the same with running programs...other than that, so far, so good.
Error 121 Language ID Error
Hi,
after running HimaUpgradeUt.exe I get the message:
Error 121 Language ID Error (N-2-1-0-1), the ROM image that you are trying to use is not designed to work with your Pocket PC.
I ran ERedit2003 Version 1.2.20 and opened the file ms_.nbf using the password 0x20040305. I saved the file with the different language settings WWE, ENG and GER. Always the problem remains the same.
My XDA2 currently has ROM 1.66.01GER.
Thanks for help.
try to change the operator name , too! or use other hymalaya upgrade files, from other roms!
Re: Error 121 Language ID Error
GentleMan said:
Hi,
after running HimaUpgradeUt.exe I get the message:
Error 121 Language ID Error (N-2-1-0-1), the ROM image that you are trying to use is not designed to work with your Pocket PC.
I ran ERedit2003 Version 1.2.20 and opened the file ms_.nbf using the password 0x20040305. I saved the file with the different language settings WWE, ENG and GER. Always the problem remains the same.
My XDA2 currently has ROM 1.66.01GER.
Thanks for help.
Click to expand...
Click to collapse
hi, i tried encoding with it again.. please download it, replace the other files and try if it still gives you errors or not. thanks... ill be waiting for your feedback
Re: Error 121 Language ID Error > Error 120
Waxx said:
hi, i tried encoding with it again.. please download it, replace the other files and try if it still gives you errors or not. thanks... ill be waiting for your feedback
Click to expand...
Click to collapse
Hi,
Thanks. But now I get the message:
Error 120 Language ID Error ( N-1-8-1-8 ), the ROM image that you are trying to use is not designed to work with your Pocket PC. I tried with settings O2 WWE, O2 GER and O2 ENG.
When specifying CDL instead of O2 the error code changes to Error 120 Language ID Error ( N-1-8-8-8 ).
So the problem remains the same
Thanks for help.
Help for beginners: upgrading O2 Xda II to ROM 1.72
New to Forum-sorry to be slow on the uptake. I am trying to undersand how to upgrade O2 Xda II (ExROM 160.50) to ROM 1.72 without losing the machine. Waxx says you need to reconfigure the ISP settings (I assume because they are lost in the upgrade). I cannot find O2 settings for GPRS Interenet and MMS on the net. Talking to O2 is a waste of time.
Does anyone have a step by step description that results in ROM 1.72/Radio 1.18 (or lower if 1.18 still in beta) working on O2 Xda II?
Has anyone reported doing it sucessfully. Have non recoverable failures been reported?
RamyG
Just copy the attached CAB file across to say, My Documents on your XDA, and run it via FileManager.
It will customise your O2 XDA II with all the correct settings.
Once it has done that (and you've tested it works), just uninstall the O2 Active bit and your settings will remain (well they did on mine)
BTW - I upgraded to the new ROM, and have had no problems at all ! Very sweet
Mark
Thnx Mark, just to make sure before I jump in: the steps are:
(1) upgrade to 1.72 using Waxx's attachement (is that the file you used?) (2) follow the procedure you described and I will get O2 customised Xda II (same as where I started) but with ROM1.72 and later Radio Stack. Right?
2 questions:
(a) are the GPRS setting for MOBILE WEB (post paid)
(b) what benefits should I expect from the upgrade? (other than the satisfaction that it succeeded, l if it works?
thnx
RamyG
Yep I used the attachment from Waxx ...
The procedure you mentioned is correct ... I did have a few heart stopping moments after the upgrade because (like you) I couldn't find the necessary settings for GPRS etc .. but the O2 cab file re-installs everything back to what it should be for the UK.
You are prompted to choose relevant settings - in this case you get a choice from either post-paid (MobileWeb) or PrePay ...
As for benefits, people are reporting better bluetooth support, and better battery life. Only upgraded mine yesterday, so can't comment on either yet !
HTH
Mark
Has anyone else had problems charging overnight with the ROM version?
Got Error 120: Country ID error N-8-1-1-1
Hi all,
I am new member here. I did upgrade to ROM 1.72WWE and seems working fine. Because the PDA is idle, I try to roll back to ROM 1.60.44 eng. and got the country id error N-8-1-1-1. I tried to set the regional to English (UK) and English (US) but failed. Any comment? My XDAII is bought from Asia-HK. Thanks a lot.
Chris
Mark thnx for your help. For all those undecided souls I can report that Waxx's ROM 172 upgrade works fine for O2 Xda II. (BTW: it takes 3 times as long to upgrade as they say it does - it's 30 min for each of ROM ExROM and Radio modules).
Mark, O2.cab did not work as exepcted for some reason. When I ran it, it simple created a text file with O2 network config info and did not actually configure the Xda II. The info was correct and a manual config worked first time. Puzzled, I ran the O2 cab again but from another directory. This time I got the O2 spiral (I may have gotten the network configed again I can't know as I had previously configured it manually . The upgrade did lose the O2 dialer screen and reverted to the iMATE one. This is trivial. the Net is full of free attractive skins. e.g http://sourceforge.net/projects/pocketpc-apps/
Mark Peters- I thank you again.
RamyG
IMPORTANT: Updated 28th September - I now know that if you have bootloader v1.06 on your XDA II, you cannot downgrade your ROM (at the moment). We will see if we can find a way round this but cannot promise anything.
Hi everyone!
Just wanted to share the experiences/conclusions with upgrading my XDA II ROM with you all.
I have split this into two posts for ease of reading and clarity. This post is the first of the two and contains the background and conclusions. The next post contains the solution (hopefully) and can be found here:
Fix and prevent ROM upgrade/downgrade Country ID errors
So the impatient ones amongst you can skip straight to it if you wish , although it is best to read this post first.
Background
Some months ago, I bought my XDA II which had the 1.03 USA ROM in it and shortly afterwards, successfully upgraded it to the latest official release from O2 (1.60.50WWE), using their supplied executable package Xda_II_Upgrade_v16050.exe obtained from here.
Last week I upgraded to the i-mate 1.72.00WWE version using the .nbf files and HimaUpgradeUt utilities extracted from the RUU172126WWE_imate.exe executable supplied in this post.
I configured the .nbf files for operator O2 and language WWE using softworkz ER2003Edit tool obtained from here.
The upgrade went smoothly enough - all seemed well, so last week-end, fired up by this success, my friend came over (merlin_uk on this forum) and wanted to upgrade his XDA II to the same version, but containing the 1.17.00 radio, using the files extracted from the UK02-172WWE.zip file obtained from here.
These .nbf files were already configured for operator O2 and language WWE.
I decided to do the same. merlin_uk upgraded with no problems, but I hit the notorious 'Country ID' error :shock:. This didn't make sense, so I tried re-running the exact same upgrade I had done the day before and it also reported Country ID error. merlin_uk re-ran the upgrade he had JUST performed and it also reported Country ID error. Something strange was afoot :?.
We looked at the information in the DeviceData.txt file produced on the device by the HimaGetDeviceData utility used by the upgrade process and saw that the operator was specified as 'CDL' even though we had configured 'O2' as the operator in the .nbf file headers. We therefore suspected that the XDA had become a 'CDL' device somehow. To confirm this I ran the i-mate upgrade without changing the headers to 'O2' so they were set to 'CDL' and it got past the initial check and would have continued if I had chosen to do so.
Now we were on a quest :evil: - something OTHER than the information specified in the headers was setting the XDA's operator code to 'CDL'. Our first thought was that it was the upgrade program itself.
We spent the next 15 hours or so using disassemblers, etc. to look at the HimaUpgradeUt.exe program trying to see where it was doing it. We even managed to get past the initial check, thanks to merlin_uk, by forging the DeviceData.txt file on the device (produced by HimaGetDeviceData) and setting it to read-only, but it still failed when trying to do the upgrade itself. At 6am we had to stop (work committments got in the way ).
Yesterday, I continued the quest and turned my attention to the .nbf ROM images instead. Eventually I found the problem. There is an extra block of information contained in the Operators ROM (ms_.nbf) image just after the nbf header. This extra block contains a language code and an operators code - and guess what? - yeh you got it - it specified 'CDL' as the operator code! EUREKA!! nailed it at last This extra block is documented in the ROM layouts described here.
I then manipulated the ms_.nbf file so that the nbf header contained 'CDL' as the operator (to match the DeviceData.txt) and so that the extra block contained 'O2' as the operator (to match what my operator should be) I ran the upgrade and it ran successfully .
Predicting that my XDA II was now back to being an 'O2' device, I ran it again immediately, and it failed with Country ID error. This confirmed everything. I then reconfigured the nbf header to operator 'O2', ran the upgrade again and voila, I have a 1.172WWE O2 XDA II. .
Since then, purely for experimentation, I have downgraded to the original O2 1.60.00 release and upgraded back again.
Conclusions
The information specified in the extra block of data in the operators ROM image (ms_.nbf) is used to set the device/operator/language in the device. It doesn't need to match what the device is set to already. It is this information which HimaGetDeviceData will retrieve at the beginning of any subsequent upgrade and return via the DeviceData.txt file. I assume it is updated to the new values towards the end of the upgrade process.
The information specified in the nbf headers of all the ROM images (NK.nbf, ms_.nbf and Radio_.nbf) is used to set the device/operator/language in the software of the device. It must match the device/operator/language currently specified in the device.
Neither the ER2003Edit tool nor xda2nbftool, obtained here, update the extra block of data in the ROM image.
The limitation of not being able to downgrade does not exist in any devices with bootloader versions earlier than v1.06. The limitation was caused by the device operator code being unwittingly updated to a 'wrong' value, which affected any further attempts to upgrade. Devices with bootloader v1.06 cannot downgrade, even if the operator code is correct.
The Country ID error could be a thing of the past, as long as anyone upgrading checks and amends, if necessary, the information contained in the extra block of data in the operators ROM before performing the upgrade. This should be done even if the nbf headers are already correctly configured.
In my next post I describe the steps I took to upgrade my XDA II. I believe it is now possible, using those procedures, to upgrade/downgrade the XDA II to/from ANY version/language/operator, as long as you don't have bootloader v1.06 installed.
I-mate pocket pc dead
Hi, my name is roderick i'm new at this site!
today i've tried to upgrade my i-mate pocket pc with wm5. It has Bootloader v1.06. I downloaded this update "ruu172751ger_e-plus_shipping.exe" and prompt a Country ID error. now my i-mate is dead...stays only at the bootloader. When
i did some research i found that i cannot downgrade. I dont have any backup...So i have to put away my pda??
PLS HELP ME I'M DESPIRATE
Is there any way to uninstall the Bootloader v 1.06 on my device coz' i think this is the main reason why i can't upgrade or downgrade my Xda2.
Pls. help.
hello sir
need help about error when upgrading radio.nbf
what should i check 1st?
my PDA O2 XDA II+bootloader v1.03
phone come from costumer in hang condition,then I try upgrade using this rom from c_shekar
ROM: 7.0b.40CS (WM6 AKU 7.0)
dated: 30.Sep.2007
OS 5.2.1620 (Build 18125.0.7.0)
upgrade....rom...ok
upgrade....extended rom...ok
upgrade...radio rom....fail(always error)
please need help?thanx...
error show like this picture:
so now my XDA just PDA cannot use phone when start 1st boot show
no gsm
6.00
please need solution thanx...
Clueless!!!
How does this upgrading of the ROM work?
I have an IMate PDAL WM5 phone and running on TF_WM5_PEAN_VER_03.00
What is a bootloader?
Can I make use of just about any ROM updates available here?
Is it possible to upgrade it from WM5 to WM6?
Obviously now,,,, I AM CLUELESS!!!!
Thank you should you help!!!
Sorry for my bad english
(i will now be responsible if something happens in your device)
reply for much more clarification
******************
Specially dedicated to the Filipinos!! MABUHAY TAYONG LAHAT
******************
Well first of all i like to say Thank You very mush to WAXX who helped me in upgrading my o2 1.66 to 1.72. Thanks You WAXX.
********************************************************
Well... firstly download this file came from WAXX.
http://forum.xda-developers.com/download.php?id=1261
After the download extract the zip file inside it, you shoul be seen 7 files.
I recommend you to extract it in desktop/new folder.
Plug the cradle in your USB.
Insert your XDA II in cradle
Run HimaUpgradeUT.exe, Then follow the steps.
if error appeared, remove the device in cradle and soft reset it, then run the HimaUpgradeUT.exe again.
if error appeared again do a soft reset again.
If no error then it will now smoothly running up to 100% of the proccess.
For me the process takes only 15 min. There are stage 1 to stage 5 for completion.
That's it.
********************************************************
Goodluck.. GodBless..
(i will now be responsible if something happens in your device)
You can approach me for some questions.
Take note this ROM was came from MAXX.
Thanks WAXX for your help.....
CONGRATULATIONS !!!!
I would like to know to your device information (list of rom) !!!
Ok, downloaded the ROM
How do i backup MY rom incase anything goes wrong ?
will the upgrade work with a XDA II for O2 UK Network ???
cheers
Hi
I downloaded the file and unzipped it, when i try the upgrade it says error 120 country id error. my rom is 1.60.00 wwe dutch what is the problem?
Thanks
I would strongly afvise anyone who wants to upgrade to use the 'manual; by dcs together with any ROM Upgrade to prevent (future) country-id errors.
see http://forum.xda-developers.com/viewtopic.php?p=62760#62760
double_ofour,
pare i certainly hope you modified WAXX's ROM to set your Device to O2, instead of CDL You may have had a successful ROM upgrade now, but setting your device to CDL has major implications for future ROM upgrades (Hint: You cant use official O2 ROMS).
Pare how can i convert CDL to o2? step-by-step please
Hi ,
I had 1.72.00wwe on my phone but i was tryin 2 upgrade it further but it got stuck while upgrading and its showing seril while not on cradle and while on cradle its showing usb 1.06
plz hlp me iam newbee and not good in programmin .I also have asecond Xda2 with 1.66.00wwe plz tell if it can b of any help
Reset your device, place it in the cradle and re-run the upgrade.
thanx i tried it already from 2 computers in one its showing error 103 no rom image found and in another its showing error 101 country code problem
Which ROM are you attempting to upgrade to? Which one exactly had you previously upgrade to? What operator do you use?
I'm asking all this to try and get a better picture. Normally, people in your situation can recover by applying the same upgrade again, or, at worst, re-applying the one they are upgrading from.
Make sure you are in bootloader mode (by pressing Jog button and Power button at the same time as pressing reset) before retrying any upgrade. Also make sure the USB cradle is plugged directly into a USB port on your PC and not through a hub and that the power supply is connected to the cradle. It may help to make sure that Activesync isn't running also.
active sync
in the active sync tray it shows that not connected
Well i had 1.72.00wwe rom image 1.14 earlier and iwas tryiong to upgrade to 1.72. something can't remember exactly but it was with rom image 1.17 it was downloaded from t mobile and my current phone is from o2
Click to expand...
Click to collapse
Activesync is not needed for upgrades. The upgrade process looks after its own connection. I suggest you follow the procedures in my post here to overcome the Country ID error problem. You will need to know what the device's operator and language IDs are currently set to, which is why I asked you above. I suspect you won't have Devicedata.txt, so it becomes necessary to know what operator and language the previous upgrade was.
to revive your XDA2 again
The main point is what is ROM 1.66 come from (e.g. i-mate ot T-mobile)
If you doesn't upgrade 1.66 ROM by yourself or it came from factory ,you must tell us which operator did you buy from.
If you try upgrade across operator ,it will hang on boot loader screen.
And again, which 1.72 ROM did you try to upgrade from?
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.