Review-Dahua IPC-HFW1831C-PIR 4k Mini Bullet

val-ipcam said:
I upgraded LNB8105X to DH_IPC-HX2X3X-Rhea_MultiLang_NP_Stream2_V2.800.0000016.0.R.200605.bin via TFTP, and then was able to upgrade via GUI to DH_IPC-HX2X3X-Rhea_MultiLang_NP_Stream2_V2.800.0000018.0.R.210707.bin. I did it recently, so not sure how reliable it will be. After upgrade IVS became available, which seems to work fine so far.
Click to expand...

This is the first report I've seen of a successful tftp upgrade of the Lorex version of this camera.
How did you perform this upgrade? Standard TFTP update?
I had one camera that came with my Lorex setup that was mistakenly running Dahua out of the box, but could not get the others that were running Lorex firmware to take the Dahua firmware via TFTP.
 
Thanks! Did you follow any specific tftp directions on ipcamtalk? Since you're showing disassembly, I'm assuming you used TFTP over serial?
Did you use a POE switch or NVR to get it to power up or use an alternate 12v power source?
 
Thanks for the file. The CRC does not look to match for versions DH_IPC-HX2X3X-Rhea_MultiLang_NP_Stream2_V2.800.0000016.0.R.200605 nor DH_IPC-HX2X3X-Rhea_MultiLang_NP_Stream2_V2.800.0000018.0.R.210707
Which is it for?

How did you get LAN install to work on these? I cannot get one of these Lorex branded cams to boot from my tftp server. I know the tftp server works as I've tested it with other devices..

Thanks!
 
I assigned 2 IP addresses to the laptop that was used as an tftp server. Described in Option 2 in the following post:

Dahua IPC EASY unbricking / recovery over TFTP

A successor of Dahua IPC unbricking / recovery over serial UART and TFTP I recommend you to read through the above thread first. If your camera still has a working bootloader (assume it does) then you can flash it easily, because: The camera tries to download a file called...
ipcamtalk.com ipcamtalk.com
 
@val-ipcam I'm getting ready to flash the Lorex, just wanted to confirm.

-I've downloaded the file you provided upgrade_info_7db780a713a4.txt that will tell the systems what it needs (in the TFTP root)
-I've downloaded the firmware BIN file (DH_IPC-HX2X3X-Rhea_MultiLang_PN_Stream2_V2.800.0000016.0.R.200605) and used WINRAR to extract all the IMG files (in the TFTP root)
-I've checked the check.IMG file, it has the cameras HWID listed with this command: http://<camera_IP_address>/cgi-bin/magicBox.cgi?action=getSystemInfo

So basically all I need is to get my laptop on 192.168.254.254 with a subnet mask of 255.255.0.0 connect the camera and power it up, it should grab the right files and update.

Thanks1
 
Nothing on TFTP, camera is on DHCP and instructions aren't clear if one needs to set the camera for 192.168.1.108 as static IP or if it defaults to this is it doesn't received any DHCP request.
@val-ipcam to you recall, did you set your cameras with static IPs 192.168.1.108 or did they default to this out of the box? Mine is set for DHCP...

Edit - I set the camera to 192.168.1.108, as well as tried both 255.255.0.0 and 255.255.255.0 subnet, there is no TFTP action whatsoever, just boots up into the menu on power cycling it...

I have the LNB8211x which is exactly like LNB8105x, I'm guessing older firmware (mine is as below)

Device Type LNB8211X
System Version 00007
Build Date 2018-08-16
WEB Version V3.2.1.582554
ONVIF Version 16.12(V2.4.3.574996)

Getsysteminfo is showing me the correct IPC though: updateSerialCloudUpgrade=IPC-HFW1831C-PIR:01:02:02:50:21:00:01:0F:01:01:04:2D0:00:00:00:00:00:00:00:00:200 which is listed in the checkinfo.img file of theDahua firmware.

So not sure what's up, either my process is wrong and I'm missing something obvious, or the firmware on this camera won't allow TFTP (I don't believe this is the case, as most use TFTP for firmware upgrades)
 
