Yep, it looks like a 256GB SD card. And you were saying it said 400GB on the card itself? That's really fishy. You should do as @Blythe93 suggested and check the card with H2testw just to make sure. But really, you should get back to the seller and ask him why you got a 256GB card instead of a 400GB. A 256GB card is not big enough on the Switch. In no time at all, you will fill it up.
In addition to what @Hayato213 said, make sure to set up DNS MITM and use it instead of prodinfo blanking (it no longer works as it was fixed in the most recent firmware).
Everytime you update your OFW Firmware, to be safe, but save your original (before Homerew/ NSP's) Nand also.
I want to share with you my findings after doing some more testing in this faulty Switch. I hope this is useful for someoneHi everyone,
After reading the many useful posts in this forum while trying to repair a friend's Switch, I have decided to ask for your help. I received the Switch and it was not turning on at all. No boot logo or anything. Therefore, I decided to measure the current being drawn by the console. I measured 15 V and 0.5 A, so I assumed that M92T36 was working fine, since the 15 V indicate that fast charging is active. After that, I decided to connect the Switch to the PC and it was detected in APX mode, so I gave it a try and load TegraRcmGUI and indeed, the console was being detected in RCM mode. I tried sending a payload, but the console is a V1 patched model, so no possibility of running Hekate.
In light of the above, I drew the following conclusion: the Switch is stuck in AutoRCM because there is some problem with the EMMC and it cannot load the OS. I disassembled the console and check for shorts around M92T36 just in case, but everything was looking fine.
What are my options at this point? I read something about rebuilding the NAND, and I saw some adapters to dump the NAND via Linux with an special adapter, but I think that since I do not have the "keys" (prod.keys, master.keys? I still do not fully understand what they are) I cannot decrypt the NAND contents and try to rebuild it.
I have also considered the possibility of soldering some modchip in order to run Hekate and check the status of the NAND, or at least do the NAND dumping to the microSD, but I see many different modchips around Aliexpress and I don't really know which one I should use.
I really appreciate any possible help you can give to this newbie.
Thanks in advance
From what I know, only sysnands are affected from this and atmosphere 1.6.2 solved that issue.
when i restore to the nand and its (as i think clean) i do go online to update to the last ofw
Correct. In step 3 you are disabling WiFi on OFW and then making a backup. If you ever enable WiFi on OFW again, you'll have to make a new backup when you're done. Just don't restore the previous one if you used WiFi on sysnand since the last time.
If you never used Incognito or any other method to blank your prodinfo on sysnand, you don't have to worry about it, just enable Atmosphere DNSMITM and (optionally) disable blanking in Exosphere.
Ah, my bad, I misunderstood that. Looks like sa-yamato meant this issue. I haven't experienced it, but as far as I can understand, if it happens to you, having Atmosphere 1.6.1+ and using it to boot 17+ on sysmmc once should be enough to fix it.
This is always good advice.
oh so no one knows if (restore a clean nand with hekate) is among the things that SciresM meant when he wrote ( wiped/reset using unofficial methods in the past) and he mentions (Tools like Haku33 or TegraExplorer or EmmcHaccGen or ChoiDujour)
Atmosphere should be backwards compatible, so yes. It should work.
Did you update the payload on Rekado as well? Also, firmware 17.0.0 introduced some changes to the save file management so some people may experience that they are not able to boot into CFW if they've ever used Haku33 / TegraExplorer / EmmcHaccGen / ChoiDujour to clean or reset their console. In that case, you'll need to boot Atmosphere 1.6.1 or higher on sysMMC. If you're using emuMMC and want to make sure that you're really booting into sysMMC, boot into Hekate and go to emuMMC > Change emuMMC and select DIsable. After that, just send fusee.bin payload (or boot to sysMMC via Hekate) and it should boot into sysMMC. More on this issue can be found here.
Just get the latest Hekate, Atmosphere, latest sigpatches and/or sys-patch module (which requires Tesla + nx-ovlloader) because these are required for games to work.
Restoring an eMMC backup is basically turning back time on your console to the state it was in when you made that backup. Meaning when you restore your backup, as long as you didn't use tools like Haku33, TegraExplorer, EmmcHaccGen, or Choidujour before you made that backup then your console will revert to the time when none of those were ran on it.
