Hacking SWITCH NOOB PARADISE - Ask questions here

[Nightf0x]

Hello everybody

My switch is mariko, sx core modchipped, ofw 11.0 as far as i remember, sx os 3.1.0, i havent been using it for a while

It was having retroreloaded installed and ofw sysnand and cfw sx os emmunand with measures to prevent ban installed also, since i bought it i never booted to the ofw, this was the setup the guy i bought from was having

Now i wanted to migrate from sx os to atmos and update the switch, so i followed this tutorial (i know files inside is outdated) https://github.com/dsync89/Ultimate-Guide-to-Migrate-SXOS-SX-Core-to-Atmosphere Until step 2.1b and the switch wont boot only blue light blinking (to turn if off i press power&vol+)

Idk what to do actually, note that i backed up all the sd card contents before i do anything, can i simply delete all the sd cards contents and copy back the initial contents as it was? Will this get the switch back as it was before i begun with the tutorial? Or what should i do?, I want to migrate to atmos and have the sysnand with lastest ofw, now my switch is just blinking blue and also i dont mind formatting my switch and starting from scratch

Thanks

 

[tlfrance]

The guide would not have left you on Atmosphere 1.3.0. Is there a reason you insist on not following everything exactly as written?

--> What do you mean? I've followed exactly https://rentry.org/ExosphereDNSMITM and https://rentry.org/MigrateToAtmosphere1_0_0

It would be helpful to those trying to help you if you would do. Otherwise we are forced to guess what you might be doing (or not doing) properly.

Please post the contents of the following files:

/atmosphere/hosts/defaults.txt
/bootloader/hekate_ipl.ini
/exosphere.ini

Here my files .
There is a open thread relating to "tsec_keygen firmware" on SXOS Pro USB dongle"

 

[binkinator]

hmm, the reason I ask and beginning to suspect it only runs full speed when docked is because of a recent update in fortnite.

they have changed a lot and there are situations now where there is a hell of a lot going on and I suffer massive slowdown and hitting something like 5fps which does not clear up till I get away from that area and there does not seem to be any difference between battery and plugged in via USB cable.

i always play fortnite in handheld mode in bed at night so going docked to try it isn't the easiest.

Have you added Tesla Menu + Overlay with Status Monitor Overlay with NX-FPS? Tis stack will tell you in real time what your clock speeds are. Will remove all doubt. :-)

 

[binkinator]

--> What do you mean? I've followed exactly https://rentry.org/ExosphereDNSMITM and https://rentry.org/MigrateToAtmosphere1_0_0

What I mean is the links on that page go to 1.3.2 rather than 1.3.0. Makes me suspicious on what else might have been missed when we go through everything but the release numbers don’t match.

Here my files .

Great! The exosphere.ini and defaults.txt both look great.

There is a open thread relating to "tsec_keygen firmware" on SXOS Pro USB dongle"

I remember helping out in that thread. We will do the same thing in this case.

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

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

in your hekate_ipl.ini remove the line I struck through and add the line I made bold.

After that you should be able to boot Atmosphere from the SXOS 4th icon in the boot menu.

e: you should also check out fastCFWSwitch because it allows you to boot SXOS directly from Atmosphere and Atmophere directly from SXOS. Super convenient if you’re going to dual boot!

 

[steve_fox]

Have you added Tesla Menu + Overlay with Status Monitor Overlay with NX-FPS? Tis stack will tell you in real time what your clock speeds are. Will remove all doubt. :-)

Is that a cfw thing? I'm playing fortnite on stock fw.

 

[NotSolaxy]

So originally I had an error on Tinfoil where it said "Unable to start software." But when I updated my sigpatches and hekati files, it worked, but when I install a game it says "Checking if game can be played..." I tried everything. But when I used my original sigpatches, I get the "Unable to start software" error. Any help? Thanks!

 

[Draxzelex]

So originally I had an error on Tinfoil where it said "Unable to start software." But when I updated my sigpatches and hekati files, it worked, but when I install a game it says "Checking if game can be played..." I tried everything. But when I used my original sigpatches, I get the "Unable to start software" error. Any help? Thanks!

I highly recommend switching to using TinWoo Installer instead. Its what I personally use and I have never ever run into any issues while using it.

 

[NotSolaxy]

Does it have a shop on it?

 

[Draxzelex]

Does it have a shop on it?

