Im pretty sure it’s the charging port. Second opinion?Well if your port doesn't work you will have to fix it since you ain't able to charge. But based on what you provided so far it point to that power management chip i mentioned
Im pretty sure it’s the charging port. Second opinion?Well if your port doesn't work you will have to fix it since you ain't able to charge. But based on what you provided so far it point to that power management chip i mentioned
Im pretty sure it’s the charging port. Second opinion?
I know. I assume this means it’s the charging port at fault for the 2101-0001 error. Do you agree? I just really want to make sure I have the right part before opening the switch up.
I know. I assume this means it’s the charging port at fault for the 2101-0001 error. Do you agree? I just really want to make sure I have the right part before opening the switch up.

Hello Folks
Is there a complete guide from 0 to hekate,atmosphere, syspatch, lockpick ....etc.?
THX in advance




After some digging, I found every method for bypassing supernag to be outdated (Gag Order, switch-sys-tweak), and some other method here:
OK. Found a way to remove nag, that even Reset required version can not remove:
1. Mount SYSTEM via hacdiscmount
2. Open /save/8000000000000045 via hexeditor
3. Find titleid for update (8 bytes) and zero next 8 bytes.
Does any workaround work on 20.3.0? Pretty sure it's a supernag considering there is no pending update.

What do you mean by Exosphere? DNS MITM is already set up, there isn't much else I'm aware of that can be configured about Exosphere that's relevant here.Just set up exosphere and I guess update your firmware to like 20.5.0 if you don't want to go to 21.x.x and you won't get nag.
What do you mean by Exosphere? DNS MITM is already set up, there isn't much else I'm aware of that can be configured about Exosphere that's relevant here.
Are you saying a system update to any version does the trick? As in, using Daybreak to install 20.5.0 will clear the nag?

All of these are set up. Why does the nag still occur? It's clearly a supernag, the system update dialogue has 2 options when attempting to open the browser.If you have setup server communication block like with exosphere you can prevent the nag, since your serial number is blanked out, so it doesn't nag you about games update and firmware update, well you have to use both.
You should setup incognito (nowadays known as Exosphere), its a setting that blanks your console serial number while atmosphere is running (so you dont get a console ban). DNS MITM is a DNS resolver built into atmosphere that blocks internet traffic to nintendo servers.
All of these are set up. Why does the nag still occur? It's clearly a supernag, the system update dialogue has 2 options.

So is there no workaround on 20.4.0? In what situations does your earlier suggestion work:If you set it up after the the system know there is an update it is too late, you need to have it up and running when you update the firmware.
Just set up exosphere and I guess update your firmware to like 20.5.0 if you don't want to go to 21.x.x and you won't get nag.
So is there no workaround on 20.4.0? In what situations does your earlier suggestion work:
hi im trying to install dlcs on dbi i just drag and drop the dlc files in using the MTP responder method but it doesnt seem to install the dlcs can i get some help?

After an update using Daybreak (20.3.0->20.4.0), the nag persists.You can use any firmware above your current firmware.
After an update using Daybreak (20.3.0->20.4.0), the nag persists.

Yes,then you must be doing something wrong, is your serial number blanked out?
blank_prodinfo_emummc=1 in exosphere.ini and settings shows all zeroes.Yes,blank_prodinfo_emummc=1inexosphere.iniand settings shows all zeroes.