Switch V2 picofly blue screen OFW still boots without modchip

[Photek22]

Hi all.

I would like some assistance please. I have a Nintendo Switch v2 and I've recently installed a picofly mod chip which I bought from eBay.

I'm pretty good with a soldering iron and I have a microscope to inspect the installation (part electronics hobbyist).

However, I can boot into the Henake payload and I've backed up my NAND but when I try and boot into the OFW or the CFW, I get a blue screen. I have all of the required CFW files as per the official guide.

I haven't damaged my switch either as I can boot into the OFW if I remove the modchip and install the NAND chip directly back onto the switch's motherboard.

I found a post here which highlighted the resistors for the CLK, Data, and Command had to be specific values which I can confirm I had to modify the picofly to ensure the values were correct.

Still, before and after modifying the picofly's resistor values, I still have a blue screen.

I did run into a situation where after I installed the picofly for the first time, the screen started to glitch and display pink pixels. I reflowed the joints and this hasn't happened since.

Scratching my head into thinking what the problem could be? I've tried two different firmwares too.

I did notice however, one of the resistors/capacitors next to the oscillator on the picofly wasn't mounted correctly. Tombstone it's called, where only one of the pins are attached. Still, after fixing that, I still get a blue screen when trying to boot into either an OFW or CFW.

I've ordered another mod chip too as I might have a faulty board.

Is there something specific to the V2 switch which I should know about when installing one of these picoflys?

Thanks all

 

[Photek22]

I've attached a screenshot of the modchip I bought

 

[thesjaakspoiler]

Blue screens are usually related to the ram modules.
Hekate uses a little bit so that is why it might not be running into any problems.
Unfortunately I don't know any DRAM check you can run from RCM or Hekate.

The picofly does need a healthy BOOT0 and BOOT1 partition.
In Hekate you can check if those are fine :

 

[Photek22]

Blue screens are usually related to the ram modules.
Hekate uses a little bit so that is why it might not be running into any problems.
Unfortunately I don't know any DRAM check you can run from RCM or Hekate.

The picofly does need a healthy BOOT0 and BOOT1 partition.
In Hekate you can check if those are fine :
View attachment 540792

Thanks for the reply. I'll upload a picture of that later.

If my RAM modules could be faulty, how come I'm able to still boot into the OFW if I directly connect the NAND flash back to the main board?

Post automatically merged: Nov 22, 2025

Please see the results of me benchmarking my NAND. All of my partitions seem fine.

Post automatically merged: Nov 22, 2025

If also modified a few of the resistor values to see if this is problem too. Currently the values are:

47R Reset
47R Clk
100R Cmd
100R Data

 

[Photek22]

I've just gone ahead and installed the chip provided by the guide listed in GBATemp. I can book in henake but I still have the exact same issue as the picofly chip.

This is really confusing.

 

[fabthegreat]

Hi, any follow up on this?