|
:: Home bs0dd.net :: Guest book :: Nokia Phones FAN-Site :: :: Elektronika MK :: Nokia 92xx Archive :: Kannel for Windows :: -- Переключиться на Русский -- News №13Nokia DCT1-2: bypassing protectionChapters:Theory
All Nokia GSM phones have been divided into generations since the very beginning of production.
Essentially, the main platform models are 1011, 1610, 2010, 2110, 3110, 8110. The rest are variations for different networks (GSM900/1800/1900), countries, or operators. The 9000 Communicator uses a telephone system similar to (and obviously based on) the 2110. DCT1 models are easily distinguished from DCT2 models - the latter have a screen with a full graphic section (without distinct characters) and a different connector for charging and connecting accessories. Moreover, only the 3110 and 8110 essentially belong to the DCT2 platform; the rest are variations that are similar in appearance. A key difference between these models and the DCT3 and subsequent models is their processor architecture. Beginning with the 6110 model, introduced in 1997, and the beginning of the DCT3 generation, phones began using ARM processors. The DCT1 and DCT2, however, operate on a completely different architecture - the Hitachi H8. This can be easily verified by disassembling the phones - the 2110 uses the H8/500 processor, while the 3110 uses the H8/3001. So, I have a couple of 2110 phones and one 3110. Their firmware versions are shown below:
In these models, we can have two security problems - carrier locking (SIM Lock) and user code locking (Security Code).
Luckily, there are solutions to both problems. They can be non-invasive (no need to connect the phone anywhere) or invasive (connecting the phone to the PC with a cable). Non-invasive methodsSo, let's imagine that our phone has a SIM-Lock. In this case, when inserting a "foreign" SIM card, a message like this will appear on the phone:
This isn't good news, is it?
The blocking needs to be removed, and the ideal solution would be to figure out the code to unlock it.
Specifically, on DCT1/2, apparently only level 1 was usually used, so we'll focus on that. This code is generated based on the specific phone's IMEI and the operator's network code, which looks like xxx-yy. xxx - the country code (Mobile Country Code, MCC), yy - the operator code (Mobile Network Code, MNC). Therefore, knowing the operator (often, at that time, their logo was still printed on the case), you can find their MCC-MNC code online. Operator variant tables are also available for phones; the model code (Product code) is indicated on the IMEI sticker, under the "Type" parameter.
For the NHE-4 type models - DOWNLOAD (TXT) SP Lock Code Generator (SPL)A simple DOS application (run in DOS-BOX or on older 32-bit Windows) that allows you to generate codes for any of the four lock levels. The version I've posted is cured of the Runtime error 200 (a common problem), which occurs when running the program on processors faster than 180MHz. Crux CalculatorA universal unlocker for DCT1-4 phones. It has a built-in operator database (no need to search for MCC-MNC codes) and also generates codes for 4 levels. For DCT1-2 phones, use the "General DCT2" profile. In this mode, it also generates the factory Security Code (the same one supplied on paper). Just remember to disable (if enabled) the IMEI checksum check (the last digit; in early GSM phones, it is always 0, because the checksum hasn't been introduced yet). So, after entering the code, there are 4 possible scenarios:
If you're unlucky and don't know your carrier or receive a "NOT ALLOWED" message - don't worry.
Video demonstration:
Now let's talk about the Security code. If you turn on your phone with a SIM card that wasn't previously in it (it stores a list of the serial numbers of the last few SIM cards) and the previous owner activated security, the phone will ask you for the security code: In this case, the code is a 5-digit sequence. As mentioned, these models come with a unique factory code by default. Therefore, if the previous owner didn't replace it with their own, you have a chance to find it using a non-invasive method. There are two main utilities for calculating the factory code using the IMEI: IMEINOKIA
A DOS application that allows you to generate a code. Crux CalculatorAs already mentioned, it can also generate a Security code if you try to generate a Sim-Lock code for any operator. If you entered everything correctly, but the phone displays a "CODE ERROR" message, you're unfortunately out of luck. The previous owner changed the code to their own. PIN bypass won't help here either; even after changing the PIN, the phone will still ask for the security code, I've verified this.
There is a potential solution (without connecting the phone to a PC) - DCT1-4 phones have a legal "backdoor" called a master code. This is a 10-digit code that can be entered instead of the unknown user code to unlock the phone (and then set a new code). For DCT3-4 phones, it can be easily generated using the IMEI. You can visit nfader.su or download the program. As for DCT1/2... I still haven't found a program capable of calculating the code, as the algorithm is clearly different for them. I'm afraid no one has dared to crack it. This code (like the current security code) can be found using a cracked version of the official WinTesla service program (see the Heavy Artillery section).
Unfortunately, the service program doesn't calculate it; it simply queries the phone with a command.
So, in the best-case scenario, the algorithm is stored in the phone's firmware. In the worst-case scenario, the code was pre-calculated at the factory and loaded into the EEPROM...
Maybe someone can figure this out.
Here are the master codes for my models - maybe someone can figure out the connection (unlikely)...
The Great MBUS
So, you couldn't remove the SIM lock with a code or unlock your phone with the factory combination?
To make the simplest available version of this cable, you'll need:
Finally, we'll have just two lines: ground and MBUS. Connecting ground to the phone is easy, but MBUS is a bit more involved.
The connectors on these models aren't very convenient, and getting the plugs is problematic, I'd even say nearly impossible.
So, I know of three types of connectors in this generation: So, using what we have, we assemble the cable. Here's what it looks like with the 2110 and 3110 connected:
I chose "Dupont" cables; everything is assembled and works without any soldering.
And similarly "upgrade" it to MBUS.
To work with a USB cable, it's best to set up a virtual machine running Windows XP or even Windows 98SE.
As variant - use VirtualBox.
In my case, the USB adapter is the /dev/ttyUSB0 device. In Windows, you'll need to select the COM* port assigned to the adapter by the system. Nokia TOOL by KOCI
This app by Tomasz Kocian is designed for working with DCT2 and DCT3 phones.
The DCT3 features are outdated, but the DCT2 mode is very useful. Its major drawback is that, contrary to its claims, it does NOT support the 2110 and (most likely) related models. Unfortunately, they use different control commands, so Nokia TOOL cannot read adequate data.
I recommend using version 3.12.0, as version 3.52.0 isn't fully cracked -
most features refuse to work, considering the app not activated. Nokia Phone InfoAn older program with similar functionality by Dejan Kaljevic, written for DOS DPMI (requires Windows or an extender). It has a pseudo-graphical interface and can calculate SIM unlock codes. Unfortunately, it suffers from a similar issue: it doesn't work with the 2110, as you can see in the screenshot. It also seems to be sensitive to PC specifications; for me, it rarely establishes a connection, often giving an error immediately. Therefore, I recommend the program above. Heavy artillery
So, let's say we now know how to unlock models like the 1610, 3110, 8110.
But what about a locked 2110 (and related models)?
Unfortunately, this requires heavier artillery, i.e., official service software. GSM SERVICE PCLOCALSThis is the official program for the 2110 (NHE-4) model, and may also work with related models. Unfortunately, it requires DOS and a COM cable to function properly. However, it has a decent number of features, although it unfortunately doesn't support SIM-Lock functions. You can view information about your phone's software and the results of the power-on self-test. Once the phone is in Local (service) mode, other options become available. You can now edit the phone's data; there's a separate section for that. For example, editing (and importing/exporting) a phone book.And most importantly, you can read your current Security Code (and change it instantly), as well as your Master Code! Plus, you can set the text for the welcome screen. You can also change settings, for example, enable additional languages (present in the firmware, but hidden). You can also change the phone's hardware version number and IMEI. However, the latter doesn't seem to want to change. The program seems to send it to the phone, but it has no effect, tested it on two phones. Perhaps some additional steps are required - only Nokia employees would know about this.
Next comes the IMEI transfer function. This is intended for use if a hardware fault is detected during service repairs
and the board needs to be replaced. In this case, the IMEI code is transferred from the faulty board to the new one.
This erases the IMEI code from the old board's EEPROM, making it completely inoperable. The last two options - a partial and full factory reset. This also resets the user code to the one calculated based on the IMEI. There's nothing else of interest to say about these options. Another main menu item - Testing and Adjustments. Here, as the name suggests, you can test and tune certain parameters of the telephone system.
This menu isn't useful for us, as adjustments should be performed by qualified personnel using specialized equipment. Finally, we are left with the most powerful publicly available program: WinTesla
WinTesla is a service software for working with DCT1-3 generation phones (starting with DCT4, it was replaced by Phoenix).
The program is written for Windows 3.1, but can be used successfully with Windows 98 and, with somewhat less success (crashes are observed), with Windows XP.
This is its main advantage over PCLOCALS. This is what the program interface looks like after launch:
We don't need to specify an ID to work, so just click OK. Here we select our model depending on its code: The program will now attempt to connect to the phone. If successful, the phone will reboot and the number of options in the program menu will increase, indicating a successful connection. Overall, the main feature set is not much different from that in PCLOCALS for 2110. Of course, we can read the Security Code, Master Code, and set a greeting: The same special settings (Product Profile) can be changed: For the 3110/8110, you can also enable a special network search mode (for testing purposes) and set a custom operator name (as in the KOCI app). For the 8110i, Smart Messages can be read and written. For the 2110, the window for changing the IMEI and hardware version number looks similar to PCLOCALS. Yes, changing the IMEI doesn't work either; the new number simply isn't saved.
For the 3110/8110, the window looks different. In addition to the above, you can change a certain Product ID and Product Code (unique for each phone subversion).
And changing the IMEI doesn't work again! The program successfully writes other data, but when trying to change the IMEI, it returns a "General error". For phones, you can also find general information…
The 3110 and 8110 have a display contrast adjustment feature. The 2110 doesn't allow you to change the contrast, but you can test the screen by displaying one of two test images. And, of course, the phone book editing function (this doesn’t apply to the 3110 – it doesn’t have its own book, only the SIM card). Essentially, that's all the basic functionality we can find useful. We can certainly run through the other windows in the testing section, but without knowledge and the necessary equipment, it won't do us any good. Here's what's available for the 2110, for example:
That's pretty much it for unlocking DCT1 and DCT2 phones.
I plan to create a similar article for DCT3 and DCT4 phones, as there are many more of these phones
and I often get requests for help unlocking them.
In the meantime, I hope this guide helps you bring your ancient "brick" back to life! 26 December 2025 year, 14:46:53 UTC CommentsThere are no comments yet. Would you like to leave yours? |
||||||||||||||||||
|
Переключиться на Русский Powered by COMPPAG 0.56 2022-2025 © Compys S&N Systems |
||||||||||||||||||