I can't find any websites to download this image, only found 104M0 (zip) and 106M0 (img).
That's fine for anyone that wants to 'convert' their box, as they can OTA up through all the builds after FW 104M0 / 106M0 is up and running running 
Posts by Poida
-
-
So far, with the 104M0 FW, the Beelink has not stalled at boot time running the 32bit build of 7.0.3.011 (although it did take a little while for the issue to surface . . . We shall see)
. . . and considering the post immediately above, this is encouraging
20+ reboots rapid succession - not a hiccup
Equally promising result so far with 106M0 and 107M0 FW . . .
Since 108M0 is already confirmed bug-free, I'll skip that one
-
Beelink is now challenging Nexbox as the number #1 contender for Stay Away Product.
That Beelink Mini MXIII II s905x is not even listed on their official website under products.
kostaman. Tell me about it! I've spent days trying to track down stock FW (any version) and, whilst I have located 105L1, 106L1 and 107L1 none install on the Beelink.
Even 104M0, and 106M0 from the 4pda.ru site fail to install
TWRP for S905X does run on this but only shows Boot, System & Data partitions (
so no real backup solution found for it yet either)
UPDATE: I did manage to 'persuade' 104M0 FW to install and so, do have a backup.
-
No, beacuse S905X doesn't need (and thus doesn't use) SARADC driver.Beelink Mini MXIII II (S905X) is affected by this
We are all aware that this issue is not restricted to S905, aren't we?
The Beelink Mini MXIII II (S905X) is also affected.
The Beelink now hangs on a black screen, immediately after the boot screen has gone off
Arghh! Beelink now getting stuck at boot logo again -
Not sure if this is correct. Put image on sd card, boot to it, then run installtonand again, I would assume it would overwrite the old install.That is the procedure, but advisable to build a 'clean' install from Android FW as it picks up some of it's settings from Android when it set's up.
It's not really a 'clean' install if you are building from another version of LE (at least that's how I interpret the info here)
-
If option 2 is too much extra work and overhead for you then option 3 is the best option diasble the temp sensor in all builds. Eiither way will be fine, I live in the UK it's generally not very warm here...not much danger of overheating these devicesBut a very real danger here, in Australia
[hr]
Build LibreELEC-S905.arm-7.0-devel-20170104082155-r23608-gcb8de5f won't get past reporting 'Failed to start load kernel modules' and spilling a load of text (all futher lines begin with OK) on the screen with the MiniMX-G
[hr]
Going forward to Krypton i would leave it Disabled and maybe Enable it as a Special Treat every now and then for S905x Boxes.
The bottom line is, S905 Boxes will no longer have a Temp Reading from now on.We are all aware that this issue is not restricted to S905, aren't we?
The Beelink Mini MXIII II (S905X) is also affected. -
-- I'd recommend staying away from the Nexbox or "MiniMX+" device I showcase in my prior post. This MiniMX+ is the only box I've ever run into issues with, after testing dozens of other Amlogic devices over the years!I came to the same conclusion after the hassles with the Nexbox A95 - Steer clear of Nexbox
-
Current usage is that if you stress CPU it will throttle after reaching 70°C and shut down after exceeding 85°C.And, jf the sensor is disabled? Will it just continue to overheat and never shut down?
I'm just throwing it out there (since it's way out of my league) but, is there a chance that the temp sensor can be enabled at a different point and avoid the hang? -
... I will check if I can modify the driver a bit to make it possible to disable it if the box (or its firmware) doesn't like it.I'm just throwing it out there (since it's way out of my league) but, is there a chance that the temp sensor can be enabled at a different point and avoid the hang?
-
Can anyone advise how to perform a clean install?. I'm wanting to transition to a 32 bit build.Cheers.
If you're using SD / USB, just use a different card. If you're on Nand, I'd be restoring the latest Android FW then follow the steps to install, listed on OP
-
Just out of curiosity, are you sure that you have a Beelink MiniMX?
Just seems a little surprising it boots with a Bear logo, instead of the Beelink logo :s -
Build LibreELEC-S905.arm-7.0-devel-20170103162229-r23610-g3b038ea.img.gz
Best so far. Hasn't stalled at all yet. Even rebooting in rapid succession hasn't caused it to hang (so far. . .) -
I again repeat i am getting desperate to solve this before Christmas and i could be showing early signs of delusional disorder.Good on ya champ! I, for one, am still hanging in there that you do get this solved before Christmas! LOL
-
LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz froze on cold boot number 10 (leaving at least 1 minute between reboots) on the Mini MX-G
kostaman I don't think that it should make any difference if the box is shutdown immediately or not. Sometimes this happens. If it does, that shouldn't affect whether the box can boot next time but, just to help check your theory, I have waited at least 1 minute before changing the status of the box
-
LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz froze on reboot number 7 (leaving at least 1 minute between reboots)
-
2nd image was good for about 6 boots
After that got stuck whether rebooting or booting from offTrying the next image . . .
-
It's not a bug, it's a feature.Totally agree - wasn't suggesting it was a bug
-
I'm more confused than he isLOL
These s905 boxes do have the reset button behind the AV port. Unfortunately, no amount of pressing that button, no amount of time, will get me into Recovery. I've tested dozens of different methods.- To enter Recovery, the only thing that has worked so far is issuing a "Reboot Recovery" from a Terminal Emulator
Methods I've used for attempting to enter recovery:
- Hold Reset (on this box it's behind AV port) - tested 50+ different boots, different ROM's, no luck
- Shorting the Reset-switch's pins (in case the switch itself is not triggering properly) - tested a dozen-plus times, no luck
- Use an Andriod Terminal Emulator to Reboot to recovery (or reboot update)- This does boots to the stock-recovery but it will not boot / run the SD version of @kszac's build.