Switch Picofly First Install Weird Issue (LP0 missing)

[Vinc3iZ]

Hello, i have a weird issue with my switch, this weekend i intalled the Picofly on a V2 Switch, i was very careful, as i know it's more thin than on every consoles i have ever worked with. This is my first Picofly install and i struggled a bit to find informations about it.

I soldered the pcb flex, maybe a connection is bad ? But here's what happened you'll understand my problem
- Soldered Picofly,
- Checked my pins multiples times (i suspect that signal might be bad maybe on one pad ?)
- First time i set up the SD Card with an HATCS Pack formatted to FAT32
- Hekate was booting for the first time, I went directly to Tools and tried to Backup BOOT0 and BOOT1 partition, it went successful,
- Then i tried to do a RAW Nand Dump, (i didn't installed anything yet but i want backups before doing anything on the switch)

Then it went stuck at 0%, i waited, and green lines started to appear on the screen. It can be overheated CPU was about 22 degrees.

And now everytime i boot to the SDCard with Hekate Files (update.bin bootloader folder and so on) i get this message shown on the image with green lines... (is this APU issue ?)

Is this hardware issue ? Or maybe by trying to read my nand it corrupted the nand and i need to rebuild a new one to be able to launch Hekate ? Thank you very much for your help i'm really stuck here and i don't want to throw that switch to the thrash... And found only only one post on this forum with someone getting almost a similar problem

Trying to boot original firmware is not working i get blue screen but i guess it's because Picofly modifies BOOT0 of original eMMC to redirect to the Payload Loader (correct me if i'm wrong).

Thank you everyone for your help

 

[gabclow00]

Hello, i have a weird issue with my switch, this weekend i intalled the Picofly on a V2 Switch, i was very careful, as i know it's more thin than on every consoles i have ever worked with. This is my first Picofly install and i struggled a bit to find informations about it.

I soldered the pcb flex, maybe a connection is bad ? But here's what happened you'll understand my problem
- Soldered Picofly,
- Checked my pins multiples times (i suspect that signal might be bad maybe on one pad ?)
- First time i set up the SD Card with an HATCS Pack formatted to FAT32
- Hekate was booting for the first time, I went directly to Tools and tried to Backup BOOT0 and BOOT1 partition, it went successful,
- Then i tried to do a RAW Nand Dump, (i didn't installed anything yet but i want backups before doing anything on the switch)

Then it went stuck at 0%, i waited, and green lines started to appear on the screen. It can be overheated CPU was about 22 degrees.

And now everytime i boot to the SDCard with Hekate Files (update.bin bootloader folder and so on) i get this message shown on the image with green lines... (is this APU issue ?)

Is this hardware issue ? Or maybe by trying to read my nand it corrupted the nand and i need to rebuild a new one to be able to launch Hekate ? Thank you very much for your help i'm really stuck here and i don't want to throw that switch to the thrash... And found only only one post on this forum with someone getting almost a similar problem

Trying to boot original firmware is not working i get blue screen but i guess it's because Picofly modifies BOOT0 of original eMMC to redirect to the Payload Loader (correct me if i'm wrong).

Thank you everyone for your help

I have the same issue did you solve it?

 

[Arledi]

I had this issue a few days ago. Switch the sd card. I have no idea why switching it worked

 

[modDVance]

Can you show photos of your connection? Your soldering might be bridged somewhere

Post automatically merged: May 19, 2025

Although, depending on where you bought your picofly from, the ribbon cable might be damanged. I did notice that the AliExpress packaging is not good when they put it in the anti static bags.

Post automatically merged: May 19, 2025

I had this issue a few days ago. Switch the sd card. I have no idea why switching it worked

Yeah this is also true. Apparently using sd cards that might be flashed to display higher storage or are non name brand is a cause.