BB5 Secure Storage Validation: Explained

Ano ang meron dito?

Ok First of all ang tool na gagamitin para sa subject na ito ay MX-Key.

Ano nga ba ang meron dito? See Picture:

Isa-isahin natin:

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed

SIMLOCK seems to be valid at SIMLOCK_TEST passed -- ito ang security data ng unit. SP data, ito ang ina-unlock natin. Ito ang PM 120. Kapag sira ito... Contact service, sa mga RAPIDO naman Nokia Hang lang.
SUPERDONGLE_KEY seems to be valid -- ito ang NPC o IMEI Validation. Ang IMEI Data ng BB5 ay binubuo ng IMEI, HWC at CCC para maging valid ito. Maaaring buo ang serial number pero kapag isa sa mga ito ay missing.... CONTACT SERVICE ang unit. Eto ang NPC na buo:

SECURITY_TEST passed -- ito naman ang PM 1 at 309. Calibration Data (RF/BB). kapag nasira.... Contact Service ang unit.


Ok, Next Question... Paano mag-Repair ng BB5 Secure Storage Validation?

tnx to original poster

NST TEAM

How To Repair SECURITY TEST FAILED

LOGS:
Phone Type: RM-411 (Nokia 5220)
SW Version: V 07.23 17-07-09 RM-411 (c) Nokia
Imei plain: 35571702837662-2
Product Code: 0563564
Language Pack:
- not available.

This is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 355717028376622
Version: SIMLOCK SERVER
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

PROCEDURES:
1- MUST BE CONNECTED TO INTERNET
2- Go To "PM" Tab then tick "LOAD RF/BB FROM SERVER" then press "SUPER SD Auth" or "PMM Auth" If successful in authentication... simply press "WRITE" SEE LOGS BELOW:

SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.3


Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8986(19-10-2010), 1.0.0.14852(19-10-2010)

Product: V 07.23 17-07-09 RM-411 (c) Nokia

Using cached productData[19F00011DBF4585022DDA49A1FDB08CA7A4D945B] ...

Authenticating to SUPERDONGLE using security server ...
Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Elapsed: 23.046 s (session timeout out after 3 second)

As you can see.... hindi tayo maka-pm auth (SX4) dahil ang superdongle key ay CORRUPTED. Kapag ganito ang nangyari.... procede to #3

3- Go to "IMEI & SECURITY" Tab then "IMEI Rebuild" and press "REPAIR SD" SEE LOGS BELOW:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8986(19-10-2010), 1.0.0.14852(19-10-2010)

Product: V 07.23 17-07-09 RM-411 (c) Nokia

Using cached productData[19F00011DBF4585022DDA49A1FDB08CA7A4D945B] ...

Calculating SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.3

Completed in 50.969 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-411_355717028376622_SD.RPL"
Updating SUPERDONGLE_KEY ...OK

Ayan mga kabayan, ok na ang SD ng phone..... NEXT STEP.............

4- Ulitin ang # 2 procedure.

SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.3


Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8986(19-10-2010), 1.0.0.14852(19-10-2010)

Product: V 07.23 17-07-09 RM-411 (c) Nokia

Using cached productData[19F00011DBF4585022DDA49A1FDB08CA7A4D945B] ...

Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 121.54.86.110
SUPERDONGLE authorized !
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.3

Updating RFBB data ...
Writing section 1...
Writing section 309...
Done.

Ayan ok na!

Now Check natin kung nagawa ang SECURITY TEST FAILED

Phone Type: RM-411 (Nokia 5220)
SW Version: V 07.23 17-07-09 RM-411 (c) Nokia
Imei plain: 35571702837662-2
Product Code: 0563564
Language Pack:
- not available.

This is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed


Imei net: 355717028376622
Version: SIMLOCK SERVER
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

How To Repair Simlock & Simlock Test Failed (Contact Service)

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!

How it's done? Follow the image instructions (IMEI & Security/Simlock/Repair Simlock/Make Simlock RPL/Repair Splock

Now there are few to be considered WHY SOME NOKIA PHONE SIMLOCK CANNOT BE RESTORED, they are as follows:
1- Hash support -- this applies to SL3 (SL2 Format) which HASH is not supported
2- Corrupted PM 120 -- this applies to handsets with tampered PM 120. See Sample Below

GOOD PM 120

