Disclaimer
Installing a non-official operating system on the Remix Mini PC is done at your own risk. This process may void your warranty...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for your excellent work! I recently found my Remix Mini in corner btw, searching for ROM. Is there something like GitHub links for contributing this? Happy to see community still alive, I love armbian
I'm also working on that. I'm in the process of building a new one from the ground up. I'll share updates from that. Stay tuned
🔧 Contributions are welcome! Check out the repo and get involved.
By the way, I'm still puzzling over the internal memory. I'm working on another (alpine-based) custom kernel to be able to erase the eMMC, which is a bit of a pain as it's locked by default. But hopefully some memory hack will do the work and make the table corrupt to go further. As soon as I have a working version I will post it and maybe create a GitHub repo to make it more public and open source.
may sudo be with you
Hi ! I followed your amazing tutorial to revive the Remix Mini. I managed to boot up the img, but have you found a way to install it on the emmc storage ? I tried several ways but haven't found one working.
I would be glad to hear if you found one !
And thank's again for the work, I was looking for some time to reuse that device
Hi LeoKryssen! It's great to hear from you, and I'm glad to see other remix users are still around! :D
You raised an excellent question. Currently, I'm at a bit of a challenging stage, as I've hit a roadblock. However, I plan to spend some time tomorrow delving deeper into the firmware and the uBoot connection.
So far, I've discovered that it's possible to "blacklist" the eMMC, which means the OS won't show up in the Disks or lsblk commands. This is a positive development, as it effectively "detaches" the eMMC from the running processes. This could potentially lead to the ability to format the eMMC from within the system. However, I have some concerns that the firmware may not permit this. Nevertheless, there's always a workaround to explore!
I will definitely continue with the project! Since I started discussing this "solution" involving the firmware exploration method, several of my friends have expressed interest as well. As a result, I expect to have more devices coming to my desk soon. So, stay tuned for updates!
I've just dug mine out as well. I'm not to savvy with these things, however, I am hoping that this will become useful again.
I've subscribed here. Is there any other ways to keep up to date with it?
Thanks for the work you've put into it already!
Hi John! Thank you for your interest. Well, I started to get this project online with a GitHub repo. If you have a profile you can also follow it there. On the other hand, I will be making a new post about the updates, and I am also thinking about making a video of the process. For a while now I've been working on another custom bootloader that will be able to completely erase the internal memory of the Remix Mini (against the firmware lock).
github.com/r4nd3l/revived_remix_mi...
Thanks for your work.
I stumbled upon my Remix Mini when cleaning out old stuff and found this post when searching for information on what can be done with the device today. So first of all thanks for your efforts! Second, was are the differences between RM1G or RM2G? I assumed it was the amount of RAM. I see that I backed for a 2GB device on Kickstarter back then but the device I have is the RM1G. Initially, I thought I might have received the 1GB model by mistake but it does appear to have 2GB onboard so not sure what to make of the naming scheme.
As far as I can remember, there was a choice between the two. But the naming does not mean anything special except the firmware. Early birds got a starter (beta version, actually a buggy one) and then later on, after the official launch, they released something more (some what) stable and that was the RM1G. But the device itself did not change during the campaign as far as I know.