That flasher that is suggested on their page just unzips it on the fly and is smart enough to not try and flash the whole zip file ![]()
Can you please share a photo of the entire screen when this message appears?
Has anyone actually flashed the new OS successfully at all?
Yes, we’ve heard from and seen video of other users using the new OS.
Which version of Balena Etcher are you using? Do you let Etcher verify the disk after it flashes it?
The latest version of Balena and yes I let it verify after flashing ![]()
Thanks for the information. We’ll take a look when we’re at the shop tomorrow. Thanks for your patience.
I just flashed it with a PC using the newest Balena - using the unzipped OS and exactly the same error message → so it definitely is not a MAC issue!
I have a gig that I need to use the Eyesy for this Friday - I am freaking out a little as it won’t work at all now, will the previous OS work I wonder
Can you try flashing with the zipped image?
on Mac or PC? haha .. the first time I flashed it from Mac was using the zipped image btw (which it seemed to extract on the fly anyway)
I used the disk image zipped
That happened to me too. Balena Etcher on the Mac. I reflashed a second time and this time it worked.
I got the new OS running with no problem, but have errors happening in some patches - at least a dozen of them had the same error as shown in the photo.
Some of them were new to me since I spent some time at Patchstorage yesterday getting some newer patches to try out, but this one in particular I know I had previously and it ran with no issues on the old OS.
Are these modes you downloaded and put on the EYESY? Modes for the old OS might need to be updated due to differences between Python 2 and 3, and some other little changes. If they are CG modes on patch storage, let me know the names and we’ll get them updated.
There is also a guide for converting them if you are interested:
@sgotb Thanks for the update.
To add to @oweno’s post about converting older modes to OSv3, I just wanted to point out that we created a separate repository for ‘stock’ EYESY modes for OSv3:
These modes have all been updated for the changes in OSv3 and in other ways as well so that the imagery scales appropriately when you switch the EYESY to different output resolutions.
yes - they’re downloaded patches. the only errors I got were from those, not the stock CG modes. thank you!
Any idea why the new OS is not working for a lot of people? I just flashed OS2.x and it worked fine on my box .. using mac
It’s good you got the older one flashed without problems… this indicates Etcher and SD card should be working properly. The other sources of problem are usually a corrupt download, or issue unzipping. You could try downloading the file again if you haven’t.
We’ve been trying to reproduce the problem, trying many different SD cards lying around here, all without any luck, so it is a little baffling.
We also now have flashed SD cards available for order on the website.
I too am encountering that (light) blue screen of death.
Orange Eyesy, original SD card, Win 10, running etcher in Admin mode, tried both unzipping and not unzipping the update file, etcher completes validation.
I’ve tried 10 times so far, same result each time.
Do you also see error messages? The blue screen appears normally for several seconds during boot up before the EYESY software loads. (although in hindsight it might not have been the best color choice lol)
I’ve been wondering if it is problem with older SD cards. Does yours have any markings on it? Thanks for trying it and sorry for the trouble!

