They only hold back on exploits when there is a reason to do so. Like not burning exploits when there is evidence of a new hardware revision on the horizon.Someone capable who will release it when they discover it
EmuNAND/RedNAND support? Or just CFW for SysNAND? Many thanks.95% good to go i'd say?
No end user should have, honestly.
Versions for what? System? Atmosphere? Hekate?It was quite useful to know which versions were good and which ones weren't at the right time.
Gbatemp wasn't as accurate and clear as reswitched at the time, even if some screenshots were posted here.
Exploitable system versionsVersions for what? System? Atmosphere? Hekate?
Emunand is honestly a waste of time considering you'd need to write a 30GB image to an SD. It's not practical like it was on 3DS. And paperclips are cheaper than 128GB+ sd cards. I'd imagine it'd be easy to implement in fs_mitm anyways so if that happens, just load that kip in ReiNX and it'll work. *shrug*EmuNAND/RedNAND support? Or just CFW for SysNAND? Many thanks.
Exploitable system versions
Emunand is honestly a waste of time considering you'd need to write a 30GB image to an SD. It's not practical like it was on 3DS. And paperclips are cheaper than 128GB+ sd cards. I'd imagine it'd be easy to implement in fs_mitm anyways so if that happens, just load that kip in ReiNX and it'll work. *shrug*
Don't we have a way to upgrade without burning fuses? If that could be practically implemented into a CFW, you could emulate EmuNAND.It's useful for the people who are still technically on a low firmware and want to
just upgrade the emuNAND![]()
That method involves hijacking the Switch's bootloader before turning on the console. Meaning you'd have to install the CFW. Which we cannot do without Nintendo's trustworthy keys. Until that happens, AutoRCM is our best bet.Don't we have a way to upgrade without burning fuses? If that could be practically implemented into a CFW, you could emulate EmuNAND.
Yeah, but what if- hypothetically- you implement that into a cfw, so your original firmware was always 1.0, and the cfw just is 5.1 or whatever?Yeh I'm on the latest with my original fuses unburnt just waiting for a coldboot then I'll go back down to 1.0.0 and just update the emuNAND
Couldn't it be done on 1.0 only, even? I'm not familiar with the ins and outs of that firmware, but from what I hear, it's wide open. Please correct me if I'm wrong, I'm speculating with no basis.That method involves hijacking the Switch's bootloader before turning on the console. Meaning you'd have to install the CFW. Which we cannot do without Nintendo's trustworthy keys. Until that happens, AutoRCM is our best bet.
i mean, i would imagine if you only boot cfw and never boot ofw you'll never run fuse burner code so yea.Yeah, but what if- hypothetically- you implement that into a cfw, so your original firmware was always 1.0, and the cfw just is 5.1 or whatever?
Couldn't it be done on 1.0 only, even? I'm not familiar with the ins and outs of that firmware, but from what I hear, it's wide open. Please correct me if I'm wrong, I'm speculating with no basis.
Theoretically yes, but look how many people have a 1.0 console (unfortunately)Couldn't it be done on 1.0 only, even? I'm not familiar with the ins and outs of that firmware, but from what I hear, it's wide open. Please correct me if I'm wrong, I'm speculating with no basis.
There's still a sizable portion. Might be worth making a bounty if the interest is low enough, people have been waiting since March 2017 for something like this.Theoretically yes, but look how many people have a 1.0 console (unfortunately)
Hm. How long would that take to create something like that for niche users once a proper CFW solution is completed? As above, if it's prohibitive, I'll back it.i mean, i would imagine if you only boot cfw and never boot ofw you'll never run fuse burner code so yea.