VTO2111D-WP bricked, won't recover

Joined
Mar 23, 2019
Messages
5
Reaction score
0
Location
Portugal
Hi, perhaps my problem is to setup the UART.
What do I need to establish the connection between the VTO and the PC?

I assume that to achieve a correct UART connection, I will need to have a special interface and make a correct wiring setup.
So far I`ve connected the VTO to the PC via RJ45 cable, and made the static network configuration explained in the link mentioned in the comment above.

Do you have a drawing or photo explaining the connections and interface, required to establish the connectivity between the VTO and the PC, required to run the TFTP?

Thanks for your help.
 

cazanova

n3wb
Joined
Feb 12, 2019
Messages
5
Reaction score
1
Location
Colombia
To connect the PC and the VTO in LAN network is possible through a router, switch or direct connection between the two devices
 
Joined
Mar 23, 2019
Messages
5
Reaction score
0
Location
Portugal
I`ve tried the LAN network connection, but that is not working.

So, I think that I need to connect the VTO to a PC with CP2102 USB to UART bridge, and my question is how can I identify in the VTO motherboard the serial port location and the correct pinout.

The file VTO MB.docx bellow, contains the VTO motherboard photo with two red circles to signalise in my opinion the possible serial port locations, I think the correct one is the one in the left top corner, and in that case I need to identify the correct pin out: 3,3v, GRD, RX e TX.

Any help?
 

Attachments

cazanova

n3wb
Joined
Feb 12, 2019
Messages
5
Reaction score
1
Location
Colombia
The UART port is the smallest connector located in the lower left and the order of the pins is: 3.3v GND Rx TX. Remember to connect the TX pin of the VTO to the RX pin of the CP2102 and the RX pin to the TX pin respectively.
 

test12345

n3wb
Joined
Jul 3, 2019
Messages
1
Reaction score
0
Location
Malta
For the VTO-2111d, can I connect it via the RS485 to USB adapter to my PC for unbricking? Thanks
 

tykasan

n3wb
Joined
Nov 23, 2019
Messages
5
Reaction score
0
Location
Poland
Dear All,
I have such issue, would you please take a look and tell my why after running all those commands i have a bootloop?
I tried to set up ncat and tftp again, but vto doesnt pick up files...

Code:
Checking DDR......OK

UBL Version: 1.46t(DM365)16:10:30 Aug  4 2017
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)

DRAM:  128 MB
SF: Got idcode c2 20 18 c2 20
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
.......
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1771112 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

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

Code:
bootcmd=fsload
bootdelay=3
baudrate=115200
eth1addr=00:01:5b:00:55:66
eth2addr=00:01:5b:00:77:88
netmask=255.255.255.0
bootfile="uImage"
dh_keyboard=1
single=0
da=protect off all;tftp 81a00000 dm365_ubl_boot_16M.bin.img;flwrite
dc=tftp 81a00000 custom-x.cramfs.img; flwrite
dr=tftp 81a00000 romfs-x.cramfs.img; flwrite
du=tftp 81a00000 user-x.cramfs.img; flwrite
dd=tftp 81a00000 data-x.cramfs.img; flwrite
dw=tftp 81a00000 web-x.cramfs.img; flwrite
dg=tftp 81a00000 gui-x.cramfs.img; flwrite
dk=tftp 81a00000 kernel-x.cramfs.img; flwrite
up=tftp 81a00000 update.img; flwrite
tk=tftp 80800000 uImage; bootm 80800000
gionum=22.25
gioval=1.1
dh_com=0
autosip=192.168.254.254
autolip=192.168.1.108
autogw=192.168.1.1
autonm=255.255.255.0
serverip=192.168.1.16
ipaddr=192.168.1.110
filesize=CACF1C
fileaddr=81A00000
HWID=VTO2111D:0:4:1:1d:5:0:1:9:3:3:0:1B0:0:2:0:0:0:0:0
bootargs=console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=cramfs,nolock mem=90M newmem=96M video=davincifb:vid0=OFF:vid1=OFF:osd0=OFF:osd1=OFF
appauto=1
ID=3L04439PAN00022
wifiaddr=14:A7:8B:0C:BC:EE
ethaddr=14:A7:8B:0D:0C:1F
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)
im trying to insert this image;

