Elektroda.pl
Elektroda.pl
X

Search our partners

Find the latest content on electronic components. Datasheets.com
Please add exception to AdBlock for elektroda.pl.
If you watch the ads, you support portal and users.

UNIFBUS GPG - ubija telefony podczas flash'a -

SELLKOM 05 Jan 2013 23:58 4152 8
  • #1
    SELLKOM
    Level 12  
    Witam,

    Może w skrócie opiszę najpierw posiadaną wiedzę a potem przejdę do konkretów.
    Swoją edukacje z GSM zakończyłem na etapie DCT4, czasów gdzie zakupiony przeze mnie N-BOX (bez HWK) z zestawem kabli był hitem... Później zmiana branży i tak jest do dzisiaj. Od jakiegoś czasu dla samej swojej satysfakcji zacząłem drążyć temat... Kupiony JAF (bez P-KEY'a - bo po co...), CYCLONE BOX i MicroHWK lecz ubity, no i bohater tego postu kabel UNIFBUS PRO 2012 w najnowszej odsłonie...

    Telefony BB5 do testów:
    - Nokia N73
    - Nokia 6300
    - Nokia 3110c - opis i logi na prośbę
    - Nokia E51 - - opis i logi na prośbę

    NOKIA N73 - telefon z T-Mobile DE - simlock oraz brak PL, 100% sprawności HARDWARE - podczas flashowania po USB CYCLONE padła - logów z tego wypadku nie mam - to mnie zmobilizowało do zakupu UNIFBUSA. Telefon był martwy, nie mogłem przejść do trybu LOCAL MODE - skończyło się wizytą w zaprzyjaźnionym serwisie postawili mi ją ale simlocka nie ruszyli. Ponowne podpięcie poprzez UNIFBUS ( przy już sprawnym telefonie):
    Booting CMT...
    APE_SYSTEM_ASIC_ID: 17100708
    APE_ASIC_MODE_ID: 00
    APE_PUBLIC_ID: 623152FC51BB57DAD4FF20C39AAF0EB8CA0D58D2
    APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
    APE_SECURE_ROM_CRC: 2C872FD4
    CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
    CMT_EM_ASIC_ID: 00000295
    CMT_EM_ASIC_ID: 00000B22
    CMT_PUBLIC_ID: 24A00114D5E60154436F39919B23D15410BF9DB6
    CMT_ASIC_MODE_ID: 00
    CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    CMT_SECURE_ROM_CRC: DFAAF68F
    CMT Ready!
    Searching for BootCode: DualLine 32Bit
    RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
    Flashbus Write baud set to 1.0Mbits
    Flashbus Read baud set to 98Kbits
    Using OLD BB5 FLASHING PROTOCOL
    If software STUCK HERE with box TX LED lit, that means:
    USING JAF/UFS CABLES!)
    2. Your cable is not TX2 Enabled!
    3. Transmission error occured, try again
    In either cases, you need to reconnect your box from USB.
    FlashChip[0,CMT]: 0x00EC22E800006921, Samsung, NOR
    FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
    FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
    Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
    Searching for BootCode: DualLine 32Bit
    FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
    RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
    Flashbus Write baud set to 2.0Mbits
    Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
    Box TX2 Data Pin set to: Service Pin 3
    Box VPP disabled
    Internal CMT Phone VPP Enabled
    PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
    APE Boot skipped on user request
    Flashbus Write baud set to 5.0Mbits
    Restarting MCU...
    MCU Version V 05wk47v61.1
    MCU Date 09-07-08
    Product RM-133 (Nokia N73)
    Manufacturer (c) Nokia.
    POMINIĘTO
    Simlock Server SIMLOCK SERVER VERSION 63
    Simlock Key 2620100000000000
    Simlock Profile 0000000000000000
    Simlock Key Cnt 0
    Simlock FBUS Cnt 0
    Simlock [1,1] State: OPENED Type: MCC-MNC Data: 26201F
    Simlock [2,1] State: OPENED Type: MCC-MNC Data: 26201F
    Auto Selecting Flash Files on User Request...
    Product Code: 0541715
    This is Valid BB5 Product
    No variant found with given Product Code, selecting first one

    Resumując simlock zdjęty telefon 100% ok.
    Komunikacja po FBUS prawidłowa???

    Nokia 6300 - telefon już z polskim menu, bez simlocka, 100% sprawny - rozebranie do płyty,podpięcie prawidłowo lini VCC / GND / BSI - wepniecie do gniazda "jack" w adapterze UNIFBUS - próba przeflashowania telefonu (dla sprawdzenia) no i:
    Initializing FBUS...
    All initialized - Ready to work
    MCU Version V 07.21
    MCU Date 05-11-08
    Product RM-217 (Nokia 6300)
    Manufacturer (c) Nokia.
    IMEI 356401014312367
    Mastercode 744543770
    IMEI Spare XXXXXXXXXXXXXXXXXX
    IMEI SV XXXXXXXXXXXXXXXXXXXXXX
    PPM V 07.21, 05-11-08, RM-217, (c) Nokia. , B
    CNT Content: b, V 07.21, 05-11-08, RM-217, (c) Nokia. ,
    PSN DEE928323
    Product Code 0537620
    Module Code 0203166
    Basic Product Code 0537040
    PSD 0000000000000000
    RETU 32
    TAHVO 53
    AHNE 11
    HW 1000
    RFIC 17211721
    DSP ICPR61_08w10
    BT 06cc-P9.1
    Simlock Server SIMLOCK SERVER VERSION 63
    Simlock Key 2440700000000000
    Simlock Profile 0000000000000000
    Simlock Key Cnt 0
    Simlock FBUS Cnt 0
    Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [1,2] State: OPENED Type: GID Data: FFFF
    Simlock [1,3] State: OPENED Type: GID Data: FFFF
    Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [2,2] State: OPENED Type: GID Data: FFFF
    Simlock [2,3] State: OPENED Type: GID Data: FFFF
    Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [3,2] State: OPENED Type: GID Data: FFFF
    Simlock [3,3] State: OPENED Type: GID Data: FFFF
    Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [4,2] State: OPENED Type: GID Data: FFFF
    Simlock [4,3] State: OPENED Type: GID Data: FFFF
    Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [5,2] State: OPENED Type: GID Data: FFFF
    Simlock [5,3] State: OPENED Type: GID Data: FFFF
    Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [6,2] State: OPENED Type: GID Data: FFFF
    Simlock [6,3] State: OPENED Type: GID Data: FFFF
    Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
    Simlock [7,2] State: OPENED Type: GID Data: FFFF
    Simlock [7,3] State: OPENED Type: GID Data: FFFF
    Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
    Auto Selecting Flash Files on User Request...
    Product Code: 0537620
    This is Valid BB5 Product
    Retrieving Variants for Product RM-217 - wait...
    269 Variants Retrieved
    Variant found for readen Product Data!
    Processing pre flash tasks...
    Backing up RPL...
    RPL Creation started...
    Processing CMT Part...
    Storing Product Code...
    Storing PSN...
    Storing HWID...
    Simlock Store not supported, not a PA_SL2 Phone
    Trying to store WMDRM RPL...
    Reading Keys...
    Storing WMDRM PD...
    Reading Security Block...
    04_214701.SecurityBlock.PM"
    read it...
    Reading CYC file from phone...
    Booting CMT...
    CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
    CMT_EM_ASIC_ID: 00000232
    CMT_EM_ASIC_ID: 00000353
    CMT_PUBLIC_ID: 0EC0000F7E5300585174E77C7B5D818ECFA334AF
    CMT_ASIC_MODE_ID: 00
    CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    CMT_SECURE_ROM_CRC: DFAAF68F
    CMT Ready!
    RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.30.0, Algo: BB5
    Flashbus Write baud set to 1.0Mbits
    Flashbus Read baud set to 98Kbits
    Using OLD BB5 FLASHING PROTOCOL
    Exploiting - running preloader...
    Preloader running OK, Running Custom Loader...
    Custom loader running OK! Working...
    Old Loader Detected
    Readed OK, Saving to "0EC0000F7E5300585174E77C7B5D818ECFA334AF.B0000C62"
    Storing Additional Data...
    Checking Superdongle Key...
    Encrypting Superdongle Key...
    Storing Superdongle Key...
    Checking CMLA Key...
    Storing CMLA Key...
    Booting CMT...
    CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
    CMT_EM_ASIC_ID: 00000232
    CMT_EM_ASIC_ID: 00000353
    CMT_PUBLIC_ID: 0EC0000F7E5300585174E77C7B5D818ECFA334AF
    CMT_ASIC_MODE_ID: 00
    CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    CMT_SECURE_ROM_CRC: DFAAF68F
    CMT Ready!
    Searching for BootCode: DualLine 32Bit
    RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
    Flashbus Write baud set to 1.0Mbits
    Flashbus Read baud set to 98Kbits
    Using OLD BB5 FLASHING PROTOCOL
    If software STUCK HERE with box TX LED lit, that means:
    USING JAF/UFS CABLES!)
    2. Your cable is not TX2 Enabled!
    3. Transmission error occured, try again
    In either cases, you need to reconnect your box from USB.
    FlashChip[0,CMT]: 0x00EC22FE00006921, Samsung, NOR
    FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
    FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
    Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
    Searching for BootCode: DualLine 32Bit
    FlashChip 0x00EC22FE (Samsung), Size: 32MBytes, VPP: 9V
    RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
    Flashbus Write baud set to 2.0Mbits
    Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
    Box TX2 Data Pin set to: Service Pin 3
    Box VPP disabled
    Internal CMT Phone VPP Enabled
    PAPUBKEYS Hash for CMT: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
    APE Subsystem Not Found
    Flashbus Write baud set to 5.0Mbits
    Storing NPC...
    Storing CCC...
    Storing HWC...
    Storing VARIANT...
    CMT PARTNERC Not Found
    Restarting MCU...
    RPL Saved OK
    RPL backup thread finished, continuing...
    Pre flash tasks finished, continuing...
    Processing rm217__07.21.mcusw (CMT)...
    Booting CMT...
    CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101001101
    CMT_EM_ASIC_ID: 00000232
    CMT_EM_ASIC_ID: 00000353
    CMT_PUBLIC_ID: 0EC0000F7E5300585174E77C7B5D818ECFA334AF
    CMT_ASIC_MODE_ID: 00
    CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
    CMT_SECURE_ROM_CRC: DFAAF68F
    CMT Ready!
    rm217__07.21.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
    Searching for BootCode: DualLine 32Bit
    RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
    Flashbus Write baud set to 1.0Mbits
    Flashbus Read baud set to 98Kbits
    Using OLD BB5 FLASHING PROTOCOL
    If software STUCK HERE with box TX LED lit, that means:
    USING JAF/UFS CABLES!)
    2. Your cable is not TX2 Enabled!
    3. Transmission error occured, try again
    In either cases, you need to reconnect your box from USB.
    FlashChip[0,CMT]: 0x00EC22FE00006921, Samsung, NOR
    FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
    FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
    Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
    Searching for BootCode: DualLine 32Bit
    FlashChip 0x00EC22FE (Samsung), Size: 32MBytes, VPP: 9V
    RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
    Flashbus Write baud set to 2.0Mbits
    Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
    Box TX2 Data Pin set to: Service Pin 3
    Box VPP disabled
    Internal CMT Phone VPP Enabled
    PAPUBKEYS Hash for CMT: 7F7E6491E8D30494B45630BB3A8599F4E1C674C9
    Flashbus Write baud set to 5.0Mbits
    Sending Certificates...
    Certificates OK
    Started group flash erase
    EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
    EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
    EraseArea[0,CMT]: 0x00020000-0x0007FFFF, NOR
    EraseArea[0,CMT]: 0x00080000-0x000DFFFF, NOR
    EraseArea[0,CMT]: 0x00100000-0x001FFFFF, NOR
    EraseArea[0,CMT]: 0x00200000-0x0031FFFF, NOR
    EraseArea[0,CMT]: 0x00320000-0x0105FFFF, NOR
    EraseArea[0,CMT]: 0x01060000-0x01067FFF, NOR
    EraseArea[0,CMT]: 0x01068000-0x0107FFFF, NOR
    Waiting 320s for erasure finish...
    Erase taken 102.945s
    Writing all blocks...
    Initializing TurboCache...
    TurboCache Loaded!
    Writing CMT NOLO Certificate...
    Block Write Failed -> Failed to write CMT cert data (3), Programming Status Error
    Processing Flash Image Failed -> Failed to write all blocks
    Failed to Process all Image files -> Failed to process rm217__07.21.mcusw
    Failed to read info -> Phone not detected



    Telefon martwy...próba powtórzenia tego samego kończy się fiaskiem.


    To co JAF mi komunikuje podczas próby CHK:
    CMT Boot Data:
    Asic ID: 000000010000022600010006010C192101001101
    Asic Mode ID: 00
    Asic EM ID: 00000353
    Asic Public ID: 0EC0000F7E5300585174E77C7B5D818ECFA334AF
    HASH: BAF3A9C3DBFA8454937DB77F2B8852B100000000
    ROM ID: 191EC665DFAAF68F
    Error finding cmt boot file...
    Manualnie JAF'em:
    FILES SET FOR FLASHING:
    MCU Flash file: NONE
    PPM Flash file: NONE
    CNT Flash file: NONE
    APE Variant file: NONE
    Searching for JAF saved location of ini...
    Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-217\

    Searching for default location of ini...
    Checking path: C:\Program Files\Common Files\Nokia\DataPackage\Products\RM-217\
    Searching for JAF saved location of ini...
    Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-217\
    Scanning ini files...
    Searching for default location of ini...
    Checking path: C:\Program Files\Common Files\Nokia\DataPackage\Products\RM-217\
    Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-217\
    FILES SET FOR FLASHING:
    MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-217\rm217__07.21.mcusw
    PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-217\rm217__07.21.ppm_a
    CNT Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-217\rm217__07.21.image_a
    APE Variant file: NONE
    Languages in ppm: English,German,Finish,Swedish,Danish,Norwegian,Icelandic
    Backing up CRT data...
    Setting FLASH MODE
    Error sync the phone...
    Failed to backup CRT...
    Backing up SIMLOCK data...
    Setting local mode...
    Failed! Aborting!
    Failed to backup LCK...
    Manual mode selected, version can't be checked!
    Booting phone...

    CMT Boot Data:
    Asic ID: 000000010000022600010006010C192101001101
    Asic Mode ID: 00
    Asic EM ID: 00000353
    Asic Public ID: 0EC0000F7E5300585174E77C7B5D818ECFA334AF
    HASH: BAF3A9C3DBFA8454937DB77F2B8852B100000000
    ROM ID: 191EC665DFAAF68F
    Error finding cmt boot file...



    Ręce mi opadają, czy mam reklamować zestaw UNIFBUS, czy ja coś źlę robie ...??

    Proszę o pomoc - fachową - obiecuję odwdzięczyć się praktycznie w każdy sposób.
  • #2
    grzyb26
    Level 21  
    Witam!
    Przed wgraniem softa lepiej sobie zawsze sprawdz czy przechodzi telefon check i info, prawdopodobnie masz złe wartości rezystancji
  • #3
    gsmline
    Level 24  
    Problem to jest z cyclone. na ATF czy MTBOX leci bez problemu i tyle, a robił ktoś flash zwykłym fbus nokia 6020 nie wstaje dobrze po cyclone a mtbox dziala. ten sam kabel nawet flash przechodzi bez błędu tu i tu tylko ze cyclone nie włączy sie do konca typowy błąd softu jak w 5130, Dodatkowo docierałem ostatnio 2700c mtbox, cyclone nie ma bata nie wstają tylko bialy lcd lub do czasu otwieranie aplikacji.... i reset, Flash atf ten sam firmware i telefon dziala??
  • #4
    Rhingsm

    Level 29  
    Cytuję Karwosa(mam nadzieję że nie będzie mi miał tego za złe):
    Code:
    *** Failed to write CMT cert data (3), Programming Status Error ***
    
    If you encountering such problem during flash programming, then this is:
    90% TX2 problem, 10% phone hardware problem.

    Usually, it's JUST tx2, so check following things:

    - YOU NEED attached TX2 adapter to use UFS/JAF cables, otherwise this problem will occur!
    - Check settings of TX2 Pin in Main Software. Attached adapter using Service Pin 3, so TX2 will work only after setting THIS PIN (is set by default). You can of course set other pins, after needed cable mods.
    - Finally make sure if your cable is ok.


    Także teraz pytanie do założyciela tematu.
    Jaka wersja cycloneboxa reloaded czy jedna z starszych wersji?
    Jeżeli starsza wersja czy podłączasz unifbus przez żółtą przelotke?
  • #5
    arczi114
    Level 28  
    -Kolego -SELLKOM- ,zapytaj z łaski swojej w tym serwisie ,który stawiał ci ten uszkodzony telefon, jestem pewien ,że naprawiali innym boxem jak Cyclone- co do kabli -też śmiem wątpić o ich awaryjności, sam mam Cyclone,ale nigdy nie jestem do końca przekonany o jego funkcjonalności, więc tu szukałbym przyczyny... :D
  • #6
    SELLKOM
    Level 12  
    Panowie, Nokia N73 stawiana innym boxem niż CYCLONE.
    Na końcu mojego postu jest log z JAFA - też brak prawidłowej komunikacji, to samo na N-BOXIE.
  • #7
    Rhingsm

    Level 29  
    Dzisiaj przytrafił mi się ten sam przypadek, czyli:
    Code:
    Block Write Failed -> Failed to write CMT cert data (3), Programming Status Error
    
    Processing Flash Image Failed -> Failed to write all blocks
    Failed to Process all Image files -> Failed to process rm217__07.21.mcusw
    Failed to read info -> Phone not detected


    Kable unifbus, podłączone przez przelotke. Problem był tego typu że pinout źle był przyłożony, bootował ale flasha wgrać nieszło. Po poprawieniu ustawienia pinout wszystko jest ok
  • #8
    gsmline
    Level 24  
    nokia n95 za chiny nie szlo ściągnąć simlock dopiero po flash poszedł lock, a tak to ciągle by się wydawało że problem z kablem...?
  • #9
    arczi114
    Level 28  
    Nokia 6500c - to jest dopiero sztuka skomunikować...,tragedia.. :cry: