Hacking SWITCH NOOB PARADISE - Ask questions here

[iepuras]

Unfortunately so. There have been bans from all companies involved..

“…anyone caught “modifying save data” will be banned.”


https://apptrigger.com/2021/01/26/nintendo-hacked-pokemon/
https://www.destructoid.com/the-pok...n-on-pokemon-sword-and-shield-cheaters-again/

ooh. do you know if anyone has reported getting banned for this yet?

 

[binkinator]

ooh. do you know if anyone has reported getting banned for this yet?

Yes, there have been reports in the Switch Banning Hub of people getting banned for game save hacks. IMO it’s on the lower end of offenses...not an insta-ban like playing nsp backups. Might want to ask people on the Hub who have actually been banned. I’m currently speaking about things I’ve not experienced first hand so I’m out of my comfort zone a little.

 

[tlfrance]

Good deal. It is absolutely achievable. We will walk you through it.

so everything works 100% at this point? We need to make sure before we go on to the next step. Let’s be sure to fix any errors before we add new things.

what is the exact words of the error that you see when you try to boot?


@tlfrance

Moving this conversation over here. I hope you don’t mind.

yes, please send a screenshot of the error. We will figure out what is going on with this upgrade. I just need to get a feel for where we are before we move forward.

Hi,
From system version that works without errors (just removed \atmosphere\contents\0100000000000081 that caused error) :

11.0.0|AMS M.19.4|E

Step 2:

• Downloaded "atmosphere-1.3.0-master-b69fa1357+hbl-2.4.1+hbmenu-3.5.0.zip" and unzip all to sdcard /root)
• Downloaded "fusee.bin" and copy to SDcard /root and /bootloader and /atmosphere (not sure where it can be copied)
• Boot on CFW with sxos pro dongle --> AvS menu displayed ok
• Click on Atmosphere button

Atmophere starting and had this error:

 

[binkinator]

Hi,
From system version that works without errors (just removed \atmosphere\contents\0100000000000081 that caused error) :

11.0.0|AMS M.19.4|E

Step 2:

• Downloaded "atmosphere-1.3.0-master-b69fa1357+hbl-2.4.1+hbmenu-3.5.0.zip" and unzip all to sdcard /root)
• Downloaded "fusee.bin" and copy to SDcard /root and /bootloader and /atmosphere (not sure where it can be copied)
• Boot on CFW with sxos pro dongle --> AvS menu displayed ok
• Click on Atmosphere button

Atmophere starting and had this error:

start here: https://rentry.org/ExosphereDNSMITM

After that I highly recommend getting the files from this tutorial.

https://rentry.org/MigrateToAtmosphere1_0_0

Following this guide and using the file download links inside should clean up those errors and get you 100% up to date. 9it even tells you what to do with that fusee.bin file…very important.)

 

[HelloShitty]

Is this the site we should look ar for error codes like for isntance:
https://switchbrew.org/wiki/Error_codes

Error Code: 2016-0060

And how do we search this error in that site, if that is the sit to searc at???

 

[binkinator]

Is this the site we should look ar for error codes like for isntance:
https://switchbrew.org/wiki/Error_codes

Error Code: 2016-0060

And how do we search this error in that site, if that is the sit to searc at???

I searched that page for 2016 by itself and 0060 by itself, trying to get at least the right section, but didn‘t get anywhere.

I believe that one is Tinfoil specific, at least that’s what comes up with good old Google.

 

[HelloShitty]

I searched that page for 2016 by itself and 0060 by itself, trying to get at least the right section, but didn‘t get anywhere.

I believe that one is Tinfoil specific, at least that’s what comes up with good old Google.

Yeah, I found some reddit posts about it too. Actually I was searching to try to answer to a post there with this error!
It's a way of learning something. Just like you do here. Searching for others!

 

[Matoxed]

Hi, i'm looking for a PC memory editor for my switch on atmosphere 1.3.2.

I know edizon but it's not practical ...

I've tried mdbell/Noexes but it didn't work out .

Thanks !

 

[Matoxed]

Hi, i'm looking for a PC memory editor for my switch on atmosphere 1.3.2.

I know edizon but it's not practical ...

I've tried mdbell/Noexes but it didn't work out .

