Hacking Possible Brick after unplugging battery while Atmosphere is running

[WhyBlu]

Good day, everyone.

TLDR;
I fixed the microSD reader on my switch and tried to boot hekate with it and Atmosphere working. I unplugged the battery hastly and completely assembled the switch again to find it not booting atmosphere or HOS at all, just a black scren. I did used to and still do receive a message saying my microSD card is in "1-bit mode" but I don't care because it used to work before even with that message. Could it be a NAND brick? if so, can I repair the brick without flashing a backup? and again, if so, how can I build a new NAND backup if I lost my old one.

Full Post:
I recently repaired my old nintendo switch v1 which wasn't functional due to a broken DAT2 pin on the microsd card reader connector.
After many attempts and much practice (considering I'm a beginner in microsoldering), I finally pulled it off and jumped the DAT2 connection from a debug pin on the back of the switch's motherboard to the reader itself. It worked when I tried it without the fan and game card slot since I just wanted to test it out: It booted into hekate with a payload injector I used (it couldn't do that before since the card wasn't being read), and I was able to successfully boot into Atmosphere. All was well, the home menu was running fine (albeit, none of the games ran and I assume it was because I didn't plug the fan in since I didn't put thermal paste), and out of excitement I forgot to power off the console and just removed the battery immediately. I put back everything and closed up the switch and attempted to boot the console back up with hekate working, but atmosphere and HOS didn't work, it just gave me a black screen, but I could tell something was running because I couldn't turn RCM on unless I forced it to shut down. I was receiving and still am receiving a message about my microSD card running in "1-bit mode" or something, but it doesn't matter and I didn't really care because it was still running perfectly fine on Atmosphere before, even with this error. Could my NAND be corrupted? If so, is there anyway I can "uncorrupt" it, or build a new NAND backup? I think I lost mine when I changed my computer.

Please help me with this as I am desperate and just want this switch to work as before.

Cheers!

 

[thesjaakspoiler]

I don't think your NAND is corrupted.
If your SD card is formatted with exFat then you might have wrecked it when pulling the battery.
An easy test would be to see if you can copy all the files off it to a PC.

But my guess is that the SD card reader running in 1 bit mode is likely the root cause of all your problems.
I would recommend sending your Switch to a good repair shop have it fixed.
After that start with a fresh install of Hekate/Atmosphere.
Trying to re-use an old installations with custom modules/homebrew stuff sometimes causes these black screens too.
Injection an older/newer version of fusee.bin with another version of the files on the card also causes strange behavior sometimes.

 

[WhyBlu]

I don't think your NAND is corrupted.
If your SD card is formatted with exFat then you might have wrecked it when pulling the battery.
An easy test would be to see if you can copy all the files off it to a PC.

But my guess is that the SD card reader running in 1 bit mode is likely the root cause of all your problems.
I would recommend sending your Switch to a good repair shop have it fixed.
After that start with a fresh install of Hekate/Atmosphere.
Trying to re-use an old installations with custom modules/homebrew stuff sometimes causes these black screens too.
Injection an older/newer version of fusee.bin with another version of the files on the card also causes strange behavior sometimes.

My SD Card is FAT32, and they can be read on my PC, but regardless I backed it up and formatted it clean and installed new hekate and atmosphere files and it still didn't work. I also tried another confirmed working microsd card and install those fresh versions of hekate and atmosphere to no avail.

As for the 1-bit mode problem, I'd prefer if I did the fix myself (like I said, even if it involves micro soldering), as I have no repair shops that can do this type of repair, let alone any repair shops at all.

I will try running a version that is on my exact firmware (18.0.1), as I have only ran the latest ones.

Thanks!