Hacking Hardware Switch oled purple screen with chip and booting fine to ofw without it

[achillebrac07]

Hello, i have an oled with a strange behavior, it was previously attempted to mod by an unexperienced diyer, i repaired what he broke and tried to mod it, did the kamikaze and everything but the console glitches fine and goes to hekate but when the chip is soldered it shows no emmc and purple screen if booting ofw or bypassing the chip, when the chip is unsoldered it boots fine, now the strangest thing is that with an instinct nx chip it works fine and i can see the partition table of the emmc. So does anybody else experienced the same or a similar behavior?

 

[thesjaakspoiler]

A purple screen is the Switch having a kernel panic because it cannot read the boot loader (either BOOT0 or BOOT1).
The picofly injects custom boot0 data and does not use the boot0 from the emmc.
After booting into hekate, it will use boot1 data from the original emmc and do some patching there.
After that it will completely ignore the emmc and use the emummc.
So my uneducated guess is that the picofly somehow doesn't interact well with your emmc and causes a kernal panic.

If the instinct nx works and the picofly not, check what emmc you have,
I recall some OLEDs have some exotic emmc brand (Hynix/Samsung?) and the resistor values for the Picofly need to be adjusted for it.
There was a discussion about this in the Picofly sticky thread a long long time ago.
The instinct is less picky about different brands of emmcs and that is why some modders only will fit instincts in OLEDs.

 

[achillebrac07]

A purple screen is the Switch having a kernel panic because it cannot read the boot loader (either BOOT0 or BOOT1).
The picofly injects custom boot0 data and does not use the boot0 from the emmc.
After booting into hekate, it will use boot1 data from the original emmc and do some patching there.
After that it will completely ignore the emmc and use the emummc.
So my uneducated guess is that the picofly somehow doesn't interact well with your emmc and causes a kernal panic.

If the instinct nx works and the picofly not, check what emmc you have,
I recall some OLEDs have some exotic emmc brand (Hynix/Samsung?) and the resistor values for the Picofly need to be adjusted for it.
There was a discussion about this in the Picofly sticky thread a long long time ago.
The instinct is less picky about different brands of emmcs and that is why some modders only will fit instincts in OLEDs.

Hello, and thanks for the reply, my emmc is sk Hynix, i even tried triple resistors on the data lines but nothing happened

 

[SaudiCraft]

If your instinct modchip works I would leave it at that.
High Frequency lines require the correct impedance in order to function properly otherwise you get unwanted noise that could potentially corrupt data and prevent boot.

Check what the instinct uses and match it with the pico.