http://www.ktemkin.com/faq-fusee-gelee/

Kate has collected and answered the most common questions she's gotten regarding Fusée Gelée. Most notably she explains the three "types" of FG hacks, software, hardware (temporary) and hardware (permanent).

Enjoy!

Kate herself responded to this thread on page 26, thanks Kate!

There's a lot more here than I can easily respond to, so apologies if I miss posts or gloss over points.



This is correct-- while there likely will be software chains around for these things in the future, I don't see them as coming along as quickly as f-g. We don't have a non-coldboot exploit chain at all for 5.0.0-- and we haven't looked yet, as we've had other things to focus on and coldboot works. We do have one for 4.1.0, but it's centered around a couple of exploits that we don't want to burn-- we're hoping to use them to get an opportunity to poke around inside T214/Mariko.



I don't view you as particularly hostile, no. I don't know if challenge is generally a good thing-- sometimes you do have to accept that other people have different ethics or viewpoints from yourself and let that pass, especially if they're just doing stuff for fun-- but I don't view your post as hostile.



Jamais Vu (1.0.0 TrustZone hack) isn't my bug, but has been written up, and is just awaiting someone with the skills to have time to do a public interpretation. Déjà Vu is currently centered around the exploit I mentioned above, and we definitely want to hold onto that for as long as it's applicable. It's entirely a Switch bug, too, so I don't see it as being something that needs responsible disclosure.



For Déjà Vu, absolutely. (explained in last quote)



I don't agree that things like tweeting are ego. This is something I work on because I find it a lot of fun to hack on things, and there's definitely an aspect in which it makes me happy when seeing the results of things makes other people happy. There's also an aspect in which I hope that showing these things are possible inspires people to want to learn e.g. reverse engineering. This stuff is cool; and I want to share the excitement with others and lift them up as much as I can.

You don't have to believe me on that or like that that's my goal. I won't hold it against you if you don't.



I honestly support people updating when it makes sense; and I recognize that there's a conflict between holding back information and enabling others to make reasonable decisions about that. I don't like or feel good about secrecy, and I know it has implications. I've tried to be as clear as I can about the costs regarding updating without crossing the line into giving things away.



I think we've been pretty clear that 4.1.0 will eventually see a non-coldboot, software-only exploit with the same level of power. That's actually been posted on the ReSwitched Discord's FAQ for months, but I know the message gets skewed as its gets communicated over to other places. That's part of why I'm here, now-- I want to help clear things up.

The interactions between the operating system and the bootloader-- say on reboot-- are actually fairly limited; and knowing what any of them are is enough to point people at the particular section of bootrom that's vulnerable. That's why I'm not commenting on Fusée Gelée and how it relates to software-only solutions right now. I have said e.g. above that since there's no public way of getting the privileges necessary to run things, 4.1.0 isn't going to see a pure software solution that the public can use at the time that f-g is released. Software exploits will likely come in time; and it's possible we'll come up with things that are even easier than f-g.



I'm not sure if they'll take it seriously enough. I don't know how they are internally-- but I can't just assume they'll fail to do anything and skip disclosure. Honestly, I don't think a "security advisory" is really a bad thing, either-- there are definitely applications of Tegra chips that I and/or the public don't know about. If giving NVIDIA notice gives them time to explain exactly what's dangerous and allow their customers to remove and replace units from places where the vulnerability can cause harm, I consider that a win, and well worth delaying some public switch hacks by a few months.

I'll also say that my fear that vendors won't take the vulnerability seriously is a huge reason I'm so keen to get things out there-- and why I provided a date after which I'll tell the public what's going on that I've said was non-negotiable. I want to make sure this doesn't get hidden, and that people understand exactly what f-g can and can't accomplish, to minimize FUD while also letting people understand the actual risks are associated with using a vulnerable device.



It changes this from an exploit that's going to be usable before the affected people know it's a thing to something that people may have a chance to react to. Making the vulnerability public without disclosure really increases the odds someone is capable of using it to do bad.

I didn't really give NVIDIA a chance to sell-off stock; though. I've said publicly multiple times that there are bugs in Tegra processors well before NVIDIA reached out to me seeking disclosure. If anything, I think telling the public that these vulnerabilities exist while pursuing disclosure helps developers interested in using Tegra chips in the future ask the right question.



