Review Sthetix fusecheck: how did this tool get released?

[SaudiCraft]

Im not saying the chip is faulty, I'm saying the chip is causing this issue. The fact is right there from your example. The nx-instinct doesn't have this issue, v1 unpatched and the v1 patched (the units that are able to achieve cfw with ofw 4.1) don't have this issue either. It seems more like an issue with the rp2040 chip itself or the firmware they use.
Also daybreak uses the same method to update as if you were to go settings and update that way.

I would like to point out the distinction here, when INSTINCT-NX is used to update, the efuse triggers at the end of the update process when the system shuts down. What are the odds that a mismatched efuse count would hang OFW the same way when switched to an INSTINCT-NX? There, I gave you an assignment.

 

[kidkat210]

Again that's a chip issues specially since the efuse check isn't done untill boot. Not at the end of shut down when updating. The more you talk bout, the more it sounds like an issue with the rp2040 glitching ON BOOT rather than an issue with efuses. Sadly I don't have the chips or switches to fully test myself or else I would

 

[MrMrMr]

Any help please, on issue with trying to boot OFW and just get black screen.

I have an OLED, bought chipped and use emuMMC. It's on v19.0.1 at moment and was going to have a go to get to latest.

I've watched the video and not being the best at this, still don't know what to do! It says on Hekate has 20 burnt fuses. If I go to semi stock, it shows firmware at 21.0.0 I think

I don't really use OFW, but would like to get it working ideally.

 

[superfiege]

Amy help please, on issue with trying to boot OFW and just get black screen.

I have an OLED, bought chipped and use emuMMC. It's on v19.0.1 at moment and was going to have a go to get to latest.

I've watched the video and not being the best at this, still don't know what to do! It says on Hekate has 20 burnt fuses. If I go to semi stock, it shows firmware at 21.0.0 I think

I don't really use OFW, but would like to get it working ideally.

Hi there
Did you update FW using Daybreak and having a Picofly installed?
If yes, open your console, disconnect Picofly and boot your switch. then shutdown and reinstall Picofly. This shoud correct your fuse-count.
More information and detailed description can be found here: https://sthetix.info/the-truth-about-fuses-why-your-ofw-wont-boot-picofly-rp2040/

Have a nice day and good luck!

 

[MrMrMr]

Hi there
Did you update FW using Daybreak and having a Picofly installed?
If yes, open your console, disconnect Picofly and boot your switch. then shutdown and reinstall Picofly. This shoud correct your fuse-count.
More information and detailed description can be found here: https://sthetix.info/the-truth-about-fuses-why-your-ofw-wont-boot-picofly-rp2040/

Have a nice day and good luck!

Just rewatched, slowly, that vid again, and the solution is, exactly as you say. Don't think I'm confident enough to do that though. I don't play online with the switch, but it would have been nice to have it working.

I did use DayBreak, wish I'd known before updating....

 

[auggiethecat]

More information and detailed description can be found here: https://sthetix.info/the-truth-about-fuses-why-your-ofw-wont-boot-picofly-rp2040/

Oh... Wow. That is... not great. I'll be back soon...
I think I see why he made the tool at least. To "diagnose" this issue? That's a strange way to do it, but I guess it technically works. Its not the cause, and it speaks with misplaced certainty. Also I don't really see why this needs "fixing". If this truly is affecting you, just use hekate stock.

 

[auggiethecat]

Hi there
Did you update FW using Daybreak and having a Picofly installed?
If yes, open your console, disconnect Picofly and boot your switch. then shutdown and reinstall Picofly. This shoud correct your fuse-count.
More information and detailed description can be found here: https://sthetix.info/the-truth-about-fuses-why-your-ofw-wont-boot-picofly-rp2040/

Have a nice day and good luck!

I was going to make a breakdown of whats wrong here, but I've run out of energy to properly investigate this and explain it simply. Its a complicated issue that I'm still struggling to understand after months. So instead, here's what you should need to know about it:

The reason its still a thing is because... nobody cares, as its not a very real issue: If you have a modchipped console, you have to boot to a payload before booting to HOS, with the exception of modchip bypass (which is only applicable if you don't have an sd card with a payload in it). For a summery, here's why it doesn't really matter:

1. Stock boots fine. You don't need Nintendos bootloader; hekates stock works just fine
2. Its only caused by updating in syscfw, (usually via daybreak sometimes via Nintendo's updater, but its fairly random), so, just don't. Update in stock/ofw. (minor/patch updates are usually fine in syscfw, major updates are the ones that can cause problems like this)
3. Its fixed every time you do a major update in stock/ofw.
4. If its still broken and you take the modchip out, booting it just fixes the issue.

Its not really an issue that needs fixing. Just use stock. If you have an extraneous case where you think you could benefit from fixing this without updating, come talk to me and we can figure out a good solution. The things mentioned in this video are not good solutions.

This thread is a bit dead, but I hope someone still finds this useful!