Hard modded my first switch soldering went well but i think i bricked it. need help!

[Wizardmonkeyjj]

Hello everyone, I just modded my switch last night and made a little mistake. i believe i should've updated the stock firmware before modding but i was stupid and didn't. (ill post pics of my soldering which could be a little bad but i dont think it would lead to this problem.) okay so after modding my switch everything went perfectly i was able to boot into stock cfw and emummc with atmosphere and run all the apps i wanted. then comes where the problems started. i downloaded games from a tinfoil freeshop, realized my switch was out of date so i wasnt able to play some of the games i had just downloaded. i decided to try to update my emummc. i successfully updated it to 18.1.0. but i used the sig patches from. 19.0.0 cause they were the only ones i could download on sigmapatch

now the first problem started. i wasn't able to launch tinfoil in the new update so i kept trying new tinfoil files to no avail i never got tinfoil running again before i screwed everything else up.

next problem is that im unable to boot into stock firmware from hekkate anymore. it will just get me stuck on the nintendo switch boot logo,

last problem is whenever i try to launch into my emummc or try to launch fusee.bin from hekkate it says "a panic has occurred in atmosphere title id: 010000000000002B"
now there is no foler in the contents folder of atmosphere with that title id that i can delete to even try to fix that, i did try the method of grabbing files from your emmc backup and replacing them but that didn't work either

lastly i swapped my sd card out to a brand new one and just reinstalled everything fresh. my switch still boots hekkate every time but running sysnand, emummc or trying to boot fusee.bin i get nothing but problems. I have 1 v1 switch unpatched that ive had for a while and of course problems have came up but nothing like this. did i just destroy my console somehow?

 

[randy_w]

Your cpu ribbon cable needs some work, it's floating on top of sp1 and sp2 capacitors and may touch the heatsink and cause shorts. But if it can boot to hekate then it's not causing problems right now and you can worry about it later.

Since you are using an sx core type of picofly i'd say your problem is caused by poorly designed picofly that introduces interference to emmc data lanes, I've dealt with this type of chips before. Remove the emmc module and solder wires to its A/B/C/D/3.3V points directly:

Cut the ribbon cable on sx core chip then solder A/B/C/D/3.3V wires directly to the exposed pads:

Can't remember which one's which, also there are many different designs so veryfy the connection with a multimeter yourself. Or you can buy a picofly chip in hwfly formfactor, avoid those sx core type of chips.

Connect the emmc module back to its original position and power on. First thing you need to do is make a full backup of your emmc. Check your emmc partition table and see if it's empty. If all partitions are there then try to boot to maintenance mode and do a system restore, if that doesn't work dump your prod.keys and format your user partition manually in nxnandmanager. If that still doesn't work, you need to do a nand rebuild with emmchaccgen with your own prod.keys, generate system titles and boot0/1, then write them to emmc with nxnandmanager. You can follow sthetix's guide for this part.

 

[jkyoho]

to those who worries about cpu flex may cause short or putting Kapton tape on to of flex "better protection", you don't need that and bigN has been thinking ahead for you


The white isolation film already applied on metal shield surround cpu die by factory from Day1.

 

[alecocr20]

I think your problem is only a configuration issue since you are still able to boot to Hekate and the modchip is doing what it is supposed to do.
I'll restart again, update ofw to the latest, create a new emummc and see if it works.