don't be a d*** it depends on the motherboard issue, user shall take a picture of the board to be sent via discord to confirm if their issue is linked with the above solution.Dont use capacitors from phones or any other elecetronics. They all have different properties.
is it hard to tell the solution here? Why go to discord:
Here is the solution why some of you guys stuck at Nintendo Joy-Con logo:
Those that are having 'stuck on joycon logo' issues after installing their sx core, a solution seems to have been found theres attached this close-up corner of the erista motherboard with the area you should check, this two parts can be easy damaged when removing the nvidia metal shield and replacing it back. The Mariko motherboard also has similar two caps in that same area as highlighted in the erista photo below. Click Image to see it.
Image
You are the one, who is trying to be ....! Instead sending everyone to discord (there might be people not using discord) you could just post, what the issue could be and what the solution is. There is already solution, that was posted on gbatemp and a picture already shows the issue, which capacitors could be damaged, when the switch is stuck on joy-con logo. You dont need to confirm anyone if their issue is linked with the above solution, when the picture I posted already shows, where to check if somebodys switch got stuck on joy-con logo.don't be a d*** it depends on the motherboard issue, user shall take a picture of the board to be sent via discord to confirm if their issue is linked with the above solution.
I have a mariko switch too. I'm still waiting for the capacitor. I will confirm if replacing it works when I get it.Can anyone confirm 0201 0.1uF is 100% correct and same for V2?
I have a V2 that froze in menu then now wont get past nintendo logo after reboot on OFW or CFW. Can enter TX boot menu fine.
I want to see if maybe replacing those caps will fix a Mariko or not.
A couple times it blue screened but then went back to black screening after Nin Logo.
that's not the case of everyone.... from which one of my consoles is stuck but not due to the two capacitors its something else, i use the group rocket tx chat, now instead of being a ****** the solution for few users could be the above...... or else you could post other fixes that are coming from the moon.....You are the one, who is trying to be ....! Instead sending everyone to discord (there might be people not using discord) you could just post, what the issue could be and what the solution is. There is already solution, that was posted on gbatemp and a picture already shows the issue, which capacitors could be damaged, when the switch is stuck on joy-con logo. You dont need to confirm anyone if their issue is linked with the above solution, when the picture I posted already shows, where to check if somebodys switch got stuck on joy-con logo.
Aha, thats why 5 users above confirm that they damaged their two capacitors at the side of cpu-shielding after checking it. One of them already confirmed, after repairing that his switch boots just fine now. Why shouldnt the solution I just posted coming from the moon when it was from TX support, that was posted on gbatemp?? There are many other capacitors around the cpu shielding and the only way to find out, which is damaged is to check each of capacitors around cpu-shielding and on the cpu. Mostly people damaged those two capacitors at the left side from the cpu-shielding. How is thats not the case of everyone, when there are many reports around gbatemp and here that those two capacitors at the left side were responsible for stuck on joy-con logo?? Sure you have to check other electronics too, where you might be damaged it but others solved it by repairing those two capacitors. Its weird that you CANT still tell those people, who have such issues, which capacitors on your side was damaged! Yet still behaving like a ....!that's not the case of everyone.... from which one of my consoles is stuck but not due to the two capacitors its something else, i use the group rocket tx chat, now instead of being a ****** the solution for few users could be the above...... or else you could post other fixes that are coming from the moon.....
you sound like a teenager mate... relax lolAha, thats why 5 users above confirm that they damaged their two capacitors at the side of cpu-shielding after checking it. One of them already confirmed, after repairing that his switch boots just fine now. Why shouldnt the solution I just posted coming from the moon when it was from TX support, that was posted on gbatemp?? There are many other capacitors around the cpu shielding and the only way to find out, which is damaged is to check each of capacitors around cpu-shielding and on the cpu. Mostly people damaged those two capacitors at the left side from the cpu-shielding. How is thats not the case of everyone, when there are many reports around gbatemp and here that those two capacitors at the left side were responsible for stuck on joy-con logo?? Sure you have to check other electronics too, where you might be damaged it but others solved it by repairing those two capacitors. Its weird that you CANT still tell those people, who have such issues, which capacitors on your side was damaged! Yet still behaving like a ....!
on 10.0.0.4 firmware and on the
If I may ask, how do you update the firmware considering that I cannot boot up in OFW or CFW?Try updating to 10.0.4 first. Mine was black screening after Nintendo logo when I was on 7.0.1.
Stuck on the nintendo switch logo after booting in either custom or original fw with sx core. I'm on 10.0.0.4 firmware and on the latest sxos.Hope someone can help me here, I've installed the SX Core (V1) and I can boot into the SX OS 3.0.2 (Firmware Version v1.1). But whenever I click on "Boot custom FW" or "Boot original FW" it boots up to the Nintendo Logo and then it just gets stuck there.
Things I've tried;
Showbox jiofi.local.html tplinklogin
My Switch is the Smash Brothers Bundle which is updated to OFW 9.1.0.
- Reseat the NAND on the mod chip
- Different SDCards (exFat and FAT32)
- Used SX OS 3.0.0 and 3.0.1, same result
- Used SX OS 2.X.X give me the "BOOT.DAT?" screen
- Dumped NAND and RESTORE
- REPAIR GPT
- CREATE EmuNAND
- Boot using (EmuNAND enabled and disabled)
- Boot into hekate_ctcaer_5.3.0.bin via the Payloads works. But can't boot anything else there.
I'm not sure what else I can do or try. I've tried searching for how to use the "Debug Port" on the mod chip but can't find anything.
Is my Switch a goner?
Before installing, your Switch was booting fine right? Maybe somehow you damaged the nand chip while installing or as you said your nand chip might be corrupt.Hope someone can help me here, I've installed the SX Core (V1) and I can boot into the SX OS 3.0.2 (Firmware Version v1.1). But whenever I click on "Boot custom FW" or "Boot original FW" it boots up to the Nintendo Logo and then it just gets stuck there.
Nox Vidmate VLC
Things I've tried;
My Switch is the Smash Brothers Bundle which is updated to OFW 9.1.0.
- Reseat the NAND on the mod chip
- Different SDCards (exFat and FAT32)
- Used SX OS 3.0.0 and 3.0.1, same result
- Used SX OS 2.X.X give me the "BOOT.DAT?" screen
- Dumped NAND and RESTORE
- REPAIR GPT
- CREATE EmuNAND
- Boot using (EmuNAND enabled and disabled)
- Boot into hekate_ctcaer_5.3.0.bin via the Payloads works. But can't boot anything else there.
I'm not sure what else I can do or try. I've tried searching for how to use the "Debug Port" on the mod chip but can't find anything.
Is my Switch a goner?
My Switch is V1 patched Eirsta, 10.0.4, try to change another SX Core, put the NAND chip to the original socket, still the same problem.Hope someone can help me here, I've installed the SX Core (V1) and I can boot into the SX OS 3.0.2 (Firmware Version v1.1). But whenever I click on "Boot custom FW" or "Boot original FW" it boots up to the Nintendo Logo and then it just gets stuck there.
Things I've tried;
My Switch is the Smash Brothers Bundle which is updated to OFW 9.1.0.
- Reseat the NAND on the mod chip
- Different SDCards (exFat and FAT32)
- Used SX OS 3.0.0 and 3.0.1, same result
- Used SX OS 2.X.X give me the "BOOT.DAT?" screen
- Dumped NAND and RESTORE
- REPAIR GPT
- CREATE EmuNAND
- Boot using (EmuNAND enabled and disabled)
- Boot into hekate_ctcaer_5.3.0.bin via the Payloads works. But can't boot anything else there.
I'm not sure what else I can do or try. I've tried searching for how to use the "Debug Port" on the mod chip but can't find anything.
Is my Switch a goner?