I've already said that while pure-software stuff is doable on 4.1.0; it'll be a wait. As far as I'm remembering, the only part of the chain that could require multiple tries to work is PegaSwitch, which is our browser-based entry point, and I haven't even tried the browser entry point that'll eventually be public to see how reliable it is. SciresM did the work to get our non-coldboot exploit working on 4.1.0; not me.



Yeah, that's hard-- especially as everyone has a different view as to how inconvenient things are. I don't know of a way to communicate this better without more details.

Incidentally, the 'inconvenience' verbiage came from SciresM and I discussing our respective views on updating. I think SciresM is more towards the opinion that people should hold back more often, where I'm more of the opinion that updating can be a good and reasonable option sometimes. The way we wound up phrasing things is a compromise between views.



(I'm going to assume this meant "on the hacking side". If not I'm not sure what hacking site you're referring to.)

Updating to latest just closes the possibility of using software exploits launched from Horizon, which can make setup more difficult. I know you'd like to know how much, but I unfortunately don't have a good way of qualifying that. As I've mentioned, if you're suffering from not being able to use your 3.0.1+ Switch, you probably do want to upgrade and just risk things being more inconvenient in the future. Worst comes to worst, if you decide you can't tolerate the inconvenience, you upgrade and then wind up having to figure out a modchip.

The downgrade protection fuses literally mean nothing to a system with f-g, which can entirely skip the downgrade check. Incidentally, SciresM actually accidentally bricked one of his systems in a way such that it was always failing the downgrade checks, and he's been able to use f-g to get that system up and running again.



I don't think that's clear at all, nor do I want to confirm or deny this. Sorry.



I think you're making a bunch of assumptions here, and that's maybe not a great idea. I'm not saying you're necessarily right or wrong; just that I don't think your assumptions are founded.



I don't think this contradicts. This is talking about vulnerabilities that aren't f-g; not because f-g doesn't work on 4.1.0, but because it's possible we may come up with vulnerabilities that are even nicer on 4.1.0 in the future.



I'm being as clear as I feel I can, and adding clarifications e.g. here where I think it helps. There will be different names for the the ways you can use f-g eventually; and I'll be fully open about everything once the summer rolls around and I'm not putting the disclosure timeline in jeopardy.



I know and have said about that this "bring your own exploit" business makes development exclusive, and that's exclusionary and I really don't like it-- I just don't see a way around it. I would love to get more developers and more perspective, and that's why my release date for f-g is tied to my disclosure timeline and not in particular to Atmosphère's release.




I've tried to point out approximately what the difficulty would be for some of the options to kind of provide this, but this is a hard thing to accomplish. In this case, providing details that are more specific really points a finger at vulnerability details, so there's not much I'm comfortable sharing. I've shared what I could-- as a data point, some of the other teams have outright stated that they think I've shared too much already and made things obvious. I don't agree or necessarily care about their opinons, but c'est la vie.



Well, this isn't the case. This has been disclosed to Nintendo, too-- as NVIDIA shares their vulnerability findings with downstream customers. It's more general malicious actors that I'd be worried about.



See above-- but I don't think I'd advise specifically updating to 4.1.0 unless that gives you enough access to the games you want.



I'm also super glad that we can do a lot of our work in the open. I hope there's a lot more of it in the future-- and I'd love to stream some of it.



I find the requirement disheartening as well, but I think this is the right way to do things, for now. I've explained my rationale above; feel free to ask questions.



I'm not sure why people are against communication, here. There were definite benefits to talking about f-g in the first place; including that it demonstrates that Tegra chips are vulnerable-- which hopefully influences buying decisions in the future and puts pressure on NVIDIA to seek as much of a fix as they can. After that there seemed to be definitely benefits to talking about more details, even in the limited sense that I'm able to. I've tried to give people more information than the nothing they would have had so they could have more of an idea whether it's be a good idea to e.g. pre-order a modchip or update their system. I know it can be frustrating to not get full disclosure, and that more information would help people to make a better or more conclusive decision, but full disclosure isn't an option until this summer. I don't think that's a reason to hold back information.



I don't have specific answers to your questions, unfortunately-- but I think it sounds like the main purpose of this Switch is as a gaming device and maybe you should upgrade and enjoy playing games with your son.



I don't think that asking for clarification is criticism. It might be rude to push me to answer something I said I wouldn't, but I don't think there's harm in answer.



I don't think I've said anything about opening the console or not. See above for my views on updating?



I'm not sure where you got this impression, or why you're confident about things enough to claim you know about the internal values or working of ReSwitched. This is also easily disprovable just from public information--Hedgeberg has tested out f-g on stream. I don't see it as great opsec to enumerate how many people have access to the vulnerability, but we've long had a policy of only giving exploit details to those who actually want to know them and are in a position where they can use them to help. This is a basic security precaution and not about trust.

I'm actually not sure how this is relevant to the broader discussion. Based on your post history, I can tell that you strongly support TX and the option they're providing, and you're welcome to that, but I think throwing around generic unfounded criticism of RS doesn't do much good and distracts from me answering community questions.



I don't think they're obviously more convenient, as they exist right now. They're both inherently however-tethered-you-consider-PegaSwitch, take a bunch of time to run, and rely on a pegaswitch entry point.



That's not correct-- everyone on a current hardware revision will be able to install and use CFW the day it's released, if they're willing to put in the effort and potentially take on some minor risk.



I'm actually not sure what you mean by this entire post? Sorry about that-- I'd love to address your ideas, but unfortunately I can't figure out your meaning.



That was about me having fun by trying to see if a DIY, cheap modchip option is reasonable. It turns out it is. As you've noted, it's not necessary on any firmware. I just really like the idea that the open exchange of knowledge -- especially when profit's not a motive -- can result in creation of neat options for the community. ^-^



Yep; that's exactly what it means.



I don't think this has been at all implied-- and you'd be hard pressed to find a way to make a solder-less Arduino option that even remotely fits in the Switch case.

I should also clarify that the DIY option isn't solderless.

If you have or are going to get the game anyway, you can. Those versions are pretty much interchangeable in the long-term.



Yep-- and it's possible at some point that we'll allow you to install Fake News without Puyo using f-g/Atmosphère. The original plan was to release Atmosphère for 1.0.0 first while we tried to figure out how to deal with Fusée Gelée, but we actually wound up with a disclosure schedule that was faster than we'd thought.

 

[ploggy]

Hey guys, I need a little help here. I'm about to buy a switch (the red mario one). I'm pretty sure it's still in v3.0.0 but the odysey game included is only a download code. Is it possible to download the game without updating?

I think you need to be on the latest Firmware to connect to the eShop to redeem that download code.?

 

[guily6669]

sadly i wish that they would do more for dev mode considering the possibilities it has, sadly i believe they limit it because of hackers, and exploits that may pop up. hopefully a jailbreak will release probably around the EOL for the xbox one.

4 me there's no point as I have a X360 with RGH with the custom unofficial Xbox original files which adds compatibility with almost all Xbox original stuff...

My X360 is OFF 4 years. Same 4 my PS3 which is not hacked and I bought later like in 2012 used cheap just for gt6 is off 4 years, they are dead consoles now.


Xbox One hacking 4 me is pointless, almost no one here owns it only PS4, then was a lot weaker than PS4 which was only fixed with the X model with its 6TFlops...

Anyway all exclusives are on PC, the only person I know from here with a Xbox 1 bought Forza horizon and he shared it with me so I could also play on my PC 4 free and I can even play online against him without needing to pay XbLive ...

Forza, Gears of war and others went all to PC, but anyway I only like Forza the rest of the exclusives I don't care.

So basically if you want a hacked Xone you buy a PC, can play online 4 free and even have all the billions? of PC extra games in addition to the Xbox games

 

[Quantumcat]

Is there something in particular you're concerned about?

That this is the same way the dramas with Hykem, Team Salt, and JustPingo began. Loads of hype, with the development looking really promising, a release date given a few months away or more, the developers answering questions which makes them lauded by all and celebrated, loads of hype with everyone being really excited, then no release, devs publicly quit or just fade away, and ensuing drama/memes.

In the Wii U's case, it severely stifled the scene. With a future release date set, and a developer that people believed in, what point was there in other people also pursuing hax? But that future date comes and goes, gets pushed back, comes and goes again, pushed back again .... and in the end, there's nothing. Squat. Zilch. And all that time someone else could have actually been developing something. After Hykem and Team Salt destroyed the scene, it got lucky again when the Brazillians came in with their release out of nowhere, and the scene suddenly came back to life and loads of people worked on multiple things and stuff actually started happening. But it all could have happened two years earlier if it wasn't for the aforementioned two.

Closed development + a long future release date [i.e. not just a few days for polishing and writing documentation/instructions] is an awful combination that only hurts things. The person who starts it usually (or always?) ends up quitting the project, the amount of time that passes hurts the scene, and obviously it frustrates hundreds of potential users. If I must be brutally honest, the thing that sways me to thinking history will repeat itself is, you could have released all this information under the Reswitched banner, and never put your name to it at all (and consulted with your colleagues on what they think should be communicated, to boot). Or, you know, just not said anything until the exploit notification period had elapsed and release was imminent. If being famous wasn't on your agenda, then you would have done this. So either you're interested in fame and all will go well [my fingers are crossed for this option] or you're interested in fame and there's going to be a lot of drama in this forum in a few months. Not having fame as a priority isn't possible.

I would say I am about 65% sure, on the information I have seen so far, that come July or August, some unforseen problem is going to come up and the release date is going to be pushed back or put on hold indefinitely. And during that time, we won't see TX's solution, because they've put development on hold or canned it due to your communications to the public (as they wouldn't be making much money) and the other teams probably won't be actively working on anything, since it is a waste of time if they can wait for Reswitched's release and build on that. I want to do cool stuff with my Switch as much as the next girl so I will be incredibly happy to be wrong. In fact, everyone is welcome to quote this post come release and rub my nose in it as much as they want - because that means I'll have CFW on my Switch, so I'll be absolutely ecstatic and nothing will be able to bring me down.

 

