country code error 120 : 1-3-1-1-1 just my experiences - Upgrading, Modifying and Unlocking

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 :?:

Related

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

"Un-brick" Imate JasJar After Failed ROM Update

First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick
Did like u said.
Still country id error
works now
thanks
my device t-mobile mda pro jasjar bootloader nope
rsteel1 said:
First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick
Click to expand...
Click to collapse
this method how?my jasjar can open normal ?
help me
error 101 problem
error 150 problem
MaUpgradeUt_noID trying in my jasjar error problem 150 .whats saying ? problm where? usb dont recognize xp .what must ı do?
please help me im using Vista and cant get connection with my imate to my pc... and what is a radio update if you can help me add my msn!
i dont want to update anymore i just want to get my wm5!
Have a look here:
http://wiki.xda-developers.com/index.php?pagename=FlashVista
Hope it helps,

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...

Atom Exec dead after upgrade

I have an Atom Exec with ROM 20060721B1WWE, Radio RS00011. In the seeO2 website I saw an upgrade (Xda Atom Exec ROM Upgrade (ENG) 20060721B1WWE_RS00013) which is the same ROM but different Radio, supposed to improve quality of calls.
Anyway I went to upgrade it, followed the steps until it said it was uploading it and it would take up to 30 minutes. I went to do something else and when came back the pc screen was saying that the process finished successfully, saying that I had to do a hard reset of the Atom, wait for 30 seconds and then soft restart. I did all of that and all I got it's the O2 screen and doesn't go any further.
Following indication on this forum I launched the bootloader (camera button+reset), conected the usb cable, killed activesync and run again the updater.
The DSUU can see the Atom, says 'Device CE image version:0, Device Radio Image version: (blank) to CE Image version: 7210621, Radio Image version: R060822N_MN2ARC_RS00013.
When I click on Upgrade I get an Error message: Connection error, also on the Atom says '!!! Please use DSUU in OS mode and sync with Pc first !!! USB transfer Fail'
The only backup I did prior to this was using SPB Backup, nothing for the ROM. Is there any other way to upload the ROM?
From the Windows/Temp folder I got the files used by the DSUU:
Device Software Update Utility.exe
diskimage_Ver.nb0
EBOOT.nb0
ExtenderRom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
I've seen in other forums people recovering iPaqs or Axims using these files and software like romupdate, but I'm afraid it could get worse uploading the diskimage_Ver.nb0 as it is.
Anybody knows a workaround for this?
I ended copying diskimage_Ver.nb0 and eboot.nb0 to an miniSD card. Inserted it in the Atom and lauch the bootloader. It recognized the card and Rom file, started downloading it. After that I got few messages saying some files were missing.
Screen went blank and that's it. Now is completly dead, it won't restart or anything.
I'll have to send it to Hong Kong I guess.

Error 270 fix

