Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] Beelink Mini MX3 II / M8S II TVStock Nexus ROM (Android TV)
Collapse
This is a sticky topic.
X
X
-
This rom works great on Scishion v88 pro. The box was pretty much useless until this rom came out. I used amlogic usb burning tool. After the inital startup I got the box to work on 1,2mhz max and 100mhz min using no frills cpu in perfomance mode. Well, all hd channels now work in Kodi without any hiccups. Thank you so much for this fantastic rom. I didnt tried wireless, only wired connection.Last edited by Marko1982; 15 March 2018, 20:59.
Leave a comment:
-
Hello guys!
First all thanks so much for all the hard work...I have several boxes on my family and everyone loves your custom roms. I currently have 2 Mini M8S II, 1 MX3 II and one X96 MINI (this one running the TX3 Mini rom).
My question is...I'm trying to do fresh installs on all of them and I've managed to clone the first three using TWRP backup and restore with your rom without any hassles...Just had to reconfigure some small things. My problem is that I use team viewer to help my family with some troubleshoot whenever necessary and I install most of the apps from the website directly. After doing this cloning, all my boxes are stuck with same name, serial number and no way to change it...I've tried Xposed framework with several id changers but none of them stick..
Is it possible to change it on some prop file? They all have the "0123456789abcdef" serial number and "Asus Nexus Player". I've managed to find some info on the build.prop but didn't touch it without knowing for sure what would happen! And also the serial number is nowhere to be found...Spend hours searching for it but no joy...
Basically can someone tell me where I can change permanently the serial number?
Thank you!
Leave a comment:
-
I didn't know that, thanks for letting me know, it has stopped me looking for the impossible Android 6.x ROM for my MX3
Leave a comment:
-
Note that this is a Lollipop ROM, since the Amlogic S905 is only supported on the Amlogic SDK 5.1. http://openlinux.amlogic.com/Android/Mbox
-
Thanks for the pointer, I will give it a go and respond in that thread
Leave a comment:
-
Magendanz,
Thanks for response.
I believe you are correct, stupid me, I took a closer look at my box and it looks like it is a Beelink Mini X3, not a Mini X3 2, with a build number MINI MXlll107L1, pic of the back markings below. Luckily the burn image software stopped me loading an incorrect image.
Are you able to supply me with a link to best (in your opinion) ROM for the Mini MX3?
As my Mini MX3 is already at Android 5.1.1 my preference would be for an Android 6 ROM.
Last edited by Jeffers; 08 February 2018, 14:52.
Leave a comment:
-
When using USB Burning Tool to install ROM I get following error, I am using the USB port next to the micro sdcard slot any idea what I need to do to fix?
[08:54:37 582][Global][Inf]--Update HUB1-17
[08:54:37 582][HUB1-17][Inf]--Update device path
[08:54:37 582][Global][Inf]--Update HUB1-18
[08:54:37 582][HUB1-18][Inf]--Update device path
[08:54:37 613][HUB1-1][Inf]--Device is connected
[08:54:37 613][HUB1-1][Inf]--Close device handle 0x000004c8
[08:54:37 691][HUB1-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&763bb00&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x000004c8
[08:54:37 753][HUB1-1][Inf]-------------Download DDR.USB-----------
[08:54:37 753][HUB1-1][Inf]--2-0-0-0
[08:54:37 753][HUB1-1][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[08:54:38 264][HUB1-1][Inf]--Control write pll reg1 0xd9000000:0x00005183
[08:54:38 775][HUB1-1][Inf]--Write initial succeed
[08:54:38 775][HUB1-1][Inf]--Upload encrypt at 0xc8100228
[08:54:38 775][HUB1-1][Inf]--ulValue = 0xedfc318c
[08:54:38 775][HUB1-1][Inf]--Read encrypt value succeed
[08:54:38 786][HUB1-1][Inf]--Transfer complete
[08:54:38 786][HUB1-1][Inf]--Run at address 0xd9000000
[08:54:38 787][HUB1-1][Inf]--RunInRam succeed
[08:54:38 790][HUB1-1][Inf]--2-0-0-0
[08:54:38 790][HUB1-1][Inf]--CheckFileRunState succeed
[08:54:38 790][HUB1-1][Inf]--runResult:0x 0,paraMagic:0x3412cdab
[08:54:38 790][HUB1-1][Err]--ReadPara failed
[08:54:38 806][HUB1-1][Err]--[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
[08:54:38 806][HUB1-1][Inf]--Close device handle 0x000004c8
[08:55:05 580][Global][Inf]--Catch DBT_DEVICEREMOVECOMPLETE
[08:55:05 580][Global][Inf]--Scan usb device
[08:55:05 580][Global][Inf]--Aml scan WorldCup Device
[08:55:05 580][Global][Inf]--Host: USB xHCI Compliant Host Controller
[08:55:05 580][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_9d2f&subsys_07041028& rev_21#3&11583659&0&a0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[08:55:05 580][Global][Inf]---->Roothub:USB#ROOT_HUB30#4&369d7e28&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Leave a comment:
-
Hello, i may need help here. I was looking for a firmware update and landed here. I burned the package to my Mini MXIII II, now I'm stock on the Set up page for Google. The wifi seems not be not working, but I'm not sure if its QUALCOMM. And if it is, i really don't know how to install the update for QUALCOMM (the zip file)...
edit: i figured it out! thanks. I'm really new on these. Hope there's a auto start 4k video on startup to fix the dark contrast
Last edited by BELPHEGOR; 06 February 2018, 15:40.
Leave a comment:
-
Originally posted by array81 View PostAmazon Prime Video not works. I have test both normal and TV version.
Leave a comment:
-
1. Not with this ROM, but the Shiningworth ROMs recently got this support and I'm working on a port to the Amlogic p212 reference board.
2. No, that would require Widevine L1 keys to be flashed at the factory.
3. Despite teases (http://www.androidpolice.com/2018/01...actually-work/), Amazon Prime Video isn't available for Android TV yet. I've heard the mobile version won't run on Android TV, and I'm guessing that it's going to require Widevine L1 even when it's available.
What's Going On
Collapse
There are currently 2328 users online. 1 members and 2327 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Leave a comment: