Bricked 2032. Not on network

the tftp recovery is done in the boot process, there wont be anything to telnet or sadp into as nothing's running at that point.
 
Open a Windows command prompt and type "Ping 192.0.0.64 -t" (without the quotation marks) which will run a continuous ping to the specified IP address
 
Q2U said:
Open a Windows command prompt and type "Ping 192.0.0.64 -t" (without the quotation marks) which will run a continuous ping to the specified IP address
Click to expand...

What does the continuous ping accomplish in this instance?
 
you'll see if its entering tftp recovery mode
 
oguruma said:
What does the continuous ping accomplish in this instance?
Click to expand...
Why do people come on here and ask for help and then don't do what is suggested?

What does this question accomplish in this instance?

No wonder you bricked your camera.

- - - Updated - - -

oguruma said:
I'll have to try it when I get home, but if I get ping responses, what does that mean? I still don't understand how I'm supposed to tftp it....
Click to expand...
You need to read the downgrader thread, the entire thread. It's clear you haven't.
 
I still don't understand how I'm supposed to tftp it....
Click to expand...
Sounds like you have not read the tftp updater instructions ...
During the boot process, the bootloader probes the IP address 192.0.0.128 with a specific UDP packet for the Hikvision-specific (note - not standard) tftp updater tool and requests a firmware download from it.
The tftp updater and instructions can be found within the download at the link here: https://www.ipcamtalk.com/showthrea...are-Downgrader-5-3-0-Chinese-to-5-2-5-English

I'll have to try it when I get home, but if I get ping responses, what does that mean?
Click to expand...
For 2 or 3 seconds after power-on, then nothing - shows it's likely to be in the classic boot loop. It responds at 192.0.0.64 while it's set up to probe for the updater tool.
 
I tried the tftp server. It got stock on trasmit file completed for over 30 mins. I later tried to reset (power + button for 30 seconds) a few more times. After a 4th try, the camera now shows up in SADP as 192.168.1.64. I can ping it, however I cannot access the GUI. It shows software version 4.0.8, although that is not what the sticker indicates. Also, the IR lights are on, in a very brightly lit room.
 
Like I said in another post, the solution is to use the 4 points connector with a small interface (like jtag), to unbrick, place new firmware and so on.
All range of Hik products have this connector for service issues. And this is from where the FW, modified FW were applied from grey market by "non official" providers.
The more dificult, get this kind of small device, and use it.
 
Like I said in another post, the solution is to use the 4 points connector with a small interface (like jtag), to unbrick, place new firmware and so on.
Click to expand...
You are correct that the serial console can be used to recover from bad things like firmware corruption etc - but this hasn't reached that stage, it's responding fine to the tftp updater.
The camera has entered the 'recovery mode' that Hikvision build in, to handle situations such as incorrect firmware being flashed. A minimal system, no web services, based on an old version 4.0.8
The solution is to apply compatible firmware.

It's very likely that it will be fine if you use the tftp update with the '5.3.0 to 5.2.5 downgrader' here, the 1-line version : https://www.ipcamtalk.com/showthrea...are-Downgrader-5-3-0-Chinese-to-5-2-5-English
You may well have to change the firmware header language with Hiktools here : https://www.ipcamtalk.com/showthrea...anguage-extract-files-and-create-own-firmware
 
You must log in or register to reply here.
Top Bottom