UART connection to recover Hik cameras

Finally got around to trying to fix my bricked 2CD2132 and its been a royal PITA.

Firstly the Prolific USB-Serial adapter turns out to be using a counterfeit chip and prolific in there wisdom have blocked it in their latest drivers without letting you know why. In my case as I was using an old Vista machine, I didn't get any errors at all let alone the cryptic code 10. Eventually I figured out the issue and used the following drivers to get it working:

Prolific USB-to-Serial Fix (Official Solution to 'Code 10 error') | Car OBD Diagnostics, ECU Chip Tuning & Auto Repair Support

I don't care about the provenance of these as i'm using a "dirty" machine, I wouldn't install on my main machines.

Anyway, couple of hours wasted and getting boot up from camera. But it doesnt appear to be taking any keyboard input. Ctrl-U does nothing, and once its booted to the prompt, I can bang the keys as I want but nothing appears.

Anyone had the same issue?
 
Heres output from camera:



U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

*** Warning - bad CRC, using default environment
crc=0x8f1a8b9b,env.crc=0xffffffff
ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
|BIND err|
Unknown command:null
nand booting ...
load kernel...
load ramdisk...
init started: BusyBox v1.19.3 (2012-12-06 11:06:28 CST)
starting pid 374, tty '': '/etc/init.d/rcS'
config & start mdev ...
done.
starting pid 389, tty '': '/sbin/inetd -f -e /etc/inetd.conf'
starting pid 390, tty '': '-/bin/sh'


