How to apply specific replacement within warranty

For the defective component within warranty as below, the customer doesn’t need to ship them back to repair.

Please follow the steps as below to provide us with required information. Once confirmed, we will send replacement to the customer.

Item Required information Warranty(From the shipping date to the repair ticket date)
Fan for S7/R4/S9 1.Original order ID
2.Repair ticket ID
3.Screenshot of Miner status
90 Days
AntRouter-R1 1.Original order ID
2.Repair ticket ID
3.Screenshot of Network->Wifi.  and Miner->R1 Miner.
1 Year

 

Step 1: Please troubleshoot under the guidance of our customer service.

Step 2: Please provide the required information for further confirmation.

Step 3: Please follow the instructions as below to create application ticket.

How to create an application ticket?

  1. Please copy the address as below to your browser.

https://shop.bitmain.com/user/repairHeaderAdd.htm

Log into your Bitmain account with your ID and password. If you don’t have a Bitmain account please click “Sign Up” to create one.

  1.   After you log in, you will enter the page to create a ticket.
  • l Make your you are in English operation page;
  • l Always click the button “Apply for Parts” to create an application ticket, which differs from repair ticket.
  • l Select the name of your defective component. Fill in the original order ID and actual quantity.
  • l Don’t forget to save each line after edit!!!
  • l Fill in your exact and valid address!
  • l Read BITMAIN After-Sales Service Terms carefully, click “Accept” and Submit to create a ticket.
  1. After submitting, you will see a page as below, which means that you have created a ticket successfully. The status of the ticket should be “Pending”. Please copy the ticket ID and send it to us for further confirmation.

  1. Click the button “View”, you can review the information of your ticket. Before we confirm the ticket, the user is allowed to revise the ticket as below.

 

 

Have more questions? Submit a request

