Toggle sidebar

my switch OLED wont turn on but the leds seems right

  • Thread starter Thread starter Fede12
  • Start date Start date
  • Views Views 965
  • Replies Replies 11
Fede12

Fede12

Well-Known Member
Newcomer
Level 2
Joined
Aug 18, 2024
Messages
80
Reaction score
14
Trophies
0
XP
239
Country
Italy
I really need help with my switch oled, screen is just black and i cant seems to find the problem, the switch still turn on and off (on the last part of the video i turn it off and on again)
 
Sort by date Sort by votes

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
 
Upvote 0 Downvote
Hayato213 said:

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
Click to expand...
so colors dont matter? in some cases led blink 2 long and 2 hsort in some led blink 3 long 1 short
 
Upvote 0 Downvote
Hayato213 said:

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
Click to expand...
Hayato213 said:
There is only three colors in used, blue, white and yellow if you are are on 2.70 and above.
Click to expand...
so its
  • ===* BCT copy failed - comparison failure
    and what does it means?
 
Upvote 0 Downvote
Hayato213 said:
your looks like ==* and =*I though not ===*
Click to expand...
the dat0 should work as it give the right value with the multimeter and i never touched it since installation, for
  • ==* CPU always reach BCT check (no glitch reaction, check mosfet)
    could you explain me what does it mean? thanks : )
 
Upvote 0 Downvote
Fede12 said:
the dat0 should work as it give the right value with the multimeter and i never touched it since installation, for
  • ==* CPU always reach BCT check (no glitch reaction, check mosfet)
    could you explain me what does it mean? thanks : )
Click to expand...

Well in your case if you have a dat0 problem then it won't glitch, based off your video it seem like to be a dat0 problem as you got a =* that point to dat0, ==* telling you it is not glitching.
 
Upvote 0 Downvote
That doesn't look like any of the error patterns, it looks... OK? Blue right after boot, changing brightness a few times while it's attempting to glitch, and then a final blink, once, to confirm success.

It might be glitching and booting fine, but display nothing if there's a problem with the screen or its connector. Does it make any sounds when you tap the screen after the light stops blinking? Does it display anything on a TV if you put the console in the dock?
 
Upvote 0 Downvote
Nephiel said:
That doesn't look like any of the error patterns, it looks... OK? Blue right after boot, changing brightness a few times while it's attempting to glitch, and then a final blink, once, to confirm success.

It might be glitching and booting fine, but display nothing if there's a problem with the screen or its connector. Does it make any sounds when you tap the screen after the light stops blinking? Does it display anything on a TV if you put the console in the dock?
Click to expand...
I agree. The LED sequence looks like it's glitching/booting properly; blue pulses then white to show a successful glitch. If you press both volume buttons together after the white LED (successful glitch), does it boot to OFW? See if you can hear sounds on the main menu assuming it'll boot to OFW. If so, you have a screen problem. I'd double check the OLED ribbon cable anyway to be sure.
 
  • Like
Reactions: Nephiel
Upvote 0 Downvote
Nephiel said:
That doesn't look like any of the error patterns, it looks... OK? Blue right after boot, changing brightness a few times while it's attempting to glitch, and then a final blink, once, to confirm success.

It might be glitching and booting fine, but display nothing if there's a problem with the screen or its connector. Does it make any sounds when you tap the screen after the light stops blinking? Does it display anything on a TV if you put the console in the dock?
Click to expand...
Stidwack said:
I agree. The LED sequence looks like it's glitching/booting properly; blue pulses then white to show a successful glitch. If you press both volume buttons together after the white LED (successful glitch), does it boot to OFW? See if you can hear sounds on the main menu assuming it'll boot to OFW. If so, you have a screen problem. I'd double check the OLED ribbon cable anyway to be sure.
Click to expand...
im sorry for late responde and thanks for the help, i removed the chip and the dat0 connector, the switch when turned on doesnt sound like its on (like main menu etc), it charges and it feels like it turns on and off.
When turning on the Amphere In goes up to ≈0.36A when turned off the Amphere goes to ≈0.16A the only issue i could find on the board is this little scratch in the photo that shouldnt bother connections (ig)

I leave the turn on and off Videos as gdrive links as they exceed in dimension
Tablet mode Video
TV mode Video
WIN_20250202_18_01_03_Pro.jpg

Thanks to anyone willing to help
 
Upvote 0 Downvote

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  Full List of N64 Recompilation Switch ports

Homebrew  New Homebrew "Foil Server"?

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Homebrew Homebrew game Project  So... Dan didn't want to reveal his Vulkan, so I made mine.

Is it fixable