I've tried libreelec and it is booting fine with no issues, so i tried connecting this box using burning tool to pc using reboot update command but the box is not recognized (tried different usb ports with no success). This box doesn't have reset button. Any suggestions?
Mecool m8s pro plus
-
- Administrator & Developer
- Posts: 1551
- Joined: Tue Oct 02, 2018 6:19 pm
- Has thanked: 211 times
- Been thanked: 334 times
You have a custom bootloader where the loc_name "aml_dt" has been changed. I suspect that the update is not possible for exactly this reason. (a uart log would be appropriate here). The only possibility I see here is to manually remove the original bootloader and install a new one, hoping that the emmc memory will have write access.
-
- Administrator & Developer
- Posts: 1263
- Joined: Mon Jun 11, 2018 11:58 pm
- Has thanked: 192 times
- Been thanked: 434 times
- Contact:
Another thing you can do is port atvX to mecool.
It's not that hard and just requires copy-pasting main files and testing to see if something's missing.
Let me know if you'd like to port atvx to mecool, I don't have the device but you have my full support
BE NICE, BE RESPECTFUL
RESPECT THE MODERATORS
PM ONLY WHEN IMPORTANT
ENJOY! My Devices:
X96 Mini, A95X Pro, H96 Pro Stick, A95X Max
RESPECT THE MODERATORS
PM ONLY WHEN IMPORTANT
ENJOY! My Devices:
X96 Mini, A95X Pro, H96 Pro Stick, A95X Max
Thanks for your support. If I can learn and help also other I`m willing to try porting atvx to this device. I`m waiting for instructions
-
- Administrator & Developer
- Posts: 1263
- Joined: Mon Jun 11, 2018 11:58 pm
- Has thanked: 192 times
- Been thanked: 434 times
- Contact:
First and foremost is, go to usb burning tool fixing guide and see point number 6.roby777 wrote: ↑Mon Feb 11, 2019 7:57 amThanks for your support. If I can learn and help also other I`m willing to try porting atvx to this device. I`m waiting for instructions
BE NICE, BE RESPECTFUL
RESPECT THE MODERATORS
PM ONLY WHEN IMPORTANT
ENJOY! My Devices:
X96 Mini, A95X Pro, H96 Pro Stick, A95X Max
RESPECT THE MODERATORS
PM ONLY WHEN IMPORTANT
ENJOY! My Devices:
X96 Mini, A95X Pro, H96 Pro Stick, A95X Max
-
- Verified Member
- Posts: 10
- Joined: Fri Oct 05, 2018 9:37 pm
I am interested in it too. I have 2 boxes and I want to falsh ATVX. But I don't undestand neither the first step: "First and foremost is, go to usb burning tool fixing guide and see point number 6"
Where I can find the fixing guide? Google found only this post
Where I can find the fixing guide? Google found only this post
Hi once again. Any suggestions for burning atvx on this android box. I have disassembled this box and inside it says that this motherboard is M8S_W_BT_V2.0 2018-06-27. I`m not sure which Emmc chip is inside. This is a gxl_281_2g device, S905W. Which version of atvx you suggest and with which options enabled in USB burning tool?
You do not have the required permissions to view the files attached to this post.
Hi, I`ve made some tests. I`ve tried booting CoreElec to this device using sd card and it is working with no issues. First according to CoreElec device Trees I`ve copied to root device tree gxl_p212_2g which supposed to be for my device (Mecool M8S Pro+ but this is for S905X (mine supposed to be S905W or not?)) It was working with no issues (wifi, usb ports). Then I ran another test and copied to root device tree gxl_p281_2g which supposed not to be for my device but for Mecool M8S Pro W (which I don`t have, and it is for S905W boxes) also according to CoreElec device Trees. Suprisingly it was working also with no issues. After all these tests I`m little bit confused. If I go into Android Recovery I can see inside that is written : Amlogic /p21x/p21x. If I run Aida 64 under board it is written that this is p21x board. If I run in terminal command: cat /proc/device-tree/amlogic-dt-id than I`ve got this message that this is: gxl_p28x_2gM8S_PRO_W board. So what board do I have gxl_p212_2g or gxl_p281_2g, and what processor is inside this box ? S905X or S905W variant? Thanks in advance.
You do not have the required permissions to view the files attached to this post.