Dahua IPC EASY unbricking / recovery over TFTP

Discussion in 'Dahua' started by cor35vet, Feb 22, 2017.

Share This Page

  1. iTuneDVR

    iTuneDVR Getting the hang of it

    Joined:
    Aug 23, 2014
    Messages:
    435
    Likes Received:
    53
    Location:
    www.iTuneDVR.ru
    Attach your original file ID_
     
  2. Anzic

    Anzic n3wb

    Joined:
    Jun 29, 2018
    Messages:
    6
    Likes Received:
    1
    Location:
    Krasnodarskij kraj
     

    Attached Files:

  3. Anzic

    Anzic n3wb

    Joined:
    Jun 29, 2018
    Messages:
    6
    Likes Received:
    1
    Location:
    Krasnodarskij kraj
    YES!! It's BOOT!!!! I don't know what happened, but after the next power off and on, the NVR has boot! I conclude that the last file that I sent is a working option to restore the recorder. Thank you very much, iTuneDVR! I wouldn't be able to restore without you!
     
    alastairstevenson likes this.
  4. iTuneDVR

    iTuneDVR Getting the hang of it

    Joined:
    Aug 23, 2014
    Messages:
    435
    Likes Received:
    53
    Location:
    www.iTuneDVR.ru
    ;)

    In 2017 rom NVR4XXX ID_XXX inside must be with calculated CRC & magic string
    After upgrade via TFTP it need by your hand reboot with already closed TFTP server
    Example in attach. Util tools the same.
    Just change XX.XXX to your SN
     

    Attached Files:

  5. BGChicago

    BGChicago n3wb

    Joined:
    Apr 17, 2016
    Messages:
    13
    Likes Received:
    4
    Anyone can provide firmware for DH-IPC-HFW4800EN? May be from 2018. Thanks.
     
  6. blueduck2001

    blueduck2001 n3wb

    Joined:
    Sep 11, 2019
    Messages:
    1
    Likes Received:
    1
    Location:
    Loire
    Hello!

    This few lines to report successful unbricking of my VTO2000A-2 (stuck with an english-only firmware while I needed french) and VTH1550CH (with a V4 firmware I had to downgrade to the same version number than the french VTO firmware).

    I pass over the network configuration, that is quite specific for everyone.

    It seemed to me that depending on each network configuration, the devices don't connect to the TFTP server systematically: it takes sometimes several reboots to connect.

    There's no need to create empty failed.txt file under the server's root: messages complaining about missing failed.txt or success.txt files are only for saying that something goes wrong or that everything is OK.

    Depending to the step where I successively get the failed.txt error message, I had to slightly adapt commands.txt to each device.

    For the VTO2000A-2 (don't keep what is in brackets):

    run dr
    run dk
    run du
    run dw
    run dd (--> for data-x.cramfs.img, instead of 'run dp' by default in the 'Dahua_TFTPBackup.zip')
    run dc
    tftp 0x82000000 pd-x.cramfs.img; flwrite (instead of 'pd-x.squashfs.img')
    tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
    sleep 5

    and for the VTH1550CH:

    run dr
    run dk
    run du
    run dg (--> for gui-x.cramfs.img, instead of 'run dw' that is for web-x.cramfs.img on the VTO: VTO has a web interface, VTH has a GUI)
    run dd
    run dc
    tftp 0x82000000 pd-x.cramfs.img; flwrite
    tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
    sleep 5

    I've first downgraded to the 3.2 firmwares, but the web interface of the VTO seemed to lack some options, and didn't work well in Firefox, had to use Edge. But I then was able to downgrade with ConfigTool to 3.1 firmwares, and finally got all in french: vocal announces, VTO web interface (but still have to use Edge, don't know why...) and VTH GUI. Maybe I will try later to get others 3.2 files...

    Hope it helps, and many thanks to all of you :)
     
    Last edited: Sep 11, 2019
    alastairstevenson likes this.