[New to repairs] No stage 2 boot, no shorts, charging, stage 1 with missing power rails

One of the pins was sketchy.

I.
Am.
Delighted.
Thank you so much @Severence , I’ve learnt so much! And @PhynxVT and @coda as well.

Note from present-Vince to Vince-from-the-past: improve your soldering skills on QFNs.

Now that I built enough confidence, I can get back to Switch #1. Here’s my battle plan:

  • Change the fuel gauge (again)
  • Change the MAX IC below the SoC (again)
  • Change MAX 77620
1 Like

I too suck at soldering QFN’s. The best thing you can do for yourself regarding them is ensuring that all the pads have a proper amount of solder on them from the get go, and that you don’t flood the middle ground pad with too much solder. As with everything else in this hobby things become easier the more you practice.

Glad you got one of em running, it always feels good especially when its taken you a while to get there :slight_smile:

2 Likes

I don’t think you need to change the fuel gauge again unless something went terribly wrong during the install or the IC is damaged (they are fragile) or because you think they are are used / poorly reballed as we talked about earlier.

I’d have another very close look at this board examining all ICs and edge on like what you did on Switch #2 - feel free to post pics if you want me to take a look.

I can’t see the issue being the main PMIC at this stage but in all honesty it could be… or anny number of other IC’s in impact damage scenarios.

One thing, which you may have already mentioned, did you try putting mild pressure on SoC and ram while prompting to boot to see if theres any change? It migh also be worth making sure the EMMC is good on this switch by dumping it’s contents elsewhere - this can done on an unpatched board (though be careful about not burning the update fuses) or by dumping on PC using low voltage EMMC adapter or a homemade SD card adapter

It’s not doing anything, still stuck in 1st stage boot.

Mine is a patched Mariko

So I’ve just started researching how it all works. From my understanding, some of those readers can only access user related partitions, while others (and more expensive ones) can also read the boot partitions. I suppose I need the latter?

