Hikvision - Clearing Passwords and/or Loading Firmware via TTL Serial

it is not geting echo;/ I can type something, but after enter it is going back on the begining of the line. leds are blinking when I am typing something ( tx led and rx led). I have converter like this: https://stak.com/image/cache/data/products/237/237977/237977-800x800.png Works fine with ESP modules.

I checked 2 convertors, one was brand new. Before connected I checked + and - on socket -about 3,3V, the same was set on converer.
 
Last edited:
m-blue said:
I can type something, but after enter it is going back on the begining of the line.
Click to expand...
It sounds like it may have a 'hidden' command to enable or activate normal command mode.
If it's echoing what you type - the connections and the serial TTL convertor are OK.
The bootloader interface is just ignoring the commands, maybe until it gets that 'activation' command.

As a long shot try 'su' as a command.
 
m-blue said:
Ok, but I have this after connected rx and tx together at converter, not after connected to dvr.
Click to expand...
Sorry, I thought what you quoted was happening was after it was connected to the DVR.
So there is still the possibility that the TX on the convertor is not connected to the RX of the DVR.
Be careful not to connect the TX to the VCC (power) of the DVR connector.
 
I made new cable... from 2 pcs of 2-pin IR connector:) Now it is better - I can stop booting, put some text but I don't have command to upgrade, after put U there is no info to confirm. At second PC I can't stop booting via CTR+U :) I can write commands but after dvr wakes up. I see the light but still small...

I think me and Greg stuck in the same place - cannot run update procedure
 
Last edited:
Any updates on getting the keyboard to work? I cannot stop boot sequence with CTRL+u as well...the <ENTER> key also returns to the line vice a new line..having problems with keyboard. I am using putty with windows 10..
 
  • Like
Reactions: ahmad966
liem said:
Any updates on getting the keyboard to work? I cannot stop boot sequence with CTRL+u as well...the <ENTER> key also returns to the line vice a new line..having problems with keyboard. I am using putty with windows 10..
Click to expand...
On the assumption that whatever you are connected to is not bricked and it's a password reset you are looking for ...
If you allow it to fully boot, can you issue any commands at the psh/bash prompt?
 
  • Like
Reactions: ahmad966
I found another simple solution that uses bootargs, which switches u-boot mode. Will Hikvision close this opportunity in new firmwares if published? They already moved the recovery mode beyond uboot.
 
novex said:
I found another simple solution that uses bootargs, which switches u-boot mode. Will Hikvision close this opportunity in new firmwares if published?
Click to expand...
Cool. Keep it in secret!

novex said:
They already moved the recovery mode beyond uboot.
Click to expand...
Yes, because firmware doesn't contain u-boot and it's hard to control....
Now they use sign method, but it not so good too for them ;)
 
Last edited:
There have between several 'useful' bootargs parameters that Hikvision have removed or disabled over time, presumably as a consequence of public exposure.
 
iTuneDVR said:
Cool. Keep it in secret!


Yes, because firmware doesn't contain u-boot and it's hard to control....
Now they use sign method, but it not so good too for them ;)
Click to expand...


Hello,
I have two DVRs with the same problem, after the firmware update the user appears blank and I can not access. Via serial connection also the CTRL + U option is not available to upgrade. If someone has another way to access via serial, thank you if you make the method available.

My e-mail is [email protected]
 
Last edited:
novex said:
Gregs53, m-blue & others - try workaround (dirty hack :) ): setenv bootcmd ';update'
Click to expand...

Hello,
I have two DVRs with the same problem, after the firmware update the user appears blank and I can not access. Via serial connection also the CTRL + U option is not available to upgrade. If someone has another way to access via serial, thank you if you make the method available. When initializing the DVR with the PUTTY connected via serial only the screen with the text "Uncompressing Linux ... done, booting the kernel" appears, but it does not accept any command.
 
Last edited:
aryjrbnu said:
Hello,
I have two DVRs with the same problem, after the firmware update the user appears blank and I can not access. Via serial connection also the CTRL + U option is not available to upgrade. If someone has another way to access via serial, thank you if you make the method available. When initializing the DVR with the PUTTY connected via serial only the screen with the text "Uncompressing Linux ... done, booting the kernel" appears, but it does not accept any command.
Click to expand...
check your wires...if not connect correctly it will not accept and command.
 
greg63 said:
The dvr (DS-7216HUHI-K2) was wrongly updated from 3.5.35 version to 3.5.50 version.
Since then, it is impossible to establish a connexion.
The admin login doesn’t exist anymore and the storage is not visible anymore from the SADP.
I’m trying to come back to the original firmware.


MOPED, thanks for your answer. I also tried your solution but it didn't work.
Click to expand...
HI, i have same problem after I use control-u, right at the beginning it stops the bootloader but then the commands don't work anymore !
are you solwe this problem ?
 
Dear sir
I connected the dvr on my pc directly by Ttl cable I follow your method,but when I turn on my dvr there are nothing show any boot file,anyone can solve this issue???
please help me
 
gpower07 said:
check your wires...if not connect correctly it will not accept and command.
Click to expand...

hello, certainly no problem with the wires as I use the same adapter cable on other DVRs and cameras and it works perfectly. The problem is with the latest firmware version that disables the commands in u-boot. I found other forums with the same case, some users mention that they could access by means of attacks, but do not share the method and do not know how to solve.
 
I've not seen that DVR - maybe I should take a look at the firmware to see if it includes the bootloader - didn't someone mention preceding the usual familiar bootloader commands with a :
Perhaps just a bit of obscurity has been put in place.
 
You must log in or register to reply here.
Top Bottom