macattack69
n3wb
- Joined
- Mar 16, 2016
- Messages
- 13
- Reaction score
- 3
Good day:
I have a HDBW4421 Dahua camera that became unresponsive, and have been trying to get it live again. So far, this is what I have done:
Background Info
-Tried to reset up camera with the Config Tool. ConfigTool does not find the camera.
-Ethernet TCP/IP settings set for an IP address in the 192.168.1.XXX relm, with no IP conflicts. (Ie. I am not using 192.168.1.108). This is direct wired through a POE Injector to the camera.
-Further to the above point, with the setup I am using, I can ping the camera. I have ran a port scanner on 192.168.1.108. I can see that only ports 23 and 6800 are open on the camera.
-I followed the guides from this forum for UART/TFTP and the "Easy" TFTP guide. I do not have a UART setup at the moment, so I used the UART tutorial as background info then headed over to the "Easy" TFTP guide. I have also read and absorbed the other posts in each forum for additional guidance.
Steps Tried: 1: Following "EASY" TFTP Unbricking Procedure
-Downloaded and got the TFTP tools setup. I also grabbed a known, working firmware for these cameras, unzipped, and placed the required files in the ROOT folder.
-Using Command Prompt, I ran TPTPServer.bat, followed by Console.bat.
-When ran, I can see that it initiates a TFTP session, and all I get is:
Listenining On: 192.168.254.254:69
Issue #1: I do not see a failed.txt or a success.txt. The process gets hung up here.
Any guidance or thoughts? I have also setup Wireshark, and I do not see any TFTP traffic going to the 192.168.1.254 or 192.168.1.108
Issue #2: "Terminal":
Throughout the UART guide, it talks about using a serial terminal application like Putty, to be able to communicate through COM to the camera. In the TFTP guide, there is not mention of using a "Terminal" to grab info on a camera Boot Sequence. In the forum posts under the TFTP guide, people talk about seeing things through use of a terminal. Is there a way to interrupt the boot sequence through a terminal of some variety to be able to pull up UBoot info, enter the 'help' command or 'printserv' command when using the TFTP method? If so, what is the terminal, and how should the terminal be setup?
Further to this, I have tried using Putty with telnet on 192.168.1.108, Port 23 (which I have confirmed is open, per the above). At times, I can connect using telnet and admin:vizxv. With relatively short order, I get an error message that says "Software Caused Connection Abort".
Steps Tried 2: Followed another guide:
Using the telnet approach as outlined above, I typed in Putty:
Then I get a software caused connection abort.
ANY GUIDANCE WOULD BE GREATLY APPRECIATED.
I have a HDBW4421 Dahua camera that became unresponsive, and have been trying to get it live again. So far, this is what I have done:
Background Info
-Tried to reset up camera with the Config Tool. ConfigTool does not find the camera.
-Ethernet TCP/IP settings set for an IP address in the 192.168.1.XXX relm, with no IP conflicts. (Ie. I am not using 192.168.1.108). This is direct wired through a POE Injector to the camera.
-Further to the above point, with the setup I am using, I can ping the camera. I have ran a port scanner on 192.168.1.108. I can see that only ports 23 and 6800 are open on the camera.
-I followed the guides from this forum for UART/TFTP and the "Easy" TFTP guide. I do not have a UART setup at the moment, so I used the UART tutorial as background info then headed over to the "Easy" TFTP guide. I have also read and absorbed the other posts in each forum for additional guidance.
Steps Tried: 1: Following "EASY" TFTP Unbricking Procedure
-Downloaded and got the TFTP tools setup. I also grabbed a known, working firmware for these cameras, unzipped, and placed the required files in the ROOT folder.
-Using Command Prompt, I ran TPTPServer.bat, followed by Console.bat.
-When ran, I can see that it initiates a TFTP session, and all I get is:
Listenining On: 192.168.254.254:69
Issue #1: I do not see a failed.txt or a success.txt. The process gets hung up here.
Any guidance or thoughts? I have also setup Wireshark, and I do not see any TFTP traffic going to the 192.168.1.254 or 192.168.1.108
Issue #2: "Terminal":
Throughout the UART guide, it talks about using a serial terminal application like Putty, to be able to communicate through COM to the camera. In the TFTP guide, there is not mention of using a "Terminal" to grab info on a camera Boot Sequence. In the forum posts under the TFTP guide, people talk about seeing things through use of a terminal. Is there a way to interrupt the boot sequence through a terminal of some variety to be able to pull up UBoot info, enter the 'help' command or 'printserv' command when using the TFTP method? If so, what is the terminal, and how should the terminal be setup?
Further to this, I have tried using Putty with telnet on 192.168.1.108, Port 23 (which I have confirmed is open, per the above). At times, I can connect using telnet and admin:vizxv. With relatively short order, I get an error message that says "Software Caused Connection Abort".
Steps Tried 2: Followed another guide:
Using the telnet approach as outlined above, I typed in Putty:
BusyBox v1.18.4 (2015-10-21 12:02:45 CST) built-in shell (ash)
Revision: 11734
Enter 'help' for a list of built-in commands.
~ # ps
PID USER TIME COMMAND
1 root 0:00 init
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
4 root 0:00 [kworker/0:0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u2:0]
7 root 0:00 [khelper]
8 root 0:00 [kdevtmpfs]
9 root 0:00 [writeback]
10 root 0:00 [bioset]
11 root 0:00 [crypto]
12 root 0:00 [kblockd]
13 root 0:00 [khubd]
14 root 0:01 [kworker/0:1]
15 root 0:00 [rpciod]
16 root 0:00 [kswapd0]
17 root 0:00 [fsnotify_mark]
18 root 0:00 [nfsiod]
32 root 0:00 [deferwq]
33 root 0:00 [kworker/u2:1]
34 root 0:00 [kworker/0:1H]
71 root 0:00 [jffs2_gcd_mtd9]
87 root 0:00 /sbin/telnetd
99 root 0:00 [OSA_98_1]
106 root 0:00 [OSA_105_3]
107 root 0:00 [OSA_105_4]
115 root 0:00 syshelper elper 60
116 root 0:00 /usr/sbin/upgraded
122 root 0:00 [OSA_119_5]
126 root 0:00 [kworker/u2:2]
201 root 0:00 /bin/sh /etc/init.d/appauto
202 root 0:00 -sh
225 root 0:00 /bin/sh
228 root 0:00 ps
~ # kill -9 116
~ # /usr/sbin/upgraded
[OSA-APP] OSA Build on Dec 15 2015 at 01:59:18.
[OSA-APP] SVN NUM: 4472.
[libpdi] libpdi.so Build on Nov 4 2015 at 03:11:52.
[libpdi] SVN NUM: 25358.
[libpdi] Get fpga upgrade cfg failed, use default
[libpdi] Support backup partition !!!
[libpdi] Flashtype = 3,patSize = 40000,rwSize = 10000,ersSize = 10000
[libpdi] WARN : Device has no crypt chip!
[libpdi] phyaddr= 0x6ffe000, memLen= 0x2000
08:52:41|[pdc] Both of Chief and Backup File CRC check OK!
Fail to get env hwidEx!
[libpdi] can't find commLen cfg
UPGRADED_MSG: Do memlock
UPGRADED_MSG: lock: addrStart=76d6d000, addrEnd=76d74000
UPGRADED_MSG: lock: addrStart=76e6d000, addrEnd=76e74000
UPGRADED_MSG: lock: addrStart=76e8c000, addrEnd=76e94000
UPGRADED_MSG: lock: addrStart=76e9d000, addrEnd=76ea4000
UPGRADED_MSG: lock: addrStart=76ea7000, addrEnd=76eae000
UPGRADED_MSG: lock: addrStart=76eb6000, addrEnd=76ebd000
UPGRADED_MSG: lock: addrStart=76f34000, addrEnd=76f3b000
UPGRADED_MSG: lock: addrStart=76f57000, addrEnd=76f5e000
UPGRADED_MSG: lock: addrStart=76f6b000, addrEnd=76f72000
Name: upgraded, bulid date: Dec 12 2015 03:27:19, svn: 537
UPGRADED_MSG: start download file
Revision: 11734
Enter 'help' for a list of built-in commands.
~ # ps
PID USER TIME COMMAND
1 root 0:00 init
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
4 root 0:00 [kworker/0:0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u2:0]
7 root 0:00 [khelper]
8 root 0:00 [kdevtmpfs]
9 root 0:00 [writeback]
10 root 0:00 [bioset]
11 root 0:00 [crypto]
12 root 0:00 [kblockd]
13 root 0:00 [khubd]
14 root 0:01 [kworker/0:1]
15 root 0:00 [rpciod]
16 root 0:00 [kswapd0]
17 root 0:00 [fsnotify_mark]
18 root 0:00 [nfsiod]
32 root 0:00 [deferwq]
33 root 0:00 [kworker/u2:1]
34 root 0:00 [kworker/0:1H]
71 root 0:00 [jffs2_gcd_mtd9]
87 root 0:00 /sbin/telnetd
99 root 0:00 [OSA_98_1]
106 root 0:00 [OSA_105_3]
107 root 0:00 [OSA_105_4]
115 root 0:00 syshelper elper 60
116 root 0:00 /usr/sbin/upgraded
122 root 0:00 [OSA_119_5]
126 root 0:00 [kworker/u2:2]
201 root 0:00 /bin/sh /etc/init.d/appauto
202 root 0:00 -sh
225 root 0:00 /bin/sh
228 root 0:00 ps
~ # kill -9 116
~ # /usr/sbin/upgraded
[OSA-APP] OSA Build on Dec 15 2015 at 01:59:18.
[OSA-APP] SVN NUM: 4472.
[libpdi] libpdi.so Build on Nov 4 2015 at 03:11:52.
[libpdi] SVN NUM: 25358.
[libpdi] Get fpga upgrade cfg failed, use default
[libpdi] Support backup partition !!!
[libpdi] Flashtype = 3,patSize = 40000,rwSize = 10000,ersSize = 10000
[libpdi] WARN : Device has no crypt chip!
[libpdi] phyaddr= 0x6ffe000, memLen= 0x2000
08:52:41|[pdc] Both of Chief and Backup File CRC check OK!
Fail to get env hwidEx!
[libpdi] can't find commLen cfg
UPGRADED_MSG: Do memlock
UPGRADED_MSG: lock: addrStart=76d6d000, addrEnd=76d74000
UPGRADED_MSG: lock: addrStart=76e6d000, addrEnd=76e74000
UPGRADED_MSG: lock: addrStart=76e8c000, addrEnd=76e94000
UPGRADED_MSG: lock: addrStart=76e9d000, addrEnd=76ea4000
UPGRADED_MSG: lock: addrStart=76ea7000, addrEnd=76eae000
UPGRADED_MSG: lock: addrStart=76eb6000, addrEnd=76ebd000
UPGRADED_MSG: lock: addrStart=76f34000, addrEnd=76f3b000
UPGRADED_MSG: lock: addrStart=76f57000, addrEnd=76f5e000
UPGRADED_MSG: lock: addrStart=76f6b000, addrEnd=76f72000
Name: upgraded, bulid date: Dec 12 2015 03:27:19, svn: 537
UPGRADED_MSG: start download file
Then I get a software caused connection abort.
ANY GUIDANCE WOULD BE GREATLY APPRECIATED.