Hikvision ERI-K216-P16 – Bound to Previous User, TFTP Update Fails

departed

n3wb
Aug 27, 2025
3
0
Georgia
Hi everyone,


I recently bought a Hikvision ERI-K216-P16 NVR second-hand (eBay purchase). Unfortunately, it turns out the device is still bound to the previous owner’s Hik-Connect account. The seller cannot help me unbind it.


I tried using the TFTP method to re-flash the firmware, hoping it would reset the binding. However, the process fails with the following error:
econet vision av2000 failure

At this point I’m stuck:


  • Is there any technical way to re-flash or unbind this model?
  • Or is the binding permanent unless Hikvision support removes it (which they likely won’t, since I’m not the original owner)?
  • Has anyone managed to bypass this error when using TFTP with this model?

Any advice or shared experiences would be greatly appreciated.


Thanks!
 
However, the process fails with the following error:
econet vision av2000 failure
That's not a process failure - it's actually a comment by the tftp updater tool that it had received a probe for ArecontVision devices.
This is something the NVR does on startup, and it uses a similar UDP probe to what the NVR uses looking for the tftp updater on bootup.

There are a couple of variables that could affect success -
The PC and NVR should each be connected to their own switch or router ports - direct connection is less likely to work.
The IP address the NVR is probing is set by a bootloader environment variable, and can vary.
Common values are 192.0.0.128 and 192.168.1.128
 
Hi everyone,


I recently bought a Hikvision ERI-K216-P16 NVR second-hand (eBay purchase). Unfortunately, it turns out the device is still bound to the previous owner’s Hik-Connect account. The seller cannot help me unbind it.


I tried using the TFTP method to re-flash the firmware, hoping it would reset the binding. However, the process fails with the following error:
econet vision av2000 failure

At this point I’m stuck:


  • Is there any technical way to re-flash or unbind this model?
  • Or is the binding permanent unless Hikvision support removes it (which they likely won’t, since I’m not the original owner)?
  • Has anyone managed to bypass this error when using TFTP with this model?

Any advice or shared experiences would be greatly appreciated.


Thanks!
Even if I manage to update firmware will that unbind from previous user?
 
E
That's not a process failure - it's actually a comment by the tftp updater tool that it had received a probe for ArecontVision devices.
This is something the NVR does on startup, and it uses a similar UDP probe to what the NVR uses looking for the tftp updater on bootup.

There are a couple of variables that could affect success -
The PC and NVR should each be connected to their own switch or router ports - direct connection is less likely to work.
The IP address the NVR is probing is set by a bootloader environment variable, and can vary.
Common values are 192.0.0.128 and 192.168.1.128
even if I manage to update firmware will it unbind from previous user?