Homebrew RELEASE Gag Order - A fix for "Supernag"

[ArcLP]

You'll need to compile it yourself and then modify hekate's ini files to load it for you (as has already been suggested by @m4xw).


A permanent fix unless you connect to the internet again without a DNS. You're entirely in control of how long it lasts.

--------------------- MERGED ---------------------------


For those who wish to be able to use Pegaswitch (or any other DNS-based tools) on 4.1.0.

Mate that makes it a temp fix aha. thats alright though (:

 

[Red1Reaper]

Very thanks, this is great, and i say is a permfix because it can be used unlimited times to remove the super nag, so we can say that the fact of having this nro on the hb chanel is a kind of perm fix

 

[Paulsar99]

It works!!!

 

[Phil5004]

what exactly can we do with that now?

 

[Paulsar99]

How do you run the nx-dreport? Should I just add it under kip1=loader.kip1 and kip1=sm.kip1 then run the payload and cfw?

 

[ArcLP]

Very thanks, this is great, and i say is a permfix because it can be used unlimited times to remove the super nag, so we can say that the fact of having this nro on the hb chanel is a kind of perm fix

Sure, it's a permanent fix in the sense you can use it multiple times.

But a permanent fix means:

A permanent fix is where you use it once, and never encounter the nag again. This is like saying a tethered jailbreak is untethered because you can use it infinite times. lol

 

[Red1Reaper]

Sure, it's a permanent fix in the sense you can use it multiple times.

But a permanent fix means:



A permanent fix is where you use it once, and never encounter the nag again. This is like saying a tethered jailbreak is untethered because you can use it infinite times. lol

Well if you see the switch as a whole, then once you put the nro on it, its a permanent fix and you don't need to copy it again to the sd card, not a fix for the super nag but a permant fix to the problem of the inhability of fixing the super nag
too is a permanent fix to the individual super nag of a system, that individual super nag is permanently fixed, if you get a new super nag, its a new super nag, a new problem.

 

[ArcLP]

Well if you see the switch as a whole, then once you put the nro on it, its a permanent fix and you don't need to copy it again to the sd card, not a fix for the super nag but a permant fix to the problem of the inhability of fixing the super nag

A permanent fix would be removing or editing the file or script that executes the supernag to run on the switch itself. Just call it a tethered fix at that point.

 

[Red1Reaper]

A permanent fix would be removing or editing the file or script that executes the supernag to run on the switch itself. Just call it a tethered fix at that point.

Its permanent in the sense that it does not come back by itself, in a individual system is permanently fixed, you can get a new super nag, but that is not caused by itself, but for another problem, that is that nintendo is giving super nag, while this is not a permanent fix to the problem of nintendo giving super nag, its a permanent fix to the individual super nag on individual system.

 

[Draxzelex]

Finally, it's about damn time we removed it! Now all of those guides are going to have to be updated...

 

[ArcLP]

Its permanent in the sense that it does not come back by itself

that's some technological acrobatics there.

If I don't change my DNS, and leave it as vanilla while running the script, later the supernag will come back, and its the same supernag. it's not supernag 2.0, 3.0, or 4.0 I don't think you really understand how systems work with notifications. That's like saying closing out of the "we updates our terms of service" on twitter, and it comes back up the next time you go on twitter, makes it a new terms of service. that logic is unbearable.

The reason why they call it a supernag is because it's a nag. Not a super "Okay I'm sending my brother to bug you next time you get rid of me" "Okay I'm sending your sister to bother you next time you close me".

I give you a C for trying though.

 

[Red1Reaper]

that's some technological acrobatics there.

If I don't change my DNS, and leave it as vanilla while running the script, later the supernag will come back, and its the same supernag. it's not supernag 2.0, 3.0, or 4.0 I don't think you really understand how systems work with notifications. That's like saying closing out of the "we updates our terms of service" on twitter, and it comes back up the next time you go on twitter, makes it a new terms of service. that logic is unbearable.

The reason why they call it a supernag is because it's a nag. Not a super "Okay I'm sending my brother to bug you next time you get rid of me" "Okay I'm sending your sister to bother you next time you close me".

I give you a C for trying though.

I know im forcing quite a bit the thing, but i was bored, that said, im giving an example, if you have a structural problem in the building because the neightbors in the upper floor are doing crazy shit, you can permanently fix the structural problem, but if the neightbors continue doing crazy shit, a new structual problem might appear, this is the same, this can be seen as a permanent fix for the problem of the super nag on a console, but its not fixing the main problem that caused the problem, and that problem whould cause you to have a new super nag in the right conditions, but while its a carbon copy of the one you had in the past, is a new problem in a sense.
I know im forcing the logic way too much, and i know what you mean, but hey, lets call it a pseudo-permanent fix, its not like something that one need to use on every boot.

 

[Naminave]

This will patch Supernag on 4.1.0 units, and possibly other versions too (but I haven't tested those). This version does what it says on the tin, however it does lack polish which will come with time.

Please note that you may have to try running it multiple times, and it will likely crash when you try to turn off your switch or return to the home menu after running it. This is due to needing to kill ns to modify its savedata. Upon restarting your switch you should have no more issues though. Your crash logs can be removed using a tool such as https://github.com/Thog/nx-dreport

Download:
https://github.com/Adubbz/Gag-Order/releases/tag/0.0.1

Disclaimer:
I am not responsible for any issues or damage this causes to your switch.

Waa thank you very much !. Can you make a Payload to delete the SuperNag?

 

[H1B1Esquire]

Wow!! I'm incredibly impressed; so much so, I wanted to like the post twice, but doing so would only count as one like, regardless.

Can't wait to see the future development for that "polish".

--------------------- MERGED ---------------------------

https://github.com/Thog/nx-dreport

I'm pretty burnt (not even from 'moking); how do I/we use this?

 

[Creatable]

Can't wait for Nintendo to detect which units used to have the supernag and ban them since they're on 4.1.0 and no longer have it.

 

[Phenj]

Can't wait for Nintendo to detect which units used to have the supernag and ban them since they're on 4.1.0 and no longer have it.

Can't wait to bypass bans like we always used to do with both Wii U and 3DS

 

[Creatable]

Can't wait to bypass bans like we always used to do with both Wii U and 3DS

Can't wait for you to realize that that's not possible on the Switch

 

[Phenj]

Can't wait for you to realize that that's not possible on the Switch

Lmao of course

 

[lordelan]

Sorry for being the guy that asks the dump question but ... what is this supernag?
That annoying FW update popup when accessing the internet (switchbru DNS) from lower firmwares or what?

 

[Creatable]

Sorry for being the guy that asks the dump question but ... what is this supernag?
That annoying FW update popup when accessing the internet (switchbru DNS) from lower firmwares or what?

Correct.