News:

Did you know - Google aren't very nice.  Apparently we're all evil pirates here on OpenIPCam, and they cancelled my adsense account due to that.  Sigh.

Recent Posts

Pages: [1] 2 3 ... 10
1
Firmware / Re: Is there such a thing as OpenNVR firmware?
« Last post by legolad on April 21, 2017, 09:30:28 pm »
Thanks for that. Sadly that's all beyond my skillset, though I do know some EEs who might take it on as a side project.

I was kind of hoping to find that some industrious folks had already started a replacement firmware for one or more of the generic NVRs out there.

Oh well. I guess I need to knuckle down and find an NVR with software that doesn't suck. If you have any recommendations, I'd like to hear them.

Thanks again.
2
Help / Re: How to extract a .OV (extention) firmware file?
« Last post by admin on April 17, 2017, 11:32:08 pm »
First off, you'll need to see what it is internally.

I'd start off with trying to find more info.
Common tools I would use for this are

head  filename.ov | hexdump -C
file filename.ov
strings filename.ov

OSX, Linux have those built in. Windows 10 now has bash/ Ubuntu if you enable it so will have after a bit of work. 
Otherwise a linux live ISO will be fine too.

For dev work, you really want a Mac or Linux box (I'm biased after using Windows for many years and hating it, hehe)

As an example -

Code: [Select]
head configs.zip | hexdump -C
00000000  50 4b 03 04 0a 00 00 00  00 00 30 0f 91 4a 00 00  |PK........0..J..|
00000010  00 00 00 00 00 00 00 00  00 00 08 00 10 00 63 6f  |..............co|
00000020  6e 66 69 67 73 2f 55 58  0c 00 d6 b0 f3 58 8c b0  |nfigs/UX.....X..|
00000030  f3 58 f5 01 14 00 50 4b  03 04 14 00 08 00 08 00  |.X....PK........|
00000040  56 0f 91 4a 00 00 00 00  00 00 00 00 00 00 00 00  |V..J............|
00000050  11 00 10 00 63 6f 6e 66  69 67 73 2f 2e 44 53 5f  |....configs/.DS_|
00000060  53 74 6f 72 65 55 58 0c  00 d3 b0 f3 58 d3 b0 f3  |StoreUX.....X...|
00000070  58 f5 01 14 00 ed 98 c1  6a c2 40 10 86 ff 89 39  |X.......j.@....9|
00000080  04 0a 65 8f 3d ee 13 48  b5 82 7a 5b 42 7c 82 be  |..e.=..H..z[B|..|
00000090  40 69 3d 0a 1e a4 f7 9c  7c ae 3e 9a 1b e6 b7 0a  |@i=.....|.>.....|
000000a0  31 62 4f 96 f6 ff 60 f8  20 99 99 24 97 dd 9d 00  |1bO...`. ..$....|


You'll see that my file starts with PK, so mine is a zip file (as phil katz invented zip, so zip files use his PK header, more history on that here  - https://en.wikipedia.org/wiki/Phil_Katz).

file will also tell me that though -
 
Code: [Select]
file configs.zip
configs.zip: Zip archive data, at least v1.0 to extract

For your OV file, you'll need to look at the header, and see if its a standard format, or its a custom format.
Its more likely to be a custom format.  Typically those will have a header with where bits are in the file, and filesize, and maybe crc's.
If you're really unlucky, its also sha1 or similar encryption on the file data.

I've written about decoding custom format files before on here, look through some of my posts on that, or on my http://www.computersolutions.cn/blog under firmware ( http://www.computersolutions.cn/blog/?s=firmware )

If you post the output from  head yourovfile.ov | hexdump -C here I can take a cursory look and tell you which its likely to be.

3
Nice!
4
Firmware / Re: Is there such a thing as OpenNVR firmware?
« Last post by admin on April 17, 2017, 10:06:25 pm »
Not really (opennvr firmware)

What you'll need to do is get hold of the SDK for the chipset, so that you can compile a kernel and app's.
Once you have that, then you can start building firmware and flash.

Issues are that not all hardware is identical, so you will have different NAND types, flash sizes, gpio usage etc.
Not insurmountable, but you'll generally want to pick the same hardware to develop, and port to.

The SDK for the HI3615C is here - http://pan.baidu.com/s/1o8TWZ0Y----

Let me know if you have problems downloading, I can put elsewhere.

Generally speaking, you'll want to open up whatever hardware you have.  Add serial headers, and connect up serial for minimal debugging, and for more serious stuff JTAG.  Boot up the hardware, and see what it tells you.  Hopefully you'll be able to see a boot log and bootloader, and communicate with it.

Developing with just serial is viable though if the hardware isn't too locked.
i.e. hopefully the device will have an accessible bootloader, then you can flash kernels and filesystems without too many headaches.

The flash will generally contain a bootloader (don't overwrite this, otherwise you'll need to use an SPI flasher or similar to rewrite).
The bootloader will load a kernel from the flash into ram, then execute it.
The kernel will then mount a filesystem from flash, and run the OS + programs.

A BSP or SDK allows you to build a kernel and programs (BSP = board support package.  SDK = software development kit).

Thats a brief overview.
5
Help / How to extract a .OV (extention) firmware file?
« Last post by G33RT on April 17, 2017, 12:24:07 pm »
Hi,

Does someone knows how to extract a .OV (extention) firmware file?

Any help on this is welcome!
6
Firmware / [REQUEST] Firmware for IPCC-B13L 960P 1.3MP (Hi3518 + AR0130)
« Last post by G33RT on April 15, 2017, 02:09:15 pm »
Hello,

I'm looking for the firmware of an IPCC-B13L 960P 1.3MP (Hi3518 + AR0130).
The manufacturer does not have the firmware for this camera at their support page.

The camera has two boards, one with the Hi3518 chip and one with the CCD sensor and schould be an Aptiva AR0130 CCD sensor.

The CCD board have the description: CCD_CAM_8M-142(A)
After searching I can not find anything about CCD CAM 8M-142.

At WebIF I could see Hard Ver: 7100-ar0130_960P
The firmware I had on this was: V2.0.6.1-X20-Build:20130928D

I have bricked the camera due to flashing a wrong firmware :-[

Does anybody knows if the whole firmware is located in the flash chip 25L12835F ?

Any help is welcome!
7
Firmware / Is there such a thing as OpenNVR firmware?
« Last post by legolad on April 10, 2017, 03:47:22 pm »
Hey folks,

I'm relatively new to this IPCam world and thanks to all of you I've managed to answer most of my questions.

I do still have a couple of questions that I'm hoping you can help with.

Question 1:
I recently picked up a few of the cheap chinese IPCams that are running this firmware:
V4.02.R11.00002520.10010.244000.00000
They have an internal ID of H264 50H20L_S39.

Based on what I've read in these forums and others, I believe this means they are running the HI3516C System on a Chip. Can any of you confirm this?

Question 2:
I see that we have an open source camera firmware available. Is anyone working on an open source NVR firmware?

I'm specifically thinking that it would be great if we had firmware that supported these generic NVR boxes out of China. For example, firmware that supports the HI3535 chip would be pretty good for someone like me who just wants a a few cameras at 1080p.

For me, I'm less concerned about people viewing my cams and more concerned about opening a back door into my home network. Having an open source firmware that is known to be secure and not part of some bot army might alleviate some of the worries many people seem to have regarding the security of these generic NVRs.

And yes, I realize I can double or triple my budget and get a better NVR. I might just do that. But first I wanted to understand what the minimum viable setup looks like.


8
Hacking & Modding / Re: Hacking the F19821 W V2 to control an Arduino Tank Rover
« Last post by nars on April 08, 2017, 09:09:49 am »
Sorry to bump this old topic, but I'm looking at how to repack firmware as well... after research theoretically I know how to do it but I didn't try it yet... would like to ask if you ever succeed doing it? Also did you update md5 for the jffs2 image on fwupgrade.md5 file? (by looking at the firmwareupdate binary apparently it does an md5sum -c to check integrity...)

Also, if you used mtdram... after mounting the jffs2 image and applying you changes... did you then unmount it and created new image file with the updates (dd back from mtdblock...)?
9
Hi krokos.

How did you copy files into cam?
My IP cam 8ELP 720p) has the same SoC but I apparently I haven't any transfer service like telnet or SSH.
But I have ftp.
Any idea how entering into its shell?

tnx
10
Hacking & Modding / Re: hacking ELP 720p cam
« Last post by cris.alberti on April 07, 2017, 09:43:58 am »
Here's the fw.

First of all I've used 7z to unpack the original bin file and here the files inside:

custom-x.cramfs.img
Install
InstallDesc
romfs-x.cramfs.img (with the pwd and system files)
u-boot.bin.img
u-boot.env.img
user-x.cramfs.img
web-x.cramfs.img

The following steps are the same for each file.

$ xxd -a custom-x.cramfs.img | head

00000000: 2705 1956 2654 4b3f 5761 3b3d 0000 7000  '..V&TK?Wa;=..p.
00000010: 0077 0000 007b 0000 be2a 4cf4 0502 0101  .w...{...*L.....
00000020: 6c69 6e75 7800 0000 0000 0000 0000 0000  linux...........
00000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000040: 453d cd28 0070 0000 0300 0000 0000 0000  E=.(.p..........
00000050: 436f 6d70 7265 7373 6564 2052 4f4d 4653  Compressed ROMFS
00000060: 122d e489 0000 0000 2e00 0000 2900 0000  .-..........)...
00000070: 436f 6d70 7265 7373 6564 0000 0000 0000  Compressed......
00000080: fd41 1402 5800 0014 c004 0000 ed41 1402  .A..X........A..
00000090: 7400 0014 430a 0000 4375 7374 6f6d 436f  t...C...CustomCo

$ binwalk custom-x.cramfs.img

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0                      0x0                         uImage header, header size: 64 bytes, header CRC: 0x26544B3F, created: 2016-06-15 11:25:49, image size: 28672 bytes, Data Address: 0x770000, Entry Point: 0x7B0000, data CRC: 0xBE2A4CF4, OS: Linux, CPU: ARM, image type: Standalone Program, compression type: gzip, image name: "linux"
64                   0x40                       CramFS filesystem, little endian, size: 28672 version 2 sorted_dirs CRC 0x89E42D12, edition 0, 46 blocks, 41 files


$ fdisk -l custom-x.cramfs.img

Disk custom-x.cramfs.img: 28 KiB, 28672 bytes, 56 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

$ dd if= custom-x.cramfs.img bs=64 skip=1 of=fs.custom

Now is ready to be opend with 7z and browsing in.

Into the fw (the romfs-x.cramfs.img  file) I've found two pwd files: passwd and passwd-
And after John's care:

 ./john --devices=0  --single  passwd

Apparently I've two system (?) credentials: root1919.....root1900
                                            root1907.....root1900

But I cannot enter into shell.

What can I do?

Tnx in advance for any reply.

Pages: [1] 2 3 ... 10