Bricked 2132F-IS with complications

Hi all,

Great info on this forum. Thanks everyone for sharing.

I have another 5.3.0 update issue on a 3232F-IS (sticker says 5.3.0, but had 5.2.5 installed), though with a slight complication. The TFTP Auto-Updater is not functional because the camera is now 192.168.1.64 (Wireshark is picking up packets from this IP with direct ethernet connection). I suppose it is looking for 192.0.0.64 which is not the IP of the camera, so the auto updater will not function.

- Upon trying Putty to Telnet in to 192.168.1.64:23 I get connection refused.
- Upon trying to FTP in I get connection refused. Not sure I had the right port though?
- Upon using Tftpd32 port 69 to connect in, I get no response. Just sits on block #0 for a while, then timeout. Again- not really sure of the right port to use for this one.
- Of course, no web access or access via Surveillance Station.

Is there a way forward here? Perhaps persist with Telnet / FTP and try to get a connection that way?

Thanks


EDIT: SUCCESS! Use the 5.3.0 downgrader on this forum to fix this issue. Even though it is not a 5.3.0 camera, the downgrader fixes it. It is the only TFTP software and 5.2.5 combination that achieves the "updated completed" status for this camera.

Getting somewhere. The use of a switch seems to be pretty important. I have connected it by means of a spare switch, and have it working with TFTP Auto Updater now, and it is finding it on 192.0.0.64 shorty after it boots. I am trying to re-flash the 5.2.5 firmware found on this forum. Fingers crossed.

No good. It reaches "Completed file[C:\........] transmit" and goes no further. I doesn't reach the "Device[192.0.0.64]system update completed!" status. Left for 20 mins and still nothing. Uplugged the 12V supply and let it run through again, still no "update completed" message.

Tried with 5.2.3 a couple of times, and 5.3.0 a couple of times. I don't think this is firmware version related. There is something strange going on with these badged 5.3.0 cameras that ship with 5.2.5 firmware. Must have had a last minute issue with them, and reverted them all back to some 5.2.5 via some method other than this.

It is getting to the point now where it is setting itself an IP of 192.168.1.64, but with no web interface access via this IP. It did this with various firmware flashes, but never actually got the "updated completed" message or web access.

Try the 5.2.5 firmware located in this forum.

http://www.ipcamtalk.com/showthread.php/4036-Custom-Firmware-Downgrader-5-3-0-Chinese-to-5-2-5-English

Cheers

The symptoms suggest the camera has gone into 'Min system mode' due to an incompatible firmware upgrade. The problem is seen, the new firmware is still written but the 'completed' status not saved, resulting in the negative check on the reboot. @davo22 suggestion above is sound, it's a firmware version that works OK for recovery.
The '5.2.5' that came with the camera is likely put on by the seller to make it appear as English, for better NVR compatibility.

Example of what may have happened:

U-Boot 1.3.4-100728 (Nov 11 2014 - 13:58:34)
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 (2015-03-20 17:37:48 CST)
starting pid 378, tty '': '/etc/init.d/rcS'
Starting udev: [ OK ]
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.
pri_iUpgSuccCnt:0x0, sec_iUpgSuccCnt:0x0
pri_part and sec_part data error.
cat: read error: Invalid argument
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot

U-Boot 1.3.4-100728 (Nov 11 2014 - 13:58:34)
ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
begin to enter mini system

Click to expand...