BusyBox v1.19.3 (2012-12-06 11:06:28 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

UBI device number 1, total 192 LEBs (24772608 bytes, 23.6 MiB), available 0 LEBs
(0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi1_0.
waiting for /dev/ubi1_0.
Check dir /dav ok! (0)
UBI device number 3, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0
bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi3_0.
Check dir /davinci ok! (0)
UBI device number 4, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0
bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi4_0.
Check dir /config ok! (0)
#

U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

*** Warning - bad CRC, using default environment
crc=0x8f1a8b9b,env.crc=0xffffffff
ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
|BIND err|
Unknown command:null
nand booting ...
load kernel...
load ramdisk...
init started: BusyBox v1.19.3 (2012-12-06 11:06:28 CST)
starting pid 374, tty '': '/etc/init.d/rcS'
config & start mdev ...
done.
starting pid 389, tty '': '/sbin/inetd -f -e /etc/inetd.conf'
starting pid 390, tty '': '-/bin/sh'


BusyBox v1.19.3 (2012-12-06 11:06:28 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

UBI device number 1, total 192 LEBs (24772608 bytes, 23.6 MiB), available 0 LEBs
(0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi1_0.


U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

*** Warning - bad CRC, using default environment
crc=0x8f1a8b9b,env.crc=0xffffffff
ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
|BIND err|
Unknown command:null
nand booting ...
load kernel...
load ramdisk...
init started: BusyBox v1.19.3 (2012-12-06 11:06:28 CST)


U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

*** Warning - bad CRC, using default environment
crc=0x8f1a8b9b,env.crc=0xffffffff
ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
|BIND err|
Unknown command:null
nand booting ...
load kernel...
load ramdisk...
init started: BusyBox v1.19.3 (2012-12-06 11:06:28 CST)
starting pid 374, tty '': '/etc/init.d/rcS'
config & start mdev ...
done.
starting pid 389, tty '': '/sbin/inetd -f -e /etc/inetd.conf'
starting pid 390, tty '': '-/bin/sh'


BusyBox v1.19.3 (2012-12-06 11:06:28 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

UBI device number 1, total 192 LEBs (24772608 bytes, 23.6 MiB), available 0 LEBs
(0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi1_0.
waiting for /dev/ubi1_0.
Check dir /dav ok! (0)
UBI device number 3, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0
bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi3_0.
Check dir /davinci ok! (0)
UBI device number 4, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0
bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi4_0.
Check dir /config ok! (0)
#
 
gb7777 said:
Finally got around to trying to fix my bricked 2CD2132 and its been a royal PITA.
Click to expand...
Are you able to use the brickfixV2 method? This doesn't need access to the serial console, and there is some scripting to help out with the export / import of mtdblock6 and other stuff.
All that's needed is the ability to run the Hikvision tftp updater, a regular tftp server, PuTTY and a hex editor.

-
Unbrick and fully upgrade your R0 / DS-2CD2x32 IP cameras -
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
 
alastairstevenson said:
Are you able to use the brickfixV2 method? This doesn't need access to the serial console, and there is some scripting to help out with the export / import of mtdblock6 and other stuff.
All that's needed is the ability to run the Hikvision tftp updater, a regular tftp server, PuTTY and a hex editor.

-
Unbrick and fully upgrade your R0 / DS-2CD2x32 IP cameras -
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
Click to expand...

I thought that was more for people who had issues editing mtdbkocks/etc manually. I’ve managed to do all the other cameras using tftp updater and hex edit.

This one is completely bricked (not connecting to tftp server) which is why I’m using UART to try and point it to the tftp server.
 
gb7777 said:
Finally got around to trying to fix my bricked 2CD2132 and its been a royal PITA.

Firstly the Prolific USB-Serial adapter turns out to be using a counterfeit chip and prolific in there wisdom have blocked it in their latest drivers without letting you know why. In my case as I was using an old Vista machine, I didn't get any errors at all let alone the cryptic code 10. Eventually I figured out the issue and used the following drivers to get it working:

Prolific USB-to-Serial Fix (Official Solution to 'Code 10 error') | Car OBD Diagnostics, ECU Chip Tuning & Auto Repair Support

I don't care about the provenance of these as i'm using a "dirty" machine, I wouldn't install on my main machines.

Anyway, couple of hours wasted and getting boot up from camera. But it doesnt appear to be taking any keyboard input. Ctrl-U does nothing, and once its booted to the prompt, I can bang the keys as I want but nothing appears.

Anyone had the same issue?
Click to expand...

I'm having the same problem, I press CTRL-U and nothing happens. Has anyone managed to solve this problem?
 
aryjrbnu said:
I'm having the same problem, I press CTRL-U and nothing happens. Has anyone managed to solve this problem?
Click to expand...


I discovered a way to solve the case where CTRL + U does not work, I used another PC and it worked normally. I made the exchange of firware.
 
aryjrbnu said:
I discovered a way to solve the case where CTRL + U does not work, I used another PC and it worked normally. I made the exchange of firware.
Click to expand...

Ok I’ll give that a try.

So on first PC no keyboard inputs were working at all? IE even after it booted nothing u typed showed up.

Have to dig out another PC and keep my fingers crossed.
 
gb7777 said:
Ok I’ll give that a try.

So on first PC no keyboard inputs were working at all? IE even after it booted nothing u typed showed up.

Have to dig out another PC and keep my fingers crossed.
Click to expand...

Hello, in the first PC, at times I could type some characters and consequently some commands, but in the first option to start the upgrade process (CTRL + U) did not obey commands. With the other PC it worked perfectly on the first try.
 
aryjrbnu said:
Hello, in the first PC, at times I could type some characters and consequently some commands, but in the first option to start the upgrade process (CTRL + U) did not obey commands. With the other PC it worked perfectly on the first try.
Click to expand...

Thanks, in my case I couldn't get any response from terminal. Banged the keyboard and not a single character appeared.
 
Hi,
I have a DS-2CD2732F-IS. It is a CH Model. I upgraded to V5.4.0 and ended up getting the language mismatch error. I read through the posts and headed to do the brickfixV2 method . However i observed that the tftp download would not work. I tried it with a switch in between as well but no luck. Until this steps the camera was seen in SADP. Now the camera Ethernet interface is not coming up at all. The green led for network activity is blinking fast but no sign of an ip address assignment. I tried resetting the device but the status does not change. What should i do now? Any suggestions are most welcome.
 
sumanalex said:
However i observed that the tftp download would not work.
Click to expand...
What messages showed on the tftp updater window?

The Hikvision tftp updater can be a bit fussy about the environment such that the probes from the camera get missed.
What works best is :
Both camera and PC wired to a switch or router.
Camera powered by external power as opposed to PoE.
PC may need the Windows firewall temporarily disabled.
And you may have to try several times before it connects.

sumanalex said:
Until this steps the camera was seen in SADP.
Click to expand...
What specific change resulted in the camera no longer showing in SADP?
Was it the 5.4.0 firmware update?
You've said the tftp download would not work, so presumably not that. Was this referring to the Hikvision tftp updater or a tftp server?
 
You must log in or register to reply here.
Top Bottom