Dahua DH-SD50225U-HNI BRICKED

[aloha984]

Hello can somebody please help me of unbricking dahua dh-sd50225u-hni.

I have tried from the unbricking thread of previous cameras but no success...from this link

Dahua IPC EASY unbricking / recovery over TFTP

A successor of Dahua IPC unbricking / recovery over serial UART and TFTP I recommend you to read through the above thread first. If your camera still has a working bootloader (assume it does) then you can flash it easily, because: The camera tries to download a file called...

ipcamtalk.com

i dont understand why my network card has to be on different subnet from the camera...
when i make conection on camera through putty (serial conection) i see
ip: 192.168.1.108
subnet:255.255.255.0
default gatway:192.168.1.108
server ip:192.168.1.1

but i cannot make network conection on camera..
I have tried with router, with switch i changed subnet on my nic from 255.255.255.0 to 255.255.0.0 as said in post no luck..
it has started downloading from root directory updateing something than suddenly it said timed out...

what is the problem with camera network adapter...i look for the cables , tried new utp cable(factory original) but no luck...
I am having feeling that network adapter on camera doesn`t cam up....

Once it has showned it`s ip adress on router 192.168.1.108 but suddenly it has dissapear

i have a firmware file that was good (i flashed with smaller file than recomended 28mb,)

here are the photos in attachmen...

I am having trouble with this since april 2020


Please somebody for help/hint...

Thank you

 

[aloha984]

This is my last progress....is it possible that network card on camera turns on and off when bootin ...
when i boot it finds it for second and two but soon it disconects..


U-Boot 2010.06-svn3089 (Jul 12 2016 - 21:13:31)
DRAM: 1 GiB
gBootLogPtr:80b80008.
NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x92 0xF1 0x80 0x95 0x40 0x7F 0x7F 0x7F
NAND_ECC_NONE selected by board driver. This is not recommended !!
128 MiB
partition file version 2
rootfstype squashfs root /dev/mtdblock7
In: serial
Out: serial
Err: serial
TEXT_BASE:81000000
Net: PHY found at 1

ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 00-12-34-56-78-9A
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throgh gateway 192.168.1.1
Download Filename 'upgrade_info_7db780a713a4.txt'.
Download to address: 0x84000000
Downloading: #################################################
done
Bytes transferred = 202 (ca hex)
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 00-12-34-56-78-9A
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throgh gateway 192.168.1.1
Download Filename 'romfs-x.squashfs.img'.
Download to address: 0x82000000
Downloading: *
ARP Retry count exceeded; starting again
cmd Failed run dr!
partition file version 2
rootfstype squashfs root /dev/mtdblock7
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
get bootargs info failed
cmdLine mem=256M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
ETH0: PHY(phyaddr=-1, rmii) not link!
ETH0: PHY(phyaddr=-1, rmii) not link!
state:ff,err_count:03
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2641032 Bytes = 2.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ...OK
OK
partition file version 2
rootfstype squashfs root /dev/mtdblock7
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
get bootargs info failed
cmdLine mem=256M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
crashflasg:1, logmagic:54410011.

Starting kernel ...
Uncompressing Linux... done, booting the kernel.