Hopefully this information has not come too late and will be helpful.
Today I successfully unbricked one of these cameras by using the C341A Flash programmer and program v1.29 to read the MX25L6436F ic removed from a working camera and flashing it to the ic from the bricked camera. The bricked camera kept it's original serial number and MAC address after flashing. I'm not sure if the password and fixed IP address were kept or not as both passwords were originally the same and I didn't keep a note of the original IP address.
I had tried to read the flash rom while it was on the pcb but was unable to. But even after removing the ic the programmer would not read the ic. After a lot of testing, as I initially suspected a fault on the USB programmer pcb after reading some information on the internet, I found that the ic clip was not connecting to the pins of the ic! I had to put the ic further down in the clip before it would connect, which bent the pins. Once I did that it was able to read and write to the ic. Use the Detect option in the program to confirm it is fully connected.
I used Program v1.29 on Windows 7 x64, while Sandboxed, to read and write to the ic. V1.30 read the ic but gave occasional error messages, which may only be because it was Sandboxed. I never tried it un-sandboxed. I only read and flashed the Main memory area of the ic.
I set the program to use the MX25L6436E ic, as the F version was not listed. The E version is identical to the F version but has a smaller Secured memory area. The Secured memory did not appear to have anything in it when I read it but that may be because it is Secured, because it is actually empty or because the program cannot read it as the wrong version, type E instead of F, was selected. Both programs V1.29 and v1.3 don't have the F version listed.
As the bricked camera kept it's original serial number and MAC address I assume they are either stored in the Secured rom area, which I didn't copy or flash, or in the 16Kb flash rom ic, which I didn't try to copy.
I purchased both of these cameras at the end of last year, they are dated 28/8/2017. Both came with firmware version V2.3.4.2103-S50-NTD-B20170508B. I was using them with a HikVision NVR DS-7732NI-SP NVR with firmware v3.4.4, which I believe is the latest firmware. When I first connected the cameras the NVR found them automatically and listed them as Hikvision type. SADP also found the cameras. I found that a later version of firmware was available for the cameras, V2.3.4.2103-S50-NTD-B20170823B, so I updated both cameras using the camera web interface. Both updated correctly but I then found that the NVR and SADAP would no longer find them! But the NVR would find them if set to ONVIF instead of Hikvision.
So I tried re-flashing the previous version of the firmware to one of the cameras, using the camera web interface. About halfway through the flashing the browser said it had lost connection and nothing I did would reconnect to it. I tried using the Product Tool and the Search tool from the SV3C website but neither would find the camera. I found that the Product Tool and the IPSearch programs do not work on Windows 7 x64 when Sandboxed. I didn't try them non Sandboxed. But they do work on XP when Sandboxed. Both found the non bricked camera.
So I opened the camera and soldered wires to the Serial connections and using Putty I got exactly the same boot log as the original poster.
After un-bricking the camera, by flashing the rom with the C341A, I tried using the Product Tool, instead of the web interface, to flash the earlier version of the firmware to see if that would work. While flashing the network led went out for a while but eventually came back on and after a long pause the Product Tool eventually said the flash had been successful. BUT the camera was bricked again and I had to remove the flash rom and reprogram it again!
Before I reflashed the rom again, I used Putty connected to the serial connections and confirmed that the camera had exactly the same boot problems, shown from the Putty log, as when I originally tried to flash it from the web interface.
With the later firmware and with the camera connected to the NVR it now only works in ONVIF mode. It will also not work on the POE ports if the camera is set to DHCP mode. I had to set a fixed IP before the NVR would find it. Although this may be because the NVR still had the settings from when the camera had been connected previously and was getting confused. I have found that moving a camera to a different port can confuse the NVR.
If the camera is connected directly to the LAN the NVR will find it when the camera is set to DHCP mode.
I would like to go back to the earlier firmware V2.3.4.2103-S50-NTD-B20170508B as it worked much better when connected to the NVR and gave far more options. You could set all of the camera settings from the NVR interface, with the later firmware it only works in ONVIF mode and almost no camera settings came be set from the NVR. The earlier firmware version has been removed from the SV3C website but I downloaded a copy before it was removed if you want a copy to look at.
Note that the current SV3C-B01POE-1080 cameras use completely different hardware and firmware. The hardware versions of my cameras are 8700-sc2035 and 8700-sc2135 but both use the same firmware.
