Based on the official StickCPlus code.
https://drive.google.com/file/d/1fKeBRxvAmH44b_zIxOOjyv3MeaxYMzkR/view?usp=sharing

@ajb2k3
I usually change the /etc/ssh/sshd_config as follows:

# Authentication:
LoginGraceTime 120
#PermitRootLogin prohibit-password
PermitRootLogin yes
StrictModes yes

then you can login as the root user

@gleiden
Generally, No serial data received is because the ESP32 has not entered download mode successfully.

Hi @scoobysnax
Yes, StampS3 does not have a built-in fuel gauge.
I suggest you make a power supply device yourself, or you can take a look at this new M5StackTimerPWR: https://docs.m5stack.com/en/unit/Unit-TimerPWR
From the official documents and the actual photos, the battery connector of Dial is indeed 1.25mm-2P. I don't understand why the connector you bought is incompatible, or you can take a look at the official power terminal specification: https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/M5Dial/1.25WT-2P.pdf.

The method is very simple: download the UiFlow firmware source code, copy the microPython code generated in UiFlow to main.py, change the boot option so that the device runs main.py after powering on, compile the UiFlow firmware, and you will get a .bin file running directly into main.py.

Step 1: Setting up ESP-IDF environment and download UiFlow source code

https://github.com/m5stack/uiflow-micropython
Follow the "How to build" instrument to setting up ESP-IDF environment and clone the UiFlow source code.

Step 2: Change the main.py file and modify boot option

Open up location /m5stack/fs/user/main.py and paste your code generated by UiFlow.
Open up location /m5stack/fs/user/boot.py and edit line 37-40

try:
        boot_option = nvs.get_u8("boot_option")
    except:
        boot_option = 1  # default

into

boot_option = 0 

By editing these codes, your device will directly runs main.py after booting. Don't forget to save the files.

Step 3: Build the firmware and flash into your device

Just follow the "Building the firmware" instrument, it will generate a .bin file in /m5stack/build-%YOUR_BOARD_NAME%/ and flash it into your device
Now you have your own .bin with microPython codes, you can publish it in the "User Custom" of M5Burner or other places.

If there is any better or easier way, please discuss it with me.

@teastain
Because the entire framework of UiFlow1 can no longer support the large number of new devices and new functions, UiFlow2 is equivalent to redoing all the functions.
No there is no UiFlow3

@ajb2k3
okay... after few hours of digging, I found it out that you must save the .bmp file as 16bit-depth (RGB565), mspaint does not have that feature so i got it worked by using Photoshop

@vxgvxg
Yes, these Bases will be adapted to UiFlow2, give it some time

@ajb2k3 @Remco
this is a known issue, fixing

@Rango
known issue, fixing

@ZokiZok

i think it should be a pin choose problem

@pkayme
You should use microPython to import external libraries

@AdventKylin
Why don't you use the official esptool but the third-party M5Launcher? This is not convincing, you don't know how M5Launcher flashes the firmware. The export function in M5Burner packages the entire flash into a bin, so of course there is no bootloader.bin or spiffs.bin.

@AdventKylin
hey...I don't know why you do that, but I just tried it on my CoreS3, and it works fine, it dumps my entire flash into a 16M bin file, then I erased the CoreS3's flash and flashed the bin to address 0x00 with esptool, and the device works perfectly fine, I don't know where your accusation comes from.

@FlappyCat
You accidentally entered M5 website hosted by Switch Science
Use this: https://m5burner-cdn.m5stack.com/app/M5Burner-v3-beta-win-x64.zip

@k0u1_H
僕の知る限り、そういった汎用的な方法は存在しないはずです。
M5Stack.hは、M5チームがCore Basicのために作成したヘッダーファイルで、当時はM5UnifiedやM5GFXがなかったため、このヘッダーファイルに基づく多くの例は古い関数が含まれています。そのため、後に廃止されたり名前が変更された関数が多く、新しい開発ボードに移植するのは大変な作業です。
僕が以前に言ったように、比較的古いモジュールやベース（特に大きなM5のロゴが印刷されたもの）を使用する場合は、Core Basicをコントローラーとして使用することをお勧めします。比較的新しいユニットやモジュールを使用する場合は、古いコントローラーと新しいコントローラーの両方から必要に応じて選択できます。

@ZokiZok
I tested it on CoreS3 and this error did not occur. Maybe you chose the wrong pin?

@echiz
https://uiflow-micropython.readthedocs.io/en/latest/index.html

@ZokiZok
have you update your firmware to the newest version?

@echiz
I think the support of LVGL has been removed in the newest version of UiFlow2
Maybe change it to a elder version will have chance?