Hacking [NEED HELP] New3DS 2.1 for OTP

[democracy]

Sorry, English isn't my native language and just learn it a while. I mean they said new 3ds with stucked 2.1 only can be updated to 4.x, not 6.x or up.

Look, I cant remember the details because I did the research long ago, but 4.x for n3ds is bad news!!! Pokemon y update, you can launch other exploits and it worked for me!

So your option is; hardmod or pokemon y update but there is a risk of brick with y update as well, but, at least on Y update there are other exploits you can try from there.

 

[Deleted User]

Look, I cant remember the details because I did the research long ago, but 4.x fo n3ds is bad news!!! Pokemon y update, you can launch other exploits and it worked for me!

Well. Silly me.

 

[Khangaroo]

And this is why if I ever (try to) install A9LH, I am going to get a hardmod first.

 

[Margen67]

And this is why if I ever (try to) install A9LH, I am going to get a hardmod first.

Just because someone messed it up doesn't mean you will.

 

[Khangaroo]

Just because someone messed it up doesn't mean you will.

Yeah, but I am extremely clumbsy. Mostly because I am flashing an old 3ds firmware on a new 3ds.

 

[d0k3]

Yeah, but I am extremely clumbsy. Mostly because I am flashing an old 3ds firmware on a new 3ds.

I am scared of breaking my N3DS myself and all that safety stuff (that software is ~70% safety, ~30% functionality) in OTPHelper is in part so that I don't mess up doing this. Not doing it for safety reasons is a valid decision, but don't overestimate the danger. As it is now, OTPHelper will detect basically everything that can go wrong and stop you from continuing. The only undetectable thing right now is if Wifi is on or not (see here).

In fact, the only bricks that I've seen for weeks come from people who forgot about the Wifi (see, f.e. this thread). And you can of course decide to go fully against Plailects guide and ignore all warning, in which case you could also manage to brick.

 

[I_AM_L_FORCE]

I heard somewhere that taking out the battery for a while resets the clock and WiFi? Try that

 

[Deleted User]

I am scared of breaking my N3DS myself and all that safety stuff (that software is ~70% safety, ~30% functionality) in OTPHelper is in part so that I don't mess up doing this. Not doing it for safety reasons is a valid decision, but don't overestimate the danger. As it is now, OTPHelper will detect basically everything that can go wrong and stop you from continuing. The only undetectable thing right now is if Wifi is on or not (see here).

In fact, the only bricks that I've seen for weeks come from people who forgot about the Wifi (see, f.e. this thread). And you can of course decide to go fully against Plailects guide and ignore all warning, in which case you could also manage to brick.

Thanks @d0k3 for adding new feature to remind N3DS users for turning WiFi only. This will prevent more bricked N3DS .

I heard somewhere that taking out the battery for a while resets the clock and WiFi? Try that

Nice suggestion. Will try this if this happen again (please not again).

Recap (according to some suggestions):
1. Don't update with game cart with 4.x firmware update. (Mine bricked because Luigi Mansion 4.5)
2. Otherwise, use 6.x instead. Only Pokemon X and Y will work.(Tested by @democracy with Pokemon Y 6.1)
3. Booting into safe mode may ask you to enable the wireless (via software). But don't update there! (Thanks to @SomeGamer)
3. Take out the battery then put it again. This will reset clock and WiFI. (Thanks to @Luke Gainsford)

 

[Hakujou]

That's weird that 4.x bricks because that's on Plaitect's guide : https://github.com/Plailect/Guide/wiki/3DS-Stuck-(2.1.0-Without-Functional-Browser)
If this is confirmed, we should make a pull request to the guide to remove that part...

 

[Deleted User]

That's weird that 4.x bricks because that's on Plaitect's guide : https://github.com/Plailect/Guide/wiki/3DS-Stuck-(2.1.0-Without-Functional-Browser)
If this is confirmed, we should make a pull request to the guide to remove that part...

Well it's according to @democracy. @Plailect should discuss this with him.

 

