Hacking Hardware OLED Picofly : Suddently allways booting OFW, specific led error code

Glendor · Wednesday at 5:57 PM

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 :

sudeki300 · Wednesday at 6:23 PM

i would say that is long + short, meaning your D0 is no longer connected.

though i may be wrong

Glendor · Wednesday at 6:28 PM

sudeki300 said:
i would say that is long + short, meaning your D0 is no longer connected.

though i may be wrong

I thought the same, but you can see that this sequence is twice repeated, after the first =* sequence, is a second one, is that normal ?

sudeki300 · Wednesday at 6:35 PM

Glendor said:
I thought the same, but you can see that this sequence is twice repeated, after the first =* sequence, is a second one, is that normal ?

dont know how i missed the second sequence, i agree it's long + short twice. did you install the chip or someone else, maybe post in the picofly thread for better help.

s4n0suk3 · Wednesday at 8:49 PM

Happens to me and is d0 cable or Flex most of times is Flex, just check with multímeter value of Dat0 point in chip

Jazmeens · Thursday at 8:46 PM

sudeki300 said:
i would say that is long + short, meaning your D0 is no longer connected.

though i may be wrong

What does DO means I soldered my chip to day and it boots up to OFW

Post automatically merged: Thursday at 8:48 PM

sudeki300 said:
i would say that is long + short, meaning your D0 is no longer connected.

though i may be wrong

Hello I’m new to this hacking stuff, can you pls tell me what DO is I soldered my Picofly chip and it boots up to OFW, any help will be appreciated

jkyoho · 2024-07-05T14:31:51+0100

Jazmeens said:
What does DO means I soldered my chip to day and it boots up to OFW

Post automatically merged: Thursday at 8:48 PM

Hello I’m new to this hacking stuff, can you pls tell me what DO is I soldered my Picofly chip and it boots up to OFW, any help will be appreciated

D0/DO is referred to the DAT0/C point on the emmc due to the cheap adapter label printing.

Hacking Hardware OLED Picofly : Suddently allways booting OFW, specific led error code

Member

Well-Known Member

Member

Well-Known Member

Member

New Member

Well-Known Member

Similar threads

Popular threads in this forum