[Viri]

JustPingo

Kernel Time Machine Switch edition when?! I want to downgrade my Switch to 9.2.

 

[guily6669]

GOD speaked to my ears saying TX will deliver. I'm not worried..........(YET)

I also heard at Church that Kate will light us all and save us from stupidity and darkness of Nintendo knowledge

 

[leonmagnus99]

Still have it?

i do, but i couldn't possibly ship it out due to very high cost from fedex/dhl..

if you lived anywhere near id sell, I'm from iraqi Kurdistan.

 

[Ghassen-ga]

That this is the same way the dramas with Hykem, Team Salt, and JustPingo began. Loads of hype, with the development looking really promising, a release date given a few months away or more, the developers answering questions which makes them lauded by all and celebrated, loads of hype with everyone being really excited, then no release, devs publicly quit or just fade away, and ensuing drama/memes.

In the Wii U's case, it severely stifled the scene. With a future release date set, and a developer that people believed in, what point was there in other people also pursuing hax? But that future date comes and goes, gets pushed back, comes and goes again, pushed back again .... and in the end, there's nothing. Squat. Zilch. And all that time someone else could have actually been developing something. After Hykem and Team Salt destroyed the scene, it got lucky again when the Brazillians came in with their release out of nowhere, and the scene suddenly came back to life and loads of people worked on multiple things and stuff actually started happening. But it all could have happened two years earlier if it wasn't for the aforementioned two.

Closed development + a long future release date [i.e. not just a few days for polishing and writing documentation/instructions] is an awful combination that only hurts things. The person who starts it usually (or always?) ends up quitting the project, the amount of time that passes hurts the scene, and obviously it frustrates hundreds of potential users. If I must be brutally honest, the thing that sways me to thinking history will repeat itself is, you could have released all this information under the Reswitched banner, and never put your name to it at all (and consulted with your colleagues on what they think should be communicated, to boot). Or, you know, just not said anything until the exploit notification period had elapsed and release was imminent. If being famous wasn't on your agenda, then you would have done this. So either you're interested in fame and all will go well [my fingers are crossed for this option] or you're interested in fame and there's going to be a lot of drama in this forum in a few months. Not having fame as a priority isn't possible.

I would say I am about 65% sure, on the information I have seen so far, that come July or August, some unforseen problem is going to come up and the release date is going to be pushed back or put on hold indefinitely. And during that time, we won't see TX's solution, because they've put development on hold or canned it due to your communications to the public (as they wouldn't be making much money) and the other teams probably won't be actively working on anything, since it is a waste of time if they can wait for Reswitched's release and build on that. I want to do cool stuff with my Switch as much as the next girl so I will be incredibly happy to be wrong. In fact, everyone is welcome to quote this post come release and rub my nose in it as much as they want - because that means I'll have CFW on my Switch, so I'll be absolutely ecstatic and nothing will be able to bring me down.

