Hacking Question No game updates without updating console?

  • Thread starter Thread starter toastytwo
  • Start date Start date
  • Views Views 5,369
  • Replies Replies 32
Hi erverybody,

i tried to update Kirby and it always nags me to update the console first before the game gets an update...
OFW or SXOS CFW / auto when starting the game or manually via menu doesn't make a difference!

Took me a while to get exFAT up and running while staying on 4.1.0, don't wanna ruin it now...

Anyone figured this out?

How did you get exFAT working on 4.1.0?
 
Yeah, I think it's up to 3.0.1 only.
It's a shame because my Switch came with 3.0.2 :(

Now all that is left for me is to wait for software hacks that exists up to 4.1 only as far as we know.
No sciresm has said that he has achieved trustzone execution up to and including 4. 1 which means cold boot for custom firmware.
 
No sciresm has said that he has achieved trustzone execution up to and including 4. 1 which means cold boot for custom firmware.

Hmmm.... But that print from page 1 said otherwise?
Right at the end.

cVuMVe0.png
 
No sciresm has said that he has achieved trustzone execution up to and including 4. 1 which means cold boot for custom firmware.
Trustzone exploitation =/= coldboot. The Trustzone exploitation SciresM is referring to is Deja Vu as seen below:

As you can tell, this is a warmboot and not a coldboot.
 
Yeah, I think it's up to 3.0.1 only.
It's a shame because my Switch came with 3.0.2 :(
You can downgrade to 3.0.1 and you don't even have to use AutoRCM as 3.0.1 and 3.0.2 use the same efuse count.
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
Once Emunand is released I will downgrade as I'm also on 3.0.2, but my Mario Odyssey cartridge requires 3.0.2 for now.

Ok, now I see why he says that it was hard.
The first tutorial makes it look way harder than it actually is, there are only 18 small steps.
 
Last edited by riyyi,
You can downgrade to 3.0.1 and you don't even have to use AutoRCM as 3.0.1 and 3.0.2 use the same efuse count.
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
Once Emunand is released I will downgrade as I'm also on 3.0.2, but my Mario Odyssey cartridge requires 3.0.2 for now.


The first tutorial makes it look way harder than it actually is, there are only 18 small steps.

I'm not sure if this downgrade method will work the way you think when it comes to exploiting. Can you really do downgrade 3.0.2 to 3.0.1 and never have to use hacks to boot?
As for Mario Odyssey: it can be played on 3.0.1, as it requires >= 3.0.1
 
I'm not sure if this downgrade method will work the way you think when it comes to exploiting. Can you really do downgrade 3.0.2 to 3.0.1 and never have to use hacks to boot?
As for Mario Odyssey: it can be played on 3.0.1, as it requires >= 3.0.1
Yes, you can also downgrade from 5.1.0 to 5.0.0 as they require the same amount of fuses.
switchbrew.org/index.php?title=Fuses#Anti-downgrade
My Odyssey cart is v001 so it requires 3.0.2 instead of 3.0.1, it's very recently purchased.
 
  • Like
Reactions: TheKerplunk
I'm not sure if this downgrade method will work the way you think when it comes to exploiting. Can you really do downgrade 3.0.2 to 3.0.1 and never have to use hacks to boot?
As for Mario Odyssey: it can be played on 3.0.1, as it requires >= 3.0.1
You need hacks to restore a NAND backup. But since the stock firmware of your console was 3.0.2, where do you want to get a 3.0.1 NAND backup which you can restore?
 

Site & Scene News

Popular threads in this forum