Results 31 to 40 of 40

Thread: FAQ from MOBILE-FILES.COM

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #28
    Super Moderator
    Join Date
    Feb 2010
    Location
    MySQL
    Posts
    41

    Default

    q:
    when i attaching phone using dcu60 i see following messages:

    Code:
    erom_readvar: error reading unit 1/725
    error while reading security units
    SECURITY UNITS CAN'T BE READ !
    DAMAGED FIRMWARE/GDFS OR EMPTY PHONE
    
    or
    
    erom_readvar: error reading unit 1/851
    error while reading security units
    SECURITY UNITS CAN'T BE READ !
    DAMAGED FIRMWARE/GDFS OR EMPTY PHONE
    and process stops,but phone works normally on com/ufs.
    what is root cause and what is solution ?

    A:
    that phone is tampered by dreambox software.

    during their "famous' method of "testpoint bypass", they writing patched erom with own custom loader embedded, patching simlock signature check and ... erasing simlock signature without any reason, which prevents setool2 from making backup.

    i had write a post on their forum, but they too arrogant even to read it.

    fix is extremly simple:

    using com/ufs write next script in SIGNED MODE (check ONLY "USE SIGNED MODE" on settings)

    for db2020:
    Code:
    gdfswrite:0001085144554D4D5944415441
    for db2012:
    Code:
    gdfswrite:0001072544554D4D5944415441
    alas, they custom loader also breaks alternative bypass support using dcu60 cable,
    so you only can use SIGNED MODE with dcu60 after their "testpoint".

    i suggest to use setool2 reset method to put proper erom instead of tampered one.

  2. The Following 5 Users Say Thank You to GSM™ For This Useful Post:


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •