Hacking n3DS wont boot after A9LH update

[MiePx3]

Both.
Will do, I sure do have backups!

 

[AlucardjX]

if without sd inserted your led stays blue and 2 black screen i think you have bricked for sure,sorry man...

 

[The Real Jdbye]

@MiePx3
You didn't replace arm9loaderhax.bin at any point during the update did you? Make sure you're using the one from Luma3DS. There is an arm9loaderhax.bin designed to shut down the 3DS so it could be possible that you replaced it by mistake. Just making sure

 

[MiePx3]

Thanks for the suggestion guys, but I tried so many arm9loaderhax.bin, it has to be my 3DS.
Ill hardmod it later today, so im probably fine anyway. But I appreciate your efforts!

 

[Yami Anubis ZX]

Hardmod should fix. I have posted in the past that changing A9LH forks or updating is potentially dangerous. Unless there is a major development in A9LH there is really no reason to mess with it if you already have a working A9LH setup. Good luck, I hope you can get a hardmod and install a NAND backup.

That would have helped me like 3 months ago when the fork changing began. Plus back then I never knew there were multiple forks.

 

[Deleted member 117573]

I myself changed forks before and got lucky. Then I started seeing posts that some people bricked and decided right then I would not change again unless a major game changing improvement comes along. I am using @FIX94 A9LH which has screen init but keeps the backlight off. I use it with arm9select also by @FIX94 and even though it is not the most advanced or updated there are currently no disadvantages compared to all the other forks. Sorry if my post upset you.

 

[Dimensional]

I stuck with the one installed by AuroraWright's SafeA9LHInstaller, which was mentioned in Plailect's guide for installing A9HL and Luma3DS.

 

[JCR1]

so the a9lh consoles really aren't brick proof after all.

 

[MiePx3]

so the a9lh consoles really aren't brick proof after all.

I wouldnt say that. "Noobs" will probably never try what I did and people who understand thiere stuff wouldnt anyway.
Im that typical windows user who wants anything to be on the latest patch. Even if it involvs things I have no idea about.
So, as long you follow instructions and dont use things you are not supposed to do, A9LH semms to be pretty prick proof.

 

[Halvorsen]

My 3DS does the exact same but a9lh works properly. Stays on when no SD is inserted and turns off when no payload is found on the SD Card.
So I don't think it's a brick, it seems to function normally.
Try using another SD Card.
Try putting an arm9loaderhax.bin in every directory of the card.
Try to remember if there were any errors during installation.

 

[Margen67]

so the a9lh consoles really aren't brick proof after all.

Only if you don't follow the guide.

 

[gkoelho]

Isnt recovery mode bad with a9lh

Is bad cause CFW patches doesnt prevent recovery mode from updating firm0\firm1 which means 11.0 = no homebrew access

 

[Deleted User]

Is bad cause CFW patches doesnt prevent recovery mode from updating firm0\firm1 which means 11.0 = no homebrew access

Not to mention updating through Recovery Mode on an N3DS flat-out bricks it...

 

[Yami Anubis ZX]

It's not even possible to get to recovery mode on A9LH, so it can't brick it,.

 

[Ichigo1000]

Not to mention updating through Recovery Mode on an N3DS flat-out bricks it...

What? I remember hearing recovery mode is fixed though.

 

[nickwhit]

It's not even possible to get to recovery mode on A9LH, so it can't brick it,.

Hes referring to DURING the process.. not after its completed.
Its mentioned in the Troubleshooting section of the guide.

Black screen on SysNAND boot after downgrading

1. Try booting with your SD card out, and then reinserting it after booting.
   1. Power off your 3DS by holding down the power button.
   2. Take out the SD card.
   3. Power on the 3DS.
   4. When the home menu appears, reinsert your SD card.
2. If you have a hardmod and a NAND backup, flash the backup back to SysNAND.
3. Try booting into recovery mode and updating your system.
   This probably will not work for an Old 3DS downgraded to 2.1.0
   This will BRICK a New 3DS downgraded to 2.1.0
   1. Power off your 3DS by holding down the power button.
   2. Hold L+R+A+Up.
   3. Power on the 3DS.
   4. If you enter safe mode, update your 3DS only if you have an entrypoint for the latest FW version and it is possible to downgrade from it and attempt the downgrade again.

I cant speak for whether or not its been fixed, I would assume not if its still included within the guide.

 

[Deleted User]

What? I remember hearing recovery mode is fixed though.

If you heard it somewhere, you could be right - I'm just stating what I read last. The reasoning I read was pretty complicated so I assumed it was right Something about different encryption keys or whatever and after overwriting the firms the keys wouldn't match, so no boot for you.