VTH 5221D

sag

n3wb
Mar 23, 2022
7
0
kar
Dear All

I have bricked by dahua VTH5221D intercom monitor and now its keep restarting after I tried flashing it . Can anyone please help me figure out how to unbrick it ?

I am completely new to this . Please advise how can I connect with the device serial port ? what connections I need to make ?.

Also you please tell what are these two ports ? ?

Picture attached
 

Attachments

  • 1.jpeg
    1.jpeg
    76.3 KB · Views: 37
UART VTH5221D

Take an old fw like this one: General_VTH52X1D_Eng_P_V1.000.0000.0.R.20170410 and don't touch the bootloader!!!

Use this commands.txt
Code:
tftp 0x82000000 romfs-x.cramfs.img; flwrite
tftp 0x82000000 user-x.cramfs.img; flwrite
tftp 0x82000000 data-x.cramfs.img; flwrite
tftp 0x82000000 gui-x.cramfs.img; flwrite
tftp 0x82000000 kernel-x.cramfs.img; flwrite
tftp 0x82000000 pd-x.cramfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5

After successful bootup you can upgrade it the official way.
 
Last edited:
UART VTH5221D

Take an old fw like this one: General_VTH52X1D_Eng_P_V1.000.0000.0.R.20170410 and don't touch the bootloader!!!

Use this commands.txt
Code:
tftp 0x82000000 romfs-x.cramfs.img; flwrite
tftp 0x82000000 user-x.cramfs.img; flwrite
tftp 0x82000000 data-x.cramfs.img; flwrite
tftp 0x82000000 gui-x.cramfs.img; flwrite
tftp 0x82000000 kernel-x.cramfs.img; flwrite
tftp 0x82000000 pd-x.cramfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5

After successful bootup you can upgrade it the official way.


I was able to find serial port with your help but after sucessful flashing I get stuck again...I am using the same Firmware as you advise.
after flashing VTH doesnt boot at all, or the screen is completely dark. No display
.
I have attached putty log file with this post. Please advise. Thank you again.
 

Attachments

  • firmware loading hang.png
    firmware loading hang.png
    996.4 KB · Views: 20
I made a mistake .. I flashed dm365_ubl_boot_16M.bin.img and now I am stuck . Please help . Is there anything we can do ?

DHBOOT# saveenv
Saving Environment to SPI Flash...
Environment SPI flash not initialized
DHBOOT#

[SERIAL/DIRECT] CONNECTED TO PORT COM3 (115200-8N1)


Checking DDR......OK

UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (Mar 28 2017 - 19:34:15)

DRAM: 128 MB
SF: Got idcode ef 40 19 00 00
SF: Unsupported Winbond ID 4019
*** Warning - probe error, using default environment

*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x01,id:1cc816
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
Environment SPI flash not initialized
Error when Got kernel from SPI flash!
Environment SPI flash not initialized
Error when Got kernel from SPI flash!
DHBOOT#




1648285728653.png
 
Last edited:
No, you are pretty f*****. The only way to recover is to program the flash ic with a external programmer.
Did this once, but it is hard for unexperienced users.
I suggest to sell the device.
 
Read out the chip, place correct bootloader at the start-address of the current bootloader and flash it.
Then you should be good to start over again.
 
Last edited: