See below for updates.

IF YOU BREAK YOUR BOOT0 PIN. DO NOT DM ME ASKING FOR HELP. THAT'S IT. YOU BREAK THAT PIN AND YOU CANT FLASH. YOUR CHIP IS STUCK WITH WHATEVER HWFLY PUT ON IT


Pre-requisites:

---

• Raspberry Pi Zero W
  • You may use another flasher if you desire.
• Pinout Diagram
• Modchip Diagram
• FULL_CHIP_STOCK.bin
• Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
  • Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
  • Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.

1. Solder a wire to each of the following pinouts on the Raspberry Pi Zero W:
   • 3.3V
   • Ground
   • GPIO 14 (UART TX)
   • GPIO 15 (UART RX)
2. Do the following to prepare the modchip:
   1. Lift pin 44 (also known as BOOT0).
   2. You will need a way to power the chip, so you need to find two 3.3v points. It can be on a MOSFET, but it will differ based on the revision of the modchip.
   3. Connect Ground on your Raspberry Pi Zero W to the Ground pin on your modchip.
   4. Check the Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
      • Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
      • Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.
3. Boot your Raspberry Pi Zero W and do the following:
   1. In the terminal, type the following command, and press enter:
      

      sudo nano /boot/config.txt

   2. Add the following line to the end of the file:
      

      dtoverlay=pi3-miniuart-bt

   3. Press CTRL + X to save and exit the editor.
   4. In the terminal, type the following command, and press enter:
      

      sudo nano /boot/cmdline.txt

   5. Remove the following line from the file:
      

      console=serial0,115200

   6. Press CTRL + X to save and exit the editor.
   7. Restart your Raspberry Pi with this command
      

      sudo /sbin/reboot

   8. In the terminal, type the following commands, and press enter after each command:
      
      

      git clone https://github.com/Pheeeeenom/stm32flash.git
      cd stm32flash
      sudo make install

4. Now you will flash the modchip.
   Note: This will remove read protection, and the modchip will wipe itself (that is what we want).
   1. In the terminal, type the following command, and press enter:
      

      stm32flash -k /dev/serial0

   2. Now to flash Spacecraft-NX Version 0.2.0, type the following, and press enter:
      

      stm32flash -v -w ./FULL_CHIP_STOCK.bin /dev/serial0

5. Once you're done flashing your modchip, remove the wiring from the modchip, and restore the 3.3v pin on the modchip to its original position.

Please post pictures of your work here to further the identification of the different board revisions!


UPDATE: So it seems like stitching the spacecraft bootloader and firmware together from the repo causes unstable glitching behaviors. For now, consistent glitching behavior works with this bootload/firmware combo. This is the original file on the OLED variant chip which has 0.2.0 spacecraft. As for glitching, I'll figure it out, give me some time...unless someone else wants to hop in and reverse the differences.

For now, this at least solves the 0.1.0 HWFLY gen 3 issue. More to come.

UPDATE 2: This is only going to work on some HWFLY chips. Older ones use higher protection than the new revisions that seem to use the QFN FPGA.

UPDATE 3: This should fully work on OLED modchips with the QFN FPGA. https://github.com/Pheeeeenom/firmware

 

[FR0ZN]

Will Mena keep on developing his version?
Or is 0.5.0 now the one that keeps updating, making 0.4.0 "obsolete" ?

 

[algolsaturn]

Hi there, I ended up ordering this particular HWFLY OLED modchip, in retrospect it was probably a mistake as it doesn't seem to have as much documentation as the other OLED modchip revision that I am sure a lot of you would have seen. I've got a few questions:

1. does this chip have the 0.2 spacecraft-nx firmware that resolves the issue with it sending incorrect voltages?

2. Would I be able to verify the firmware version via dumping boot0? I have purchased an st-link programmer, what would be the best way to hook it up to this chip.

3. is it possible to flash this with Mena custom firmware.

I've heard that this chip is particularly "bad", in terms of quality, although I ordered a separate dat0 emmc adaptor as there have been stories where people have used that particular OLED dat0 adaptor and its caused issues with the emmc, possibly its broken off and shorted something. I would very much appreciate an answer to this as I am new to this. Thanks.

 

[doom95]

1) yes, although the issue might not even be an issue at all
2) yes. dump boot0 through hekate. no stlink involved.
3) probably not, at least not right now. more research needed.

 

[suchy101]

is the V3 OLED HWFLY with a corner EMMC adapter used in Sthetix video (INSTALLING - UPDATING - RESETTING THE CHIP : UPDATED VERSION)

the best one to get these days ?

 

[doom95]

no the worst

 

[suchy101]

thank you .

May I please ask which one would you actually recommend ?

 

[doom95]

my signature could give a hint. i might also not be unbiased

 

[suchy101]

