Recent content by rikochet

Yes hik-connect and EZVIZ appear to use the same backend platform, so you can view your EZVIZ camera in the hik-connect app and you can view your hikvision camera in your EZVIZ app. At least that's my experience anyway..

So I went out and bought a CS-CV248-A0-32WFR (US model) and ripped mtdblock2.. The byte values were: 0x10 = 01 (English) 0x55 = C6 (Brazil) - strange as I bought it in Hong Kong 0X64 = D722 (same as CN) The main things that were different were: 0x1E > 0x23 - Challenge Code 0x35 > 0x3A -...

I'm still trying to figure this out.. If I write the paraBlock from the first CN camera to the second CN camera it connects to the EZVIZ network perfectly.. This isn't a solution as you can't have 2 devices with the same serial registered on the EZVIZ network. It's as if at some point I...

So the current working camera has US firmware and mtdblock2 has the following mods; -- 0x10 = 02 (Chinese) -- 0x55 = 0D (RR region) -- 0x80 -> 0x91 = 43 53 2D 43 56 32 34 38 2D 41 30 2D 33 32 57 46 52 CS-CS248-A0-32WFR (Model string) -- 0x04 & 0x05 = Checksum-16...

Thanks for your clear explanation, it makes perfect sense now! :) After some tinkering I have managed to get the camera connected to the EZVIZ network! - VICTORY! :headbang: I am now trying to replicate the process on a secondary camera, once I have the steps to reproduce I shall publish them...

I've been trying different combinations in the paraBlock but think I am missing something... Could you please be a little more specific by what you mean below? TIA :)

I found this post for a different camera which I believe is not Chinese. So I modified the paraBlock so that the devType was 2a69 and patched mtdblock2 again using your tftp method. The device loads up fine and prtHardInfo reports the new devType. /bin # prtHardInfo Start at 2019-10-12...

You sir, are a magician! The good news! Using tftp I was able to write the modified paraBlock.. There was one slight hiccup in that you had a typo with vmalloc address (should be 0xc2800000) but I was able to locate the correct value quickly thanks to your verbose instructions. :-D The bad...

HKVS # help sf sf - SPI flash sub-system Usage: sf probe [bus:]cs [hz] [mode] - init flash device on given SPI bus and chip select sf read addr offset len - read `len' bytes starting at `offset' to memory at `addr' sf write...

As suggested, I set the bootargs.. dmesg now outputs the following, so I guess the kernel is just appending the string an overriding the u-boot bootargs :facepalm: Kernel command line: mem=38M console=ttyAMA0,115200 init=/bin/sh...

Thanks for this! How do you know the block layout and which bytes to change? Also unfortunately 'ptrHardInfo' is not a valid command. I tried to write the updated block file to mtd however I get a write error.. :( /mnt/mmc01 # cat /mnt/mmc01/mtdblock2_updated > /dev/mtdblock2 cat: write...

I have root ASH access via UART and have installed the US firmware with patched region to CN. Which files should I be live editing?? I managed to locate a copy of @montecrypto repacker, seems to work better than the windows Hiktool - thanks! My linux skills are average, although I have zero...

Hi, TLDR; I have installed US firmware on CN hardware but unable to connect to EZVIZ service. I purchased a couple of C6TC (CS-C6TC-32WFR) IP cams from TaoBao in an attempt to save a few dollars. What I didn't realise was that the cameras are region locked and it requires a Chinese phone...