Hacking Weird 2ds Softbrick

[Abu]

Here's my story:

-Went through the plailect guide step by step, got to part 2 of the guide.

-Downgraded to 2.1.0 ctrtransfer just to realize the wireless on the 2ds is turned off. google searched ways to turn it back on again, came across a post somewhere instructing to update the sysnand with a super smash bros REV0

1 card which I happen to have to get back to 9.2.

-What ended up happening was, the 2ds got updated, it booted up fine. The catch was that no application wanted to boot, the 2ds stopped reading game cards and trying to access the browser results in a frozen screen.


I haven't really managed to get A9hl on any 3ds model and have been doing fine with emunand on multiple systems*2 O3dses, 1 2ds and 1 N3ds*. I have a japanese N3ds that's on 9.2 rearing to go, but I held off doing the plailect guide because of this experience. Do you guys have any suggestions? or should I just sell this 2ds as is and stick with emunand on my N3ds.


Honestly, I am willing to pay someone to do it for me at this point.


EDIT: Entering soft recovery mode works, but I am holding off updating it to
11.1.0-34 U

EDIT 2: I tried to update through recovery mode and the update ended up failing.

EDIT 3:even after multiple attempts, the 2ds wont update through recovery mode and will always show the same error as the image posted below.

 

[Deleted-379826]

Here's my story:

-Went through the plailect guide step by step, got to part 2 of the guide.

-Downgraded to 2.1.0 ctrtransfer just to realize the wireless on the 2ds is turned off. google searched ways to turn it back on again, came across a post somewhere instructing to update the sysnand with a super smash bros REV01 card which I happen to have to get back to 9.2.

-What ended up happening was, the 2ds got updated, it booted up fine. The catch was that no application wanted to boot, the 2ds stopped reading game cards and trying to access the browser results in a frozen screen.


I haven't really managed to get A9hl on any 3ds model and have been doing fine with emunand on multiple systems*2 O3dses, 1 2ds and 1 N3ds*. I have a japanese N3ds that's on 9.2 rearing to go, but I held off doing the plailect guide because of this experience. Do you guys have any suggestions? or should I just sell this 2ds as is and stick with emunand on my N3ds.


Honestly, I am willing to pay someone to do it for me at this point.

If you read around in the guide, you would of known you had to just remove battery and place it back in and wireless would be auto turned on!

 

[Quantumcat]

Here's my story:

-Went through the plailect guide step by step, got to part 2 of the guide.

-Downgraded to 2.1.0 ctrtransfer just to realize the wireless on the 2ds is turned off. google searched ways to turn it back on again, came across a post somewhere instructing to update the sysnand with a super smash bros REV01 card which I happen to have to get back to 9.2.

-What ended up happening was, the 2ds got updated, it booted up fine. The catch was that no application wanted to boot, the 2ds stopped reading game cards and trying to access the browser results in a frozen screen.


I haven't really managed to get A9hl on any 3ds model and have been doing fine with emunand on multiple systems*2 O3dses, 1 2ds and 1 N3ds*. I have a japanese N3ds that's on 9.2 rearing to go, but I held off doing the plailect guide because of this experience. Do you guys have any suggestions? or should I just sell this 2ds as is and stick with emunand on my N3ds.


Honestly, I am willing to pay someone to do it for me at this point.

You could have just taken the battery out and reinserted it :-/

If you downgrade to 2.1.0 on New 3DS or 2DS and left Wireless Communication off, you can re-enable the wireless by removing the battery for several seconds then booting back up.

You will probably end up having to update it to the latest version. But wait to see if anyone can suggest anything else.

 

[Abu]

If you read around in the guide, you would of known you had to just remove battery and place it back in and wireless would be auto turned on!

Just use a screw driver and remove the battery at the back of the 2ds right? http://en-americas-support.nintendo.com/app/answers/detail/a_id/610/~/how-to-remove,-reseat,-or-replace-the-battery
...yeah I feel like a dumb ass now, cannot say much to excuse myself.

 

[Deleted-379826]

Just use a screw driver and remove the battery at the back of the 2ds right? http://en-americas-support.nintendo.com/app/answers/detail/a_id/610/~/how-to-remove,-reseat,-or-replace-the-battery
...yeah I feel like a dumb ass now, cannot say much to excuse myself.

Yeah

 

[Abu]

Is there a way to factory reset my 2ds's setting without Tinyformat or any other homebrew applications?

Don't tell me to enter to "system settings" because I cannot do that on the 3ds's menus.

 

[Quantumcat]

Is there a way to factory reset my 2ds's setting without Tinyformat or any other homebrew applications?

Don't tell me to enter to "system settings" because I cannot do that on the 3ds's menus.

You can format through System Settings. As long as you're not below 6.0.

Edit: why can't you enter the settings? You could also update through the recovery menu.

 

[Abu]

You can format through System Settings. As long as you're not below 6.0.

Edit: why can't you enter the settings? You could also update through the recovery menu.

Part of the softbrick is not being able to enter system settings. but I can navigate through recovery mode just fine.
I can see the applications on the home menu, but I cannot enter any of the applications. it isn't a full software brick, but it looks like a bad update or something like that.

 

[Quantumcat]

Part of the softbrick is not being able to enter system settings. but I can navigate through recovery mode just fine.
I can see the applications on the home menu, but I cannot enter any of the applications. it isn't a full software brick, but it looks like a bad update or something like that.

Ah that sucks. Maybe you could try another cart with a higher firmware on it (before giving up and updating through recovery mode).

 

[Abu]

Ah that sucks. Maybe you could try another cart with a higher firmware on it (before giving up and updating through recovery mode).

Carts aren't bootable neither, it isn't much of a loss to be honest. I used the 2ds as a A9hl guinea pig before trying it on a N3ds and ended up messing it up for a minor reason.

 

[Quantumcat]

Carts aren't bootable neither, it isn't much of a loss to be honest. I used the 2ds as a A9hl guinea pig before trying it on a N3ds and ended up messing it up for a minor reason.

Well if you have another old 3DS or 2DS you can always use DSiWare downgrade on it after updating.