[pkmz]

I did mine with Luigi mansion legit cart when a9hl first released and had no issues. Once i got to 4.5 ran browserhax to rewrite my sysnand backup.

 

[cultopi]

People who got into this problem usually have menuhax/themehax installed. I have a suggestion to the plailect guide for getting the OPT on N3DS to avoid this completely. Change the guide to use only browserhax instead of "hax of your choice." This way wifi is forced to be on all the time.

 

[Plailect]

Thanks @d0k3 for adding new feature to remind N3DS users for turning WiFi only. This will prevent more bricked N3DS .

Nice suggestion. Will try this if this happen again (please not again).

Recap (according to some suggestions):
1. Don't update with game cart with 4.x firmware update. (Mine bricked because Luigi Mansion 4.5)
2. Otherwise, use 6.x instead. Only Pokemon X and Y will work.(Tested by @democracy with Pokemon Y 6.1)
3. Booting into safe mode may ask you to enable the wireless (via software). But don't update there! (Thanks to @SomeGamer)
3. Take out the battery then put it again. This will reset clock and WiFI. (Thanks to @Luke Gainsford)

A 4.X update in general most certainly does not brick, you may have just gotten unlucky or some 4.X versions may not work, but that will need more testing.

As for the other suggestions, I could use some confirmation on those as well.

 

[weks]

well you can try removing battery and wait 15 minutes then put it back. and see if the wireless is enabled.

I have exactly same issue as yours and removing and inserting battery seems to work on my 3DS.

 

[Deleted User]

I did mine with Luigi mansion legit cart when a9hl first released and had no issues. Once i got to 4.5 ran browserhax to rewrite my sysnand backup.

Isn't that browserhax is only available for 9.x or up?

People who got into this problem usually have menuhax/themehax installed. I have a suggestion to the plailect guide for getting the OPT on N3DS to avoid this completely. Change the guide to use only browserhax instead of "hax of your choice." This way wifi is forced to be on all the time.

Ninjhax is my entrypoint. And since the one that got downgraded is EmuNAND then move it to SysNAND, seems like menuhax as SysNAND entrypoint don't affect this CMIIW.

A 4.X update in general most certainly does not brick, you may have just gotten unlucky or some 4.X versions may not work, but that will need more testing.

As for the other suggestions, I could use some confirmation on those as well.

Thanks. Keep gather more informations.

well you can try removing battery and wait 15 minutes then put it back. and see if the wireless is enabled.

I have exactly same issue as yours and removing and inserting battery seems to work on my 3DS.

New 3DS? or Old 3DS?

I got the new problem now. Sent it to modder and he said the nand can't be detected. Other consoles can be detected. Gonna open a new thread soon.

This is the thread: https://gbatemp.net/threads/n3ds-xl-nand-not-detected.423614/

 

[cavolo]

The nand detection is boring, I've tried 30min of plug-in/out, reboot console, ... after many tries, my computer see my nand. For a friend, it was detected in the first try, I've retried mine and... nope, again, difficulties to detect.

 

[weks]

Isn't that browserhax is only available for 9.x or up?

Ninjhax is my entrypoint. And since the one that got downgraded is EmuNAND then move it to SysNAND, seems like menuhax as SysNAND entrypoint don't affect this CMIIW.

Thanks. Keep gather more informations.

New 3DS? or Old 3DS?

I got the new problem now. Sent it to modder and he said the nand can't be detected. Other consoles can be detected. Gonna open a new thread soon.

This is the thread: https://gbatemp.net/threads/n3ds-xl-nand-not-detected.423614/

Mine new 3DS = no wireless switch.

 

[Zanoab]

People who got into this problem usually have menuhax/themehax installed. I have a suggestion to the plailect guide for getting the OPT on N3DS to avoid this completely. Change the guide to use only browserhax instead of "hax of your choice." This way wifi is forced to be on all the time.

I think it would be easier to have OTPHelper make sure internet is enabled and working before starting "One Click Setup".