No but shops are dead and bad for the scene. Majority of the community don't use shops and we all are able to pirate Switch games without issue.

 

[Nightf0x]

Hello, my mariko switch while i was migrating from sx os to atmos wont boot up now only rhe sx modchip blinks blue, what to do? I dont mind to format the switch and lose all the data and start feok scratch

 

[binkinator]

Is that a cfw thing? I'm playing fortnite on stock fw.

Yes, It is absolutely a CFW thing. That said, you could play any other game to find out what happens between docked, undocked, powered or not (or any other permutations your heart desires) and be relatively sure the same clock speeds would carry over to Fortnite.

 

[877]

If I have autorcm enabled from updating firmware with ChoiDeJourNX, does that mean my sysNAND is not clean? I.e. would get online banned?

Any way to check if my sysNAND is clean? Pretty sure I only installed NSP’s to SDcard.

 

[binkinator]

If I have autorcm enabled from updating firmware with ChoiDeJourNX, does that mean my sysNAND is not clean? I.e. would get online banned?

AutoRCM is really just minor but intentional “corruption” that prevents the boot process from continuing. Although I would doubt anyone would be banned for corruption of their file system it always pays to read through the ban hub for specific first hand accounts.

Any way to check if my sysNAND is clean? Pretty sure I only installed NSP’s to SDcard.

the only way I’m aware of to be sure your Sysnand is clean is to restore from a clean Sysnand backup. You will need things to be the way they were the last time your system contacted Ninty, including the state of your logs, which will be hard to duplicate without a backup.

PS Choi is out of date. You should seriously consider using Daybreak to update Firmware moving forward.

 

[NotSolaxy]

Hey Draxzelex, I found a new issue, I used Lithium and even on there it says "Checking if game can be played..." Tinwoo also doesn't show up but I much rather fix this issue than Tinwoo.

 

[NotSolaxy]

Golden leaf also doesn't work either, FYI.

 

[binkinator]

Golden leaf also doesn't work either, FYI.

The error you got is sometimes related to your user profile. Do you have more than one profile? If so you might want to remove one and then reinstall tinfoil and then the games under one user profile.

e: did you install the installable tinfoil.nro using title override? Tinfoil will behave strangely if you install it in applet mode.

e2: Curious what errors you got under Tinwoo and goldleaf. @Draxzelex knows what he’s talking about. Tinwoo (and goldleaf) are both about the most straightforward installers out there. Low bar of entry and trouble free. Others have more bells and whistles but come with complications. Trouble at this level might point to a much larger problem. Besides, it’s nice to have installer options on hand. I run all three plus DBI myself.

 

[877]

AutoRCM is really just minor but intentional “corruption” that prevents the boot process from continuing. Although I would doubt anyone would be banned for corruption of their file system it always pays to read through the ban hub for specific first hand accounts.

the only way I’m aware of to be sure your Sysnand is clean is to restore from a clean Sysnand backup. You will need things to be the way they were the last time your system contacted Ninty, including the state of your logs, which will be hard to duplicate without a backup.

PS Choi is out of date. You should seriously consider using Daybreak to update Firmware moving forward.

Thank you binkinator!

I think I have a clean NAND backup from when I first had the switch years ago, however not sure if I burned fuses accidentally after that backup. So not sure that’s any use?

The console has never been online as far as I remember..

 

[Vyrnox]

hey all
i have a question about nintendo mariko
i have sx modchip i just installed few days a go and now im currently using hakate and them i boot for atmosphere my question is how can i boot with OFW since i dont have any opiton on hakate is a way to create one?
many thanks

 

[binkinator]

Thank you binkinator!

I think I have a clean NAND backup from when I first had the switch years ago, however not sure if I burned fuses accidentally after that backup. So not sure that’s any use?

The console has never been online as far as I remember..

Ideally you would make a new backup every time you upgrade your Sysnand Firmware but it’s rare to find anyone with that kind of discipline. You can check your burned fuses via Hekate and compare it to this list:

https://switchbrew.org/wiki/Fuses#Anti-downgrade

 

[binkinator]

hey all
i have a question about nintendo mariko
i have sx modchip i just installed few days a go and now im currently using hakate and them i boot for atmosphere my question is how can i boot with OFW since i dont have any opiton on hakate is a way to create one?
many thanks

This added to your current /bootloader/hekate_ipl.ini file should do it:

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

edited: for clarity