can you guys help please/?
when i run any commends i get
 
Last edited:

tykasan

n3wb
Joined
Nov 23, 2019
Messages
5
Reaction score
0
Location
Poland
OK, after few hours of work I was able to recover VTO2111D
but my MY Home panel VTH5221D cannot open door lock when someone ringing to the doors,
Im not able to monitor VTO - but im able to set up as IPC and i can see picture from it.
Do you guys knows what Im missing>?

I was not able to to 'run dp' . So i did flash without it.
Can this be a issue?

one more thing is... now i have boot loader from 2018 (i bought this unit in 2017) i think something overwrite boot loader..
Code:
ver=U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)
should i do downgrade?

please help.
 
Last edited:

tykasan

n3wb
Joined
Nov 23, 2019
Messages
5
Reaction score
0
Location
Poland
OK, guys, got it back and running on firmware 3.120
General_VTO2111D_Eng_P_16M_V3.120.0012000.0.R.20180731
Whole flash with bootloader was done via UART

I also made an upgrade of my VTH5221D to match rifmware revisions..
All works, but one thing..

VTO doesnt switch on IR Led when to dark... even id Scene is set to automatic.

Did anyone had the same issue?
M
 

Ruper

n3wb
Joined
Dec 31, 2019
Messages
2
Reaction score
2
Location
Madrid
Hello all

Let's see if anyone can help me with my bricked VTO2111D.
The thing is that it bricked while upgrading to "General_VTO2111D_Eng_P_16M_V3.120.0012000.0.R.20180731" firmware. Since then the VTO is continuously resetting. I followed the procedure posted here Dahua IPC EASY unbricking / recovery over TFTP with no luck and I´m not able to send any command because the device is continuously resetting.
I´ve executed the tftp server and this is the output:
Code:
accepting requests..
Open TFTP Server MultiThreaded Version 1.64 Windows Built 2001

starting TFTP...
alias / is mapped to root\
permitted clients: all
server port range: all
max blksize: 65464
default blksize: 512
default timeout: 60
file read allowed: Yes
file create allowed: No
file overwrite allowed: No
thread pool size: 1
Listening On: 192.168.254.254:69
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served

This is the output of the UART port:

Code:
Checking DDR......OK

UBL Version: 1.46t(DM365)16:10:30 Aug  4 2017
 Oscillator: 24MHZ
 ARM Rate: 432 MHZ
 DDR Rate: 340 MHZ
 BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)

DRAM:  128 MB
SF: Got idcode c2 20 18 c2 20
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
APP_OFFSET_NEW test
.......
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1798424 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

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

Checking DDR......OK

UBL Version: 1.46t(DM365)16:10:30 Aug  4 2017
 Oscillator: 24MHZ
 ARM Rate: 432 MHZ
 DDR Rate: 340 MHZ
 BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)

DRAM:  128 MB
SF: Got idcode c2 20 18 c2 20
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
APP_OFFSET_NEW test
.......
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1798424 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................ done, booting the kernel.
Uncompressing Linux........................................................................................................................ done, bootiUncompressing Linux........................................................................................................................ done, booting the kernel.
The file upgrade_info_7db780a713a4.txt is created in the root folder with the following content

Code:
CRC:1393106523
MagicString:c016dcd6-cdeb-45df-9fd0-e821bf0e1e62
run dr
run dk
run du
run dw
run dd
run dc
tftp 0x82000000 pd-x.cramfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5
And with the wireshark this is what I get:

Code:
No.    Time    Source    Destination    Protocol    Length    Info    Src Port    Dst Port
1    0.000000    Zte_d4:f0:80    Broadcast    ARP    42    Who has 192.168.1.133? Tell 192.168.1.1       
2    4.608767    192.168.1.141    224.0.0.251    MDNS    289    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
3    4.609658    fe80::62ab:67ff:fec0:5ff3    ff02::fb    MDNS    309    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
4    5.848288    192.168.1.1    224.0.0.1    IGMPv2    46    Membership Query, general       
5    6.333145    192.168.254.254    239.255.255.250    IGMPv2    46    Membership Report group 239.255.255.250       
6    7.535331    192.168.1.108    192.168.254.254    TFTP    84    Read Request, File: failed.txt, Transfer type: octet, timeout=1, blksize=1468    1212    69
7    7.535879    192.168.254.254    192.168.1.108    TFTP    67    Option Acknowledgement, timeout=1, blksize=1468    50866    1212
8    7.542671    192.168.1.108    192.168.254.254    TFTP    46    Acknowledgement, Block: 0    1212    50866
9    7.542747    192.168.254.254    192.168.1.108    TFTP    247    Data Packet, Block: 1 (last)    50866    1212
10    7.548154    192.168.1.108    192.168.254.254    TFTP    46    Acknowledgement, Block: 1    1212    50866
11    7.578793    Zhejiang_0c:8b:48    Broadcast    ARP    60    Who has 192.168.1.1? Tell 192.168.1.108       
12    8.333107    192.168.254.254    224.0.0.252    IGMPv2    46    Membership Report group 224.0.0.252       
13    12.332994    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254       
14    12.801982    fe80::1    ff02::1:ffdc:cefa    ICMPv6    86    Neighbor Solicitation for fe80::66cc:2eff:fedc:cefa from 50:78:b3:d4:f0:80       
15    13.332993    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254       
16    13.333177    192.168.254.254    224.0.0.251    IGMPv2    46    Membership Report group 224.0.0.251       
17    14.332993    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254       
18    15.362362    fe80::1    ff02::1    ICMPv6    102    Router Advertisement from 50:78:b3:d4:f0:80       
19    15.567132    192.168.1.131    224.0.0.251    MDNS    131    Standard query response 0x0000 A, cache flush 192.168.1.131 AAAA, cache flush fe80::62ab:67ff:fee4:cb83 NSEC, cache flush Android.local    5353    5353
20    15.567133    fe80::62ab:67ff:fee4:cb83    ff02::fb    MDNS    151    Standard query response 0x0000 A, cache flush 192.168.1.131 AAAA, cache flush fe80::62ab:67ff:fee4:cb83 NSEC, cache flush Android.local    5353    5353
21    16.284170    Zte_d4:f0:80    Broadcast    ARP    42    Who has 192.168.1.131? Tell 192.168.1.1       
22    20.790400    192.168.1.141    224.0.0.251    MDNS    289    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
23    20.791417    fe80::62ab:67ff:fec0:5ff3    ff02::fb    MDNS    309    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
24    26.896453    92.122.45.168    192.168.254.254    TLSv1.2    85    Encrypted Alert    443    50057
25    26.896453    92.122.45.168    192.168.254.254    TCP    85    [TCP Retransmission] 443 → 50057 [PSH, ACK] Seq=1 Ack=1 Win=245 Len=31    443    50057
26    26.896454    92.122.45.168    192.168.254.254    TCP    54    443 → 50057 [FIN, ACK] Seq=32 Ack=1 Win=245 Len=0    443    50057
It seems that the file "upgrade_info_7db780a713a4.txt" is not being requested by the VTO but the file "failed.txt" it is.

I´ve tried with firmwares "General_VTO2111D_Eng_P_16M_V3.120.0012000.0.R.20180731" and "General_VTO2111D_Eng_P_16M_V1.000.0000.0.R.20170414" but as no command is executed no firmware is transfered to the VTO.
I´ve also tried with different commands in the "upgrade_info_7db780a713a4.txt" file, but it is never transfered to the VTO.

Can anyone help me, please.

Thanks in advance
 

tykasan

n3wb
Joined
Nov 23, 2019
Messages
5
Reaction score
0
Location
Poland
Hello all

