Booting ofw while Auto-rcm is on?

[Windsall]

I wanted to ask a few things around auto-rcm.

1) I saw someone say that booting stock from hekate isn't 100% clean. Is that true? Is there any risk (like of online ban) due to booting that way from having auto-rcm?

2) When I try to 'reboot' into ofw from hekate with auto-rcm on, it just goes into rcm instead of the ofw. Is there a way to change this? (I want it to go into ofw directly)

3) My ofw is updated but not hakate and atmosphere, and I haven't been able to launch the stock option in hekate. I wanted to know if there's a way to boot stock without updating hekate and atmosphere. I don't really want to do that everytime there's a new update on the ofw.


Any info around this is appreciated.

 

[binkinator]

I wanted to ask a few things around auto-rcm.

1) I saw someone say that booting stock from hekate isn't 100% clean. Is that true?

Many people boot stack from Hekate. There is nothing untoward about doing so.

Is there any risk (like of online ban) due to booting that way from having auto-rcm?

None at all

2) When I try to 'reboot' into ofw from hekate with auto-rcm on, it just goes into rcm instead of the ofw. Is there a way to change this? (I want it to go into ofw directly)

You should create a stanza in your hekate_ipl.ini along with up to date Atmosphere and Hekate and you will be able to boot OFW from inside Hekate like everyone else.

3) My ofw is updated but not hakate and atmosphere, and I haven't been able to launch the stock option in hekate. I wanted to know if there's a way to boot stock without updating hekate and atmosphere. I don't really want to do that everytime there's a new update on the ofw.

You only need to be as up-to-date as your firmware and that only needs to be done if you run into a game that requires the next version so this is not something you will need to do on a regular basis.

Any info around this is appreciated.

Anyone else feel free to chime in...

 

[Windsall]

You should create a stanza in your hekate_ipl.ini along with up to date Atmosphere and Hekate and you will be able to boot OFW from inside Hekate like everyone else.

I don't know what a stanza is. And I'm guessing you mean the usual going to 'launch' instead?

You only need to be as up-to-date as your firmware and that only needs to be done if you run into a game that requires the next version so this is not something you will need to do on a regular basis.

I use stock/ofw mainly to play online games, which means I have to stay up to date with ofw to play those.
I don't like the idea that everytime my system firmware updates I have to wait for a new version of hetake+atmosphere and load those up, just to go back into stock.

Thought to ask in a thread to see what people knew. Though you've been very helpful.

 

[binkinator]

I don't know what a stanza is. And I'm guessing you mean the usual going to 'launch' instead?

Used stanza to mean a section of your hekate_ipl.ini so you have a CFW/Emunand stanza and a Sock stanza etc., etc. just a group of lines that go together.

I use stock/ofw mainly to play online games, which means I have to stay up to date with ofw to play those.

Perfect. I do the same.

I don't like the idea that everytime my system firmware updates I have to wait for a new version of hetake+atmosphere and load those up, just to go back into stock.

You don’t. It’s just that you are behind at the moment and need to upgrade to match your firmware.

Thought to ask in a thread to see what people knew. Though you've been very helpful.

Anyone else care to chime in and correct where I have gone astray? Please do so.

 

[Windsall]

You don’t. It’s just that you are behind at the moment and need to upgrade to match your firmware.

I wasn't far behind. I updated everything for 14.0.1 or a bit higher.

Though even if it was pretty sparsed out, I still want to know if there's a way to get to stock without updating things xD.

 

[binkinator]

Here’s the error for those following along:

I have another issue right now, and I don't understand why.

When I try to boot into stock firmware from hakate, it gives me this error:

"Unknown pkg1 version.
HOS version not supported!
Trying backup bootloader...
Found pkg1 <*numbers*>.

[repeate msg]

Failed to launch HOS!

press any key"

And it goes back into hekate when i press a system button.

 

[randy_w]

I don't like the idea that everytime my system firmware updates I have to wait for a new version of hetake+atmosphere and load those up, just to go back into stock.

That's what you have to put up with if you want to run cfw on your switch..
Good thing is you usually only need to update hekate/atmosphere/sigpatches after a major update, like from 13.2.1 to 14.0.0 and from 14.1.2 to 15.0.0. Also new atmosphere build are usually released within 1-2 weeks so it isn't that bad. Iirc nintendo also gives you some grace period after an update is released and you can keep using the old firmware for like a week or two.

I don't know what a stanza is. And I'm guessing you mean the usual going to 'launch' instead?

Yes it means to create an entry in your hekate_ipl.ini to boot to ofw, if you don't have one already add following lines to the ini file:

[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1

Note it also boots with package3 from atmosphere, so you have to keep atmosphere up to date.

Reboot to ofw from reboot menu works for my chipped oled switch, maybe it's autorcm causing the problem. Try disabling it and see if reboot to ofw works.

 

[Windsall]

Here’s the error for those following along:

I updated atmosphere and hekate and it worked now. So it was really just them being out of date. So now we know that's what it is.

That's what you have to put up with if you want to run cfw on your switch..
Good thing is you usually only need to update hekate/atmosphere/sigpatches after a major update, like from 13.2.1 to 14.0.0 and from 14.1.2 to 15.0.0. Also new atmosphere build are usually released within 1-2 weeks so it isn't that bad. Iirc nintendo also gives you some grace period after an update is released and you can keep using the old firmware for like a week or two.

That's good to know. It's unfortunate though that it would need those updates just to boot into stock. It makes auto-rcm not as simple .

Reboot to ofw from reboot menu works for my chipped oled switch, maybe it's autorcm causing the problem. Try disabling it and see if reboot to ofw works.

Yeah it's due to auto-rcm I'm pretty sure. I thought they'd have a way to do it with that option but I guess auto-rcm makes it hard to boot normally or something.


If anyone knows of a way please do post. Else I guess I'll assume there isn't really a way, when using auto-rcm

Thx for the info up to now.

 

[Ragna666]

this is the original untouched hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=0
updater2p=1


{--- Custom Firmware ---}
[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

this works f*ckin fiiiine.

just replace this line:

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp

with this:
[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp

it's gonna look like this:

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=0
updater2p=1


{--- Custom Firmware ---}
[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

and now you can't start cfw sysmmc accidentally.
just only ofw sysmmc and cfw emummc.