[120]
0=000000000000000024407000000000000018070000000000 0050000005FFFFFF00B4000005FFFFFF0118000005FFFFFF01 7C000005FFFFFF01E0000005FFFFFF0244000005FFFFFF02A8 000005FFFFFF000000007FFF6F07FFFFFFFFF800030C030005 03000000007FFF6F3EFFFFFFFFC000030F0200010300000000 7FFF6F3FFFFFFFFFC000031102000103000000007FFF6F07FF FFFFFF07FE031308000503000000007FFF6F07FFFFFFFF07FE 031B08000503000000007FFF6F07FFFFFFFFF8000323030005 03000000007FFF6F3EFFFFFFFFC00003260200010300000000 7FFF6F3FFFFFFFFFC000032802000103000000007FFF6F07FF FFFFFF07FE032A08000503000000007FFF6F07FFFFFFFF07FE 033208000503000000007FFF6F07FFFFFFFFF800033A030005 03000000007FFF6F3EFFFFFFFFC000033D0200010300000000 7FFF6F3FFFFFFFFFC000033F02000103000000007FFF6F07FF FFFFFF07FE034108000503000000007FFF6F07FFFFFFFF07FE 034908000503000000007FFF6F07FFFFFFFFF8000351030005 03000000007FFF6F3EFFFFFFFFC00003540200010300000000 7FFF6F3FFFFFFFFFC000035602000103000000007FFF6F07FF FFFFFF07FE035808000503000000007FFF6F07FFFFFFFF07FE 036008000503000000003F007F206F07FFFFF8000368030005 03000000003F007F206F3EFFFFC000036B0200010300000000 3F007F206F3FFFFFC000036D02000103000000003F007F206F 07FFFF07FE036F08000503000000003F007F206F07FFFF07FE 037708000503000000003F007F206F07FFFFF800037F030005 03000000003F007F206F3EFFFFC00003820200010300000000 3F007F206F3FFFFFC000038402000103000000003F007F206F 07FFFF07FE038608000503000000003F007F206F07FFFF07FE 038E08000503000000003F007F206F07FFFFF8000396030005 03000000003F007F206F3EFFFFC00003990200010300000000 3F007F206F3FFFFFC000039B02000103000000003F007F206F 07FFFF07FE039D08000503000000003F007F206F07FFFF07FE 03A508000503FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
1=10561C2F8D1850D6F54B3C90CBF093DE912D63B8C1F2AAD9 A02CE9E1D557C6D45FEA0EE248AE4841C378F4D5850FB286F5 7AB5E0C3C8FA2419F1A2A71C3F868CDA3F5111E67E469EBBBB 8C8322CBB897
2=49423D9947AEDF42473157F9360EE184AC9046A2
3=000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000

INVALID/CORRUPTED PM

[120]
0=000000000000000024407000000000000018070000000000 0050000005FFFFFF00B4000005FFFFFF0118000005FFFFFF01 7C000005FFFFFF01E0000005FFFFFF0244000005FFFFFF02A8 000005FFFFFF000000007FFF6F07FFFFFFFFF800030C030005 03000000007FFF6F3EFFFFFFFFC000030F0200010300000000 7FFF6F3FFFFFFFFFC000031102000103000000007FFF6F07FF FFFFFF07FE031308000503000000007FFF6F07FFFFFFFF07FE 031B08000503000000007FFF6F07FFFFFFFFF8000323030005 03000000007FFF6F3EFFFFFFFFC00003260200010300000000 7FFF6F3FFFFFFFFFC000032802000103000000007FFF6F07FF FFFFFF07FE032A08000503000000007FFF6F07FFFFFFFF07FE 033208000503000000007FFF6F07FFFFFFFFF800033A030005 03000000007FFF6F3EFFFFFFFFC000033D0200010300000000 7FFF6F3FFFFFFFFFC000033F02000103000000007FFF6F07FF FFFFFF07FE034108000503000000007FFF6F07FFFFFFFF07FE 034908000503000000007FFF6F07FFFFFFFFF8000351030005 03000000007FFF6F3EFFFFFFFFC00003540200010300000000 7FFF6F3FFFFFFFFFC000035602000103000000007FFF6F07FF FFFFFF07FE035808000503000000007FFF6F07FFFFFFFF07FE 036008000503000000003F007F206F07FFFFF8000368030005 03000000003F007F206F3EFFFFC000036B0200010300000000 3F007F206F3FFFFFC000036D02000103000000003F007F206F 07FFFF07FE036F08000503000000003F007F206F07FFFF07FE 037708000503000000003F007F206F07FFFFF800037F030005 03000000003F007F206F3EFFFFC00003820200010300000000 3F007F206F3FFFFFC000038402000103000000003F007F206F 07FFFF07FE038608000503000000003F007F206F07FFFF07FE 038E08000503000000003F007F206F07FFFFF8000396030005 03000000003F007F206F3EFFFFC00003990200010300000000 3F007F206F3FFFFFC000039B02000103000000003F007F206F 07FFFF07FE039D08000503000000003F007F206F07FFFF07FE 03A508000503FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

