Hacking RCM Loader One help

[pustal]

I bought an RCM Loader One and I'm having some trouble with it, namely:

- On SX OS mode it keeps complaining about not having boot.dat, although being on the root of the SD card;

- I have no idea how to boot Android. I followed the guide, flashed the card but when I get to Hekate, I doesn't boot;

Note that Atmosphere seems to boot fine so it is reading from the card. I also tried multiple SD cards for SX OS and formatting them through the Switch settings menu.

Thanks in advance for any help.

 

[cherup]

Are you sure that the SD card reader from the switch is working? With the boot.dat on the SD card it shouldn't be a problem....

Gesendet von meinem ELE-L29 mit Tapatalk

 

[pustal]

Are you sure that the SD card reader from the switch is working? With the boot.dat on the SD card it shouldn't be a problem....

Gesendet von meinem ELE-L29 mit Tapatalk

I think so, else wouldn't launch Atmosphere. Also the system menu recognizes it and formats it.

 

[RHOPKINS13]

Are you using separate micro SD cards for Android and SX OS?

I personally don't have experience with SX OS, but that image that gets flashed for Android has a weird partition structure, and it's entirely feasible that SX OS isn't looking in the right place for the FAT32 partition, and it's causing it not to find boot.dat. Try doing a complete wipe of your card, and just throw one big FAT32 partition on it, and then see if SX OS boots.

Regarding Android, you're not supposed to boot it directly the first time. You're supposed to hold VOL+ until you get to TWRP and flash gapps. Sometimes it takes a few minutes for TWRP to load.

Are you sure your microSD card is legit and not counterfeit? Try running h2testw on it. I've seen some weird stuff with counterfeit microSD cards, that say they're one size when in reality they're much smaller. I've already seen where someone has gone through all the correct procedures for setting up emunand, and everything seemed to be successful, but he still couldn't boot emunand and a counterfeit microSD card was to blame.

 

[Lazyboss]

Are you sure you choose the sx os mode? Press and hold the "+" button on the rcm loader until it flash "red" then connect it to the switch.

 

[pustal]

Are you using separate micro SD cards for Android and SX OS?

Yup. I have two 128GB card, one with Android band the other with the rest. I also tried a 32 GB one for SX OS.

Try doing a complete wipe of your card, and just throw one big FAT32 partition on it, and then see if SX OS boots.

I tried this, with both FAT32 and exFAT. When the Switch formats it, it creates and empy partition of 16MB and then formats the rest in exFAT. On Windows I deleted everything and tried formating it FAT32 first and then exFAT with no results.

Regarding Android, you're not supposed to boot it directly the first time. You're supposed to hold VOL+ until you get to TWRP and flash gapps. Sometimes it takes a few minutes for TWRP to load.

If I keep doing that a message appear on the top of the screen saying that I don't have a ReiNX folder or it is empty. WHen I flash the image it creates me a small 1.9GB FAT partion and then a big unreadable partition (in WIndwos at least). Is it supposed to be like that?

Are you sure your microSD card is legit and not counterfeit? Try running h2testw on it. I've seen some weird stuff with counterfeit microSD cards, that say they're one size when in reality they're much smaller. I've already seen where someone has gone through all the correct procedures for setting up emunand, and everything seemed to be successful, but he still couldn't boot emunand and a counterfeit microSD card was to blame.

They're legit. I tried more than one card. I bought them all on different reputable retail stores.

Are you sure you choose the sx os mode? Press and hold the "+" button on the rcm loader until it flash "red" then connect it to the switch.

I am, it's the only one that asks for the boot that. The blue - Atmosphere - mode seems to work fine.

 

[EmulateLife]

Do you have a usb type c cable? See if you can boot SX OS normally without the Loader.

--------------------- MERGED ---------------------------

Also like if you're on 8.1 cfw you need sx os 2.8 beta.

 

[pustal]

Do you have a usb type c cable? See if you can boot SX OS normally without the Loader.

--------------------- MERGED ---------------------------

Also like if you're on 8.1 cfw you need sx os 2.8 beta.

Yup Tegra works fine and boots on SX OS. Using 2.8 beta.

 

[EmulateLife]

So that basically narrows it down to some issue with the Loader. Try to reapply the payload otherwise I can't think of anything else you can do.

 

[pustal]

So that basically narrows it down to some issue with the Loader. Try to reapply the payload otherwise I can't think of anything else you can do.

I messaged both xkit and the seller. Xkit didn't answer. The seller said he'd send me a second unit.

 

