Homebrew RELEASE Gag Order - A fix for "Supernag"

[baretbh]

No, this screen can not be removed as the titles require the corresponding firmware to work.
EDIT: My bad, misread the text on your screen, thought you were seeing a cart update message. The message you see there can be removed without any tools! Simply boot into recovery mode (not RCM) by shutting down your Switch, holding Vol+ and Vol- at the same time and pressing power.

This is the answer ive been looking for! Thank you soo much!

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

If you boot into the Nintendo Recovery Mode (not the Tegra RCM), it should clear this update that's apparently been pre-downloaded.

Edit: You should block updates after doing this.


Mario Odyssey requires 3.0.1, and he's on 5.0.2. In addition, the option to start the software without updating is present.

Thanks! I do have "auto update software" already turned off, is there a way to complete block them though? Or is that what you mean

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

No, this screen can not be removed as the titles require the corresponding firmware to work.
EDIT: My bad, misread the text on your screen, thought you were seeing a cart update message. The message you see there can be removed without any tools! Simply boot into recovery mode (not RCM) by shutting down your Switch, holding Vol+ and Vol- at the same time and pressing power.

Hey just tried it and it worked perfectly!!! thanks!

 

[Lacius]

This is the answer ive been looking for! Thank you soo much!

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


Thanks! I do have "auto update software" already turned off, is there a way to complete block them though? Or is that what you mean

You should use the proper DNS settings, or you should delete your internet connection settings. Considering that you will eventually need to be on the latest system version in order to use the eShop and online play, the latter option is recommended.

 

[baretbh]

You should use the proper DNS settings, or you should delete your internet connection settings. Considering that you will eventually need to be on the latest system version in order to use the eShop and online play, the latter option is recommended.

Thanks again, I will def add those dns settings right now! Who hosts this DNS btw and im assuming i can still keep wifi on now with these dns right? or do i stay in airplane mode still.
Edit: This is pegaswitch. Deerp. The dns just blocks internet access. Ignore my retardedness

 

[DJTurnTable]

I've tried several times to run this but it just hangs at "attempting to terminate ns..." Is that supposed to happen or do i just keep trying?

Edit:I am on 4.1.0

Edit 2: Got it working by using version 0.0.1 instead of the newest release.

 

[Leolas123]

Hi I always have an error on my switch in 4.1, after several tries,
I tried 20 to 30 times already, error code:
(x1) XAj40011980649
(x2) 4.1.0

 

[Olmectron]

So.

Not so off-topic, but sorry anyway.

Is Pegaswitch already working on 4.1.0? I guess not. I've tried everything since this thread was created.

 

[sheg0]

So.

Not so off-topic, but sorry anyway.

Is Pegaswitch already working on 4.1.0? I guess not. I've tried everything since this thread was created.

Not yet.
Look at Pegaswitch Github Issue 126 (cant post links )

 

[Lunalik]

Is there anything this can currently be used to do. What does Pegaswitch do?

 

[demsondjoo]

i used gag-order on 5.1.0 and it said failed. my switch crashed after. but after restart, the nag was gone. so i guess it worked?

 

[bawzy]