Wow, you really have to relax, and at least give them some credits because a part of their work is open sourced, we lose nothing by waiting, no one is asking you to get your hopes up, you could just ignore the whole thing and wait untill the summer.

 

[Quantumcat]

Wow, you really have to relax, and at least give them some credits because a part of their work is open sourced, we lose nothing by waiting, no one is asking you to get your hopes up, you could just ignore the whole thing and wait untill the summer.

I fully intend to, but she did ask.

 

[thekarter104]

I think you need to be on the latest Firmware to connect to the eShop to redeem that download code.?

Yes, you need to have the latest update to connect to the eShop.
Are you sure it will be on 3.0.0? Super Mario Odyssey requirs 3.0.1 on cartridge. I'm sure Nintendo isn't that stupid to put an Odyssey bundle with 3.0.0 on it lol.

 

[Risingdawn]

That this is the same way the dramas with Hykem, Team Salt, and JustPingo began. Loads of hype, with the development looking really promising, a release date given a few months away or more, the developers answering questions which makes them lauded by all and celebrated, loads of hype with everyone being really excited, then no release, devs publicly quit or just fade away, and ensuing drama/memes.

In the Wii U's case, it severely stifled the scene. With a future release date set, and a developer that people believed in, what point was there in other people also pursuing hax? But that future date comes and goes, gets pushed back, comes and goes again, pushed back again .... and in the end, there's nothing. Squat. Zilch. And all that time someone else could have actually been developing something. After Hykem and Team Salt destroyed the scene, it got lucky again when the Brazillians came in with their release out of nowhere, and the scene suddenly came back to life and loads of people worked on multiple things and stuff actually started happening. But it all could have happened two years earlier if it wasn't for the aforementioned two.

Closed development + a long future release date [i.e. not just a few days for polishing and writing documentation/instructions] is an awful combination that only hurts things. The person who starts it usually (or always?) ends up quitting the project, the amount of time that passes hurts the scene, and obviously it frustrates hundreds of potential users. If I must be brutally honest, the thing that sways me to thinking history will repeat itself is, you could have released all this information under the Reswitched banner, and never put your name to it at all (and consulted with your colleagues on what they think should be communicated, to boot). Or, you know, just not said anything until the exploit notification period had elapsed and release was imminent. If being famous wasn't on your agenda, then you would have done this. So either you're interested in fame and all will go well [my fingers are crossed for this option] or you're interested in fame and there's going to be a lot of drama in this forum in a few months. Not having fame as a priority isn't possible.

I would say I am about 65% sure, on the information I have seen so far, that come July or August, some unforseen problem is going to come up and the release date is going to be pushed back or put on hold indefinitely. And during that time, we won't see TX's solution, because they've put development on hold or canned it due to your communications to the public (as they wouldn't be making much money) and the other teams probably won't be actively working on anything, since it is a waste of time if they can wait for Reswitched's release and build on that. I want to do cool stuff with my Switch as much as the next girl so I will be incredibly happy to be wrong. In fact, everyone is welcome to quote this post come release and rub my nose in it as much as they want - because that means I'll have CFW on my Switch, so I'll be absolutely ecstatic and nothing will be able to bring me down.

It does have echoes of the Hykem incident unfortunately, it even has a similar promised release if I recall correctly, summer/e3.

