mecool m8s pro l

[tv4you2016]

@ophub I used the img
Armbian_22.08.0_Aml_s912-m8s_jammy_5.15.60_server_2022.08.14.img.gz

and the boot from the pen does not work

i also know the img Armbian_22.08.0_Aml_s912-m8s_jammy_5.10.136_server_2022.08.14.img.gz

and the boot doesn't work, but using the img
CoreELEC-Amlogic.arm-9.0.2-Generic.img.gz
the boot works.
Can you help me or check what's going on?

[ophub]

#158

Device name?
MECOOL M8S PRO L

soc model?
S912

dtb name?
meson-gxm-q201.dtb

u-boot name?
u-boot-s905x-s912

support for 5.4/5.15 kernel?
yes

support for writing emmc?
yes

amlogic-s9xxx-armbian/build-armbian/common-files/rootfs/etc/amlogic_model_database.conf

Line 35 in 97c6768

206:MECOOL M8S Pro L:s912:meson-gxm-q201.dtb:u-boot-s905x-s912.bin:NA:NA

Tested with usb, using 5.15 kernel firmware

[tv4you2016]

I did the following:

1-> download from Armbian_22.08.0_Aml_s912-m8s_jammy_5.15.60_server_2022.08.14.img.gz

2-> flashed the pen with balenaEtcher

4-> I checked the dtb

5-> with the box off I put the flash drive in the box then put the power on,

result:

booted to android

is there any log you can share?

[ophub]

https://github.com/ophub/amlogic-s9xxx-armbian/tree/main/build-armbian/armbian-docs#124-set-the-box-to-boot-from-usbtfsd

[tv4you2016]

PS C:\platform-tools_r33.0.2-windows\platform-tools> ./adb connect 192.168.1.231:5555

• daemon not running; starting now at tcp:5037
• daemon started successfully
  connected to 192.168.1.231:5555
  PS C:\Downloads\platform-tools_r33.0.2-windows\platform-tools> ./adb shell reboot update

the device rebooted and went to android recovery

[tv4you2016]

[tv4you2016]

Uart debug on run android
COM6_2022-08-17.txt

[ophub]

Set the box to boot from USB/TF/SD

• Write the firmware to USB/TF/SD, insert it into the box after writing.
• Open the developer mode: Settings → About this machine → Version number (for example: X96max plus...), click on the version number for 5 times in quick succession, See the prompt of Enable Developer Mode displayed by the system.
• Turn on USB debugging: System → Advanced options → Developer options again (after entering, confirm that the status is on, and the USB debugging status in the list is also on). Enable ADB debugging.
• Install ADB tools: Download adb and unzip it, copy the three files adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll to the two files system32 and syswow64 under the directory of c://windows/ Folder, then open the cmd command panel, use adb --version command, if it is displayed, it is ready to use.
• Enter the cmd command mode. Enter the adb connect 192.168.1.137 command (the ip is modified according to your box, and you can check it in the router device connected to the box), If the link is successful, it will display connected to 192.168.1.137:5555
• Enter the adb shell reboot update command, the box will restart and boot from the USB/TF/SD you inserted, access the firmware IP address from a browser, or SSH to enter the firmware.

[tv4you2016]

at the end of the command adb shell reboot update
the box presents me this img and is not detected on the network

[ophub]

Open the developer mode: Settings → About this machine → Version number (for example: X96max plus...), click on the version number for 5 times in quick succession, See the prompt of Enable Developer Mode displayed by the system.

Does this box have a reset button? Press and hold for 5 seconds and release it to see if it can enter usb mode

[tv4you2016]

Developer Mode is enable :D

MECOOL M8S PRO L box we observe the small aluminum radiator and the different components, it is necessary to highlight that we do not have a reset button to reach the flash mode, so we will have to bridge with something metallic in the two points indicated in the photograph.

I added a button here

[ophub]

The firmware written in your usb was decompressed and flashed from the armbian_xxx.img file, right? Use this software: https://rufus.ie/

[tv4you2016]

117 / 5.000
Resultados de tradução
I used balenaEtcher.exe
With the armbian img :
Armbian_22.08.0_Aml_s912-m8s_bullseye_5.15.60_server_2022.08.17.img

[ophub]

Use this software: https://rufus.ie/

[tv4you2016]

I will try with rufus

wait for the feed

[tv4you2016]

this is the Corelec aml_autoscript file in which the box boots from the pen.

Was the armbian aml_autoscript correct?

aml_autoscript.txt

[ophub]

Not universal, he is Android system

[tv4you2016]

I already installed it on an x96 max on a Hk1 and it works 5* now this mecool m8s is giving me headaches

[ophub]

The first time you start the USB, you can always start from the USB. Some devices choose USB, and some people change several USBs before starting. Change the USB port, or use USB2.0

[tv4you2016]

I'm using a USB 2.0 pen and I've already tried it on 2 mecool ports and the result is always the same

[ophub]

#158

You @parkjw0117 to see how it started.

[tv4you2016]

Use this software: https://rufus.ie/
result is the same

could it be because of the kernel?

[ophub]

It's not because of the kernel, you're still in Android and haven't entered armbian yet.

If it is a kernel error, the code output on the screen will have related errors instead of being stuck in the Android system

[parkjw0117]

My install method when I run into problem.

1. Install stock rom on m8s pro l.
2. Boot and install terminal.
3. Insert USB or SD card into m8s.
4. Enter 'reboot update' and after reboot, it will be boot from USB/SD card.

[ophub]

Wrong, you can't insert the armbian system disk into the Android system in advance, which will cause it to be modified and unusable.

To enter reboot update, then quickly insert usb

If the USB is modified by Android, it cannot be used.

Rewrite the armbian firmware in the USB, wait for the command to be entered and then insert the USB

[tv4you2016]

I give up I can't even for nothing

for the 1st time i feel defeated