topclickgsm

Topclickgsm is in need of Forum Moderator

contact Admin

Join the forum, it's quick and easy

topclickgsm

Topclickgsm is in need of Forum Moderator

contact Admin

topclickgsm

Would you like to react to this message? Create an account in a few clicks or log in to continue.
topclickgsm

Keywords

Latest topics

» TEST2MNKMKMKMKNJNJK M, , MKN
tips on how to use some sl3 simlock invalid or common cause contact service EmptyTue Feb 18, 2014 5:34 am by topclickgsmadmin

» TEST1234MKMKMKKMKLLKKLL;.LMKO
tips on how to use some sl3 simlock invalid or common cause contact service EmptyTue Feb 18, 2014 5:24 am by topclickgsmadmin

» bago lang po mga sir................
tips on how to use some sl3 simlock invalid or common cause contact service EmptyFri Sep 21, 2012 8:23 am by topclickgsmadmin

» Medusa box,flasher updates.....
tips on how to use some sl3 simlock invalid or common cause contact service EmptyFri Jun 29, 2012 10:20 am by topclickgsmadmin

» Adding forum section request
tips on how to use some sl3 simlock invalid or common cause contact service EmptyFri Jun 29, 2012 8:57 am by topclickgsmadmin

» ITRANSFER FULL FOR ALL IOS DEVICE
tips on how to use some sl3 simlock invalid or common cause contact service EmptyMon Dec 19, 2011 3:31 pm by topclickgsmadmin

» unblock the bloked sim..talk en texk and smart
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Dec 14, 2011 5:41 am by topclickgsmadmin

» bagong salta idol pa welcome po
tips on how to use some sl3 simlock invalid or common cause contact service EmptySun Nov 20, 2011 2:58 pm by buyvpn

» zte mf631 claro unlock done
tips on how to use some sl3 simlock invalid or common cause contact service EmptySat Nov 19, 2011 2:40 pm by syrup

» b-series new config...................
tips on how to use some sl3 simlock invalid or common cause contact service EmptyThu Nov 17, 2011 1:35 pm by strikeone

» ALMOST ALL TRICK FOR THOSE USING VPN CONNECTION..
tips on how to use some sl3 simlock invalid or common cause contact service EmptyThu Nov 17, 2011 5:04 am by topclickgsmadmin

» marquez trick tyo beat paquio kuno??????????
tips on how to use some sl3 simlock invalid or common cause contact service EmptyTue Nov 15, 2011 1:24 pm by gilyn

» 6303 nokia then shut off done
tips on how to use some sl3 simlock invalid or common cause contact service EmptySat Oct 01, 2011 2:23 pm by gilyn

» C3 mic problem/mouthpiece problem SIMPLE TRICK
tips on how to use some sl3 simlock invalid or common cause contact service EmptyFri Sep 30, 2011 10:09 am by gilyn

» MICRO BOX NEWS & UPDATES................................................
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 3:14 pm by topclickgsmadmin

» ADVANCE BOX (ATF) NEWS & UPDATES
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 1:52 pm by topclickgsmadmin

» MX-KEY NEWS & UPDATES VER.3.5 REV 1.3
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 1:26 pm by topclickgsmadmin

» SETOOL UPDATES...LATEST VER .................
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 1:16 pm by topclickgsmadmin

» Fix Error 1603 When Restoring iPhone With iTunes
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 11:24 am by topclickgsmadmin

» IPHONE 5 TOUCH PANEL DEFECT
tips on how to use some sl3 simlock invalid or common cause contact service EmptyWed Sep 28, 2011 10:18 am by topclickgsmadmin

April 2024

MonTueWedThuFriSatSun
1234567
891011121314
15161718192021
22232425262728
2930     

Calendar Calendar

Navigation

Top posting users this month

