problem with backup and firmware upgrade

[Timosha]

Greetings everyone!
It all started when I tried to change the firmware because my microsd required a system update. I read in one thread that I needed to upgrade to 6.2 (I did not know then that I could updrade to a later version). everything went fine, but after the final reboot the switch did not turn on for about a minute and I decided to turn it on myself (until that point I strictly followed the instructions presented here https://team-xecuter.com/community/...ine-nintendo-switch-with-choidujournx.128170/)
Now the switch began to automatically start CFW and gives an error 2162-0002. Several times I managed to get into the CFW menu and I decided that I needed to use the backup. Now I do not know how I managed to get into the menu, now it automatically launches the firmware even when I just insert the dongle.
CFW version 2.8 and OFW 8.0.0

Please tell me what to do, otherwise I will ruin something again: D
I hope this problem can be fixed
Thanks for the help, have a nice day everyone

 

[imprezgc8]

It sounds like you updated using ChoijudourNX which enables autoRCM by default. You can get to that menu by holding Vol+ when booting up. Try to get to that menu again and boot Official Firmware. It sounds like maybe the update didn't finish or you did not pick the exFAT version of the FW and your SD is exFAT.

 

[Timosha]

It sounds like you updated using ChoijudourNX which enables autoRCM by default. You can get to that menu by holding Vol+ when booting up. Try to get to that menu again and boot Official Firmware. It sounds like maybe the update didn't finish or you did not pick the exFAT version of the FW and your SD is exFAT.

ofw also get the same error. I chose the version of exFat for sure and after that I tried to format the flash drive in fat32; the result did not change
I also tried to make a backup from this menu but I did not succeed: NAND restore failed. Errcode=00FFFD47
also failed to start hekate
sounds like i broke it all

 

[sixtynine]

First) I would recommend you read up on autorcm mode until you have a completely thorough grasp on every bit of it. I have never used it myself and don't care if my fuses get burnt to prevent downgrading as I never upgrade first without making absolutely certain the OFW is fully supported by TX. Then I wait a week or so to make sure the bugs are worked out, just in case any show up. IMO autorcm is a dangerous feature that should not be used until the user is 100% informed on all its features and quirks as you can cause serious headaches with it. So seriously read up on it first before doing anything else!

Second) How are you formatting your SD card and I don't just mean exfat or fat32? I mean the process and/or OS being used, or the device being used. Also very important, what brand is the card? Where did you buy it from and for how much? Seriously.
Cheap cards cause many-many problems and some cards are even fakes... Usually cheap ones purchased off ebay. Make certain this is not your problem before doing or reading anything else. Make sure your card is real and fully supported by Nintendo for the Switch. I listed the part number below of a fully supported card by Nintendo that I use and have never had a problem with.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Can you get it to boot into OFW and work normally? If you can get back into SX OS menu then you need to see if you can turn off autorcm. This is the part you need to be sure of first, Before disabling the autorcm, as not having the correct fuse count based on your current firmware can cause the system to either burn a fuse or not boot at all if on the wrong firmware. So do your homework first. Seriously !

If you determine that it is ok to disable autorcm and fully power down and reboot your switch then I would try the following. But only after trying several more times to get a "hekate" NAND backup with all partitions. See below for nand backup info.

At this point if autorcm is able to be disabled maybe it might be worth trying to update the switch the official way since it is the most error free way of upgrading and at the same time.... hopefully repairing your system to normal operation. You will likely get your switch banned though because just enableing AUTORCM will flag your console to Nintendo, whether you are currently using autorcm or not. But many people have banned switches and don't care. Thing is, if your switch is broke already then maybe its worth a shot. Up to you though as I do not know the best answer for your specific situation. However, whatever you decide, please read the information below as it is very important.


Information below is the best way to backup your NAND BEFORE AND AFTER ANY system update or system tampering. SX OS is too inconsistent. Sorry Devs.

I have never been able to get a good or consistent backup without using hekate and I have spent hours-upon-hours-upon-hours-upon-hours trying with SX OS. None of the NAND files dumped with SX OS cfw ever match up while verifying them with hash checks. In case somebody is wondering what brand/size SD card I use... I only use the Nintendo officially supported SanDisk 128GB microSDXC UHS-I card for Nintendo Switch - SDSQXAO-128G-GN6ZA card and have tried exfat and fat32, also on multiple firmwares. No doubt that SX OS is a great piece of software, my hats off to the devs, but the devs definitely do not have this part locked down well at all. The only way to be 100% certain you have a good Nand backup is with hekate. Then do your own verification with md5 or sha256. Although every single dump I do with hekate ends up being a perfect match via the hash checks. No matter what format I use on my SD card.

get the files: (just make sure to grab the newest versions)

TegraRcmSmash.exe (you can use the gui but I don't see any reason for it when just making a simple nand backup as the non-gui way couldn't possibly be any easier to use)
&
hekate (payload file)

https://switchtools.sshnuke.net/
https://github.com/CTCaer/hekate/releases

The problem however, if something is already messed up, dumping the nand now will likely do no good. But I'd try to dump it anyways as its always possible to make things worse when tampering, and if you don't get a known good dump first you may be super scr3w3d. Just keep this in mind for the future in case you get your problem figured out.


The readme instructions for tegrarcmsmash.exe

TegraRcmSmash 1.2.1-3 (21.06.2018)
A reimplementation of fusee-launcher in C++ for Windows platforms.
Lets you launch fusee/shofEL2 payloads to a USB connected Switch in RCM mode.

Driver setup (hekate will not work until you install the driver on your pc)
1. Get your Switch into RCM mode and plug it into your Windows PC. It should show up somewhere (like Device manager) as "APX"
2. Download and run Zadig driver installer from https://zadig.akeo.ie/
3. From the device list, choose APX (if it's not showing up in the list, go to Options menu and check List All Devices)
4. For the driver type, cycle the arrows until you see libusbK (v3.0.7.0) in the text box (IMPORTANT!)
5. Click the big Install Driver button. Device manager should now show "APX" under libusbK USB Devices tree item.

Usage
TegraRcmSmash.exe [-V 0x0955] [-P 0x7321] [--relocator=intermezzo.bin] [-w] inputFilename.bin [-r] [--dataini=coreboot.ini] ([PARAM:VALUE]|[0xADDR:filename])*
If your Switch is ready and waiting in RCM mode, you can also just drag and drop the payload right onto TegraRcmSmash.exe

An example cmdline for launching linux using coreboot is something like this (the empty relocator is important):
TegraRcmSmash.exe -w --relocator= "coreboot/cbfs.bin" "CBFS:coreboot/coreboot.rom"

A simpler way to load coreboot/other AArch64 payloads is to use my memloader payload (see https://switchtools.sshnuke.net) and either put the files on microsd or use the --dataini parameter

After that, you can use imx_load as you would on Linux (Windows binaries available at https://github.com/rajkosto/imx_usb_loader/releases)
Alternatively, setup your u-boot cmdline to just load everything from microSD to not bother with imx_load


For updates check https://switchtools.sshnuke.net
Source code available at https://github.com/rajkosto/TegraRcmSmash

**I am not responsible for anything, including dead switches, blown up PCs, loss of life, or total nuclear annihilation.**

Good luck and hope this helps.

 

[imprezgc8]

ofw also get the same error. I chose the version of exFat for sure and after that I tried to format the flash drive in fat32; the result did not change
I also tried to make a backup from this menu but I did not succeed: NAND restore failed. Errcode=00FFFD47
also failed to start hekate
sounds like i broke it all

Making a backup after issues have started will not really help and that's probably why it's failing. Do you have a back up from before you tried updating with Choi? Have you actually tried formatting the SD to fat32 and booting? That's the most common issue when people use Choi to update, they don't actually pick the exFAT version of the FW. You might want to try downloading a fresh boot.dat file as well. There could be corruption as well. You could try just reformatting as exFAT if you didn't already.