Crap. Then just need to wait for TX solution.Nope. You're screwed atm.
Like I said it's a patched switch and like BaamAlex said I think it's dead we can't downgrade patched switch. Need to wait TX solution. But thx your answearNote that by updating to version 9, you also burnt a fuse related to the game cart.
So if you go back to a lower firmware, you won't be able to use original game carts.
Yes it's 9.0.1 a mistake of my part sorry.What is 9.0.3? i thought the latest was 9.0.1. Even the official site says it's 9.0.1
What is 9.0.3? i thought the latest was 9.0.1. Even the official site says it's 9.0.1
What is your problem ? We can do mistake.LOL.. Many people loved to use "accidentally" as an excuse. LOL!
What is your problem ? We can do mistake.
Up to you to believe or notre.
We can update ipatched switches with ChoixdujourNX ?
EDIT: Nevermind - just learned about Pegaswitch
And this is why you should not even have an entry for launching CFW sysNAND on an iPatched Switch. Just keep everything on emuNAND and pretend your sysNAND doesn't even exist as it takes so little to lock yourself out of homebrew/CFW when you are using the sysNAND.Hello all,
I updated accidently the OFW (sysnand?) 4.1.0 of my Ipatched switch to 9.0.1 with choixdujourNX. It's possible to downgrade ?
I have a backup of my nand.
Thx.
You are right in saying that some are liars, but I think that we should not generalize because we can not know who is telling the truth or not. We use the word "accidentally" to say "I made a mistake". As you said it may be the problem, but some people may take what you wrote (maybe that's not the point). Put yourself in their place one day and you'll see: pNo, no problem here. Some people are the liars. I have seen many time here say same things over and over. We can make a mistakes but used the word "accidentally" often for switch as pretends can be noticed. This Switch is very easy to be disabled so that's no excuse, really.
You are right in saying that some are liars, but I think that we should not generalize because we can not know who is telling the truth or not. We use the word "accidentally" to say "I made a mistake". As you said it may be the problem, but some people may take what you wrote (maybe that's not the point). Put yourself in their place one day and you'll see: p
And this is why you should not even have an entry for launching CFW sysNAND on an iPatched Switch. Just keep everything on emuNAND and pretend your sysNAND doesn't even exist as it takes so little to lock yourself out of homebrew/CFW when you are using the sysNAND.
You can also understand the frustration that it gives when you have a new game that is waiting for you on your PC (like pokemon sword) and just waiting for you to install it on the switch but that asked for an update of the software and by hurry you make the bigger dumpling.Yeah. I already put myself in their place one day a long time ago and I understand.
And if you have to update the emunand software with choixdujourNX you always have to tick emunand otherwise you get fucked like me.You can update with choidujournx, but it won't help as you can't avoid burning the fuses with an ipatched switch.
How that works is you force into RCM on every boot and then use a payload, but that can't possibly work for you. Either choidujournx will refuse to enable autorcm, or your switch will be bricked and require you to remove autorcm using a hard mod. Either way as soon as you boot then fuses will be burned.
if you want the latest version on an ipatched switch then you need to setup emunand, but of course you need to be on a quite low firmware to be able to trigger that right now.
I'm pretty sure you can't update sysNAND from emuNAND. The whole point is that sysNAND access is redirected, that's what makes emuNAND work, anything that tries to write to sysNAND gets redirected. Otherwise if they left ways to bypass the redirection, Nintendo could take advantage of that, use it to detect a hacked console and write some flag to sysNAND etc. that tells the servers to ban you the next time you connect.This is the problem i used choixdujourNX in emunand to update my sysnand leaving the choice sysnand without doing it on purpose.
--------------------- MERGED ---------------------------
You can also understand the frustration that it gives when you have a new game that is waiting for you on your PC (like pokemon sword) and just waiting for you to install it on the switch but that asked for an update of the software and by hurry you make the bigger dumpling.
--------------------- MERGED ---------------------------
And if you have to update the emunand software with choixdujourNX you always have to tick emunand otherwise you get fucked like me.
I think yes in choixdujourNX you have the choice to update sysnand or emunand. The mistake that I had is leaving tick sysnand by default.I'm pretty sure you can't update sysNAND from emuNAND. The whole point is that sysNAND access is redirected, that's what makes emuNAND work, anything that tries to write to sysNAND gets redirected. Otherwise if they left ways to bypass the redirection, Nintendo could take advantage of that, use it to detect a hacked console and write some flag to sysNAND etc. that tells the servers to ban you the next time you connect.
But with which tool we can downgrade ? If it's possible.@mattytrog and/or @MatinatorX
Wouldn't it be possible to do a raw dump of the nand? I guess you need the keys to do a "raw" downgrade as well?