IPC-T5442T bricked? Any way out?

J

Joepoe

n3wb
Nov 11, 2021
13
10
There where Home is
Received my new T5442T camera from @EMPIRETECANDY this week. Everything fine including discovery, setting user & password, assigning a proper IP address until updating firmware to (Andy's) februari 2022 version thru the webinterface.. To prevent discussion about "need": I want all camera's on the same firmware, this one was july 2021. Waited a LONG time but this camera never came back online.

After about 15-20 minutes took the power off to reboot manually. The camera never came back. Tried discovery with the config-tool, tried reset button and config tool again - no dice. As the camera runs on PoE of a switch I checked the status:
Power consumption on booting seems normal compared to other (identical) camera, about 15W. After booting power drops to about 50% of the working camera.

Looking at the network log I see the camera coming up and almost immediately going in a continuous up/down connection loop. The working camera connects about about 25 seconds - 2 tries, probably because of speed/PoE negotiation or something - after (re)connecting the powered network cable. Switched cables between camera's, same behaviour. Used a dumb (non-PoE) switch and a separate 12V 1A power supply - same problem but of course no log information.

Question: Is there anyway to reset/reprogram the firmware without an ethernet connection (hard-wired, serial, USB, whatever)? If not: do I have myself a nice, expensive paperweight?

Thanks!
 
Try to make a hard reset to the camera, press the reset button for 5-7 seconds, make sure camera is using good power.
then camera can be defaulted. Normally this kind of camera not easy brick after update.
The 12V1A will not work well. Use 12V 2A adapter is the best. Lots of adapters on the market are poor quality and the injector too.
Here is the real power camera need.
12V DC (±30%)/PoE (802.3af)/ePoE
 
  • Like
Reactions: Gimmons, Old Timer, sebastiantombs and 4 others
Thanks Andy, will try the reset again. PoE power from Cisco PoE switch should be OK:
1658325639639.png

Port 6 is the new camera, port 5 is the working camera. If reset will still not fix the problem I will a separate (new) network, I have a 30A 12V PSU as well so will do some more attempts but that will have to wait till the weekend.
 
  • Like
Reactions: JDreaming and c hris527
OCD bites again LOL.

I had this happen once before I finally decided not to fix what ain't broke. Some of my cams are on 2019 firmware and I am fine with that because the camera flat out works and it is isolated from the internet so no reason to update it due to a vulnerability patch.

I held down the reset button long enough to hear the IR cut filter 15 times (so a couple of minutes) and after that the camera came back. Strangely, I had to initialize it in Edge as the drop-down boxes wouldn't show in Explorer.

I know its hard, but resist the urge if the camera is working for your needs....Updating for kicks and grins to all be on the same update usually results in an issue somewhere.
 
  • Like
Reactions: sdkid, StevenFromTexas, JDreaming and 5 others
Making some progress. Made separate stand-alone network setup with some spare stuff, installed Wireshark to see if anything is going on and lo and behold, the camera identifies itself with IP address 192.168.1.251???? Looking for 192.168.1.1. Will need further research as I am not a network specialist.

@wittaj will try the loooong reset tomorrow, for now to hot inside. Yes, agree about firmware update, I don't always update but like to have some common baseline over equipment.......
 
  • Like
Reactions: JDreaming
were you able to see a user interface login at ....251?
 
  • Like
Reactions: JDreaming
I think the .251 address is a default address used by the boot loader. In that case it won't be an address where you can get to the cam's web interface. Search Dahua and 192.168.1.251 and you should find some info. But it's still alive and trying so there's a chance I think to load the firmware via TFTP. I'm not a good guy to walk you through that but take a look at some of the unbricking threads here.
 
  • Like
Reactions: Old Timer, Joepoe, Flintstone61 and 1 other person
Mike A. said:
I think the .251 address is a default address used by the boot loader. In that case it won't be an address where you can get to the cam's web interface. Search Dahua and 192.168.1.251 and you should find some info. But it's still alive and trying so there's a chance I think to load the firmware via TFTP. I'm not a good guy to walk you through that but take a look at some of the unbricking threads here.
Click to expand...
Thanks! had not found those yet, probably been looking for the wrong subject.

@Flintstone61 No, have not gotten that far yet - only noticed the advertised IP which I could not place and with a 30C temperature plus instable laptop did not feel like looking further.

Have a feeling a solution could be within reach. Will give an update later but not forseveral days I suspect.
 
Hey @Joepoe - were you able to find a resolution to this issue? I have a brand new camera behaving exactly the same way as in your first post after an attempted firmware update, and hardware reset isn't working.
 
Camera brick, just ask amazon for a replacement. When make update, make sure camera is good powered and network cable is stable, sometimes brick when these 2 has some poor working.
 
  • Like
Reactions: cambender and sebastiantombs
wittaj said:
OCD bites again LOL.

I had this happen once before I finally decided not to fix what ain't broke. Some of my cams are on 2019 firmware and I am fine with that because the camera flat out works and it is isolated from the internet so no reason to update it due to a vulnerability patch.

I held down the reset button long enough to hear the IR cut filter 15 times (so a couple of minutes) and after that the camera came back. Strangely, I had to initialize it in Edge as the drop-down boxes wouldn't show in Explorer.

I know its hard, but resist the urge if the camera is working for your needs....Updating for kicks and grins to all be on the same update usually results in an issue somewhere.
Click to expand...
While I would generally agree, the updated firmware resolves some IR issues that existed in the original firmware.
 
  • Like
Reactions: EMPIRETECANDY
I bricked a DH-IPC-HDW5231R-Z a while back after a firmware update, only with help of members of IPCT did I effect a recovery. It's not a process I want to repeat.

Dahua IPC EASY unbricking / recovery over TFTP

I've tried everything ... I get him to go back to china but in ntsc, not in pal. before it was like this: Device Type IPC-HDW4631C-A System version 2.460.GP01.16.R, Build Date: 2017-09-04 WEB3.2.1.491565 version ONVIF version 16.12 (V2.4.0.485616) After updating, blocked, only ping, I used...
ipcamtalk.com ipcamtalk.com

I still do firmware updates but only if justified and I am prepared to take down a camera and replace it.
I suggest when doing a reset you keep the reset button pressed for at least 30 seconds.
 
  • Like
Reactions: EMPIRETECANDY and sebastiantombs
Joepoe said:
Making some progress. Made separate stand-alone network setup with some spare stuff, installed Wireshark to see if anything is going on and lo and behold, the camera identifies itself with IP address 192.168.1.251???? Looking for 192.168.1.1. Will need further research as I am not a network specialist.

@wittaj will try the loooong reset tomorrow, for now to hot inside. Yes, agree about firmware update, I don't always update but like to have some common baseline over equipment.......
Click to expand...

@Joepoe Did you ever get any further with this. One of my cams went down the other night (after nearby lightning I think) and will no longer boot. Did the same as you, have set up a isolated network, and installed Wireshark, and all I can see from the cam (on 192.168.1.251) is ARP requests asking about 192.168.1.1

I got the files from the "Dahua IPC EASY unbricking / recovery over TFTP" thread, and have run the TFTP and console programs, but the cam never seems to make contact.
 
Sorry, have not been able to reply sooner. Been off line for health reasons but today picked up the bricked camera issue again.

@cambender Issue still not fixed

@EMPIRETECANDY Andy, thanks for reply. Time to return has been way to long - besides, it is an issue I have caused. The only problem with the camera is the inability to recover, there should be some way to get to a basic working device. In my opinion that is a Dahua issue.... Cables are certified Cat6 SFTP, should be fine. Original PoE was Cisco, PoE+ router - should have been fine, now running off an adapter. My other cam's did fine updating with this setup, so adapter seems OK as well.

@toastie Thanks, I'll check that out. I could not get TFTP to work last year, maybe this year will be better. The solution might be loading through a serial (or USB) connection similar to loading an ESP8866, ESP32 or similar, just haven't found anything about that yet. Reset for 5-10 secs, 30 secs, 3 minutes, 5 minutes - it makes no difference.....

@iandrews I restarted today. Am at the point of a seperate network: camera @ 192.168.1.251 <> router @ 192.168.1.1 <> laptop @ 192.168.254.254. Wireshark shows it wants the recoveryfiles from 192.168.254.254. That will be the next step, however I remember from last year that it was asking for the files on 3 different ports (forgot the numbers) and when uploading to 1 using the tool in the recovery set or using MobaXterm the upload would be "successful" before giving a failure message within seconds.

When/if there is progress/failure I'll post again, I like a challenge but this takes time and energy which are currently both in short supply. In the mean time: If anyone knows of a method to load via a serial connection or some other offbeat method I'm interested.....
 
Hi Joe

maybe send to warranty center to do fix up it if you are in US.
 
  • Like
Reactions: CanCuba
wittaj said:
OCD bites again LOL.

I had this happen once before I finally decided not to fix what ain't broke. Some of my cams are on 2019 firmware and I am fine with that because the camera flat out works and it is isolated from the internet so no reason to update it due to a vulnerability patch.

I held down the reset button long enough to hear the IR cut filter 15 times (so a couple of minutes) and after that the camera came back. Strangely, I had to initialize it in Edge as the drop-down boxes wouldn't show in Explorer.

I know its hard, but resist the urge if the camera is working for your needs....Updating for kicks and grins to all be on the same update usually results in an issue somewhere.
Click to expand...
My recent foray into update-it-stan cured me of my OCD. Good luck to the OP.
 
  • Like
Reactions: CanCuba
EMPIRETECANDY said:
Hi Joe

maybe send to warranty center to do fix up it if you are in US.
Click to expand...
Hi Andy,

no luck - EU, delivery came through Ali but thanks for the suggestion - sending back would be more trouble than it's worth I think, half of it was already paid with customs savings from the other 2 cams which work fine running aug 2022 firmware- it's just part of life.

Next cam I buy should not be so Internet Explorer dependent :cool:
 
  • Like
Reactions: Flintstone61
That is bad, i will check if has some way to do a remote support for you. You have all serial port tools ready?
 
You must log in or register to reply here.
Top Bottom