RicoR_XNL 





Profile Overview for RicoR_XNL 

Official XNL Future Technologies Account
Account Type: XNL Future Technologies Founder & Owner

User Badges
 

Last 10 posts by RicoR_XNL 

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-02-18 13:05:50
No worries😊

And yes, you should indeed 100% certainly WAIT about 2-3 minutes before turning it off if you don't have video on during the first boot. The reason for this is that ArkOS is re-partitioning the SD-Card to it's maximum size and if you interrupt that process there is a very high probability it won't be able to boot properly at all anymore.

IF you however already know which files you need, then you can often just prepare the sd-card in your pc, then also (before inserting it into your R36) copy the dtb files to it and then do the first boot instantly with screen and all (which I also often do myself). But then you do already have to know which boot files you have.

I'm however very interesting to learn/discover if "you're doing something wrong" accidentally so to speak, or that there now (unfortunately) also ready is an imitation R36H or one with yet another display panel we haven't heard about yet.

Not only to possibly improve/update the text tutorial (this post) if needed, but also to see if I would possibly need to make an update for other R36H units for example..

Is there a possibility that you can upload the .dtb files from your original SD-Card to something like a googledrive or so and post the link here? (So I can investigate them?)😊

You could indeed also just try to remove all .dtb files and replace them with the ones from the download (or your original for that matter) if you can't get the new ArkOS to work....

IF you really have an (real) R36H, then it most likely is just the Panel 4 you'll need. I PERSONALLY haven't seen any other R36H units yet (and I have about 20 of them, with various board dates).

the rk3326-rg351mp-linux.dtb in your boot ini means it uses that file as loader for linux indeed. You could just go 'nuclear' and indeed just remove all .dtb's and the boot.ini file and then drop the new ones into that drive to see if you can get it to work.

IMPORTANT!!!!!! There are some other files on there (image and uInitrd for example), whatever you do: DO. NOT. REMOVE. THOSE😉😂. Those are CRITICAL to keep, I could in detail explain what they are but the reply is already turning into a book for you😉. In short: that is THE Linux kernel and the initial bootloader used to load Linux. Without those, nothing is going to happen ever either 😉

Good luck and keep me posted please😊👍🏽

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-02-16 17:10:31
Thanks, I will add them (after properly patching them) to my Distro properly crediting you. I have noticed a small difference and despite the fact they are a SLIGHTLY different than the Panel 0 files I have (which come from my purple R36S with the same board date), both my Purple R36 (same as yours) boots perfectly fine with with it. BUT strangely enough my latest Black R36S (board V22 2024-12-18) ALSO boots with it perfectly fine... BUT!!! If i use the original SD-card which came with each of those units and swap the cards? Nope no screen or a white screen with striping...

So definitely worth some investigation and an add to the selectable bootfiles in the Distro I'm building..

