n73 simlock data corrupted! - GSM-Forum

supersonic-x · 02-24-2010, 06:26

mx-key masters how to solve this problems?

heres the logs

Using device: J.A.F, FW ver: 01.B0
Library version: 1.0.0.11893, Date: 26-01-2010
APE Data :
SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0]
ASIC MODE ID: 00
PUBLIC ID: C90FCED89E26CEE26FF4B2FD72ADE6FBEC7EF266
ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000
ROM ID: 1DFD66132C872FD4
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 1B600210C3C100545351A9D66D6814726D33D128
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
RAP PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: NAND,APE
ExtBUSC: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Original Imei: 35973800642985
Original Product code: 0541479
Bluetooth ID: 0018C53C262F

Phone Type: RM-133 (Nokia N73)
SW Version: V 05wk47v60.1 20-03-08 RM-133 (c) Nokia.
Imei plain: 35973800642985-8
Product Code: 0541479
Language Pack:
- not available.
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST failed!

SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

tia

Ramzan khan · 02-24-2010, 06:40

1. You need to backup Certificate first. NPC ONLY.
BB5 > Servie > Imei & Security - Select NPC from drop down menu.

2. You need to COMPLETELY ERASE the whole flash.
BB5 > Flash > Advanced, Get Addr, untick SAFE Erase

3. Reflash all necessary data to phone. (ENO (if needed), MCU, PPM, etc)
In this case, regarding with supported firmware for simlock rebuid, you will need to use OLDER firmware.

4. Flash MCU ONLY, same version with ENO firmware, that you flashed on first flashing

5. Next step is Certificate restore. Write back your NPC Backup.

6. REPAIR SIMLOCK - Determind first what SL level you got
- It's SL2, so what?
> Tick PA_SL2
> Choose Repair SIMLOCK
> Tick make SIMLOCK RPL
> Click Repair SPLock

7. REPAIR SD

8. Now check for your Certificate by Certificate Validation Tool
BB5 > Service > Phone Test > Various > BB5 Certificate Validation

In my case, phone doesn't has CCC and HWC, next step is:

Write CLONE RPL

9. Proceed with SUPER SD Auth, and write PM after it.
Load PM > Suped SD Auth

10. And the last step, you can update to the latest firmware.

All done in 10 steps.
This method also work for phone that can not be fully backuped. (cant' safe PM, can't local mode, blank screen, etc)

!! DONT DO THIS ON SL3 !!

If you got phones with corrupted simlock, the main thing is you need to clean it up first. That phone's PM is messy
The whole steps as simple as:
Backup NPC > Erase > Reflash > Restore NPC > Rebuild Simlock > Pm auth, write pm. Thats all

if you not understand go to this link i all learn from here and copy paste

just want to help you

http://forum.gsmhosting.com/vbb/show...=726058&page=2

02-24-2010, 06:26	#1 (permalink)
supersonic-x Insane Poster Join Date: Aug 2007 Location: angeles city Posts: 66 Member: 565282 Status: Offline Thanks Meter: 22	n73 simlock data corrupted! mx-key masters how to solve this problems? heres the logs Using device: J.A.F, FW ver: 01.B0 Library version: 1.0.0.11893, Date: 26-01-2010 APE Data : SYSTEM ASIC ID: 17100708 [OMAP1710 ver: 2.0] ASIC MODE ID: 00 PUBLIC ID: C90FCED89E26CEE26FF4B2FD72ADE6FBEC7EF266 ROOT KEY HASH: 49A97E826B93BA20B7ED0B082475C00500000000 ROM ID: 1DFD66132C872FD4 RAP Data : SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] EM0 ID: 00000295 EM1 ID: 00000B21 PUBLIC ID: 1B600210C3C100545351A9D66D6814726D33D128 ASIC MODE ID: 00 ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00 Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 FlashID0: 00EC 22E8 - 0000 6921 [Samsung K8S2815ETB,128 Mbits] type: NOR,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10 Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 RAP PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 FlashID0: 00EC 00A1 - 0080 0015 [Samsung KAL00T00EM-DGYY/66,1 Gbits] type: NAND,APE ExtBUSC: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF Algorithm: h3_sam_nand_xsr.fg [OMAP1710 UNISTORE-II-1.2.1 ALG] version: 1.49.0 revision: 0.0 size: 0x13AA0 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 APE PAPUBKEYS HASH: 5E8D0D504A0902E261268C14FCD8A2C9093523BC Original Imei: 35973800642985 Original Product code: 0541479 Bluetooth ID: 0018C53C262F Phone Type: RM-133 (Nokia N73) SW Version: V 05wk47v60.1 20-03-08 RM-133 (c) Nokia. Imei plain: 35973800642985-8 Product Code: 0541479 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST failed! SECURITY_TEST failed! SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted! tia

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
5220 simlock data corrupt , what to do ?	gsmsikar	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	8	07-03-2009 05:19
N70 Simlock data corrupted	silhouette	Nokia Base Band 5 ( BB-5 )	20	06-17-2009 18:53
N80 Simlock Data Corrupted	mtony969	Nokia Base Band 5 ( BB-5 )	0	10-05-2007 10:50

02-24-2010, 06:40	#2 (permalink)
Ramzan khan No Life Poster Join Date: Dec 2006 Posts: 522 Member: 405696 Status: Offline Thanks Meter: 148	1. You need to backup Certificate first. NPC ONLY. BB5 > Servie > Imei & Security - Select NPC from drop down menu. 2. You need to COMPLETELY ERASE the whole flash. BB5 > Flash > Advanced, Get Addr, untick SAFE Erase 3. Reflash all necessary data to phone. (ENO (if needed), MCU, PPM, etc) In this case, regarding with supported firmware for simlock rebuid, you will need to use OLDER firmware. 4. Flash MCU ONLY, same version with ENO firmware, that you flashed on first flashing 5. Next step is Certificate restore. Write back your NPC Backup. 6. REPAIR SIMLOCK - Determind first what SL level you got - It's SL2, so what? > Tick PA_SL2 > Choose Repair SIMLOCK > Tick make SIMLOCK RPL > Click Repair SPLock 7. REPAIR SD 8. Now check for your Certificate by Certificate Validation Tool BB5 > Service > Phone Test > Various > BB5 Certificate Validation In my case, phone doesn't has CCC and HWC, next step is: Write CLONE RPL 9. Proceed with SUPER SD Auth, and write PM after it. Load PM > Suped SD Auth 10. And the last step, you can update to the latest firmware. All done in 10 steps. This method also work for phone that can not be fully backuped. (cant' safe PM, can't local mode, blank screen, etc) !! DONT DO THIS ON SL3 !! If you got phones with corrupted simlock, the main thing is you need to clean it up first. That phone's PM is messy The whole steps as simple as: Backup NPC > Erase > Reflash > Restore NPC > Rebuild Simlock > Pm auth, write pm. Thats all if you not understand go to this link i all learn from here and copy paste just want to help you http://forum.gsmhosting.com/vbb/show...=726058&page=2