Any chance one of the otp.bins from those made its way onto this one that bricked?to be fair, i installed a9lh in over 35 Old3DS and 23 New3DS (OTPless) and this is the only time i got a brick

Is OTP Bricked recoverable? Since he/she can fixed her problem by hardmoding & restore a nand back up.Any chance one of the otp.bins from those made its way onto this one that bricked?
Yes, they've already recovered via hardmod.Is OTP Bricked recoverable? Since he/she can fixed her problem by hardmoding & restore a nand back up.

Giving into paranoia is only holding you behind. It's actually extremely unlikely to brick if you follow the guide fully.And that's why I did not install a9lh

OP already fixed his/her console by hardmod.Giving into paranoia is only holding you behind. It's actually extremely unlikely to brick if you follow the guide fully.
I feel like there has to be some details missing or something that went wrong during the install.
Are you at all able to boot into A9LH payloads? And did you try looking through the troubleshooting guide
https://3ds.guide/troubleshooting

I am glad the OP followed the guide properly and kept a NAND backup.OP already fixed his/her console by hardmod.
I still hold my horse about A9LH is safe. Hardware failure or other factors should also be the cause.
That's why I think that @BlueFox gui has a right to fear.
Atleast, for me, if he/she doesn't use rxtools, his setting is OK and up-to-date.
Although he/she will get less fuction & support.
PS. @BlueFox gui once said that he will only install A9LH only if someone guarantee by giving him another 3DS if he got brick.
So, I don't think you can persuade him with word only.

It's his console. So I still think it's his right to fear or paranoia.I am glad the OP followed the guide properly and kept a NAND backup.
And chances of bricking are still extremely unlikely. Hardware issues are often able to be prevented with the tools provided in the guide and proper preparation. Not to mention the new method has basically made the process beyond stupid easy and safe. It's only paranoia holding someone back from installing A9LH at this point.

They are free do that and I am still free to encourage updating.It's his console. So I still think it's his right to fear or paranoia.
I know that even though if they really brick when following the guide without a miss, hardmod can help them.
Not all of them can do a hardmod (by themselves or by a pro) to fix it with a NAND Back Up.
Everyone have their own reason and their own point of view. That's why I respect his decision.
If his console has a problem because his setting, he can blame no one because this is his choice.
My opinion is, sometimes you should let them walk the path they want.
I know you want to help them get the better option. But, if they really don't want to do it.
It won't be a help, you're bothering them.

Glad you understand what I said.They are free do that and I am still free to encourage updating.
But if they don't want a better option, I will make this my last post about it

my english is horrible in some part i will note understand something, sometime i will start creating many threads for simple questions XDGiving into paranoia is only holding you behind. It's actually extremely unlikely to brick if you follow the guide fully.
I feel like there has to be some details missing or something that went wrong during the install.
Are you at all able to boot into A9LH payloads? And did you try looking through the troubleshooting guide
https://3ds.guide/troubleshooting