Hacking SWITCH NOOB PARADISE - Ask questions here

[Vektast]

The latest is 18.1.0. How did you update to 18.0.0 via the settings menu?

Actually it's on 18.0.1 I didn't update after that. I've updated from 17.x.x from the settings menu. I'm pretty noob at Switch hacking, do you know hogy to retrain this chip?

 

[RedColoredStars]

Actually it's on 18.0.1 I didn't update after that. I've updated from 17.x.x from the settings menu. I'm pretty noob at Switch hacking, do you know hogy to retrain this chip?

Sorry. don't know anything about the chip. But could try a few things.

First off, are you sure you're using the latest HATS? Latest is 1.71-1 from June 14th. If not grab the latest and replace all files.

Secondly, after you're 100% positive you have the latest....
Download this: https://github.com/CTCaer/hekate/releases/

Extract the hekate_ctcaer_6.2.0.bin from the zip file and rename it to reboot_payload.bin
Place the renamed file in your Atmosphere folder and overwrite the one that's already there.

When finished, update emuMMC to 18.1.0 using Daybreak. You'll need to locate 18.1.0 FW as it is not allowed to link to it here. After emuMMC is updated, update sysMMC to 18.1.0 through the Switch settings.

 

[Vektast]

Sorry. don't know anything about the chip. But could try a few things.

First off, are you sure you're using the latest HATS? Latest is 1.71-1 from June 14th. If not grab the latest and replace all files.

Secondly, after you're 100% positive you have the latest....
Download this: https://github.com/CTCaer/hekate/releases/

Extract the hekate_ctcaer_6.2.0.bin from the zip file and rename it to reboot_payload.bin
Place the renamed file in your Atmosphere folder and overwrite the one that's already there.

When finished, update emuMMC to 18.1.0 using Daybreak. You'll need to locate 18.1.0 FW as it is not allowed to link to it here. After emuMMC is updated, update sysMMC to 18.1.0 through the Switch settings.

I'm 100% sure that I'm using the latest HATS from telegram. I can't use Daybreak because the Switch only boots to Stock ofw, no CFW, no Hekate just Stock.
Extract the hekate_ctcaer_6.2.0.bin from the zip file and rename it to reboot_payload.bin <--- did it, still no hekate

 

[RedColoredStars]

I'm 100% sure that I'm using the latest HATS from telegram. I can't use Daybreak because the Switch only boots to Stock ofw, no CFW, no Hekate just Stock.
Extract the hekate_ctcaer_6.2.0.bin from the zip file and rename it to reboot_payload.bin <--- did it, still no hekate

Sorry I can't be of more help. Hopefully someone familiar with the chip will come along shortly to help out. You could also ask on the SwitchPirates subreddit.

 

[Vektast]

Sorry I can't be of more help. Hopefully someone familiar with the chip will come along shortly to help out. You could also ask on the SwitchPirates subreddit.

No problem bro, thanks for trying! I'll try SwitchPirates subreddit

 

[Near14]

Hello
So , I bricked my nand because of oc and I got a nand backup that I made on 18.0.1 but I’m not sure if I can safely restore this nand without a risk of ban . Nintendo would find it weird that I play on 18.0.1 while I was casually playing on latest firmware last week nah ?

Thanks for help

 

[BigOnYa]

@Hayato213 , @impeeza if one of you two fine gentlemen could help out with the above post, thank you.

 

[Hayato213]

Hello
So , I bricked my nand because of oc and I got a nand backup that I made on 18.0.1 but I’m not sure if I can safely restore this nand without a risk of ban . Nintendo would find it weird that I play on 18.0.1 while I was casually playing on latest firmware last week nah ?

Thanks for help

If you play online with 18.1.0 and then restore to 18.0.1 you will get banned.

 

[impeeza]

@Hayato213 , @impeeza if one of you two fine gentlemen could help out with the above post, thank you.

Hello
So , I bricked my nand because of oc and I got a nand backup that I made on 18.0.1 but I’m not sure if I can safely restore this nand without a risk of ban . Nintendo would find it weird that I play on 18.0.1 while I was casually playing on latest firmware last week nah ?

Thanks for help

Hello there, If you restore a past NAND and your console already had send data to Nintento Telemetry which is not on the restored NAND is very probable you will be banned, you can read more on the thread: https://gbatemp.net/threads/nintendo-switch-banning-hub-warning.508710/

 

[Near14]

If you play online with 18.1.0 and then restore to 18.0.1 you will get banned.

What about if I don’t go online and I upgrade the restored sysnand to 18.1.0 with daybreak , then I wipe out sysmmc with tegraexplorer ?

Post automatically merged: Jun 19, 2024

Hello there, If you restore a past NAND and your console already had send data to Nintento Telemetry which is not on the restored NAND is very probable you will be banned, you can read more on the thread: https://gbatemp.net/threads/nintendo-switch-banning-hub-warning.508710/

