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?
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...
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...
The backup restoring went well in 6.1.0 up until I updated to 6.2.0, then online stopped working
auto
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
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.
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...
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...
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...
Still haven't got to tell the owner to do it
auto
It was 100% clean NAND. A micro SD with boot.dat only got into the switch when it was factory reseted. The online worked for like 2 days from when restoring nand backup and it stoped just after the update to 6.2.0
List of things done:
Backed up all saves to cloud. Did restore factory settings. (This deleted all saved wifi APs)
Loaded SXOS boot.dat to microsd, used rcm jig and Tegra to boot into bootloader.
Dumped NAND ofw 6.1.0 and generated license-request.dat
While getting license.dat on pc, emunand was...
The only diference I see is how backup was made... never AutoRCM (RCMTegraGUI or ns-atmosphere injector) cfw always airplane mode and stealth came on when installed 2.0.1. No update anyhow... First time restored and BAN
Could Nintendo test the console, tell me it was or was not CFW related and tell me to pay for unbaning it (they said max was 150€)... and if so, if it's not worth paying that amount if i can get a used one for 200€ and decide to decline Nintendo's repair... could they send it back patched but...
@SylverReZ, I also heard one of the Prince of Persia games was so unfinished that it required the "24/7 online" drm so a puzzle could be done and the game could be finished. And that when the Ubisoft servers were closed the (cracked) game was impossible to finish or something like that
I like that games can be fixed after the fact, hate that it's being abused via beta tests... And DLC... I was a 7800 owner back in the day and loved Impossible Mission, turns out I couldn't beat it because it was actually impossible lol