Hi,
trying to unbrick my VTO with the tools described here, following is the code I read:
And nothing happens
trying to unbrick my VTO with the tools described here, following is the code I read:
Code:
U-Boot 2010.06-svn2661 (Jul 10 2015 - 17:23:04)
DRAM: 1 GiB
gBootLogPtr:80b80008.
NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x98 0xF1 0x80 0x15 0xF2 0x16 0x08 0x00
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 3
state:ff,err_count:02
ETH0: PHY(phyaddr=-1, rmii) not link!
Try again use backup_serverip
ETH0: PHY(phyaddr=-1, rmii) not link!
Failed to get info.txt
Fail to get info file!
Init error!
ETH0: PHY(phyaddr=-1, rmii) not link!
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2232408 Bytes = 2.1 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=349M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
crashflasg:1, logmagic:54410011.
Starting kernel ...
Uncompressing Linux... done, booting the kernel.And nothing happens
riogrande75
Pulling my weight
Thanks for answer. That attempt was made without ethernet cable plugged in, using a software called terminal, because putty initially was unable to connect.
Yesterday finally putty worked fine. With * pushed I was able to obtain what show us on first post of this thread. This evening I'll try further steps. Finally I have to add that in VTO3221/3211 model the uart is different and when my work reaches the espected results, as I hope, I will post pictures that could be useful for others. Meantime I hope for an help here for the further steps.
Yesterday finally putty worked fine. With * pushed I was able to obtain what show us on first post of this thread. This evening I'll try further steps. Finally I have to add that in VTO3221/3211 model the uart is different and when my work reaches the espected results, as I hope, I will post pictures that could be useful for others. Meantime I hope for an help here for the further steps.
First of all I need to understand exactly what does it mean:
my firmware image is a file .bin, is this file to be "extracted" ? File .bin to me is not an archive. Or it means that in this image.bin I can find subset of image files to do this?:
Sorry, but how can I extract these files from my image.bin file ?
riogrande75
Pulling my weight
alastairstevenson
Staff member
Are you referring to the original firmware distribution, or a full flash image recovery file?
The firmware is just a normal zipfile with the first 2 bytes switched from PK (Phil Katz - remember him? PKware) to DH, inside the zip archive are the various components.
Change DH to PK
I don't have firmwares in zip format. I have only .bin files downloaded also from a dahua repository and from other websites. All are bin files. How can figure out if they are full flash recovery files ? Maybe the size could suggest something ( they are about 25mb) ? Or the name, i.e: General_VTO3211D_Eng_P_32M_V3.200.0012000.0.R.20180615.bin ?
edit: in the same repository you can find bin files for IPC, no ZIP files avalaible there:
Index of /Firmware/Dahua Firmware/Baseline Firmware/IP/IP Cameras/IPC-HX8XXX-Eos
So for mine VTO all files are bin also.
edit: in the same repository you can find bin files for IPC, no ZIP files avalaible there:
Index of /Firmware/Dahua Firmware/Baseline Firmware/IP/IP Cameras/IPC-HX8XXX-Eos
So for mine VTO all files are bin also.
Last edited:
Within the aforementionned .zip file, your .bin file is alotted as well, however tons of other files (like cramfs/sonia.zip etc) too, which you would need if you flash by TFTP. If you flash by Configtool/VDPConfig, only the .BIN file is enough. Works like a charm for VTO/VTH.
Hope this helps!
CC
Hope this helps!
CC
alastairstevenson
Staff member
The .bin files are actually slightly modified ZIP files, with the first 2 bytes changed as above, and without the .zip extension.
Very disappointed but I have at least a question for each step ! I have the VTO connected with an ethernet cable directly to the laptop but it find always my gateway as a server. Do I to switch off the wifi of the laptop?
Can't believe that this VTO has a wifi board, so what means this line : wifiaddr=00:12:34:56:78:91
Code:
U-Boot 2010.06-svn2661 (Jul 10 2015 - 17:23:04)
DRAM: 1 GiB
gBootLogPtr:80b80008.
NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x98 0xF1 0x80 0x15 0xF2 0x16 0x08 0x00
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 3
state:ff,err_count:03
Hit any key to stop autoboot: 0
> printenv
bootcmd=kload 0x82000000; bootm 0x82000000
bootdelay=1
baudrate=115200
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91
dh_keyboard=1
sysbackup=1
loglevel=4
ethact=gmac
filesize=1A595C5
fileaddr=82000000
da=tftp 0x82000000 dhboot.bin.img;flwrite;tftp 0x82000000 dhboot-min.bin.img;nand protect off;flwrite;
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite;
dk=tftp 0x82000000 kernel.img;flwrite;
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite;
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img;flwrite;
tk=tftp 0x82000000 uImage;bootm;
HWID=VTO3221D:01:04:01:36:1A:17:01:11:03:03:04:258:00:02:00:00:00:00:00:00:200:FF
appauto=1
ID=4E05687PAZD2581
ethaddr=38:AF:29:65:B9:F0
bootargs=mem=349M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06-svn2661 (Jul 10 2015 - 17:23:04)
Environment size: 1065/131068 bytes
>Can't believe that this VTO has a wifi board, so what means this line : wifiaddr=00:12:34:56:78:91
Hi,
as you can see here finally did the work:
But the VTO is still in a boot loop. On boot I see always errors like bootargsParameters. Can anyone suggets something to do ( non the waste pls) ?
as you can see here finally did the work:
Code:
> run dr
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'romfs-x.squashfs.img'.
Download to address: 0x82000000
Downloading:#################################################
done
Bytes transferred = 1204288 (126040 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: romfs
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 1204224 Bytes = 1.1 MiB
Load Address: 01200000
Entry Point: 01a00000
Verifying Checksum ... OK
Programing start at: 0x01200000
write : 100%
done
> run dk
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'kernel.img'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 2232536 (2210d8 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: kernel
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 2232472 Bytes = 2.1 MiB
Load Address: 00d00000
Entry Point: 01200000
Verifying Checksum ... OK
Programing start at: 0x00d00000
write : 100%
done
> run du
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'user-x.squashfs.img'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 22237248 (1535040 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: user
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 22237184 Bytes = 21.2 MiB
Load Address: 02200000
Entry Point: 03b80000
Verifying Checksum ... OK
Programing start at: 0x02200000
write : 100%
done
> run dw
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'web-x.squashfs.img'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 1355840 (14b040 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: web
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 1355776 Bytes = 1.3 MiB
Load Address: 01a00000
Entry Point: 01e00000
Verifying Checksum ... OK
Programing start at: 0x01a00000
write : 100%
done
> run dp
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'partition-x.cramfs.img'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 4160 (1040 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: partition
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 4096 Bytes = 4 KiB
Load Address: 00500000
Entry Point: 00600000
Verifying Checksum ... OK
Programing start at: 0x00500000
write : 100%
done
> run dc
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.254.254
Download Filename 'custom-x.squashfs.img'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 16448 (4040 hex)
## Checking Image at 82000000 ...
Legacy image found
Image Name: custom
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 16384 Bytes = 16 KiB
Load Address: 00600000
Entry Point: 00980000
Verifying Checksum ... OK
Programing start at: 0x00600000
write : 100%
done
>But the VTO is still in a boot loop. On boot I see always errors like bootargsParameters. Can anyone suggets something to do ( non the waste pls) ?
riogrande75
Pulling my weight
What firmware image did you try to install? I miss "pd-x.cramfs.img" but I never hat found "partition-x.cramfs.img" in one of the firware images I flashed so far.
Can you post the logs from the bootloop?
Can you post the logs from the bootloop?
Thanks Riogrande fro interesting to. Here is the booloop code:
Trying three different firmwares, the result it's the same. Names of firmwares are:
General_VTO3211D_Eng_P_32M_V3.200.0012000.0.R.20180615
General_VTO3221D_Eng_P_32M_SIP_V3.200.0012001.0.R.20180330
General_VTO3221D_EngItlSpnFrnDthGetPtg_P_32M_V3.200.9999000.0.R.20180421
I have to add that I've bought the VTO3211D P2, but when I connected it the first time to config tool the hardware device recognized was VTO3221D, so I desume they are different versions of the same hardware. Anyway doesn't work 3211 nor 3221 firmware.
Code:
▒
U-Boot 2010.06-svn2661 (Jul 10 2015 - 17:23:04)
DRAM: 1 GiB
gBootLogPtr:80b80008.
NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x98 0xF1 0x80 0x15 0xF2 0x16 0x08 0x00
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 3
state:ff,err_count:01
Hit any key to stop autoboot: 0
> boot
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2232408 Bytes = 2.1 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=349M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
crashflasg:1, logmagic:54410011.
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
U-Boot 2010.06-svn2661 (Jul 10 2015 - 17:23:04)
DRAM: 1 GiB
gBootLogPtr:80b80008.
NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x98 0xF1 0x80 0x15 0xF2 0x16 0x08 0x00
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 3
state:ff,err_count:02
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Download Filename 'upgrade_info_7db780a713a4.txt'.
Download to address: 0x84000000
Downloading: *
Retry count exceeded; starting again
Try again use backup_serverip
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
*** ERROR: `serverip' not set
Failed to get info.txt
Fail to get info file!
Init error!
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: 38-AF-29-65-B9-F0
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Download Filename 'failed.txt'.
Download to address: 0x82000000
Downloading: *
Retry count exceeded; starting again
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2232408 Bytes = 2.1 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=349M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
Starting kernel ...
Uncompressing Linux... done, booting the kernel.Trying three different firmwares, the result it's the same. Names of firmwares are:
General_VTO3211D_Eng_P_32M_V3.200.0012000.0.R.20180615
General_VTO3221D_Eng_P_32M_SIP_V3.200.0012001.0.R.20180330
General_VTO3221D_EngItlSpnFrnDthGetPtg_P_32M_V3.200.9999000.0.R.20180421
I have to add that I've bought the VTO3211D P2, but when I connected it the first time to config tool the hardware device recognized was VTO3221D, so I desume they are different versions of the same hardware. Anyway doesn't work 3211 nor 3221 firmware.
riogrande75
Pulling my weight
Ahh... you must flash ALL partitions! Without flashing the signature partition (sign.img) the system will remain in a reboot loop.
Sonia (the main program on the device) checks signatures and if there is something wrong it will reboot the device.
I do not really know the abbreviation code ("run xx") for the sign.img partition, so do the following:
Get a old (unsigned) firmware for your device (from 2017), maybe this one: http://ftp.tdtorus.ru/Firmware/VDP/...O3221D_Eng_P_32M_V1.000.0000.0.R.20171009.bin
Extract it and flash it as usual. Then your device should come up and you should be able to upgrade it to latest version 2018.06.15 the official way with VDPconfig.
Sonia (the main program on the device) checks signatures and if there is something wrong it will reboot the device.
I do not really know the abbreviation code ("run xx") for the sign.img partition, so do the following:
Get a old (unsigned) firmware for your device (from 2017), maybe this one: http://ftp.tdtorus.ru/Firmware/VDP/...O3221D_Eng_P_32M_V1.000.0000.0.R.20171009.bin
Extract it and flash it as usual. Then your device should come up and you should be able to upgrade it to latest version 2018.06.15 the official way with VDPconfig.
