Search results

  1. A

    Dahua IPC EASY unbricking / recovery over TFTP

    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!
  2. A

    Dahua IPC EASY unbricking / recovery over TFTP

    ID_2G024C5PAMK588G.txt custom-x.cramfs.img logo-x.cramfs.img web-x.cramfs.img romfs-x.cramfs.img return: Listening On: 192.168.254.254:69 Client 192.168.1.108:3470 root\ID_2G024C5PAMK588G.txt, 1 Blocks Served Client 192.168.1.108:3336 root\custom-x.cramfs.img, 3 Blocks Served Client...
  3. A

    Dahua IPC EASY unbricking / recovery over TFTP

    I found interesting information in the Install.lua file. Perhaps I need to change the command file? managed to get the commands executed, now the NVR downloads the file. But for some reason it does not execute commands. First it say: Client 192.168.1.108:1615 root\ID_2G024C5PAMK588G.txt, 1...
  4. A

    Dahua IPC EASY unbricking / recovery over TFTP

    CRC:4050037456 MagicString:c016dcd6-cdeb-45df-9fd0-e821bf0e1e62 run dr run dk run du run dw run dp run dc tftp 0x82000000 pd-x.squashfs.img; flwrite tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW sleep 5
  5. A

    Dahua IPC EASY unbricking / recovery over TFTP

    I can't get the NVR4416-16p to download files from the tftp server. wireshark catches a request for file ID_2G024C5PAMK588G.txt (507 57.576155 192.168.1.108 192.168.254.254 TFTP 104 Read Request, File: ID_2G024C5PAMK588G.txt, Transfer type: octet, timeout=1, tsize=0...
Top