Hacking Nintendo switch V2 picofly issue

MentendoSnitch

Member
Newcomer
Joined
Oct 17, 2024
Messages
18
Reaction score
3
Trophies
0
Age
27
XP
99
Country
Italy
I've got a V2 Nintendo Switch with picofly which gives me 90% of the times error =** and 10% of the times boots perfectly fine, i Just can think at insulation problems, but i would like to have some opinions, i modded a lot of V2 in the past but never had an issue like that, tried the rp2040-zero of waveshare and the new instinct chip, nothing seems to fix the issue, ofw boots Just fine

SOLVED: It was as I initially taught an insulation problem, I solved with some tape between emmc and the chip, I think that I will do that as a praxis from now on
 
Last edited by MentendoSnitch,
Does it always boot fine into OFW?
If so, then you can exclude the emmc itself as a point of failure.
If you have issues even booting into OFW, then you might need to reflow the emmc itself.
Heat sometimes causes the solderball connections to go bad.

It might be a bad connection.
It might be hard to see though.
You can measure that with a multimeter in diode mode.

Some OLEDs have the same issue (emmc initialization) with some model emmcs.
I think it was Hynix or Samsung emmcs.
Increasing the resistor values usually helps.
For details, look in the Picofly sticky thread.
There are way more OLEDs out there than V2 so maybe that is why people complain about the OLEDs more.
 
Does it always boot fine into OFW?
If so, then you can exclude the emmc itself as a point of failure.
If you have issues even booting into OFW, then you might need to reflow the emmc itself.
Heat sometimes causes the solderball connections to go bad.

It might be a bad connection.
It might be hard to see though.
You can measure that with a multimeter in diode mode.

Some OLEDs have the same issue (emmc initialization) with some model emmcs.
I think it was Hynix or Samsung emmcs.
Increasing the resistor values usually helps.
For details, look in the Picofly sticky thread.
There are way more OLEDs out there than V2 so maybe that is why people complain about the OLEDs more.
It Always boots fine ofw, when it boots fine cfw hekate shows emmc at full Speed (400mb/s) and no partition errors, I also noticed that It usually works when the console Is off from a long time (some hours/a day), i don't know if somebody got this kind of behavior before.
I tried different resistor values on cmd, Dat0 and clk (from 100 to 220 ohms on cmd and Dat0 and from 47 to 68ohms on clock), and tried to change different CPU cables, during the last change I even ripped a CPU (sp2) pad, but i've read that the glitch should work even with only Sp1, and that the pads on CPU are two Just for redundancy, however, nothing changed.
I Remember of someone on the picofly thread talking about the scl and sda pads to make the glitch easier, can someone give me a clue about that? Does that really work to reduce emmc initializing problems?
 
Last edited by MentendoSnitch,
Hi so i need help so when i go to settings while a game is running it crashes like atmosphere crashes here is the error code 2181-4008 (0x1f50b5)
 
Hi so i need help so when i go to settings while a game is running it crashes like atmosphere crashes here is the error code 2181-4008 (0x1f50b5)
Hi, that's not exactly the right way to ask a question here. You should open your own thread where you explain the issue, the console rev (V1, V2, OLED), the kind of mod (if picofly install or v1 mod via fusee). If you got a Picofly install It could be useful to have sono photos of the install.

However, the error code you sent Is Just Nintendo telling you that your console Is banned. You can still use all of the mod and console features, but you can't connect to Nintendo servers and online services.
 
Last edited by MentendoSnitch,
Yo thanks for the answer the problem got fixed a long time ago and sorry for not making a new thread im pretty new here so sorry. When atmosphere crashed thats the error code i saw so yeah but thanks for the answer. I apologies for not making a new thread and i should have deleted this thread when it got fixed but apologies
 
Yo thanks for the answer the problem got fixed a long time ago and sorry for not making a new thread im pretty new here so sorry. When atmosphere crashed thats the error code i saw so yeah but thanks for the answer. I apologies for not making a new thread and i should have deleted this thread when it got fixed but apolog
No worries m8, happy that your issue is solved!
 

Site & Scene News

Popular threads in this forum