Hi guys,
Basically, i got my Switch OLED Modded with PicoFly barely 9 months ago. Everything worked fine , i was running a clean eMMC on 17.0 OFW and a separated emuNAND with Athmosphere CFW.
Some time before, i just left my Switch on its Dock Station, and now, maybe 3-4 months after, i decided to play again and when i toke the console, it was still booted on with CFW loaded. I downloaded some XCI and when i went to the DBI Installer app to install them, entered on MTP Transponder i realized that nothing happens , so i decided to restart the console because of this.
Just when i restarted i realized that for some reason, the console now directly boots into OFW, HEKATE its not being booted as before letting me decide if i want to boot in my eMMC OFW or emuNand CFW.
I have no idea what could happened here, i can provide a video showing the PicoFly led codes, maybe this helps, but i don´t know if it has to do something with the internal wiring, means some hardware related problem, or it has more to do with some update, missing file etc...
Looking on PicoFly documentation, it says that the (long+short) =* means D0 not connected, and also that (long+short+long+short) =*=* means no emmC init, but i dont know witch one is mine, because im actually running on eMMC.
Here is the led code video :
Basically, i got my Switch OLED Modded with PicoFly barely 9 months ago. Everything worked fine , i was running a clean eMMC on 17.0 OFW and a separated emuNAND with Athmosphere CFW.
Some time before, i just left my Switch on its Dock Station, and now, maybe 3-4 months after, i decided to play again and when i toke the console, it was still booted on with CFW loaded. I downloaded some XCI and when i went to the DBI Installer app to install them, entered on MTP Transponder i realized that nothing happens , so i decided to restart the console because of this.
Just when i restarted i realized that for some reason, the console now directly boots into OFW, HEKATE its not being booted as before letting me decide if i want to boot in my eMMC OFW or emuNand CFW.
I have no idea what could happened here, i can provide a video showing the PicoFly led codes, maybe this helps, but i don´t know if it has to do something with the internal wiring, means some hardware related problem, or it has more to do with some update, missing file etc...
Looking on PicoFly documentation, it says that the (long+short) =* means D0 not connected, and also that (long+short+long+short) =*=* means no emmC init, but i dont know witch one is mine, because im actually running on eMMC.
Here is the led code video :
Last edited by Glendor,