What is Country Code? - MDA II, XDA II, 2060 ROM Development

I see many posts on what to do when this error occurs, and I see that there is a tool (EREdit) around this, but I'm confused as to what "country" specifically means in the context it is used. Of particular interest to me is the new 1.72 Beta ROM.
1. Is it really country, as in USA, UK, France, etc., or is this only in reference to device brand (T-Mobile MDA II, O2XDA II, Orange XDA II, iMate, Qtek)?
2. In other words, If I have an MDA II, with T-Mobile 1.60.36 ROM, would the new 1.72 ROM consider that the same country?
3. Or since I see this has a UK reference, and my ROM came actually from the Netherlands site, does this mean that I will get into the country (from Dutch to UK)?
I hope I have not asked the ridiculous. I just don't know specifically what the "country" means.
Ed

gratefuled,
I don't know exactly, to answer your questionabout the country code - but
I have an O2, XDA11, and have just updated to 1.72 TMobile ROM.
I used the current ROM Editor and selected CDL for the operator. The other options, incl. O2 gave me a Country Code error.
That was last night, and now 24 hours later, the XDA2 is still working OK.
Seems a little faster, and easier on the battery.
BB

My point regarding the country code stuff is this.
If one is flashing a ROM from the same carrier, say from T-Mobile to T-Mobile, does this eliminate any country code error problems? My point is is the term "country", actually mean carrier, (T-Mobile, O2, iMate, Qtek, etc.)?
In other words does the country error only occur when one is switching from , say O2 to a T-Mobile ROM?
Ed

Related

T-Mobile PPC-PE on Orange UK

Please tell me there is a way to get the T-Mobile version of the XDA (from Canada) to work on the Orange network in the UK! :roll: :?:
I have just bought one for my Dad (I already have an O2 XDA on Orange) and I've gone into the bootloader and selected radio 900/1800 which i believe is what orange runs on, but when I put my Sim into the device it just says no service
It's currently got RS 6.24.00 on the device, do I need to change this to 4.21.00 ?
If so how ? As I can't see the option in the bootloader to load/backup rom's like on mine
Please help
Cheers
Neil
Anyone ?
try to do a search i'm pretty sure that the gsm settings cant just be changed in software, and if thats the case then a US (900/1900) can never be used in EU (900/1800)
xda2 dont have that issues because it's triband (900/1800/1900)
Have tried searching already... couldn't find anything of relevance
There is the option in the bootloader that includes 1800, can't remember what the other exact options were as I don't have the phone with me atm. But I'm pretty sure the one I selected was 900/1800, so I hope (and pray) that this phone supports 1800.
Do I also need to select the band through WM2003 aswell as doing it in the bootloader?
Can someone confirm what band the UK networks Orange and Vodafone use, just to make sure I'm trying it with the right ones...
Any help much appreciated, as I'm getting desperate on this one, as its a crimbo present for my dad..
Cheers :wink:
Neil
EU as in all cellphone companies use 900/1800
it's the EU std like PAL is
US use 900/1900 and i dont think anybody else use that
did a quick search in the forum and came across this
http://xda-developers.com/phpBB/viewtopic.php?t=3064&highlight=900+1800
S**t S**t S**t thats not good
I've just been doing some searching on google and found that Cellnet and Vodafone use 900 & 1800, and Orange and One2One use 1800.
Does this mean I will be able to use Voda or Cellnet as they use 900.. and the phone is on 900 / 1900 ????
Cheers
Probably, just shove a voda or O2 card in and see what happens.
Thanks to everyone who helped, my Dad has now been given his PPC and it works on Voda

Question about the XDA Developers Rom.....