Most important part is that you got yours working, and therefor I also truly appreciate you kept taking your time to keep replying😊👍🏽

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-02-16 15:41:18
Thank you VERY much for supplying the files, helps greatly in debugging which one you truly have 😊. I have decompiled the file:
rk3326-r35s-linux.dtb (because that is actually the one used while rg351mp-kernel.dtb is the one for the boot system (they use VERY wrong naming conventions for those files).. The rk3326-rg351mp-linux.dtb one is not used, the only need two dtbs with those devices.. and your screen/display initalization sequence don't match the original panel 0 for 100% (which is a LONG line which looks like this: "panel-init-sequence = [39 00 04 b9 f1 12 83 39 00 06 b1 ........."

But when I tested YOUR rk3326-r35s-linux.dtb on my panel 0 R36 (be coincidence also a purple one😂) and EXACTLY the same version AND board date (R36S-V12 2023-08-18), it did booted just fine.

The "Without FN Button" however means that the dtb file is MOSTLIKELY not configured properly for that, it does not mean your device doesn't have the FN button, but that it just won't work (the button that is, the display most likely will😊).

The files you've used.. are those from your original SD-Card, or 'partial experimental copying' from downloads for example? 😊

Again: Major thanks for supplying these details, since it also GREATLY helps me make my Advanced OS specifically for the (Real) R36 units much more compatible 😊 (Files delivered by others will be appropriately credited btw of course)

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-02-16 00:15:28
R36H you say with issues that the panel doesn't work😳, pleaseeeee don't tell me they (in China) started messing with the R36H screens also now🤦🏽‍♀️....

For anyone struggling and not being able to figure out the exact issue with the main tutorial:
You basically need TWO dtb files... One if for the booting process and the second one is for linux ((d)ArkOS itself). BUT how they are named can be different unfortunately. You can however open boot.ini to see how the linux one (the most important one) should be named:
load mmc 1:1 ${dtb_loadaddr} rk3326-rg351mp-linux.dtb

that line shows the filename 'rk3326-rg351mp-linux.dtb' in this example.

But (like stated in my main tutorial also) IF you can't get it to work at all... you can also as last resort try to just copy the dtb files and boot.ini from your original SD-Card/backup to the boot partition of your new card to see if that works 😊

I'm sorry I can't be of more assistance with 'direct instructions', but they unfortunately make it absurdly complex for regular users by constantly changing the filenames, displays and sources they copy the distributions of the operations systems from. Which also makes it nearly impossible for me to keep up with all the random stuff each reseller keeps doing (often even without truly understanding what they are doing).

Hope this information helped you (or some others) a bit further though if issues arise.

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-02-14 22:13:22
Correct😊 but this has already also been explained in the 'fold-out-section' about if your screen would not be recognized 😊.

The problem is that there are A LOT of different devices (ESPECIALLY the R36S units) which use slightly different hardware. Most likely for them to save a couple more bucks on production I don't know🤷🏽‍♀️. But due to that inconsistency it's just getting a big hell more and more to keep maintaining all files for the R36S units. The real units are in general not an issue, and will most of the time work perfectly fine. But indeed (also like stated in the tutorial); sometimes you do might need to use your original files..

Would you be willing to email me a copy of your original boot files for analysis? You can also post me a link to a dropbox, google drive, wetransfer etc if you prefer 😊.

I'm currently working on a distro for more advanced users and would like to know about other panels and their data if needed.. Could you also provide me (IF visible for you) which version and board date is printed on the PCB of your R36S (Often found underneath the battery and looks something like: R36S-V12, 2023-08-18 for example😊

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2026-01-17 03:46:15
Thanks for your comment, however the Debian Based ArkOS (dArkOS) is as far as I know the same procedure to run use the tutorial😊

I'm GUESSING (can't confirm because I personally will most likely not be moving do Debian based, but instead have by own Ubuntu based custom Distro for these devices with the latest LTS base).

But same as for ArkOS, christian yet again strongly advices AGAINST using Balena etcher:
"DO NOT USE BALENA ETCHER WITH THIS IMAGE! There has been reports of various strange issues and inconsistent performance using Etcher for this image."

I don't know why, I never used balena etcher (I use other more direct tools on Linux), and don't know WHY it would be the case what he is reporting, but considering he states that for his project I will just stick to his guide lines in regard to that.

I DO acknowledge your comment though, because there had been a few people in the past who told me that it didn't worked with Win32imager or even rufus and that they DID had to use Balena.. I'm GUESSING it has something to do with the sd-card, the card-reader or maybe even some drivers which are different on different pc's 🤷🏽‍♀️

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2025-11-15 19:58:22
Hey, first have to make sure that you are indeed using the latest (Official or Community) ArkOS (since there can be a problem with the Chinese bootfiles (dtb). AND that you actually have a real R36S or R36H, because it could just as well like with the user CannotCannot be that you don't have an "Official R36" but an “Soy Sauce Console” for example. Which means you simply need the official boot files. for that one (which I don't have though!)😊.

I would NOT recommend just messing with system files yourself (in the Root partition that is) if mappings are incorrect. Because incorrect mappings most likely just indicate that you are already using the wrong boot files. And then you would only see "just an inverted stick" but there can (and will be) much bigger/serious problems which you (initially) don't notice like for example: Charge controller not functioning properly resulting in undercharging or even over charging the batter, overheating the console (incorrect power management) etc etc....

I would FOR AN SOY SAUCE model recommend checking this thread on GitHub: https://github.com/AeolusUX/ArkOS-R3XS/issues/95

On there is also a link provided to the correct bootfiles download 😊. IMPORTANT: Do make sure you confirm which device you exactly have!

