04-14-17 01:39 PM
31 12
tools
  1. stevie_wonder's Avatar
    Dear all,

    few days back my Z10/3 10.3.2.500 stopped working out of nothing.
    Black display, no logo, no led, no nothing, nada, zero.
    First I thought it was the battery but quickly proved me to be wrong.

    Thus I tried to reload the full system using a new autoloader 10.3.2.500 and 680.

    All starts fine, but then after a few seconds the solid greed led stops and a double blinking red led comes up and the autoloader stops with zero effect.

    Pls see the full output:

    ### Start ###

    C:\Users\Tom\Downloads\BB>Z10-STL234-10.3.2.680-681.exe
    RIM Wireless Device Command-Line Auto-Programmer Version 3.11.0.14 (Win32) [Oct
    3 2014 15:34:35]
    Copyright 2012 Research In Motion Limited

    Connecting to Bootrom:
    Enter password (10 left): ************
    Connected

    [ Uploading RAM Image 0x80239CAC ] [############## 100 ##############]

    QCFMv1/v2 Hybrid File
    containing: IFS, OS, User File System

    IFS/OS Version: 10.3.2.680 DEV
    Hardware ID: 0x051D0001 RIM BlackBerry Device
    Metrics Version: 3.18
    Build Date: May 05 2015
    Build Time: 23:39:00
    Build User: developer
    STP Protocol Ver: 0.0.4 (release OS)

    Signature Trailer:
    EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
    EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
    [ Writing 0x00000000 ] [ 0 ]

    Error: Failed to load images.

    Error: Internal Error: device disappeared

    #### END ###

    So my simple guess is a broken internal Flash memory of the Z10 or such.

    Does anybody maybe has an idea or some wisdom of how to reanimate my SnowWhite?

    Thanks in advance for all of your help, wisdom and thoughts.

    Cheers, Stevie

    P.S: Obviously I've tried all the simple stuff first like different USB port, new computer, new cable, new autoloader etc pp.
    05-21-15 03:29 PM
  2. anon(9208252)'s Avatar
    Might be a bad loader, d/l one from Thurask site and try again.

    https://drive.bitcasa.com/send/6tMMp...3dTocYhTwQn6io
    stevie_wonder likes this.
    05-21-15 04:24 PM
  3. DarcyTallGuy's Avatar
    [ Writing 0x00000000 ] [ 0 ]

    Error: Failed to load images.

    Error: Internal Error: device disappeared
    This to me says the internal flash isn't operative. It fails at the first write and says the device has disappeared.

    CFP FLASHINFO might be a good command to run if you want more info (can get CFP from Thurask's archive as well I think). Or just plain CFP INFO

    CFP Link https://drive.bitcasa.com/send/Lrb0V...QTWzO9sj5uDEvw

    Code:
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 2014 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    FLASHINFO Usage
    ===============
        FLASHINFO
    
    Description:
    ------------
    The FLASHINFO command extracts and then displays information about the flash
    
    Examples:
    ---------
    The following command will display all known information about a device:
        CFP FLASHINFO
    For reference valid output should look similar to this (my Z10, you may have things a little bit different)

    Code:
    CSD Register:
    CSD Version Number = 0x3
    Specification Version = 0x4
    TAAC = 0x27
    NSAC = 0x1
    TRAN_SPEED = 0x32
    
    ..... SNIPPED a lot of lines .....
    
    POWER_OFF_NOTIFICATION = 0x0
    CACHE_CTRL = 0x0
    FLUSH_CACHE = 0x0
    
    Write protection table
    
    Start Block         End Block           HW Partition        Write Protect Type
    --------------------------------------------------------------------------------
    0                   31                  Boot 0              Permanent
    32                  671                 User                None
    672                 1311                User                Temporary
    1312                238592              User                None
    
    Health Status
    --------------------------------------------------------------------------------
    Total Remaining Reserved Blocks = 0x62
      Die[1] = 0x31
      Die[2] = 0x31
      Die[3] = 0x0
      Die[4] = 0x0
    
    Maximum Erase Count Value MLC = 0x15f
    Minimum Erase Count Value MLC = 0x1
    Average Erase Count Value MLC = 0x112
    
    Maximum Erase Count Value SLC = 0x3512
    Minimum Erase Count Value SLC = 0x0
    Average Erase Count Value SLC = 0x31e3
    
    Total Initial Bad Blocks  = 0x4
      Die[1] = 0x2
      Die[2] = 0x2
      Die[3] = 0x0
      Die[4] = 0x0
    
    Total Runtime Bad Blocks  = 0x0
      Die[1] = 0x0
      Die[2] = 0x0
      Die[3] = 0x0
      Die[4] = 0x0
    
    Read Reclaim  = 0x0
    
    
    Done.
    Last edited by DarcyTallGuy; 05-21-15 at 04:58 PM. Reason: added CFP link / good output
    05-21-15 04:44 PM
  4. stevie_wonder's Avatar
    Thanks Withdrawl for your thought! Sadly I tried already 3 autoloader and all fail at the same stage and the same message!
    anon(9208252) likes this.
    05-21-15 05:33 PM
  5. stevie_wonder's Avatar
    This to me says the internal flash isn't operative. It fails at the first write and says the device has disappeared.

    CFP FLASHINFO might be a good command to run if you want more info (can get CFP from Thurask's archive as well I think). Or just plain CFP INFO
    Thank you DarcyTallGuy for the fantastic tool and your help! Much appreciated!!
    I just downloaded and tried it. Not sure how to "read" the results but maybe it tells you something:
    Do I have more bad blocks ?

    Code:
     
    Write protection table
    
    Start Block         End Block           HW Partition        Write Protect Type
    --------------------------------------------------------------------------------
    
    0                   31                  Boot 0              Permanent
    
    32                  671                 User                None
    
    672                 1311                User                Temporary
    
    1312                238592              User                None
    
    
    Health Status
    --------------------------------------------------------------------------------
    
    Total Remaining Reserved Blocks = 0x60
      Die[1] = 0x31
      Die[2] = 0x2f
      Die[3] = 0x0
      Die[4] = 0x0
    
    Maximum Erase Count Value MLC = 0xfa
    Minimum Erase Count Value MLC = 0x1
    Average Erase Count Value MLC = 0xd8
    
    Maximum Erase Count Value SLC = 0x22cb
    Minimum Erase Count Value SLC = 0x0
    Average Erase Count Value SLC = 0x2125
    
    Total Initial Bad Blocks  = 0x6
      Die[1] = 0x2
      Die[2] = 0x4
      Die[3] = 0x0
      Die[4] = 0x0
    
    Total Runtime Bad Blocks  = 0x0
      Die[1] = 0x0
      Die[2] = 0x0
      Die[3] = 0x0
      Die[4] = 0x0
    
    Read Reclaim  = 0x0
    
    
    Done.
    Last edited by stevie_wonder; 05-21-15 at 05:50 PM. Reason: HTML syntax
    05-21-15 05:40 PM
  6. DarcyTallGuy's Avatar
    Thank you DarcyTallGuy for the fantastic tool and your help! Much appreciated!!
    I just downloaded and tried it. Not sure how to "read" the results but maybe it tells you something:
    Do I have more bad blocks ?

    Code:
     
    Write protection table
    
    Start Block         End Block           HW Partition        Write Protect Type
    --------------------------------------------------------------------------------
    
    0                   31                  Boot 0              Permanent
    
    32                  671                 User                None
    
    672                 1311                User                Temporary
    
    1312                238592              User                None
    
    
    Health Status
    --------------------------------------------------------------------------------
    
    Total Remaining Reserved Blocks = 0x60
      Die[1] = 0x31
      Die[2] = 0x2f
      Die[3] = 0x0
      Die[4] = 0x0
    
    Maximum Erase Count Value MLC = 0xfa
    Minimum Erase Count Value MLC = 0x1
    Average Erase Count Value MLC = 0xd8
    
    Maximum Erase Count Value SLC = 0x22cb
    Minimum Erase Count Value SLC = 0x0
    Average Erase Count Value SLC = 0x2125
    
    Total Initial Bad Blocks  = 0x6
      Die[1] = 0x2
      Die[2] = 0x4
      Die[3] = 0x0
      Die[4] = 0x0
    
    Total Runtime Bad Blocks  = 0x0
      Die[1] = 0x0
      Die[2] = 0x0
      Die[3] = 0x0
      Die[4] = 0x0
    
    Read Reclaim  = 0x0
    
    
    Done.
    Honestly I didn't expect you to get anything but an error if your flash was dead. You did have a few extra bad blocks, but those were bad at the factory, a common occurrence, not bad during use so nothing to be worried about because it just meant a few less spare blocks.

    Your erase counts (number of times each block has been used) are even lower than mine so it's not worn out.

    So a little inconclusive I'm afraid.

    The point of this was to try get any sort of extra error messages that might shed some more light on what's happening.

    Other things to try

    CFP INFO

    And if all else fails... this will erase everything. Then try an autoloader again.

    CFP NUKE

    Posted via CB10
    stevie_wonder likes this.
    05-21-15 10:47 PM
  7. stevie_wonder's Avatar
    Honestly I didn't expect you to get anything but an error if your flash was dead. You did have a few extra bad blocks, but those were bad at the factory, a common occurrence, not bad during use so nothing to be worried about because it just meant a few less spare blocks.

    Your erase counts (number of times each block has been used) are even lower than mine so it's not worn out.

    So a little inconclusive I'm afraid.

    The point of this was to try get any sort of extra error messages that might shed some more light on what's happening.

    Other things to try

    CFP INFO

    And if all else fails... this will erase everything. Then try an autoloader again.

    CFP NUKE
    Misterious but it gives me some hope to reanimate the Z10.

    Thus I did try CFP INFO and compared it with my Q10 running on 10.3.1.1779 (SR). The only obvious anomaly is the missing OS

    OS * not present *


    Code:
    C:\Users\Tom\Downloads\BB>cfp57.exe info
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 2
    14 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    Connecting to Bootrom:
    Enter password (10 left): ************
    Connected
    
    [       Uploading RAM Image 0x8023913C ] [############## 100 ##############]
    
    
    QNX Device Info:
      PIN:               2B7DAFF1
      BSN:               1144749123
    
    Bootrom Version:     5.35.0.29
      Hardware ID:       0x8500240A RIM BlackBerry Device
      HW ID Override:    0x8500240A (OSTypes: 0x00000010)
      Hardware OS ID:    0x051D0001
      BR ID:             0xFF009000
      Metrics Version:   6.43
      Build Date:        Nov  3 2012
      Build Time:        09:10:00
      Build User:        ec_agent
      Security:          Enabled
      Supported Options: 0x0000270D
      Drivers:           0x00000010
      Processor:         0x01000001
      FlashID:           0x00000000
      LDR Blocks:        0x2E02FE00
      Bootrom Size:      0x00080000
      Persist Data Addr: 0x2E0AFC00
      External MCT/HWV:  Enabled
    
      Trustzone Info:
            No information available
    
      Boot OS Count:     0,39,0 (Region0,Region1,Max)
                         3,1,1 (Version,Requested Region,Actual Region)
      OS Extra info:     2,0,0 (Version,Radio Max Boot Count,Error code)
      JTAG SW Support:   Unknown
      RPMB Support:      Enabled
      WP Mode:           Permanent
      Slack Mode:        Disabled
      OS Blocking by Date:   Enabled
        Oldest Allowed MFI:  10/4/2012
        Oldest Allowed SFI:  10/24/2012
    
      HWV:
        Board Revision       0x01 - 0x13
        CPU Version          0x02 - 0xBB
        SW Compatibility     0x03 - 0x02
        POP Revision         0x04 - 0x04
        Power Mgt Hardware   0x07 - 0x0F
        POP Security         0x0B - 0x01
        BSIS support         0x41 - 0x02
        NFC                  0x49 - 0x09
        Plastics Type        0x12 - 0x10 *
    
      Mem Config Table (ver 1.28):
        Flash Chip:    blocks 0-262143, Chip 0, Sub 0
        Boot0 MMC:     blocks 0-31, total = 32, flags = 0x0003
        User MMC:      blocks 32-262143, total = 262112, flags = 0x0003
        Bootrom:       blocks 0-31
        MCT:           block 32
        OS NV:         blocks 33-95, total 63
        Cal Working:   blocks 96-671, total = 576
        Cal Backup:    blocks 672-1567, total = 896
        OS Extended:   blocks 1568-2079
        MBR:           blocks 2080-2095
        OS Fixed:      blocks 2096-18463
        Radio Fixed:   blocks 18464-22559
        FS Fixed:      blocks 22560-262143, total = 239584
        QNX region 0:  blocks 2096-10271, total = 8176
        QNX region 1:  blocks 10288-18463, total = 8176
        QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-671, total = 576, "cal_work"
        QNX Partition: type=0x10:00, blocks 672-1567, total = 896, "cal_backup"
        QNX Partition: type=0x11:80, blocks 1568-2079, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 1568-1568, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 1583-1583, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 1584-2079, total = 496, "dmi_fsys"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
        QNX Partition: type=0x02:80, blocks 18464-22559, total = 4096, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-20511, total = 2032, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 20512-20512, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 20528-22559, total = 2032, "radio_fsys"
        QNX Partition: type=0x05:80, blocks 22560-262143, total = 239584, "user"
        RAM Chip:      0x80000000-9FFFFFFF, Bank Size 67108864
        RAM Chip:      0xA0000000-BFFFFFFF, Bank Size 67108864
        RAM Chip:      0xC0000000-DFFFFFFF, Bank Size 67108864
        RAM Chip:      0xE0000000-FFFFFFFE, Bank Size 67108864
        NAND Config:   type 0, data 0x00001000 0x00010000
        NAND Config:   type 1, data 0x17FF0006 0x00FF0015
        NAND Config:   type 3, data 0x00000140 0x00FF0015
        CRC:           0xA9A9BE0F
    
      Mem Config Table (ver 1.28) (actual):
        Flash Chip:    blocks 0-262143, Chip 0, Sub 0
        Boot0 MMC:     blocks 0-31, total = 32, flags = 0x0003
        User MMC:      blocks 32-262143, total = 262112, flags = 0x0003
        Bootrom:       blocks 0-31
        MCT:           block 32
        OS NV:         blocks 33-95, total 63
        Cal Working:   blocks 96-671, total = 576
        Cal Backup:    blocks 672-1567, total = 896
        OS Extended:   blocks 1568-2079
        MBR:           blocks 2080-2095
        OS Fixed:      blocks 2096-18463
        Radio Fixed:   blocks 18464-22559
        FS Fixed:      blocks 22560-262143, total = 239584
        QNX region 0:  blocks 2096-10271, total = 8176
        QNX region 1:  blocks 10288-18463, total = 8176
        QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-671, total = 576, "cal_work"
        QNX Partition: type=0x10:00, blocks 672-1567, total = 896, "cal_backup"
        QNX Partition: type=0x11:80, blocks 1568-2079, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 1568-1568, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 1583-1583, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 1584-2079, total = 496, "dmi_fsys"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
        QNX Partition: type=0x02:80, blocks 18464-22559, total = 4096, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-20511, total = 2032, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 20512-20512, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 20528-22559, total = 2032, "radio_fsys"
        QNX Partition: type=0x05:80, blocks 22560-262143, total = 239584, "user"
        RAM Chip:      0x80000000-9FFFFFFF, Bank Size 67108864
        RAM Chip:      0xA0000000-BFFFFFFF, Bank Size 67108864
        RAM Chip:      0xC0000000-DFFFFFFF, Bank Size 67108864
        RAM Chip:      0xE0000000-FFFFFFFE, Bank Size 67108864
        NAND Config:   type 0, data 0x00001000 0x00010000
        NAND Config:   type 1, data 0x17FF0006 0x00FF0015
        NAND Config:   type 3, data 0x00000140 0x00FF0015
        HWV Entry:     0x12 - 0x10
        CRC:           0xD3634FD6
    
    Flash:
      Number of chips:       1
      Flash ID:              NAND blocks 0-238591
      Device ID:             0x10
      Vendor ID:             0x15
      Manufacturer Name:     Samsung
      OEM/Application ID:    0x100
      Product Name:          MAG2GA
      Product Revision:      0x12
      Product Serial Number: 0xDC2521DC
      Manufacturing Date:    Year 2013, Month 4
      MMC Partition Info:
        Boot0:               2048 KB (enhanced)
        Boot1:               2048 KB (enhanced)
        User:                15267840 KB
      Total Size:            14912 MB
    
    DRAM:
      Size:              2048 MB
      VendorID:          0x1
      Vendor Name:       Samsung
      Revision:          0x100
    
    Memory Map:
      NAND Blocks:       238592 * 64 Kb
      RAM Base:          0x80000000
      IRAM Base:         0x2E000000
      OS Range:          2096 - 18463
    
    File System:
      Memory Map:
                         22560 - 238591
      Sectors:           216032
    
    Branding:
      ECID:              10534
    
    OS * Not present *
    
    OS Blocklist:
       range:              From 10.3.1.0 DEV To 10.3.1.8191 DEV
        type:              SFI
       range:              From 10.3.0.0 DEV To 10.3.0.8191 DEV
        type:              SFI
       range:              From 10.2.1.0 DEV To 10.2.1.8191 DEV
        type:              SFI
       range:              From 0.0.0.0 DEV To 255.31.31.8191 PROD
        type:              Unsupported,Untrusted
       range:              From 0.0.0.0 DEV To 10.0.10.8191 DEV
        type:              SFI
       range:              From 10.1.0.0 DEV To 10.1.0.8191 DEV
        type:              SFI
       range:              From 4.0.10.0 DEV To 4.0.10.513 DEV
        type:              MFI
       range:              From 4.0.11.0 DEV To 4.0.11.307 DEV
        type:              MFI
       range:              From 127.0.0.0 DEV To 127.0.1.4892 DEV
        type:              SFI
    
    Radio Blocklist:
       range:              From 0.0.0.0 DEV To 0.0.0.0 DEV
    
    
    
    Done.
    
    
    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.
    
    C:\Users\Tom>cd Downloads
    
    C:\Users\Tom\Downloads>cd BB
    
    C:\Users\Tom\Downloads\BB>dir
     Volume in drive C is Windows8_OS
     Volume Serial Number is F050-6F1E
    
     Directory of C:\Users\Tom\Downloads\BB
    
    21.05.2015  23:23    <DIR>          .
    21.05.2015  23:23    <DIR>          ..
    21.05.2015  23:23        16.361.984 cfp57.exe
    12.05.2015  15:30     3.038.514.164 Z10-STL234-10.3.2.680-681.exe
                   2 File(s)  3.054.876.148 bytes
                   2 Dir(s)   9.636.286.464 bytes free
    
    C:\Users\Tom\Downloads\BB>cfp57.exe -info
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 20
    14 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    ERROR: Invalid option
    
    C:\Users\Tom\Downloads\BB>cfp57.exe info
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 20
    14 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    Connecting to Bootrom:
    Enter password (10 left): ************
    Connected
    
    [       Uploading RAM Image 0x8023913C ] [############## 100 ##############]
    
    
    QNX Device Info:
      PIN:               2B7DAFF1
      BSN:               1144749123
    
    Bootrom Version:     5.35.0.29
      Hardware ID:       0x8500240A RIM BlackBerry Device
      HW ID Override:    0x8500240A (OSTypes: 0x00000010)
      Hardware OS ID:    0x051D0001
      BR ID:             0xFF009000
      Metrics Version:   6.43
      Build Date:        Nov  3 2012
      Build Time:        09:10:00
      Build User:        ec_agent
      Security:          Enabled
      Supported Options: 0x0000270D
      Drivers:           0x00000010
      Processor:         0x01000001
      FlashID:           0x00000000
      LDR Blocks:        0x2E02FE00
      Bootrom Size:      0x00080000
      Persist Data Addr: 0x2E0AFC00
      External MCT/HWV:  Enabled
    
      Trustzone Info:
            No information available
    
      Boot OS Count:     0,39,0 (Region0,Region1,Max)
                         3,1,1 (Version,Requested Region,Actual Region)
      OS Extra info:     2,0,0 (Version,Radio Max Boot Count,Error code)
      JTAG SW Support:   Unknown
      RPMB Support:      Enabled
      WP Mode:           Permanent
      Slack Mode:        Disabled
      OS Blocking by Date:   Enabled
        Oldest Allowed MFI:  10/4/2012
        Oldest Allowed SFI:  10/24/2012
    
      HWV:
        Board Revision       0x01 - 0x13
        CPU Version          0x02 - 0xBB
        SW Compatibility     0x03 - 0x02
        POP Revision         0x04 - 0x04
        Power Mgt Hardware   0x07 - 0x0F
        POP Security         0x0B - 0x01
        BSIS support         0x41 - 0x02
        NFC                  0x49 - 0x09
        Plastics Type        0x12 - 0x10 *
    
      Mem Config Table (ver 1.28):
        Flash Chip:    blocks 0-262143, Chip 0, Sub 0
        Boot0 MMC:     blocks 0-31, total = 32, flags = 0x0003
        User MMC:      blocks 32-262143, total = 262112, flags = 0x0003
        Bootrom:       blocks 0-31
        MCT:           block 32
        OS NV:         blocks 33-95, total 63
        Cal Working:   blocks 96-671, total = 576
        Cal Backup:    blocks 672-1567, total = 896
        OS Extended:   blocks 1568-2079
        MBR:           blocks 2080-2095
        OS Fixed:      blocks 2096-18463
        Radio Fixed:   blocks 18464-22559
        FS Fixed:      blocks 22560-262143, total = 239584
        QNX region 0:  blocks 2096-10271, total = 8176
        QNX region 1:  blocks 10288-18463, total = 8176
        QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-671, total = 576, "cal_work"
        QNX Partition: type=0x10:00, blocks 672-1567, total = 896, "cal_backup"
        QNX Partition: type=0x11:80, blocks 1568-2079, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 1568-1568, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 1583-1583, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 1584-2079, total = 496, "dmi_fsys"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
        QNX Partition: type=0x02:80, blocks 18464-22559, total = 4096, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-20511, total = 2032, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 20512-20512, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 20528-22559, total = 2032, "radio_fsys"
        QNX Partition: type=0x05:80, blocks 22560-262143, total = 239584, "user"
        RAM Chip:      0x80000000-9FFFFFFF, Bank Size 67108864
        RAM Chip:      0xA0000000-BFFFFFFF, Bank Size 67108864
        RAM Chip:      0xC0000000-DFFFFFFF, Bank Size 67108864
        RAM Chip:      0xE0000000-FFFFFFFE, Bank Size 67108864
        NAND Config:   type 0, data 0x00001000 0x00010000
        NAND Config:   type 1, data 0x17FF0006 0x00FF0015
        NAND Config:   type 3, data 0x00000140 0x00FF0015
        CRC:           0xA9A9BE0F
    
      Mem Config Table (ver 1.28) (actual):
        Flash Chip:    blocks 0-262143, Chip 0, Sub 0
        Boot0 MMC:     blocks 0-31, total = 32, flags = 0x0003
        User MMC:      blocks 32-262143, total = 262112, flags = 0x0003
        Bootrom:       blocks 0-31
        MCT:           block 32
        OS NV:         blocks 33-95, total 63
        Cal Working:   blocks 96-671, total = 576
        Cal Backup:    blocks 672-1567, total = 896
        OS Extended:   blocks 1568-2079
        MBR:           blocks 2080-2095
        OS Fixed:      blocks 2096-18463
        Radio Fixed:   blocks 18464-22559
        FS Fixed:      blocks 22560-262143, total = 239584
        QNX region 0:  blocks 2096-10271, total = 8176
        QNX region 1:  blocks 10288-18463, total = 8176
        QNX Partition: type=0x03:80, blocks 33-95, total = 63, "nvram"
        QNX Partition: type=0x0F:80, blocks 96-671, total = 576, "cal_work"
        QNX Partition: type=0x10:00, blocks 672-1567, total = 896, "cal_backup"
        QNX Partition: type=0x11:80, blocks 1568-2079, total = 512, "dmi"
        QNX Partition: type=0x12:00, blocks 1568-1568, total = 1, "dmi_mbr"
        QNX Partition: type=0x93:00, blocks 1583-1583, total = 1, "dmi_sig"
        QNX Partition: type=0x13:00, blocks 1584-2079, total = 496, "dmi_fsys"
        QNX Partition: type=0x01:80, blocks 2080-10271, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 2080-2080, total = 1, "os_mbr"
        QNX Partition: type=0x07:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x89:40, blocks 2095-2095, total = 1, "os_sig"
        QNX Partition: type=0x08:40, blocks 2096-2271, total = 176, "system"
        QNX Partition: type=0x09:40, blocks 2272-10271, total = 8000, "os_fsys"
        QNX Partition: type=0x01:80, blocks 10272-18463, total = 8192, "os"
        QNX Partition: type=0x06:20, blocks 10272-10272, total = 1, "os_mbr"
        QNX Partition: type=0x07:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x89:00, blocks 10287-10287, total = 1, "os_sig"
        QNX Partition: type=0x08:00, blocks 10288-10463, total = 176, "system"
        QNX Partition: type=0x09:00, blocks 10464-18463, total = 8000, "os_fsys"
        QNX Partition: type=0x02:80, blocks 18464-22559, total = 4096, "radio"
        QNX Partition: type=0x0A:20, blocks 18464-18464, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x8C:40, blocks 18479-18479, total = 1, "radio_sig"
        QNX Partition: type=0x0C:40, blocks 18480-20511, total = 2032, "radio_fsys"
        QNX Partition: type=0x0A:20, blocks 20512-20512, total = 1, "radio_mbr"
        QNX Partition: type=0x0B:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x8C:00, blocks 20527-20527, total = 1, "radio_sig"
        QNX Partition: type=0x0C:00, blocks 20528-22559, total = 2032, "radio_fsys"
        QNX Partition: type=0x05:80, blocks 22560-262143, total = 239584, "user"
        RAM Chip:      0x80000000-9FFFFFFF, Bank Size 67108864
        RAM Chip:      0xA0000000-BFFFFFFF, Bank Size 67108864
        RAM Chip:      0xC0000000-DFFFFFFF, Bank Size 67108864
        RAM Chip:      0xE0000000-FFFFFFFE, Bank Size 67108864
        NAND Config:   type 0, data 0x00001000 0x00010000
        NAND Config:   type 1, data 0x17FF0006 0x00FF0015
        NAND Config:   type 3, data 0x00000140 0x00FF0015
        HWV Entry:     0x12 - 0x10
        CRC:           0xD3634FD6
    
    Flash:
      Number of chips:       1
      Flash ID:              NAND blocks 0-238591
      Device ID:             0x10
      Vendor ID:             0x15
      Manufacturer Name:     Samsung
      OEM/Application ID:    0x100
      Product Name:          MAG2GA
      Product Revision:      0x12
      Product Serial Number: 0xDC2521DC
      Manufacturing Date:    Year 2013, Month 4
      MMC Partition Info:
        Boot0:               2048 KB (enhanced)
        Boot1:               2048 KB (enhanced)
        User:                15267840 KB
      Total Size:            14912 MB
    
    DRAM:
      Size:              2048 MB
      VendorID:          0x1
      Vendor Name:       Samsung
      Revision:          0x100
    
    Memory Map:
      NAND Blocks:       238592 * 64 Kb
      RAM Base:          0x80000000
      IRAM Base:         0x2E000000
      OS Range:          2096 - 18463
    
    File System:
      Memory Map:
                         22560 - 238591
      Sectors:           216032
    
    Branding:
      ECID:              10534
    
    OS * Not present *
    
    OS Blocklist:
       range:              From 10.3.1.0 DEV To 10.3.1.8191 DEV
        type:              SFI
       range:              From 10.3.0.0 DEV To 10.3.0.8191 DEV
        type:              SFI
       range:              From 10.2.1.0 DEV To 10.2.1.8191 DEV
        type:              SFI
       range:              From 0.0.0.0 DEV To 255.31.31.8191 PROD
        type:              Unsupported,Untrusted
       range:              From 0.0.0.0 DEV To 10.0.10.8191 DEV
        type:              SFI
       range:              From 10.1.0.0 DEV To 10.1.0.8191 DEV
        type:              SFI
       range:              From 4.0.10.0 DEV To 4.0.10.513 DEV
        type:              MFI
       range:              From 4.0.11.0 DEV To 4.0.11.307 DEV
        type:              MFI
       range:              From 127.0.0.0 DEV To 127.0.1.4892 DEV
        type:              SFI
    
    Radio Blocklist:
       range:              From 0.0.0.0 DEV To 0.0.0.0 DEV
    
    
    
    Done.

    Long story short, now I will NUKE the baby and try the autoloader again.
    Back to report later!
    canuckcam likes this.
    05-22-15 06:25 AM
  8. stevie_wonder's Avatar
    Bad news, it did not work at all. I tried
    CFP NUKE
    Code:
    C:\Users\Tom\Downloads\BB>cfp57.exe -v5 nuke
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 20
    14 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    ************** Info Dump ********************
    *** Version 3.10.0.57
    *** Build date: Feb 13 2014 (14:12:15)
    *** Compiler: vc9
    *** CMDLine: -v5 nuke
    ************ Info Dump END ******************
    
    --> Using USB timeout values.
    
    --> calling BBDevMgr::Advise()
    
    Connecting for Nuke:--> USBDriver OpenChannel
    --> closing channel
    --> In FindADevice
    --> In RecordDeviceInfo
    --> Waiting for device
    --> Reset m_DeviceAttached
    --> deviceCount = 1
    --> Looking for device with GUID property having a FS Value = 1C861A87503C6BCCF7
    61FD61C871194E28F81233 or HS Value = 1C861A87503C6BCCF761FD61C871194E28F81233 or
     GUID 1C861A87503C6BCCF761FD61C871194E28F81233
    --> Checking connected device (1 of 1)
    --> GUID = 1C861A87503C6BCCF761FD61C871194E28F81233
    --> Hub Address = \DosDevices\HCD1\1\2
    --> Device Name = \\?\USB#VID_0FCA&PID_0001#6&b2dbb92&0&2#{80375827-83b8-4a51-b3
    9b-905fedd4f118}
    --> In RecordDeviceInfo
    --> Selected this device with property : GUID and value : 1C861A87503C6BCCF761FD
    61C871194E28F81233. Returning.
    --> WaitForDevice returned -- opening channel
    --> Attempting to open Channel
    
    Your device is currently being erased. Please wait for
    the LED to extinguish before attempting to reload code.
    This operation may take several minutes.
    
    --> CFP_Imp::Abort() called
    --> USBDriver::Abort() called
    --> Device Detached
    --> USBDriver::Abort() called
    --> Device Disconnected
    --> USBDriver Close
    --> calling BBDevMgr::Unadvise()
    --> Detached from BBDevMgr. Cleaning up.
    --> USBDriver: Closing handles.
    --> Exiting application.
    But autoloader just stops at the same line
    Code:
    C:\Users\Tom\Downloads\BB>Z10-STL234-10.3.2.680-681.exe
    RIM Wireless Device Command-Line Auto-Programmer Version 3.11.0.14 (Win32) [Oct
     3 2014 15:34:35]
    Copyright 2012 Research In Motion Limited
    
    Connecting to Bootrom: Connected
    
    [       Uploading RAM Image 0x80239CAC ] [############## 100 ##############]
    
    QCFMv1/v2 Hybrid File
        containing: IFS, OS, User File System
    
        IFS/OS Version:        10.3.2.680 DEV
            Hardware ID:       0x051D0001 RIM BlackBerry Device
            Metrics Version:   3.18
            Build Date:        May 05 2015
            Build Time:        23:39:00
            Build User:        developer
            STP Protocol Ver:  0.0.4 (release OS)
    
        Signature Trailer:
           EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
           EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
    [                  Writing  0x00000000 ] [               0                 ]
    
    
    Error: Failed to load images.
    
    
    Error: Internal Error: device disappeared
    WIPE also didn't help

    Code:
    --> Writing to Loader Action Log "555F2691:3.10.0.57:DONE:E:CFP -v5 wipe--0"
    --> Got LAL_RESPONSE
    --> Dumping the Loader Action Log:
    --> S:00010014
    --> Fri May 22 13:47:05 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Fri May 22 13:44:35 2015:3.10.0.57:DONE:E:CFP wipe-ErrorCode:0-Success!
    --> Fri May 22 13:44:03 2015:3.10.0.57:E:CFP wipe
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> Fri May 22 13:31:44 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Fri May 22 13:31:14 2015:3.10.0.57:DONE:E:CFP -v5 wipe-ErrorCode:0-Success!
    --> Fri May 22 13:30:25 2015:3.10.0.57:E:CFP -v5 wipe
    --> S:00010014
    --> Fri May 22 13:23:37 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> S:00010014
    --> Fri May 22 12:31:15 2015:3.10.0.57:DONE:EF:CFP nuke -a-ErrorCode:0-Success!
    --> Fri May 22 12:31:15 2015:3.10.0.57:EF:CFP nuke -a
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> S:00010014
    --> Thu May 21 21:15:21 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Thu May 21 21:11:55 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Thu May 21 21:05:23 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Thu May 21 18:33:13 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Thu May 21 18:31:53 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> D:00010015
    --> D:00010015
    --> Mon May 18 10:20:03 2015:3.11.0.14:QNXLOAD:0.0.0.0 DEV
    --> D:00010015
    --> Sun May 17 21:35:45 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Sun May 17 21:16:14 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Sun May 17 20:48:52 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Sun May 17 00:44:53 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Sun May 17 00:39:40 2015:3.11.0.14:QNXLOAD:10.3.2.680 DEV
    --> D:00010015
    --> Sat May 16 23:55:35 2015:3.11.0.14:DTM connection type: PC
    --> D:00010015
    --> Fri Mar 13 16:43:32 2015:3.11.0.8:DONE:QNXLOAD:0.0.0.0 DEV-ErrorCode:0-Succe
    ss!
    --> Fri Mar 13 16:43:30 2015:3.11.0.8:QNXLOAD:0.0.0.0 DEV
    --> Fri Mar 13 16:43:30 2015:3.11.0.8:DTM connection type: PC:10.2.1.3442 DEV
    --> Fri Mar 13 16:43:29 2015:3.11.0.8:DONE:QNXLOAD:10.2.1.3442 DEV-ErrorCode:0-S
    uccess!
    --> Fri Mar 13 16:39:59 2015:3.11.0.8:QNXLOAD:10.2.1.3442 DEV
    --> Fri Mar 13 16:39:59 2015:3.11.0.8:DTM connection type: PC
    --> D:00010015
    --> Fri Mar 13 16:17:29 2015:3.11.0.18:DONE:QNXLOAD:0.0.0.0 DEV-ErrorCode:0-Succ
    ess!
    --> Fri Mar 13 16:17:25 2015:3.11.0.18:QNXLOAD:0.0.0.0 DEV
    --> D:00010015
    --> D:00010013
    --> D:00010013
    --> D:00010013
    --> Mon Feb 10 16:21:07 2014:3.10.0.47:DTM connection type: PC:AppLoader v8.0.0.
    42: load os file
    --> Mon Feb 10 16:17:38 2014:3.10.0.47:DTM connection type: PC
    --> D:00010013
    --> D:00010013
    --> D:00010013
    --> D:00010013
    --> D:00010013
    --> D:00010013
    
    Done.
    
    --> CFP_Imp::Abort() called
    --> USBDriver::Abort() called
    --> USBDriver::Abort() called
    --> Requesting BootImage Exit
    --> USBDriver Close
    --> Device Detached
    --> calling BBDevMgr::Unadvise()
    --> Device Disconnected
    --> Detached from BBDevMgr. Cleaning up.
    --> USBDriver: Closing handles.
    --> Exiting application.
    Should I try the ERASE command (what RANGE?)
    Shouldn't be different from WIPE according to the HELP though.

    Anyways huge thank you for the thoughts and guidance!
    05-22-15 08:59 AM
  9. anon(9208252)'s Avatar
    Have you nuked your yet, with cfp
    stevie_wonder likes this.
    05-22-15 09:32 AM
  10. DarcyTallGuy's Avatar
    Have you disabling firewalls, antivirus, etc? Those can potentially interfere with communication. Antivirus more so than firewall usually.

    Looking at your logs the nuke apparently finished in 0 seconds - that's a bit fast to think it actually worked, but the wipe command took almost a minute the first time and about 30 seconds the second time you tried it. So it may have been doing something at least.

    You can always try CFP LOAD to load the signed images after you split the autoloader. Technically it does the same thing as CAP when running an autoloader, but CFP is far older than the recent CAP versions and the code it loads to do it may do it in a very slightly different way.

    You've obviously got a problem, but I can't help much further because that's the limit of the tools we have. You've done more or less everything I would have at this point.
    05-22-15 09:38 AM
  11. stevie_wonder's Avatar
    Have you nuked your yet, with cfp
    Yes, that was the first command I tried with CFP, see first code sample above.
    05-22-15 10:06 AM
  12. anon(9208252)'s Avatar
    Yes, that was the first command I tried with CFP, see first code sample above.
    I don't get all that when i do a nuke, but mine was made for me,
    stevie_wonder likes this.
    05-22-15 10:07 AM
  13. stevie_wonder's Avatar
    Will try one more time without firewall and virus protection and report back.


    Have you disabling firewalls, antivirus, etc? Those can potentially interfere with communication. Antivirus more so than firewall usually.

    Looking at your logs the nuke apparently finished in 0 seconds - that's a bit fast to think it actually worked, but the wipe command took almost a minute the first time and about 30 seconds the second time you tried it. So it may have been doing something at least.

    You can always try CFP LOAD to load the signed images after you split the autoloader. Technically it does the same thing as CAP when running an autoloader, but CFP is far older than the recent CAP versions and the code it loads to do it may do it in a very slightly different way.

    You've obviously got a problem, but I can't help much further because that's the limit of the tools we have. You've done more or less everything I would have at this point.
    05-22-15 10:07 AM
  14. stevie_wonder's Avatar
    So bad luck, switched of virus, firewall etc. but still the same: it stops after a few seconds and ends with a double red blinking led.
    LOAD does not work either, even FORCING does not help. Here is some output:

    Code:
    C:\Users\Tom\Downloads\BB>cfp57.exe load -P -F -Q -NC Z10-STL234-10.3.2.680-681@
    IFS.signed
    RIM Wireless Device Command-Line Programmer Version 3.10.0.57 (Win32) [Feb 13 20
    14 14:12:14]
    Copyright 2012 Research In Motion Limited
    
    Connecting to Bootrom: Connected
    
    [                  Writing  0x00000000 ] [               0                 ]
    
    
    Error: Internal Error: device disappeared
    Same same, not writing at all.

    Huge appreciation of your valuable time and wisdom to heal my Z10 (R.I.P)

    Luckily I grabbed a white Q10 during last Black Friday deals for an awesome price :-)
    05-22-15 10:49 AM
  15. stevie_wonder's Avatar
    I don't get all that when i do a nuke, but mine was made for me,
    I used the -v5 parameter (full verbose mode) to get all the additional info
    05-22-15 10:51 AM
  16. Uzi's Avatar
    Hi try sic wipe
    It might be help

    http://www.mediafire.com/download/5b...es+n+CFP57.rar

    Z30STA100-2/10.3.2.680
    stevie_wonder likes this.
    05-22-15 10:55 AM
  17. stevie_wonder's Avatar
    Hi try sic wipe
    It might be help

    SIC Multiwipe V1.3_with Choices n CFP57

    Z30STA100-2/10.3.2.680
    Thanks Usman. Though it did wipe heavily for 5 times the result is just the same when trying to install the autoloader.
    Too bad but it was well worth the shot!
    05-22-15 11:14 AM
  18. DarcyTallGuy's Avatar
    Thanks Usman. Though it did wipe heavily for 5 times the result is just the same when trying to install the autoloader.
    Too bad but it was well worth the shot!
    Not too surprising it didn't work when CFP didn't. SIC wipe just runs CFP nuke/erase. So it's the same process you just went through, it even includes the same version of CFP. It just hides the command line behind a user interface so it's easier to use, but you also don't get the same level of feedback which is useful for troubleshooting.
    05-22-15 11:19 AM
  19. glimer4's Avatar
    Have you try to change the connection cable and with other PC or laptop??
    05-22-15 11:46 AM
  20. Kaacz's Avatar
    Have you try to change the connection cable and with other PC or laptop??
    Have you read first post to end?
    >> P.S: Obviously I've tried all the simple stuff first like different USB port, new computer, new cable, new autoloader etc pp. <<
    stevie_wonder likes this.
    05-22-15 12:43 PM
  21. ivill's Avatar
    How do you used to charge your dying BlackBerry?

    I'm curious

    Posted via CB10
    05-22-15 02:37 PM
  22. clie610's Avatar
    Interesting that if the flash memory was bad then the process will stopped/giving error on wiping/nuke process while here is only when applying autoloader.

    So far I notice that autoloader used was using CAP 3.11.0.14, and perhaps it worth to try to use autoloader using newer CAP (3.11.0.22). Either you can find available autoloader created using CAP 3.11.0.22 or you can also create it yourself using Darcy's tool, I saw that the DBBT 2.7.1.8 has already using CAP 3.11.0.22.

    Make sure to restart your PC first before applying the autoloader to have better memory availability in your PC.
    stevie_wonder likes this.
    05-22-15 02:56 PM
  23. stevie_wonder's Avatar
    How do you used to charge your dying BlackBerry?

    I'm curious

    Posted via CB10
    First have a spare battery.
    But more importantly the tests above were done even without battery only the usb cable plugged into the laptop.

    Q10
    WimpySr likes this.
    05-22-15 03:01 PM
  24. stevie_wonder's Avatar
    Interesting that if the flash memory was bad then the process will stopped/giving error on wiping/nuke process while here is only when applying autoloader.

    So far I notice that autoloader used was using CAP 3.11.0.14, and perhaps it worth to try to use autoloader using newer CAP (3.11.0.22). Either you can find available autoloader created using CAP 3.11.0.22 or you can also create it yourself using Darcy's tool, I saw that the DBBT 2.7.1.8 has already using CAP 3.11.0.22.

    Make sure to restart your PC first before applying the autoloader to have better memory availability in your PC.
    Thanks a lot for your idea. I'll search for the right version tomorrow and report back to you!

    Q10
    05-22-15 03:39 PM
  25. clie610's Avatar
    Thanks a lot for your idea. I'll search for the right version tomorrow and report back to you!

    Q10
    Either you do that or you can always extract 10.3.2.680 autoloader that you have with DBBT 2.7.1.8 and create new autolader from the extracted signed files with the same DBBT and you will have new autoloader created from CFP 3.11.0.22
    05-22-15 05:38 PM
31 12

Similar Threads

  1. My z10
    By dpaulod in forum BlackBerry Z10
    Replies: 29
    Last Post: 05-26-15, 07:59 AM
  2. Z30 and a slimport to HDMI cable?
    By theegoldenone in forum BlackBerry Z30
    Replies: 6
    Last Post: 05-21-15, 09:46 PM
  3. Replies: 5
    Last Post: 05-21-15, 04:19 PM
  4. Replies: 8
    Last Post: 05-21-15, 03:34 PM
  5. I upgraded to software 10.3.1 and now none of my sound profiles work but normal?
    By CrackBerry Question in forum General BlackBerry Discussion
    Replies: 5
    Last Post: 05-21-15, 01:21 PM
LINK TO POST COPIED TO CLIPBOARD