Let's see if anyone can help me with my bricked VTO2111D.
The thing is that it bricked while upgrading to "General_VTO2111D_Eng_P_16M_V3.120.0012000.0.R.20180731" firmware. Since then the VTO is continuously resetting. I followed the procedure posted here Dahua IPC EASY unbricking / recovery over TFTP with no luck and I´m not able to send any command because the device is continuously resetting.
I´ve executed the tftp server and this is the output:
Code:
accepting requests..
Open TFTP Server MultiThreaded Version 1.64 Windows Built 2001

starting TFTP...
alias / is mapped to root\
permitted clients: all
server port range: all
max blksize: 65464
default blksize: 512
default timeout: 60
file read allowed: Yes
file create allowed: No
file overwrite allowed: No
thread pool size: 1
Listening On: 192.168.254.254:69
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served
Client 192.168.1.108:3100 root\failed.txt, 1 Blocks Served

This is the output of the UART port:

Code:
Checking DDR......OK

UBL Version: 1.46t(DM365)16:10:30 Aug  4 2017
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)

DRAM:  128 MB
SF: Got idcode c2 20 18 c2 20
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
APP_OFFSET_NEW test
.......
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1798424 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

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

Checking DDR......OK

UBL Version: 1.46t(DM365)16:10:30 Aug  4 2017
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (May 23 2018 - 10:46:47)

DRAM:  128 MB
SF: Got idcode c2 20 18 c2 20
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
APP_OFFSET_NEW test
.......
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1798424 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................ done, booting the kernel.
Uncompressing Linux........................................................................................................................ done, bootiUncompressing Linux........................................................................................................................ done, booting the kernel.
The file upgrade_info_7db780a713a4.txt is created in the root folder with the following content

Code:
CRC:1393106523
MagicString:c016dcd6-cdeb-45df-9fd0-e821bf0e1e62
run dr
run dk
run du
run dw
run dd
run dc
tftp 0x82000000 pd-x.cramfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5
And with the wireshark this is what I get:

Code:
No.    Time    Source    Destination    Protocol    Length    Info    Src Port    Dst Port
1    0.000000    Zte_d4:f0:80    Broadcast    ARP    42    Who has 192.168.1.133? Tell 192.168.1.1      
2    4.608767    192.168.1.141    224.0.0.251    MDNS    289    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
3    4.609658    fe80::62ab:67ff:fec0:5ff3    ff02::fb    MDNS    309    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
4    5.848288    192.168.1.1    224.0.0.1    IGMPv2    46    Membership Query, general      
5    6.333145    192.168.254.254    239.255.255.250    IGMPv2    46    Membership Report group 239.255.255.250      
6    7.535331    192.168.1.108    192.168.254.254    TFTP    84    Read Request, File: failed.txt, Transfer type: octet, timeout=1, blksize=1468    1212    69
7    7.535879    192.168.254.254    192.168.1.108    TFTP    67    Option Acknowledgement, timeout=1, blksize=1468    50866    1212
8    7.542671    192.168.1.108    192.168.254.254    TFTP    46    Acknowledgement, Block: 0    1212    50866
9    7.542747    192.168.254.254    192.168.1.108    TFTP    247    Data Packet, Block: 1 (last)    50866    1212
10    7.548154    192.168.1.108    192.168.254.254    TFTP    46    Acknowledgement, Block: 1    1212    50866
11    7.578793    Zhejiang_0c:8b:48    Broadcast    ARP    60    Who has 192.168.1.1? Tell 192.168.1.108      
12    8.333107    192.168.254.254    224.0.0.252    IGMPv2    46    Membership Report group 224.0.0.252      
13    12.332994    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254      
14    12.801982    fe80::1    ff02::1:ffdc:cefa    ICMPv6    86    Neighbor Solicitation for fe80::66cc:2eff:fedc:cefa from 50:78:b3:d4:f0:80      
15    13.332993    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254      
16    13.333177    192.168.254.254    224.0.0.251    IGMPv2    46    Membership Report group 224.0.0.251      
17    14.332993    Tp-LinkT_0a:0d:07    Zhejiang_0c:8b:48    ARP    42    Who has 192.168.1.108? Tell 192.168.254.254      
18    15.362362    fe80::1    ff02::1    ICMPv6    102    Router Advertisement from 50:78:b3:d4:f0:80      
19    15.567132    192.168.1.131    224.0.0.251    MDNS    131    Standard query response 0x0000 A, cache flush 192.168.1.131 AAAA, cache flush fe80::62ab:67ff:fee4:cb83 NSEC, cache flush Android.local    5353    5353
20    15.567133    fe80::62ab:67ff:fee4:cb83    ff02::fb    MDNS    151    Standard query response 0x0000 A, cache flush 192.168.1.131 AAAA, cache flush fe80::62ab:67ff:fee4:cb83 NSEC, cache flush Android.local    5353    5353
21    16.284170    Zte_d4:f0:80    Broadcast    ARP    42    Who has 192.168.1.131? Tell 192.168.1.1      
22    20.790400    192.168.1.141    224.0.0.251    MDNS    289    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
23    20.791417    fe80::62ab:67ff:fec0:5ff3    ff02::fb    MDNS    309    Standard query response 0x0000 PTR, cache flush Android.local PTR, cache flush Android.local A, cache flush 192.168.1.141 AAAA, cache flush fe80::62ab:67ff:fec0:5ff3 NSEC, cache flush 141.1.168.192.in-addr.arpa NSEC, cache flush 3.F.F.5.0.C.E.F.F.F.7.6.B.A.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa NSEC, cache flush Android.local    5353    5353
24    26.896453    92.122.45.168    192.168.254.254    TLSv1.2    85    Encrypted Alert    443    50057
25    26.896453    92.122.45.168    192.168.254.254    TCP    85    [TCP Retransmission] 443 → 50057 [PSH, ACK] Seq=1 Ack=1 Win=245 Len=31    443    50057
26    26.896454    92.122.45.168    192.168.254.254    TCP    54    443 → 50057 [FIN, ACK] Seq=32 Ack=1 Win=245 Len=0    443    50057
It seems that the file "upgrade_info_7db780a713a4.txt" is not being requested by the VTO but the file "failed.txt" it is.

