Hacking Screens do not turn on. Led blue yes

[Tocamos]

Good! I apologize again for my translator's English.

The screens of my 2DS do not light up. I followed several tutorials, changed the .boot file and nothing. Any solution? A friend told me that I should restore the NAND but since I do not want to leave it as a last resort.

Help?

 

[Byokugen]

We need more info. What did you exactly do? How, when?

 

[Tocamos]

Well here goes the long explanation:
I was banned two weeks ago by the wave of Nintendo bans. They spent about 10 days and I found another friendcodeseed_b to change then I did. However it did not work. In the tutorial I said that in case of not working we had to change the file SecureinfoA I did it and did not turn on anymore.
After several days with no solution came the update to LUMA and boot9trap, I updated everything but it still did not light.
To all this I had not made a backup on my pc (Yes, my mistake). But I did it now to remove all .bin files however it still does not fire.

 

[Byokugen]

Well here goes the long explanation:
I was banned two weeks ago by the wave of Nintendo bans. They spent about 10 days and I found another friendcodeseed_b to change then I did. However it did not work. In the tutorial I said that in case of not working we had to change the file SecureinfoA I did it and did not turn on anymore.
After several days with no solution came the update to LUMA and boot9trap, I updated everything but it still did not light.
To all this I had not made a backup on my pc (Yes, my mistake). But I did it now to remove all .bin files however it still does not fire.

Ca you post a pic of your sd card? Maybe luma update went wrong. You can rename. .bin.bak.to the .bin(delete the first .bin)

 

[Lacius]

Does the blue light stay on indefinitely, or does it come on and then turn off within seconds?

 

[SquidGuy]

Well here goes the long explanation:
I was banned two weeks ago by the wave of Nintendo bans. They spent about 10 days and I found another friendcodeseed_b to change then I did. However it did not work. In the tutorial I said that in case of not working we had to change the file SecureinfoA I did it and did not turn on anymore.
After several days with no solution came the update to LUMA and boot9trap, I updated everything but it still did not light.
To all this I had not made a backup on my pc (Yes, my mistake). But I did it now to remove all .bin files however it still does not fire.

Your 3DS is proboably bricked

 

[Byokugen]

Your 3DS is proboably bricked

Nope, you can't be sure yet.

 

[CrispyYoshi]

I'll ask what Lacius asked for emphasis: Does your blue LED light blink when you turn the console on, or does the blue light stay on?

 

[Lacius]

If you changed the SecureinfoA without CFW (e.g. Luma3DS), then you're bricked. I find it unlikely that you did this, but you're not giving us a lot of information to go on.

Did you install B9S? Did you have A9LH installed before that?

 

[Byokugen]

You should have boot.firm.bak , rename it to boot.firm delete boot.firm before doing this.

 

[NFates]

You must restore your SecureInfoA, every console has its own and if you inject the one from another 3DS this happens. At least that's what I have read.

 

[Lacius]

OP, did you edit your SecureInfoA, or did you copy one from another 3DS?

 

[Tocamos]

Ca you post a pic of your sd card? Maybe luma update went wrong. You can rename. .bin.bak.to the .bin(delete the first .bin)

http://i.imgur.com/UVLeN2g.png <- image

Does the blue light stay on indefinitely, or does it come on and then turn off within seconds?

It stays on indefinitely

OP, did you edit your SecureInfoA, or did you copy one from another 3DS?

I downloaded one and put it in my SD.

 

[Lacius]

http://i.imgur.com/UVLeN2g.png <- image


It stays on indefinitely


I downloaded one and put it in my SD.

You probably need to restore your SecureInfo_A. If you didn't backup your old one, you need to restore your NAND backup.

If you really don't want to restore your NAND backup, you could do the following:

1. Backup your current NAND that's not booting
2. Restore your old backup from when your system was booting
3. Dump your old SecureInfo_A
4. Restore the broken NAND
5. Restore the old SecureInfo_A

 

[Tocamos]

Is there any guide to do this? I do not understand much of these things

 

[Lacius]

Is there any guide to do this? I do not understand much of these things

I can try to walk you through it. First, are you able to boot into GodMode9 or Decrypt9WIP, or do I need to walk you through that too?

In other words, do you know how to boot into anything other than a black screen?

 

[Tocamos]

I can try to walk you through it. First, are you able to boot into GodMode9 or Decrypt9WIP, or do I need to walk you through that too?

In other words, do you know how to boot into anything other than a black screen?

If I can, with the start + on

 

[Lacius]

If I can, with the start + on

Download and boot the latest version of GodMode9. Make sure you have at least 1GB free on your SD card and make a new NAND backup. If you don't know how, let me know. After that, we're going to use GodMode9 to do a safe restore of your old sysNAND.

 

[Tocamos]

http://imgur.com/Du3rmSB

http://imgur.com/hJdOGRw

Well, the first picture is when you enter the Godmode9. (Select + on)
The second is where he had seen that he can do the backup. (Start + on) where should I do it?

 

[Lacius]

http://imgur.com/Du3rmSB

http://imgur.com/hJdOGRw

Well, the first picture is when you enter the Godmode9. (Select + on)
The second is where he had seen that he can do the backup. (Start + on) where should I do it?

In the GodMode9 main menu, hit the HOME button. Click "More..." and click "Backup NAND."