Dahua IPC EASY unbricking / recovery over TFTP

I have to double check but yes.
After the last event the nvr is rebooting due to a software reboot :

Code: 
#Load STORAGE SPINAND
ROSC: 0103 threshold: 0100
D-03 Infinity2_DDR3_32_8X_CL14_2133_EXT_Nanya_20181203-F6.h
EXT_NYA2133_20181203-F6
CPU_1400Mhz
Set CPUCORE to 1.05V
BootSource: SW reset
 
Hello guys, could someone help me salvage my VTO2000A or tell if it's time for a new one?
I have gone through every single page on this thread (1-28) and still can't get my VTO working. Here is what I've done:
  1. I am unable to ping the camera regardless the connection method (PoE switch, unmanaged switch with 12v power to camera etc, direct p2p connection etc.)
  2. I'm able to access the camera via USB-TTL and ST-LINKv2 (see attached log from U-Boot I've also added the complete startup dump)
  3. Using ST-LINKv2 I was able to change the firmware using a HEX file (instructions found here)
  4. I know step 2 worked because my language changed from Dutch to English
  5. Following the instruction on page 1 of this thread, I got everything setup - see attached image
  6. When I power up my VTO after everything is connected (tftp and console running), nothing at all happens. No network activity whatsoever
  7. When I run a command such us "run dr" in DHBOOT# I get the following message
    T WARN: emac_send_packet: No link
  8. I also see the following messages in a more verbose log:
    davinci_eth_open:no link
    WARN: emac_send_packet: No link
    Retry count exceeded; starting again
    IP-Config: No network devices available.
  9. I also don't see any lights burning when I connect the camera to the switch - not sure this is important
Now my biggest fear.
Could this be a hardware issue with my network interface? PoE connection still powers on the VTO by the way.
Could this be a hardware issue or perhaps a software issue that can still be fixed.
Any help or pointers in the right direction will be greatly appreciated. Thanks in advance.
 

Attachments

  • netip.png
    netip.png
    36.8 KB · Views: 0
Hello,
I have a VTH2421FB(W)-P which I tried to upgrade with DH_VTHX421H_MultiLang_SIP_EMEA_V4.800.0000000.0.R.241114.zip.
But I made a mistake and give to ConfigTool 2 times the DH_VTHX421H_MultiLang_SIP_EMEA_V4.800.0000000.0.R.241114_part1.bin ...

Now my VTH screen is black, and when I look to my switch POE status is ON but Port status is OFF.

I tried the Dahua_TFTPBackup.zip (which it already rescued one of my camera) but, nothing happen. I guess the Ethernet port is not running?

There is a COM port behind the VTH with 12 pin (IN1 IN2 IN3 IN4 GND IN5 IN6 N/A N/A GND NO COM), is there a way to use it ?

Any thought ?

EDIT : COM port is an ALARM PORT
EDIT2 : I plug 12V directly in the VTH and it start, it appears POE is not working anymore on the VTH (I tried 3 differents POE switch with different cable, which work with my POE Camera)
Is it possible a firmware issue cause POE stop working ?

Thanks
 
Last edited:
Focster said:
Hey, everybody.
I got a DH-IPC-HFW4433F-ZSA camera.

View attachment 200862

Received it in a state of not booting.
I managed to download the firmware DH_IPC-HX4XXX-Eos_Chn_PN_Stream3_V2.680.0000000.46.R.231027.bin via tftp.

The camera started up, I can access its web interface (only in Chinese) or configure it via SmartPSS.

I can add the camera to the Dahua recorder (Europe) on the old firmware of the recorder.
I can NOT add a camera to Dahua (Europe) on the new firmware of the recorder 4+....

Is there any broken firmware for this camera, so that it works with Dahua recorders (not Chinese) with firmware version 4+...??
Click to expand...
I have the same camera, not booting, like yours. Could you please post here the firmware you got? thank you.
 
Hello there!

My situation is that I have VTH1560B on v4.000.0000.0.R.20180622 firmware right now. I need to downgrade it to v2.100 or even v1.000 to get it to work with my household. And of course I cant make it through configtool.
I have read this thread about TFTPtools and etc. and prepared all necessary files and commands like described but I cant make devices to start TFTP session...

I have tried to create environment (like option 2) in which VTH is 192.168.1.108 (255.255.0.0 and gateway 192.168.1.1) is connected directly to single notebook with IP 192.168.254.254 (255.255.0.0 and gateway 192.168.1.1).
Then I start TFTPServer.bat and Console.bat. TFTP-server says something like "Listening to 192.168.254.254:69"
Then I powerup the VTH...

And nothing happens. VTH is just starting main program and TFTP-server standing still...

What am I doing wrong?
 
Hello Guys!

i have old AV-VTI03W Dahua VTH1550CH with brick firmware - totaly blank screen.


ChatGPT, after scanning the sticker, indicated that this is a 1510, not a 1550?? Strange. I tried flashing that firmware and a bunch of others from the 1550 and 1510 series too... everything ended with 'failed' right after this:


kernel-x.cramfs.img, 1149 block served
failed.txt


Please advise what could have happened here or which firmware I need to load because i have new silver hair on my head :)
 
Hello,
I have a Dahua 1431 that doesn't save settings. Restore to factory with inside button doesn't work.
When I try update via TFTP i get the message as below. What am I doing wrong?

Using ambarella mac device
TFTP from server 192.168.1.9; our IP address is 192.168.1.241
Download Filename 'romfs-x.squashfs.img'.
Download to address: 0x2000000
Downloading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################################################
done
Bytes transferred = 3303672 (3268f8 hex)

## Checking Image at 02000000 ...
Legacy image found
Image Name: romfs
Created: 2019-12-02 7:54:50 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3303608 Bytes = 3.2 MiB
Load Address: 01b80000
Entry Point: 01fd0000
Verifying Checksum ... OK
Programing start at: 0x01b80000
SPI probe: 32768 KiB W25Q256FV at 0:1 is now current device
write : 0%__do_write_flashSpi: error!
flwrite error 1!
 
You must log in or register to reply here.
Top Bottom