Hi, I have a Wallaby which was originally from the United States. I live in England however. I downloaded the XDA Developers Rom and installed it which unlocked my device with no problems. However, the only network I seem able to use is O2 (I tried a friends chip) but I want to use my T-Mobile UK chip. I tried the function included in the rom which allows you to switch bands but I still cant get it to recognise T-Mobile, I don't know if it is anything to do with the radio stack, I don't think it is but I could be wrong? Anyway, can any of you offer anyt advice or have you maybe had the same or a similar problem? If so I would really appreciate any imput you might have. Many thanks.
xda1 is only dualband and us xda1's only support 900/1900 not 900/1800 like eu use no way of getting around that really
hi
my previous wallaby was phone edition DT Com from the states, friend of mine which bought it there for me unlocked it and I used it normally in Bosnia, also he had one US wallaby marked as siemens sx56 also unlocked and used here too. As far as I can remember he also bought one more for his cousin here too... Now you know where all those old wallabys are - here !
Dont want to argue is it possible or not just want to inform you, maybe those wallabys was some special kind, dont know.
GL
900Mhz is used by both us and eu so operators who use that band are supported but there is no way to make a dual band a tri band or any way to change a eu dualband to a us dualband that i know of
My Qtek 1020, incidentally bought in the UK, also suffers from this 'feature' and as a result only works on O2 and Vodafone (maybe others but those for sure), but definitely not on T-Mobile and Orange.
Regards,
Neil.

Niki100 can't read South Korean Sim? [Solved]

Hey Ladies and Gents, I've got a bit of an issue here.
I've got my faithful Niki100, which was purchased in Australia, completely unlocked (spl 1.22 Hard, completely CID unlocked as per the stickied threads), but it won't read the new KTF sim I have here in Korea. It detects what the number attached to the SIM is, but won't read anything else on it.
The sim does appear slightly different (see attached photo).
The Australian sim would be a GSM/WCMDA USIM, the Korean sim is (probably) a CDMA2000/WCDMA USIM.
Regardless though, I *expected* the phone to pick it up and read the WCDMA (UMTS) part of the sim and connect - It's quite happy using the Australian sim and roaming on the 2100mhz network here, I was expecting it to do the same with the Korean SIM.
Any ideas?
I'm using a custom cooked 6.1 rom I made with the old Nike Kitchen about 8 months ago, and the 1.65.22.29 radio.
Cheers
EDIT:
Solved: It was a combination of needing new Sim Manager version, and the retarded IMEI lock South Korea puts on all foreign phones.
I'm surprised that it roamed on the 2100 Mhz network, I thought it didn't support that, the only option I can think about is try to flash a wm 6.5 rom.
I hope this solve your issue but unfortenally I'm not an expert in these things.
Goodluck

[Q] When should I expect updates?

Hello! I got a new Lumia 920 (Vodaphone branded ROM, though the phone itself doesn't have any branding, "Manufacturer Model Name" listed as RM-821_eu_euro2_268, and running on an AT&T gophone SIM card, dev unlocked), and was wondering when I should expect to see updates. I've seen news sites talking about the release of updates like Portico on AT&T, Vodaphone, etc., but I'm not sure if I should follow the updates for Vodaphone 920s (since that's the ROM it's running on), AT&T 920s (since that's my carrier), or unlocked 920s. Any chance one of you could help clear this up for me? Thanks!

O2 say my phone is not on their locked database

I have a sony xz premium phone model G8141. I purchased it second hand from a business on ebay, who say it is locked to o2. This appears to be correct as there is an app called "o2 recommends", i can use o2, tesco and giffgaff sims in it, but not ee or vodafone the phone comes up requesting the unlock code. I contacted o2 to get the unlock code, but they told me that it is not on an o2 phone and is not in their database. I can go and get it unlocked at a high street unlocker, but why might the imei not be on o2 s database. Could the phone be actually locked to another network eg tesco, sky, giffgaff, lycamobile etc. Could o2 have recorded the imei incorrectly, or could the phone have been originally locked to a different network, say ee, then unlocked and then locked again, but this time to o2? Or could there be another possibility?

Categories

Resources