@ktemkin The problem is alot of us got pretty burnt out by Hykem, so I don't think I'm alone when I say many of us would prefer not to know anything really untill something is released. You can't win here of course, one section can never have enough information, the other just wants the product not discussion.

Discourse about ethics and disclosure is all well and good, and I'm not going to lie it's exciting to get technical nuggets of info. But all it really does is build a shed load of hype, and like quantum said; Hykem, team salt, it never seems to end particularly well tbh and it more often than not leads to more speculation and questions than answers.

It doesn't really matter how much information is disclosed, folks will never be happy till they know everything and have the product there. When the core exploit can't really be talked about, for whatever reason, speculation will never stop and nor will the questions.

Right now it's descended into a typically opinionated debate on the moral ambiguity of disclosure windows and the ethics of business practices. And that's one area that is frankly none of most people's business, being as your moral compass is yours and yours alone, and you are free to do as you will without the constant need to justify your actions but it ends up pulling out a load of biased ill-informed opinions.

Unless something is open-sourced, accessble from a git-hub and free to all it should be worked on behind scenes imho, where a disclosure agreement has been decided even more so.

There is still a chance this could not come to anything. A legal cease and desist or actual legal action is fully possible. If Nintendo or Nvidia or whoever decide your work is going to cost them long-term why would they not? The fact this has supposed ramifications beyond a simple 'games console' makes that eventuality seem even more likely, or at worst would provide a perfect 'get out clause' not unlike the 'federal confiscation' of the work of Hykem.

 

[BL4Z3D247]

That this is the same way the dramas with Hykem, Team Salt, and JustPingo began. Loads of hype, with the development looking really promising, a release date given a few months away or more, the developers answering questions which makes them lauded by all and celebrated, loads of hype with everyone being really excited, then no release, devs publicly quit or just fade away, and ensuing drama/memes.

In the Wii U's case, it severely stifled the scene. With a future release date set, and a developer that people believed in, what point was there in other people also pursuing hax? But that future date comes and goes, gets pushed back, comes and goes again, pushed back again .... and in the end, there's nothing. Squat. Zilch. And all that time someone else could have actually been developing something. After Hykem and Team Salt destroyed the scene, it got lucky again when the Brazillians came in with their release out of nowhere, and the scene suddenly came back to life and loads of people worked on multiple things and stuff actually started happening. But it all could have happened two years earlier if it wasn't for the aforementioned two.

Closed development + a long future release date [i.e. not just a few days for polishing and writing documentation/instructions] is an awful combination that only hurts things. The person who starts it usually (or always?) ends up quitting the project, the amount of time that passes hurts the scene, and obviously it frustrates hundreds of potential users. If I must be brutally honest, the thing that sways me to thinking history will repeat itself is, you could have released all this information under the Reswitched banner, and never put your name to it at all (and consulted with your colleagues on what they think should be communicated, to boot). Or, you know, just not said anything until the exploit notification period had elapsed and release was imminent. If being famous wasn't on your agenda, then you would have done this. So either you're interested in fame and all will go well [my fingers are crossed for this option] or you're interested in fame and there's going to be a lot of drama in this forum in a few months. Not having fame as a priority isn't possible.

I would say I am about 65% sure, on the information I have seen so far, that come July or August, some unforseen problem is going to come up and the release date is going to be pushed back or put on hold indefinitely. And during that time, we won't see TX's solution, because they've put development on hold or canned it due to your communications to the public (as they wouldn't be making much money) and the other teams probably won't be actively working on anything, since it is a waste of time if they can wait for Reswitched's release and build on that. I want to do cool stuff with my Switch as much as the next girl so I will be incredibly happy to be wrong. In fact, everyone is welcome to quote this post come release and rub my nose in it as much as they want - because that means I'll have CFW on my Switch, so I'll be absolutely ecstatic and nothing will be able to bring me down.

But SigHax and B9S had the same hype and more of a wait and that ended up being legit(not that I ever doubted it).

I could see if it was just Kate and no ReSwitched team that was working on this but she's working with ScriesM and I think that dude has earn his trust with the community. I don't think he'd be working with someone who was untrustworthy.

