So after you said No to the update, you restarted the console on your own, is that correct?
Also check your PM.
Maintenance mode (volume - and + and hit power) gets it stuck in switch logo.Try maintenance mode again. Initialize without deleting user information.
Any luck> I haven't been able to spend any time on this the last couple days. Damn Adulthood!!
You'll be fine. Aafter you set activate the new license on the TX site your License file will work fine. IDK why you bricked before. Like I said, there is usually something the user thought was nothing that was actually something. A quick install of some save editor NSP... Maybe a homebrew app that isn't fully understood.by the user Good luck with the new one. If you want help PM me. NAND backup is key.
I made a SXOS backup and Hekate backup for mine. Upload a copy to the cloud as well.
the fact that this is unsolved makes me feel some type of way. Feelsweirdman, Also keeping an eye on this cuz this is some type of stuff i could have gotten myself into, i hacked my switch when sx-pro 2nd batch shipments were received, and I JUST BARELY BACKED UP MY NAND ON THE 13TH WHEN LETS GO WAS LEAKED. Yikes. It was the .nsp's with brick code that finally made me remember to do it. Once again yikes, i should have remembered, also to be fair before that day i only used .xci's so that was the first time i was gonna install a .nsp
That backup should not be considered clean though.
I bet this could have been resolved. The amount of effort put forth may have something to do with it. You would have to read and follow instructions. Some of the methods are not straight forward. IF they had a NAND Backup like they were supposed to in the first place it would be no big deal. Also the PC method can write directly to the NAND. More than likely could have fixed it there. I am pretty sure there was more than meets the eye. When people read partial instructions, don't know what they are doing, and make decisions they have no business making, they tend to have these results. Read, backup and don't say yes to anything you don't fully understand. You should be fine.
My friend shipped his console to Nintendo for repair. I hope they'll be nice and do it.
He got a new console meanwhile, on 4.1.0 too. I am backing up his NAND and boot0/1. I'll also dump the bis keys, then use a fat32 sd card to install 5.1.0 with exFAT support, via ChoiDuJour.
We want to use the dongle we already have with a new SX OS license, but I'm afraid this might brick it, as the dongle comes with a license...
Sounds like a bad NSP. IF you followed that guide, the most important part was leaving AutoRCM on... It protects fuses. You are on 6.1 fuses now though so who cares? If you turned off AutoRCM and booted to stock firmware you burned your fuses. You can't ever boot stock firmware below 6.1 again without cfw. You should try maintenance mode (COMPLETELY POWER OFF BY HOLDING POWER 20 SECONDS. hold both vol+ and vol-, tap power.) then select the initialize without deleting save and user data. IF that doesn't work, restore your backup, If the backup is on 4.1, stock loader won't work. No reason to leave it on 4.1. at that point So IF the backup works, update to 6.1 with ChoiDuJourNX... Stop guessing. Your "Turned off AutoRCM just in case" move was bad. Stop tinkering before you understand what you are doing and why you are doing it. Most mistakes on this board are from newbies thinking they have some kind of right to make decisions. Bad move. Just stop it.
This is basically the same solution I suggested earlier in this thread to the other Newbie expert who bricked. He had no success but I don't think he follows instructions well either. Google is your friend.
Sounds like a bad NSP. IF you followed that guide, the most important part was leaving AutoRCM on... It protects fuses. You are on 6.1 fuses now though so who cares? If you turned off AutoRCM and booted to stock firmware you burned your fuses. You can't ever boot stock firmware below 6.1 again without cfw. You should try maintenance mode (COMPLETELY POWER OFF BY HOLDING POWER 20 SECONDS. hold both vol+ and vol-, tap power.) then select the initialize without deleting save and user data. IF that doesn't work, restore your backup, If the backup is on 4.1, stock loader won't work. No reason to leave it on 4.1. at that point So IF the backup works, update to 6.1 with ChoiDuJourNX... Stop guessing. Your "Turned off AutoRCM just in case" move was bad. Stop tinkering before you understand what you are doing and why you are doing it. Most mistakes on this board are from newbies thinking they have some kind of right to make decisions. Bad move. Just stop it.
This is basically the same solution I suggested earlier in this thread to the other Newbie expert who bricked. He had no success but I don't think he follows instructions well either. Google is your friend.
You'll be fine. Aafter you set activate the new license on the TX site your License file will work fine. IDK why you bricked before. Like I said, there is usually something the user thought was nothing that was actually something. A quick install of some save editor NSP... Maybe a homebrew app that isn't fully understood.by the user Good luck with the new one. If you want help PM me. NAND backup is key.
I made a SXOS backup and Hekate backup for mine. Upload a copy to the cloud as well.