Hacking RCMLoader One + SX OS

  • Thread starter Thread starter parpagnas
  • Start date Start date
  • Views Views 6,006
  • Replies Replies 8

parpagnas

Member
Newcomer
Joined
Dec 22, 2019
Messages
7
Reaction score
0
Trophies
0
Age
125
XP
116
Country
France
Hello,

I double-checked that my switch is supported so i bought the rcmloader. At first I thought i'd be using atmosphere... Then i got frustrated cause it would not work, nor would reinx, so I bought the license for sx os and it fails as well...I've been trying to get this to work for a week and i havn't been able to get it to work a single time...

I searched over the internet but found very little on the RCMloader One and its usage. It comes with 3 payload.bin, fine, but looking at the internet it seems that this won't work if you don't add additional files on the sd card, right? So i tried updating the payload.bin, then to copy the associated files on the sd card. But it's been failing for everything.

I also tried downloading files from a video i can't link here because i'm new to the forum and it didn't change anything...

So, as i bought the sx os license, i've been focusing on getting this to work (i know i should have bought the dongle + the license instead...). I have downloaded the 2.9.2 boot.dat and put it at the root of the sd card, as well as the corresponding license.dat.
It boots well on the sx os payload where you can slect the regular or the custom firmware and setup Options. I went to Options, backed up the nand then i tried to have the emunand format the sd it didn't work, so I tried to have the emunand files be copied to the sd card but it's failing as well.

So, it boots on sx os payload, i get the menu where i can boot the regular or a custom firmware or options. When i select custom firmware it gets to a black screen and nothing else happens (whether emunand is activated or not). It never gets to the sx os i have seen on the net, not onto the regular firmware from there. I checked and when i select to boot on the regular firmware there no homebrew or anything in "album".

What's confusing me is that it allows to boot other payloads... Am I missing something here? Can it boot on the sx os real interface where i can select homebrew, xci etc without running another payload???

Thanks
 
I forgot to add that I have succesfully upgraded RCMLoader to the firware 1.2, and that I read another thread here (i can't link as i'm new here) but all the links in this other thread are dead, and the video didn't help much...
 
SX Os should work out of the box if you have the boot.dat on your microsd. The loader does not contain any cfw files itself, just the payloads. Cfw goes on microsd.
The menu you're speaking of is the launcher, you use this to boot into the cfw. You cannot run any homebrew or games from there.
Why you only get a black screen, that I don't know.
 
Thanks @wurstpistole :) Ok, then I think that is what i don't understand... What else than the boot.dat must be installed on the sd card? What do you mean by cfw here? There's more to sx os (or atmosphere?) to install on the sd card to run the games?
I think i'm missing the connection between the payload and the cfw, i thought it was the same thing...
 
So, i got it to work, finally. I followed what's written on the switch guide nh-server github io, and added some files to what i had alread put on the sd card, some would overwrite so i didn't overwrite. Once i reboot it worked...
I suspect that what made the difference is that I put hekate files on the sd... whereas i had only put atmosphere files... Can one confirm maybe?

My problem now is that i would like to understand this in depth, on only put what's required there and nothing more. So I can write a knowledge article somewhere, for dummies like me :).

Further help from you guys would be much appreciated
 
Here is the thing: none of the tutorial i found explain how to use sx os + rcmloader. I still don't know why it is working now. What specific file(s) was mandatory for sx os to actually boot on a custom firmware successfully, and that's my main concern...

Also, I find it odd that neither xyz and team executer do not provide any doc on this, even though i suspect this is to protect themselves from dmca or whatever...
 
Here is the thing: none of the tutorial i found explain how to use sx os + rcmloader. I still don't know why it is working now. What specific file(s) was mandatory for sx os to actually boot on a custom firmware successfully, and that's my main concern...

Also, I find it odd that neither xyz and team executer do not provide any doc on this, even though i suspect this is to protect themselves from dmca or whatever...
You should not need anything else than the boot.dat and possibly the license file on your SD to boot into sxos. At least that was the case when I got my switch about a year ago.
Anyway, you got it to work so all is good!

Skickat från min ONEPLUS A6003 via Tapatalk
 

Site & Scene News

Popular threads in this forum