If they are going to fix this then also substream 2 being disabled on restart, if that could also be fixed
I just upgraded 2 of my 5231-ze cams, things to note:
1) For both of the cams that I tested this on, the first time I tried the upgrade, it seemed to go through the steps but then within 10-15 seconds it rebooted the cam. On logging on to the cam the firmware was still the old version. So I did it again and this time I saw the upgrade progress bar and the cam updated as expected. No idea why it seemed to not perform the update on the first attempt, can only surmise that maybe it was preparing the cam for the upgrade?
2) Substream 1 and 2 settings are maintained after a restart, on the previous version of the firmware, substream 2 would always be disabled and substream 1 would always be set back to default values.
3) On some versions of the previous firmware the Video Detection option would get re-enabled after a restart which would cause havoc with my IVS rules as it would trigger the cams on any motion. With this version of the firmware the Video Detection setting is also maintain after a restart.
All in all I'm very happy with this version of the firmware and all the bugs that I had previously reported have been fixed
Going to leave this running on the 2 cams for a few days before committing to updating my other 5231-ze cams.
EDIT: Forgot to thank Andy for the update
Hoping somebody can help me out with my attempts to flash my Amcrest IP5M-T1179EW to Dahua IPC-HDW2531TP-AS firmware. I am hoping to enable some of the IVS functions but haven't had any luck with changing the firmware.
I tried the "DH_IPC-HX25(8)XX-Molec_MultiLang_NP_V2.800.0000000.19.R.200628" firmware everyone seems to have success with, as well as a number of other firmware bins listed for this camera. None of them worked using the GUI console or the ConfigTool, except for the "Amcrest_IPC-HX25(8)XX-Molec_Eng_N_AMCREST_V2.800.00AC001.0.R.201230" firmware.
I checked the system info and get the following:
appAutoStart=true
deviceType=IP5M-T1179E
hardwareVersion=1.00
processor=SSC328Q
serialNumber=AMC060F2**
updateSerial=IPC-HDW2531TP-AS
updateSerialCloudUpgrade=IPC-HDW2531TP-AS:01:02:02:7C:3D:00:01:10:01:00:04:400:00:00:00:00:00:01:00:00:100
The updateSerialCloudUpgrade is the same as HWID @pozzello posted back on post #84, so I figured it was the same hardware. However after having no luck I turned to the TFTP method and tried to run "printenv" by using the following commands.txt instructions:
printenv
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5
The console window output is below but it indicates that the "cmd: (printenv) is not support! ".
Ncat: Version 7.40 ( Ncat - Netcat for the 21st Century )
Ncat: Listening on 192.168.254.254:5002
gBootLogPtr:20b80008.
NAND: SPINAND: _MDrv_SPINAND_GET_INFO:error, Found SPINAND INFO
(0xEF) (0xAA) (0x21)
SPINAND: board_nand_init:error, CIS contains part info
128 MiB
partition file version 2
rootfstype squashfs root /dev/mtdblock12
partition file version 2
rootfstype squashfs root /dev/mtdblock12
gParameter[0]:node=bootargs, parameter=mem=260096K console=ttyS0,115200 root=/dev/mtdblock12 rootfstype=squashfs LX_MEM=0xFE00000 mma_heap=mma_heap_name0,miu=0,sz=0x84B4000.
gParameter[1]:node=upgradeMode, parameter=switchBootPart=1.
In: serial
Out: serial
Err: serial
TEXT_BASE:21000000
Net: fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
MAC Address 9C:8E:CD:::**
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
MMC: DGS info:start addr=0x2fd7c000
dgsBufStart:0x2fd7c000
partition file version 2
rootfstype squashfs root /dev/mtdblock12
dgs offset:0x500000 size:0x100000
[DGS]:dgs_BootCreate
[DGS]:readPtrC:0 writePtr:0 covered:0
[DGS]:dgs_BootCreate end
Invalid addr 0x23000000, the fixed default addr is 0x22000000
MDrv_EMAC_start
RBQP_BASE=0x21080000
Using sstar_emac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.251; sending through gateway 192.168.1.1Download Filename 'upgrade_info_7db780a713a4.txt'.Download to address: 0x22000000
Downloading: *
done
Bytes transferred = 126 (7e hex)
disable wdt
string value is 0
The end of file
cmd
Invalid addr 0x82000000, the fixed default addr is 0x22000000
MDrv_EMAC_start
RBQP_BASE=0x21080000
Using sstar_emac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.251; sending through gateway 192.168.1.1Download Filename '.FLASHING_DONE_STOP_TFTP_NOW'.Download to address: 0x22000000
Downloading: #
done
cmd
partition file version 2
rootfstype squashfs root /dev/mtdblock12
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
cmdLine mem=260096K root=/dev/mtdblock12 rootfstype=squashfs LX_MEM=0xFE00000 mma_heap=mma_heap_name0,miu=0,sz=0x84B4000
MDrv_EMAC_start
RBQP_BASE=0x21080000
Does anyone any any ideas as to what the heck is going on? I'm stumped and don't understand if I am doing something wrong or the camera is just locked out somehow. I did a port scan on the camera and only have ports 80, 554, 1935, & 37777 opened, so I can't telnet or SSH into it. With the Amcrest firmware it is working fine, just without the IVS functions.
Thanks in advance for any assistance.
EDITED: To reduce size using Spoiler.
UPDATE: Problem solved, well at least I was able to flash my camera and update the firmware. Posting this to help anyone else with the same problem.
I realized that I was having problems extracting my .bin files since I was not changing the files to .zip after editing the first two bytes. I was then able to open the Install and HWID files. Confirmed the hardware ID was correct based on my system info data above. Then used the install file to make the following commands.txt.
tftp 0x82000000 partition-x.cramfs.img; flwrite
tftp 0x82000000 kernel.img; flwrite
tftp 0x82000000 romfs-x.squashfs.img; flwrite
tftp 0x82000000 web-x.squashfs.img; flwrite
tftp 0x82000000 .FLASHING_DONE_STOP_TFTP_NOW
sleep 5
After flashing using the TFTP method, I was able to get into the camera but none of the menus would open or display. I then went to the ConfigTool and the able to reflash using the original .bin file. Now the camera is fully operational and updated to Dahua firmware. I used the newest firmware General_IPC-HX25(8)XX-Molec_MultiLang_NP_V2.800.0000000.24.R.201014 found on the Dahua site for the IPC-HDW2531TP-AS camera. Hopefully this can help someone else.
Thank you all for all the great information in this thread and on this site!
Priceless - "others (Firmware) all Abandoned" - Andy you make it sound like people wanted to stay on v16! - Andy you must be joking!
