When I found out I had a V1 Switch, I homebrewed it as soon as I was able, and ripped all my games to put them onto an emulator. After looking further into it, I found that homebrewing could improve the console experience as well. I’m eager to use it, but I’d rather not manually inject a payload every time through Tegra. Are there any ways to make the Switch boot into a payload like Hekate?

  • ubergeek77@lemmy.ubergeek77.chat
    link
    fedilink
    English
    arrow-up
    13
    ·
    1 month ago

    If you don’t want to open this and solder a chip, then no, you can’t do what you want.

    The closest you can get is to enable AutoRCM, which will cause the Switch to always boot into recovery mode and accept a payload. This skips the need to use a jig in the Joy-Con rail, but you still need to inject a payload. And because recovery mode is just a black screen, you don’t have any visual feedback to know if the Switch is actually in recovery mode, or if the battery is just dead.

    Your best option is to just boot into whatever OS you use most, then make it a habit to keep it charged enough to not shut down.

  • conciselyverbose@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    My experience is that I only have to do anything if it shuts all the way down. You can reboot from the power menu and it goes back to selecting which firmware to boot.

    I don’t ever use the regular firmware on it though.

  • Venia Silente@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    30 days ago

    Boot it once, don’t let it ever fully power down (suspend is fine).

    If your V1 is on firmware 3.1 or 4.1 but does not work with the RCM jig and you have run your serial ID through the test site and it comes up as “possibly ipatched”, you might be able to use “online boot” via Pegascape, which you can also host locally (eg.: in a raspberry pi) and there is at least one alternative frontend. It’s pretty much the only way to boot an ipatched > 3.x into hekate without a hardmod, and even then it’s only limited to firmware 4.x that I know.

    (On such a setup, you’d then install an eMMC partition for CFW with the firmware you want, eg.: 16.x).