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.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.
Yes, that is correct, but I never did anything in the switch, just got the NO SD screen and then it wouldn't work.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.
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.By modchip disconnected, do you mean everything unsoldered? or just the power not running to it?
.