<![CDATA[Strange program running in after installing UIflow2 on factory set new AtomS3 Lite]]>Moved from General

Experienced a strange event while using my ATOM S3 Lite for the first time.

MacOS

M5Burner was already running when I attached the device.
Downloaded the latest uiflow2 dated 29-05-2025
Configured, and started burn, which ran quickly, without the usual bind request.
Started a new project.
Connected, but was unable to Run or Load.
Process running in terminal installed itself as something suggesting a BT Beacon, and established
a WiFi AP on a 192.168.4.1 IP. It also appeared to be transferring data.

Unfortunately I don't have a copy of the output.

I restarted M5 Burner, and a new update from the same date was available. Burning this version solved the problem.

Does anyone know what happened here?

]]>https://community.m5stack.com/topic/7592/strange-program-running-in-after-installing-uiflow2-on-factory-set-new-atoms3-liteRSS for NodeMon, 16 Mar 2026 14:56:33 GMTSun, 01 Jun 2025 10:58:04 GMT60<![CDATA[Reply to Strange program running in after installing UIflow2 on factory set new AtomS3 Lite on Sun, 01 Jun 2025 20:57:55 GMT]]>@ajb2k3 There was no previous firmware that I installed. This was an out-of-the-box installation. I downloaded the latest update - I think 2.2.7 - and that's when the problem occurred.
Also, when I went to press burn, there was no opportunity to erase before burning.

]]>https://community.m5stack.com/post/29155https://community.m5stack.com/post/29155Sun, 01 Jun 2025 20:57:55 GMT<![CDATA[Reply to Strange program running in after installing UIflow2 on factory set new AtomS3 Lite on Sun, 01 Jun 2025 17:50:55 GMT]]>@Boomvalt No must always erase first to remove the previous firmware and config.
Once the erase process is done then you will be asked to bind (you may need to erase the old Atom3 from UIFLOW2 account first) then you can burn a clean update.

]]>https://community.m5stack.com/post/29153https://community.m5stack.com/post/29153Sun, 01 Jun 2025 17:50:55 GMT