Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

zte F102 unlocking error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • zte F102 unlocking error

    sir we are not realise why it error appears
    its version is supported

    DC - Unlocker 2 Client 1.00.0717

    Detecting phone :

    selection :
    manufacturer - ZTE phones
    model - ZTE F102/F102i

    Found Phone : F102
    Model : ZTE F102/F102i
    IMEI : 356740031181101
    Firmware : H3G_GB_P607C3V2.0.0B03-S
    Compile date / time : Aug 15 2009 23:23:53
    Chipset : Qualcomm QSC6240
    User Lock Code : 0000

    ================================================== =================

    Unlocking, please wait ...



    bufer overflow !

    (error code 15)

    bufer overflow !

  • #2
    Originally posted by khansahab View Post
    sir we are not realise why it error appears
    its version is supported

    DC - Unlocker 2 Client 1.00.0717

    Detecting phone :

    selection :
    manufacturer - ZTE phones
    model - ZTE F102/F102i

    Found Phone : F102
    Model : ZTE F102/F102i
    IMEI : 356740031181101
    Firmware : H3G_GB_P607C3V2.0.0B03-S
    Compile date / time : Aug 15 2009 23:23:53
    Chipset : Qualcomm QSC6240
    User Lock Code : 0000

    ================================================== =================

    Unlocking, please wait ...



    bufer overflow !

    (error code 15)

    bufer overflow !
    my problem is solve by using latest software

    DC - Unlocker 2 Client 1.00.0738

    Detecting phone :

    selection :
    manufacturer - ZTE phones
    model - Auto detect (recommended)

    Found Phone : F102
    Model : ZTE F102/F102i
    IMEI : 356740031181101
    Firmware : H3G_GB_P607C3V2.0.0B03-S
    Compile date / time : Aug 15 2009 23:23:53
    Chipset : Qualcomm QSC6240
    User Lock Code : 0000

    ================================================== =================

    Unlocking, please wait ...

    Phone successfully unlocked !

    Credits left : 0


    ================================================== =================

    Comment


    • #3
      Yes, you are right. This problem is fixed in latest (738) version.

      Comment

      Working...
      X