What about if I upgrade my restored nand which is on 18.0.1 to 18.1.0 with daybreak offline so I don’t send data to Nintendo telemetry and then I wipe out sysmmc with tegraexplorer , I know people do that when they get sysnand dirty

 

[impeeza]

What about if I don’t go online and I upgrade the restored sysnand to 18.1.0 with daybreak , then I wipe out sysmmc with tegraexplorer ?

Post automatically merged: Jun 19, 2024

What about if I upgrade my restored nand which is on 18.0.1 to 18.1.0 with daybreak offline so I don’t send data to Nintendo telemetry and then I wipe out sysmmc with tegraexplorer , I know people do that when they get sysnand dirty

The problem is the local database of Telemetry vs the database of Telemery on Big N servers, if they are different you could get banned, if your NAND is connected to the net and transmitting data to Big N servers the chance of getting banned is high.

 

[Near14]

The problem is the local database of Telemetry vs the database of Telemery on Big N servers, if they are different you could get banned, if your NAND is connected to the net and transmitting data to Big N servers the chance of getting banned is high.

But how these data would be different ? im not gonna connect to their servers till im in 18.1.0 (like the initial firmware of the nand that i was in before it got corrupted).Like how they would flag me ? I appreciate your help by the way thanks for help

 

[impeeza]

But how these data would be different ? im not gonna connect to their servers till im in 18.1.0 (like the initial firmware of the nand that i was in before it got corrupted).Like how they would flag me ? I appreciate your help by the way thanks for help

But you did connected to network on the NAND which got corrupted, THAT NAND on the past sent information to Big N servers and now is impossible to create the same information on a new NAND or an old backup. that's the risk.

 

[Near14]

But you did connected to network on the NAND which got corrupted, THAT NAND on the past sent information to Big N servers and now is impossible to create the same information on a new NAND or an old backup. that's the risk.

mmm so what about if i had a old backup with the latest firmware. That would be the same risk nah ?Since informations would not be the same too ?

 

[impeeza]

mmm so what about if i had a old backup with the latest firmware. That would be the same risk nah ?Since informations would not be the same too ?

if your NAND is connected to the net and no incognito (RCM or Atmosphere's Stratosphere) yes, is a risk

 

[Near14]

if your NAND is connected to the net and no incognito (RCM or Atmosphere's Stratosphere) yes, is a

if your NAND is connected to the net and no incognito (RCM or Atmosphere's Stratosphere) yes, is a risk

Damn .So basically , if you brick your sysnand which alrealy went online by the past , restoring an old sysnand backup would be a risk even if the firmware of the backup is the same as the bricked one ?

 

[Hayato213]

What about if I don’t go online and I upgrade the restored sysnand to 18.1.0 with daybreak , then I wipe out sysmmc with tegraexplorer ?

Post automatically merged: Jun 19, 2024

What about if I upgrade my restored nand which is on 18.0.1 to 18.1.0 with daybreak offline so I don’t send data to Nintendo telemetry and then I wipe out sysmmc with tegraexplorer , I know people do that when they get sysnand dirty

Still won't match with what they have, would be even worse since you used Daybreak. Don't use tegraexplorer to wipe sysnand, it cause brick.

 

[Near14]

Still won't match with what they have, would be even worse since you used Daybreak. Don't use tegraexplorer to wipe sysnand, it cause brick.

I’ve already used tegraexplorer by the past to clean a dirty nand , it didn’t brick anything.And if i had a nand backup that had the same firmware as my actual corrupted nand (the latest) , it would match what they have ? Based on what impeeza said ,restoring a sysnand backup which went online is always risky apparently.
(I really appreciate your help , thanks for taking the time to help me)

 

[impeeza]

Damn .So basically , if you brick your sysnand which alrealy went online by the past , restoring an old sysnand backup would be a risk even if the firmware of the backup is the same as the bricked one ?

In short words, YES. give a try to the Banning hub thread.

Post automatically merged: Jun 19, 2024

I’ve already used tegraexplorer by the past to clean a dirty nand , it didn’t brick anything.And if i had a nand backup that had the same firmware as my actual corrupted nand (the latest) , it would match what they have ? Based on what impeeza said ,restoring a sysnand backup which went online is always risky apparently.
(I really appreciate your help , thanks for taking the time to help me)

tegraexplorer cleaning process do not brick per se, but Big N introduced some changes on FW 17 wich combined with the clean process could generate a soft brick, that soft brick even happened with big N tools. Atmosphère 1.6.1 try to fix it but not always can be recovered.

 

[Near14]

In short words, YES. give a try to the Banning hub thread.

Post automatically merged: Jun 19, 2024

tegraexplorer cleaning process do not brick per se, but Big N introduced some changes on FW 17 wich combined with the clean process could generate a soft brick, that soft brick even happened with big N tools. Atmosphère 1.6.1 try to fix it but not always can be recovered.

I got it thank you , so basically what is the way that you would recommend to me.Since im cooked with no backup ?