Search results

@mastec if you open the .bin7 file with 7zip you should be able to extract it's contents and inside there should be the .img files you need (there are many) do you also have the SFTP setup to be able to upload the files? @nikos1671 try seeing if uboot has a "help" variation activated, your...

If you go up in firmware then the GUI is the safe way, it should check if it's compatible or not. I'm not sure of the exact model of camera but if there are many versions of the firmware in between maybe skip 5 at a time before getting to the latest, I see no reason not to use the latest but...

Can you access it from the GUI at 192.168.1.108? Success.txt means that it worked, if it's still not accessible then something else might have gone on as I also am not sure why the "Read Request, File: failed.txt" exists if it succeeded? Would suggest to ensure you shut down the TFTP as soon...

There are a few things I could suggest, Some firmware need the tftp line to be 0x0800000 or 0x02000000 instead of 0x82000000 depending on the size of the RAM on the device, I don't think it's an issue due to the upgrade failing after Web-X being served instead of the PD and DC. I suspect...

If the TFTP server loads up then you may not have to change the uboot, BUT you may have to do some work to reset all the enviroment variables to match the correct settings for the correct model. You may also not have the right tools if the HX5XXX uses different memory or flash then the HX5X3X...

It's been encountered before that at some point Dahua ran out of space on some of the partitions and realigned the partition boundaries. During a web upgrade it upgrades and aligns properly but during a TFTP flash it doesn't update the partition pointers so it actually overwrites portions...

I recall there being a thread that talks about using an external programmer but I don't have a link to it handy, it was something I came across while researching my own problem, It's not a very convenient process and requires getting the write programmer for the right type of chip on your...

Based on the other thread you should be able to do a TFTP recovery by installing the firmware again over TFTP, but you can also try using telnet since that seems to be open to you, with telnet you need to add "7ujMko0" (without the quotes) before the password you used example: Web login...

Are you able to setup a scenario where you have a TFTP server running on a machine with 192.168.254.254 netmask /24 or 255.255.255.0 and a gateway at 192.168.1.1 netmask /24 or 255.255.255.0. Preferably it's a windows machine and you can just use the tftp server and console.bat files from the...

By console I mean the console (Ncat) that is included in the TFTP (Click the link or check page one of this thread) package on this site, it reads the output from from the camera over the network during the tftp and displays the results. It also has the batch file needed to generate the proper...

If it is responding to the network, I would suggest going the TFTP route, the arp for 192.168.1.1 is indicative of it looking for the gateway to contact 192.168.254.254. You can run most of the serial commands though the TFTP load file and view the output in the console, and while it doesn't...

The only suggestion I can think of at this point would be to see if you can get kermit or another file server running on the host computer and see if when the camera boots it tries to initiate a binary transfer over serial. There is a slight chance it will either pull or accept a boot image...

If you can let us know what commands you tried it might help in letting us troubleshoot if your still interested, the whole NAND doesn't seem wiped since the minboot is there, but the uboot partition seems to be. What did you try between the last time you rebooted the camera and when it...

Ubiquiti i would recommend.... Reolink..... eh not really Dahau did remove the need for plugins for the browser, and I personally find the firmware easy to find and the new versions have a build in update checker on the camera's interface (it's still a little hit or miss but does work) Sorry...

Did you flash the boot loader? That would indicate that the bootloader kernel does not match the required version, the good news is the serial works so likely u-boot-min is still intact to do an initial load, the bad news is that I'm not sure what and how to work with it, perhaps someone more...

When you connect it to serial are you getting any input? I find that I have to mash * the moment I connect power to the camera to get it to jump into the boot loader. Do you get a network link when it's plugged in? do you see any activity over the link?

It shouldn't be completely bricked unless you overwrote the bootloader, if you can still get a serial console you can TFTP back the latest firmware, uboot magic might indicate that you flashed an older version that the bootloader doesn't support. But the boot loader itself should still boot...

If there is a sticker on the unit you can check then can verify on that, if you are absolutely sure that it's the right camera you can try updating the boot loader...... But if that goes wrong you can't go back (without physically accessing the camera and programming the chip with specialized...

I don't think that will work still, are you sure you have the right model for the camera? 2.422.0000 still has web, 0, 0x0000000001a00000, 0x0000000000800000, RW in the partition table and your camera is expecting web, 0, 0x0000000001600000...

Yes you need the upgrade_info_7db780a713a4.txt as that is the secret file generated by command.bat (Based on the contents of command.txt) that tells the camera what to do over TFTP. unknown core,use back can also indicate that you've flashed the wrong firmware, can you confirm what file you've...

Client 192.168.1.108:3827 root\success.txt, File not found or No Access That would indicate that the flash was a success, if you shutdown the TFTP server at that time the camera should boot normally. fail to load bootargsParameters.txt fail to load bootargsParameters.txt file get bootargs info...

Create a success.txt and failed.txt file in the root directory of tftp server, see if it downloads either of those. You should be getting one or the other to indicate if the process succeeded or failed, aside from that one line that stands out is: amb_nand_read_oob read page:49152 err That...

Right now it's on a evaluation copy of Server 2019. Issue existed before I bound the network nic's, binding them was one of the steps I did during troubleshooting. Since it's working when the master is set to limit decoding and the clone set to decode for motion I doubt it's network related...

I can confirm it was properly cloned, the clones have/had 0 bitrate and the same FPS as the master. When I had "limit decoding unless required" unchecked on both the master and clone it would create the above issue, when I have it only unchecked on the clone (Since I believe it's required for...

So I think I'm onto something here: I increased the buffer to 40MB, no real change Changed profile from Genertic RTSP/ONVIF to Dahua Mainstream, no change Changed the main 24/7 recording to "Limit decoding unless necessary" and now the streams are pulling ~15fps So there seems to be an issue...

Ouch!, Yup it's the soy and a lot of cars use plant based plastics now too for the wiring. I wouldn't be surprised at the bench grinder.... The squirrels here are sharpening their teeth on the roofing shingles. I think anything that has an abrasive edge and they go for it.

If it's outdoors I would strongly suggest conduit and mounts unless you are able to feed everything from inside without anything exposed. I have 6 Cameras, 5 that I have installed using conduit (3/4 as 4 camera's feed back through the same conduit) and a 2 gang outlet box with weatherproof...

Problem still occurs with acceleration disabled, it was one of the reasons I added the GPU in thinking it was a CPU load issue. Codec is the H.264H codec, not with smart codec turned off. Between the working camera and the non working ones I checked again and all settings are identical both in...

Can confirm that RTSP is being received without error as well, When I Change the decoder on the camera it works perfectly for about 10 seconds then starts to stutter again. I do have one camera (The first camera I've added) that is working perfectly, recording and receiving all frames and I...

The jumping occurs when watching live view or recorded clips no matter how many times watched both through BI and UI3 as well as when the clips are exported and I watch on the desktop. Server isn't completely headless as there is a monitor connected to it however it is off most of the time and I...