Summer is nearing and either way you look at it there is an exploit and CFW coming even without Fusée Gelée (although I don't doubt it's real and coming out with Atmosphére/Thermosphére this summer).

 

[sarkwalvein]

I have too say that for burns you always have alloe vera or some cream. /s

I personally prefer to know about the status, developments, intentions, etc. Even if in the end it doesn't come to fruition.

Those reads are very enjoyable. Hell perhaps I never even use the hacks in the end, but I still enjoy the reads.

 

[DarthDub]

I have too say that for burns you always have alloe vera or some cream. /s

I personally prefer to know about the status, developments, intentions, etc. Even if in the end it doesn't come to fruition.

Those reads are very enjoyable. Hell perhaps I never even use the hacks in the end, but I still enjoy the reads.

I enjoy it too, even if I don't understand it.

 

[guily6669]

Those reads are very enjoyable. Hell perhaps I never even use the hacks in the end, but I still enjoy the reads.

Red Alert, Spy detected, exterminator on the way .

I like the reads too. Anyway I don't judge any of them... Now If it was a Kickstarter project where you would have to pay to then be a scam I would go there and tell them to go F* them selfs...

But since this is free I just wait and don't even like to judge specially before even getting to the release reported time. And if it's released good, if it's not I just keep waiting for other hack release...

 

[Kioku]

But SigHax and B9S had the same hype and more of a wait and that ended up being legit(not that I ever doubted it).

I could see if it was just Kate and no ReSwitched team that was working on this but she working with ScriesM and I think that dude has earn his trust with the community. I don't think he'd be working with someone who was untrustworthy.

Summer is nearing and either way you look at it there is an exploit and CFW coming even without Fusée Gelée (although I don't doubt it's real and coming out with Atmosphére/Thermosphére this summer).

This. There's a huge difference between what we've got going on here and what happened with Hykem.

 

[BelmontSlayer]

So I'm wondering if it is going to be possible to replace the Switch's battery with something of comparable battery life and size so the back plate still fits?
Same question for the Joycons.
Also, any battery life saving tips would be appreciated (any specific to Switch uses?).

I work in the computer/phone repair business and one of our vendors sells Switch batteries, LCD and other parts. Best advice to maintain your battery life is don't let the battery drop below 20%, charge it often. Hopefully it isn't against the rules to post this here but it's the only place (in the USA) I know of that sells Switch parts.

https://www.revampwholesale.com/catalogsearch/result/?q=Switch

I'm pretty sure it's still in v3.0.0 but the odysey game included is only a download code. Is it possible to download the game without updating?

Nope, you have to be on the newest firmware to download games or updates.

 

[sarkwalvein]

Nope, you have to be on the newest firmware to download games or updates.

But I have to say that I "love" this new troll method that Nintendo has implemented, where you can go into the eShop, browse whatever is in there, even buy things, all with the old firmware (v4.1), and only after that it tells you "There's data that has not been downloaded due to having an outdated firmware version. Please update." Genius.

 

[Risingdawn]

This. There's a huge difference between what we've got going on here and what happened with Hykem.

Yeah hopefully, it's just there was alot shown and talked about at the time and little doubt in it's authenticity, promises and release dates were made, assurances given. And then it all turned into a steaming pile of Hykem.

It's not really a doubt here about 'fake' exploits for me, more about potential legal dangers. And I'd rather remain sceptical and then be pleasantly surprised, than get excited and risk potential disappontment.

 

[BelmontSlayer]

But I have to say that I "love" this new troll method that Nintendo has implemented, where you can go into the eShop, browse whatever is in there, even buy things, all with the old firmware (v4.1), and only after that it tells you "There's data that has not been downloaded due to having an outdated firmware version. Please update." Genius.

They want to take your money and THEN force you to update lololol.

 

[annson24]

But I have to say that I "love" this new troll method that Nintendo has implemented, where you can go into the eShop, browse whatever is in there, even buy things, all with the old firmware (v4.1), and only after that it tells you "There's data that has not been downloaded due to having an outdated firmware version. Please update." Genius.

So they'll allow you to purchase any game even in lower firmware only to find out that you cannot download it without updating to the latest firmware? Sneaky bastards.

Sent from my SM-G950F using Tapatalk