There are some quite fundamental things yet unclear with the prototypes presented here.

The deciding question is what is the hardware platform, is it intel or arm? That has not fully been cleared yet, as I think the SOC's are under a welded shielding cage as @dirkvl noted. Hence it would need a bit of meddling to actually eyeball the chips.

Something could be deduced from the boot display, as I think the devices (or one/some of them?) are in a mode that shows up the startup messages on screen. It scrolls probably too fast for human reading so it is advisable to make a video recording of the bootup messages.

However, the OS by itself doesn't necessarily tell anything about the intended HW platform since it is fairly common to run first development releases on an existing platforms when the "Real HW" is not yet made in sufficent quantities so that all involved R&D people would have their own development environment.
Hence, it is possible that the HW platform is arm but the OS in the device is Ilmatar.
(This is a very common R&D pattern in Nokia, and I believe also in other design houses.)

As for the flasher; I believe that the base protocol between the flasher and NOLO is most probably same whether the HW platform is arm or intel; it is designed to be fairly insensitive for the underlying architecture.
Flasher has two different modes; an inquiry/setting mode where device operation parameters can be read and tweaked and the actual flashing mode which is implemented by separate extension for each device model.

In the flashing mode the flasher utility reads a specific part from the image file called "APE Algorithm" which is a self-contained rescue-OS image which is sent to device and which therein performs the actual device-dependent actions of the flashing.
This way it doesn't make any difference what HW platform is under flashing.
The trick here is now to find a good image file to be flashed to the device. (pro tip; you won't find one )