alexdelprete
Getting comfortable
This is definitely an RCA camera - received in full RCA packaging, and it's an RCA faceplate (oval camera lens rather than circular like ezviz). The auto-recovery routine is checking for ezviz.dav though. When bootloader is interrupted via CTRL+U, the update command looks for digicap.dav.
It may have been possible to recover this doorbell by placing a firmware file named ezviz.dav on the sdcard and possibly doing some press of the reset button that causes it to wipe the config (if there is a reset button sequence that can make it wipe the config - I don't think we really know that).
Do note that I first flashed the firmware using update, and the doorbell was still bricked at that point, because writing firmware doesn't dump the config (see screenshot below). The info I had from previous owner is that he was changing wireless network config when it bricked. Something was definitely messed up in the config. But hey that's how I got it for 50 bucks shipped and started on this science project....
Only once I issued the format command (which erases everything but bootloader) followed by the update command did it unbrick.
It makes sense that updating firmware doesn't drop the config - this is how the DB stays setup for your network, phone app account, etc. through firmware changes.
This is from page 23 of the Putty log file on my previous post - when I did format followed by update. Notice the format command wipes the config area, while the firmware update doesn't touch it.
It would be great to have that log while pressing the physical reset button on the camera, to see if it resets the whole config like the format command or not. I think it doesn't. But probably there's a procedure to do it that is undocumented.