Good luck😊👍🏽

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2025-10-13 23:07:43
Sorry, I didnt' noticed your comment any sooner, we've had quite an hectic week. I thought I had covered that in the blog post, but it turns out I did in the video, but forgot to cover it in the blog post, my apologies. I did now added a section about that issue in it.

But basically put, you can just try then one-by-one to see which one does work. But most of the time a non recognized one just turns out to be a slightly modified Panel 4 dtb file (hence why it's not recognized). If they all fail to boot, you can always try to fallback to the original backup of your "official" SD-Card and just copy those bootfiles to your R36 once it's done installing 😊

On Installing or Updating ArkOS/dArkOS (R36S & R36H) at 2025-08-25 13:12:38
Hey Johannes😊.

Nope it's indeed not a Dutch website, I'm Dutch myself though, but I've chosen to make all my content (Video's, Website, Software and other projects) in English so everyone can benefit from it and not just our 'Tiny Country' 😉😊). So thank you for taking this into account and commenting in English (since your problem might also help others world wide when they come across it now😊👍🏽).

I'm strongly suspecting yours MIGHT not be a 'real R36S', which might cause the problem. First let me ask this (and please DO NOT feel insulted😉😂, but it COULD be an problem with booting with these devices): Have you made sure it's fully charged? Although USUALLY when the battery is too low it will just give an on screen text error provided by the bootloader/ArkOS instead of the blinking red LED.

I do however still strongly 'believe' yours is unfortunately a clone which would explain the current issues you're having. I myself can't confirm it directly, but the symptoms you're describing match VERY closely with what I've heard, read and received from other developers and users whom turned out to be having an "Emulec Clone"/K36. I would recommend trying one of these links/resources to see if those will help you further:

https://handhelds.wiki/R36S_Clones#Custom_Firmware_for_the_EmuELEC_Clone

And the download from AeolusUX:
https://github.com/AeolusUX/ArkOS-K36

I THINK these will solve your problem 😊. Do you still have the original SD card though? Because if you still have the original SD-Card AND the files that where on it, then you can compare the boot files and try to swap those as a last resort. But I would recommend to just try the K36 version of ArkOS by AeolusUX😊.

IMPORTANT: Like mentioned in all my tutorials: Please DO NOT use the original SD-Card for your new installation! Those WILL be problematic and eventually even just die randomly. (They are VERY low quality SD cards)..

Good luck and keep me up-to-date if you like if it worked😊

On Installing Cheap WiFi On Your R36S or R36H (ArkOS) at 2025-08-23 16:49:46
Hi there, and welcome 😊

"I suspect it’s because the tool is designed to uninstall your driver, but the one currently on my system is a different one that came with the OS." That is indeed correct, to prevent breaking AeolusUX his system (and thus most likely causing (other) people to start complaining at his release/support tickets etc about a problem they themselves created with "my" driver, I made sure it refuses to uninstall anything which is (pre) installed on the system if it's running either AeolusUX ArkOS, OR!!! If Christian in the future adds a driver to the official ArkOS which doesn't have 'my signature' (this is a simple but common way to prevent one installation breaking other installations, which COULD become a VERY serious issue on Linux machines)...

If you would still want to proceed (at your own risk) to use my driver on AeolusUX his ArkOS then please read along 😊

Again (for ANYONE reading this in the future):
PROCEED AT OWN RISK - And this will ONLY work for the current release as of writing this (Version 1.0)!!
To let the installer ignore the AeolusUX check you could outcomments (adding # in front of the lines):
126-129 in the Install Driver.sh

and for the uninstaller you could do the same for lines 119 to 122

WARNING THOUGH: The uninstaller might (very likely) still not uninstall anything, because it is specifically made to uninstall "my" driver. However the installer should using this method install anyway... DO KEEP IN MIND: That this MIGHT cause conflicts, and I'm also NOT able to guarantee it works since I personally don't use the AeolusUX ArkOS at all on my devices.

So you could try doing these tips (mainly for the installer), but please do keep in mind that it's not intended nor tested for that version of ArkOS though. I'm GUESSING it should work, since I had it running on it back in the day I tested it, but since then AeolusUX has changed a few things and if I'm correct also added additional driver support 😊. And I have absolutely no clue in how or what would be supported in combination with my driver or what could cause issues for example..

I hope this information helped you a bit further though in experimenting 😊, Good luck👍🏽