A few days ago, I successfully installed a HWFLY 4.2 OLED Chip into my Switch OLED. I set everything up, and it worked fine, but because I wanted to play online on my OFW and HOS 16.0.0 got released, I had to update my SysNAND via system settings. In theory, there is no problem doing so (I thought), because the modchip has nothing to do with the HOS version and my emuNAND can stay on 15.0.1 until everything gets updated. After the update, I reset my hwfly chip by shorting the two pins and the chip led turned blue and booted to OFW, as it should.
But after that, the chip was stuck on training forever. Resetting the chip again or changing the firmware version of the chip didn't help. My seller suggested me to install hwfly-nx 0.7.1, instead of the newest 0.7.2, because 0.7.2 is for V1 he said, which doesn't make sense at all in my eyes. Looking for a fix online, I only found people saying that the DAT0 adapter came loose or the soldering was bad, but I didn't believe it was my soldering. All my diode mode readings were fine.

Then i saw this post, and wanted to try it out myself.

Make a 'diagnose log' and post it here for analysis:
- Insert USB cable into switch ('up' faces AWAY from modchip, so you can read it)
- Make sure console is fully powered off (hold power button for 15s)
- Insert other end of USB cable into PC and make note of the COM port that shows up in device manager.
- Use PuTTY to open a connection to this COM port. Make sure to enable "implicit CR in every LF" in the settings.
- Press 'd' (for 'diagnose') and it should tell you to power on the switch first
- Power on switch and press 'd' again.

Paste the output here when it completes.

The "h" command gave me following information:

# Debug menu keys overview

• 'v' Show modchip board info
• 'd' Diagnose single boot
• 's' Boot into SDIO handler
• 'b' Boot OFW
• 't' (Re-)train modchip
• 'c' Show timing configuration table
• 'r' Reset timing configuration table
• 'p' Program eMMC with embedded payload
• 'e' Erase eMMC BOOT0 payload
• 'x' Jump to bootloader
• 'h' Show this help text

First I entered "r" to reset the chip again, followed by "d" which returned: "# Diagnose status: BAD00107 # Please make sure console is powered on"
I powered on the console and was greeted with a lot of debug information in putty. After less than a minute, it found the right timings and hekate was on the screen.
So if your chip doesn't work properly (and the diode mode readings are fine), consider resetting your hwfly using putty before resoldering, to save yourself some headache.

The only problem I have now, is this "Failed to match warm boot with fuses - Sleep Mode won't work" error I get when booting my emuNAND which still is on 15.0.1. If the console's screen is off for more than a few seconds, it never wakes up again.
As far as I understood, I only have to update to 16.0.0 to get it working again.

 

[trepp0]

Ok

 

[jrl_1644]

Is there anyway to do this through Firmware toolbox? I am having the same issue.

 

[binkinator]

Is there anyway to do this through Firmware toolbox? I am having the same issue.

Here are the routines hwfly-toolbox is aware of:

https://github.com/hwfly-nx/hwfly-toolbox/blob/master/toolbox/main.c

launch_payload
hekate_launch
fw_update
fw_dump
sdloader_update
sdloader_dump
train_data_show
train_data_backup
train_data_restore
train_data_reset
session_info
deep_sleep

you might try to reset the training data…

 

[flypico]

A few days ago, I successfully installed a HWFLY 4.2 OLED Chip into my Switch OLED. I set everything up, and it worked fine, but because I wanted to play online on my OFW and HOS 16.0.0 got released, I had to update my SysNAND via system settings. In theory, there is no problem doing so (I thought), because the modchip has nothing to do with the HOS version and my emuNAND can stay on 15.0.1 until everything gets updated. After the update, I reset my hwfly chip by shorting the two pins and the chip led turned blue and booted to OFW, as it should.
But after that, the chip was stuck on training forever. Resetting the chip again or changing the firmware version of the chip didn't help. My seller suggested me to install hwfly-nx 0.7.1, instead of the newest 0.7.2, because 0.7.2 is for V1 he said, which doesn't make sense at all in my eyes. Looking for a fix online, I only found people saying that the DAT0 adapter came loose or the soldering was bad, but I didn't believe it was my soldering. All my diode mode readings were fine.

Then i saw this post, and wanted to try it out myself.


The "h" command gave me following information:

# Debug menu keys overview

• 'v' Show modchip board info
• 'd' Diagnose single boot
• 's' Boot into SDIO handler
• 'b' Boot OFW
• 't' (Re-)train modchip
• 'c' Show timing configuration table
• 'r' Reset timing configuration table
• 'p' Program eMMC with embedded payload
• 'e' Erase eMMC BOOT0 payload
• 'x' Jump to bootloader
• 'h' Show this help text

First I entered "r" to reset the chip again, followed by "d" which returned: "# Diagnose status: BAD00107 # Please make sure console is powered on"
I powered on the console and was greeted with a lot of debug information in putty. After less than a minute, it found the right timings and hekate was on the screen.
So if your chip doesn't work properly (and the diode mode readings are fine), consider resetting your hwfly using putty before resoldering, to save yourself some headache.

The only problem I have now, is this "Failed to match warm boot with fuses - Sleep Mode won't work" error I get when booting my emuNAND which still is on 15.0.1. If the console's screen is off for more than a few seconds, it never wakes up again.
As far as I understood, I only have to update to 16.0.0 to get it working again.

I also updated to 16.0.1 from OFW and since then couldnt glitch succesfully even after reflashing the chip to several versions (R0.32, R031, 0.72, 0.62) so I tested every point with the multimeter but all in range, before resoldering everything I wanted to try putty, but it comes to this errors, any idea what they mean?

 

[ShiroHasake]

I need to reset the chip with R, but when I connect it to pc and select the port in putty, console opens all fine but when I try writing anything putty fatal error pops up with "error writing to serial device" or "error reading from serial device" and the chip starts flashing red.

 

[ceut]

Hello,
Thank you for sharing this great tips !
I give you my Putty output for some more screens (from my Oled), with the CariageReturn after LineFeed enabled in Putty
RS232 power

 

[ffheart]

Somehow this isnt working for me, whenever i click open a tab pops up saying "COM5: ERROR 5: Access is denied."
I have no idea what I'm doing wrong