Gateway says the following on their website regarding downgrading to 4.5:
I don't have a NAND mod, but I'm assuming they're just saying that because it's still in beta and they don't want to be responsible for any (more) bricks. Is there actually a significant risk, as long as I keep it plugged in and don't turn it off or anything during the process? My sysnand is 9.2, and my emunand is 9.4.
If I do a NAND backup beforehand, the worst case scenario is just that I'd need to get a NAND mod installed, rather than a new 3DS, right? I mean if even that is a significant risk I wouldn't want to try it yet, but if it's like a 1% chance I'm willing to accept the risk.
Has anyone tried to downgrade using GW and gotten a brick, or is Gateway simply overstating the risk since it hadn't had a significant amount of testing when they posted that?
We want to caution users using the downgrade feature: it is a dangerous operation as it will write to sysnand and if something goes wrong it may brick your 3DS.
We currently recommend that ONLY USERS WITH A NAND MOD try this, and report back any issues.
I don't have a NAND mod, but I'm assuming they're just saying that because it's still in beta and they don't want to be responsible for any (more) bricks. Is there actually a significant risk, as long as I keep it plugged in and don't turn it off or anything during the process? My sysnand is 9.2, and my emunand is 9.4.
If I do a NAND backup beforehand, the worst case scenario is just that I'd need to get a NAND mod installed, rather than a new 3DS, right? I mean if even that is a significant risk I wouldn't want to try it yet, but if it's like a 1% chance I'm willing to accept the risk.
Has anyone tried to downgrade using GW and gotten a brick, or is Gateway simply overstating the risk since it hadn't had a significant amount of testing when they posted that?