Jump to content

Recommended Posts

Here's the modified v5.3 CN file, throw that in your "/temp" directory you're using, run hiktool create and see if that works. If it does, double check what you're doing to re-make that file. If it doesn't - something else at fault here; my hiktools is "05r" - perhaps there's a bug in your release?

Sorry for the late reply, I tried your file and it happens exactly the same as with my modifications: the camera is no longer accessible afterwards. Can you please provide me the "05r" version of hiktools as it seems to be no longer available?

 

However I still cannot remake the file. I get the message ; Unable to open dav file' when I execute this:

 

C:\hiktools05R1\hiktools05R1.exe create digicam.dav temp

The "digicam.dav" file you have used for the "split" command is required in the same folder which also contains "hiktools05R1.exe" and the "temp" folder.

Share this post


Link to post
Share on other sites

How to add the files to firmware, I add files and create firmware on hiktools, the web interface "Upgrading failed"

If you type cat / proc / kmsg turns

"<4> [109449.494315] RTL871X: send eapol packet

<5> [110279.805687] UBI: attaching mtd14 to ubi2

<5> [110279.805735] UBI: physical eraseblock size: 131072 bytes (128 KiB)

<5> [110279.805760] UBI: logical eraseblock size: 129024 bytes

<5> [110279.805780] UBI: smallest flash I / O unit: 2048

<5> [110279.805797] UBI: sub-page size: 512

<5> [110279.805816] UBI: VID header offset: 512 (aligned 512)

<5> [110279.805836] UBI: data offset: 2048

<5> [110280.048031] UBI: max. sequence number: 419

<5> [110280.126029] UBI: attached mtd14 to ubi2

<5> [110280.126065] UBI: MTD device name: "app_sec"

<5> [110280.126089] UBI: MTD device size: 24 MiB

<5> [110280.126107] UBI: number of good PEBs: 192

<5> [110280.126123] UBI: number of bad PEBs: 0

<5> [110280.126139] UBI: number of corrupted PEBs: 0

<5> [110280.126156] UBI: max. allowed volumes: 128

<5> [110280.126173] UBI: wear-leveling threshold: 4096

<5> [110280.126190] UBI: number of internal volumes: 1

<5> [110280.126206] UBI: number of user volumes: 1

<5> [110280.126222] UBI: available PEBs: 0

<5> [110280.126239] UBI: total number of reserved PEBs: 192

<5> [110280.126259] UBI: number of PEBs reserved for bad PEB handling: 2

<5> [110280.126279] UBI: max / mean erase counter: 45/42

<5> [110280.126296] UBI: image sequence number: 1845203879

<5> [110280.129179] UBI: background thread "ubi_bgt2d" started, PID 22786

<5> [110282.621125] UBIFS: mounted UBI device 2, volume 0, name "app_sec"

<5> [110282.621208] UBIFS: file system size: 22,837,248 bytes (22302 KiB, 21 MiB, 177 LEBs)

<5> [110282.621246] UBIFS: journal size: 1,161,216 bytes (1134 KiB, 1 MiB, 9 LEBs)

<5> [110282.621276] UBIFS: media format: w4 / r0 (latest is w4 / r0)

<5> [110282.621302] UBIFS: default compressor: lzo

<5> [110282.621328] UBIFS: reserved for root: 1,078,659 bytes (1053 KiB)

<5> [110273.925253] UBIFS: un-mount UBI device 2, volume 0

putty2.JPG.6c77facdf4010480fcca73d5b46aa287.JPG

Share this post


Link to post
Share on other sites
I also don't understand it. The firmware is Chinese for sure: if I delete the "temp" folder containing the extracted image and execute the following commands I get a working image "temp.dav":

hiktools05R1.exe split digicap.dav temp
hiktools05R1.exe create digicap.dav temp

 

If I now add the further step to replace the "IEfile.tar.gz" (even if I just unpack and repack the file) in the temp directory before executing the second command, the TFTP Update will stop at "Completed file [C:\test\digicap.dav] transmit" and the "Device[192.0.0.64] system update completed!" message will never show up.

 

Here's the modified v5.3 CN file, throw that in your "/temp" directory you're using, run hiktool create and see if that works. If it does, double check what you're doing to re-make that file. If it doesn't - something else at fault here; my hiktools is "05r" - perhaps there's a bug in your release?

 

http://www.filedropper.com/iefiletar

 

 

Hi link is not working can you pelase upload again modified iefile.tar.gz ?

Share this post


Link to post
Share on other sites

