Hacking Hacked switch help.

[Deleted member 475203]

.

 

[User154]

You need sigpatches and to boot from fusee, I dont think either of those things are covered in that guide.

https://rentry.org/EristaEmuNAND

Copy sigpatches and fusee as described in step 2 and 3 and then edit your hekate_ipl.ini to look like the one in step 3

 

[Deleted member 475203]

.

 

[aoikurayami]

It's just a name of a part of the atmosphere firmwre stuff.
Don't mind it
Just place all the proper files on your sd.

PS:
Sigpatches are *not* necessarily needed to boot.

Everything needed to boot is found here
https://github.com/Atmosphere-NX/Atmosphere/releases

1. Put files on SD
2. Make sure switch is off, insert SD
3. Insert rcm thing (or use your pc\smartphone)
3.5 insert jig into right rail
4. hold "vol+" and press power
5. it should boot (or at least show a message)


==Sigpatches==
You will need them to boot any *non official downloaded* softwarey even everything installed via goldleaf\tinwoo\etc

@Costello @shaunj66
Can we have a "NintendoSwitch" Noob section ?
I feel like this mirrors the olden "I just bought my r4 halp!" or "can I have free pokeymanz" days...
GBA was relatively safe from these. Bless the lil cutie

 

[Deleted member 475203]

.

 

[H1B1Esquire]

now whoor

I had a similar issue, but I resolved mine by using title override (holding R while launching a game) and installing that way. It's a catch-22 initially, but install a small (less than 300 Mb from released 2017-2020 to be sure of FW reqs.) game or the HBL.nsp.

Basically: every title would crash or show blank/wheel until I used
atmoXLtit
to get one title that let me use override for non-applet DBI



I think you need this for YT:
I theenk

 

[Deleted member 475203]

.

 

[Deleted member 475203]

.

 

[H1B1Esquire]

hat yo

If you can use RAM, get a .nsp and atmoXL.nro in your SD in your Switch folder, load it, find your .nsp and tell me if it works.

I'm maybe pointing at your FW as the cause...but it's a maybe.

a noob section.

A noob warning, like, use broad search terms, then work to specifics.

 

[Deleted member 475203]

.

 

[H1B1Esquire]

....

i tried to install with atmoxl via usb,

mai du, you may need to explain a little more......I told you to put the atmoxl.nro and whatever .nsp on your SD....this will make troubleshooting easier.

If you can't use your SD normally and you've been using .mtp, you need to say that....it may seem minimal, but it might be the thing that narrows your problem.


At this point tho, I'm going to recommend you try the AIO on a new SD so you can verify it works and copy the contents (minus the Nintendo folder) back to your OG SD.

Do you have a spare MSD above 4GB?

 

[Deleted member 475203]

.

 

[H1B1Esquire]

mai du" me

my dude.....

i tried to install with atmoxl via usb

+

atmoxl.nro IS on sw in switch folder, hence me runing it from homebrew menu.

=
k.

took out the card phisically and inserted it into a SD card reated on my PC.

+

just seems like a lot of work for just installing a single homebrew app...

=
but it really isn't...its like, an absolute test that, if it works, can become your new litmus test for troubleshooting.

Okay...let's start over.

0. What FW are you on?
1. Can you use a new Micro SD?
2. Put that MSD into your switch to generate a "Nintendo" folder.

 

[The Real Jdbye]

It's just a name of a part of the atmosphere firmwre stuff.
Don't mind it
Just place all the proper files on your sd.

PS:
Sigpatches are *not* necessarily needed to boot.

Everything needed to boot is found here
https://github.com/Atmosphere-NX/Atmosphere/releases

1. Put files on SD
2. Make sure switch is off, insert SD
3. Insert rcm thing (or use your pc\smartphone)
3.5 insert jig into right rail
4. hold "vol+" and press power
5. it should boot (or at least show a message)


==Sigpatches==
You will need them to boot any *non official downloaded* softwarey even everything installed via goldleaf\tinwoo\etc

@Costello @shaunj66
Can we have a "NintendoSwitch" Noob section ?
I feel like this mirrors the olden "I just bought my r4 halp!" or "can I have free pokeymanz" days...
GBA was relatively safe from these. Bless the lil cutie

We have a thread for that. I don't think we need an entire section.

 

[Deleted member 475203]

.

 

[H1B1Esquire]

I'm just having really hard time following you.

Click my profile pic, look next to "gift" on the left, there you'll find "follow"; it;s just that easy!

Surasely, I think I see something you might want to look into:
DBI and the DBI backend; it was updated 16 hours ago.

dbi and backend. exe

Personally, I just had an issue where Awoo, atmoxl, etc, weren't installing anything....and then DBI backend gave me my answer.....also reminded me about sigpatches.


Also, like I said, a new SD is for tests. This way, when you try a bunch of shit and it doesn't work, you reduce the chances of having to start from scratch.....but s'coo.

 

[HalfScoper]

No need for the backend. Just use the MTP responder function, open the fifth folder called "SD installation" and drag and drop your desired backups in there.

 

[Deleted member 475203]

.

 

[HalfScoper]

No offense but maybe Switch hacking isn't recommendable for you.
https://rentry.org/NSUSBInstall/#dbi-installer-mtp

 

[JackTheFroster]

No offense but maybe Switch hacking isn't recommendable for you.
https://rentry.org/NSUSBInstall/#dbi-installer-mtp

i think its just hard to follow anything when you try it for the first time... many things got me confused too at the beginning of hacking. still, if you want to understand, you first need to start learning and its hard if people recommend things here and there and nothing gets fixed.

i tried to install with atmoxl via usb, but same warning, signature check and failed to install when i said i want to continue.
if this helps, i use some lockpick payload, thats whats its called i think... its not fusee, but i have it in hekate to choose... im saying this even though i have no idea what this is but people mentioned it somewhere so if helps it helps...

First of all, lockpick just needs to be runned once since it will just create a keys file. the keys file is used for various things to work, i cant remember for what exactly though.

2. what payloads do you have in the bootloader/payloads folder on the sd card? and did you change your hekate_ipl.ini already? it should look like this:

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=30
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
{}

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/atmosphere.bmp
{}

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


https://github.com/CTCaer/hekate#bootloader-configuration < this should explain most of the config in the .ipl file if you want to understand it better. if you use custom icons, make sure it redirects to the correct .bmp file for every boot option. be sure to have the line "kip1patch=nosigchk" in the boot option you want to use, since it enables the sigpatches (make sure you have the latest ones installed).

3. If you are always booting from hekate and there are still errors, try booting from fusee.bin