Hacking eFuses and 6.2 update

[lacrima08]

Hi all,

Sorry if the question has already been posted but to much threads...

If I update my switch to 6.2 firmware with ChoiDuJourNX. (to dump new keys with lockpick ...) can I restore my 6.0 backup (boot0 boot1 and rawdump) or not ?

will there be burnt efuses even if I use ChoiDuJourNX ? I read something like this when 6.2 firm launched .

I don't want to stay in 6.2 when it's not absolutely necessary (i don't get online for the moment and don't have games that require more than 5.1 firm)

Thanks

 

[Kafluke]

Yes it will prevent fuse burn and yes you can downgrade afterwards as long as you dont accidentally boot into OFW (turn on autoRCM)

 

[lacrima08]

Yes it will prevent fuse burn and yes you can downgrade afterwards as long as you dont accidentally boot into OFW (turn on autoRCM)

Thank You for your quick and clear response !!

 

[realg123]

Yes it will prevent fuse burn and yes you can downgrade afterwards as long as you dont accidentally boot into OFW (turn on autoRCM)

Hi what happens if you upgrade via ChoiDuJourNX to 6.2 and then boot into OFW without autoRCM?

 

[Kafluke]

Hi what happens if you upgrade via ChoiDuJourNX to 6.2 and then boot into OFW without autoRCM?

Then you just negated your reasons for using choi. Booting into OFW will burn the fuses so you may have just updated normally which also will burn fuses

 

[ZachyCatGames]

Hi what happens if you upgrade via ChoiDuJourNX to 6.2 and then boot into OFW without autoRCM?

It'll burn fuses

 

[realg123]

Thanks guys,
I'm assuming if you updated using choi, and booted into OFW it will stick work and not semi-brick but just burn the fuses?

 

[smf]

Thanks guys,
I'm assuming if you updated using choi, and booted into OFW it will stick work and not semi-brick but just burn the fuses?

Right. Letting it burn fuses only stops you booting earlier OFW.

Whenever you boot OFW it checks the fuses and will refuse to boot if more fuses are burnt than expected, if fewer fuses are burnt than expected then it will burn up to the expected number.

 

[pLaYeR^^]

Whenever you boot OFW it checks the fuses and will refuse to boot if more fuses are burnt, otherwise it will burn up to the expected number.

That's not exactly true. The fuses will only be burnt if you boot your console with the nintendo boot loader. If you inject a payload (for example the SX loader) and boot in this way in OFW, no fuses will be burnt.

 

[ZachyCatGames]

That's not exactly true. The fuses will only be burnt if you boot your console with the nintendo boot loader. If you inject a payload (for example the SX loader) and boot in this way in OFW, no fuses will be burnt.

If you use an alternate bootloader, then it isnt pure OFW

 

[pLaYeR^^]

If you use an alternate bootloader, then it isnt pure OFW

Whats different?

 

[Kafluke]

Whats different?

Why confuse noobs? I dont know why people feel the need to bring up what you did. There is exactly no benefit in using a custom boot loader to load OFW when fuse count is too high. In the context of saving your fuse count for downgrading later when/if a better exploit is released then using a custom boot loader wont help at all. That's why I say to people you cant downgrade if your fuses aren't burnt. Because you cant in the context of what they're asking. Do people correct me just so they can be right?

Yes, you can downgrade but then you have to use a custom boot loader to get into OFW and again, this accomplishes nothing.

 

[pLaYeR^^]

Why confuse noobs? That's why I say to people you cant downgrade if your fuses aren't burnt.

You CAN downgrade if your fuses aren't burned and you own a working backup of the low firmware.

 

[Kafluke]

You CAN downgrade if your fuses aren't burned and you own a working backup of the low firmware.

Did you even read the whole post. Yes I know you can but people are using that info thinking that they can just downgrade and then boot OFW without RCM and it will be fine. Just read the front page of the forum. Its filled with users complaining that they cant boot after a downgrade.

When/if another exploit is revealed for lower firmware you will need to have your OFW on that firmware booting without RCM. Why is this so hard for people to understand? There is no benefit to flashing your firmware to a lower version if you have use a custom boot loader to make it work!

It's all about context

 

[pLaYeR^^]

Did you even read the whole post. Yes I know you can but people are using that info thinking that they can just downgrade and then boot OFW without RCM and it will be fine. Just read the front page of the forum. Its filled with users complaining that they cant boot after a downgrade.

When/if another exploit is revealed for lower firmware you will need to have your OFW on that firmware booting without RCM. Why is this so hard for people to understand? There is no benefit to flashing your firmware to a lower version if you have use a custom boot loader to make it work!

It's all about context

You tell people to not confuse noobs but thats what you do here with your „context“. Think about it.

 

[ZachyCatGames]

Whats different?

Even with the "stock" option in custom bootloaders, some patches still get applied (ex. warmboot patches)

 

[pLaYeR^^]

Even with the "stock" option in custom bootloaders, some patches still get applied (ex. warmboot patches)

But its still defined as „OFW“ in SX OS. So I guess it doesn‘t matter.

 

[Kafluke]

You tell people to not confuse noobs but thats what you do here with your „context“. Think about it.

What you just said makes no sense. It's okay. I cant argue with stupid. Moving on

 

[lacrima08]

Hi all,

Update from 6.0 to 6.2.0 OK, new keys dumped.

Restored with success to my 6.0 backup

Same count of efuses than before update

Everything is fine !

Thanks you @Kafluke

 

[smf]

Whats different?

You didn't boot OFW. You booted something else which then loaded OFW but bypassed the fuse checks.

If you allow that to count as booting OFW then everything is OFW.