Dahua firmware

[chubros 0]

Hello from Greece. I have the dahua hfw3200sn. I flash it with a wrong firmware and the cam stop working. I open it to find the 3 pin's for rs232 but i can't find any. Did anyone have an idea? Also did someone have a correct firmware for this cam? I 'm desperate...Thanks in advance...

[MaxIcon 0]

I haven't seen anyone identify the connections here, or even whether it's a serial interface vs JTAG, which is more complicated. If anyone here knows, they're not sharing.

 

My HFW3300C has a three pin connector inside, and I haven't played with it yet. My HFW2100 is the same size as your camera, but I haven't looked for the connector yet.

 

Here's the board with connector (labeled J3) that I suspect is the serial/JTAG connector on the HFW3300C:

[chubros 0]

The strange thing is that when i ping the camera at the 192.168.1.108 i take some ping replies for some seconds. For this seconds i could telnet the cam but the cam restarts and the telnet loses connection. I dont know if there is a special cable for connecting the cam to pc via a rs232(pc) and ethernet(cam) and run tftp like software.... Inside the cam i had also a 4 pin connector like this in your photo but i cant understand what it is...

[cheetokhan 0]

Device Type IPC-HFW2100

Software Version 2.100.0001.0.R, build : 2012-10-31

WEB Version 3.0.0.0

Format: NTSC

 

 

https://dl.dropboxusercontent.com/u/16362986/General_IPC-HX2XXX_Eng_N_BootSpi_V2.100.0001.0.R.20121031%20(1).bin

 

Thanks. Does anyone know what this changes from the Costco QSee firmware?

 

Software Version 2.100.QS00.8.R, build : 2012-07-19

WEB Version 3.0.0.0

[Q2U 0]

Device Type IPC-HFW2100

Software Version 2.100.0001.0.R, build : 2012-10-31

WEB Version 3.0.0.0

Format: NTSC

 

https://dl.dropboxusercontent.com/u/16362986/General_IPC-HX2XXX_Eng_N_BootSpi_V2.100.0001.0.R.20121031%20(1).bin

 

Thanks. Does anyone know what this changes from the Costco QSee firmware?

 

Software Version 2.100.QS00.8.R, build : 2012-07-19

WEB Version 3.0.0.0

 

 

Are you seriously considering installing firmware which was posted by a person who has been a member for one single month and has contributed only seven posts? This sounds like flash 'n to me bro...and not very wise.

[fdnyfish 0]

It's legit, I just stumbled on the forum after looking for some help

[dexterash 0]

I have a bunch of firmwares too... Anyone wanna try killing their camera? Including the main bootloader(as in dead SoC until resolder)?

[MaxIcon 0]

An easy test would be to download another file of the same version and do a binary compare:

 

viewtopic.php?p=213477#p213477

 

Broken record time: This would be so much easier if Dahua would provide a little support, like Vivotek, Messoa, Hikvision, Arecont, IQInvision, etc, etc...

[dexterash 0]

Where did you find HIK providing official support?(just curiosity)

Also, Arecont is US based so they have(somehow) to provide support.

 

The others are low-exposure (at least at an international level) companies, so...

 

And just as an advice: firmware for flashing via NFS/TFTP/RS232/JTAG is completely different from what you flash via the web interface/standard tools provided.

[MaxIcon 0]

I don't have a Hikvision, but the firmware was readily available on a google search. This was how I identified the Swann as a Hikvision in the first place, when someone posted their firmware revision. Here are some Hikvision downloads:

http://www.hikvisioneurope.com/portal/index.php?dir=Technical%20Materials/Firmwares/Cameras/

 

The TFTP/RS232 updates are easy if you have the right cable. JTAG can be more difficult, depending on the interface, but you know that, I'm sure.

[dexterash 0]

I doubt that is a legit/original HIK Site. There are DAHUA named/cloned sites too... Since they are growing as a manufacturer, their exposure it's growing too, allowing others to use the fake products/names (I talk about fake products/copies, not OEM/reseller products - like SWANN, QSEE&others).

 

Simple fact:

Main HIK Site: http://www.hikvision.com/en/us/partner.asp - with no firmware downloads & others; only the usual SDK, CMS, etc; also, in the partner list, no link to that site, although they do provide partners from Europe

 

Because I know how to flash and what can happen when you flash I advise people that are not used to this kind of stuff to stay away from that. These SoCs use bootloaders&other loaders that are stored inside them(initially flashed during the manufacturing process). The RS232 method can only check for the integrity of the file, not if the file is indeed what needs to be flashed and at what address. Because of this, devices can be very easily bricked (yes, I speak from my own experience with customers trying to "upgrade" their devices).

 

L.E.: you stated HIK as a manufacturer that provides higher level support than DAHUA, that's why I asked

 

