This guide to make it easier to distinguish between one type to another:
SL1 Phones:
SL1 => it is kind of BB5 Phones "regular" with Security Level 1 types of phones (N70, 3110C, E65, and so on ...)
No matter he uses the concept of Single or dual engines, or using RAP3xx or Rapido .
if your phone does not have the PM120 and PM308 does not have a protected , Then the phone is using Security Level 1 (Protected application security level 1 / PA_SL)
you can Doing Unlock / repair SL Zone with many tools that are available in the market today, even with software2x FREE.
example mobile phones with PA_SL1:
Using Rapido CPU type:
N95 (RM-159) - RAPIDOYAWE_V1.11_PA_385ZWK
N95 (RM-245)
N95 (RM-160)
E90 (RA-6)
Using the CPU type RAP3GV2:
6630 (RM-1)
6680 (RM-36)
6681 (RM-57)
6682 (RM-58)
N70 (RM-84)
N70-5 (RM-99)
N71 (RM-67)
N90 (RM-42)
N91-1 (RM-43)
N91-8GB (RM-43)
N91-5 (RM-158)
N93 (RM-55)
Using the CPU type Rap3Gv3:
3109c (RM-274) - RAPGSM
3110c (RM-237) - RAPGSM
3250 (RM-38)
3500c (RM-272) - RAPGSM
3500cb (RM-273)
5200 (RM-174) - RAPGSM
5200b (RM-181)
5300 (RM-146) - RAPGSM
5300b (RM-147)
5500 (RM-86)
6085 (RM-198)
6086 (RM-188)
6086b (RM-260)
6125 (RM-178)
6126/6133 (RM-126)
6131 (RM-115)
6131 NFC (RM-216)
6136 (RM-199)
6151 (RM-200)
6233 (RM-145)
6234 (RM-123)
6280 (RM-78)
6300 (RM-217)
6300b (RM-222)
7370 (RM-70)
7373 (RM-209)
7390 (RM-140)
8600 (RM-164)
E50 (RM-170)
E50 (RM-171)
E50 (RM-172)
E61 (RM-89)
E61i (RM-227)
E62 (RM-88)
E65 (RM-208)
N73-1 (RM-133)
N73-5 (RM-132)
N75 (RM-128)
N77 (RM-194)
N80-1 (RM-92)
N80-3 (RM-91)
N92 (RM-100)
some people misjudged by saying 5310, 6210s, E71, and so on, by saying these are the SL2 class phone, BUT it does NOT have the kind ponsel2x PM308 protected section.
types still SL1 Phones with some extra security in Section PM120. This type is called class BB5 +,
Unlocking can be performed with many of the tools available in the market.
You can do it for free, and there are some tools that still require credit to unlock BB5 + phone type.
Jenis2x BB5 + phone type:
3555
3120c RM-364 V2.0 RAP3GS
5310
5320 RM-409 RAPIDO yawe
5610 RM-242 RAP3GS
5800
6121c
6124
6210
6210s
6263
6267
6290
6301
6555
6555c
6650
7500
7900
8800
8800a
E51
E66
E71
N78
N79
N81
N81 8GB
N82
N85
N95 8GB
N96
================================================== =========
SL2 Phones:
SL2 => are all types of BB5 Phones with Security Level 2 types of phones (7210c, 5800, 5220, and so on ...)
No matter he uses the concept of Single or dual engines, or using RAP3xx or RAPIDO.
if the phone already has the PM120 and PM308 are also protected, then the phone is using the system Security Level 2 (PA_SL2).
This is an example of a phone with Protected Application with Security Level 2 (PA_SL2):
RAPS_V3.03-3600s based on CPU PA_SL2
5220 based on RAPS_V3.03-PA_SL2 CPU
6600f-325 RM-PA_SL2 RAP3GS_V3.02 based on CPU
6600s RM-414 based on RAP3GS_V3.02-PA_SL2 CPU
RAPS_V3.03-7210s based on CPU PA_SL2
7310s based on RAPS_V3.03-PA_SL2 CPU / RM-378 RAP3GS V23.1
RAPS_V3.03-7610s based on CPU PA_SL2
it inlah who explains why many of the tools available in the market have not been able to unlock (except Genie who I know. Now MT-Box and UB also been able to), because Ponsel2 PA_SL2 have the PM308 PM308-protected so that the area can not be in writing on the condition of Local Mode.
BUT Rebuild Certificate (using the ASK-RPL) can be done and 100% working.
================================================== =========
so-called "SL3" Phones:
SL3 => it's all kind of BB5 Phones with Security Level 2 types of mobile phones.
No matter he uses single or dual engine concept, or use RAP3xx or RAPIDO.
if the phone already has the PM120 and PM308 are also protected, and also using firmware are protected; that makes any tool available in the market to write simlock simlock data and key data into the phone.
examples of type SL3 phones:
* 3600s RM-352 - MCU SW 56.26
* 5310 RM-303 - MCU SW 58.58, MCU SW 59.42. Raps V3.01
* 6300 RM-217 - MCU SW 57.20
* 6500c RM-265 - MCU SW 59.45 RAP3GS V2.0
* 6500s RM-240 - MCU SW 59.60 RAP3GS
PA_SL3 with HASH: 9DDBF
* 5130c RM-495 version RAPS_V3.03 ALL-PA
* 2700c RM-561
* RM-578 2730c / 2730c RM-579-1b
* 6303c RM-443
PM308 cell phone with a different security, firmware v30/300/200 used RAPIDOYAWE v1.13E PA_SL2 phones! such as E63, E71, N85, N96, 5800.
it inlah who explains why many of the tools available on the market can NOT unlock the phone with the security of this type (except DM3), because this phone has jenis2x PM308 area is not being written even on the condition of the Flash Mode.
and Rebuild Certificate (using the ASK-RPL) NOT Support (for simlock simlock data and key data not being written)
if you get a phone with simlock data is corrupted, do not buy RPL services in such a hurry because there are no tools available to him rebuild the entire certificate back correctly!
Your phone has a permanent data, here some of the important part:
1. NPC - Nokia Public Certificates - without this - and the phone has no IMEI
security watchdog timer will switch off after 3 minutes
(Security Hardware Watchdog is a module that monitors the CPU software
activities and resources for all logical CPUs restart).
2. Simlock data - this data is necessary to be able to accept the simcard , If damaged
phone will be on Contact Service. This data is not associated with other fixed data.
3. Energy management data - this data holds the values ??for the analog
of the chipset, it is necessary to have the proper charging and other important powers
distribution of values.
4. RF tuning data - the value to the Radio the phone. Various
parameters required to have the receiver working properly and the transceiver
5. Super dongle data and signing key - this is a special area that contains the SX4
exchange of key data + the signing of the Energy Data Management and Tuning of RF Data
Simlock Key Data => THE PM120 BB5 phones Bg5 + SL1 and SL2; And There Is asithi SL1 PM308 BB5 phones.
transovarial writing related RPL pm 308 New articles:
Key-Superdongle
-Simlock simlock data and key data
superdongle private key is the key in use for the article who produce digital signatures (signing the surgery) and decrypt data.
And signatures for the article commonly used encryption keys to verify the data.
And if superdongle applies when turn on the phone PM In the sector containing 1 and 309 A has not entered so nuanced on cell phone service will keanaeragaman contact.
SIMLOCK seems to apply ==> PM 308 sec.1 There ukurannyanya And right, not the content is not true Danijel Care.
SUPERDONGLE_KEY seem to apply ===> Superdongle data lock ON AM There are 308 sec.1 (Macth with public key)
SIMLOCK_TEST passed ==> If the data simlock simlock AT 308 PM And the key sec.1 already "Match / In was signed" By superdongle key.
SECURITY_TEST failed! And if the data =====> AM 1309 There has been, and "Match / In was signed" By superdongle key.
NPC ===> Nokia Public Certificate is where the husband is the backup file certificate USING mobile phones, while superdongle (private key) has been signed by the PM ON data2x sec 1, 309.
And data2x taxable income is already in its signature verification Then On Reported By Public Key encryption (RAP)
If then we read the certifcate in store in the form of NPC, CCC, HWC.
=====================
- SX4 Bypass added after PA_SL2 Activate, if necessary
- "Create RPL from phone" added. This is used to backup possible security data from a phone in their native format NMP RPL (plain one) this includes WMDRM Backup, All low-level certificate (Nokia Public Certificate, Common Configuration Certificate, Hardware Certificate, VARIANT Cert), and Original SIMLOCK (only on the Phone PA_SL2!)!, which can be used to simlock restore / counter reset / PM 308 reset - if needed - this data is sent directly to SIMLOCK SERVER directly so SL birthday is 100% "legal"
- Added Codes Counter Reset for phone PA_SL2. Used to reset Keyboard / FBUS Code Counter.
- Added BB5 NCK Code FBUS Send (# pw + xxxxxxxxxxxxxxx + y), use especially when Keyboard counter is locked.
- Added BB5 NCK Code KEYBOARD Send (# pw + xxxxxxxxxxxxxxx + y), use especially when FBUS counter is locked.
- Export SL BB5 added. This exporting phone configuration key + simlock blocks to "SL5" file
- BB5 SL Import added. Used to import previously exported "SL5" structure to phone in BB5 SP Initialization.
- BB5 PM -> Simlock RPL added, if the phone PA_SL2 - use if simlock has been corrupted, and you only have a backup PM. If PM have needed fields, he will make plain RPL file which can create simlock for you without the headache.
- SL5 Creator support for Creating snaps back SL5 for desired MCC + MNC / Profile Bits
- Added "BB5_Autolock_IMSI.sl5" in UnlockData. Use with IMPORT SL5 for Bg5 phone automatically lock to IMSI (one sim card).
- Added "BB5_Autolock_MCCMNC.sl5" in UnlockData. Use with IMPORT SL5 Bg5 automatic lock for the phone to MCC-MNC (operator).
- Write RPL BB5 added innocently.
- Added "UB Backup" option while writing BB5 Plain RPL (SIMLOCK AREA), since they are not adding SHA-1 before SIMLOCK_DATA in RPL file - need to be skipped in the case.
- Added "Erase Security" option before RPL write. This is used when phone have problem with PM 308 blocks (downgrade, for example) and can not boot to accept superdongle / simlock data - in the case, do not need full erase in case. It should be noted that after RPL write YOU NEED SX4 Authorization with server and writing PM Field 1 and 309. If your phone will fail to pass ST_SECURITY_TEST, and influences that can not boot.
- Skin stack updated to v6.30, this is more stable and faster
- Product code send added
- HWID send added
- PSN send added
- DCT4 Nand MASS MEMORY Partitioning added before write. May skipped ticking apporiative Skip MM Part button.
- When no patch file found, SW will generate unlock codes for DCT4 unlock (asics 2,5,6,7)
- Security Code MasterCode now being produced on reading info
- Added "Skip patch" option. Use it to phone DCT4plus are patched already, and all you need is to Initialize SP lock again (relock, etc)
- DCT4 NCK Key / FBUS Count is now being readed correctly
- DCT4 UEM OTP Imei Read added
- DCT4 SP Locks are being parsed in reading
- Added full support for Vista OS
- Added support for 64bit CPUs - tested on X64 XP Professional, should work on NT6 too
- BB5 Simlock backup before flash write again asking the user to the directory, it's automaticlly saving to StoredFiles
- BB5 Simlock backup automatically saving backup in RPL format if possible (PA_SL2 phone detected), otherwise it will save them in formats PM
- BB5 Booting routines totally refactoring
- After DCT4 Page erase, the last-error-status is now questionable from the phone
- Data checksum is now being checked back in BB5 Flash Write
- When NPC Certificate are being backed up during SX4 Bypass, it is now stored as "" PUBLIC_ID.Sx4Bypass.NPC.CMT.CRT, DowngradeRepair not "" like the previous
- When Writing Bg5 Cert, now default pointing to StoredFiles
- Users are now being warned before "Erase all certificates" - BB5 (avoid mistakes)
- For now, Erase All Certs remove APE certificates too, if APE unit found
- DCT4 Plus 2680 v6.82 unlock partial fixed
- 2630 v57.20 Unlock added
- 2630b v57.20 Unlock added
- 2630b v06.82 Unlock added
- 2760b v06.82 Unlock added
- 2600c-b v06.82 Unlock added
- 1680c v06.82 Unlock added
- 1680c-b v06.82 Unlock added
- 5000db v 05.27 Unlock added
- Unlock added 5000db v 05:45
- Included old "new security" partial opening for 2630,, 1680 5000, 2680 - v6.82
- FastMM problem after exiting Main Application fixed
- Some bugs fixed DCT4Plus open (such as Integer is not valid ...)
- Added WD2 CBUS BT Phones support (bluetooth flashing problems)
- Check Flashing Business (BB5) now booting phone completly, not just taking a Boot Data
- Fixed problem when sometime wrong CMT / APE bootloader are being selected in the Certificate of Operation
- Increased FBUS Timeout to repair FBUS transactions problems on some environments
- Netmonitor activation DCT4/WD2 added
- WD2 Format User Area added
- "Initial SP corrupted" fixed on the phone DCT4plus
- After finished flashing the sound now being played
- Cyclone HW Revision A112 support added
- Progressbar problem fixed while BT Flash
- SX4 Server Transaction fixed
- Delay greater added after SX4 Bypass to handle PM write correctly
- More debug messages is now being displayed on booting BB5
- Refactoring DCT4 ADSP Flashing routines
- DCT4 / default factory Bg5 after flashing fixed in some cases
- Minor changes and bug fixes
- Increased Bg5 Local / Test mode changes
- Support: Fixed "Connection closed gracefully" in some cases
- Problem fixed when invalid IMEI are being readed out from phone (in case the phone is not initialized and FBUS problems occurred)
- PM Write routines rewritten
- Security card is now being resetted before phone flashing, this effect on authenthication speed when flashing many phones one by one
- Selftests routines improved (dynamic timeout)
- Multiple files can now be selected in the Writing Certificate is saved as "" CRT format (Cyclone binary)
- BB5 SP Locks now being parsed on the read out (blocks count, block content, etc)
- DCT4Plus partial to the version 6.82 has now been removed from supported UPP list ASIC ID "3168" which is not unlockable (for now) with rom 0600 to avoid destroyed phones (no signal), in case you will get the message "Not supported UPP ID ", but your phone SL area will be untouched and after flash will still work.
- Blue screen of death fixed on some configurations
- After PM Write, Statistics added, so users can easily see how many PM Record written OK / NOT OK
- IMEI in "Credits" in the calculation is now checked for validity (last digit)
- Updated Message before using DCT4 RPL Credits - ASIC 11 takes 2 credits and rest 1 credit
- Main Nokia Firmware v1.03 avaiable, this changes:
- Output pin tx2 now constant (Service Pin 3) due to many mistakes on user side.
- Flash write speed optimized, should be around 10% - 30% faster, especially on NAND-ONENAND phone. Again came optimization.
- Erase status is now by USB (red) led.
- Added support for WD2 CBUS BT Flashing
- BB5 Booting Improved on some environments
- RTOS Code Updated to 5.2.0
- Microcode USB Stack is now Vista compatible
- Removed the blue screen of death problem on some XP configurations
- Minor bugs, fixes, and various improvements.