Develop Bugs

country code error 120 : 1-3-1-1-1 just my experiences

today i tried to switch my xda2 from t-mobile's 1.72.170GER final rom back to o2's 1.72.184GER final which has been provided recently. i run into that damn country code error 120 because my xda2 has got a t-mobile device id. please find my steps for solving that problem:
1. unpacked the 1.72.184GER package into a folder and replaced the original HimaupgradeUt.exe by the hacked one (which is supposed to ignore country codes).
-> result: same problem - country code error 120 : 1-3-1-1-1
2. then i deleted the HimaGetDeviceData.exe in the folder containing the rom-files. and i deleted any existing DeviceData.txt in the windows folder of my xda2. time to start again the hacked HimaupgradeUt.exe.
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom 1.72.01, radio 1.17.00, extrom 1.72.170 to rom 1.72.01, radio 1.17.00, extrom 1.72.184. i am happy so far but the next screen is again that damn county code error 120 message :-( meanwhile my device is stuck in bootloader 1.06 mode.
3. at this time i deleted the HimaClearJumpCode.exe (which is no longer needed for setting the xda2 in bootloader mode, it is already there) and started again the hacked HimaUpgradeUt.exe (the third time).
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom "blank", radio "blank", extrom "blank" to rom 1.72.01, radio 1.17.00, extrom 1.72.184. next screen tells me that the devices rom is getting erased now and the progress bar shows the current status. everything went through the update process fine.
and my device has been successfully transformed from a t-mobile mda2 which looks like an xda2 to a real o2 xda2 with current xda2-software
summary: i guess you can shorten the whole procedure by setting the xda2 into bootloader mode connecting to your pc by usb unpack only the three rom file images into a folder, copy the hacked HimaUpgradeUt.exe into that folder and start it. but i have no time and motivation for doing that since my device works now.
best regards
peter

where to download hacked HimaUpgradeUt.exe
Dear
where to download hacked HimaUpgradeUt.exe
beast regards
:lol: :lol: :lol:

Thank you very much
Thank you very much its work now
beast regards

o2 ruu
i have tryed upgrading my i-mate to the o2 finaleng ruu with the help of dcs i got it to work with the acked file but now i have megga probs, no camera no extrom and no caller id file so i can't open pictures or video as they are looking for 'albam' to view them, can you suggest a way to get them back???
i have tried the upgrade a fair few times and am getting to the end of a short fuze..... if i run the upgrade direct from o2 i get a model id error, in the device data file i noticed that it has::
usb30 cdl uk5
cdl 1.70.00wwe ph10
or something like that..... it's the uk5 bit that is new..
any ideas :?:

iMate PDA2K behaving as if no SIM card is inserted

Good evening, kind forum readers.
Per the subject line, I find myself in possession of one misbehaving iMate-branded Blue Angel. Everything was working perfectly until a day and a half ago. Now the device is acting as though there is no SIM card inserted whatsoever.
As you might expect, there is no signal detected whatsoever. The 'Device Information' system applicaton reports no information for the Radio or Protocol version. There is no IMEI number listed on the Identity tab. Launching the 'SIM Manager' tool does nothing - the application never launches. When I do a soft reboot, it correctly lists the ROM verion on the startup screen, but says directly above it "No GSM". I've tried a hard boot and restore from a backup from about a week ago, no luck. I have tried with two SIM cards from two different providers, neither one produces any different results. Both cards work perfectly when inserted into another phone.
I am using the official 1.40.00 WWE ROM from iMate. When I try to reapply the ROM, I receive the "COUNTRY ID ERROR". I tried with an older third-party ROM that I had been using a while back, but that also aborts with the same error message.
Speaking with iMate support netted me the typical "Send it in to a service center" answer.
Hoping that someone else out there might have gone through something similar? Any thoughts/suggestions on how I might recover from this?
Regards,
Shawn.

http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom

bosjo said:
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom
Click to expand...
Click to collapse
I just tried this option, and it did progress further this time, but it produced the following error:
Device Software Update Utility - R2500 D1001 - CB2.07 -1
ERROR 114: RADIO ROM UPDATE ERROR
There has been a problem while updating your device software.
To continue the update, please:
1 Disconnect your device and the USB cradle.
2 Perfrom a normal reset by pressing the reset button (as left picture show).
3 Reconnect your device and the USB cradle and run this device software update program again.
Click Exit to quit.
Click to expand...
Click to collapse
Being something of a newbie in such matters, I didn't realize that I had to run GetDeviceData.exe first, so I didn't have a copy of DeviceData.txt. In that the device was not in a bootable state, I wasn't sure how to run the OS upgrade without the Radio upgrade. I ended up going with the decidedly unscientific but seemingly effective solution of just renaming the 'radio_.nbf' file. The OS and extended ROM both upgraded successfully. So now I'm back where I started - the radio is still not functioning.

Run the same upgrade this time with the radio.nbf and remove the other 2 nbfs.
Else ron the radio upgrade only of wiki using those files.

And if what MDAIIIuser says don't work.
Download the latest Rom upgrade from your wendor website,
extract the .exe file with a zip program,
delete the nk, ms, radio files,
Copy the 1.13 radio in there,
Run the BaUpgradeUt.exe
Or try to only delete the ms and nk files leaving what ever radio is in there, and run the BaUpgradeUt.exe

Gday, me BA is dead, failed to upgrade..

I did not get the upgrade out of the PDA first, it is in bootloader mode.
By mistake, I picked up a XDA II upgrade instead of PDA III and clicked the sucker, only to get bummed completely. I guess it "deleted" the orig OS, or parts of it.
The BA is from o2, but private buy, no support expected from them.
The BA was in German, there is no "ID" for o2 given in the ID table.
I even tried T-kom's blackberry upgrade (German) gives same error as the 3 WWE SHIPS I tried, 120 "Country ID error"
Anyway to get the needed ROM info with the bootloader only ?
I would not mind the BA_5.1.1700_build_14343_Upgrade Engrish...
Somebody please help bring my new thang into life again

Hi Man,
Do not worry...Just upgrade the ext rom part of any ROM u have and it will be live again...then u can re-upgrade it completely

One problem I recognize I have: how to get DevData...
Thanks for the assuring words. But I have no idea what you mean with :"upgrade the ext rom part of any ROM u have and it will be live again."
I Assume the ext rom is a nbf file ?
I tried several of the ROM linked from this site (without modifiying them) no succes.
The nice guide made, explains how to get devdata on the PDA when working, but how to get that when bootloader mode is only option ? Or is that necessary? Are there ROM's that works anyway ??
The guide says:
"Device data reads:
PH20B 0 B GER R T-MOB101 1.12.00 0 0 1.12.100 1.02.00 02.00"
I do not have any of this info on my PDA Can it be retreived from the PC ?? (with a program)
I might also explain why I wanted to upgrade the ROM and didnt realize how "complicated" it can be. When trying to install a new appl. (Copilot) with a SD-card, the BA gave:
"setup-Fehler
Die datei "\storagecard\\2577\tts.cab ist keine gultige datei fur windows CE setup"
So, I thought the ROM version was ****ty not even knowing CAB files!
Any hints & help much appreciated
Rgds

Okeh..
Learned alot during the day on this site, it RAWKS!
I found the BA_TMUK_14200_112_11300_Ship (ENG)
& the MDAIII_TMDE_14201_116_11300_Ship (GER)
Using the "MaUpgradeUt_noID" I managed to get the GER running
Dropped the RADIO ROM of the GER to the ENG version and tried runnin the MaUpgradeUt_noID from that ROM. It worked!
The "standard" windows theme is NOT in the ENG pack, but in the GER one.
I then try run these Copilot cab files, still no luck ?!?
Tried some other CAB files snagged from the FTP, they worked...
I both tried the SD card install (autorun the cab) and from the install CD (to PC & device) both gives same error ? A little suspicious that none of the 2 install options work. Perhaps copilot is NOT compatible...

error 120 (incorrect country ID)

I have a spanish vodafone v1640 and i want to change the ROM by using UNI_QTEK_13077_176_10900_WWE_Ship.exe
I have followed the steps from here http://forum.xda-developers.com/viewtopic.php?t=45874 but all I achieve is that error (120 incorrect country ID).
The Rom is in english but the phone is spanish, should that be a problem? I already made a backup.

i have also same problem
Rom is english
Update is Dutch (UNI_DT_WWE_13077_176_10900_Ship.exe)
what can i do ?

Follow this: http://forum.xda-developers.com/viewtopic.php?t=54071

hi quintus.. hmm maybe you can try to upgrade again when u get the error country id, sometimes you need to run 2 times of the upgrade so that i will be successful. just try out c if this works..
cheerss

Not sure if this applies but when doing the radio ROM upgrade I also got the country ID error. I just ran it immediately again without doing anything else. Worked fine. :lol:

Country ID Error Fixed
Hi guys this is my first post!!!
Country ID error....
i fixed my Vodafone V1640 today after a long and hard work
first download WM6.1 or 6.5 then get the original ROM for your
PPC in my was vf-uk_v1640_aku2_v130194_wwe_ship. extract
both to two separate folders (WIN RAR) copy the full content of
the subfolder “OutputFile” and paste in the WM6 folder, it will ask
if you will want to replace “nk.nbf” click yes. go to boot loader mode
and install…..
congratulations!!!

WM6 Flash ends with error "cusTSK.exe doesn't exist"

I have tried to flash WM6 ROMs (both english versions available at wiki - pdaviet and orbit) to HTC original Artemis and every flash ends with error msg "The file \windows\cusTSK.exe does not exist", which is displayed after soft reset when it tries to install extrom.
Does anybody know where is the problem ? I have tried this flash several times, but always with this error ...

It sounds like you may have a corrupt extended Rom. I'd try flashing your original carrier ROM to fix it.

The error message is normal.
When I got the error the first time I boot the device (pdamobiz rom) I waited for 5 mins to see what happens. Then I simply made a power-off-power on to the mobile phone and the error never reappeared ever since. It works perfectly now!

I am not sure, but I guess this err msg is displayed when it tries to install apps from extrom, it is displayed after each hard reset. This is no limitation in functionality, everything works fine, only limitation is that there are no extrom apps installed, but these can be installed manually

I think the problem is that the program that changes the background in WM6 is not cusTSK.exe anymore. I don't know what is the program to do that in WM6 but maybe someone here knows. The error happens because on you extended rom there is a reference to cusTSK.exe. We need to know what is the name of the new program and then update our extended rom.

Sounds logically ...