Hacking Stuck on Switch boot logo after ChoiduJour Downgrade from a broken 8.1.0 to a clean 5.1.0

[antoclass]

Hi everyone,

Earlier this week I accidently connected my switch to another network without the custom dns, the switch downloaded the 9.XX upgrade so I decided to backup my saves using checkpoint and restarted the console to erase the downloaded update like i used to do on earlier firmwares.

The switch would not boot up again I had the error 2101-0001.

For what I saw online it can hardware issue but it would not make any sens because the switch worked fine earlier.

I tried updating to the latest atmosphere wich is compatible with every firmware ; my switch is a launch model from 2017.

So I backed up my (broken ?) nand and followed this guide to downgrade my console to 5.1.0 https://switch.homebrew.guide/usingcfw/manualchoiupgrade wich is known to be compatible with ChoiduJour
I followed it until the end so I've "formated" my SYSTEM using hacDiskMount to get a default nand .

Neither Atmosphere (after restored default hekate) or OFW will boot, it's stuck on the Nintendo Switch Boot Logo.

My battery is running really low so, firstly how can I charge my switch before retoring my nand backup (made after error 2101-0001) and secondly what are the firmware compatible with ChoiDuJour to create a 8.1.0 nand or even a 9.1.0.

Thank you in advance for your patience with all of this.

 

[shchmue]

1. plug your switch into the official charger and leave it for a few hours, it can't boot below a certain battery level
2. when you downgraded, did you delete everything in the system and user partitions? if not, incompatible savedata from later versions can cause weird errors
3. ChoiDujour only supports up to version 6.1.0 as a target, no higher

 

[antoclass]

It's probably dead my only bet is to get the battery out of the console then charge it, i was getting 30 seconds to boot to atmosphere using fusee gelee, but it wasn't enough to get to the charging part of horizon, after I plugged it to the wall charger when it booted i saw the charging icon in red so the console in the top half of the screen ; it had not enough time to get to the charging part the ac adapter wasn't recognized.

 

[vlone59]

Hi,

So, it may sounds funny but I actually bought Antoclass's Switch.
I know him IRL for a long time but he haven't told me that he opened a thread here.

So, long story short:

The switch doesn't seem to be charging at all, I have to charge the battery with an other switch every time it gets low (dead charger chip?)


I downgraded all the way down to 5.1.0 = first boot failed, stuck on the switch logo.

Cleared all partitions and pasted ChoiDuJour files = still stuck on the switch logo.

I get this screen in every scenario except if I boot on OFW, which result in just a black screen and no Nintendo logo at all.


Upgraded to 6.1.0 with the same process = error 2101-001 in every scenario (Atmosphère, OFW...)


I checked fuses, and they seems burnt up to 10, which correspond to 8.1.0, but ChoiDuJour do not support that FW.

I will give it other tries tomorrow but it looks like a dead end...


Also, I tried with both FAT32 and ExFAT SD Cards, it didn't changed anything.

If anyone have an idea...


thanks a lot

 

[ZachyCatGames]

Hi,

So, it may sounds funny but I actually bought Antoclass's Switch.
I know him IRL for a long time but he haven't told me that he opened a thread here.

So, long story short:

The switch doesn't seem to be charging at all, I have to charge the battery with an other switch every time it gets low (dead charger chip?)


I downgraded all the way down to 5.1.0 = first boot failed, stuck on the switch logo.

Cleared all partitions and pasted ChoiDuJour files = still stuck on the switch logo.

I get this screen in every scenario except if I boot on OFW, which result in just a black screen and no Nintendo logo at all.


Upgraded to 6.1.0 with the same process = error 2101-001 in every scenario (Atmosphère, OFW...)


I checked fuses, and they seems burnt up to 10, which correspond to 8.1.0, but ChoiDuJour do not support that FW.

I will give it other tries tomorrow but it looks like a dead end...


Also, I tried with both FAT32 and ExFAT SD Cards, it didn't changed anything.

