Hacking Switch V2 Picofly ==* error code and boots to nintendo os

  • Thread starter Thread starter mausfany
  • Start date Start date
  • Views Views 2,341
  • Replies Replies 2
  • Likes Likes 1

mausfany

New Member
Newbie
Joined
Nov 23, 2024
Messages
1
Reaction score
1
Trophies
0
Age
27
XP
30
Country
Spain
Hello! I recently installed an rp2040 picofly from aliexpress on my v2 nintendo switch. When I installed it the connections were good and everything turned out great, I even booted it and it showed the "No sd card" text with the raspberry logo.

I was very happy so I was ready to assemble the switch and finally homebrew the switch, but the thing is that when I turned it on, it went to the nintendo os, not to the picofly os. It does have the firmware installed since it showed the hack the first time.

It gives an ==* error code, I don't know what it can be, I haven't seen much people with the same issue. I can send pictures if you need them.
Post automatically merged:

Fixed! It was just that the mosfets in the cpu flex were in contact with the metalic shield and it shorted and the picofly couldn't boot, it's working now and everything is going fine! :)
 
Last edited by mausfany,
  • Like
Reactions: MsTiaDaniel
Hello! I recently installed an rp2040 picofly from aliexpress on my v2 nintendo switch. When I installed it the connections were good and everything turned out great, I even booted it and it showed the "No sd card" text with the raspberry logo.

I was very happy so I was ready to assemble the switch and finally homebrew the switch, but the thing is that when I turned it on, it went to the nintendo os, not to the picofly os. It does have the firmware installed since it showed the hack the first time.

It gives an ==* error code, I don't know what it can be, I haven't seen much people with the same issue. I can send pictures if you need them.
Post automatically merged:

Fixed! It was just that the mosfets in the cpu flex were in contact with the metalic shield and it shorted and the picofly couldn't boot, it's working now and everything is going fine!
not sure if you will read this but im having the same issue on the switch lite and tried fixing it the same way you did but mine still gives me a blue light followed by an ** error and the github says to check the rst and i have multiple times but no joy. its still goes blue ** then boots to official firmware.
Post automatically merged:

Hello! I recently installed an rp2040 picofly from aliexpress on my v2 nintendo switch. When I installed it the connections were good and everything turned out great, I even booted it and it showed the "No sd card" text with the raspberry logo.

I was very happy so I was ready to assemble the switch and finally homebrew the switch, but the thing is that when I turned it on, it went to the nintendo os, not to the picofly os. It does have the firmware installed since it showed the hack the first time.

It gives an ==* error code, I don't know what it can be, I haven't seen much people with the same issue. I can send pictures if you need them.
Post automatically merged:

Fixed! It was just that the mosfets in the cpu flex were in contact with the metalic shield and it shorted and the picofly couldn't boot, it's working now and everything is going fine!
not sure if you will read this but im having the same issue on the switch lite and tried fixing it the same way you did but mine still gives me a blue light followed by an ** error and the github says to check the rst and i have multiple times but no joy. its still goes blue ** then boots to official firmware.
 
not sure if you will read this but im having the same issue on the switch lite and tried fixing it the same way you did but mine still gives me a blue light followed by an ** error and the github says to check the rst and i have multiple times but no joy. its still goes blue ** then boots to official firmware.
Post automatically merged:
Someone with that problem mentioned that some flex cables have the wrong pin-out :
https://gbatemp.net/threads/switch-lite-booting-on-ofw-rst-problem.664584/
 

Site & Scene News

Popular threads in this forum