Last edited:
teredactle said:
Nothing on TFTP, camera is on DHCP and instructions aren't clear if one needs to set the camera for 192.168.1.108 as static IP or if it defaults to this is it doesn't received any DHCP request.
@val-ipcam to you recall, did you set your cameras with static IPs 192.168.1.108 or did they default to this out of the box? Mine is set for DHCP...

Edit - I set the camera to 192.168.1.108, as well as tried both 255.255.0.0 and 255.255.255.0 subnet, there is no TFTP action whatsoever, just boots up into the menu on power cycling it...

I have the LNB8211x which is exactly like LNB8105x, I'm guessing older firmware (mine is as below)

Device Type LNB8211X
System Version 00007
Build Date 2018-08-16
WEB Version V3.2.1.582554
ONVIF Version 16.12(V2.4.3.574996)

Getsysteminfo is showing me the correct IPC though: updateSerialCloudUpgrade=IPC-HFW1831C-PIR:01:02:02:50:21:00:01:0F:01:01:04:2D0:00:00:00:00:00:00:00:00:200 which is listed in the checkinfo.img file of theDahua firmware.

So not sure what's up, either my process is wrong and I'm missing something obvious, or the firmware on this camera won't allow TFTP (I don't believe this is the case, as most use TFTP for firmware upgrades)
Click to expand...

The camera IP setting does not matter. At lower level when the firmware boots, it has a default IP it checks for tftp with before the firmware continue fully booting up the camera.
 
exarkun said:
The camera IP setting does not matter. At lower level when the firmware boots, it has a default IP it checks for tftp with before the firmware continue fully booting up the camera.
Click to expand...

I see, thanks for that info. Yet I don't get anything on the TFTP, not even a tried connection from the camera while it's booting. I have a 12V power supply I'm using (which I've tested and it works, camera is powered up just fine with the DHCP IP, etc) and then connecting right to the laptop directly. Laptop port is on 192.168.254.254 and 255.255.0.0 subnet. I've used the TFT server linked in here, as well as another (that I've used before for access point firmwares) and on the latter I've bound the TFTP server to the 192.168.1.254.254 IP. It's listening but doesn't see anything....
 
teredactle said:
I see, thanks for that info. Yet I don't get anything on the TFTP, not even a tried connection from the camera while it's booting. I have a 12V power supply I'm using (which I've tested and it works, camera is powered up just fine with the DHCP IP, etc) and then connecting right to the laptop directly. Laptop port is on 192.168.254.254 and 255.255.0.0 subnet. I've used the TFT server linked in here, as well as another (that I've used before for access point firmwares) and on the latter I've bound the TFTP server to the 192.168.1.254.254 IP. It's listening but doesn't see anything....
Click to expand...

Yah, same here.
 
I've also used a hub to connect both sides (PC and Camera). In the past I ran into an issue updating an access point, by the time the PC ethernet port initiated it would be too late for the AP to connect via TFTP and grab the firmware. I pulled my hair out till someone suggested putting a switch/hub in between them to keep the port in an "active/ready" state.
So I also tried this, but same deal - no action from the camera to the TFTP server.

Curious, what is the firmware your Lorex is running? I.e. mine is this

Device Type LNB8211X
System Version 00007
Build Date 2018-08-16
WEB Version V3.2.1.582554
ONVIF Version 16.12(V2.4.3.574996)
 
teredactle said:
I've also used a hub to connect both sides (PC and Camera). In the past I ran into an issue updating an access point, by the time the PC ethernet port initiated it would be too late for the AP to connect via TFTP and grab the firmware. I pulled my hair out till someone suggested putting a switch/hub in between them to keep the port in an "active/ready" state.
So I also tried this, but same deal - no action from the camera to the TFTP server.

Curious, what is the firmware your Lorex is running? I.e. mine is this

Device Type LNB8211X
System Version 00007
Build Date 2018-08-16
WEB Version V3.2.1.582554
ONVIF Version 16.12(V2.4.3.574996)
Click to expand...

