Hacking error 2101-0001

  • Thread starter Thread starter Acide0
  • Start date Start date
  • Views Views 17,342
  • Replies Replies 15

Acide0

Well-Known Member
Newcomer
Joined
Aug 21, 2016
Messages
83
Reaction score
9
Trophies
0
Age
47
XP
484
Country
Canada
Hi, someone bring me back a switch that I have install a trinket M0, the problem is that when it boot it give a 2101-0001 error, whebn you press power its reboot in loop, need to hold the power bouton.

Desolder the trinket same result, when I plug the psu the system don't go on same on computer. I could through my computer launch a payload like hekate but in hekate I could not launch exemple reinx it give me a black screen.

I have no nand dump so what I could do with that ?

Thank you for your answers !
 
I would advise trying a system restore. If that doesn't resolve the issue it sounds like you have a hardware problem. if you get the same bootloop issue trying to get to system restore then you definitely have a hardware issue.
 
Allready check sd even without the sd part itself does the same.

For a system restore you need to acces the the interface so in this situation à cannot.
 
Sounds like it cant find data on SD to me. I have a switch with the trinket installed too. It should boot to hekate if it cant detect the sd card (as long as you're using the universal uf2 file). You may want to look into flashing the universal uf2 file to your trinket. It helps in troubleshooting your issue.
 
its NOT a sd issue if it was the problem on ofw will not be there and rigth now the trinket is unsolder
I could launch hekate via my pc even do a nand backup with no problem.

My trinket install boot directly on atmosphere with the multi payloader loader found here .nx file in the 0 folder,
 
I was getting those errors with Reinx. Had to use that tool thing that lets you enable and disable the kips. Had to disable a kip then reboot from the toolkit menu. Test a game. If you get same error, re-enable the kip and reboot again from the toolkit menu. Should be good to go
 
  • Like
Reactions: 0000ff
this error happened to me too, WITHOUT cfw, on games that were from the eshop. What I was using was a Samsung MicroSD that i popped in out of box. What i did to fix issue was use the Format the Memory Card in the System Settings, and then i initialized the system again, and I have never gotten the problem again after
 
  • Like
Reactions: iriez
this error happened to me too, WITHOUT cfw, on games that were from the eshop. What I was using was a Samsung MicroSD that i popped in out of box. What i did to fix issue was use the Format the Memory Card in the System Settings, and then i initialized the system again, and I have never gotten the problem again after

I could not initialized the system because I have not acces to it ! When the system boot after the nintendo logo it give me this error and when turn off it reboot by itself and do it again with or without sd... its not happening just when I launch a game like you...

--------------------- MERGED ---------------------------

So after launching biskeydump it magically fixed itself? Nothing else was done?
I have done a nand dump just before and launch biskeysdump thats it !
 
I could not initialized the system because I have not acces to it ! When the system boot after the nintendo logo it give me this error and when turn off it reboot by itself and do it again with or without sd... its not happening just when I launch a game like you...

--------------------- MERGED ---------------------------


I have done a nand dump just before and launch biskeysdump thats it !

Everyone has access to a system initialize process.

https://en-americas-support.nintend...ze-nintendo-switch-without-deleting-save-data

Follow those instructions next time from a power off state, though I would recommend deleting data and doing a 'full wipe' if you are having issues if the non-save-data deleting process doesn't work.

Doing the nand dump wouldn't affect anything. So launching biskey affected it somehow?

I had a system brick on me after sending a biskeydump payload. I was in the process of dumping the keys on a freshly modded system. It made no sense to me and I dont think the payload caused the brick. I think it was just a shitty coincedence and the hardware happened to fail in that moment. What was frustrating is that i couldn't launch the system restore. It would get stuck at that same spot even when launching system initialize mode.

There are a few devices that can fail on the switch that will stop it from booting but will allow the switch to operate normally. For example, if the system cannot go through its chain of trust processes and get the correct signatures/payloads, then you cannot get past the boot screen. If a device fails in this chain it may have no other purpose other than security.

This means you could for example run a payload and launch linux and use lakka, despite being stuck in a boot loop on OFW.

Im not sure whats wrong with your switch, but I wouldn't discount the possibility that you may have a pending hardware issue. Since you already tried without the sd card I think its logically obvious the sd card is not what was causing the issues.
 
  • Like
Reactions: gameboy
hold both the volume up/down and turn on the system, then initialize it, then use the 'format' option in the nintendo switch itself to format the sd card and see if that works
 
Hello, i get this error when i try to put m92t17 instead of m92t36, i lost 3h with this
 

Site & Scene News

Popular threads in this forum