If anyone have an idea...


thanks a lot

2101-xxxx errors are i2c related. That combined with the fact that it won’t charge indicates that one of the power related ICs is dead.

 

[tabzer]

I don't understand where this idea that ChoiDuJour doesn't support current firmware comes from. I used it to install my latest FW on emuMMC without a hitch.

 

[ZachyCatGames]

I don't understand where this idea that ChoiDuJour doesn't support current firmware comes from. I used it to install my latest FW on emuMMC without a hitch.

ChoiDujour and ChoiDujourNX are two completely separate/different programs.

 

[tabzer]

Ah, I see. I don't know much about ChoiDujour then. Wouldn't the user be able to use hekate/atmosphere to bypass fuse checks to use ChoiDujourNX to install the latest firmware? I don't understand the purpose of using ChoiDujour in this context.

 

[Kafluke]

Ah, I see. I don't know much about ChoiDujour then. Wouldn't the user be able to use hekate/atmosphere to bypass fuse checks to use ChoiDujourNX to install the latest firmware? I don't understand the purpose of using ChoiDujour in this context.

Look at the guide that the OP posted. It's a manual downgrade guide using the PC version. The switch won't charge. It has nothing to do with choidejour.

 

[tabzer]

Look at the guide that the OP posted. It's a manual downgrade guide using the PC version. The switch won't charge. It has nothing to do with choidejour.

For some reason I mentally compartmentalized @vlone59 and OP separately. I know the battery not charging could be a physical issue, non-fixable by software restoration, but he did say he could charge it using another Switch. Also, there has been no mention of recovery mode, which has been known to fix botched firmware upgrades.

 

[vlone59]

Hi,

Thanks all for your answers.

Sounds like a chip issue to me too.

I will check for shorted capacitors tonight.

Also, I forgot to mention that I tried recovery or maintenance mode without any success, it never appeared.
Is there any payload to force it to boot the switch in maintenance mode ?

And yes, Atmosphère doesn't care about fuses so it doesn't looks like a fuse issue

Anyway it's still strange that it haven't booted even on the error code on FW 5.1.0

Thanks

 

[ZachyCatGames]

Hi,

Thanks all for your answers.

Sounds like a chip issue to me too.

I will check for shorted capacitors tonight.

Also, I forgot to mention that I tried recovery or maintenance mode without any success, it never appeared.
Is there any payload to force it to boot the switch in maintenance mode ?

And yes, Atmosphère doesn't care about fuses so it doesn't looks like a fuse issue

Anyway it's still strange that it haven't booted even on the error code on FW 5.1.0

Thanks

Maintenance mode is the same as normal mode except a few sysmodules don’t run and it boots the maintenance applet instead of qlaunch. It’ll run into the same 2101-0001 error.

 

[vlone59]

So, after a check, it looks like I have only one shorted capacitor.

The thing is that from threads I have read, it is not the same capacitor.

Here is a picture :

[Sorry I cannot had this picture --"]

Can it be just a dead capacitor or the whole M92T36 chip dead ?
Thanks

 

[The Real Jdbye]

So, after a check, it looks like I have only one shorted capacitor.

The thing is that from threads I have read, it is not the same capacitor.

Here is a picture :

[Sorry I cannot had this picture --"]

Can it be just a dead capacitor or the whole M92T36 chip dead ?
Thanks

If it's just one capacitor, it's less likely to be the chip but it could still be.

 

[vlone59]

here is the picture : imgur . com / gallery / wnCLH8W

I checked the pin5 and 0v
I but the ground on the same I used to check shorted capacitors, so it sounds like there is a big probability that this chip is dead isn't it ?

 

[vlone59]

Hi guys,

So just a quick update, I received the chip and a friend of mine replace it (beceause I do not have that kind of hardware)

And now the Switch is working perfectly fine.
No more errors and it is now charging

so thanks to all of you guys for your help !