Hacking So...is my N3DS dead?

[leonmagnus99]

ouch this is no good, i had a issue with my og3ds (a9lh+aureinand'now luma') my problem was error has occured please turn off the 3ds and power it back on, and that issue sticked permanent, i was forced to do a restore to get it to work again.

and that issue actually sticked right after i installed something with BBM , similar to you..? hm now i am afraid to use BBM on my n3ds to be honest..
would not want to go through so much restore hassle.

i hope you get your n3ds fixed somehow.

edit: i am wondering if either A9LH or Aurei(Luma) have some compatibility issues with BBM etc.? i would hope not.

edit2: and also maybe because of updated sysNAND? cause that is what i use.. i have wiped my emuNAND partition from all my ds consoles (og,ogXL and n3dsXL) i have updated sysNAND on all of them cause i prefer to have one thing that performs all? i like having it cleaner etc.

but now i am wondering if it would be better to have an emuNAND at all times just in case , i do have backups though ,but considering you can run into various issues so randomly hm.

btw. @ op < what mSD are you using? class4, 10? is it a legit brand etc.?

 

[Ichigo1000]

Nope

 

[3dsn00b]

btw. @ op < what mSD are you using? class4, 10? is it a legit brand etc.?

One is Samsung EVO other is SanDisk Ultra, both class 10 and ~45MB/s. Both bought from legit reputable stores.

--------------------- MERGED ---------------------------

I really think the only way to save this N3DS is to either find the old pre-A9LH sysNAND or being able to run sysupdater. I've like 70% given up tbh and will just drown myself in beer and use it as a paper weight

 

[Ichigo1000]

One is Samsung EVO other is SanDisk Ultra, both class 10 and ~45MB/s. Both bought from legit reputable stores.

--------------------- MERGED ---------------------------

I really think the only way to save this N3DS is to either find the old pre-A9LH sysNAND or being able to run sysupdater. I've like 70% given up tbh and will just drown myself in beer and use it as a paper weight

What was the last thing you did for this to happen?

 

[Disco]

He wrote it in first post... Installed the game via BBM, there was no game after succesfull install, he then rebooted console and bam...black screen.

This makes me wonder about BBM, I am using it for quite some time frome when i used GW emuNAND. I also tried the latest FBI, but it freezes.
Is there any other alternative for a9lh/Luma?

 

[Ichigo1000]

You can get bricked in recovery mode even with firm protection?

 

[SomeGamer]

This makes me wonder about BBM, I am using it for quite some time frome when i used GW emuNAND. I also tried the latest FBI, but it freezes.
Is there any other alternative for a9lh/Luma?

Speaking of which, can FBI 2.0 install DLC properly? (The text-based version couldn't.)

 

[SnakeOil992]

Speaking of which, can FBI 2.0 install DLC properly? (The text-based version couldn't.)

Ιt can.

 

[SomeGamer]

Ιt can.

So now if I install a DLC CIA will it actually be usable? (The old FBI also installed it, but the DLC didn't appear in-game.)

 

[SnakeOil992]

So now if I install a DLC CIA will it actually be usable? (The old FBI also installed it, but the DLC didn't appear in-game.)

Yeah, I tried it.

 

[SomeGamer]

Yeah, I tried it.

Thanks a lot! Then I have no reason to keep DevMenu anymore.

 

[DocKlokMan]

@3dsn00b Please try this:

Download GodMode9 and use Luma3DS's chainloading feature to boot it like you can Decrypt9.

Once you've opened GodMode9, navigate to this folder: CTRNAND:/title/00040138/00000002/content

Tell us what's in there.

 

[daxtsu]

You can get bricked in recovery mode even with firm protection?

In safe mode, FIRM protection doesn't get applied. The act of entering safe mode is fine, but if you update with it, say goodbye to your N3DS if you have no hardmod. The reason it happens is because A9LH corrupts the secret key part of NAND, and updating the system firmware doesn't fix that, so your N3DS will decrypt FIRM to garbage (as it would with A9LH), but since A9LH isn't there, it's a brick. In theory it's fine for O3DS to update via safe mode with A9LH (but it'd remove A9LH), but I wouldn't recommend it at all.

 

[3dsn00b]

Download GodMode9 and use Luma3DS's chainloading feature to boot it like you can Decrypt9.

How do I do this just rename the GodMode9.bin into b_GodeMode9.bin and put it into the luma/payloads folder and then hold b on boot?

 

[DocKlokMan]

How do I do this just rename the GodMode9.bin into b_GodeMode9.bin and put it into the luma/payloads folder and then hold b on boot?

B did not work for me, try down_G9.bin and hold down while booting.

 

[Ichigo1000]

In safe mode, FIRM protection doesn't get applied. The act of entering safe mode is fine, but if you update with it, say goodbye to your N3DS if you have no hardmod. The reason it happens is because A9LH corrupts the secret key part of NAND, and updating the system firmware doesn't fix that, so your N3DS will decrypt FIRM to garbage (as it would with A9LH), but since A9LH isn't there, it's a brick. In theory it's fine for O3DS to update via safe mode with A9LH (but it'd remove A9LH), but I wouldn't recommend it at all.

I see. Is there something that can block the 3ds from entering recovery? Just for troll proofing, since if recovery bricks a9lh, is useless.

 

[daxtsu]

I see. Is there something that can block the 3ds from entering recovery? Just for troll proofing, since of recovery bricks a9lh, is useless.

If you use Luma it already blocks that key combo. Otherwise, simply using something like Arm9select or some other boot manager should block it automatically (because they don't boot FIRM immediately).

 

[3dsn00b]

Tell us what's in there.

This is what I see in GodMode9

 

[DocKlokMan]

Alright, in the cm

This is what I see in GodMode9
View attachment 47158

Alright, in the cmd folder is the a file called 00000002.CMD ?

If there is, please back out to the main GodMode9 screen and press Y to unlock sysNAND for writing. Then go to CTRNAND:/title/00040138/00000002/content and press X to delete these files:

0000001f.app and 00000002.CMD in the cmd folder. See if it boots now.

 

[3dsn00b]

Alright, in the cmd folder is the a file called 00000002.CMD ?

OK, but my folder isn't 0000002 it's 20000002... is that normal?

--------------------- MERGED ---------------------------

Alright, in the cmd folder is the a file called 00000002.CMD ?

and it's 00000003.cmd