Where to get these FW, Google found only these Index of /download/Files/IPC/Firmware/IPC720P (2 different FW)
nayr
IPCT Contributor
bcd
n3wb
- Aug 5, 2016
- 9
- 2
Yes, my cameras are without IR-filter. day colors have some specific distortions, but it is not pink. see attachment. I think camera turns off IR-correction software but does not turn to b/w mode at twilight. Anyway a rollout to the old FW will fix it.
I used to have these cameras for year and a half.
some different name formats were on this link: 搜狐企业网盘 - 文件链接
General_HZXM_IPC_HI3518E_50H10L_S38_RT3070_V4.02.R12.20150317_ALL.bin
General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20150518_ALL.bin
General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20150910_ALL.bin
General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.Nat.OnvifS.20160304_ALL.bin
General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.Nat.OnvifS.20160615_ALL.bin
if you are not sure why you need it don't do it
the filter must be, shut photodiode and listen to after a short time, the sound of a closing flap
chorizo
n3wb
- Dec 11, 2016
- 15
- 5
You're right about the accessibility issue regarding the gif (for example it can't be read by people using a screen reader): I didn't copy & paste the whole thing because only a few commands are really necessary (the others are additional checks).
I think that providing an exact recording of what I've done was something valuable because it allows people to also see the same output I've seen during that session.
I wanted to provide textual instructions too but, that day, didn't had enough time: anyway thanks to @JoeShmo who filled the gap.
Last edited:
chorizo
n3wb
- Dec 11, 2016
- 15
- 5
Here's a memo I've made after managing to establish a serial connection to the camera (hopefully the PIN layout is right):
There are other ways to change the password but, to avoid possible issues, I think the safest thing you can do is firewalling telnet's port 23 of that device (TCP, input & output).
There are other ways to change the password but, to avoid possible issues, I think the safest thing you can do is firewalling telnet's port 23 of that device (TCP, input & output).
Two tips for low light settings in Camera param.
The camera at the front of my door with white wide angle LED at 0.4W close to the camera.
Default Camera param.: Slow shutter low, AGC limit 50
Camera param.: Slow shutter high, AGC limit 15
With AGC limit you set optimal white level at artificial light.
These 2 parammeter have no influence at day time.
To get all bits from image senzor you must In Color window set Brightnes to 70 and Contrast to 42.
Sharpnes is for my taste best at 8 or 9, 7 and lower have no influence, 10 and more produce distorted edges.
The camera at the front of my door with white wide angle LED at 0.4W close to the camera.
Default Camera param.: Slow shutter low, AGC limit 50
Camera param.: Slow shutter high, AGC limit 15
With AGC limit you set optimal white level at artificial light.
These 2 parammeter have no influence at day time.
To get all bits from image senzor you must In Color window set Brightnes to 70 and Contrast to 42.
Sharpnes is for my taste best at 8 or 9, 7 and lower have no influence, 10 and more produce distorted edges.
Last edited:
So yesterday I ran out of options for a public SHA-1 SMTP server for my cameras. I had hosted a mail server for it but they no longer allow SHA-1. So has anyone figured out a better option to receive email alerts? I have not seen anything saying that a new version of firmware is available even a year later. I am still running V4.02.R12.00006510.10010.140700
I sure would like to get my email alerts working again.
I sure would like to get my email alerts working again.
"Stef said: ↑
It seems to me that you have figured out what is wrong.
So what is required is a firmware update or we are stuck with SMTP servers which use SSL SHA-1 or no encryption."
Agreed. But what did everyone else do? Just give up on email alerts? Surely there are other options. I am really hoping those who found solutions will chime in. For instance, does anyone know of other existing SHA-1 SMTP servers?
It seems to me that you have figured out what is wrong.
So what is required is a firmware update or we are stuck with SMTP servers which use SSL SHA-1 or no encryption."
Agreed. But what did everyone else do? Just give up on email alerts? Surely there are other options. I am really hoping those who found solutions will chime in. For instance, does anyone know of other existing SHA-1 SMTP servers?
Did anyone try to change and burn just one partition of camera's flash? Are there any instructions? I am interested in modifying 'custom' partition (referred to as 'custom-x.cramfs.img' in firmware ZIP file).
The reason I would like to do it is that I flashed newer firmware to my camera and lost TELNET access through port 9527. However, it seems (from /etc/rcS file) possible to create a script located at /mnt/custom/extapp.sh and put a '/sbin/telnetd&' command into it. Alternatively, I have images of original firmware (/dev/mtdblock* devices), copied using 'dd' command to NFS share. But, still, I do not know how to re-construct a legitimate firmware ZIP file out of it.
Camera bears 'smar' logo, model number SAE60-NX4C1001C-E
Product definition: "Hardware" : "50H10L_S38"
/proc/cpuinfo: Hardware : hi3518ev200
Original firmware version:
Build Date:2016/10/24 10:29:57
System: V4.02.R12.00018510.10010.142300.00000
New firmware version (with port 9527 rejecting TELNET connections)
Build Date:2017/1/4 10:15:35
System: V4.02.R12.00018510.12012.142300.00000
The reason I would like to do it is that I flashed newer firmware to my camera and lost TELNET access through port 9527. However, it seems (from /etc/rcS file) possible to create a script located at /mnt/custom/extapp.sh and put a '/sbin/telnetd&' command into it. Alternatively, I have images of original firmware (/dev/mtdblock* devices), copied using 'dd' command to NFS share. But, still, I do not know how to re-construct a legitimate firmware ZIP file out of it.
Camera bears 'smar' logo, model number SAE60-NX4C1001C-E
Product definition: "Hardware" : "50H10L_S38"
/proc/cpuinfo: Hardware : hi3518ev200
Original firmware version:
Build Date:2016/10/24 10:29:57
System: V4.02.R12.00018510.10010.142300.00000
New firmware version (with port 9527 rejecting TELNET connections)
Build Date:2017/1/4 10:15:35
System: V4.02.R12.00018510.12012.142300.00000
I assume you downloaded and installed:
General_HZXM_IPC_HI3518EV200_50H10L_S38_V4.02.R12.Nat.OnvifS.20170104_ALL.bin
杭州雄迈信息技术有限公司-(00018510)IPC_HI3518EV200_50H10L_S38_V4.02.R12.00018510.1
If so, this may work (warning, no garantees, bricking may occur)
General_HZXM_IPC_HI3518EV200_50H10L_S38_V4.02.R12.Nat.OnvifS.20160407_ALL.bin
搜狐企业网盘 - 文件链接
I may have the same camera module, but did not try to flash it (on the basis that it worked, don't fix it if it aint broke)
Good to know now that I should stay away from 2017 firmwares, unless if I really have to.
PS: as to the firmware reconstruction, sorry no. I did "unpack" and compare a few firmware's once using the linux "binwalk" utility, but never reconstructed. From your description, you seem to have done the same.
General_HZXM_IPC_HI3518EV200_50H10L_S38_V4.02.R12.Nat.OnvifS.20170104_ALL.bin
杭州雄迈信息技术有限公司-(00018510)IPC_HI3518EV200_50H10L_S38_V4.02.R12.00018510.1
If so, this may work (warning, no garantees, bricking may occur)
General_HZXM_IPC_HI3518EV200_50H10L_S38_V4.02.R12.Nat.OnvifS.20160407_ALL.bin
搜狐企业网盘 - 文件链接
I may have the same camera module, but did not try to flash it (on the basis that it worked, don't fix it if it aint broke)
Good to know now that I should stay away from 2017 firmwares, unless if I really have to.
PS: as to the firmware reconstruction, sorry no. I did "unpack" and compare a few firmware's once using the linux "binwalk" utility, but never reconstructed. From your description, you seem to have done the same.
Last edited:
Thank you very much, cybermaus. That worked perfectly and backdoor is back!
One of the reasons I wanted to upgrade is that with original firmware, telnet to port 9527 was not giving any screen output, so I had to login and type commands blindly without seeing any result. Your firmware version has output in telnet session. Another thing which did not work is FTP upload when motion is detected (and quite ugly mail client requiring AUTH command to be implemented in MTA even if username/password is blank) - but it does the same in 2017 version anyway. Thanks again, will continue my experiments with these cameras (got 3 of them).
Oh, and sticker on my camera reads "720p". Not sure if there is a difference between 720 and 960..
Just to confirm - this firmware does 'http://WEBCAM-IP/webcapture.jpg?command=snap&channel=1' just fine
Last edited: