Dahua SD49225XA-HNR Auto Tracking Enabled Firmware.
- Thread starter ljw2k
- Start date
Indeed a clone 49225-xa and in teamviewer using the Dahua toolbox it does not see it as a SD49225XA-HNR.
Forget trying to get autotracking working.
Forget trying to get autotracking working.
WOW - what did the userface look like - was it Dahua or was it customized?
If I were the purchaser I would be going back and trying to get my money back for selling me the wrong model.
searched my original firmware and found another firmware, but it appears to be buggy.
It links to a dahau SD49225T-HN. i believe.
yeah that is the older version that did not have autotracking.
Dahua Branding in the interface. looks exactly like what the pictures others have posted, minus the autotracking.
what firwmare would work best? this one looks like it has 3 files in the zip file
www.dahuasecurity.com
Dahua Technology - World-leading Video-centric AIoT Solution and Service Provide
Dahua Technology
Attachments
too late i already tried another firmware. seems buggy, so im trying to revert back
Well for future reference since you are getting into cameras....
You really need to be asking yourself why are you updating? If it is just for grins and giggles or OCD behavior to be running the latest firmware, think twice.
A common theme around here is don't fix what ain't broke. If the unit is working and meets your needs, in many instances an update breaks what you had working and provides you with something you didn't need or bricks the camera. In most instances, updates are simply security vulnerability patches (usually years after the breach was found), but since we do not give our cameras internet access, the update is useless to us.
Unless the release notes specifically mention it fixing a problem you are experiencing, more than likely it won't fix an issue and may make the camera worse by removing functionality.
Here are issues I have seen people report here where they were upgrading just for the sake of upgrading:
Another thing to consider is that the same model could have different firmware for different chipsets used during the life of that model. So you run the risk of bricking if you do not know what chipset you have.
Here is an example - the HFW3549T1-AS-PV is available in 2 versions of firmware across 3 different chipsets for the same model camera:
Further, it is best to obtain any firmware updates from the vendor you purchased it from so that you do not run into issues. Any firmware you find here or elsewhere is obviously proceed at your own risk. We have many threads here where someone tried an update with a firmware they found on the internet and bricked their unit.
Many units being sold are Chinese hacked units into English that will either brick or go into Chinese upon updating. Some vendors will be upfront and tell consumers that as part of their website, but many do not or the consumer forgets...here is one such example....
You really need to be asking yourself why are you updating? If it is just for grins and giggles or OCD behavior to be running the latest firmware, think twice.
A common theme around here is don't fix what ain't broke. If the unit is working and meets your needs, in many instances an update breaks what you had working and provides you with something you didn't need or bricks the camera. In most instances, updates are simply security vulnerability patches (usually years after the breach was found), but since we do not give our cameras internet access, the update is useless to us.
Unless the release notes specifically mention it fixing a problem you are experiencing, more than likely it won't fix an issue and may make the camera worse by removing functionality.
Here are issues I have seen people report here where they were upgrading just for the sake of upgrading:
- Dahua 5241E-Z12E that someone updated and then constantly reboots.
- Dahua 49225 and 49425 PTZ that Dahua intentionally removed autotracking with an update to force people to buy the more expensive PTZ.
- Hikvision DS-2DEA425IW-DW PTZ that Hikvision intentionally removed autotracking with an update to force people to buy the more expensive PTZ (*V5.7.3 220315 -Remove auto-tracking functions on DE4A).
- Hikvision ANPR camera losing half the FPS and loses the ability to read US plates - those are big deals to have happen, especially if you live in the USA.
- Hikvision ANPR DS-2CD4A26FWD camera that lost all ability to read plates - kinda makes a plate reader camera useless.
- Hikvision camera that the user lost ability to control the LED light function at night.
- Hikvision DS-7616NI-Q2 NVR that has the APIs changed. This is a big deal if you run automation.
- Hikvision DS-7616NI-K2 NVR that loses basic functionality when updated.
- Hikvision wifi camera that loses the ability to use wifi after a firmware update and was intentionally removed due to too many complaints that the camera was dropping signal.
- DH-DB61 Doorbell that loses API functionality. A big deal for someone with automation.
- DS-2CD2387G2-LU that loses API functionality. A big deal for someone with automation.
- Hikvision iVM4200 v3.8 - loses the free ability to use the computer as storage and now need to subscribe.
- Dahua IPC-HFW1320S that started phoning home using 60MB/hr and costing someone thousands of dollars in data overages when he got his next mobile bill.
- Dahua 5442 that will not allow playback of the SD card.
- Dahua NVR58XX-4KS2 that had custom protocol (ability to add a camera via RTSP) removed possibly to force people to purchase same brand cameras.
- SmartPSS that intentionally removed the ability to use the Intercom for those with VTO devices after firmware version 2.02.08
- Countless other instances where the camera or NVR simply bricked and became useless.
- Countless examples where the camera or NVR went into Chinese.
- Manufacturers are now preventing their equipment to be updated with an older working firmware after it was updated to a more recent firmware.
Another thing to consider is that the same model could have different firmware for different chipsets used during the life of that model. So you run the risk of bricking if you do not know what chipset you have.
Here is an example - the HFW3549T1-AS-PV is available in 2 versions of firmware across 3 different chipsets for the same model camera:
- HFW3549T1-AS-PV-S4 uses the HX3XXX-Taurus firmware.
- HFW3549T1-AS-PV and IPC-HFW3549T1-AS-PV-S3 use the HX5XXX-Volt firmware
Further, it is best to obtain any firmware updates from the vendor you purchased it from so that you do not run into issues. Any firmware you find here or elsewhere is obviously proceed at your own risk. We have many threads here where someone tried an update with a firmware they found on the internet and bricked their unit.
Many units being sold are Chinese hacked units into English that will either brick or go into Chinese upon updating. Some vendors will be upfront and tell consumers that as part of their website, but many do not or the consumer forgets...here is one such example....
can you guys explain what the wording or name scheme meanings for the files. for example a camera lists firmwares of:
��
��
| General_SD49XXX-HN_MCU_V2.301.0000000.22.R.190923 | |||
| DH_SD-Mao-Rhea_MultiLang_PN_Stream3_IVS_V2.800.0000000.6.R.210705 | |||
| DH_SD-Mao-Rhea_MultiLang_NP_Stream3_IVS_V2.800.0000000.6.R.210705 |
will installing the incorrect version of the same firmware brick the unit? meaning if you use a pal instead of NTSC would it brick? and if so how would you tell the format?
also would i understand that this would be NTSC?
DH_SD-Mao-Rhea_EngSpnFrn_N_Stream3_IVS_V2.622.0000000.7.R.180404.bin