This will patch Supernag on 4.1.0 units, and possibly other versions too (but I haven't tested those).

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/latest

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

It appears Gag Order is not compatible with the new OS 6.0. I am currently on 5.1 but 6.0 got downloaded in the background.

I run it, and it tells me "Invalid nag magic detected: 0x18000168. Expected 0x14020028."

Can you please update Gag Order to be compatible with this? I need this so I can setup DNS, which isn't letting me due to the supernag.

 

[M7L7NK7]

Can something be done about the joycon update nag?

 

[ms87]

i used gag-order on 5.1.0 and it said failed. my switch crashed after. but after restart, the nag was gone. so i guess it worked?

Similar thing here. I tried it several times and it didn't work, until I read your post. My Switch never actually crashed so after receiving the same error message after attempting to patch, I just held the power button down until it switched off. After booting up again it was gone. I was using GagOrder V1.3.0.

 

[rooshoes]

It appears Gag Order is not compatible with the new OS 6.0. I am currently on 5.1 but 6.0 got downloaded in the background.

I run it, and it tells me "Invalid nag magic detected: 0x18000168. Expected 0x14020028."

Can you please update Gag Order to be compatible with this? I need this so I can setup DNS, which isn't letting me due to the supernag.

Same here. Running v5.1.0 with the 6.0 update supernag. Seems to run into trouble using pmshellTerminateProcessByTitleId(0x010000000000001F); to kill ns, error code 0x0000020f. After exiting and returning to Gag Order, it behaves as if ns has been killed and attempts to patch the savedata, but as shown above the bytes don't match what's expected — either because Nintendo has changed the nag magic or the savedata is not being properly mounted.

Similar thing here. I tried it several times and it didn't work, until I read your post. My Switch never actually crashed so after receiving the same error message after attempting to patch, I just held the power button down until it switched off. After booting up again it was gone. I was using GagOrder V1.3.0.

v1.3.0? The latest public release on github is v0.1.0. What exactly did you do to remove the supernag in your case?

 

[ms87]

Same here. Running v5.1.0 with the 6.0 update supernag. Seems to run into trouble using pmshellTerminateProcessByTitleId(0x010000000000001F); to kill ns, error code 0x0000020f. After exiting and returning to Gag Order, it behaves as if ns has been killed and attempts to patch the savedata, but as shown above the bytes don't match what's expected — either because Nintendo has changed the nag magic or the savedata is not being properly mounted.



v1.3.0? The latest public release on github is v0.1.0. What exactly did you do to remove the supernag in your case?

This is what it's showing on my Switch. I'm unsure if it came from the github or hb App Store.

I hit patch in GagOrder, received the same error message as quoted above and then long-held the power button to turn off the switch. When I launched into CFW after that I no longer received the nag. I had tried several times using GagOrder and had no luck, so I'm not sure if it's just pure coincidence but powering down from within the app seemed to make something stick.

 

[pOOB73]

Anyone tested this on 6.1.0?
[Edit] Never mind.. Just tested it and it said it's incompatible.

 

[rfg]

Could someone please compile the latest code of Gagorder? I'm on firmware 4.1.0 with latest atmosphere/hekate and I'm getting:

Failed to terminate ns. Error code: 0x0000020f Patching failed! Please ensure you are on a supported firmware version and try restarting the application and/or your console.

I see there was a commit done that supposedly fix this issue: Improved reliability of killing PM. Latest commit 35d4fb4 on Jun 21, 2018

 

[8BitWonder]

Could someone please compile the latest code of Gagorder? I'm on firmware 4.1.0 with latest atmosphere/hekate and I'm getting:

Failed to terminate ns. Error code: 0x0000020f Patching failed! Please ensure you are on a supported firmware version and try restarting the application and/or your console.

I see there was a commit done that supposedly fix this issue: Improved reliability of killing PM. Latest commit 35d4fb4 on Jun 21, 2018

Switched it over to console from the old gfx API and compiled it.
https://github.com/16BitWonder/Gag-Order/releases/latest

Hopefully that fixes your issue.

 

[rfg]

Switched it over to console from the old gfx API and compiled it.
https://github.com/16BitWonder/Gag-Order/releases/latest

Hopefully that fixes your issue.

Thank you so much! I will test it tomorrow and I will update this thread with the information if it fixed or not.

 

[rfg]

Thank you so much! I will test it tomorrow and I will update this thread with the information if it fixed or not.

After testing your version of gagorder, I confirm that it works well (maybe you could push your changes to the official repository)

I still have the update button on the news tab but through the internet connection test I'm able to launch the pegascape menu. The only thing is the pegascape menu says I'm on version 4.0.0 but in reality I'm on version 4.1.0.

Thanks again 8BitWonder!

 

[8BitWonder]

... maybe you could push your changes to the official repository ...

Made a pull-request, will see how that goes.
Adubbz could also have their own fix in the works. ¯\_(ツ)_/¯

Edit:
Looks like it was merged