Open Samybigio opened 1 month ago
update: i did some research and apparently its an issue related to picofly modchips, seems like it could be fixed with a firmware update, and now another error popped up, its =
I have the same problem, either in sysnand or emunand 18.0.1, when I reboot the switch it starts directly in ofw and I can't start in hekate by any means or combination of buttons. Were you able to solve it? It happens to me on the oled switch
I am also having this problem. I have installed many OLEDs and first time this is happening. 1 out of 15 boots it goes into OFW. When it boots to hekate everything works as it should.
I have the same problem, either in sysnand or emunand 18.0.1, when I reboot the switch it starts directly in ofw and I can't start in hekate by any means or combination of buttons. Were you able to solve it? It happens to me on the oled switch
sadly not, i am just living with this error popping up every once in a while
I have the same problem, either in sysnand or emunand 18.0.1, when I reboot the switch it starts directly in ofw and I can't start in hekate by any means or combination of buttons. Were you able to solve it? It happens to me on the oled switch
sadly not, i am just living with this error popping up every once in a while
I solved it by updating the fw to 2.75, I found it on google.
the issue is that sometimes the switch will boot in ofw with the following error code (**=) (this happens with both 2.7.3 and 2.7.5) which is not even listed in the readme, it does mostly boot in hekate. i have an OLED switch and more info is in the video
https://github.com/user-attachments/assets/a1335fcc-97ee-42a7-9d71-00214da8f12f