I'm running Vista and when I wanted to run the bootloader upgrade on my Dash I kept getting this message error. Error 260. anybody find any way around it? I've tried to manually set th ephone into bootloader mode, same result. help!! PS the error is supposed to mean "port already open" or "open port error" I'd really appreciate any help!
erro 260 - fixed
switches to my wife's laptop that had XP on and it worked like a charm. I'd be glad to assist anybody in the process od de-branding their Dash. Removing the ugly T-mobile paint logo on the unit was easy too.
ERROR 260
Sorry for thislong story....
OK, I've been on looking around the site for a while. I installed the WM6 Beta. I was looking for two days for the WM5 ROM only because I want the little things to work. Finally found it. But now every time I try to flash my phone ack to WM5 bI keep getting the 260 connection error. The readme only says to restart the comp and phone and try again. I have literally, no joke, done this 12 times in the last 2 hours, hoping maybe it will go. All the phone does is go to the green, blue, and red screen and stays there. Then the comp says it gets the error. I know it's connected because Sync Center syncs, I can look through the phone, install apps from my comp, etc. Also I tried doing the 'Update only' rom for version 1.11 or so, and it starts to go but then says its the wrong version RUU. Has anyone had this problem before? Flashing to WM6 did this once and then worked after.
I'm running Vista Premium, stock sync cable, Microsoft Sync Center for vista. All this is the sameas when I flashed to WM6.
There goes another 3 attempts, trying to change timing, reinstalling Sync Center, etc.
Decided to try it on my XP desktop, and for some reason, first time it worked. Maybe Vista didn't like it? Who knows..
Mladito Vista!!
Hi there,
I have the same little problem here!!!! I have a laptop with Vista (garbage)... so i´ll try on a laptop running XP...thank you for posting this, it was a big help..i let you know how it turns out... see you around
WM5 to WM6 --> Problems at 3%
Hi all,
I've errors upgrading my phone to WM6.
I Can open the Wizard (it`s a generic to S620/S621), but in 3% i`ve an error.
I think thats my phone has a blocked CID.
How can i unlock this? i`ve tryed with tools to unlock, but without success...
Regards,
Emerson
Hello,
Welcome to the forum.
Your problem is that your phone is CID-Locked. Hence, you'd need to use a paid service to unlock it. I personally used the following service which provides instant unlocking:
http://www.gsmliberty.net/shop/htc-excalibur-instant-remote-unlock-p-1452.html
I used a credit card, it's 39.99 $ - I was done unlocking and upgrading to Windows Mobile 6 in about 15-20 minutes.
Good Luck !
P.S:
Steps to install WM6
- First CID/SIM Unlock using GSM Liberty
- Flash Bootloader
- Install WM6 ROM (It will take some time for it to load so give it about 5-10 mins. it does get stuck at the boot screen for sometime but eventually it'll load)
- Install Office/Audio Manager
- Application Unlock your phone using SDA Application Unlocker
- Install the necessary software/tweak/hacks
there you go, if you have any questions, feel free to ask. also, if you use the search function, everything's available here.
Good Luck !
Here's the following links you require
1) Flash Bootloader
ftp://xda:[email protected]
2)here's the WM6 ROM:
http://files-upload.com/files/472108....90_Ship.ex e
here's office for those who want it:
http://rapidshare.com/files/31706137/Office.WM6.zip
here's Htc Audio Manager for those who want it:
http://forum.xda-developers.com/atta...1&d=1183909664
Ps. I better like German flash, it's smaller due to fewer language packs, and contains English, here: http://files-upload.com/files/472422....90_Ship.exe
thanks to jsp_m for the links.
Hi,
I`ve problems because my IMEI is from Brazil...
And in the site accept only 15 digits IMEI..
My imei is: 35*************02 (17 Digits IMEI)
Thanks,
Emerson
hey,
that's not a problem. everyone has 17 digits, don't include the last 2 digits when you type in your IMEI so for example
11111111111111102
just include the first 15 and submit and you'll get an unlock link in your e-mail, follow that link, scroll down to the page to download dashunlock software and download the .UNL file for your IMEI and then make sure ur phone is connected to active sync and it's green, open the dash-unlock program and then hit enter then it'll ask for the .UNL file, locate it and open it and your good to go - your phone will be unlocked then soft reset it or i think it's automatic and everything's set.
good luck !
p.s: in other words, don't include 02 when you type in your IMEI.
HTC Audio Manager
http://forum.xda-developers.com/showpost.php?p=1355010&postcount=5
Thanks!
I'll Try NOW and let all know...
Regards,
Emerson
Arrghhh!!
My phone still give the message:
Invalid Model ID [244]....
And now? i`ve payed 40 bucks for an unlock software....
Thanks,
Regards,
tatarezende said:
Arrghhh!!
My phone still give the message:
Invalid Model ID [244]....
And now? i`ve payed 40 bucks for an unlock software....
Thanks,
Regards,
Click to expand...
Click to collapse
Emerson;
Read the second post from luckybandit on this thread. That´s exactly what to do to get rid of the "invalid model" issue. Download the bootloader, flash the phone, flash the new ROM and be patient.
My excalibur is also from South America, and worked OK. If you have any doubt just let it know to this thread.
Boa sorte!
Hi,
I`ve problems with the link of Boot loader....
Anyone can send the full URL?
Thanks,
Regards,
Emerson
Hello,
I'm sorry about the links not working, here - i've attached the bootloader for you. here's what you do
1) Run bootloader (attached file)
2) Run the WM6 WWE ROM
3) Run SDA Application Unlock
4) Install Office/Microsoft Voice Command/HTC Audio Manager
5) Install Tweaks/Hacks
here's a site that has some applications and tweaks:
http://mobile.surrealnetworks.com/DashApps.htm
and search this forum, there's tons of information, hacks - etc.
Good Luck !
oh by the way, did you unlock your phone properly?
1) Download unlock software
2) Download .UNL file specifically for your IMEI
3) Connect phone to computer and make sure the activesync's icon has turned green
4) Run unlock software
5) When unlock software asks for .UNL file, browse for it, choose it
6) That's it ! It should say Unlocking done and it'll reboot
Your phone is now Sim & Cid Unlocked. If you have more questions, feel free to ask. just do what i said first then post.
Good Luck ! Hope to see everything working for u...
Hi again...
Now i`ve the Error 260 message everytime my phone boots in "Flash mode" (3 color screen)....
Follow my configuration in this screen:
Excalibur Wi-Fi RUU
ONBL 1.15.0000
Excalibur
SPL 1.15.0000
Excalibur IU
ERROR [260] - No connection
tatarezende said:
Hi again...
Now i`ve the Error 260 message everytime my phone boots in "Flash mode" (3 color screen)....
Follow my configuration in this screen:
Excalibur Wi-Fi RUU
ONBL 1.15.0000
Excalibur
SPL 1.15.0000
Excalibur IU
ERROR [260] - No connection
Click to expand...
Click to collapse
Hi,
Are you using Windows Xp? Cause I've gotten that error a couple of times too but it was in Vista. Try Xp if you're using Vista.
Hi!!
DONE with XP.... but now i`m affraid!! The "Green Screen" with nem OS apparently locked... this is normal? at least 3/4 minutos in the same screen.. both "patches" are applyed sucefully....
Is there anything else to do now?

Categories

Resources