Update OLED OFW with Picofly Installed

[JonniBravo]

Hi all,

I recently installed a Picofly rp2040 on my Switch OLED and stupidly did not update the ofw first. I logged into the official firmware yesterday and the switch is asking to update to the latest firmware, I do not know what firmware it is on or what firmware it wants to update to.

I have heard that if you update via OFW it messes with the Picofly timings and can damage the chip. What is the safest way to update the OFW.

 

[Deleted member 681324]

I wouldn't go too far into utilizing emummc just yet... maybe disconnect ribbon cables from chip, and update OFW? May have to redo emummc partition, like a fresh install?

 

[JonniBravo]

Is it not possible to update OFW via daybreak on CFWsys?

 

[Deleted member 681324]

... but you just said you're worried about your rp2040?! Good luck in your endeavors

 

[JonniBravo]

I just wandered if doing this offline in daybreak was safe as opposed to allowing OFW and Nintendo to do the process, but I guess your right, I should disconnect the chip and do it that way, I am just lazy is all.

 

[alecocr20]

Hello,

I have updated a couple of times having my picofly installed without any major issues.
1. Update atmosphere and all on the SD card to the new FW
2. Update the OFW
3. Update CFW with daybreak

Not sure how updating the OFW can break the picofly, pretty much sure it's not possible and worst case you open the console and reset to chip so it retrains

 

[JonniBravo]

Hello,

I have updated a couple of times having my picofly installed without any major issues.
1. Update atmosphere and all on the SD card to the new FW
2. Update the OFW
3. Update CFW with daybreak

Not sure how updating the OFW can break the picofly, pretty much sure it's not possible and worst case you open the console and reset to chip so it retrains

Thank you, so you update OFW as you would normally in the OS, Not with daybreak in CFW.

 

[bvang913]

Daybreak is for updating the firmware in atmosphere which you should be doing as well.

 

[MaD_mAnIaC]

Hello,

I have updated a couple of times having my picofly installed without any major issues.
1. Update atmosphere and all on the SD card to the new FW
2. Update the OFW
3. Update CFW with daybreak

Not sure how updating the OFW can break the picofly, pretty much sure it's not possible and worst case you open the console and reset to chip so it retrains

This is exactly what needs to be done.
First chip boot after updating OFW could take longer than usual, just leave it alone while it trains and hekate should pop in 30s or so.

 

[JonniBravo]

Thank you, I'll do this when I finish work.

 

[Rockfello]

Daybreak is for updating the firmware in atmosphere which you should be doing as well.

This is supposing that you need to update the emunand right ? If I only use the CFWsys to apply cheats in offline games and backup my save files I can just update through Nintendo official means right ?

 

[bvang913]

This is supposing that you need to update the emunand right ? If I only use the CFWsys to apply cheats in offline games and backup my save files I can just update through Nintendo official means right ?

Yeah, if you're not using emunand I suppose you don't need to update firmware on that side.

 

[ELY_M]

following, I hope updating to 20.0.0 do not break the rp2040. I have mod chipped oled switches.
I know to wait for updated atmosphere code.

 

[slimeinacloak]

following, I hope updating to 20.0.0 do not break the rp2040. I have mod chipped oled switches.
I know to wait for updated atmosphere code.

Tested a lite and oled that have rp2040 chips in them, boots to hekate fine on 20.0.0, emuMMC works also (beside sleep issue due to fuses)

 

[cucholix]

Tested a lite and oled that have rp2040 chips in them, boots to hekate fine on 20.0.0, emuMMC works also (beside sleep issue due to fuses)

Did you had to update the modchip itself?

 

[slimeinacloak]

Did you had to update the modchip itself?

There were already on v2.80 (https://github.com/rehius/usk/releases/tag/PicoFly_2.80_2024.09.04_04-12)

 

[urherenow]

Tested a lite and oled that have rp2040 chips in them, boots to hekate fine on 20.0.0, emuMMC works also (beside sleep issue due to fuses)

What? That's a complete lie, considering not even Atmosphere works with 20.0.0 yet. Stop spreading misinformation. It will be at LEAST several days before CFW can be used on 20.0.0.

And if you perform a major update on OFW (different from Hekate stock, or SYS CFW), then you will have to reset, and retrain your mod chip. But that's not going to help you play anything at all, if you update to 20.0.0 before everything is updated to work with it.

I mean... you *could* update your sysnand and leave emummc on 19.0.1, and that would be fine. But update via sys cfw or hekate stock, to prevent blown fuses (or face sleep issues in emummc)... but once you do that, you won't be able to boot sys cfw OR hekate stock. The moment you boot into sys, your fuses will be blown. It's simply not worth it, until things are updated.

 

[slimeinacloak]

What? That's a complete lie, considering not even Atmosphere works with 20.0.0 yet. Stop spreading misinformation. It will be at LEAST several days before CFW can be used on 20.0.0.

And if you perform a major update on OFW (different from Hekate stock, or SYS CFW), then you will have to reset, and retrain your mod chip. But that's not going to help you play anything at all, if you update to 20.0.0 before everything is updated to work with it.

I mean... you *could* update your sysnand and leave emummc on 19.0.1, and that would be fine. But update via sys cfw or hekate stock, to prevent blown fuses (or face sleep issues in emummc)... but once you do that, you won't be able to boot sys cfw OR hekate stock. The moment you boot into sys, your fuses will be blown. It's simply not worth it, until things are updated.

Sorry shouldve been more specific, I was talking about the console booting to hekate after being updated to 20.0.0 as I assumed ELY_M's was about the new fuses or if there were any breaking changes to the current rp2040 firmware that stops the payload being injected.

The sysMMC of the consoles I tested with were updated to 20.0.0 and the emuMMC were still on 19.0.1 (why I mentioned the sleep issue)

 

[urherenow]

Sorry shouldve been more specific, I was talking about the console booting to hekate

Even more specific, you're just referring to hekate booting NYX. I don't think this is what people are asking about. They generally want to know if they can still use the console.

If you update sysmmc in OFW mode (not through hekate at all, with either cfw or stock options), then you have a chance at just getting a black screen when trying to boot through hekate, or even while trying to boot hekate or any payload.bin. In this case, a chip reset/retrain is needed. With picofly... this might be an automatic thing. I don't have one, so I don't know. With hwfly, this requires you to remove the back cover, and power on the Switch while shorting 2 points on the chip, to reset it.

 

[ELY_M]

I had to update to 20.0.1 because of online game forcing me to update.
I updated and I have 19.0.0v atmosphere working (20_support branch on github)
NOTE: I am not using emunand on the OLED.

the mod chip booted abit slow but it got to boot up.