12 Comments

  • 0
    Avatar
    Michael

    i have done what is requested, my unit has been working now for 31 days and this am all 3 hashboards are dead no red led, but voltage test on pci-e plug shows 12vdc...

  • 0
    Avatar
    Barbara

    Hi Michael,

     

    Please email us at support@bitmain.com. This will create a service ticket and we can help you resolve the issue. 

  • 0
    Avatar
    Goldtrm

    Hello,

    I can't open your site at https://shop.bitmain.com/user/repairHeaderAdd.htm  , so i can't open ticket , etc.

     

     

    I need help about my antminer D3.

    What should i do?

    Thanks

    Edited by Goldtrm
  • 0
    Avatar
    Kilometers686

    @Goldtrm

    Same thing just happened to me on my D3 too, Goldtrm. Chain 2 glitched out in the exact same way. This happened after I updated my firmware.

  • 0
    Avatar
    Goldtrm

    @Kilometers686 , i can't sent back to Bitmain because the fee.

    Handling fee $140 :(

    So, mining with 2 hashboard = about 11 Ghs.

  • 0
    Avatar
    Michael

    what is so frustrating is the need to send back under warranty for that handling fee. i asked for a replacement and offered to purchase outright as it would be less of a hassle and quicker.....they say no, you have to return the faulty component..... poor after sales service

     

  • 0
    Avatar
    Softmaster

    my miners arrived dead, which i address i need to ship it back?

  • 0
    Avatar
    Goldtrm
  • 0
    Avatar
    Mlivelanpin

    I'm waiting for confirmation. 

    • Order ID: 0012017090504885
    Ticket ID:

    0332017121415174446045n3yXDa0678

    my miners arrived dead, which i address i need to ship it back?

  • 0
    Avatar
    Muhammed Bilgin

    my ticket ID: 033201801140407344177dl801wS065F 

     

    and I'm send my product California. Is this adress correct? 

     

    Name: Tomrepair-Bitmain
    Add: 5640 Grace Place, Commerce, CA 90022, USA
    Tel: (+1) 626 362 7240

  • 0
    Avatar
    Artem Sarkisov

    I'm trying to flash my own control board.It is loaded from the SD card but not flashing.I then decided to flash it myself.Tell me what I'm doing wrong?

     

    U-Boot# nand erase.chip

    NAND erase.chip: device 0 whole chip
    Erasing at 0xffe0000 -- 100% complete.
    OK
    U-Boot# load mmc 0 0x81000000 MLO
    reading MLO
    100416 bytes read in 16 ms (6 MiB/s)
    U-Boot# nand erase 0x0 0x20000

    NAND erase: device 0 offset 0x0, size 0x20000
    Erasing at 0x0 -- 100% complete.
    OK
    U-Boot# nand erase 0x0 0x20000

    NAND erase: device 0 offset 0x0, size 0x20000
    Erasing at 0x0 -- 100% complete.
    OK
    U-Boot# nandecc hw 2
    8-bit BCH HW ECC selected
    U-Boot# load mmc 0 0x81000000 MLO
    reading MLO
    100416 bytes read in 16 ms (6 MiB/s)
    U-Boot# nand write 0x81000000 0x00000 0x20000

    NAND write: device 0 offset 0x0, size 0x20000
    131072 bytes written: OK
    U-Boot# nand write 0x81000000 0x20000 0x20000

    NAND write: device 0 offset 0x20000, size 0x20000
    131072 bytes written: OK
    U-Boot# nand write 0x81000000 0x40000 0x20000

    NAND write: device 0 offset 0x40000, size 0x20000
    131072 bytes written: OK
    U-Boot# nand write 0x81000000 0x60000 0x20000

    NAND write: device 0 offset 0x60000, size 0x20000
    131072 bytes written: OK
    U-Boot# load mmc 0 0x81000000 u-boot.img
    reading u-boot.img
    380552 bytes read in 50 ms (7.3 MiB/s)
    U-Boot# nand erase 0x80000 0x40000

    NAND erase: device 0 offset 0x80000, size 0x40000
    Erasing at 0xa0000 -- 100% complete.
    OK
    U-Boot# nandecc hw 2
    8-bit BCH HW ECC selected
    U-Boot# nand write 0x81000000 0x80000 0x60000

    NAND write: device 0 offset 0x80000, size 0x60000
    393216 bytes written: OK
    U-Boot# load mmc 0 0x81000000 uImage.bin
    reading uImage.bin
    4394136 bytes read in 532 ms (7.9 MiB/s)
    U-Boot# nand erase 0x280000 0x500000

    NAND erase: device 0 offset 0x280000, size 0x500000
    Erasing at 0x760000 -- 100% complete.
    OK
    U-Boot# nandecc hw 2
    8-bit BCH HW ECC selected
    U-Boot# nand write 0x81000000 ${nandsrcaddr} ${nandimgsize}

    NAND write: device 0 offset 0x280000, size 0x500000
    5242880 bytes written: OK
    U-Boot# load mmc 0 0x81000000 initramfs.bin.SD
    reading initramfs.bin.SD
    15023475 bytes read in 1808 ms (7.9 MiB/s)
    U-Boot# nand erase 0x780000 0x1000000

    NAND erase: device 0 offset 0x780000, size 0x1000000
    Erasing at 0x1760000 -- 100% complete.
    OK
    U-Boot# nandecc hw 2
    8-bit BCH HW ECC selected
    U-Boot# nand write 0x81000000 0x780000 ${filesize};

    NAND write: device 0 offset 0x780000, size 0xe53d73
    15023475 bytes written: OK
    U-Boot# rom boot
    Unknown command 'rom' - try 'help'
    U-Boot# ram boot
    Unknown command 'ram' - try 'help'
    U-Boot# nand boot
    nand - NAND sub-system

    Usage:
    nand info - show available NAND devices
    nand device [dev] - show or set current device
    nand read - addr off|partition size
    nand write - addr off|partition size
    read/write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
    nand read.raw - addr off|partition [count]
    nand write.raw - addr off|partition [count]
    Use read.raw/write.raw to avoid ECC and access the flash as-is.
    nand erase[.spread] [clean] off size - erase 'size' bytes from offset 'off'
    With '.spread', erase enough for given file size, otherwise,
    'size' includes skipped bad blocks.
    nand erase.part [clean] partition - erase entire mtd partition'
    nand erase.chip [clean] - erase entire chip'
    nand bad - show bad blocks
    nand dump[.oob] off - dump page
    nand scrub [-y] off size | scrub.part partition | scrub.chip
    really clean NAND erasing bad blocks (UNSAFE)
    nand markbad off [...] - mark bad block(s) at offset (UNSAFE)
    nand biterr off - make a bit error at offset (UNSAFE)
    U-Boot#
    U-Boot SPL 2013.04-dirty (Aug 04 2014 - 11:06:44)
    Control_status {00420313}
    Could not probe the EEPROM; something fundamentally wrong on the I2C bus.
    Could not get board ID.
    default->A335BNLT.
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    USB Peripheral mode controller at 47401000 using PIO, IRQ 0
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    USB Host mode controller at 47401800 using PIO, IRQ 0
    CONFIG_SYS_NAND_U_BOOT_OFFS:80000
    CONFIG_SYS_NAND_PAGE_SIZE:800
    spl_image.size:5ce88
    spl_image.load_addr:807fffc0
    image entry point: 0x80800000


    U-Boot 2013.04-dirty (Aug 04 2014 - 11:06:44)

    I2C: ready
    eDRAM: 256 MiB
    WARNING: Caches not enabled
    Could not probe the EEPROM; something fundamentally wrong on the I2C bus.
    Could not get board ID.
    NAND: 256 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    *** Warning - bad CRC, using default environment

    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    USB Peripheral mode controller at 47401000 using PIO, IRQ 0
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    USB Host mode controller at 47401800 using PIO, IRQ 0
    Net: <ethaddr> not set. Validating first E-fuse MAC
    cpsw, usb_ether
    Hit any key to stop autoboot: 0
    gpio: pin 53 (gpio 53) value is 1
    mmc_send_cmd : timeout: No status update
    Card did not respond to voltage select!
    mmc0(part 0) is current device
    mmc_send_cmd : timeout: No status update
    Card did not respond to voltage select!
    No micro SD card found, setting mmcdev to 1
    Card did not respond to voltage select!
    mmc1(part 0) is current device
    mmc_send_cmd : timeout: No status update
    Card did not respond to voltage select!
    Booting from nand ...

    NAND read: device 0 offset 0x280000, size 0x500000
    5242880 bytes read: OK
    gpio: pin 54 (gpio 54) value is 1

    NAND read: device 0 offset 0x800000, size 0x1400000
    20971520 bytes read: OK
    gpio: pin 55 (gpio 55) value is 1

    NAND read: device 0 offset 0x260000, size 0x20000
    131072 bytes read: OK
    gpio: pin 56 (gpio 56) value is 1
    ## Booting kernel from Legacy Image at 80200000 ...
    Image Name: Linux-3.8.13
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 4394072 Bytes = 4.2 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    Wrong Ramdisk Image Format
    Ramdisk image is corrupt or invalid
    U-Boot#

     

  • 0
    Avatar
    Nawaf911

    Hello,

    I send many emails and I waited very long to get confirmation from you about my ticket below, the 2 faulty D3 hash board sent and received by you 6 days back but till now no update happens to my ticket status or to my estimate shipping for my hash board, as you know time is money and I am waiting, please reply ASAP :

    Courier: DHL
    Tracking No.: 7715694184
    Total Packs: 1
    Remark: Faulty Asics
    Ticket ID: 03****************************w06D3
    Status: Uncollected
    Total Items: 2
    Repair Site: HongKong


    Thank you

Please sign in to leave a comment.