Before I do that, what’s bugging me it the fact that it’s detected by TegraRCM as an RCM device, and it has a QR code on the Nand. I’m probably wrong, but none of the other motherboards I saw online (or on Switch #2) had one. Is it because it’s an aftermarket one, and therefore not paired to this device? In which case, trying to fix it is pretty pointless, isn’t it?

is this switch #2 ?

Right so you won’t be able to dump the boot 0/1 parititions without more specialised tools (mmcblk) but it doesn’t matter… these partitions are largely unimportant (as donor partitions can be made and used) and we are just looking to test that the EMMC is working so dumping the other partitions is fine for this. Also mmcblk is pretty much terrible anyway in terms of design and functionality soooo there’s that too :slight_smile:

Nope completely normal to have them though it’s a coin toss which boards do and don’t have the stickers

No, that’s switch number 1, the one with the missing 1.35V rail. I’m still waiting for my EMMC reader to arrive, to be able to rule that out - or find that it was faulty from the beginning. It should be there in a couple of days.

Also, Switch #2 (the one that was fixed) couldn’t get passed the installation process because the left joycon wouldn’t be recognized. So I took the rail out and noticed it was slightly different from the right one (more wear marks), but more importantly, the ribbon was ripped beyond repair.

So I tried the other joycon rail from the other Switch, and it wouldn’t work either… because it was completely corroded, to a point where copper had been completely eaten away. Never mind, I thought, they’re cheap, let’s get new ones.

I finally got the parts tonight… but the Switch is now stuck on the Switch logo! I tried going into maintenance mode, and it reads a 2134-0501 error. I’m pretty sure that’s M92 related, isn’t it?

I don’t recall ever having the error myself but as far as I can see online all resolutions seem to revolve around the M92 IC (though that hopeless Switch repair wiki mentions the main PMIC and fuel gauge…)

But, given that this problem only exhibited itself after you connected up a corroded connector it would suggest that this was the cause of this new fault (assuming not a coincidence) so perhaps that has killed something - sorry I’ve done very little in tracing out the joycon related circuit (and what it has or hasn;t got in common with the M92 IC if at all) so can’t help much in this regard but you might want to see if the symptoms change with both ribbons disconnected (just incase something jammed in the connectors - which you’ll want to check for) and then after also checking the M92 IC for shorts and the like again.

I’d also take a very close look at the joycons (assuming they came with this switch) as if the rails were correded the joycons themselves will likely will have corrosion on the pins too.

Of course and I’m sure you have been. Make sure to disconnect the battery prior to any of this.

Just found this which seems to confirm my thinking - i think :wink:

Don’t understand German, but from the visuals, same error, same corroded joycon pins (likely as the initial cause) - presumably killing the M92 IC (somehow).

So yeah, after going over what i mentioned earlier failing that, I’d swap out the M92 IC again and then make sure your new joycon rails pins and contacts all look good prior to hooking up power again :slight_smile:

At first I thought « not again », given the previous trauma. But I need practice, and it went pretty smoothly this time! As it turns out, the key to not having components flying everywhere is… to not blow crazy air flow at them… you were right again. I’m using a much reduced air speed now.

Anyway, since all the pins were looking good, I turned the switch on. Now I get 2101-001. Since I’m now forming this mental model you’ve mentioned, I went back to M92 and took some readings. Some are wrong I think.

But the chip is new, so did a cap blow? When soldering m92, something crackled and smoked. I thought it was merely the flux sizzling.

2100-001 is generally an I2C error. Take a look at the following diagram, on the rear side of the battery connector (same side as the fuel gauge) there are two TP’s (one for SDA and SCL). If you look at the M92 image you can see where these pads SHOULD buzz out too. Also, if you notice on the SDA pin of M92 it leads to two small unpopulated pads. In between those two pads is a small trace. Verify you have continuity through both pads to the pad on M92. Also verify you have enough solder and a good connection for both these pins on M92.

Good news is that this error means you’re almost getting to the homescreen, so once you solve it you SHOULD be in the clear and have a functional console again :slight_smile:

Yeah not right. I’d retrace your steps and lift the M92 IC and see if these shorts clear. Bit hard to tell but your M92 IC is possibly slightly a skew (though could just be your cameras angle) which may be the cause, if lifting the IC resolves the shorts, try reinstalling the IC again and after check again for those shorts and if not present still do a thorough inspection of the IC edge on looking at all pins. if those same shorts are present upon reinstall then it suggests the IC is bad.

Unlikely to be the caps. Crackles and smoking is probably indicating your running your hot air too hot I’d guess.

Or fake… ht tps:// youtu .be/gJyjI45RQOY
I bought those before you guys warned me against Aliexpress.

Yeah maybe, though didn’t the other one work initiatially? presumably from the same seller?

As they typically work or don’t, unless you got really unlucky and the seller was selling a mixture

I’d just check that those shorts clear after removal before jumping to conclusions just yet :slight_smile: it might well be fake but best to rule it out first (then get a refund on aliexpress once proved )

1 Like

The chip wasn’t from the same seller.
I took it off, it relieved the short. Put it back again, the short was back.
Took another chip from a donor board, and now it’s working perfectly! Soldering an M92 chip is getting easier every time, I’m glad.

I can now hopefully focus on switch #1 as soon as I receive the EMMC reader. Will keep you posted.

Thank you again @Severence and @coda

1 Like

I’ve bloody jinxed it. I got a brand new pair of joycons. The left joycon syncs, it’s recognised when inserted (red bar), and it charges on other switches.
Since the left rail is also new, and other left joycons won’t charge on that rail. I think the issue lies on the motherboard. Need to investigate further.

does your fan work? do you have a small diode behind the fan connector on the mobo? That part when it fails will cause issues with joycon charging. There are two small IC’s (usually with a PU marking) that can also affect joycon charging if bad. Obviously usual culprits of contacts, ribbons, and connectors also apply./

1 Like

In addition to what @coda mentioned it’s also worthwhile popping the pin out on the left rail and checking continuity to/from the contacts to the other end of the ribbon contacts. I’ve got a few of these rails from China (or a Chinese seller listing within EU) listed as “New” but in actuality the rail/s themselves are refurbished with black enamel covering the “defects” in the existing paint with “new” aftermarket ribbons put in (usually of lower quality). I’ve had a few on occasions (much like with the supposedly “new” but in actuality refurbished LCD’s for Switch backlight ribbons) with hairline tears in them or hard folds which breaks the copper traces which sometmes only reveal themselves while wiggling while checking continuity across the lines. Most likely what Coda mentioned is your issue but worth checking :slight_smile:

:man_facepalming:
I’m so embarrassed… there was flux residue inside the joycon connector on the motherboard. So sorry for the hassle!

don’t be, that’s good news, easy fixes are a wonderful thing.

1 Like

I finally received the EMMC reader!

…aaaand the NAND is not recognized. I tried with other NANDs from other boards, it works like a charm with NxNandManager, but that one isn’t. So it’s been a NAND issue from the beginning. Anything I could attempt, in your opinion?