Hacking 3.0.0 Firmware exploit without RCM jig - Where are we now? (Q4 2018)

[TerminatR]

It seems like a long time since the original 3.0.0 exploit was released (actually only a few months though)

Are we any closer to release of a RCM free bootloader for this firmware?

It seems a shame to let this thing sit idle with so many games to play. And yes, I realize that I could update to firmware 4, 5 or 6 without blowing e-fuses, but I'd rather not bother if there's light at the end of the tunnel.

It's almost as if all the scene resources are being targeted at the newest firmware, which I understand makes sense, covering the largest user base, but is anyone trying to solve the RCM free boot issue?

 

[Kubas_inko]

we are pretty much waiting for ninty to release revision which would fix most of the exploit.

 

[mattytrog]

RCM free?

Maybe run choidujour?

Might attempt to make a RCM toggle nro actually.

Possible? Don't know yet.

 

[TerminatR]

we are pretty much waiting for ninty to release revision which would fix most of the exploit.

Could you elaborate?

I had thought that firmware 3.0.1 patched whatever made the original exploit without RCM possible. Are you implying that boot loaders are possible on later firmware without RCM jig?

 

[Kubas_inko]

Could you elaborate?

I had thought that firmware 3.0.1 patched whatever made the original exploit without RCM possible. Are you implying that boot loaders are possible on later firmware without RCM jig?

Some parts still work/can be applied to the latest FW (probably). So Ninty is waiting for the community to release the exploit and patch it or we are waiting for Ninty to patch it so that the community can then release the exploit. Someone has to do the first step.

 

[mattytrog]

Some parts still work/can be applied to the latest FW (probably). So Ninty is waiting for the community to release the exploit and patch or we are waiting for Ninty to patch it so that the community can then release the exploit. Someone has to do the first step.

I agree.

It's a bit like the police not knowing where an axe murderer is...

"I know, let's wait until the next severed limb appears... The we will know where to pounce"

 

[kkcheong]

You are doing yourself a disservice. Just update officially and play all the games. Nintendo switch main reason is for playing pirated games. And sxos can be used to enable that. Waiting for cold/warm boot is exercise in futility and a bit dumb when we all play happily with our Switch.

 

[mattytrog]

Just make sure your fuses are safe... Choidujour it to 5.1.0 / 6.0 and play

 

[TerminatR]

You are doing yourself a disservice. Just update officially and play all the games.

I understand all that. Still, I'd almost rather sell my 3.0.0 to someone who appreciates what it could be in the future (maybe for someone who can afford multiple Switch consoles) and get an updated one to enjoy.

After waiting all this time, it would seem like a waste to just blindly update it.

 

[kkcheong]

I understand all that. Still, I'd almost rather sell my 3.0.0 to someone who appreciates what it could be in the future (maybe for someone who can afford multiple Switch consoles) and get an updated one to enjoy.

After waiting all this time, it would seem like a waste to just blindly update it.

If you wait any longer it's even more waste. Its just your feeling. Its just psychology state of mind. Overcome it. Update it. Play it and have fun.

 

[mattytrog]

1) nand backup
2) boot into CFw
3) choidujour upgrade keeping autoRCM on
4) play
5) downgrade when you are ready

 

[TerminatR]

Some parts still work/can be applied to the latest FW (probably). So Ninty is waiting for the community to release the exploit and patch it or we are waiting for Ninty to patch it so that the community can then release the exploit. Someone has to do the first step.

Okay, but.... wasn't the original exploit already released? People were running homebrew on the Switch before anyone knew what an RCM jig or Fusee was.

 

[Kubas_inko]

Okay, but.... wasn't the original exploit already released? People were running homebrew on the Switch before anyone knew what an RCM jig or Fusee was.

That was also fixed on 4.1.0 and up (or maybe on 3.0.2, idk).
But deja vu and jamais vu are based on something different.

 

[TerminatR]

That was also fixed on 4.1.0 and up (or maybe on 3.0.2, idk).
But deja vu and jamais vu are based on something different.

It was patched in 3.0.1. But that's exactly what I am asking about - it's different than Fusee, but in some ways better, as you don't require extra hardware or dongles to launch.

That was the whole point of not updating 1.0.0 through 3.0.0. Hopefully people haven't forgotten.

...Remember when people where paying premium prices for Pokken Tournament to get their Switch to 3.0.0 to do the web based hack.

 

[Kubas_inko]

It was patched in 3.0.1. But that's exactly what I am asking about - it's different than Fusee, but in some ways better, as you don't require extra hardware or dongles to launch.

That was the whole point of not updating 1.0.0 through 3.0.0. Hopefully people haven't forgotten.

But homebrew is not CFW.
It is not better than fusee, as it does not allows you to patch the FW.
And updating 1.0.0 is the worst thing you can do.

And right now, there are no exploits for homebrew only for 3.0.1 and higher. Nobody is focusing homebrew only. Everyone wants CFW.

 

[TerminatR]

But homebrew is not CFW.
It is not better than fusee, as it does not allows you to patch the FW.
And updating 1.0.0 is the worst thing you can do.

And right now, there are no exploits for homebrew only for 3.0.1 and higher. Nobody is focusing homebrew only. Everyone wants CFW.

Can you have unsigned code execution (home brew) without patching the firmware on some level?

Maybe I am wrong, but I just feel the old exploit is under developed and didn't hit its true potential.

I still feel like I am missing some key information on this subject.

 

[Deleted member 381889]

we are pretty much waiting for ninty to release revision which would fix most of the exploit.

ninty have already fixed the bootrom exploit in devices manufactured after july 2018

Some parts still work/can be applied to the latest FW (probably). So Ninty is waiting for the community to release the exploit and patch it or we are waiting for Ninty to patch it so that the community can then release the exploit. Someone has to do the first step.

all public exploits have already been patched, either in 3.0.1 or in new hardware revisions

 

[Kubas_inko]

ninty have already fixed the bootrom exploit in devices manufactured after july 2018

all public exploits have already been patched, either in 3.0.1 or in new hardware revisions

You don't say...

Do you know what we're talking about?
About the unreleased exploits...

 

[bundat]

I understand all that. Still, I'd almost rather sell my 3.0.0 to someone who appreciates what it could be in the future (maybe for someone who can afford multiple Switch consoles) and get an updated one to enjoy.

After waiting all this time, it would seem like a waste to just blindly update it.

I mean, if you restore a NAND backup you make at 3.0, it'll be basically like going back in time and never having updated (as long as you always have noGC enabled).

I see no reason not to update if you can easily restore a backup to go back to 3.0.

And yes, I realize that I could update to firmware 4, 5 or 6 without blowing e-fuses, but I'd rather not bother if there's light at the end of the tunnel.

I dunno, this just sounds like laziness or unwillingness to learn new things or go outside your comfort zone.

I personally have gone back and forth between 4.1, 5.0, and 6.0 several times using NAND backups I've made in each version. It's quite painless, and it's like I never even updated after going back to an old backup.

Nobody is working on RCM free exploits using lower FW versions because it's so easy to downgrade if/when someone ever comes out with something (which is unlikely as everyone is working on the newest versions). You'll most likely be waiting forever.

I see no reason to do this... unless you have a second Switch that you can play with the latest FW version for the latest games. In that case, feel free to keep it in 3.0 forever. If this is your only Switch though... then it just seems like a total waste.

 

[Deleted member 381889]

You don't say...

Do you know what we're talking about?
About the unreleased exploits...

You don't even know if they exist tho