12-11-13 10:02 AM
27 12
tools
  1. fgarat's Avatar
    Hi CB,

    Last night my Z10 went off and did not turn. Replace batteries, probe with Link RELOAD perform without success.

    Now testing with an autoloader, fails to load the image and throws the following error:

    RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.38 (Win32) [Jun
    10 2013 14:59:12]
    Copyright 2012 Research In Motion Limited

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

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

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

    IFS/OS Version: 10.1.0.4651 DEV
    Hardware ID: 0x051D0001 RIM BlackBerry Device
    Metrics Version: 3.18
    Build Date: Jul 14 2013
    Build Time: 22:52:15
    Build User: ec_agent
    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


    Now my Z10 is blinking in sequence, one, three and then two blinks

    Anyone have any idea what could be happening?
    08-05-13 05:05 PM
  2. masterscarhead1's Avatar
    Hi CB,

    Last night my Z10 went off and did not turn. Replace batteries, probe with Link RELOAD perform without success.

    Now testing with an autoloader, fails to load the image and throws the following error:

    RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.38 (Win32) [Jun
    10 2013 14:59:12]
    Copyright 2012 Research In Motion Limited

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

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

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

    IFS/OS Version: 10.1.0.4651 DEV
    Hardware ID: 0x051D0001 RIM BlackBerry Device
    Metrics Version: 3.18
    Build Date: Jul 14 2013
    Build Time: 22:52:15
    Build User: ec_agent
    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


    Now my Z10 is blinking in sequence, one, three and then two blinks

    Anyone have any idea what could be happening?
    Try it with the battery out. Does it give the same results?
    The blinking has me worried. If it doesn't work with your battery out, there may be a hardware problem :S
    fgarat likes this.
    08-05-13 06:24 PM
  3. fgarat's Avatar
    Already tried that. Same results.
    08-05-13 06:29 PM
  4. masterscarhead1's Avatar
    Already tried that. Same results.
    Try rebooting devices, PC & phone, but I guess you can't reboot something that isn't boot can you
    Make sure BB Link is not on
    Then try again. If that doesn't work, it seems more like a hardware issue to me, but I can't be 100% certain because I haven't tested your device myself
    fgarat likes this.
    08-05-13 06:31 PM
  5. mkelley65's Avatar
    Try a different USB cable?
    fgarat likes this.
    08-05-13 06:35 PM
  6. Kris Simundson's Avatar
    Hi CB,

    Last night my Z10 went off and did not turn. Replace batteries, probe with Link RELOAD perform without success.

    Now testing with an autoloader, fails to load the image and throws the following error:

    RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.38 (Win32) [Jun
    10 2013 14:59:12]
    Copyright 2012 Research In Motion Limited

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

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

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

    IFS/OS Version: 10.1.0.4651 DEV
    Hardware ID: 0x051D0001 RIM BlackBerry Device
    Metrics Version: 3.18
    Build Date: Jul 14 2013
    Build Time: 22:52:15
    Build User: ec_agent
    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


    Now my Z10 is blinking in sequence, one, three and then two blinks

    Anyone have any idea what could be happening?
    If your bricked on that OS, you need a Lower OS to autoload from

    Posted via CB10
    fgarat likes this.
    08-05-13 06:37 PM
  7. fgarat's Avatar
    tried everything you mention
    08-05-13 06:40 PM
  8. masterscarhead1's Avatar
    If your bricked on that OS, you need a Lower OS to autoload from

    Posted via CB10
    ^^^ Give this a go. I completely forgot about that. No guarantees it will work if it's a hardware issue, but it's worth a shot
    fgarat likes this.
    08-05-13 06:41 PM
  9. fgarat's Avatar
    If your bricked on that OS, you need a Lower OS to autoload from

    Posted via CB10
    Try this too. same results
    08-05-13 06:43 PM
  10. masterscarhead1's Avatar
    Try this too. same results
    Assuming everything you did was correct, I say take it to carrier and see what they can do. Probably send it back for repair
    fgarat likes this.
    08-05-13 06:49 PM
  11. fgarat's Avatar
    Now I got this:

    RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.29 (Win32) [Apr
    1 2013 19:59:10]
    Copyright 2012 Research In Motion Limited

    Connecting to Bootrom: Connected

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

    QCFMv1/v2 Hybrid File
    containing: Radio

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

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

    IFS/OS Version: 10.1.0.2342 DEV
    Hardware ID: 0x051D0001 RIM BlackBerry Device
    Metrics Version: 3.18
    Build Date: May 22 2013
    Build Time: 11:26:10
    Build User: ec_agent
    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 0x0001484E ] [############## 85 ########## ]


    Error: Failed to load images.


    Error: Internal Error: device disappeared
    08-05-13 07:30 PM
  12. vgorous's Avatar
    Could be a bad connection on your usb port

    Posted via CB10
    fgarat likes this.
    08-05-13 07:35 PM
  13. Kris Simundson's Avatar
    Could be a bad connection on your usb port

    Posted via CB10
    That's what it's starting to sound like, the device is definetly alive

    Posted via CB10
    fgarat likes this.
    08-05-13 07:57 PM
  14. fgarat's Avatar
    That's what it's starting to sound like, the device is definetly alive

    Posted via CB10
    I'm starting to believe that is a power related issue.

    I can achieve that result with a fully charged battery only. And after that i have to fully charge the battery again.

    I already changed everything else (USB cables, ports, etc.).
    08-05-13 08:03 PM
  15. Kris Simundson's Avatar
    I'm starting to believe that is a power related issue.

    I can achieve that result with a fully charged battery only. And after that i have to fully charge the battery again.

    I already changed everything else (USB cables, ports, etc.).
    Need to try a new battery than

    Posted via CB10
    08-05-13 08:07 PM
  16. vgorous's Avatar
    I still think it is your usb port on your device. You can install an OS without the battery.

    Changing usb cord won't do much if the solder/joints of your usb port on your device is cracked. Take it back for warranty replacement.

    Posted via CB10
    08-05-13 08:31 PM
  17. kevets's Avatar
    Different USB port on your PC would also be worth trying. Anything really. Another reason inductive charging would be an awesome hack. Less wear on the USB ports!

    Posted via CB10
    08-05-13 08:37 PM
  18. vgorous's Avatar
    Different USB port on your PC would also be worth trying. Anything really. Another reason inductive charging would be an awesome hack. Less wear on the USB ports!

    Posted via CB10
    He already tried that. Slightly wiggling it while plugged in to a computer can help determine if the usb port is losing connection. Your pc should make distinctive audible when something gets plugged in or unplugged.

    Posted via CB10
    08-05-13 08:43 PM
  19. tb146's Avatar
    i got the exact same issue... Z10 die.
    08-05-13 11:24 PM
  20. mkskud's Avatar
    Scratch up one more dead Z10. Mine decided it didn't want to turn on anymore tonight. My Z10 just die.
    08-05-13 11:32 PM
  21. inked18's Avatar
    Easy way to test your port is to plug something else in try a thumb drive then transfer over a movie

    Posted via the Batcave
    fgarat likes this.
    08-05-13 11:36 PM
  22. tb146's Avatar
    It is not the port, i think the chip was damage. It can be recognized by BB Link or autoloader but cannot communication during writing the OS to the chip. Some of damage communication chip.
    I have tried many ways to reload the OS, always end with the same result. Communication error.
    fgarat likes this.
    08-06-13 07:25 AM
  23. fgarat's Avatar
    Thanks everyone for the suggestions. I was able to load 10.2 but the phone still doesn't boot. When i turn it on the red led turn but nothing else.

    The "good thing" (???) is that now is not blinking anymore.
    08-06-13 09:07 AM
  24. tb146's Avatar
    Now i have red blinking 1-3-2 then pause.
    I tried to get the information using CFP, does anyone can help me since the hardware still alive but cannot reload the OS ?

    Extract Information :
    QNX Device Info:
    PIN: 24d636f4
    BSN: 1136967215

    Bootrom Version: 5.33.0.38
    Hardware ID: 0x04002607 RIM BlackBerry Device
    HW ID Override: 0x04002607 (OSTypes: 0x00000010)
    Hardware OS ID: 0x06001A06
    BR ID: 0xFF000072
    Metrics Version: 6.43
    Build Date: Nov 22 2012
    Build Time: 18:13:52
    Build User: ec_agent
    Security: Enabled
    Supported Options: 0x00002FC9
    Drivers: 0x00000010
    Processor: 0x00000020
    FlashID: 0x00000000
    LDR Blocks: 0x80029494
    Bootrom Size: 0x00080000
    Persist Data Addr: 0x800F0000
    External MCT/HWV: Enabled
    Boot Mode: Product

    Trustzone Info:
    Version: 1.7.2.6
    Buildtime:
    Supported: 4460/4470 - 0x7
    Debug type: Off/Secure - 0x2
    Traces: Disabled - 0x1
    Key Size: 1024 - 0x0
    Emif Obf: Off - 0x1
    Efuse Lib: CP_PPA_SWRV_ONLY - 0x1
    Extra Flags: 0x1

    Boot OS Count: 2,0,0 (Region0,Region1,Max)
    2,0,0 (Version,Requested Region,Actual Region)
    JTAG SW Support: Disabled
    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
    Sec BR Flags: 0x00000001
    Sec Boot Count: 0x00000000
    Sec Retry Count: 0x00000000

    HWV:
    Board Revision 0x01 - 0x14
    CPU Version 0x02 - 0x12
    SW Compatibility 0x03 - 0x01
    POP Revision 0x04 - 0x02
    CPU Family 0x05 - 0x01
    Power Mgt Hardware 0x07 - 0x46
    POP Security 0x0B - 0x01
    GPS 0x0C - 0x21
    Hearing Aid Compat 0x37 - 0x01
    WCDMA Band supported 0x3B - 0x07
    BSIS support 0x41 - 0x02
    Power Seq Compat 0x44 - 0x00
    NFC 0x49 - 0x09
    ISP 0x4E - 0x01


    Mem Config Table (ver 1.28):
    Flash Chip: blocks 0-262143, Chip 0, Sub 0
    Boot0 MMC: blocks 0-0, total = 1, flags = 0x0001
    Boot1 MMC: blocks 1-8, total = 8, flags = 0x0001
    User MMC: blocks 9-262143, total = 262135, flags = 0x0003
    MCT: block 0
    Bootrom 2nd: blocks 1-8
    Bootrom: blocks 9-16
    OS NV: blocks 2057-2120, total 64
    MBR: blocks 2121-2136
    OS Fixed: blocks 2137-18504
    OS Extended: blocks 18505-18952
    Radio Fixed: blocks 18953-21000
    FS Fixed: blocks 21001-262143, total = 241143
    MMC Enhanced: blocks 9-1928, total 1920
    QNX region 0: blocks 2137-10312, total = 8176
    QNX region 1: blocks 10329-18504, total = 8176
    QNX Partition: type=0x01, flags=0x80, blocks 2121-10312, total = 8192, "
    os"
    QNX Partition: type=0x06, flags=0x20, blocks 2121-2121, total = 1, "os_m
    br"
    QNX Partition: type=0x07, flags=0x40, blocks 2136-2136, total = 1, "os_s
    ig"
    QNX Partition: type=0x89, flags=0x40, blocks 2136-2136, total = 1, "os_s
    ig"
    QNX Partition: type=0x08, flags=0x40, blocks 2137-2312, total = 176, "sy
    stem"
    QNX Partition: type=0x09, flags=0x40, blocks 2313-10312, total = 8000, "
    os_fsys"
    QNX Partition: type=0x01, flags=0x80, blocks 10313-18504, total = 8192,
    "os"
    QNX Partition: type=0x06, flags=0x20, blocks 10313-10313, total = 1, "os
    _mbr"
    QNX Partition: type=0x07, flags=0x00, blocks 10328-10328, total = 1, "os
    _sig"
    QNX Partition: type=0x89, flags=0x00, blocks 10328-10328, total = 1, "os
    _sig"
    QNX Partition: type=0x08, flags=0x00, blocks 10329-10504, total = 176, "
    system"
    QNX Partition: type=0x09, flags=0x00, blocks 10505-18504, total = 8000,
    "os_fsys"
    QNX Partition: type=0x11, flags=0x80, blocks 18505-18952, total = 448, "
    dmi"
    QNX Partition: type=0x12, flags=0x00, blocks 18505-18505, total = 1, "dm
    i_mbr"
    QNX Partition: type=0x93, flags=0x00, blocks 18520-18520, total = 1, "dm
    i_sig"
    QNX Partition: type=0x13, flags=0x00, blocks 18521-18952, total = 432, "
    dmi_fsys"
    QNX Partition: type=0x02, flags=0x80, blocks 18953-21000, total = 2048,
    "radio"
    QNX Partition: type=0x0A, flags=0x20, blocks 18953-18953, total = 1, "ra
    dio_mbr"
    QNX Partition: type=0x0B, flags=0x40, blocks 18968-18968, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x8C, flags=0x40, blocks 18968-18968, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x0C, flags=0x40, blocks 18969-19976, total = 1008,
    "radio_fsys"
    QNX Partition: type=0x0A, flags=0x20, blocks 19977-19977, total = 1, "ra
    dio_mbr"
    QNX Partition: type=0x0B, flags=0x00, blocks 19992-19992, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x8C, flags=0x00, blocks 19992-19992, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x0C, flags=0x00, blocks 19993-21000, total = 1008,
    "radio_fsys"
    QNX Partition: type=0x05, flags=0x80, blocks 21001-262143, total = 24114
    3, "user"
    RAM Chip: 0x80000000-9FFFFFFF, Bank Size 536870912
    RAM Chip: 0xA0000000-BFFFFFFF, Bank Size 536870912
    RAM Chip: 0xC0000000-DFFFFFFF, Bank Size 536870912
    RAM Chip: 0xE0000000-FFFFFFFE, Bank Size 536870912
    NAND Config: type 0, data 0x00001000 0x00010000
    NAND Config: type 1, data 0x17ff0006 0x00ff0015
    NAND Config: type 3, data 0x00000140 0x00ff0015
    CRC: 0x27AA7C3A


    Mem Config Table (ver 1.28) (actual):
    Flash Chip: blocks 0-262143, Chip 0, Sub 0
    Boot0 MMC: blocks 0-0, total = 1, flags = 0x0001
    Boot1 MMC: blocks 1-8, total = 8, flags = 0x0001
    User MMC: blocks 9-262143, total = 262135, flags = 0x0003
    MCT: block 0
    Bootrom 2nd: blocks 1-8
    Bootrom: blocks 9-16
    OS NV: blocks 2057-2120, total 64
    MBR: blocks 2121-2136
    OS Fixed: blocks 2137-18504
    OS Extended: blocks 18505-18952
    Radio Fixed: blocks 18953-21000
    FS Fixed: blocks 21001-262143, total = 241143
    MMC Enhanced: blocks 9-1928, total 1920
    QNX region 0: blocks 2137-10312, total = 8176
    QNX region 1: blocks 10329-18504, total = 8176
    QNX Partition: type=0x01, flags=0x80, blocks 2121-10312, total = 8192, "
    os"
    QNX Partition: type=0x06, flags=0x20, blocks 2121-2121, total = 1, "os_m
    br"
    QNX Partition: type=0x07, flags=0x40, blocks 2136-2136, total = 1, "os_s
    ig"
    QNX Partition: type=0x89, flags=0x40, blocks 2136-2136, total = 1, "os_s
    ig"
    QNX Partition: type=0x08, flags=0x40, blocks 2137-2312, total = 176, "sy
    stem"
    QNX Partition: type=0x09, flags=0x40, blocks 2313-10312, total = 8000, "
    os_fsys"
    QNX Partition: type=0x01, flags=0x80, blocks 10313-18504, total = 8192,
    "os"
    QNX Partition: type=0x06, flags=0x20, blocks 10313-10313, total = 1, "os
    _mbr"
    QNX Partition: type=0x07, flags=0x00, blocks 10328-10328, total = 1, "os
    _sig"
    QNX Partition: type=0x89, flags=0x00, blocks 10328-10328, total = 1, "os
    _sig"
    QNX Partition: type=0x08, flags=0x00, blocks 10329-10504, total = 176, "
    system"
    QNX Partition: type=0x09, flags=0x00, blocks 10505-18504, total = 8000,
    "os_fsys"
    QNX Partition: type=0x11, flags=0x80, blocks 18505-18952, total = 448, "
    dmi"
    QNX Partition: type=0x12, flags=0x00, blocks 18505-18505, total = 1, "dm
    i_mbr"
    QNX Partition: type=0x93, flags=0x00, blocks 18520-18520, total = 1, "dm
    i_sig"
    QNX Partition: type=0x13, flags=0x00, blocks 18521-18952, total = 432, "
    dmi_fsys"
    QNX Partition: type=0x02, flags=0x80, blocks 18953-21000, total = 2048,
    "radio"
    QNX Partition: type=0x0A, flags=0x20, blocks 18953-18953, total = 1, "ra
    dio_mbr"
    QNX Partition: type=0x0B, flags=0x40, blocks 18968-18968, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x8C, flags=0x40, blocks 18968-18968, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x0C, flags=0x40, blocks 18969-19976, total = 1008,
    "radio_fsys"
    QNX Partition: type=0x0A, flags=0x20, blocks 19977-19977, total = 1, "ra
    dio_mbr"
    QNX Partition: type=0x0B, flags=0x00, blocks 19992-19992, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x8C, flags=0x00, blocks 19992-19992, total = 1, "ra
    dio_sig"
    QNX Partition: type=0x0C, flags=0x00, blocks 19993-21000, total = 1008,
    "radio_fsys"
    QNX Partition: type=0x05, flags=0x80, blocks 21001-262143, total = 24114
    3, "user"
    RAM Chip: 0x80000000-9FFFFFFF, Bank Size 536870912
    RAM Chip: 0xA0000000-BFFFFFFF, Bank Size 536870912
    RAM Chip: 0xC0000000-DFFFFFFF, Bank Size 536870912
    RAM Chip: 0xE0000000-FFFFFFFE, Bank Size 536870912
    NAND Config: type 0, data 0x00001000 0x00010000
    NAND Config: type 1, data 0x17ff0006 0x00ff0015
    NAND Config: type 3, data 0x00000140 0x00ff0015
    HWV Entry: 0x12 - 0x01
    CRC: 0xCD20D87D

    Flash:
    Number of chips: 1
    Flash ID: NAND blocks 0-236648
    Device ID: 0x10
    Vendor ID: 0x15
    Manufacturer Name: Samsung
    OEM/Application ID: 0x100
    Product Name: MAG2GA
    Product Revision: 0x12
    Product Serial Number: 0x4F03FDCA
    Manufacturing Date: Year 2012, Month 8
    MMC Partition Info:
    Boot0: 2048 KB (enhanced)
    Boot1: 2048 KB (enhanced)
    User: 122880 KB (enhanced)
    User: 15022080 KB
    Total Size: 14790 MB

    DRAM:
    Size: 2048 MB
    VendorID: 0x1
    Vendor Name: Samsung
    Revision: 0x100

    Memory Map:
    NAND Blocks: 236649 * 64 Kb
    RAM Base: 0x80000000
    IRAM Base: 0x40304000
    OS Range: 2137 - 18504

    File System:
    Memory Map:
    21001 - 236648
    Sectors: 215648

    Branding:
    ECID: 10001

    OS * Not present *

    OS Blocklist:
    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.1482 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
    08-07-13 11:53 PM
  25. inked18's Avatar
    You've tried reloading the software using the NEWEST available download of blackberry link? If it's flashing like that you should have no problem reloading not restoring.

    Posted via the Batcave
    08-08-13 01:11 AM
27 12

Similar Threads

  1. BB10.1.0.4181 update for Telus Z10
    By PierreC in forum BlackBerry Z10
    Replies: 22
    Last Post: 09-04-13, 05:50 AM
  2. Z10 Transform Case 14.99
    By Jane Li in forum More for your BlackBerry 10 Phone!
    Replies: 4
    Last Post: 08-31-13, 07:46 PM
  3. My Experience with 10.2.0.1047
    By Papaguan in forum BlackBerry 10 OS
    Replies: 6
    Last Post: 08-12-13, 03:41 PM
  4. My Take on BB 10 Marketing
    By westcoastjay in forum General BlackBerry News, Discussion & Rumors
    Replies: 7
    Last Post: 08-08-13, 11:40 AM
  5. How to Keep Work Emails off my Personal Profile in Balance?
    By pauljamesm in forum BlackBerry Z10
    Replies: 2
    Last Post: 08-08-13, 12:56 AM
LINK TO POST COPIED TO CLIPBOARD