Special Request

KCulver said:
Having some difficulty following the logic. Where do the tools like command.bat have to reside? In the root directory of the PC? Thanks.
Click to expand...
I don't understand the question?
Just extract the zip file, .bat files are fine how they are.
Then you need to extract your cameras firmware.bin into the root folder so you have the .img files in the root folder.
Running Commands.bat reads the commands.txt and generates the upgrade_info.txt file which is then placed in the root folder.
 
cor35vet said:
I don't understand the question?
Just extract the zip file, .bat files are fine how they are.
Then you need to extract your cameras firmware.bin into the root folder so you have the .img files in the root folder.
Running Commands.bat reads the commands.txt and generates the upgrade_info.txt file which is then placed in the root folder.
Click to expand...

Got it! Thanks.
 
Are you sure your network is set up correctly? aka. you added 192.168.254.254 ?
Else you can replace 192.168.254.254 with 0.0.0.0 to listen on all interfaces.
Or: ncat.exe -v -u -l -p 5002 should work too
 
KCulver said:
Gave this a try and it looks like all commands completed except the console.bat file and this is the error I got. Any ideas where I went wrong?






View attachment 15533
Click to expand...
cor35vet said:
Are you sure your network is set up correctly? aka. you added 192.168.254.254 ?
Else you can replace 192.168.254.254 with 0.0.0.0 to listen on all interfaces.
Or: ncat.exe -v -u -l -p 5002 should work too
Click to expand...

I did add 192.168.254.254. I double checked the network settings and everything looked correct. I'll try these two alternatives. Thanks.
 
KCulver said:
I did add 192.168.254.254. I double checked the network settings and everything looked correct. I'll try these two alternatives. Thanks.
Click to expand...

I found my mistake - I had entered 192.168.254.254. as gateway address and not IP address. Now I get this ...
Capture.JPG

This is what is in my root.

upload_2017-2-25_8-28-41.png
All I have done is run the commands.bat file. You had sent me a link to the latest firmware file and I put that in root. This is all I need to do right?
 
That looks like firmware from the english/international dahua wiki.
Do you have an international model? Then it should be okay, start the TFTPServer.bat and powercycle your camera.

Commands.bat only generates the upgrade_info.txt file from commands.txt.
You need to write the commands.txt yourself, however for your camera the default one should work.

If you have a chinese model you need to use patched firmware, I made one for SD-Zi-Themis before:
https://i.botox.bz/DH_SD-Zi-Themis_Eng_P_Stream3_IVS_V2.400.0000.16.R.20160517.zip
 
cor35vet said:
That looks like firmware from the english/international dahua wiki.
Do you have an international model? Then it should be okay, start the TFTPServer.bat and powercycle your camera.

Commands.bat only generates the upgrade_info.txt file from commands.txt.
You need to write the commands.txt yourself, however for your camera the default one should work.

If you have a chinese model you need to use patched firmware, I made one for SD-Zi-Themis before:
https://i.botox.bz/DH_SD-Zi-Themis_Eng_P_Stream3_IVS_V2.400.0000.16.R.20160517.zip
Click to expand...

Hopefully I am closer! if I understood you correctly, It was not necessary for me to write my own commands.txt as i could just use the default. After starting TFTPserver.bat and power cycling the camera, this is what I get:

upload_2017-2-25_9-8-39.png
 
the tftpserver is failing to listen on 192.168.254.254 port 69.
Try to start it as admin
 
cor35vet said:
the tftpserver is failing to listen on 192.168.254.254 port 69.
Try to start it as admin
Click to expand...

I ran as admin before but double checked and the results are the same. Port 69 bind failed. My PC is connected to a switch and the Camera is connected to the same switch. These are the only devices on the switch. Also, no data activity on the switch at the camera connection. I also did power cycle the camera.
 
KCulver said:
I ran as admin before but double checked and the results are the same. Port 69 bind failed. My PC is connected to a switch and the Camera is connected to the same switch. These are the only devices on the switch. Also, no data activity on the switch at the camera connection. I also did power cycle the camera.
Click to expand...
It has nothing to do with the physical network, the application is not able to bind on the requested address.
So either something is already listening on that address, the address doesn't exist (though netcat apparently can listen on it so it does), you have no permission to bind on that port (<1024 requires admin on linux no idea about windows)
or god knows what. In either case it's a software issue.
Try rebooting or use another computer/laptop?