L.E.: My fault (http://www.hikvision.com/en/us/contactHikvision.asp)! Sorry.

[MaxIcon 0]

Device Type IPC-HFW2100

Software Version 2.100.0001.0.R, build : 2012-10-31

WEB Version 3.0.0.0

Format: NTSC

 

 

https://dl.dropboxusercontent.com/u/16362986/General_IPC-HX2XXX_Eng_N_BootSpi_V2.100.0001.0.R.20121031%20(1).bin

 

For what it's worth, this compares identically to the same rev firmware uploaded by ilkevinli in another thread.

 

Thanks to both of you for helping out. It's sad that it's come to this, but it's good that the community is stepping up to the plate. Those of us without access to Dahua's inner circle appreciate it.

Edited May 2, 2013 by Guest

[MaxIcon 0]

Because I know how to flash and what can happen when you flash I advise people that are not used to this kind of stuff to stay away from that. These SoCs use bootloaders&other loaders that are stored inside them(initially flashed during the manufacturing process). The RS232 method can only check for the integrity of the file, not if the file is indeed what needs to be flashed and at what address. Because of this, devices can be very easily bricked (yes, I speak from my own experience with customers trying to "upgrade" their devices).

 

Sigh. Look, I understand your point of view. This is your business and your living, and you don't want to give away free expertise; it's completely understandable. Nobody wants to work for free.

 

I'm just a hobbyist, and I'm also a troubleshooter and maker. I like to help people who don't have my technical expertise. I do this for fun.

 

I never mention TFTP except when someone has *already* bricked their device. If they had Dahua support, they'd have used it. These users who have already made a mistake and now have unusable devices now have no other option. Dahua doesn't offer them anything, that's for sure.

 

Most people don't have the technical skills to TFTP their firmware, and many of them don't have the files they need even if they did have the skills. Still, this is what Dahua would do to fix their gear if they could get Dahua to help.

 

They ask "Is there anything else that can be done?" So far, nobody's ever come back and said "Hey, that TFTP upload fixed my problem, and here's how it worked!" If they do, well, there's a useful data point. If I ever get the opportunity to make it work, I'll publish the details, because that's what I do.

 

Until then, yeah, the advice may be useless, but it's the only thing they have.

 

If Dahua offered them support, it would be a different matter, but they don't. If someone else offered useful suggestions, that would be great, but they don't. When your only option's the trashcan, where's the harm?

[dexterash 0]

Well,if it was my main business, I would probably be broke by now (since most don't understand some things).

 

What I wanted to point out is that:

-firmwares can be cloned and modified easily - products are being copied, that means this is a regular thing;

-I'm an IT guy: programming, networks (including Linux servers) & security (and, also, pentesting/"whitehat" hacking), so I always check for what devices I use and, if needed to update, where I get my update from

-people are asking support directly from DAHUA, but not how to get support (from whom, where etc); trashing is not an option, asking for direct support will go to junk bin(I suppose!), but asking WHERE to get support might have results

-I've never seen a major manufacturer explaining test points, JTAG and serial interfaces on their products (it's a major security flow, besides other problems)

(side note: we don't own any firmwares; all products that are firmware broken will go to our local DAHUA's representative to be flashed there, on site, with the firmwares that are tested to be sure)

 

I'm aware this sounds a little crazy, but I will not recommend anyone to (try) update their product using "any" firmware they can find. Having security cameras installed in the most sensitive places of your objective and leaving them with unknown/maybe buggy software is a major security flow. It's like providing a free access to your assets for anyone bad intended. And, trust me, there are people!

 

For example, there's been an issue around with DAHUA's ONVIF implementation with no security. True, there is a test version of an ONVIF firmware that has some bugs. Using this firmware you just make an invite to your (free) security system.

 

Also, as I stated before, with some testing, knowledge and hardware the firmware can be "read" and modified using open-source tools. Sounds nice, but also leaves a major security gap. (even here, someone posted a way to bypass any security and just delete the config of the recording camera... not the smartest thing I've seen)

[Dâniel Fraga 0]

I got the new Dahua HFW2100 firmware (2.210.0000.0.R, build : 2013-03-13) from my re-seller and I upgraded it succesfully. It has new options (https login, better picture controls, a much improved motion detection area settings etc).

 

The problem is: it isn't recording anything to the FTP. I already tried to reset to default settings and reconfigure the settings again, without success. Everything is correctly configured in Event and Storage menus.

 

With previous firmware (2012/10) everything works fine.

 

Is anybody using the same firmware and noticed the same FTP recording issue?

 

Thank you.

 

Ps: please don't ask for the firmware since I can't redistribute it (it contains dealer code buitin and the dealer could lose

the reseller's license if it is distributed so ask your own reseller if you want it).

[dexterash 0]

You got a SD card installed?

[Dâniel Fraga 0]

You got a SD card installed?

 

No. I record directly to the FTP server.

[dexterash 0]

Only snapshots can be uploaded to FTP server.

 

For recordings, FTP server is used as a "backup" device, and it needs a card to "temporary" store the recordings, before uploading them.

[Dâniel Fraga 0]

Only snapshots can be uploaded to FTP server.

 

For recordings, FTP server is used as a "backup" device, and it needs a card to "temporary" store the recordings, before uploading them.

 

With previous firmware I could upload video recordings directly to the FTP. The Dahua HFW2100 doesn't accept any SD card and it

can record videos... I have the directory structure to proof it if you want:

 

ls 2013-05-16/001/dav/16

16.00.02-16.00.40[M][0@0][0].dav 16.08.11-16.08.47[M][0@0][0].dav

16.00.02-16.00.40[M][0@0][0].idx 16.08.11-16.08.47[M][0@0][0].idx

16.00.42-16.01.21[M][0@0][0].dav 16.08.53-16.09.13[M][0@0][0].dav

16.00.42-16.01.21[M][0@0][0].idx 16.08.53-16.09.13[M][0@0][0].idx

16.01.26-16.01.45[M][0@0][0].dav 16.09.18-16.09.40[M][0@0][0].dav

16.01.26-16.01.45[M][0@0][0].idx 16.09.18-16.09.40[M][0@0][0].idx

16.01.52-16.02.11[M][0@0][0].dav 16.09.44-16.10.58[M][0@0][0].dav

16.01.52-16.02.11[M][0@0][0].idx 16.09.44-16.10.58[M][0@0][0].idx

16.02.21-16.02.54[M][0@0][0].dav 16.11.06-16.11.40[M][0@0][0].dav

16.02.21-16.02.54[M][0@0][0].idx 16.11.06-16.11.40[M][0@0][0].idx

16.03.18-16.03.53[M][0@0][0].dav 16.11.42-16.13.11[M][0@0][0].dav

16.03.18-16.03.53[M][0@0][0].idx 16.11.42-16.13.11[M][0@0][0].idx

16.03.57-16.04.48[M][0@0][0].dav 16.13.22-16.14.49[M][0@0][0].dav

16.03.57-16.04.48[M][0@0][0].idx 16.13.22-16.14.49[M][0@0][0].idx

16.04.52-16.05.32[M][0@0][0].dav 16.14.53-16.15.50[M][0@0][0].dav

16.04.52-16.05.32[M][0@0][0].idx 16.14.53-16.15.50[M][0@0][0].idx

16.05.36-16.06.50[M][0@0][0].dav 16.15.54-16.17.53[M][0@0][0].dav

16.05.36-16.06.50[M][0@0][0].idx 16.15.54-16.17.53[M][0@0][0].idx

16.07.10-16.08.05[M][0@0][0].dav 16.17.59-16.18.31[M][0@0][0].dav

16.07.10-16.08.05[M][0@0][0].idx 16.17.59-16.18.31[M][0@0][0].idx

 

This was generated with a Dahua HFW2100 using the firmware form 2012 October.

 

The new firmware, for some unknown reason isn't recording anything.

[dexterash 0]

Auch, not a very nice bug. I'll check it out soon.Also, we mostly use NVRs so we're less concerned by this, but it's a good thing to know/test. I'll get back with news ASAP.

 

Honestly, I haven't had time to fully check this release, since I was interested in other facts (more picture settings, hourly settings, playback on SD-Card enabled IPCs etc)

[Dâniel Fraga 0]

Auch, not a very nice bug. I'll check it out soon.Also, we mostly use NVRs so we're less concerned by this, but it's a good thing to know/test. I'll get back with news ASAP.

 

Honestly, I haven't had time to fully check this release, since I was interested in other facts (more picture settings, hourly settings, playback on SD-Card enabled IPCs etc)

 

Thank you very much! And feel free to ask me to test anything you want.

[dexterash 0]

Do you have a custom path setup for recordings?

[Dâniel Fraga 0]

Do you have a custom path setup for recordings?

 

Yes. I record to "sda_part1" directory (where DD-WRT mounts my external HD).

 

I noticed it even created the folder inside it, but just creates the "DVRWorkDirectory" file and nothing else.

[dexterash 0]

Can you make ddwrt upload syslogs to another box?

Maybe it's a thing about FTP/uploading.

[Dâniel Fraga 0]

Can you make ddwrt upload syslogs to another box?

Maybe it's a thing about FTP/uploading.

 

The problem is not with the DD-WRT since it was working perfectly with the previous firmware. I just upgraded to the new one and the camera doesn't record anymore. Anyway I looked at the logs and everything is fine, no error messages.

 

I'm almost sure it's a bug in the new firmware.