Hacking Switch doesn't boot anymore. Picofly pulsating blue light.

[Subtle Demise]

I have a "v2" Switch that was modded with a Picofly Core. It has worked fine for months and months up until recently. Last week I played it on a road trip for a while and when I got home it was getting a low battery so I set it into the dock. I went to play it last night and it wouldn't turn on nor even show the charging indicator when plugged in. "Oops, I must not have seated in the dock all the way and the battery discharged," I thought to myself.

I charge it overnight and it still won't boot up or charge. I open it up, unplug the battery and re-seat it and do the same with the SD card reader. I turn it on to test it before putting the back plate back on and I noticed that the Picofly is just solid blue and slowly pulsating but the Switch is doing nothing (while writing this it did change to a yellowish whitish sort of color for maybe one or two seconds and then went back to the pulsating blue). If I take out the SD card it will turn green and then show the "No SD Card" warning with the Raspberry Pi logo. It also feels pretty warm to the touch on the back side. What could the issue be? I attached a video of the light if it helps any.

 

[Deleted member 301661]

​

I have a "v2" Switch that was modded with a Picofly Core. It has worked fine for months and months up until recently. Last week I played it on a road trip for a while and when I got home it was getting a low battery so I set it into the dock. I went to play it last night and it wouldn't turn on nor even show the charging indicator when plugged in. "Oops, I must not have seated in the dock all the way and the battery discharged," I thought to myself.

I charge it overnight and it still won't boot up or charge. I open it up, unplug the battery and re-seat it and do the same with the SD card reader. I turn it on to test it before putting the back plate back on and I noticed that the Picofly is just solid blue and slowly pulsating but the Switch is doing nothing (while writing this it did change to a yellowish whitish sort of color for maybe one or two seconds and then went back to the pulsating blue). If I take out the SD card it will turn green and then show the "No SD Card" warning with the Raspberry Pi logo. It also feels pretty warm to the touch on the back side. What could the issue be? I attached a video of the light if it helps any.

View attachment 458915

Error codes list (= is long pulse, * is short pulse):​

• = USB flashing done
• ** RST is not connected
• *= CMD is not connected
• =* D0 is not connected
• == CLK is not connected
• =** eMMC init failure during glitch process
• =*= CPU never reach BCT check, should not happen
• ==* CPU always reach BCT check (no glitch reaction, check mosfet)
• === Glitch attempt limit reached, cannot glitch
• =*** eMMC init failure
• =**= eMMC write failure - comparison failed
• == eMMC write failure - write failed
• =*== eMMC test failure - read failed
• ==** eMMC read failed during firmware update
• ==*= BCT copy failed - write failure
• ===* BCT copy failed - comparison failure
• ==== BCT copy failed - read failure

 

[Subtle Demise]

​

Error codes list (= is long pulse, * is short pulse):​

• = USB flashing done
• ** RST is not connected
• *= CMD is not connected
• =* D0 is not connected
• == CLK is not connected
• =** eMMC init failure during glitch process
• =*= CPU never reach BCT check, should not happen
• ==* CPU always reach BCT check (no glitch reaction, check mosfet)
• === Glitch attempt limit reached, cannot glitch
• =*** eMMC init failure
• =**= eMMC write failure - comparison failed
• == eMMC write failure - write failed
• =*== eMMC test failure - read failed
• ==** eMMC read failed during firmware update
• ==*= BCT copy failed - write failure
• ===* BCT copy failed - comparison failure
• ==== BCT copy failed - read failure

So it's either Glitch Attempt Reached or BCT copy failed. I'm not sure how to tell the difference between the three or four pulses. How would I go about troubleshooting those? If it involves soldering or anything similar I won't be able to do it with my current tools, knowledge, or skills. Also, the white light came on again for a few seconds and then disappeared. What would that mean?

 

[Deleted member 301661]

So it's either Glitch Attempt Reached or BCT copy failed. I'm not sure how to tell the difference between the three or four pulses. How would I go about troubleshooting those? If it involves soldering or anything similar I won't be able to do it with my current tools, knowledge, or skills. Also, the white light came on again for a few seconds and then disappeared. What would that mean?

Oohh did you check: https://gbatemp.net/threads/picofly-aio-thread.628951/ my info seems outdated

 

[Subtle Demise]

Oohh did you check: https://gbatemp.net/threads/picofly-aio-thread.628951/ my info seems outdated

So I can bypass the chip and OFW boots just fine (although it became unresponsive as soon as I put my SD card back in), plus the NO SD CARD error pops up when I don't have it in there. Is it just a corrupted SD card? Would that cause it? Which file would be corrupted?

EDIT: Oh yeah it's definitely the SD card. It doesn't even show up on Windows when I plug it in to my PC. It works with a different reader, so now I'm backing it up overnight and will try loading fresh payload files and stuff back on in the morning and see if it works again.