Actually, did it ask you about the windows firewall crap, and did you allow it on all interfaces?
 
cor35vet said:
It has nothing to do with the physical network, the application is not able to bind on the requested address.
So either something is already listening on that address, the address doesn't exist (though netcat apparently can listen on it so it does), you have no permission to bind on that port (<1024 requires admin on linux no idea about windows)
or god knows what. In either case it's a software issue.
Try rebooting or use another computer/laptop?

Actually, did it ask you about the windows firewall crap, and did you allow it on all interfaces?
Click to expand...

solarwinds was using port 69 so i stopped it which corrected the bind error. now i am getting listening on 192.168.254.254:69

just wanted to update you where i was. i've bothered you enough and many thanks for your help. i'll keep trying and will let you know if successful. do you have a paypal....would like to donate a 6 pack! lol...
 
  • Like
Reactions: cor35vet
Nice, so did you get it running yet?
My paypal is paypal.me/BotoX
 
cor35vet said:
Nice, so did you get it running yet?
My paypal is paypal.me/BotoX
Click to expand...
No luck getting it to run but looks much more promising. No errors and now listening on 192.168.254.254:69. Going to go over eveything again and backtrack a bit from scratch. :)
 
neverever said:
I have used the firmware from cor35vet to upgrade my Chinese cameras (Dahua H2.65 IPC-HDW4431C-A) and it has been working very good so far.
Better than the modified original one.
Is it a risk that the cameras can be bricked later under any circumstances according to what cor35vet wrote:
"Dahua purposely put an almost immediate reboot into their software when it detects english language on a chinese region model."
Click to expand...
@cor35vet which firmware file was this? I should be receiving some of the same IPC-HDW4431C-A cameras in a week or so and want to insure they have more recent firmware, as they are probably older stock being clearanced.
 
nayr said:
Dont go updating firmware just because you find a firmware file and you wont ever find your self in the situation where you need to perform a recovery because of a botched upgrade.

If its not broken; then it dont need fixing.. people just cant leave well enough alone.

If your having issues that you know have been resolved in a newer firmware; and those issues are show-stopping issues.. then its already broken, and you have a justification for the risk involved.
Click to expand...

Also let people who know how to do all of the crazy and advanced unbricking methods try out the firmware upgrades once they confirm it won't brick your camera then go for it, I never do a firmware upgrade unless there is a good reason AND a few other people have tried it without any issues.
 
VorlonFrog said:
@cor35vet which firmware file was this? I should be receiving some of the same IPC-HDW4431C-A cameras in a week or so and want to insure they have more recent firmware, as they are probably older stock being clearanced.
Click to expand...
HDW4431C-A is Eos, see Dahua Firmware Mod Kit + Modded Dahua Firmware

hmjgriffon said:
Also let people who know how to do all of the crazy and advanced unbricking methods try out the firmware upgrades once they confirm it won't brick your camera then go for it, I never do a firmware upgrade unless there is a good reason AND a few other people have tried it without any issues.
Click to expand...
Pretty easy to unbrick cameras with TFTP, if you are up for some fun why not?
You also update your computer regularly even though there probably isn't anything wrong. Or do you not?
 
cor35vet said:
HDW4431C-A is Eos, see Dahua Firmware Mod Kit + Modded Dahua Firmware


Pretty easy to unbrick cameras with TFTP, if you are up for some fun why not?
You also update your computer regularly even though there probably isn't anything wrong. Or do you not?
Click to expand...

Sure, IF your camera isn't so fucked up that you can do TFTP, if you get to the point where you are having to solder JTAG connectors onto it and stuff, not everyone wants to do all that. Typically if my computer borks itself I can reinstall the OS and be back up in 10 minutes. All depends on the situation, do I want to risk bricking one of my in production security cameras? Not really, or any camera I paid a couple hundred bucks for not long ago, nah, if its a camera someone gave me, or is old and junk anyways, sure why not lol.
 
You must log in or register to reply here.
Top Bottom