https://github.com/Pheeeeenom/payloadchecker/releases/tag/1.0 Made this really simple app to check the payload that's written to your boot0. This will tell you if the chip that's currently installed is a hwfly with spacecraft v1 or v2 payload. Simply open it press the button and select your boot0
If you're testing multiple chips be sure to connect the USB cable and press E on PuTTy or other equivalent Serial COM application.
You need it for every boot.You say "written to your boot0", does this mean that the DAT0 connection is actually used only once to write the modified boot0 to the eMMC? Or is a DAT0 connection necessary for every boot?
I always thought that the chip injects a modified BCT at boot over DAT0 and then again I always wondered why it's not written permanently to the eMMC.
Can you explain what the hack actually does?You need it for every boot.
They write a custom bct and bootloader to boot0 then glitch the bootrom's pubkey hash check to make the bootrom think a custom pubkey in the custom bct is correct/valid.Can you explain what the hack actually does?
My understanding was that it glitches the signature check of BCT.
But it seems that there is more involved, if boot0 is altered as well
I’m interested in trying this out. Once I connect the USB cable do I have to power the chip somehow? Or does the USB port power the chip? Also, do I need an application for the computer to recognize the chip or driver or is your app enough?https://github.com/Pheeeeenom/payloadchecker/releases/tag/1.0 Made this really simple app to check the payload that's written to your boot0. This will tell you if the chip that's currently installed is a hwfly with spacecraft v1 or v2 payload. Simply open it press the button and select your boot0
If you're testing multiple chips be sure to connect the USB cable and press E on PuTTy or other equivalent Serial COM application.
your fan doesn't work and your joycons don't charge? they likely don't detect either. i would do voltage injection on the fan circuit.Hello there, maybe someone will help in this topic. After installing modchip SX Lite in switch oled, the fan stopped spinning, joycons do not charge. Switch works fine. Joycons are detected and work without bluetooth. On switch V1-V2, pu chip was responsible for charging the joycons and the fan, but I can't find it on switch oled.
your fan doesn't work and your joycons don't charge? they likely don't detect either. i would do voltage injection on the fan circuit.
Joycons are detected and work as usual, but are not charged. The power supply is 0v in the fan circuit, but there is no short circuit to the groundyour fan doesn't work and your joycons don't charge? they likely don't detect either. i would do voltage injection on the fan circuit.
Unfortunately, I don't have such equipment...Can you inject 5v from a bench supply into the circuit, see how much it sinks?
Don't the chips sniff DAT0 to synchronize the timing since Mariko has the random delays?They write a custom bct and bootloader to boot0 then glitch the bootrom's pubkey hash check to make the bootrom think a custom pubkey in the custom bct is correct/valid.
I'd guess they flash it on each boot because the OS attempts to restore stuff at some points, or maybe they reflash the original package1 for compatibility on each boot after glitching, idk.
Dunno shrugsDon't the chips sniff DAT0 to synchronize the timing since Mariko has the random delays?
yes, if anyone has an explanation to this , i also want to know. some tap off from the 2 caps for 3.3v, some tap off from the cap near EMMC for 3.3v , whats the difference?I ordered an oled specific chip, I'm hearing that we shouldn't use the 3.3v off of bridging the 2 capacitors. Why is this? And if it's true what point should we use?
Who said this?yes, if anyone has an explanation to this , i also want to know. some tap off from the 2 caps for 3.3v, some tap off from the cap near EMMC for 3.3v , whats the difference?