gsmilocos

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

Share Me


    SL3 SD Repair!! ATF Network!![what is this]

    HYPERTEK
    HYPERTEK
    Site Owner
    Site Owner


    Location : Banga Town
    Posts : 3948

    Character sheet
    INCSA:

    SL3 SD Repair!! ATF Network!![what is this] Empty SL3 SD Repair!! ATF Network!![what is this]

    Post by HYPERTEK Fri Mar 04, 2011 10:12 am

    HERE WE GO FOR ALL PLEASE READ CAREFULLY



    PART I

    So now I want to expose some VERY important Information to everyone
    because Nokia is playing some tricks on us again...

    Nokia stopped using PA_SL3 simlocks since 3 months ago. All new
    firmwares are now using PA_SIMLOC30 and it is NOT COMPATIBLE with
    the current phones in the Market. This is because PA_SIMLOC30 uses
    a different PM 120... So your old PA_SL3 PM 120 cannot work with
    these new firmwares. If you flash your PA_SL3 phone with PA_SIMLOC30
    firmware, then the PA_SIMLOC30 firmware cannot verify your PM 120
    and it will give you Simlock problems....


    For Demonstration Purposes, I will kill one of my X3-00 RM-540 by
    flashing it with the Latest Nokeeeya Firmware:

    Ok, here is Step 1: Check Phone and Show Simlock Versions:
    So here we a perfectly working X3-00 RM-540 with Firmware version 4.11.
    [You must be registered and logged in to see this link.]


    [You must be registered and logged in to see this image.]
    [You must be registered and logged in to see this link.]



    A quick check of the simlock version (vis BUSCHECK) shows us the phone
    is using PA_SL3 simlocks...


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]



    So now we try to flash the phone with firmware 8.54...
    If you are using ATF 7.00, then it will ask you if you want
    to check if this firmware is compatible with your Phone.


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]



    Click YES and it will show you this ERROR Message...
    This is because firmware 8.54 is using PA_SIMLOC30 simlocks...
    And it is not compatible with your phone [You must be registered and logged in to see this image.]

    A note to the other teams who still don't have a clue about this...
    Tell your programmer that this is the part where he should USB Sniff and
    copy-paste how we check the firmwares so that your end users will not
    kill phones using your software.


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]




    Since I promised you guys that I will kill this phone, let
    us click "NO" instead of yes [You must be registered and logged in to see this image.]....


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]




    Yey!!! Now it is flashing!!!


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]




    Crap!!,, NOW the Simlocks are Damaged!!! Why ? Why ?
    Why ?


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]



    Because Nokeeyah is now using PA_SIMLOC30 which it
    is impossible to Brute Force and is not compatible with
    your old PM 120 from PA_SL3.



    So the lesson from this story is:

    1. PA_SL3 Brute Force is OBSOLETE,, Nokeeyah is now
    using PA_SIMLOC30

    2. Never flash your phone with other tools that do not
    check Firmware Compatibility.

    3. Buy ATF Credits to fix your phone if you damaged it
    using other tools hehehehhe....


    Also, DO NOT WORRY... The SIMLOCKS ARE NOT DAMAGED!!!
    It is just NOT COMPATIBLE with the Firmware...
    Watch out for PART 2 of this story where I will fix the phone using The ATF Network



    Best Regards,
    X-Shadow
    HYPERTEK
    HYPERTEK
    Site Owner
    Site Owner


    Location : Banga Town
    Posts : 3948

    Character sheet
    INCSA:

    SL3 SD Repair!! ATF Network!![what is this] Empty Re: SL3 SD Repair!! ATF Network!![what is this]

    Post by HYPERTEK Fri Mar 04, 2011 10:15 am

    PART II


    How to Downgrade PA_SIMLOC30 phones back to a Compatible Firmware PA_SL3


    Killing phones is easy, especially because our special friends from
    Nokeeyah make it very easy for us to make mistakes even when
    using their original Phoenix, Nokia Care, NSU etc. Service Softwares.

    In the beginning, they did not want us to DOWNGRADE the Firmware
    of our Phones... and now, they don't even want us to UPGRADE the
    Firmware of our phones to the Latest versions!!! Why Nokeeyah?




    Anyway, here is how we can fix a phone from Nokiyos dirty tricks....







    STEP 1: As always, BACKUP RPL Certificates

    STEP 2: Same as STEP 1

    STEP 3: Same as STEP 2

    [You must be registered and logged in to see this link.]


    [You must be registered and logged in to see this image.]
    [You must be registered and logged in to see this link.]





    STEP 4: Read Out Full PM 0-400

    You can see here, PM 120 is still OK and it is not damaged at all!!!



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 5: ENABLE SL3 phone FULL ERASE option



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 6: FULL ERASE PHONE (Click SCAN then select the FLASH CHIP, then click ERASE)



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 7: Now FULL Flash the Phone with Firmware 4.11 (Or any PA_SL3 Firmware compatible with your Phone)

    SKIP BACKUP RPL and SKIP BACKUP SIMLOCKS...



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 8: Write BACK RPL



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 9: Authorize Phone via the ATF Network (Because phone is NEW HASH)



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]





    STEP 10: Stand Alone SX-4 and write the FULL PM BACKUP from STEP 4



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]







    Now Phone is 100% OK Again and Downgraded Back to version

    4.11 [You must be registered and logged in to see this image.]



    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]


    Code:
    MCU: V 04.11 09-12-09 RM-540 (c) Nokia           
    IMEI: 359367031341159
    Model : Nokia X3-00
    Product Serial Number: 0
    Default SN Type      : 0
    MCU SW Version      : V 04.11 09-12-09 RM-540 (c) Nokia            T
    BT MCM Version      : 1673-46034
    PPM Version          : V 04.11 09-12-09 RM-540 (c) Nokia
    RFIC Version        : 0831
    DSP Version          : ICPR91_09w44_RC
    LCD Version          : SEIKO
    Content Pack Version : Content: ctv ph V 04.11 09-12-09 RM-540 (c) Nokia
    AHNE Version        : 41
    Retu Version        : 40
    Tahvo Version        : 00
      ********  Reading SimLock  ********
    Unable to read SP Data..
      ********  Reading SimLock  ********
    Unable to read SP Data..
    SIMLOCK_TEST      : FAILED
    SECURITY_TEST          : PASSED
    SECURITY_CODE          : 12345
    PHONE_MODE              : TEST MODE
                                                   
    ================================================
              Dynamic Camera Configuration         
    ================================================
    DCC ID  : NI00IIIIRR030C20C607
    DCC Ver: 003003
    Status  : OK
     
    ================================================
          SX4 Custom Keys Stand Alone Edition     
    ================================================
    *** WARNING: Current Super Dongle Keys are Invalid! ***
    Attempting to write New Super Dongle Keys...

    MCU: V 04.11 09-12-09 RM-540 (c) Nokia           
    IMEI: 359367031341159
    Model : Nokia X3-00
    Product Serial Number: 0
    Default SN Type      : 0
    MCU SW Version      : V 04.11 09-12-09 RM-540 (c) Nokia            T
    BT MCM Version      : 1673-46034
    PPM Version          : V 04.11 09-12-09 RM-540 (c) Nokia
    RFIC Version        : 0831
    DSP Version          : ICPR91_09w44_RC
    LCD Version          : SEIKO
    Content Pack Version : Content: ctv ph V 04.11 09-12-09 RM-540 (c) Nokia
    AHNE Version        : 41
    Retu Version        : 40
    Tahvo Version        : 00
      ********  Reading SimLock  ********
    Unable to read SP Data..
      ********  Reading SimLock  ********
    Unable to read SP Data..
    SIMLOCK_TEST      : FAILED
    SECURITY_TEST          : PASSED
    SECURITY_CODE          : 12345
    PHONE_MODE              : TEST MODE
                                                   
    ================================================
              Dynamic Camera Configuration         
    ================================================
    DCC ID  : NI00IIIIRR030C20C607
    DCC Ver: 003003
    Status  : OK
     
    ===================================================
          Super Dongle RPL Stand Alone Edition       
    ===================================================
    Generating Super Dongle RPL...                   
    (This may take upto 30 Seconds on New RAPIDO HASH)
    Sending Superdongle RPL...
    OK: Super Dongle RPL accepted

    Successfully done.
    ================================================
          SX4 Custom Keys Stand Alone Edition     
    ================================================
    >>> : SX4 Auth Successfull
    Selected PM File: C:\AdvanceBox Turbo Flasher\Nokia\Backup\359367031341159\359367031341159_0-400_32403.pm
    Start Uploading PM...
    Field : 1 Sub : 0 Byte(s): 116  - Ok
    Field : 1 Sub : 1 Byte(s): 4  - Ok
    Field : 1 Sub : 2 Byte(s): 88  - Ok
    Field : 1 Sub : 4 Byte(s): 112  - Ok
    Field : 1 Sub : 5 Byte(s): 4  - Ok
    Field : 1 Sub : 6 Byte(s): 88  - Ok
    Field : 1 Sub : 8 Byte(s): 112  - Ok
    Field : 1 Sub : 13 Byte(s): 88  - Ok
    Field : 1 Sub : 15 Byte(s): 4  - Ok
    Field : 1 Sub : 16 Byte(s): 88  - Ok
    Field : 1 Sub : 18 Byte(s): 88  - Ok
    Field : 1 Sub : 20 Byte(s): 88  - Ok
    Field : 1 Sub : 22 Byte(s): 16  - Ok
    Field : 1 Sub : 23 Byte(s): 4  - Ok
    Field : 1 Sub : 24 Byte(s): 84  - Ok
    Field : 1 Sub : 25 Byte(s): 16  - Ok
    Field : 1 Sub : 29 Byte(s): 8  - Ok
    Field : 2 Sub : 0 Byte(s): 768  - Ok
    Field : 4 Sub : 1 Byte(s): 800  - Ok
    Field : 4 Sub : 3 Byte(s): 12  - Ok
    Field : 4 Sub : 4 Byte(s): 8  - Ok
    Field : 4 Sub : 5 Byte(s): 8  - Ok
    Field : 4 Sub : 6 Byte(s): 8  - Ok
    Field : 4 Sub : 9 Byte(s): 8  - Ok
    Field : 4 Sub : 18 Byte(s): 80  - Ok
    Field : 4 Sub : 19 Byte(s): 4  - Ok
    Field : 4 Sub : 28 Byte(s): 4  - Ok
    Field : 8 Sub : 0 Byte(s): 4  - Ok
    Field : 8 Sub : 3 Byte(s): 128  - Ok
    Field : 8 Sub : 4 Byte(s): 128  - Ok
    Field : 8 Sub : 8 Byte(s): 8  - Ok
    Field : 11 Sub : 0 Byte(s): 4  - Ok
    Field : 11 Sub : 1 Byte(s): 4  - Ok
    Field : 11 Sub : 2 Byte(s): 4  - Ok
    Field : 11 Sub : 3 Byte(s): 4  - Ok
    Field : 11 Sub : 4 Byte(s): 244  - Ok
    Field : 12 Sub : 0 Byte(s): 104  - Ok
    Field : 13 Sub : 0 Byte(s): 4  - Ok
    Field : 13 Sub : 1 Byte(s): 4  - Ok
    Field : 13 Sub : 2 Byte(s): 4  - Ok
    Field : 13 Sub : 3 Byte(s): 4  - Ok
    Field : 13 Sub : 4 Byte(s): 4  - Ok
    Field : 13 Sub : 5 Byte(s): 4  - Ok
    Field : 13 Sub : 6 Byte(s): 4  - Ok
    Field : 13 Sub : 7 Byte(s): 4  - Ok
    Field : 13 Sub : 8 Byte(s): 4  - Ok
    Field : 13 Sub : 9 Byte(s): 4  - Ok
    Field : 13 Sub : 10 Byte(s): 4  - Ok
    Field : 13 Sub : 11 Byte(s): 48  - Ok
    Field : 13 Sub : 12 Byte(s): 4  - Ok
    Field : 13 Sub : 13 Byte(s): 4  - Ok
    Field : 13 Sub : 14 Byte(s): 4  - Ok
    Field : 13 Sub : 15 Byte(s): 888  - Ok
    Field : 13 Sub : 16 Byte(s): 4  - Ok
    Field : 13 Sub : 17 Byte(s): 4  - Ok
    Field : 13 Sub : 18 Byte(s): 4  - Ok
    Field : 13 Sub : 19 Byte(s): 8  - Ok
    Field : 13 Sub : 20 Byte(s): 4  - Ok
    Field : 13 Sub : 21 Byte(s): 4  - Ok
    Field : 13 Sub : 22 Byte(s): 4  - Ok
    Field : 13 Sub : 23 Byte(s): 4  - Ok
    Field : 13 Sub : 24 Byte(s): 4  - Ok
    Field : 13 Sub : 25 Byte(s): 4  - Ok
    Field : 13 Sub : 26 Byte(s): 4  - Ok
    Field : 13 Sub : 27 Byte(s): 4  - Ok
    Field : 13 Sub : 28 Byte(s): 4  - Ok
    Field : 13 Sub : 29 Byte(s): 4  - Ok
    Field : 13 Sub : 30 Byte(s): 4  - Ok
    Field : 13 Sub : 31 Byte(s): 4  - Ok
    Field : 13 Sub : 32 Byte(s): 4  - Ok
    Field : 13 Sub : 33 Byte(s): 4  - Ok
    Field : 13 Sub : 34 Byte(s): 4  - Ok
    Field : 13 Sub : 35 Byte(s): 4  - Ok
    Field : 13 Sub : 36 Byte(s): 4  - Ok
    Field : 13 Sub : 37 Byte(s): 4  - Ok
    Field : 13 Sub : 38 Byte(s): 4  - Ok
    Field : 13 Sub : 39 Byte(s): 4  - Ok
    Field : 13 Sub : 40 Byte(s): 4  - Ok
    Field : 13 Sub : 41 Byte(s): 4  - Ok
    Field : 13 Sub : 42 Byte(s): 4  - Ok
    Field : 13 Sub : 43 Byte(s): 4  - Ok
    Field : 13 Sub : 44 Byte(s): 4  - Ok
    Field : 13 Sub : 45 Byte(s): 4  - Ok
    Field : 13 Sub : 46 Byte(s): 4  - Ok
    Field : 13 Sub : 47 Byte(s): 4  - Ok
    Field : 13 Sub : 48 Byte(s): 4  - Ok
    Field : 13 Sub : 49 Byte(s): 4  - Ok
    Field : 13 Sub : 50 Byte(s): 4  - Ok
    Field : 13 Sub : 51 Byte(s): 4  - Ok
    Field : 13 Sub : 52 Byte(s): 4  - Ok
    Field : 13 Sub : 53 Byte(s): 4  - Ok
    Field : 13 Sub : 54 Byte(s): 4  - Ok
    Field : 13 Sub : 55 Byte(s): 4  - Ok
    Field : 13 Sub : 56 Byte(s): 4  - Ok
    Field : 13 Sub : 57 Byte(s): 4  - Ok
    Field : 13 Sub : 58 Byte(s): 4  - Ok
    Field : 13 Sub : 59 Byte(s): 4  - Ok
    Field : 13 Sub : 60 Byte(s): 4  - Ok
    Field : 13 Sub : 61 Byte(s): 4  - Ok
    Field : 13 Sub : 62 Byte(s): 4  - Ok
    Field : 13 Sub : 63 Byte(s): 4  - Ok
    Field : 13 Sub : 64 Byte(s): 4  - Ok
    Field : 13 Sub : 65 Byte(s): 4  - Ok
    Field : 13 Sub : 66 Byte(s): 4  - Ok
    Field : 13 Sub : 67 Byte(s): 4  - Ok
    Field : 13 Sub : 68 Byte(s): 4  - Ok
    Field : 13 Sub : 69 Byte(s): 4  - Ok
    Field : 13 Sub : 70 Byte(s): 4  - Ok
    Field : 13 Sub : 71 Byte(s): 4  - Ok
    Field : 13 Sub : 72 Byte(s): 4  - Ok
    Field : 13 Sub : 73 Byte(s): 4  - Ok
    Field : 13 Sub : 74 Byte(s): 4  - Ok
    Field : 13 Sub : 75 Byte(s): 4  - Ok
    Field : 13 Sub : 76 Byte(s): 4  - Ok
    Field : 13 Sub : 77 Byte(s): 4  - Ok
    Field : 13 Sub : 78 Byte(s): 4  - Ok
    Field : 13 Sub : 79 Byte(s): 4  - Ok
    Field : 13 Sub : 80 Byte(s): 4  - Ok
    Field : 13 Sub : 81 Byte(s): 4  - Ok
    Field : 13 Sub : 82 Byte(s): 4  - Ok
    Field : 13 Sub : 83 Byte(s): 4  - Ok
    Field : 13 Sub : 84 Byte(s): 4  - Ok
    Field : 13 Sub : 85 Byte(s): 4  - Ok
    Field : 13 Sub : 86 Byte(s): 4  - Ok
    Field : 13 Sub : 87 Byte(s): 4  - Ok
    Field : 13 Sub : 88 Byte(s): 4  - Ok
    Field : 13 Sub : 89 Byte(s): 4  - Ok
    Field : 13 Sub : 90 Byte(s): 4  - Ok
    Field : 13 Sub : 91 Byte(s): 4  - Ok
    Field : 13 Sub : 92 Byte(s): 4  - Ok
    Field : 13 Sub : 93 Byte(s): 4  - Ok
    Field : 13 Sub : 94 Byte(s): 4  - Ok
    Field : 13 Sub : 95 Byte(s): 4  - Ok
    Field : 13 Sub : 96 Byte(s): 4  - Ok
    Field : 13 Sub : 97 Byte(s): 4  - Ok
    Field : 13 Sub : 98 Byte(s): 4  - Ok
    Field : 13 Sub : 99 Byte(s): 4  - Ok
    Field : 13 Sub : 100 Byte(s): 4  - Ok
    Field : 13 Sub : 101 Byte(s): 4  - Ok
    Field : 13 Sub : 102 Byte(s): 4  - Ok
    Field : 13 Sub : 103 Byte(s): 4  - Ok
    Field : 13 Sub : 104 Byte(s): 4  - Ok
    Field : 13 Sub : 105 Byte(s): 4  - Ok
    Field : 13 Sub : 106 Byte(s): 4  - Ok
    Field : 13 Sub : 107 Byte(s): 4  - Ok
    Field : 13 Sub : 108 Byte(s): 4  - Ok
    Field : 13 Sub : 109 Byte(s): 4  - Ok
    Field : 13 Sub : 110 Byte(s): 4  - Ok
    Field : 13 Sub : 111 Byte(s): 4  - Ok
    Field : 13 Sub : 112 Byte(s): 4  - Ok
    Field : 13 Sub : 113 Byte(s): 4  - Ok
    Field : 13 Sub : 114 Byte(s): 4  - Ok
    Field : 13 Sub : 115 Byte(s): 4  - Ok
    Field : 13 Sub : 116 Byte(s): 4  - Ok
    Field : 13 Sub : 117 Byte(s): 4  - Ok
    Field : 13 Sub : 118 Byte(s): 4  - Ok
    Field : 13 Sub : 119 Byte(s): 4  - Ok
    Field : 13 Sub : 120 Byte(s): 4  - Ok
    Field : 13 Sub : 121 Byte(s): 4  - Ok
    Field : 13 Sub : 122 Byte(s): 4  - Ok
    Field : 13 Sub : 123 Byte(s): 8  - Ok
    Field : 13 Sub : 124 Byte(s): 4  - Ok
    Field : 13 Sub : 125 Byte(s): 4  - Ok
    Field : 13 Sub : 126 Byte(s): 4  - Ok
    Field : 13 Sub : 127 Byte(s): 4  - Ok
    Field : 13 Sub : 128 Byte(s): 4  - Ok
    Field : 13 Sub : 129 Byte(s): 4  - Ok
    Field : 13 Sub : 130 Byte(s): 4  - Ok
    Field : 13 Sub : 131 Byte(s): 4  - Ok
    Field : 13 Sub : 132 Byte(s): 4  - Ok
    Field : 13 Sub : 133 Byte(s): 4  - Ok
    Field : 13 Sub : 134 Byte(s): 4  - Ok
    Field : 13 Sub : 135 Byte(s): 4  - Ok
    Field : 13 Sub : 136 Byte(s): 4  - Ok
    Field : 13 Sub : 137 Byte(s): 4  - Ok
    Field : 13 Sub : 138 Byte(s): 4  - Ok
    Field : 13 Sub : 139 Byte(s): 4  - Ok
    Field : 13 Sub : 140 Byte(s): 4  - Ok
    Field : 13 Sub : 141 Byte(s): 4  - Ok
    Field : 13 Sub : 142 Byte(s): 4  - Ok
    Field : 13 Sub : 143 Byte(s): 4  - Ok
    Field : 13 Sub : 144 Byte(s): 4  - Ok
    Field : 13 Sub : 145 Byte(s): 8  - Ok
    Field : 13 Sub : 146 Byte(s): 4  - Ok
    Field : 13 Sub : 147 Byte(s): 4  - Ok
    Field : 13 Sub : 148 Byte(s): 4  - Ok
    Field : 13 Sub : 149 Byte(s): 4  - Ok
    Field : 13 Sub : 150 Byte(s): 4  - Ok
    Field : 13 Sub : 151 Byte(s): 4  - Ok
    Field : 13 Sub : 152 Byte(s): 4  - Ok
    Field : 13 Sub : 153 Byte(s): 4  - Ok
    Field : 13 Sub : 154 Byte(s): 4  - Ok
    Field : 13 Sub : 155 Byte(s): 4  - Ok
    Field : 13 Sub : 156 Byte(s): 4  - Ok
    Field : 13 Sub : 157 Byte(s): 4  - Ok
    Field : 13 Sub : 158 Byte(s): 4  - Ok
    Field : 13 Sub : 159 Byte(s): 4  - Ok
    Field : 13 Sub : 160 Byte(s): 4  - Ok
    Field : 13 Sub : 161 Byte(s): 4  - Ok
    Field : 13 Sub : 162 Byte(s): 4  - Ok
    Field : 13 Sub : 163 Byte(s): 4  - Ok
    Field : 13 Sub : 164 Byte(s): 4  - Ok
    Field : 13 Sub : 165 Byte(s): 4  - Ok
    Field : 13 Sub : 166 Byte(s): 4  - Ok
    Field : 31 Sub : 4 Byte(s): 16  - Ok
    Field : 42 Sub : 0 Byte(s): 4  - Ok
    Field : 42 Sub : 1 Byte(s): 12  - Ok
    Field : 42 Sub : 2 Byte(s): 36  - Ok
    Field : 42 Sub : 3 Byte(s): 36  - Ok
    Field : 42 Sub : 4 Byte(s): 36  - Ok
    Field : 42 Sub : 5 Byte(s): 36  - Ok
    Field : 42 Sub : 6 Byte(s): 36  - Ok
    Field : 42 Sub : 7 Byte(s): 40  - Ok
    Field : 42 Sub : 8 Byte(s): 40  - Ok
    Field : 42 Sub : 9 Byte(s): 40  - Ok
    Field : 42 Sub : 10 Byte(s): 40  - Ok
    Field : 42 Sub : 11 Byte(s): 40  - Ok
    Field : 42 Sub : 12 Byte(s): 40  - Ok
    Field : 42 Sub : 13 Byte(s): 40  - Ok
    Field : 42 Sub : 14 Byte(s): 40  - Ok
    Field : 42 Sub : 15 Byte(s): 40  - Ok
    Field : 42 Sub : 16 Byte(s): 40  - Ok
    Field : 42 Sub : 17 Byte(s): 40  - Ok
    Field : 42 Sub : 18 Byte(s): 40  - Ok
    Field : 42 Sub : 19 Byte(s): 40  - Ok
    Field : 42 Sub : 20 Byte(s): 40  - Ok
    Field : 42 Sub : 21 Byte(s): 40  - Ok
    Field : 42 Sub : 22 Byte(s): 40  - Ok
    Field : 42 Sub : 23 Byte(s): 40  - Ok
    Field : 42 Sub : 24 Byte(s): 40  - Ok
    Field : 42 Sub : 25 Byte(s): 40  - Ok
    Field : 42 Sub : 26 Byte(s): 40  - Ok
    Field : 50 Sub : 0 Byte(s): 4  - Ok
    Field : 54 Sub : 0 Byte(s): 4  - Ok
    Field : 88 Sub : 0 Byte(s): 36  - Ok
    Field : 96 Sub : 0 Byte(s): 4  - Ok
    Field : 107 Sub : 0 Byte(s): 24  - Ok
    Field : 107 Sub : 1 Byte(s): 92  - Ok
    Field : 107 Sub : 2 Byte(s): 72  - Ok
    Field : 107 Sub : 3 Byte(s): 72  - Ok
    Field : 107 Sub : 25 Byte(s): 136  - Ok
    Field : 107 Sub : 26 Byte(s): 12  - Ok
    Field : 116 Sub : 0 Byte(s): 4  - Ok
    Field : 116 Sub : 1 Byte(s): 12  - Ok
    Field : 116 Sub : 2 Byte(s): 36  - Ok
    Field : 116 Sub : 3 Byte(s): 36  - Ok
    Field : 116 Sub : 4 Byte(s): 36  - Ok
    Field : 116 Sub : 5 Byte(s): 36  - Ok
    Field : 116 Sub : 6 Byte(s): 36  - Ok
    Field : 116 Sub : 7 Byte(s): 40  - Ok
    Field : 116 Sub : 8 Byte(s): 40  - Ok
    Field : 116 Sub : 9 Byte(s): 40  - Ok
    Field : 116 Sub : 10 Byte(s): 40  - Ok
    Field : 116 Sub : 11 Byte(s): 40  - Ok
    Field : 116 Sub : 12 Byte(s): 40  - Ok
    Field : 116 Sub : 13 Byte(s): 40  - Ok
    Field : 116 Sub : 14 Byte(s): 40  - Ok
    Field : 116 Sub : 15 Byte(s): 40  - Ok
    Field : 116 Sub : 16 Byte(s): 40  - Ok
    Field : 120 Sub : 0 Byte(s): 944  - Ok
    Field : 120 Sub : 1 Byte(s): 160  - Ok
    Field : 120 Sub : 2 Byte(s): 132  - Ok
    Field : 120 Sub : 3 Byte(s): 112  - Ok
    Field : 193 Sub : 2 Byte(s): 8  - Ok
    Field : 193 Sub : 3 Byte(s): 32  - Ok
    Field : 193 Sub : 4 Byte(s): 32  - Ok
    Field : 193 Sub : 9 Byte(s): 64  - Ok
    Field : 218 Sub : 0 Byte(s): 4  - Ok
    Field : 238 Sub : 1 Byte(s): 4  - Ok
    Field : 301 Sub : 0 Byte(s): 4  - Ok
    Field : 301 Sub : 1 Byte(s): 12  - Ok
    Field : 301 Sub : 2 Byte(s): 36  - Ok
    Field : 301 Sub : 3 Byte(s): 36  - Ok
    Field : 301 Sub : 4 Byte(s): 36  - Ok
    Field : 301 Sub : 5 Byte(s): 36  - Ok
    Field : 301 Sub : 6 Byte(s): 36  - Ok
    Field : 301 Sub : 7 Byte(s): 40  - Ok
    Field : 301 Sub : 8 Byte(s): 40  - Ok
    Field : 301 Sub : 9 Byte(s): 40  - Ok
    Field : 301 Sub : 10 Byte(s): 40  - Ok
    Field : 301 Sub : 11 Byte(s): 40  - Ok
    Field : 301 Sub : 12 Byte(s): 40  - Ok
    Field : 301 Sub : 13 Byte(s): 40  - Ok
    Field : 301 Sub : 14 Byte(s): 40  - Ok
    Field : 301 Sub : 15 Byte(s): 40  - Ok
    Field : 301 Sub : 16 Byte(s): 40  - Ok
    Field : 308 Sub : 0 Byte(s): 4  - Failed
    Field : 308 Sub : 1 Byte(s): 8192  - Failed
    Field : 308 Sub : 2 Byte(s): 4  - Failed
    Field : 308 Sub : 3 Byte(s): 4  - Failed
    Field : 308 Sub : 4 Byte(s): 4  - Failed
    Field : 308 Sub : 5 Byte(s): 12  - Failed
    Field : 308 Sub : 6 Byte(s): 4  - Failed
    Field : 308 Sub : 7 Byte(s): 4  - Failed
    Field : 308 Sub : 8 Byte(s): 4  - Failed
    Field : 308 Sub : 9 Byte(s): 40  - Failed
    Field : 309 Sub : 0 Byte(s): 4  - Ok
    Field : 309 Sub : 1 Byte(s): 4  - Ok
    Field : 309 Sub : 2 Byte(s): 12  - Ok
    Field : 309 Sub : 4 Byte(s): 12  - Ok
    Field : 309 Sub : 5 Byte(s): 12  - Ok
    Field : 309 Sub : 7 Byte(s): 12  - Ok
    Field : 309 Sub : 8 Byte(s): 12  - Ok
    Field : 309 Sub : 17 Byte(s): 12  - Ok
    Field : 322 Sub : 0 Byte(s): 4  - Ok
    Field : 334 Sub : 0 Byte(s): 4  - Ok
    Field : 339 Sub : 0 Byte(s): 512  - Ok
    Field : 339 Sub : 1 Byte(s): 512  - Ok
    Field : 341 Sub : 0 Byte(s): 4  - Ok
    Field : 341 Sub : 3 Byte(s): 4  - Ok
    Field : 341 Sub : 4 Byte(s): 4416  - Ok
    Field : 354 Sub : 0 Byte(s): 4  - Ok
    Field : 355 Sub : 0 Byte(s): 14608  - Ok
    Field : 355 Sub : 1 Byte(s): 14608  - Ok
    Field : 356 Sub : 0 Byte(s): 4  - Ok
    Field : 362 Sub : 0 Byte(s): 4  - Ok
    Field : 362 Sub : 1 Byte(s): 144  - Ok
    PM  Upload Done!...

    Done,, new HASHES TOTALLY PWNED !!!


    ANG LIWANAG YUN PALA NOW ALAM NA NATIN LAHAT PAANO

    SA MGA HINDI NAKAKA INTINDI

    ABA ANDITO LANG AKO



    Originally Posted by Advance-Box View Post
    @-=Meltech09=-

    Well it is obvious that some teams may not be aware...

    That NEW Protocol is only compatible with 3 kinds of CPUs (FOR USB FLASHING, RAP3Gv30 new loaders does not work for USB)...

    RAP3Gv40
    RAPUYAMA
    and
    BROADCOM



    That is why these teams who still use other people's box (UFS) and cannot design
    their own boxes, want you to believe that FBUS is no longer usefull.

    If FBUS is no longer useful, then why do they still support UFS Interface?

    If FBUS is no longer useful, why cant they make RPL Backup's using USB cable to
    the following CPUs;

    RAP3Gv2 - N70, 6630
    RAP3Gv3 - 5130c, 7210c, 2690
    RAPIDO - N97, C6-00, X6-00, 5233, 5800, E71, E63 etc...


    And then what? They tell you "Please use UFS Box to backup RPL for these phones..."
    How are you suppose to do this when UFS Box does not support New Protocol and
    phones like C6-00, X6-00, 5233, new 5800 etc etc... cannot support OLD Protocol
    Loaders? Are they totally out of their minds???

    And what, they are selling USB Flashing??? USB flashing is 100% free:

    1. Cracked Phoenix
    2. Nokia Care
    3. NSU
    4. Ovi Suite
    5. Cracked JAF

    etc..
    etc..


    So they are telling you... Please do not waste your money on buying FBUS cables...
    Instead, waste your money in paying for a NON FREE USB Flasher.

    And really, we should expect that they can make a better USB flasher than Nokia Engineers?

    Come on... People in gsm are not that stupid anymore...


    B/R
    HYPERTEK
    HYPERTEK
    Site Owner
    Site Owner


    Location : Banga Town
    Posts : 3948

    Character sheet
    INCSA:

    SL3 SD Repair!! ATF Network!![what is this] Empty Re: SL3 SD Repair!! ATF Network!![what is this]

    Post by HYPERTEK Fri Mar 04, 2011 10:16 am



    Ito na ang sample na atf lang makakagawa as off today





    Here are logs from X-Shadow post:

    Here the phone shows SUPER DONGLE Problem


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    When we try with "Stand-Alone" SD Repair, you will see this message


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    So go to "The ATF Network" and Authorize this Phone...


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    After it is "Authorized" you can stand alone SD Repair it!


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    Now SD is repaired... but....


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    We need to SX-4 this phone and upload PM 1 and 309 as well


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    So here SX-4 was a Success (Stand Alone as well)


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    SD Check Button shows everything is OK


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    Self Tests show everything is OK as well


    [You must be registered and logged in to see this image.]
    [You must be
    registered and logged in to see this image.]

    Sponsored content


    SL3 SD Repair!! ATF Network!![what is this] Empty Re: SL3 SD Repair!! ATF Network!![what is this]

    Post by Sponsored content


      Current date/time is Sat Nov 16, 2024 6:55 am