Unable to change DS-2CD2232-i5 IP address or password

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Hi all

After getting some help about our NVR off this forum, I tried to tackle a camera that had a little water damage in the POE connector.

We replaced the connector with a wall plate adapter (female) and plugged it into the PC. Reloaded the firmware for good measure as originally we never had any passwords for our camera system when we moved in.

I got SADP to recognise the camera at home on my PC, showed a IP of 192.168.1.64 255.255.255.0 and status was active. I tried to conenct via web browsers, however the connection refused to connect in the browser. Camera was pingable through cmd.

I tried to change the IP through SADP tool last night, however it wouldnt accept any default password simply returning a error about 'Time out' when clicked 'Modify' to allow it to make changes.

I tried a password reset through the .exe program and the online calculator on this site, however it just claims password recovery failed.

Software version is V4.0.8Build 1504.

I have just come to plug the camera into our NVR this morning and still doesnt recognise it. The camera setup page attempts to connect and occasionally says detecting, however it wont connect to the camera. Presumably because the IP address is incorrect for the POE network on the NVR.
NVR also states the reason for not connecting is because the Network is Unreachable.

Has anyone got any suggestions as to how I can gain access to the camera to reset it enough to be able to add it to our NVR.

Chris
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Software version is V4.0.8Build 1504.
That's the clue that the camera is operating in the 'min-system recovery' mode.
It's a basic system with no web services that's used for recovery actions when it's unable to operate properly.
This could be due to incorrect firmware being loaded, or EN/ML firmware being loaded on a Chinese camera for example.

Reloaded the firmware for good measure as originally we never had any passwords for our camera system when we moved in.
It seems likely this is the cause.
What exact firmware did you load?
Is this a Chinese camera? If so, loading EN/ML firmware will 'brick' it, giving the symptoms you've described.
If so, this method can be used to unbrick and convert to EN :
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Was the latest version off hikvision for the camera.

Not sure if it’s a Chinese or not, is there a easy way to tell?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Not sure if it’s a Chinese or not, is there a easy way to tell?
The original serial number would have 'CCCH' in it.
And the place where you bought it would be another clue.

Was the latest version off hikvision for the camera.
The could cover a large number of model variants off quite a lot of Hikvision sites.
For the record, the camera you've quoted is an R0 series camera.
The stock firmware for those can be found here : DOWNLOAD EU PORTAL
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Will have to check later on for the full serial as our computer in the garage doesn’t pick it up on sadp despite being plugged into the NVR and access is available to it through the web gui. (Neither does it see our other 4 cameras either)

Couple pics of the sadp software and the sticker on the back.
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Couple pics of the sadp software and the sticker on the back.
OK, so the CCRR in the serial number, and the 5.3.0 firmware version on the label suggests this is not a Chinese camera, so should be upgradable to any stock Hikvision firmware.

My suggestion :
Use the Hikvision tftp updater method to apply either the stock R0 5.3.0 firmware, or the @whoslooking '5.3.0 to 5.2.5 downgrader' firmware.
If the firmware you loaded (link?) was 5.4.0 or higher, there will be a downgrade block now that will inhibit any firmware updates below that version.
TFTPServ
R0 series DS-2CD2x32x-Ixx IP camera firmware
Custom Firmware Downgrader 5.3.0 Chinese to 5.2.5 English

But either way - the brickfixV2 convert / update method should get the camera back to a working state, and confirm if under the covers it's actually a Chinese camera that was running 'hacked to English' firmware that made it look like an EN model.
Unbrick and fully upgrade your R0 / DS-2CD2x32 IP cameras -
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
I'll have a look at that thread tonight and try re-loading the firmware. Did try 3 different ones, all different sizes but one of them was definitely off the hikvision 'discontinued product' page on their website.

From the firmware link you linked to above under TFTP server, what version would you recommend putting on? We arent too fussy about having a lower version one as there shouldnt be any complications to using the newest stuff in regards to passwords etc as we effectively started fresh when we took the garage over.