I'm using the same exact version.
 
I called Lorex, gave them the model number and then they told me to download this and upgrade it via the GUI. However it didn't work.
In their email where link was provided, it said for "LNB8973B" which is definitely not the LNB8211/8105. I don't know if the features matter or it's supposed to be for all LNB series, in any case, I got an error and couldn't load it to the camera.... I wrote them back and awaiting a response.

Download LOREX_IPC-HX5X3X-Rhea_Internal_NP_Stream3_V2.640.00LR000.21.R.180929.bin

However, maybe someone needs the version above, the link works for 48 hours I'm told.

Cheers
 
Called back lorex after they sent me the wrong fw link, and was told there is no newer firmware than the 2018 one for the LNB8105 or LNB8211 (same camera). Would much prefer to have the Dahua fw on it.

@val-ipcam any chance you can chime in here considering you were able to flash the Dahua fw on the LNB8105s?? Not sure what we're doing wrong....
 
Hi,
I had camera and laptop connected to the POE switch. Laptop has 2 IP addresses configured on the NIC:
192.168.254.254 subnet mask 255.255.0.0
192.168.1.1 subnet mask 255.255.0.0


Here's the beginning of the camera upgrade log:

U-Boot 2010.06-svn4911 (May 25 2018 - 10:24:57)
I2C: ready
DRAM: 118 MiB
gBootLogPtr:00b80008.
spinor flash ID is 0xc21920c2
oem : set green&red led off(1)
partition file version 2
rootfstype squashfs root /dev/mtdblock5
gParameter[0]:node=bootargs, parameter=console=ttyS0,115200 mem=118M root=/dev/mtdblock5 rootfstype=squashfs init=/linuxrc.
TEXT_BASE:01000000
Net: Detected MACID:00:40:7f:bd:b9:64
PHY:0x001cc816,addr:0x00
s3l phy RTL8201 init

MMC: sdmmc init
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.251; sending through gateway 192.168.1.1
Download Filename 'upgrade_info_7db780a713a4.txt'.
Download to address: 0x5000000
Downloading: *#################################################
done
Bytes transferred = 202 (ca hex)
Using ambarella mac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.251; sending through gateway 192.168.1.1
Download Filename 'romfs-x.squashfs.img'.
Download to address: 0x2000000
Downloading: *#################################################
done
Bytes transferred = 4073720 (3e28f8 hex)


Hope this helps.
 
  • Like
Reactions: mat200
Success!!
Thank you for the instructions TXT file @val-ipcam , and also I appreciate you responding, as I was very frustrated and wasted a lot of time.
@exarkun see below

1) I missed the part about having the 2nd IP (192.168.1.1) - my mistake here!!!

2) For me there was also the problem of the TFTP that was linked in this topic, this was not working for me. I instead used TFTPServerSP V1.6x (which I've used in the past to get OWRT FW onto some Meraki MR42s). This worked and it's more flexible options wise; I edited the INI file to listen on ALL IPs, although I think you can keep your laptop/desktop connected to your regular network and then configure the INI file to only listen to 192.168.254.254 and 192.168.1.1 (I'm guessing here, but should work).

3) It complained there was not success.txt file at the end after grabbing all the IMG files (I extracted ALL the IMG files from the BIN into the root folder of the TFTP server). Well other than grabbing the IMG files and this complaint at the end, it wasn't very verbose, so I didn't know if I should leave it, or reboot it... I left it, saw there was a green light at the front and when I picked it up the alarm went off AHAHAH, thankfully I was in the basement and didn't wake up anyone.

It kept the same login/password as I had before, but instead a nice DAHUA screen, with working live feed (without downloading some stupid plugins). Info still says it's a LNB8211x, but the rest, as you see below.

1663645605658.png

I used a little 8 port hub I bought more than a decade ago, which I kept as it's very handy for such things. Laptop port plugged into it, camera plugged into it, and I used a 12v DC power supply for the camera (again, from Meraki APs).

Cheers!
 
Last edited:
You must log in or register to reply here.
Top Bottom