Sorry, I meant the whole HWFLY, not the adapter.

Still reading through everything so apologies if this was already discussed. But since I am bumping into reports of issues with older chips, requiring to update the firmware (5V issue) I was just wondering if there is "the kit" to get ?

The one used in that video has usb port for flashing. It also goes through flashing to V2. If I will get this kit, should I start with flashing before install pre-emptively ?

 

[lufeig]

Hi there, I ended up ordering this particular HWFLY OLED modchip, in retrospect it was probably a mistake as it doesn't seem to have as much documentation as the other OLED modchip revision that I am sure a lot of you would have seen. I've got a few questions:

1. does this chip have the 0.2 spacecraft-nx firmware that resolves the issue with it sending incorrect voltages?

2. Would I be able to verify the firmware version via dumping boot0? I have purchased an st-link programmer, what would be the best way to hook it up to this chip.

3. is it possible to flash this with Mena custom firmware.

I've heard that this chip is particularly "bad", in terms of quality, although I ordered a separate dat0 emmc adaptor as there have been stories where people have used that particular OLED dat0 adaptor and its caused issues with the emmc, possibly its broken off and shorted something. I would very much appreciate an answer to this as I am new to this. Thanks.

View attachment 298243

Apparently this modchip model has better glitching times than the other model with usb debug port. The ones I’ve seen glitch almost instantly.

So I wouldn’t be worried about updating its firmware, at least by now. It works great doing its primary purpose: hacking the Switch.

 

[lufeig]

Sorry, I meant the whole HWFLY, not the adapter.

Still reading through everything so apologies if this was already discussed. But since I am bumping into reports of issues with older chips, requiring to update the firmware (5V issue) I was just wondering if there is "the kit" to get ?

The one used in that video has usb port for flashing. It also goes through flashing to V2. If I will get this kit, should I start with flashing before install pre-emptively ?

IMHO people not experienced with all this stuff - me included - should have the modchip installed first, then updated if needed.

Because if things go wrong, it will be harder to know if it happened during the flashing, the installing, or the chip was DOA.

Just my 0.02

 

[Vladjaye]

IMHO people not experienced with all this stuff - me included - should have the modchip installed first, then updated if needed.

Because if things go wrong, it will be harder to know if it happened during the flashing, the installing, or the chip was DOA.

Just my 0.02

I think that chip should be updated first, if possible, to get the best SD card compatibility and working NO SD on Micron memory consoles. If the chip comes with the USB interface - it comes with updating functionality in mind. If it fails on first flash - well, chip is most likely defective.

 

[Mena]

Will Mena keep on developing his version?
Or is 0.5.0 now the one that keeps updating, making 0.4.0 "obsolete" ?

it is "obsolete". it seems like whoever is behind 0.5.0 and that github took the fw on my github and added to it, it's fully open source too.

 

[suchy101]

well, I went ahead and ordered the set called V3, with usb header for easy updates. Hope this was not a wrong choice to make.

About a year or so ago I bought second hand Lite and the TX SX Lite and did that myself, without microscope. It was hell, especially with my poor eyesight.

Learned the lesson, and this time shelled out for a microscope.

In the meantime I will read through all the tutorials available to get myself up to speed how to install and use Atmosphere, Hekate and such, as the SX did not need any of that.

I would like to use this opportunity to humbly express my sincere thanks to the unbelievably smart, talented and skilled individuals keeping this scene alive by putting in the work for the benefit of us regular folk.

I bow in awe and respect.

Thank You.

 

[xdMatthewbx]

Has anyone tried flashing 0.5.0 from 0.4.0 using toolbox? I'd prefer not to open my OLED again...

 

[lufeig]

Has anyone tried flashing 0.5.0 from 0.4.0 using toolbox? I'd prefer not to open my OLED again...

 

[xdMatthewbx]

Not sure if that means you'd also like to know or if you tried this.

 

[lufeig]

Not sure if that means you'd also like to know or if you tried this.

I updated from 0.4.0 to 0.5.0 using toolbox.

I just followed the instructions given on this post:

https://gbatemp.net/threads/tutorial-how-to-flash-the-hwfly-clone-chips.606008/post-9749756

 

[xdMatthewbx]

I updated from 0.4.0 to 0.5.0 using toolbox.

I just followed the instructions given on this post:

https://gbatemp.net/threads/tutorial-how-to-flash-the-hwfly-clone-chips.606008/post-9749756

Having difficulty getting it to boot with VOL+ held, did you have this issue?

EDIT: ignore me, I need a recurring reminder every 5 minutes that just says "RTFM"

 

[lufeig]

Let me guess, Autoboot was set to on in Hekate?

 

[xdMatthewbx]

Let me guess, Autoboot was set to on in Hekate?

No you just don't hold VOL+ before flashing SD loader