If any help the NVR is a DS-7616NI-E2/16p with the software version V3.4.92 build 170518
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
In terms of what to try with the tftp updater, it depends on what versions you have already tried.
For versions of 5.4.0 or later, even if not successful, the resultant downgrade block will inhibit earlier versions.
The brickfixV2 method will get round any downgrade block.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Do you think it’ll be best to just downgrade it and do it that way and stick the firmware on that article recommends?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Do you think it’ll be best to just downgrade it and do it that way and stick the firmware on that article recommends?
In terms of what to try with the tftp updater, it depends on what versions you have already tried.
For versions of 5.4.0 or later, even if not successful, the resultant downgrade block will inhibit earlier versions.
As indicated - it does depend on what (unspecified) versions of firmware you have already tried.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Trying to do the unbricker method, however when doing the initial load using tftp, I don’t get the system update completed. It just hangs and hangs. The last line of text is shown in the picture.

Do I need that last line to pop up before proceeding? This also never come up the first time I flashed firmware onto it
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
It just hangs and hangs.
You have not said which version of the brickfixV2 firmware you are using.
There are 2 versions - EN header and CN header, to cater for the unbricking of both EN and Chinese cameras.
I'm guessing that you need to use the other version.

Do I need that last line to pop up before proceeding? This also never come up the first time I flashed firmware onto it
Yes, you do.
Without 'System upgrade completed' it is an indication that incompatible firmware has been applied.

As indicated - it does depend on what (unspecified) versions of firmware you have already tried.
You will still need to use the correct version of firmware for Stage 3 of the process.
You have still not specified the versions you have used already, which appear to have triggered this problem.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
I initially tried with the EN version.

Ill try now with the chinese version.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Worked through the process, changed all the bytes and checksums, saved the mod file and re-ran the script. Putty claimed the firmware update was sucessful, however it doesnt pick it up in SADP or via the 192.168.1.64 IP address. This was with the V5.4.5_build170123 firmware.
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Little update, tried the downgrader again, however with the 5.2.3 firmware, still the same. These are the files I got from the log files.

Tried to update to the 5.4.5 firmware through the TFTP server through the normal method. This said it was successful however the camera still does not show in SADP tool. Ill also upload a photo of the mod file done in HxD editor
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Worked through the process, changed all the bytes and checksums, saved the mod file and re-ran the script. Putty claimed the firmware update was sucessful, however it doesnt pick it up in SADP or via the 192.168.1.64 IP address. This was with the V5.4.5_build170123 firmware.
Well done for managing the brickfixV2 process.
Your fixup.log file looks fine, as does the firmware file used.

The question now is - why isn't the camera starting up normally?
Can you zip up and attach the mtd6ro_orig and mtd6ro_mod files and I'll validate the contents?
 

chrisc90

Young grasshopper
Joined
Oct 28, 2018
Messages
48
Reaction score
1
Location
UK
Not too sure, there was some water damage in the connector to begin with so maybe could have fried something inside it.

I tried with the other firmware versions late last night and still no luck. However, looking at the network switch, the camera shows activity for about 2-3minutes, then the activity light drops out, comes back on for a second or a few and goes off again. Back on and cycle repeats. Not sure if that’s something related or what.

However, it picked up prior to the brickfix in sadp tool.

Will upload the 2 files when I get home later. The initial file pulled off the camera had the language as 02 and the device version as FF 98. Obviously the checksum to match that as expected.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,945
Reaction score
6,784
Location
Scotland
Ok.
Sounds like a reboot loop is what's happening.

The 02 confirms it's a Chinese camera, and the FF98 would cause it to 'brick' on a firmware update.

If there is no clue in the mtd6 data, the next step is a bit more fiddly - hooking up to the serial console.

I don't think the cable is likely to be a cause - but if you have one, it may be worth powering with a 12v adapter.
 
Top