Electronics > Repair

Swann DVR (security camera recorder) bricked after firmware update (Fixed)

(1/18) > >>

I have a Swann DVR model swdvr-44000H / DVR4-4000 that I found a firmware update from this link: https://www.swann.com/downloads/drivers/DVR_4000/GA1.9/ I selected the DVR4-4000_GA1.9_1025.pak file and it updated and booted normally.  I then found by going back a link and to this link: https://www.swann.com/downloads/drivers/DVR_4000/GA2.0/ a newer (or what I thought) version of the firmware here DVR4-4000.0118.759.676.10.2.nor.sw.S300.pak and it installed but when the unit rebooted it never fully booted up (no screen output and the blue remote activity indicator light on the front never de illuminated).  What would I have to do to unbrick the unit?  I did find it a bit odd with the first successful firmware update that the USB drive that I used to install the update with was giving me an error about unable to mount the file system and I had to use another one to install the (newer) update that bricked the unit.  The motherboard has the markings TCBB02 V140 2012-04-07 and the sub board with the CPU on it has these markings TCCB01_V110 2012-03-09.  I think this unit runs Linux but I am unsure.  Can send pictures if needed.

I accidentally bricked a dsl modem/router/w-wireless.  spent many calls / time trying to undo with company, no luck.  It's good for australia, canada and maybe others - ebay item :-//.  The wireless I think I can get to work with my network, have not tried.  sitting on the shelve for the last several years.

Well I found the serial port and all I get out of it is a repeating string of CCCC's.  I think the uboot firmware has been bricked.  Is there any way to use an Arduino UNO to fix the NAND flash by writing to it?

CCCC is typically the ROM bootloader testing the line, so an external host can  respond and perform a serial boot. Depending on the device on the board, there is a chance its manufacturer will have the procedure documented somewhere. Then, locate a valid firmware (probably a
.bin file) then there is a chance the box will boot normally.

If this is a linux-based device, you will probably need to check the status of the flash before the kernel boots - you need to halt at the u-boot phase to erase and write flash, etc. But at this point anything is heavily dependent on the device in question.

If you can locate the chip that holds the firmware and have a way of reading/writing it, you may be able to fix this.


[0] Message Index

[#] Next page

There was an error while thanking
Go to full version