How the hell did you get on 2.1 on N3DS? Is this some sort of arm9loaderhax trickery? If you're not bricked you should be able to use a cart to upgrade.Uh, I'm stuck on 2.1 but I used New Super Marios 2 to get on 4.1.0.4E on my N3DSXL, what do I need to do? Have cooking mama which mounts an 9.2...
The A9LH requires you to downgrade to 2.1 and by changing headers information you "unbrick" it on N3DSHow the hell did you get on 2.1 on N3DS? Is this some sort of arm9loaderhax trickery? If you're not bricked you should be able to use a cart to upgrade.
You'll have to get them from an upgrade tutorial from this forum... since you'll need the exact ones for your console region o.oFeeling frustrated about this, really dunno what to do to fix my problem <.< Btw, couldn't I update directly using a card or is it somewhat different?
So does it create a 2.1 FW for the New3DS? Because O3DS would hard brick wouldn't it?The A9LH requires you to downgrade to 2.1 and by changing headers information you "unbrick" it on N3DS
O3DS is able to run 2.1 since it "existed" for it. but since N3DS "oldest" FW version was 9.5 or something like that.... if you get it to 2.1 the console will enter a state of "WTF is this ancient thing?!" and brick... using OTPHelper you unbrick it and then inject it to sysNAND... dump OTP and then restore 9.2So does it create a 2.1 FW for the New3DS? Because O3DS would hard brick wouldn't it?
Yes, followed that guide and when I went to 2.1 on my N3DS, I noticed that I forgot to turn on the wifi after the second format of the emunand, so since 2.1 can't access to that function, I'm stuck like this from yesterday.How the hell did you get on 2.1 on N3DS? Is this some sort of arm9loaderhax trickery? If you're not bricked you should be able to use a cart to upgrade.
The A9LH requires you to downgrade to 2.1 and by changing headers information you "unbrick" it on N3DS
You'll have to get them from an upgrade tutorial from this forum... since you'll need the exact ones for your console region o.o
Yeah I meant O3DS FW on the New3DS. I got an O3DS at launch So I know 2.1 is a thing. I'll check out a thread on it because I'm not sure how OTPHelper would work.O3DS is able to run 2.1 since it "existed" for it. but since N3DS "oldest" FW version was 9.5 or something like that.... if you get it to 2.1 the console will enter a state of "WTF is this ancient thing?!" and brick... using OTPHelper you unbrick it and then inject it to sysNAND... dump OTP and then restore 9.2
OTP Helper can't help you get out of 2.1 that's for sure... I just tried explaining why you could get to 2.1 without "bricking" the console heheYeah I meant O3DS FW on the New3DS. I got an O3DS at launch So I know 2.1 is a thing. I'll check out a thread on it because I'm not sure how OTPHelper would work.
I do have all of the backups from the guide, separated in named folders after the part/section/even step number, but does browserhax even works on 4.1? OTP is still on my SD so I shouldn't have problems launching it, I want to restore my sysnand.bin+emunand_formatted.bin, then reboot into emunand+turning on that damned wifi option and retry the downgrade, to finally go into final part 5 of said guide.If you still have your sysnand 9.2 backup (i know you deleted the emunand backup but bare with me here) you could use that browser exploit that loads up the OTP helper application and flash the 9.2 sysnand to the emunand instead, and thus getting a 9.2 emunand installed which is better than no emunand at all. from there you can update it to 10.6 emunand.
I do have all of the backups from the guide, separated in named folders after the part/section/even step number, but does browserhax even works on 4.1? OTP is still on my SD so I shouldn't have problems launching it, I want to restore my sysnand.bin+emunand_formatted.bin, then reboot into emunand+turning on that damned wifi option and retry the downgrade, to finally go into final part 5 of said guide.
I've been told that since my fw is very old, making such a big update as 9.2 would brick my console, that's why I've been nagging people like everywhere for help Dunno if that guide can help me, but I'll be sure to read it good, thanks.I have no idea why you wouldn't just restore your sysNAND backup taken from the start of the process, but okay.
Follow this guide and hope it works on whatever version you happened to be on.
I've been told that since my fw is very old, making such a big update as 9.2 would brick my console, that's why I've been nagging people like everywhere for help Dunno if that guide can help me, but I'll be sure to read it good, thanks.
Oh, you're on a N3DS? How the hell do you not have a backup of sysNAND? That should have been the first thing created and backed up to several places the second you were on 9.2, much less at the beginning of the OTP/2.1 downgrade process.
Not sure what you can do at that point if you don't have a sysNAND backup and sysUpdater can't fix it.