Dahua IPC EASY unbricking / recovery over TFTP

Regardless of the fault message (timeout), does your device boot up after the upgrade at all?
If not, what does UART output tell you?
 
Sorry, without UART it's quite hard to say, what's the real problem.
Did you doublecheck, if you'r tryin to flash the right software? What device, what firmware file r u workin with?
 
File is normal.
Try rename it, change tftp template, try it only 1 without run ... but many times, stop your antivirus.
 
Yes.
Dublicate this string several time
Try rename file and use rename at this script.
Such a feeling that there is no file or access to it for other reasons.
Start tftp from another directory, closer to the root of the disk!
 
rename pd-x.squashfs.img to romfs-x.squashfs.img
don't forget about
run dr
at your script
 
Open your ipc and connect to ttl.
Stop u-boot loading and enadle dh_keyboard.
Put here boot-log.
 
usaf_pride said:
First off, this 5231 camera always seemed a bit odd, but it was working, so I put up with some weird reboots along the way. I decided to UG the firmware to get the day/night functionality and the UG seemed to go ok, but it would run for 5 minutes and then reboot. I then attempted to downgrade the firmware back to the original and of course at 99% it reboots and went into a boot loop. I got the TFTP working and was able to get the November 2017 firmware on board and it was working. Not one to leave well enough alone, I thought I would go back to the September firmware that was originally on the camera and of course, boot loop. No worries (so I thought) I'll just go back to the November firmware that was working. Same result for that firmware or any other firmware that I try to install.

My command.txt has (removed the pd-x.squashfs.img as it would timeout)
Code: 
run dr
run dk
run du
run dw
run dp
run dc
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5

The TFTP server reports success:
Code: 
Listening On: 192.168.254.254:69
Client 192.168.1.108:2655 root\upgrade_info_7db780a713a4.txt, 1 Blocks Served
Client 192.168.1.108:2815 root\romfs-x.squashfs.img, 910 Blocks Served
Client 192.168.1.108:3735 root\kernel.img, 1070 Blocks Served
Client 192.168.1.108:1446 root\user-x.squashfs.img, 10517 Blocks Served
Client 192.168.1.108:3000 root\web-x.squashfs.img, 4448 Blocks Served
Client 192.168.1.108:3274 root\partition-x.cramfs.img, 6 Blocks Served
Client 192.168.1.108:1364 root\custom-x.squashfs.img, 31 Blocks Served
Client 192.168.1.108:2191 root\.FLASHING_DONE_STOP_TFTP_NOW, 1 Blocks Served

and the console has this at the end (all img's appear to download and write 100%)
Code: 
partition file version 2
rootfstype squashfs root /dev/mtdblock5
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
cmdLine console=ttyS0,115200 mem=118M root=/dev/mtdblock5 rootfstype=squashfs init=/linuxrc

Is it the bootargsParamaters.txt that is causing this or some other issue? My other 3 cameras took the update successfully with no issues. Like I said, this was a weird camera to start with.
Click to expand...


Did you ever get this to work? I seem to have the exact same problem.
 
Can someone please confirm what is the first step to unbrick my VTO2000A ?$Installed wrong fw on it and can't g back to previous firmware.
What is the first thing to do - is it possible that someone please explains step by step, slowly (I have time).

P.S. Do I need specific material / dongle to do so ?

Many Thanks !!!
 
ok, I see first step is to connect the VTO to the computer, you have done it over the switch method or connecting to the computer directly ?
Do you need specific material ?
 
I suggest a switch. The timeframe in boot when VTO tries to connect to the tftp server is very short. Via a switch, the ethernet port of the PC hosting the servers is already up when VTO is booting.
 
ok guys, i am blocked at the first step where I need to connect the VTO and the computer to the same switch ... have you used the Dahua switch to connect both or an external PoE switch ?

If I use the Dahua switch, the VTO is powered on, but the computer connected to the same switch is not getting an IP adress it seems.

If I use a Netgear Prosafe PoE GS108P unmanaged switch, the cmputer is getting an IP adress, but the VTO connected to one of the PoE ports is not powered on (the led on the switch is not on ...)

Can you please clarify how you did it ?
 
Last edited:
You must log in or register to reply here.
Top Bottom