Hacking Question Restored NAND Backup OFW 6.1.0 and Update 6.2.0 got banned?

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
tell the owner to do it? sorry?

all im saying is if theres no error code and nintendos saying its not banned? then surely its not banned as it would be on there system? i think something wrong with the switch.
It's a friend's of mine but I did all the CFW
 
D

Deleted User

Guest
Then I don't know why you got banned. Best of luck figuring this mystery out.

What you could do is hack it again and look at your error messages, see if there's anything unusual. Your error log might not be empty.
 

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
Then I don't know why you got banned. Best of luck figuring this mystery out.

What you could do is hack it again and look at your error messages, see if there's anything unusual.

--------------------- MERGED ---------------------------
Options were try to restore 6.1.0 backup and sacrificing ofw through RCM, no sleep mode available etc... Finally wondering if sending it in to Nintendo is the best option. Worst case is they don't fix it, best is they ask max 150€ and fix it (and improbable is they send back patched and banned console lol)
 

mowsie

Well-Known Member
Newcomer
Joined
May 16, 2018
Messages
70
Trophies
0
Age
34
XP
220
Country
United States
If you used SX OS to make the backup..it's the reason why you got banned.

Sadly, the only good thing of SX OS/Pro is xci cartridge emulation, everything else is stolen or copied from open-source apps.

I always advice to use SX OS/Pro only for this xci stuff, nothing else.

Lol trash information and opinion presented as fact but okay. What a fuckin moron you are. You don't know the cause of the ban so stop spreading lies and misinformation. And sx has way more advantages than xci so stop pushing your anti sx agenda, you're harming the community with your lies.

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

I've been using SX OS since June, and I have not been banned. If used correctly you won't be banned. It sounds like his mistake was installing NSP's. That, or going online. I've created a backup using SX OS 2.0.1 last tuesday (the 13th), to play Pokemon let's go, Eevee early. I restored the backup using SX OS last friday (16th), after I purchased the game, to play it online legitimately. You are just talking smack, without anything to back up your statements. More people have been banned on ReiNX and Atmosphere, than those that have been banned using SX OS. That's the truth. Go check the pinned ban thread in this subforum. So far from what I'm seeing, people are only getting banned on SX OS for installing NSP's, going online with pirated games, or booting up homebrew.

Yeah this is the most accurate statement here, Perfect One is spreading absolute bullshit claiming sx os is the cause of bans and not NSP installation. I urge everyone here to ignore his posts as they are pushing his agenda and not providing accurate info.

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

You should have done this to do a full nand backup: https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/

SX OS/Pro has be proven to not be so well done and anything related to NAND are dangerous in various ways.

Not to say that in order for your SX OS Menu appear, you had to load the CFW first, so, you made a dirty NAND backup.

That's why you got banned.

If you had followed that guide i showed you in this my comment, you could see that no CFW is loaded in order for the NAND be fully backed up without triggering anything into Switch's Telemetry Log file(s).

Now you'll need to buy a new switch and use another account if you got any kind of ban, since in all them, at least, the used nintendo account is gone.

Sad for you, bro.

You have absolutely no clue how a bootloader works do you? You seriously believe the crap youre typing here huh? Stop posting in this thread you're causing a huge spread of false information. You even claim to know how Nintendo numbers their updates.. you're so full of shit.
 
Last edited by mowsie,
  • Like
Reactions: Aniblaze and x02a

Aniblaze

Well-Known Member
Newcomer
Joined
Oct 23, 2009
Messages
75
Trophies
1
XP
508
Country
Netherlands
If you used SX OS to make the backup..it's the reason why you got banned.

Sadly, the only good thing of SX OS/Pro is xci cartridge emulation, everything else is stolen or copied from open-source apps.

I always advice to use SX OS/Pro only for this xci stuff, nothing else.

Nintendo do ban waves, so, you or anyone else can be banned in future if did something wrong, like using SX OS/Pro for nand backup.

