Hahaha, yeah seems common on Android. Funny, Windows programs normally warn you to reboot
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
I deleted the EZVIZ app off iPhone and reinstalled it.
The banner notification is working again.
alexdelprete
Getting comfortable
True, what also is interesting is James has a RCA DB and it is looking for ezviz.dav file.
So looking back on all the firmware's, Nelly's seem to be the only one who has their firmware upgrade/update as digicap.dav in their file. I would assume renaming a firmware to digicap.dav should work, but it is only an assumption.
Also I just noticed Nelly's latest firmware has a March 12, 2020 build date (Under Downloads). Also what is strange is the filename is digicap (2).dav and has a Nov. 10, 2020 date like they just threw in a change (No Chime???)
Does anyone know of the latest build number for Nelly's
3MP Wi-Fi Video Doorbell ONVIF Compliant IP Camera with 2 Way Audio, PIR Motion Sensor, Night Vision, 16GB SD Card Pre-Installed, and 3 Face Plates (NSC-DB2)
Video Doorbell Camera delivering 3MP of crisp clear video Dual Band Wifi (2.4Ghz / 5GHz) to reach all types of routers and wireless access points PIR Motion Detection to detect true human movement. Much less false motion events than standard pixel based motion. Clear Night Vision up to 16' -...www.nellyssecurity.com
The Putty Log File James provided is pretty kewl.
Probably both filenames would work.
alexdelprete
Getting comfortable
Hahaha, yeah seems common on Android. Funny, Windows programs normally warn you to reboot
I never reboot on windows. But you have to know how it works.
Rebooting is the solution when you don't know or you don't have a way to fix things: it doesn't depend on the OS, but mainly it's about the level of knowledge of the platform.
In the case of Android on a phone: reboot is the fastest way.
Last edited:
alexdelprete
Getting comfortable
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
I deleted that post ... I have not fixed chime issue - they are shipping me. replacement DB1 as soon I ship my DB1 back to them.
alexdelprete
Getting comfortable
Yes. When they replaced mine, they sent UPS to collect it and after 5 days UPS delivered the replacement. Everything free of charge.
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
They said I have to pay to have it shipped back because it been over 30 days since I purchased it.
alexdelprete
Getting comfortable
Apparently you missed the fact that it’s running Linux or something of the sort hence why it has uboot. If this is the case then it’s simpler then modifying firmware and is as simple as logging into the device and turning options on by hand.
Dont think so, it might be simpler. I won’t be home for a while so can’t jump into it like he did but great stuff has been found.
Yes changing a 1 to 0 or 0 to 1 but not the firmware. I seriously think it’s this config file he’s talking about
I highly doubt the code is missing. It most likely is just options set in the nvram or config file
Tap a button on your coomputee after the camera boots and see if you get a Linux prompt or a password prompt
This camera could be a ezviz camera which means it has a ezviz bootblock it’s looking for ezviz.dav firmware file to recover the bad firmware would be nice to know if other brands are looking for ezviz or a different file. They all might in fact look for the same file.
Digitap is the unbranded uboot update file but the unattended recovery tools will want to make sure it’s branded
Seriously I think if someone has a dead vdb I would suggest taking a blank se card and putting 2 copies of firmware on it ezviz and digital that sdcatd will most likely recover 90% of dead vdb
James92TSi
n3wb
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.
Last edited:
Makes sense. So I wonder if the cfg also holds the Chime info (Mech./Digital/No Chime)? Maybe those who are experiencing Chime lost needs to wipe this cfgThis 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. View attachment 74705
Question, I know you have your RCA working, do you plan on connecting it to a Chime?
Oh, BTW, these Doorbells are Hikvision cameras, you can see they are Rebrands by RCA, Nelly's, LaView. EZVIZ is a division/company of Hikvision.
You can check out the FCC filings showing the same hardware (Look at Internal Photos):
From the 101:
⦁ FCC Registrations: Search FCC ID Database
FCC ID 2ADTD-DSHD1 3MP Wi-Fi Doorbell Camera by Hangzhou Hikvision Digital Technology Co., Ltd. (Info on Hikvision Doorbell)
FCC ID VIXHSDB2 Video Doorbell by Voxx Accessories Corp. (Info on RCA Doorbell)
FCC ID 2APV2-CSDB1 Wi-Fi Doorbell Camera by Hangzhou Ezviz Software Co., Ltd. (Info on EZVIZ Doorbell)
FCC ID 2APYR-PDB1630 Wi-Fi Doorbell Camera by LaView Eagle-Eye Technology Inc. (Info on LaView Doorbell)
FCC ID 2ADTD-DOORBELL 3MP Wi-Fi Doorbell Camera by Hangzhou Hikvision Digital Technology Co., Ltd. (Info on Nelly's Doorbell)
Last edited: