Search results

you can change the mac address in the bootloader with printenv / setenv and about the zoom function, look for the official firmware there should be two bins, the small one is for some special partition which does the zoom. if not the probably the HWID of your camera is wrong, you can change...

It'll only work if your camera still has a working bootloader, you'll notice that it prints text on the serial console while booting if it does. If it doesn't have a bootloader anymore then your only chance is flashing the SPI chip directly. This is not a trivial task. You have to identify the...

Dahua IPC unbricking / recovery over serial UART and TFTP CP2102 or FT232R, make sure you only use 3.3V uart dongles.

Did you turn off P2P in the camera settings?

I think import/export only works with the shitty dahua plugin, try internet explorer? I've actually just finished the FW for the HDW4631C-A yesterday for a seller on aliexpress. He sent me a camera and paid me for it, so I guess I'll wait a bit before releasing it to the public? I haven't been...

upgraded isn't even running on any of the newer cameras / firmware. Has to be manually started through telnet and that is also not available on newer cams / firmware ¯\_(ツ)_/¯ I'm happy for them to fix these issues but they've made the cameras less interesting for me since they added firmware...

>upgrade firmware >thing that worked before doesn't anymore Yep, definitely sounds like a software bug + bad QC from Dahua. Wouldn't be the first time anyways. If you want to revert to an older firmware then you should/have to get a serial UART dongle like this one: CP2102 USB 2.0 to TTL UART...

I can disable the check by patching the sonia/Challenge binary in the new firmware. But you have to get that new firmware onto the camera somehow...

Coincidentally somebody e-mailed me today about the same topic. Also it has been asked in this and other threads a bunch of times. Check out the recovery link in my signature vvvvvvv

On older bootloaders it won't send the console output over the network so you either have to work blind or get a serial interface.

People counting is definitely not possible on this camera. Everything that is available has been unlocked.

Same content, different filetype.

The MTD files represent the partitions of the camera's flash memory. So everything is in there.

Dahua Firmware Mod Kit + Modded Dahua Firmware

Good job. I didn't dare to ask at first because it seemed kinda obvious to check the settings lmao.

I have never heard about that problem and I have no clue what is causing it or how to fix it. But I do know that NFS works fine for me... I guess you've turned off the delete option in the settings? I think it's next to the auto reboot setting.

Well.... You have to do printenv in the u-boot shell xd but you can do this instead: cat /proc/mtdinfo and look for hwid cat /dev/mtd1ro (when mtd1 is hwid in mtdinfo) and you should basically get what printenv does

Are you using the info from this thread? It should work unless Dahua changed something, in which case I'll look at it later.

The PTZ firmware is for some other chip I guess, it's just some tiny blob. And here's the patched main firmware: https://i.botox.bz/DH_SD-Mao-Rhea_EngSpnFrn_N_Stream3_IVS_V2.600.0000.2.R.20170905.bin Removed the signature check, the region check and added telnet on port 2300.

There is only one firmware, the different versions PAL/NTSC PTZ?? don't mean much, at least it doesn't matter for me - no clue if they have different functions / options. Anyways send me the firmware you want me to modify.

You can't just "remove the signature". You can remove the check from a firmware, but then the signature doesn't match anymore and the camera won't accept it. If you are on a firmware that checks the signature then you can only flash signed firmware and only dahua can sign it because only they...

The info I need would be the same, some stuff would be different like the serial number - but as I said not important

Once I get that printenv info this method can be used: Dahua IPC EASY unbricking / recovery over TFTP

Sure, I can do that today.

Yeah the same utelnetd works on the same camera, well in theory Dahua could change the libc being used but that doesn't happen. I can modify the new firmware and remove the signature check, done it before pretty easy. Then you can flash back via the webui too.

Some cameras use different libc or have different processors so the same compile of utelnetd will not work on all cameras. For example eos uses uclibc while these ones use armhf gnu libc. Also if you edit any file the signature changes and you have to flash through u-boot / recovery.

NFS is not a filesystem, it's a protocol for transmitting files, just like FTP - but way better. So you want to downgrade from DH_SD-Eos_Eng_P_Stream3_V2.600.0000.3.R.20170630 to DH_SD-Eos_EngSpnFrn_N_Stream3_V2.420.0001.0.R.20161220, correct? 20170630 has signature verification. 20161220 DOES...

Okay, here is the firmware for @wxman : https://i.botox.bz/General_SD-Mao-Rhea_Eng_N_Stream3_IVS_V2.422.0000.1.R.20161130.bin Telnet is on port 2300

My suggestion is to use Linux with XFS or ZFS (depending on how many disks / RAID) so you can split up HDDs into smaller blocks and export those through NFS (Network File System - it's a protocol). For syncing I'd use syncthing, free software and self hosted. But not everyone can be an expert...

Okay, that was my fault, I got the two of you mixed up. So Miles wants to flash DH_SD-Eos_EngSpnFrn_N_Stream3_V2.420.0001.0.R.20161220 on his SD52C225U-HNI. Though I'd suggest just setting up an NFS share, FTP sucks. Would that be a possibility for you? And wxman wants telnet access to his...