Enjoy while you can.

I'm kind of done with your bull, so I'm going to call you out on it. Could you back this up with actual facts, or are you just people spreading false rumors regarding the risk of bans using SX OS?

SX OS uses the same means as the other custom firmware for creating backups. Meaning it starts up their bootloader before the OFW or CFW is launched. No telemetry can take place at this point. It's like booting up a live CD of Ubuntu before your default installation of Windows is loaded up. You can browse around in Ubuntu, use Firefox, use the command line, you name it. None of it will be detected in Windows, simply because it's not running.

So explain to me how exactly SX's bootloader will get you banned for using it to create NAND backups? You can't. You're just here talking smack about SX OS, because you don't like the fact they are asking money for piracy. And you're allowed to have that opinion, that's not what's pissing me off. What makes you a terrible human being, is that you are parroting around false information to push your own opinion onto others as much as you can, essentially making it impossible for others to make an informed decision on actual facts. If they really are as shit as you say they are, you wouldn't need to do that. You could just use the actual facts. Stop lying.
 
Last edited by Aniblaze,
  • Like
Reactions: mowsie

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
A factory reset will not clear your nand you realize this right?
If you had read the context of the answer, I was answering if what was a possible cause of ban was not because backup was done before any CFW was introduced in the console. It was factory reseted so dumping took less time and it'd be smaller in size after compressed for storing, so yes, I knew that before your comment, thank you very much
 
Last edited by Napsteir,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
If you had read the context of the answer, I was answering if what was a possible cause of ban was not because backup was done before any CFW was introduced in the console. It was factory reseted so dumping took less time and it'd be smaller in size after compressed for storing, so yes, I knew that before your comment, thank you very much
If it was factory reset, then there's a chance the NAND wasn't 100% clean as a factory reset does not remove all traces of CFW/hacking. Was the console used?
 

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
If it was factory reset, then there's a chance the NAND wasn't 100% clean as a factory reset does not remove all traces of CFW/hacking. Was the console used?
Ok, let me say it again.
1: Console had ALWAYS been in OFW before all this.
2: In order to not loose the saves if ever went back to OFW I backed them in Nintendo's Cloud. (still OFW, no CFW ever installed)
3: I did a factory reset so no Nintendo Account was linked, no WiFi APs were saved and to reduce the wait and size of the dump. (still OFW, no CFW ever installed)
4: I added boot.dat from SXOS 2.0.1 to a 128 gb Sandisk Ultra micro sd card. (still OFW, no CFW ever installed)
5: I made sure the console was fully off. (still OFW, no CFW ever installed)
6: I inserted the micro sd card in the console's slot. (still OFW, no CFW ever installed)
7: I proceeded to get the console into rcm using a diy rcm jig and pressing Vol+ and Power. (this is the argument if bootloader is CFW or not)
8: Bootloader appeared, went to "Options" -> "Nand" -> "Nand Dump" and proceeded with default settings.
9: When finished, i generated license-request.dat (still in bootloader, never got into booting CFW or got Nintendo or Switch logo on screen).
10: Turned console off through the bootloader option up left. Copied license-request.dat and Nand dump (also including boot0 and boot1) in PC.
12: While waiting for a license seller to answer in the store chat i accessed bootloader (same procedure as before) and went to "Options" -> "Emunand" and created Emunand (default settings) and when finished turned it off as before.
13: When i got the SXOS code the license was activated through my PC and inserted back license.dat in the micro sd.
14: Accessed bootloader again (yes, kept holding Vol+ so it wont boot directly to CFW as license.dat was in micro sd and would have directly booted in CFW) to make sure emunand appeared as "enabled", and THEN booted into CFW.
15: First thing I did when in CFW was change the theme to black to differentiate OFW and CFW and turned Airplane mode on (I know this does nothing but ensuring no internet was a must for me).

There you have it.