I´ve tried with firmwares "General_VTO2111D_Eng_P_16M_V3.120.0012000.0.R.20180731" and "General_VTO2111D_Eng_P_16M_V1.000.0000.0.R.20170414" but as no command is executed no firmware is transfered to the VTO.
I´ve also tried with different commands in the "upgrade_info_7db780a713a4.txt" file, but it is never transfered to the VTO.

Can anyone help me, please.

Thanks in advance
Hi there.
I had exact same issue.
I was missing pressing ********* (asterisk) on the keyboard while booting.
This will stop bootloop.
Then you will be able to do all other magic. I was able to recover mine vto with newest firmware.
 

Ruper

n3wb
Joined
Dec 31, 2019
Messages
2
Reaction score
2
Location
Madrid
Hi there.
I had exact same issue.
I was missing pressing ********* (asterisk) on the keyboard while booting.
This will stop bootloop.
Then you will be able to do all other magic. I was able to recover mine vto with newest firmware.
Thank you for your indications. I did what you posted and now I have my VTO up un running.

Thank you very much and a happy new year.
 
Joined
May 25, 2020
Messages
2
Reaction score
0
Location
mexico
Thank you for your indications. I did what you posted and now I have my VTO up un running.

Thank you very much and a happy new year.

Hi.
I have the same problem with my VTO 2111d-wp, I tried to update it and after completing 100% and asking for the restart it stays in constant bootloop,
but I am not an expert in this and I would like to indicate if you were so kind step by step what I must do to recover it.

I will thank you very much since I have not found help in this regard.

An apology for my bad English, I am from Mexico and it is not my native language.
 
Joined
May 25, 2020
Messages
2
Reaction score
0
Location
mexico
Happy to help.
M

Hi @tykasan .
I have the same problem with my VTO 2111d-wp, I tried to update it and after completing 100% and asking for the restart it stays in constant bootloop,
but I am not an expert in this and I would like to indicate if you were so kind step by step what I must do to recover it.

I will thank you very much since I have not found help in this regard.

An apology for my bad English, I am from Mexico and it is not my native language.
 
Top