VIOFO A329 FIRMWARE

VIOFO 512GB and VIOFO 256GB. I used the 256GB to upgrade the firmware but the remote wouldn't re-pair with the dashcam. Once I changed back to the 512GB the remote worked without issue.
 
bunnyspecs said:
VIOFO 512GB and VIOFO 256GB. I used the 256GB to upgrade the firmware but the remote wouldn't re-pair with the dashcam. Once I changed back to the 512GB the remote worked without issue.
Click to expand...
Strange, maybe it needed to be formatted in the camera for it to work?
 
Both were formatted in the dashcam. I used the 256GB card in the A329 for about a month before switching to the 512GB. Only difference is I plugged the 256GB card into my MacBook to load up the firmware last night and the 512GB has only ever been plugged into the A329.
 
What is the trick to upgrade the firmware?

A 2GB card has been formatted in-camera.
v1.1 .bin file copied to root of card.

Capture.webp


With camera off, card inserted.
Camera powered on, and it just sat there with this on the screen:

20250125_100320_1200.webp


After 6 minutes, I powered the camera down, and swapped the card back to my normal 256GB recording card.

Is it expecting the .bin file to be somewhere else?
If elsewhere, where?
 
I've been looking at that bin file for a couple of minutes wondering if it was uploaded incorrectly. I would expect the format to be similar to the earlier versions (like FWA329_V1.0_20241029 instead of just FWA329.bin). I think you just answered the question for me.
 
5.0ALM said:
What is the trick to upgrade the firmware?

A 2GB card has been formatted in-camera.
v1.1 .bin file copied to root of card.

View attachment 77005

With camera off, card inserted.
Camera powered on, and it just sat there with this on the screen:

View attachment 77006

After 6 minutes, I powered the camera down, and swapped the card back to my normal 256GB recording card.

Is it expecting the .bin file to be somewhere else?
If elsewhere, where?
Click to expand...
I had the exact same issue no matter if I formatted the card via Viofo GUI tool, or in PC, or in the camera itself.

You need to swap to a different memory card and try that again, that's what worked for me. I was stuck on the 10% screen and it never went past it.

By the way, check @viofo latest post, there's a 1.2 firmware now...
 
Never mind.
I now know what I'm dealing with here... buggy software that was written by interns.

I formatted another card, this time a larger 64GB Samsung, in-camera.

20250125_105930_1200.webp


First attempt was using a Toshiba 2GB card (seen at left).
These are the smaller, older, cards that end up lying around begging for a use.

Interesting, this time, the DCIM folder wasn't created.
Nor was there a zero byte length file called format.txt.
(compare to my post above)

Capture2.webp


I think it's inexcusable that a card formatted in the camera itself does not work reliably, no matter what the capacity.
(Obviously observing any maximum size limit)
Especially when you consider this exercise is not needing to fast write large blocks of data as per recording video.

This update exercise reveals sloppy programming bugs in Viofo's coding.
Nothing more, nothing less.

Anyway, using the 64GB Samsung card, the bin file was copied to the root of the card, and the update was successful this time, taking a minute or so.

20250125_104518_1200.webp


20250125_105400_1200.webp


Now to do the second A329 in the other car.

Hope this helps somebody else.
 
So I’m assuming this is not the firmware released today?
 
Agie said:
5.0ALM said:
Thanks Agie.
Found it.
Silly me - looking for firmware in a thread called "Viofo A329 Firmware".... and not somewhere else.

v1.2 posted here:
viofo

Post in thread 'HDR question for the VIOFO A329'

The latest version was released on 1.20.
https://drive.google.com/file/d/1xUAow7C7nXvpFj0Thl_z2NvDG5Egipof/view?usp=sharing
  • Like
Click to expand...

By the way, check @viofo latest post, there's a 1.2 firmware now...
Click to expand...

v1.2 update done.

This update doesn't wipe your settings, like v1.1 did.

20250125_113237_1200.webp
 
As we can see, more sloppy coding.
Still says v1.1 (not v1.2) but with the later date.
 
5.0ALM said:
As we can see, more sloppy coding.
Still says v1.1 (not v1.2) but with the later date.
Click to expand...
I'm not too hip to the naming structure of bin files, but I am 100% certain that the firmware you flashed today, based upon the photo you posted, is not today's release. On January second, Karagandinez posted a link to that firmware version. So not v1.2.
 
Rocket Man said:
I'm not too hip to the naming structure of bin files, but I am 100% certain that the firmware you flashed today, based upon the photo you posted, is not today's release. On January second, Karagandinez posted a link to that firmware version. So not v1.2.
Click to expand...
???

As per my quote above, it was Viofo suggesting this was 1.2.
Note the date.
This was posted by them almost 4 hours ago.


Capture.webp



I'm not going to update the other car now.
It can stay at the factory release.
All confidence is lost for now, and I don't spending hard earned money on premium-priced items to be a guinea pig.
 
Rocket Man said:
I'm not too hip to the naming structure of bin files, but I am 100% certain that the firmware you flashed today, based upon the photo you posted, is not today's release. On January second, Karagandinez posted a link to that firmware version. So not v1.2.
Click to expand...
It is today's release, I'm 100% on that.

If you check the upload details by Viofo on the file on Google drive, it's the 25th January 2025 which is today.
 
5.0ALM said:
???

As per my quote above, it was Viofo suggesting this was 1.2.
Note the date.
This was posted by them almost 4 hours ago.


View attachment 77014


I'm not going to update the other car now.
It can stay at the factory release.
All confidence is lost for now, and I don't spending hard earned money on premium-priced items to be a guinea pig.
Click to expand...
Yeah that's what I said - and if you check the upload date of the file on Google Drive it's today's date lol. Not early January like the previous one was.

Don't know if they meant 1.2 but they forgot to change the firmware version tag to 1.2. they've had various 1.x firmwares for the VS1 and A229 Pro for example, that remain the same version number but the date is updated.

Confusing cos they were updates but just not publicised haha
 
You must log in or register to reply here.
Back
Top