*=* Error On Switch OLED! (Can't find much info about it)

  • Thread starter Thread starter Joeorisit
  • Start date Start date
  • Views Views 1,874
  • Replies Replies 27
you don't have to reball the emmc. That is unnesssary, I mean you should really check your dat0 work, see if it connected correct, the error code mean it is not connected correctly, can always do kamikaze if you want permanent dat0.
 
you don't have to reball the emmc. That is unnesssary, I mean you should really check your dat0 work, see if it connected correct, the error code mean it is not connected correctly, can always do kamikaze if you want permanent dat0.
Ok. I will keep trying that. The only reason I am thinking that is because it won't even boot normally.
 
To recap: the console is an OLED, modded with Picofly, that one day stopped glitching, with error code *=* (eMMC read failure). Disconnecting DAT0 the error became =* (makes sense). But the console still doesn't boot, not even OFW. Did I get that right?

Does the console boot to OFW with both DAT0 and the modchip disconnected, and no microSD?

If it doesn't boot, did you recently update OFW with Daybreak, or downgrade it by restoring from a backup? (if you didn't, then we can rule out any potential issues with eFuses).

Otherwise, it might have a short somewhere, I'd remove the DAT0 adapter, clean flux residue, check for any debris and try to boot OFW.

If it still can't boot OFW normally, the eMMC may have gotten corrupted.
 
  • Like
Reactions: Joeorisit
To recap: the console is an OLED, modded with Picofly, that one day stopped glitching, with error code *=* (eMMC read failure). Disconnecting DAT0 the error became =* (makes sense). But the console still doesn't boot, not even OFW. Did I get that right?

Does the console boot to OFW with both DAT0 and the modchip disconnected, and no microSD?

If it doesn't boot, did you recently update OFW with Daybreak, or downgrade it by restoring from a backup? (if you didn't, then we can rule out any potential issues with eFuses).

Otherwise, it might have a short somewhere, I'd remove the DAT0 adapter, clean flux residue, check for any debris and try to boot OFW.

If it still can't boot OFW normally, the eMMC may have gotten corrupted.
Yes, that is correct, but I never did anything in the switch, just got the NO SD screen and then it wouldn't work.

By modchip disconnected, do you mean everything unsoldered? or just the power not running to it?

I will try and clean it up better. The CMD 4.7k resistor was reading .567 in diode mode, and was difficult to solder to with the flex cable (hence why I used the copper wire). I am starting to think that it somehow has stopped working because I can't get it to boot to OFW. But I won't know unless I remove the solder mask. Also I'm pretty sure that you get a purple screen if that resistor is burnt.

Thanks for this detailed answer it is really helpful
 
By modchip disconnected, do you mean everything unsoldered? or just the power not running to it?
I meant disconnecting the flex from the modchip board, but yeah, at this point I'd focus on getting it to boot OFW, even disconnecting all the lines from the modchip.
Just to make sure the console still works unmodded and its eMMC is OK.

Good luck!
 
  • Like
Reactions: Joeorisit
If it never worked, it could be a simple mixup of dat/cmd/clk cables. If it however did boot at some point, it must be something else.
I've gotten this error a few times when the reball didn't connect all dat points properly. My best guess is that there is flux or residue from the dat0 adapter shorting between multiple dat points. can be hard to clean since you can't really reach underneath the emmc - isopropyl alcohol in a spray can would work, or reballing the emmc.
 
So sadly after cleaning the board and emmc really well, while testing the console, I bent a pin in the display FPC connector :cry:.
So gonna have to put a pause on it until the new connector gets here.

Thanks for the help though guys! I'll keep everybody updated :rofl:
 
Hey Joeorisit,

just modded my Switch Oled with kamikaze and got that same error *=* like you.
Can't boot in OFW either.

You got your problem fixed?
 

Site & Scene News

Popular threads in this forum