No user

    tips on how to use some sl3 simlock invalid or common cause contact service

    gilyn
    gilyn
    Topclickgsm Support Team
    Topclickgsm Support Team


    Posts : 24
    Thanks : 18046
    Thanked : 9004
    Join date : 2011-07-30

    tips on how to use some sl3 simlock invalid or common cause contact service Empty tips on how to use some sl3 simlock invalid or common cause contact service

    Post by gilyn Sat Aug 06, 2011 8:09 pm

    here is a sample

    5130c contact service

    caused by

    SIMLOCK invalid!
    SUPERDONGLE_KEY invalid!
    - WD timer enabled, phone will reboot itself after 3 min.
    SIMLOCK_TEST failed
    SECURITY_TEST passed


    SIMLOCK_DATA corrupted!

    most of us knows the solution for this.It can only be done by unlocking for simlock test failed.since its sl3 it needs brutforce and to much expensive


    but here is the cheapiest way to remove contact service


    backup full pm data

    then full erase the phone by getting its address


    after erasing make full flash then here is the result


    Using device: UFS_USB V2.8 (c) SarasSoft 2007.
    Driver: ohci:hub:hub:UFS2XX, ver: 1.6.6.0 , NTMP ver: 1.6.6.1
    Module ver: 1.0.0.17743(23-06-2011), Library ver: 1.0.0.11773(23-06-2011)
    Processing MCU file: rm495__07.97.mcusw
    [BB5,BB5 ALGORITHM] size: 18.20 MB
    Supported Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
    CMT Data :
    SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
    EM0 ID: 00000296
    EM1 ID: 00000B22
    PUBLIC ID: 2050001440EF7D56ED1F79A87E402C3D5AA5BC07
    ASIC MODE ID: 00
    ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
    ROM ID: 273F6D55DFAAF68F
    SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
    Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    Storage0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
    Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
    Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
    TransmissionMode: 16Bit
    Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
    Supported 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
    CMT PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
    TransmissionMode: DDR&TX2
    Storing certificate [NPC, VARIANT, R&D, CCC, HWC] ...OK
    Erase size: 21 MB
    CMT FLASH,NOR area [00000000-000006BF] erased in 0.761 s
    CMT FLASH,NOR area [000006C0-0001FFFF] erased in 0.130 s
    CMT FLASH,NOR area [00040000-000BFFFF] erased in 3.034 s
    CMT FLASH,NOR area [000C0000-0013FFFF] erased in 0.210 s
    CMT FLASH,NOR area [00140000-0137FFFF] erased in 29.072 s
    CMT FLASH,NOR area [01380000-0151FFFF] erased in 10.084 s
    Flash programming ...
    CMT NOLO block sent
    CMT KEYS block sent
    CMT PRIMAPP block sent
    CMT PASUBTOC block sent
    CMT PAPUBKEYS: 0C917F11 [RAP Certificate 164 v.1] sent
    CMT UPDAPP block sent
    CMT DSP0 block sent
    CMT MCUSW block sent
    Programming completed in 2 min 45.198 s
    Processing PPM file: rm495__07.97.ppm_mh
    [BB5,BB5 ALGORITHM] size: 7.04 MB
    Supported Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
    CMT Data :
    SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
    EM0 ID: 00000296
    EM1 ID: 00000B22
    PUBLIC ID: 2050001440EF7D56ED1F79A87E402C3D5AA5BC07
    ASIC MODE ID: 00
    ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
    ROM ID: 273F6D55DFAAF68F
    SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
    Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    Storage0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
    Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
    Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
    TransmissionMode: 16Bit
    Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
    Supported 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
    CMT PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
    TransmissionMode: DDR&TX2
    Erase size: 8.62 MB
    CMT FLASH,NOR area [01520000-01DBFFFF] erased in 2.043 s
    Flash programming ...
    Programming completed in 1 min 3.651 s
    Processing CNT file: rm495__07.97.image_mr_blu
    [BB5,BB5 ALGORITHM] page size: 128 K size: 10.39 MB
    Supported Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
    NOR page size in the phone is 128 K.
    CMT Data :
    SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
    EM0 ID: 00000296
    EM1 ID: 00000B22
    PUBLIC ID: 2050001440EF7D56ED1F79A87E402C3D5AA5BC07
    ASIC MODE ID: 00
    ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
    ROM ID: 273F6D55DFAAF68F
    SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
    Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
    Storage0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
    Storage content: 0000 0000 0000 0000 0000 0000 0000 0000
    Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
    TransmissionMode: 16Bit
    Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
    Supported 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
    CMT PAPUBKEYS HASH: 0C917F11196FDB7378C18EF7260698CA4489DCA0
    TransmissionMode: DDR&TX2
    Erase size: 34 MB
    CMT FLASH,NOR area [01DC0000-0215FFFF] erased in 25.898 s
    CMT FLASH,NOR area [02160000-03FBFFFF] erased in 7.060 s
    Converting UCP blocks to 128 K.
    Flash programming ...
    Programming completed in 1 min 30.630 s
    Total time for flashing process(boot+erase+write) was 7 min 30.047 s

    Phone Type: RM-495 (Nokia 5130c-2)
    SW Version: V 07.97 13-09-10 RM-495 (c) Nokia
    Imei plain: 12345610654321-?
    Battery voltage: 4754 mV, current: 0 mA
    Language Pack:
    - not available.

    SIMLOCK invalid!
    SUPERDONGLE_KEY invalid!
    - WD timer enabled, phone will reboot itself after 3 min.
    SIMLOCK_TEST passed
    SECURITY_TEST passed


    Imei plain is invalid !!!
    SIMLOCK_DATA corrupted!
    SIMLOCK_DATA corrupted!


    now contact service removed..but the only prob is that phone restarts it self every 3min

    resulting imei plain is invalid...



    good thing is u can use ur phone/ bom bom bom bom bom bom bom bom

      Current date/time is Fri Apr 19, 2024 3:16 pm