[Lazyboss]

All you can do is simply connect it to the PC and replace the payload with another one, or update.
There is no need to return it.

 

[RHOPKINS13]

I seriously doubt it's anything wrong with the loader.

I tried this, with both FAT32 and exFAT. When the Switch formats it, it creates and empy partition of 16MB and then formats the rest in exFAT. On Windows I deleted everything and tried formating it FAT32 first and then exFAT with no results.

Have you tried using the exFAT partition just as it is after formatting the card using the Switch? Just add the boot.dat payload and send SX OS using the loader?

If I keep doing that a message appear on the top of the screen saying that I don't have a ReiNX folder or it is empty. WHen I flash the image it creates me a small 1.9GB FAT partion and then a big unreadable partition (in WIndwos at least). Is it supposed to be like that?

Aha! Booting Android requires Hekate, and somehow you are accidentally sending the ReiNX payload with your dongle instead of the Hekate one!
You can replace the payloads that are included with whatever payloads you want, you just have to delete the old payload and make sure the new payload is named payload.bin. BE CAREFUL! Windows likes to hide known file extensions, you could end up accidentally naming the file payload.bin.bin, which won't work. If you don't plan on using ReiNX, just replace the ReiNX payload with the Hekate one (that's what I did.)

It's totally normal for you to have only a 2GB FAT partition you can use in Windows, and Windows doesn't recognize the rest. That's perfectly fine, make sure you follow the instructions EXACTLY. After flashing the card, remove it, and put it back in your computer. Windows will complain that partitions need to be formatted, hit cancel when anything like that pops up. The FAT32 partition should already have bootloader files for Hekate, but you do need to copy gapps to it, along with the shieldifier zip if you choose to (I did.)

Start Hekate, go to "More Payloads", and hold down the VOL+ button before and while tapping on Switchroot. Don't let go of the VOL+ button until you're in TWRP (it could take a few minutes to load.)

 

[pustal]

I seriously doubt it's anything wrong with the loader.



Have you tried using the exFAT partition just as it is after formatting the card using the Switch? Just add the boot.dat payload and send SX OS using the loader?

Yup, no change.

Aha! Booting Android requires Hekate, and somehow you are accidentally sending the ReiNX payload with your dongle instead of the Hekate one!
You can replace the payloads that are included with whatever payloads you want, you just have to delete the old payload and make sure the new payload is named payload.bin. BE CAREFUL! Windows likes to hide known file extensions, you could end up accidentally naming the file payload.bin.bin, which won't work. If you don't plan on using ReiNX, just replace the ReiNX payload with the Hekate one (that's what I did.)

I tried this, no change. Newer version of Hekate just crash the console through the RCM Loader One.

 

[xabier]

Yup, no change.



I tried this, no change. Newer version of Hekate just crash the console through the RCM Loader One.

Have you tried replacing the payloads on the dongle with new ones from the internet? There is a new hekate, sx payload hasn't changed since it was released but there is no harm in overwriting it with a fresh one. You can download from xecuter download page - sx loader 1.0 and overwrite the file on the dongle

 

[RHOPKINS13]

I tried this, no change. Newer version of Hekate just crash the console through the RCM Loader One.

What do you mean by "crash the console"? Can I get a picture? What error are you getting?

 

[CreAtor135]

You sure it's the rcmloader? Have you tried the standard method of sending payloads to your switch? (USB cord, jig and PC)

 

[pustal]

Have you tried replacing the payloads on the dongle with new ones from the internet? There is a new hekate, sx payload hasn't changed since it was released but there is no harm in overwriting it with a fresh one. You can download from xecuter download page - sx loader 1.0 and overwrite the file on the dongle

I tried replacing with no success. But it did work after putting the payload on the first user profile. Odd. I'll try later today the latest Atmosphere on the second user profile.

What do you mean by "crash the console"? Can I get a picture? What error are you getting?

No error, a very fast booting screen, then blacks and shutdown.

You sure it's the rcmloader? Have you tried the standard method of sending payloads to your switch? (USB cord, jig and PC)

I did for SX OS but not for Android yet. I'll try tonight as well as the new profile thingy.

 

[pustal]

Have you tried replacing the payloads on the dongle with new ones from the internet? There is a new hekate, sx payload hasn't changed since it was released but there is no harm in overwriting it with a fresh one. You can download from xecuter download page - sx loader 1.0 and overwrite the file on the dongle

I tried as the latest Atmosphere on the second user folder and it worked . I also tried with Kosmo's payload and it works