I will tell you all point blank its rajnx fw, use this and expect a FULL brick that cant be recovered PERIOD!
I have been using tumGER for weeks, as well as reinx with our SwitchME chip with ZERO issues what so ever, not even the slightest hiccup.
Last night I decide I will try rajnx because why not? I like to check everyone's cfw to see if they have any benifits over others or some new patches, also to see if they will brick a system (I was not prepared for it to brick this bad).
So I made a full nand backup last night along with boot 0/1 just in case.
After testing rajnx it seemed like it was OK. I went on to test tinfoil and install a few games of mine I made backups of.
Games installed as they should, played some Mario Odysseus for a bit to test and moved on to zelda, everything was cool. Mind you console is in the OFFICIAL dock the entire time. Fast forward to today, threw on some octopath, console was docked in the OFFICIAL dock, after 1 maybe 2 mins in octopath console fully shuts off without warning, black screen wont turn on when I press power. Remove from dock, console wont power on. Try rcm and see if SwitchME will launch the payload (NOPE) gets me thinking there is no power from the battery because switchME needs to be powered from the battery when not docked. Plug it into my mac with a usb C (that works with the switch not some pos) throw the console into rcm launch a payload and poof hekate loads. Now I do the motions of checking the battery, nand, keys blah blah blah.
Keys all look good, battry is pretty much FUCT as its showing 0+ mA on the right side for charging.
Flash boot 0/1 and reboot again with the console plugged into the mac. shows nintendo logo for a .5 sec and shits itself.
back to rcm mode again this time to flash the full nand. NOPE that wont work because it cant draw enough power so it shits the bed again.
Thankfully I have the SwithcME installed so I pop the console back in the dock, OH would you look at the SwitchME loads instantly even further telling me this cfw totally fuct the battery/controller along with who knows wtf else at this point.
Proceed to fully flash my nand backup (takes forever but I'm hopeful) I figured after the flash it "should" fix the issue for the boot loop.
...NOPE
So now I start testing the voltage behind the battery. I'm only getting .5v so that's an issue...
But docked this still shouldn't be the case as it has enough power to flash the nand when using hekate but could not when using ucb to pc.
So this is my only warning to anyone who uses cfw, maybe raj sould test the hell out of his cfw before releasing anything onto the public.
I mean bro test, test, and TEST more until you know its not going to fuck someones system!
Take a page from our book developing rebug, we never released anything without testing it on our on systems hundreds if not thousands of times before we released anything so it was BUG free.
At this point you are the new waninkoko but for the nintendo scene
Anyway I'm off to the store to go waste another $350 thanx home boi