Thanks !

EDIT : it's fine, NoExes working great !

 

[877]

Hi all,
I want to view game hours played but nothing shows in profile, just ‘Link account’. But I don’t have a Nintendo account and the switch is blocked from internet.

I have original unpatched switch, autorcm enabled, sxos3.1.0 and firmware 11.0.0.

Any ways to view game hours played? Or maybe a homebrew solution?

Thanks!

 

[Dothackjhe]

I have an unpatched Switch on firmware 14.0.0, runs on Atmosphere 1.3.2, and has the latest sigpatches. But for some reason, Fire Emblem Warriors (2017), which used to work just fine with my unit, suddenly stopped working. I'm getting the "software was closed because an error occurred" whenever I try to start the game.

Here are the steps I tried to remedy the problem, but to no avail:

• Check the game's integrity: there's no corrupt file
• Uninstall and then reinstall the game

Any idea on what's causing this and how do I fix it?

 

[Draxzelex]

Hi all,
I want to view game hours played but nothing shows in profile, just ‘Link account’. But I don’t have a Nintendo account and the switch is blocked from internet.

I have original unpatched switch, autorcm enabled, sxos3.1.0 and firmware 11.0.0.

Any ways to view game hours played? Or maybe a homebrew solution?

Thanks!

https://gbatemp.net/threads/nx-activity-log-view-slightly-more-detailed-play-statistics.549370/

I have an unpatched Switch on firmware 14.0.0, runs on Atmosphere 1.3.2, and has the latest sigpatches. But for some reason, Fire Emblem Warriors (2017), which used to work just fine with my unit, suddenly stopped working. I'm getting the "software was closed because an error occurred" whenever I try to start the game.

Here are the steps I tried to remedy the problem, but to no avail:

• Check the game's integrity: there's no corrupt file
• Uninstall and then reinstall the game

Any idea on what's causing this and how do I fix it?

I recommend following the suggestions in this thread to see if they help solve your issue.

 

[tlfrance]

start here: https://rentry.org/ExosphereDNSMITM

After that I highly recommend getting the files from this tutorial.

https://rentry.org/MigrateToAtmosphere1_0_0


Following this guide and using the file download links inside should clean up those errors and get you 100% up to date. 9it even tells you what to do with that fusee.bin file…very important.)

Hi,
I've followed this guide, and able to boot to Atmos 1.3.0 via Hekate and load fusee.bin payload. But i've 1 error (failes to run tsec_keygen firmare):

after pressing power, atmos boot well. I'am able to run tinfoil and other apps.
I've upgraded FW to 13.2.0 without issue.

Step 3:

• Fix this tsec error
• Launch atmos directly by clicking Atmosphere under AvS screen without loading hekate --> copy fusee.bin to Atmosphere folder and rename it to fusee-primary.bin ?

 

[binkinator]

Hi,
I've followed this guide, and able to boot to Atmos 1.3.0 via Hekate and load fusee.bin payload. But i've 1 error (failes to run tsec_keygen firmare):
View attachment 309292

after pressing power, atmos boot well. I'am able to run tinfoil and other apps.
I've upgraded FW to 13.2.0 without issue.

Step 3:

• Fix this tsec error
• Launch atmos directly by clicking Atmosphere under AvS screen without loading hekate --> copy fusee.bin to Atmosphere folder and rename it to fusee-primary.bin ?

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? 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

 

[steve_fox]

I know that the switch runs the CPU at its rated speed when docked and under clocks it on battery but is the full speed mode only when docked or does it run at full speed when plugged in to any external power source?

 

[binkinator]

I know that the switch runs the CPU at its rated speed when docked and under clocks it on battery but is the full speed mode only when docked or does it run at full speed when plugged in to any external power source?

That’s a tough one. There’s a little info at the bottom of the sys-clk readme on GitHub but it’s not real declarative.

https://github.com/retronx-team/sys-clk

Spoiler: Readme

Capping​

To protect the battery from excessive strain, clocks requested from config may be capped before applying, depending on your current profile:

​	Handheld​	Charging (USB)​	Charging (Official)​	Docked​
MEM​	-​	-​	-​	-​
CPU​	-​	-​	-​	-​
GPU​	460​	768​	-​	-​

