I'm experiencing a very strange problem, PicoFly stopped working after using RetroArch.
I have a OLED model ( latest FW 17.0.1 ) + HATS 1.6.2, with PicoFly ( also latest firmware installed v2.75)
Usually all functions grate, after second or third blue blink i got the glitch and Heckate opened. In very rear situation the glitch happened after the first blue blink.
Fore safety reasons I'm using emummc. From there i launched and used RetroArch, playing god of war with ppsspp core.
After i stopped playing i powered off the switch, normally as anyone would doo, holding the power button and clicking on power off. Shortly, maybe two - three minutes after powering off i wanted to power on again ( I'm a tester, searching for bugs and reporting problems ) the nintpppendo logo appeared and the console booted direct to OFW. Repeating Power Off/On five times. The same happened, the console booted direct to OFW.
What was PicoFly doing at the time?
It indicated a Yellow light Error: =** eMMC init failure during glitch process ( all six times the same )
A solution to this problem is to Restore Factory Settings trough OFW.
After the console finished restoring with powering off, i pressed the power button, hoping that PicoFly will wake up and do its thing.
Guess what? It worked better then ever before. After the fist blue blink i got in to Heckate. Repeated Power off/on several times, suddenly all was back to normal. I was in Heckate after every first blue blink.
Now, I'm back on CFW over emummc.
I launched RetroArch and i was just clicking around, updating cores and other stuff. , powered off the console. power on, and the console booted again directly to OFW. Repeated On/Off ten times, every time i got to OFW.
This time PicoFly showed another Error code.
==*= BCT copy failed - write failure
So i just did the same as the first time ( Restore Factory Settings )
After Restore finished, PicoFly functioned normally on every on/off.
Hi.
I'm experiencing a very strange problem, PicoFly stopped working after using RetroArch. I have a OLED model ( latest FW 17.0.1 ) + HATS 1.6.2, with PicoFly ( also latest firmware installed v2.75) Usually all functions grate, after second or third blue blink i got the glitch and Heckate opened. In very rear situation the glitch happened after the first blue blink.
Fore safety reasons I'm using emummc. From there i launched and used RetroArch, playing god of war with ppsspp core. After i stopped playing i powered off the switch, normally as anyone would doo, holding the power button and clicking on power off. Shortly, maybe two - three minutes after powering off i wanted to power on again ( I'm a tester, searching for bugs and reporting problems ) the nintpppendo logo appeared and the console booted direct to OFW. Repeating Power Off/On five times. The same happened, the console booted direct to OFW.
What was PicoFly doing at the time? It indicated a Yellow light Error: =** eMMC init failure during glitch process ( all six times the same )
A solution to this problem is to Restore Factory Settings trough OFW. After the console finished restoring with powering off, i pressed the power button, hoping that PicoFly will wake up and do its thing. Guess what? It worked better then ever before. After the fist blue blink i got in to Heckate. Repeated Power off/on several times, suddenly all was back to normal. I was in Heckate after every first blue blink.
Now, I'm back on CFW over emummc. I launched RetroArch and i was just clicking around, updating cores and other stuff. , powered off the console. power on, and the console booted again directly to OFW. Repeated On/Off ten times, every time i got to OFW.
This time PicoFly showed another Error code. ==*= BCT copy failed - write failure
So i just did the same as the first time ( Restore Factory Settings ) After Restore finished, PicoFly functioned normally on every on/off.
Is someone else experiencing such weird stuff?