Blank Screen, RCM okay, OFW does not boot

[Severence]

@Azriel

stage 1 boot

I always get a bit concerned when i see references such as this as it implies your using retrosix wiki guide… not to be mean to the author (the heart is in the right place) but to put it bluntly the guide is dumb af and promotes dangerous diagnostic techniques (which could cause permanent damage), pointless ones, incorrect terminology (for example " If your VSYS did not pull a short" ) poor choice of terms for rails, for example “VSYS” is a terrible term to use for the rail which the BQ IC generates (even though this is how the BQ IC defines it) about another x20 IC’s also use this term for completely unrelated I/O and they are, or can be completely different in voltage (which could lead to disastrous consequences if the user doesn’t know this) - I hope the author stumbles across this post at some point and fixes his guide, it’s shocking quite honestly and has probably destroyed more Switch consoles than it’s saved anyway,

@Azriel

Visually perfect but of course without function

@Azriel

It does indeed run

I’m a bit confused on this, does the Switch boot or no? I’m going to assume I’m misinterpreting the above and assume no and it’s a black screen throughout.

@Azriel

eMMC also had 1.8V present.

What does this tell you? I ask because there is two rails for the EMMC.

@Azriel

RCM then worked when I disconnected the battery briefly and then reconnected it

I’m not sure what you mean by this, do you mean you weren’t seeing the console in RCM state (in TegraRCMGUI) until you disconnected the battery and reconnected it? if yes then you have an issue here. I guess you using a Jig to get it into this state or?

@Azriel

Unfortunately, the switch still didn’t boot and so I first carried out a firmware update.

Again, need clarification, if it doesn’t boot and has a black screen how are you doing a firmware update? do you mean your generateing newer OS/FW files elsewhere (or you are capable of booting into some homebrew/CFW which can do it?) and then writing them to the EMMC?

@Azriel

This went through but unfortunately the switch did not boot afterwards

Ok, confusion again, this implies it did boot prior and now doesn’t boot, again you need to clarify (try making it clear as to your definition of “boot” also, ie: boots to Hekate, boots to OS, no boot at all, shows boot logo but doesn’t enter OS, only boots CFW and not stock OS etc etc )

@Azriel

The switch also behaves differently from time to time, sometimes I can boot AMS, sometimes not, sometimes the OFW also works.

Ok so now this is different to what you just mentioned prior. So it does infact boot both Atmosphere (that’s what you mean right) and stock OS but it’s intermittent, now I understand

@Azriel

Although it does benchmark and everything else well. But the longer the use, the less it works at the end of the day. After rebuilding it does work 1-2 times and then it starts to fall apart again.

It’s not impossible I suppose. Transfer the data to another module and see if the problem persists

@Azriel

Is there anything hardware-related that could explain this behaviour?

What you mentioned with the EMMC module is possible. The fuel gauge, Ram, SoC would also candidates which could also cause the symptoms your seeing (intermittent boot)