Good try at restoring 5.3.0 to work like before, but as you have found out and modifications will cause the system to reboot on CRC failure.

 

If you need your camera's to be multi-language like in older version and avoid the miss-match issue.

 

Then use my 5.3.0 to 5.2.5 downgrader.

Share this post


Link to post
Share on other sites

Do you think there would be any way to hack the firmware to change the resolution of the pictures it e-mails out when motion triggered?

 

DVR model number set to record in 1080p:

 

285117_1.jpg

 

Camera model number:

 

285117_2.jpg

 

E-mails out these dinky resolution pictures:

 

285117_3.jpg

 

Let me know please and thanks!

 

-Jamie M.

Share this post


Link to post
Share on other sites
RE: ALL POSTS: Use at own risk. Get ASH back on V5.3 (PSH restrictions)

(Involves TFTP firmware flash process - very much do at own risk)

[*] Edit C:\hiktools05r\temp\initrun.sh with wordpad (turn off line wrap) or your favourite text editor other than notepad (notepad doesn't support unix text file linebreaks) and append "sed -i 's/psh/ash/g' /etc/profile" (without the double quotes) and save.

 

Move files around without scp

PC to Cam

cat [localfile] | ssh root@camip "cat - > [fileoncam]"

Keep It Simple:

ssh root@$camip "sed -i 's/psh/ash/g' /etc/profile"

Enjoy it

Share this post


Link to post
Share on other sites

here is my cross compiled busybox for a DS-2CD2432F-IW. works fine for me.

has anyone managed to get a disk image of the camera that could be used in QEMU? or an easy way to combile the nand partition backups into a workable image?

 

https://drive.google.com/file/d/0B7LZJiQoLpWoU0g1Yl9jUktnTXc/view?usp=sharing

 

# /dav/busybox
BusyBox v1.25.0 (2016-09-05 15:31:18 AEST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
  or: busybox --list[-full]
  or: busybox --install [-s] [DIR]
  or: function [arguments]...

       BusyBox is a multi-call binary that combines many common Unix
       utilities into a single executable.  Most people will create a
       link to busybox for each function they wish to use and BusyBox
       will act like whatever it was invoked as.

Currently defined functions:
       [, [[, acpid, addgroup, adduser, adjtimex, arp, ash, awk, base64, basename, bash, blkdiscard, blkid, blockdev, bunzip2, bzcat, bzip2, cal, cat, catv, chattr, chgrp, chmod, chown, chpasswd,
       chroot, cksum, comm, conspy, cp, cpio, cryptpw, cttyhack, cut, date, dd, delgroup, deluser, depmod, devmem, df, dirname, dmesg, dnsdomainname, du, echo, egrep, env, expand, expr, false, fdisk,
       fgrep, find, free, freeramdisk, fsck, fsync, ftpd, ftpget, ftpput, fuser, getopt, getty, grep, groups, gunzip, gzip, halt, hd, head, hexdump, hostid, hostname, hwclock, i2cdetect, i2cdump,
       i2cget, i2cset, id, ifconfig, init, insmod, ionice, iostat, kill, killall, killall5, klogd, last, less, linux32, linux64, linuxrc, ln, logger, login, logread, losetup, ls, lsattr, lsmod, lsof,
       lspci, lsusb, lzcat, lzma, lzop, lzopcat, makedevs, makemime, md5sum, mdev, mesg, mkdir, mke2fs, mkfifo, mkfs.ext2, mknod, mkpasswd, mkswap, modinfo, modprobe, more, mount, mpstat, mv,
       nanddump, nandwrite, netstat, nice, nsenter, passwd, ping, ping6, pivot_root, pkill, poweroff, ps, pwd, rdate, rdev, readlink, readprofile, realpath, reboot, renice, reset, rev, rm, rmdir,
       rmmod, route, rtcwake, script, scriptreplay, sed, sendmail, setarch, setserial, sh, shuf, sleep, sort, strings, stty, su, sulogin, swapoff, swapon, switch_root, sync, sysctl, syslogd, tail,
       tar, telnet, telnetd, test, time, timeout, top, touch, tr, true, truncate, tty, ttysize, ubiattach, ubidetach, ubimkvol, ubirename, ubirmvol, ubirsvol, ubiupdatevol, uevent, umount, uname,
       unexpand, unlink, unlzma, unlzop, unshare, unxz, unzip, uptime, users, vlock, volname, wall, watch, watchdog, wc, wget, who, whoami, xz, xzcat, yes, zcat

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×