support for this firmware V380^AK3918EV200W^EV2W_VA3^1.3.7.0 #86
Replies: 11 comments 42 replies
|
All that's required with the update is to find out the camera code. Although they might send an incorrect match, not for your camera. I previously looked at the file inside the zip file in a text editor. It looks like your camera code is EV2W_VA3. |
|
alright :)
Sent from [Proton Mail](https://proton.me/mail/home) for Android.
…-------- Original Message --------
On Wednesday, 02/25/26 at 11:01 Arkady ***@***.***> wrote:
I'll have a look a little later. I'm not at home.
—
Reply to this email directly, [view it on GitHub](#86 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AUSD2DUVQAFBVOFUXUB64JD4NUNB7AVCNFSM6AAAAACV5XSNOSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJRHA2TIOI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Я вам приготовил патч, который должен сделать копию конфигурации на sd-карту. То что внутри zip поместите на sd и включите камеру. Патч должен отработать и на sd появится архив. Пришлите его на email a@kornienko.ru. Я проанализирую и дальше сделаю установочный патч. |
|
okay I'll try soon
Sent from [Proton Mail](https://proton.me/mail/home) for Android.
…-------- Original Message --------
On Friday, 02/27/26 at 03:42 Arkady ***@***.***> wrote:
There's another telnet connection on port 4322. This was suggested in a related thread. This is the last thing we can try to get telnet on port 4322.
[EV2W_VA3_telnet15new.zip](https://github.com/user-attachments/files/25587097/EV2W_VA3_telnet15new.zip)
—
Reply to this email directly, [view it on GitHub](#86 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AUSD2DSG5X2XPFEKQPJF37T4N5LD7AVCNFSM6AAAAACV5XSNOSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJTHA4TGMA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Patch isn't a problem. Until I see your Linux distribution, it's undesirable to change any settings. If you do apply any settings, please try them one at a time, so you can see what works and what doesn't. As practice has shown, this folder is sufficient for analysis. Everything you need is located in this folder. An archive will appear on your SD card. Send the resulting archive to a@kornienko.ru. If you break something later, you can use the downloaded data to restore the files and create a recovery patch. |
|
Hi @Arkady23 , I own a device similar to the OP (EV2W_VA3). I bought it from amazon (https://www.amazon.in/Conbre-UltraXR-Outdoor-Wireless-Security/dp/B0CNTGCGGV) and it's called Conbre UltraXR [Model:K802]. The patch files that you've shared in this thread all seem to trigger firmware update on my device as well. But as @archcloudy pointed out already, nothing changes after the 'update' and the camera continues to work as usual without any changes (no telnet/RTSP/ONVIF). For more information, I opened up the camera enclosure and found out that the SOC was Anyka "AK3918EN088" NOT the usual "AK3918EN080"
So, I decided to take a look inside the original firmware file posted here . I don't have much knowledge in reverse engineering but I followed the instructions posted here and managed to extract the patch file using both binwalk and patchv380. Binwalk listed the following files:
Whereas, patchv380 listed the files under these names: In both cases, I did not see 'exshell_bfu.sh' file in the root of the file system. Is this normal? By the look of things, I wonder if the firmware's file system and structure has changed in the recent v380 models? To extract the romfs, I tried using romfsck2. It listed the following output, but did not succeed in extracting the file contents. Do you have any idea on how to extract aliosromfs files? Kindly let me know. Just to check if the custom patching process worked, I tried manually creating a patch using the 'exshell_bfu.sh' file. The patch was recognized by the device, and the firmware upgrade audio played. But, as reported multiple times in this thread, the script do not seem to have worked. This was the content of the script (exshell_bfu.sh): After the device rebooted, I tried checking the sdcard. But 'test.log' file was not there. I also contacted the support requesting for a way to enable RTSP/ONVIF feature via ceshi.ini file and I was told that it's not possible to do that in this model. I am sharing this information for future reference of both myself and others. Also, I am willing to help run tests using your scripts if you want. Please let me know if you need something tested. Appreciate what you are doing for this community. Thank you. |
|
@archcloudy /mnt/mtd seems like a system mount point that contains a bunch of configs and stuff. Have a look at the attachment for the xxd output, it should give you a good idea.
The recordings are being saved to RecFiles folder in the SD Card and they are indeed AVI files. I was able to play them using the default windows media player without any additional codecs.
The only script with the .sh extension was something named patchrule.sh, but I couldn't find any ways to extract it. If there's a known method to extract these files, please let me know. Other things I learned from snooping around the file system: I am looking to compare and test stuff between different firmwares. If you happen to have these below files, kindly post them here.
@Arkady23 The attachments contain the xxd outputs targeting /mnt/sdcard that you asked for. P.S I am still a beginner trying to learn reverse engineering. Kindly bear with me if the information I post here is too trivial. If there's a standard workflow to analyzing firmware (extracting, decompiling, recompiling, building the image, etc) kindly let me know. It would be most helpful. |
|
У меня такая же камера на чипе 88 очень жду новостей по этому поводу |
|
Hello @Arkady23, Same platform EV2W_VA3, similar result as others in this thread. Software: AppEV2W_VA3_V1.3.6.1_20231113 I applied diagnostic patch (update complete voice). ls.txt was NOT created on SD. Please advise which patch I should try next for AWT3710D. Thank you. |
|
hi, use this alternative for now: https://github.com/PyanSofyan/V380Decoder Works really well, i even integrated it onto my Frigate NVR 💀 |














Uh oh!
There was an error while loading. Please reload this page.
hi, i was wondering if this firmware could be patched? i managed to get v380techical@gmail.com send firmware to me
so sorry if im not following the usual rules or smth here
V380^AK3918EV200W^EV2W_VA3^1.3.7.0^2023-12-11.zip
All reactions