3- IMEI with 123456789? CANNOT BE REPAIRED -- hini mo magagawa ang simlock kapag corrupted na ang IMEI, kahit ano gawin mo liban na lamang kung kaya mong i-restore ang NPC

regards

NOKIA SPECIALIST TEAM

Jailbreak iPhone 4, 3GS on iOS 4.1 with Limera1n Step by step!!! Moments ago, we posted that Limera1n was released to jailbreak all iOS 4.1 devices

Moments ago, we posted that Limera1n was released to jailbreak all iOS 4.1
devices forever. We promised with how-to guides and here we go, you can now use the step by step guide below to jailbreak iPhone 4 and iPhone 3GS using Limera1n on Windows only.

Here's the instructions to jailbreak iPhone 4, 3GS on iOS 4.1 using Limera1n, PLEASE read the important notes at the end of the post:

STEP 1: Download Limera1n for Windows from here.

STEP 2: Connect your iPhone to your PC via USB then launch Limera1n and hit “make it ra1n”

STEP 3: You will have to get your device into DFU mode by following the steps on the screen shown by Limera1n.
You iPhone will now be placed in recovery mode.

Press both the power and the home buttons.

When Limera1n asks you to, release the power button.

Your phone will now be in DFU mode

STEP 4: Now, Limera1n app should be shown on your iPhone's home screen. Limera1n will pwn your device forever now.

STEP 5: The jailbreak should be done now. Tap on the limera1n icon on your device and install Cydia.

IMPORTANT:
You have to keep some points in your mind, first, Limera1n will not unlock your device (i.e. you will lose unlock if you upgraded to iOS 4.1 and used limera1n).

Second, Limera1n is not working with old bootrom devices and it doesn't support iOS 4.2 beta, Geohot is fixing the issues right now. Stay tuned.

Limera1n would mess up GreenPois0n jailbreak release as the teams don't want to give Apple two exploits. They would better save one of them to 5th-generation devices.

Original Poster
Regards
Techgsmnet

IPOD 20 GB Hang on Battery w/thunder Done via Hardware

How To Solved ? Contact me : opgmark@yahoo.com 

Say No To PRICE DUMPER !!!

Original Poster : k r i t z

Redsn0w 0.9.6 for Windows to Jailbreak iOS 4.1 on iPhone 3g Has been Released

Dev-Team has just released a fresh beta version of redsn0w version 0.9.6 b1 for Windows, which allows users to jailbreak iPhone 3G and iPod touch 2G on iOS 4.1. The same tool for Mac is already existing as we reported you the last few weeks.

The Dev-Team warned who use ultrasn0w to unlock their devices, to stay away from redsn0w, and wait for PwnageTool to support iOS 4.1. that is because to use redsn0w at 4.1, you need to already have updated to official 4.1 from Apple, if you do that you will lose the ultrasn0w unlock.

This BETA release supports:
iPhone 3G and iPod touch 2G only (for now)
Mac OS X x86 and Windows only (for now)
4.1 or 4.0 firmware from Apple
Note: if you have an “MC” model of the ipt2g, your 4.1 jailbreak will be tethered…sorry! (Consider rolling back to a FW supported by jailbreakme.com or spiritjb.com)

Any Windows users seeing “Waiting for reboot” for too long (more than 20 seconds or so), please try “shaking” the JB process by unplugging then replugging your USB cable (while letting redsn0w continue to run). Also, try using a USB port “closer” to your computer (as opposed to on your monitor or behind another hub). We’re still tweaking the Windows flow and so any feedback you can provide will help!

Unlock and Jailbreak your iPhone 3Gs Using JailbreakMe for Version [4.0.0, 4.0.1]

Step One
Press to launch Safari from your Springboard.

Step Two
Press to select the address bar and input http://jailbreakme.com then press the Done button.

Step Three
To begin the jailbreak simply move the slider to right.

Step Four
You will be displayed a status bar as the download progresses.

Step Five
Once the download is complete the jailbreak process will begin

Step Six
Once you are notified that the jailbreak process is complete press the OK button.

  Press the Home button to reveal Cydia on your desktop! 

Congratulations you are done! You may now continue by installing UltraSn0w to unlock you device. iPhone 4 users still need to wait a bit for an UltraSn0w update which will arrive shortly.

A big thanks goes to Comex and the iPhone Dev-Team for their efforts and successes.