Clock table (MHz)​

MEM clocks​

• 1600 → official docked, boost mode, max clock
• 1331 → official handheld
• 1065
• 800
• 665

CPU clocks​

• 1785 → max clock, boost mode
• 1683
• 1581
• 1428
• 1326
• 1224 → sdev oc
• 1122
• 1020 → official docked & handheld
• 918
• 816
• 714
• 612

GPU clocks​

• 921 → max clock
• 844
• 768 → official docked
• 691
• 614
• 537
• 460 → max handheld
• 384 → official handheld
• 307 → official handheld
• 230
• 153
• 76 → boost mode

Notes:

1. GPU overclock is capped at 460Mhz in handheld and capped at 768Mhz if charging, unless you're using the official charger.
2. Clocks higher than 768MHz need the official charger is plugged in.

 

[Nightf0x]

mariko sx modchiped here, retroreloaded installed, last sx os version, stock ofw 11.0
didnt use the switch for a longtime and this is its current state
want to migrate to atmosphere from sxos on emmunand and update ofw in sysnand to latest version
i followed this guide here: https://github.com/dsync89/Ultimate-Guide-to-Migrate-SXOS-SX-Core-to-Atmosphere
just after step 2.1b switch wont boot, i pressed power&vol+ until i heared a crackling sound, then i powered the swtch up the sx modchip blinks blue but pressing vol- wont boot to hekate ?!
(i know the files in the guide is outdated but i told myself i firstly migrate os then i update)

 

[steve_fox]

That’s a tough one. There’s a little info at the bottom of the sys-clk readme on GitHub but it’s not real declarative.

https://github.com/retronx-team/sys-clk

Spoiler: Readme

Capping​

To protect the battery from excessive strain, clocks requested from config may be capped before applying, depending on your current profile:

​	Handheld​	Charging (USB)​	Charging (Official)​	Docked​
MEM​	-​	-​	-​	-​
CPU​	-​	-​	-​	-​
GPU​	460​	768​	-​	-​

Clock table (MHz)​

MEM clocks​

• 1600 → official docked, boost mode, max clock
• 1331 → official handheld
• 1065
• 800
• 665

CPU clocks​

• 1785 → max clock, boost mode
• 1683
• 1581
• 1428
• 1326
• 1224 → sdev oc
• 1122
• 1020 → official docked & handheld
• 918
• 816
• 714
• 612

GPU clocks​

• 921 → max clock
• 844
• 768 → official docked
• 691
• 614
• 537
• 460 → max handheld
• 384 → official handheld
• 307 → official handheld
• 230
• 153
• 76 → boost mode

Notes:

1. GPU overclock is capped at 460Mhz in handheld and capped at 768Mhz if charging, unless you're using the official charger.
2. Clocks higher than 768MHz need the official charger is plugged in.

pp

That’s a tough one. There’s a little info at the bottom of the sys-clk readme on GitHub but it’s not real declarative.

https://github.com/retronx-team/sys-clk

Spoiler: Readme

Capping​

To protect the battery from excessive strain, clocks requested from config may be capped before applying, depending on your current profile:

​	Handheld​	Charging (USB)​	Charging (Official)​	Docked​
MEM​	-​	-​	-​	-​
CPU​	-​	-​	-​	-​
GPU​	460​	768​	-​	-​

Clock table (MHz)​

MEM clocks​

• 1600 → official docked, boost mode, max clock
• 1331 → official handheld
• 1065
• 800
• 665

CPU clocks​

• 1785 → max clock, boost mode
• 1683
• 1581
• 1428
• 1326
• 1224 → sdev oc
• 1122
• 1020 → official docked & handheld
• 918
• 816
• 714
• 612

GPU clocks​

• 921 → max clock
• 844
• 768 → official docked
• 691
• 614
• 537
• 460 → max handheld
• 384 → official handheld
• 307 → official handheld
• 230
• 153
• 76 → boost mode

Notes:

1. GPU overclock is capped at 460Mhz in handheld and capped at 768Mhz if charging, unless you're using the official charger.
2. Clocks higher than 768MHz need the official charger is plugged in.

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.

 

[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"