I have apparently bricked my IPC-T5442T-ZE while doing an uncomplicated firmware update. I used the web interface of the camera (like I have done with 9 other cameras). The update progress bar went to completion and stated "rebooting". Since then I cannot connect to the camera with my assigned static IP. I did a factory reset twice and I can't connect using 192.168.1.108. Will option 2 on page one work in this situation? Should the direct connection to the computer be with a crossover cable? Or since the camera does not seem to be responding to ethernet contact, do I need to use a serial port type connection to the camera? Any help would be appreciated. This recovery is definitely outside my wheelhouse.
tftp 0x82000000 partition-x-bak.cramfs.img; flwrite
tftp 0x82000000 kernel_min.img; flwrite
tftp 0x82000000 romfs_min-x.squashfs.img; flwrite
tftp 0x82000000 kernel.img; flwrite
tftp 0x82000000 partition-x.cramfs.img; flwrite
tftp 0x82000000 romfs-x.squashfs.img; flwrite
tftp 0x82000000 pd-x.squashfs.img; flwrite
tftp 0x82000000 web-x.squashfs.img; flwrite
tftp 0x82000000 firmware-x.squashfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5
If you go back a few pages and find the working link for the files (originally from the OP), with the guide it's all pretty clear... You copy the commands into the commands.txt, run a .bat file which creates another .txt file in the folder you'll extract the fw files in. Then it's just launch the tftp server.I guess I should ask now. I've never setup and used a TFTP server. Do I copy and paste your whole list of commands at once? Or do I wait for each command to finish before typing in the next command? Thanks again.
Woke up yesterday to no signal on my IPC-HFW1831C-PIR, a reboot didn't bring it back up, and it just has a solid red led on between what is the white leds on the front.
A bit of investigation shows that all cams on the same switch this one is plugged into all went down / rebooted about the same time. It was raining heavily at the time, and on another cam not connected to that switch there seemed to be a flash (of lightning) about the time this happened. SO suspect that caused this (however everything is on UPS, and as far as I know all my other equipment was ok).
I have tried the reset button on the IPC-HFW1831C-PIR, but no difference.
I have taken the camera down, connected it to a spare (isolated) poe switch, and also plugged a space pc into said switch. Got the Dahua_TFTPBackup.zip file, and extracted files to pc. Also installed Wireshark on pc. Set IP on pc to 192.168.254.254, and disabled Firewall. I can run TFTPServer.bat and Console.bat and it says they are listening on port 69 and 5002, however nothing else ever comes up on them (even when disconnecting and re-connecting the camera network wire to reboot it).
A wireshark scan shows ARP Broadcast messages saying:
who has 192.168.1.1? Tell 192.168.1.251
But nothing else from the camera.
Anyone have any ideas or seen this before. Any chance I can get the cam back, or just cut my losses and get a new one.
Thanks.
I had the same problem and I managed to unlock the VTH5221dw s2 by adding the environment variablesI now have console running.
The corect firware should be DH_VTHX421L_*** for this devices.
However all I get on Serial console is:
HELLO! BOOT0 is starting! Nov 16 2018 02:18:28
boot0 version : 4.0.0
boot0 commit : 8
DRAM DRIVE INFO: V0.7
DRAM Type = 3 (2DR2,3DR3,6:LPDDR2,7:LPDDR3)
DRAM CLK = 672 MHz
DRAM zq value: 000039bb
DRAM size = 128 MB
Succeed in reading Boot1 file head.
Ready to disable icache.
Jump to secend Boot.
[ 0.110]
U-Boot 2011.09-rc1-svn4146 (Aug 18 2019 - 03:11:44) Allwinner Technology
[ 0.119]version: 1.1.0
[ 0.123]uboot commit : 8
[ 0.129]pmbus: ready
[ 0.134]DRAM: OK
env import count 0
then nothing and device hangs.
Device takes img files on TFTP from correct firmware but not all files can be flashed. It refuses to flash uboot.img.bin for instance.
Is the camera looking through a window?One of the cameras has this double image or what you could call a ghost image.