Is it now clear that I fully understand that factory reset DOES NOT clean any NAND that had CFW in it and that it was done just to reduce size and ensure no Nintendo Account or WiFi was saved?
 
Last edited by Napsteir,

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
That means you you did you backup with sx and not with hekate.. this may be the problem
Oh, please, read the whole thread, PLEASE. This argument has already been talked before and conclusion was saying there's a difference between two bootloaders doing the same process is nonsense.
 
Last edited by Napsteir,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Oh ,jesus, please, read the whole thread, PLEASE. This argument has already been talked before and conclusion was saying there's a difference between two bootloaders doing the same process is nonsense.
Well he may be onto something as TX's NAND backup tool does not verify the NAND dump while Hekate's does. Meaning TX may (emphasis on possibly) dumped a bad NAND that may have flagged you upon restoration.
 

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
The backup restoring went well in 6.1.0 up until I updated to 6.2.0, then online stopped working

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

Does this mean that SXOS did a wrong backup of my nand, it could be true, but something changed in 6.2.0 that made a restored backup work and access online in 6.1.0 to stop working
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
The backup restoring went well in 6.1.0 up until I updated to 6.2.0, then online stopped working

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

Does this mean that SXOS did a wrong backup of my nand, it could be true, but something changed in 6.2.0 that made a restored backup work and access online in 6.1.0 to stop working
Again just because the backup process went fine doesn't mean the dump was fine because SX OS lacks the verification if your dump was good or not unlike Hekate which has a green bar when dumping the NAND to verify its good.
 

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
Again just because the backup process went fine doesn't mean the dump was fine because SX OS lacks the verification if your dump was good or not unlike Hekate which has a green bar when dumping the NAND to verify its good.
Ok, then green bar must be the difference, I'll just stop arguing. Absolutely normal to not being banned in a restored 6.1.0 but instantly after 6.2.0 update online was unavailable... Error code didn't appear on message but in error inspector and was not listed in Nintendo's error listing... It must have been SXOS. Do you realize that now I don't care if the console got banned because of a "non verified with green bar" NAND Dump but for something that may have changed in 6.2.0 that may make everyone using SXOS (or maybe other CFW) to getting insta-banned for a restored dump? No more posts will follow regarding this subject, just information and facts will be answered.
 
Last edited by Napsteir,

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
UPDATE: It seems all that was needed was a Factory Settings Reset. Picture proof now a Nintendo Account can be added. For the record, for "This Nintendo account cannot be used at this time, this user can't use online features" message and error code "2154-2005" after 6.2.0 update should be solved with a factory reset.
 

Attachments

  • WhatsApp Image 2018-11-21 at 11.28.34.jpeg
    WhatsApp Image 2018-11-21 at 11.28.34.jpeg
    69.4 KB · Views: 162
Last edited by Napsteir,

Aniblaze

Well-Known Member
Newcomer
Joined
Oct 23, 2009
Messages
75
Trophies
1
XP
508
Country
Netherlands
UPDATE: It seems all that was needed was a Factory Settings Reset. Picture proof now a Nintendo Account can be added. For the record, for "This Nintendo account cannot be used at this time, this user can't use online features" message and error code "2154-2005" after 6.2.0 update should be solved with a factory reset.
It was a fun ride. Good to know for future endeavors. My apologies BTW. Instead of actually helping to find a solution, I was more focused on dispelling false accusations.
 

Napsteir

Member
OP
Newcomer
Joined
Nov 20, 2018
Messages
21
Trophies
0
Age
32
XP
82
Country
Spain
It was a fun ride. Good to know for future endeavors. My apologies BTW. Instead of actually helping to find a solution, I was more focused on dispelling false accusations.
No hard feelins to anyone :D. Just think for next time, arguing goes nowhere, just 3 pages of nonsense that cause people to not read the whole post and makes it difficult to solve any problem. Anyway to finally close the thread?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over