How To Upgrade Amcrest / Lorex to Dahua Firmware And Get All Dahua Features
- Thread starter jd415
- Start date
Here is the report from malwarebytes. And then a clip from IP Blacklist Check - Over 50+ Blacklist Providers. Looks like it is on one blacklist (all others say its fine). Interesting. probably fine.
This is what I get from the DNSBL, the link you provided: DNSBL check page
"This IP was flagged due to misconfiguration of the e-mail service or the suspicion that there is no MTA at it."
It has nothing to do with Trojans. Your software misinterprets the DNSBL listing. Moreover, dahuawiki.com resolves to one of GoDaddy servers. I doubt they will host anything bad.
"This IP was flagged due to misconfiguration of the e-mail service or the suspicion that there is no MTA at it."
It has nothing to do with Trojans. Your software misinterprets the DNSBL listing. Moreover, dahuawiki.com resolves to one of GoDaddy servers. I doubt they will host anything bad.
Very cool. with these latest posts I was able to update my Amcrest IP8M-2496EB to the firmware @Schnoidz referenced above. My snapshot looks the same. I did have to clear my browser/history cache to get rid of the amcrest login. Basically, after factory reset post updating the firmware, I reset the static IP to what I had it set as in my router and BI. When I went to login it was with the amcrest logo, etc. So, I set IP back to 192.168.1.108 (.108 is what you get after a factory reset most of the time), cleared browser/history, restarted chrome, logged back in, changed IP back to my original static IP address, and login worked great with Dahua firmware. Another poster suggested going to the latest amcrest firmware first - I also did this; not sure if it matters. Adding IVS is a good upgrade in my book; didn't log all changes, but face detection an option under Event now as well.
@mmmburritos - thanks for the link! The one in the video was not working.
So, if I'm not mistaken, this then camera takes the same Dahua firmware as the IPC-HDW5231R-ZE.
Attachments
Last edited:
Did you gain anything by updating the firmware to Dahua's? I know you get extra features like IVS etc. but if you are using BI are they useful? I am in doubt that updating the firmware to Dahua's brings anything strictly for BI usage.
AngryToast
Young grasshopper
I would like to do this too. I have the IP8M-T2499EW running the Dahua DH_IPC-HX5X3X-Rhea_MultiLang_NP_Stream3_V2.800.0000014.0.R.191203.bin firmware and tried to roll back to the 2 latest Amcrest FW versions but neither would complete the upgrade:
Amcrest_IPC-HX5X3X-Rhea_Eng_N_Stream3_AMCREST_V2.622.00AC000.0.R.191024.bin
Amcrest_IPC-HX5X3X-Rhea_Eng_NP_Stream3_AMCREST_V2.622.00AC000.0.R.200320.bin
but at least it didn't brick the camera. I too would like to know how to go back to the Amcrest firmware. I must be odd, I prefer the Amcrest FW over the Dauhua because the Amcrest saves the videos to FTP as an mp4.
Last edited:
SOLVED
For anyone interested in this post please go to this thread to find the solution.
Hello IPCam fanatics,
I'm here because I want to convert my Amcrest PTZ camera (IP2M-853EW) to a Dahua. I've tried upgrading to the latest Amcrest firmware and then afterwards upgrading to the latest Dahua firmware through the web gui but that didn't work.
I've also already read this thread and now I'm so close to hitting pay dirt I can taste it!!!
Here is where I'm stuck...as you can see from my tftp server results below I have successfully used the tftp server to interface with the Amcrest camera (All blocks served). When finished executing the commands I get the error message "success.txt, File not found or No Access". Afterwards it begins this process all over again in a loop.
As for the console.bat results below, as far as I can tell the error that I think is relevant is the "failed to load bootTargsParametersV22.txt".
I'm trying to upgrade to the DH_SD-Mao-Rhea_MultiLang_PN_Stream3_IVS_Market_V2.800.0000000.4.R.191105 firmware. I've read that several users have had success with this firmware with these types of PTZ's. When comparing this Dahua firmware to the latest Amcrest firmware, which is loaded on the camera, I noticed the Dahua firmware has three bin files compared to the Armcrest's one bin file. The Dahua's additional bin files are called "Partition.bin" and "Upall_SD-Mao-Rhea.20191105.bin". The "Partition.bin" file is 1KB and the "Upall_SD-Mao-Rhea.20191105.bin" is 135,168 KB's. The latter .bin contains 2 files named "partition.txt" and "partitionV2.txt".
If anyone has any ideas to get me through this last hurdle I would greatly appreciate any help. Thank you
For anyone interested in this post please go to this thread to find the solution.
Hello IPCam fanatics,
I'm here because I want to convert my Amcrest PTZ camera (IP2M-853EW) to a Dahua. I've tried upgrading to the latest Amcrest firmware and then afterwards upgrading to the latest Dahua firmware through the web gui but that didn't work.
I've also already read this thread and now I'm so close to hitting pay dirt I can taste it!!!
Here is where I'm stuck...as you can see from my tftp server results below I have successfully used the tftp server to interface with the Amcrest camera (All blocks served). When finished executing the commands I get the error message "success.txt, File not found or No Access". Afterwards it begins this process all over again in a loop.
Code:
accepting requests..
Open TFTP Server MultiThreaded Version 1.64 Windows Built 2001
starting TFTP...
alias / is mapped to root\
permitted clients: all
server port range: all
max blksize: 65464
default blksize: 512
default timeout: 60
file read allowed: Yes
file create allowed: Yes
file overwrite allowed: Yes
thread pool size: 1
Listening On: 192.168.254.254:69
Client 192.168.1.108:3109 root\upgrade_info_7db780a713a4.txt, 1 Blocks Served
Client 192.168.1.108:3284 root\romfs-x.squashfs.img, 973 Blocks Served
Client 192.168.1.108:1500 root\kernel.img, 1178 Blocks Served
Client 192.168.1.108:3657 root\user-x.squashfs.img, 13308 Blocks Served
Client 192.168.1.108:1345 root\web-x.squashfs.img, 3953 Blocks Served
Client 192.168.1.108:1411 root\partition-x.cramfs.img, 5 Blocks Served
Client 192.168.1.108:2312 root\custom-x.squashfs.img, 853 Blocks Served
Client 192.168.1.108:3187 root\pd-x.squashfs.img, 47 Blocks Served
Client 192.168.1.108:1135 root\.FLASHING_DONE_STOP_TFTP_NOW, 1 Blocks Served
Client 192.168.1.108:3496 root\success.txt, File not found or No Access
Client 192.168.1.108:3106 root\upgrade_info_7db780a713a4.txt, 1 Blocks Served
Client 192.168.1.108:3281 root\romfs-x.squashfs.img, 973 Blocks Served
Client 192.168.1.108:1475 root\kernel.img, 1178 Blocks Served
Client 192.168.1.108:3567 root\user-x.squashfs.img, 13308 Blocks ServedAs for the console.bat results below, as far as I can tell the error that I think is relevant is the "failed to load bootTargsParametersV22.txt".
Code:
Ncat: Version 7.40 ( https://nmap.org/ncat )
Ncat: Listening on 192.168.254.254:5002
tition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename '.FLASHING_DONE_STOP_TFTP_NOW'.Download to address: 0x2000000
Downloading: #
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
get bootargs info failed
cmdLine console=ttyS0,115200 mem=150M root=/dev/mtdblock8 rootfstype=squashfs init=/linuxrc
arella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'romfs-x.squashfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 1427704 (15c8f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: romfs
Created: 2019-11-05 9:00:05 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1427640 Bytes = 1.4 MiB
Load Address: 01200000
Entry Point: 01600000
Verifying Checksum ... OK
Programing start at: 0x01200000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'kernel.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 1728248 (1a5ef8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: kernel
Created: 2019-11-05 9:00:03 UTC
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 1728184 Bytes = 1.6 MiB
Load Address: 00c80000
Entry Point: 01200000
Verifying Checksum ... OK
Programing start at: 0x00c80000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'user-x.squashfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 19536120 (12a18f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: user
Created: 2019-11-05 9:00:31 UTC
Image Type: ARM Linux Standalone Program (uncompressed)
Data Size: 19536056 Bytes = 18.6 MiB
Load Address: 01e00000
Entry Point: 03a80000
Verifying Checksum ... OK
Programing start at: 0x01e00000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'web-x.squashfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 5802232 (5888f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: web
Created: 2019-11-05 9:00:09 UTC
Image Type: ARM Linux Standalone Program (uncompressed)
Data Size: 5802168 Bytes = 5.5 MiB
Load Address: 01600000
Entry Point: 01e00000
Verifying Checksum ... OK
Programing start at: 0x01600000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'partition-x.cramfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 6392 (18f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: partition
Created: 2019-11-05 9:00:02 UTC
Image Type: ARM Linux Standalone Program (uncompressed)
Data Size: 6328 Bytes = 6.2 KiB
Load Address: 00500000
Entry Point: 00600000
Verifying Checksum ... OK
Programing start at: 0x00500000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'custom-x.squashfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 1251576 (1318f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: custom
Created: 2019-11-05 9:00:47 UTC
Image Type: ARM Linux Standalone Program (uncompressed)
Data Size: 1251512 Bytes = 1.2 MiB
Load Address: 00600000
Entry Point: 00940000
Verifying Checksum ... OK
Programing start at: 0x00600000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
fail to load bootargsParametersV22.txt
fail to load bootargsParametersV21.txt
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'pd-x.squashfs.img'.Download to address: 0x2000000
Downloading: *
done
Bytes transferred = 67832 (108f8 hex)
do not find BOOT_IMG_NAME!
Erasing update flag partition.
partition file version 2
rootfstype squashfs root /dev/mtdblock8
partition file version 2
rootfstype squashfs root /dev/mtdblock8
## Checking Image at 02000000 ...
Legacy image found
Image Name: pd
Created: 2019-11-05 9:00:45 UTC
Image Type: ARM Linux Standalone Program (uncompressed)
Data Size: 67768 Bytes = 66.2 KiB
Load Address: 00940000
Entry Point: 00c80000
Verifying Checksum ... OK
Programing start at: 0x00940000
write : 100%
done
partition file version 2
rootfstype squashfs root /dev/mtdblock8
parI'm trying to upgrade to the DH_SD-Mao-Rhea_MultiLang_PN_Stream3_IVS_Market_V2.800.0000000.4.R.191105 firmware. I've read that several users have had success with this firmware with these types of PTZ's. When comparing this Dahua firmware to the latest Amcrest firmware, which is loaded on the camera, I noticed the Dahua firmware has three bin files compared to the Armcrest's one bin file. The Dahua's additional bin files are called "Partition.bin" and "Upall_SD-Mao-Rhea.20191105.bin". The "Partition.bin" file is 1KB and the "Upall_SD-Mao-Rhea.20191105.bin" is 135,168 KB's. The latter .bin contains 2 files named "partition.txt" and "partitionV2.txt".
If anyone has any ideas to get me through this last hurdle I would greatly appreciate any help. Thank you
Last edited:
Attempt to buy this IP8M-T2499EW (4mm version)
1. Hope anyone can kindly help to let me know if this camera at night time will NOT show any glow (absolutely no light).
2. How far (feet or meter) the camera can see in a clear picture if I buy the 4mm version ?
Thanks a lot.
1. Hope anyone can kindly help to let me know if this camera at night time will NOT show any glow (absolutely no light).
2. How far (feet or meter) the camera can see in a clear picture if I buy the 4mm version ?
Thanks a lot.
fenderman
Staff member
- Mar 9, 2014
- 36,892
- 21,407
Thanks. visible ? how bright of the red ? (The reason was that I read a post somewhere talking about the IR light on this model won't show red at night.) I thought only 940nm won't show red light ?!
Schnoidz
Getting the hang of it
It's not bright but it absolutely can be seen. Glow is a good description. I have 6 of these (all 2.8mm) and tested turning off the IR light in my darkest area. It does not see well at all with no light but does a much better job with the built-in IR turned on, which is how I use them. These are great daytime cameras and OK for night.
I have 2 Dahua IPC-T5442TM-AS cameras, 1 - 2.8mm and 1 - 4mm. They are both great daytime and amazing nighttime cameras.
I have 2 Dahua IPC-T5442TM-AS cameras, 1 - 2.8mm and 1 - 4mm. They are both great daytime and amazing nighttime cameras.
Thanks Schnoidz. as learning from you all here, can you share your experiences ? This will help me to choose either one for my driveway which has no light.
1. how far will the images for the IP8M-T2499EW (with turn-off the IR) can be reasonabely-clear seen ?
2. your IPC-T5442TM-AS 4mm starlight+ cameras doesn't have glow at night (in b/w), right ? What is your experiences ? [I read a review saying this one doesn't have the IR filter cut. but another article saying IR LED's are under the black plastic cover. people wont see them unless you're looking at them at night.]
3. does IPC-T5442TM-AS have the firmware converting from Amcrest to Duhua for the additional IVS type of features ?
Many thanks to you and all.
Last edited:
Schnoidz
Getting the hang of it
Depending on the available light, the Amcrest IP8M-T2499EW might see a bit at night but it won't be clear. They are really sharp and impressive during the day but are not night cameras. I use extra IR lights to flood my backyard with IR light at night and they do a pretty good job out here. Last night when I tested one without any IR light in a dark area I could only see a few feet and NOTHING was clear.
All my IR lights on all 19 cameras have a glow and can be seen if looking straight into them. So can all my external IR lights. If I look into my backyard with my eyes it looks pitch black while my cameras see the yard as flooded in light (in black and white).
The IPC-T5442TM-AS is a Dahua camera and comes with their firmware installed.
All the IR lights give off no visible light except for the light red glow of each bulb. If someone does not know they are emitting infrared light they would have no idea that there is light in the area. What the cameras see as a spotlight our eyes see as nothing but little glowing specks. Standing off to the side of the iIR lights they are hard to see. Looking straight into them they are obvious glows.
Turning off the IR light on the IPC-T5442TM-AS still allows you to see at night, very much better than the Amcrest IP8M-T2499EW. But turning on the IR lets it see clear and sharp in the dark.
All my IR lights on all 19 cameras have a glow and can be seen if looking straight into them. So can all my external IR lights. If I look into my backyard with my eyes it looks pitch black while my cameras see the yard as flooded in light (in black and white).
The IPC-T5442TM-AS is a Dahua camera and comes with their firmware installed.
All the IR lights give off no visible light except for the light red glow of each bulb. If someone does not know they are emitting infrared light they would have no idea that there is light in the area. What the cameras see as a spotlight our eyes see as nothing but little glowing specks. Standing off to the side of the iIR lights they are hard to see. Looking straight into them they are obvious glows.
Turning off the IR light on the IPC-T5442TM-AS still allows you to see at night, very much better than the Amcrest IP8M-T2499EW. But turning on the IR lets it see clear and sharp in the dark.
fenderman
Staff member
- Mar 9, 2014
- 36,892
- 21,407
Dont be paranoid about the ir glow. Someone seeing the camera is not a bad thing. They can see the camera during the day with no ir glow. There are two different versions of the same camera, one with IR light one with LED white light. All cameras with IR light have visible 850nm IR light because it has a stronger effect. The 5442 is a dahua camera, amcrest does not rebrand this model.
Just flashed an Amcrest NVR NV4108E-HS with Dahua firmware. Used the firmware from this model. Dahua Wiki
Looks like I gained some Ai functionality...still need to play around with it.
Looks like I gained some Ai functionality...still need to play around with it.
Thanks for the heads up! My friend just ordered one and should be getting his within a week. Did you just basically load the dahua firmware and it took it?
Pretty much, installed with no issues. Can access the video now on chrome with no plugins. Amcrest firmware needed IE or some awful chrome extension.