Yes it does in the plailect bibleDoes this OTPless method is in the Plailect's guide?
Yes it does in the plailect bibleDoes this OTPless method is in the Plailect's guide?
Good that you're careful, but it makes more sense to me, if climbing a mountain, to just put on a safety harness instead of saying, "I'm the special, careful one, different from all the countless others, who won't slip". Maybe you are, but is saving 30 seconds not putting on the harness really worth the risk of the fall to your death?I know, I've had it happen, which is why I always double check the firmware version even if I've loaded it from emunand, and if it appears to reboot while I'm in system settings I shut down and start over. I'm OCD about making sure I don't update my sysnand
well I know to some people having a bricked console would be a major hit to their income, which is why I would prefer the risk be acknowledged and everyone be given a honest warning rather than implying that it's only idiots and noobs with crap sd cards that brick as it's not, it's just a random very very rare bug that can affect anyone running the installer even if they did everything correctly.........that said there is no reports of bricks with 2.6.7 so far, but with it being a rare bug it may be a while before we get another hit if it's not fixedI find this quite interesting.Most of everyone getting bricked with the otpless method are people who have more than 1 N3ds and can afford to brick,while people who are sticking to menuhax probably don't want to brick there only 3ds they own.Not everyone is made of MONEY$$$,so it's still pretty smart to go the cautious route or accept the risks before they happen.
There will be nothing stopping me from installing A9LH when I actually need it, and until then the only risk I run is updating, which won't happen, and if I were careless enough to make that mistake, would you really recommend I install A9LH myself? Why should I spend an hour and half installing something that I don't need yet, and may in fact never need, and which could lead to a possible brick even if I do everything correctly?Good that you're careful, but it makes more sense to me, if climbing a mountain, to just put on a safety harness instead of saying, "I'm the special, careful one, different from all the countless others, who won't slip". Maybe you are, but is saving 30 seconds not putting on the harness really worth the risk of the fall to your death?
If you want to take the cautious route, you don't downgrade in the first place. There is more risk of something going wrong and you don't have a backup...I find this quite interesting.Most of everyone getting bricked with the otpless method are people who have more than 1 N3ds and can afford to brick,while people who are sticking to menuhax probably don't want to brick there only 3ds they own.Not everyone is made of MONEY$$$,so it's still pretty smart to go the cautious route or accept the risks before they happen.
Correct.Once you downgrade there is no going backIf you want to take the cautious route, you don't downgrade in the first place. There is more risk of something going wrong and you don't have a backup...
May be until aurora-san found the cause of brick problem.Sadly, OTPless a9lh install method seems to have been completely removed from Plailect guide. I would have preferred to have been given the option to go OTPless or 2.1.0 ctrtransfer
Sadly, OTPless a9lh install method seems to have been completely removed from Plailect guide. I would have preferred to have been given the option to go OTPless or 2.1.0 ctrtransfer
Sadly, OTPless a9lh install method seems to have been completely removed from Plailect guide. I would have preferred to have been given the option to go OTPless or 2.1.0 ctrtransfer
The brick were completely random and every attempt to fix them only caused more bricks. The dev can't pin down (or recreate) the problem so they have to push random updates and see if it works.Why the hell was it removed for only a small number of bricks?
But it's still a small number of bricks, not really enough remove it from the guide.The brick were completely random and every attempt to fix them only caused more bricks. The dev can't pin down (or recreate) the problem so they have to push random updates and see if it works.
Its still better to know what and how bricks are happening (sleep mode on 2.1 ect) then to not have a clue how bricks are happening and have to push updates that have not been tested.But it's still a small number of bricks, not really enough remove it from the guide.
But it's still a small number of bricks, not really enough remove it from the guide.
That's complete bullshit actually. Every form of hacking comes with a risk and I go into every hack full knowing that this might end up breaking my system. That's the cost of hacking.If it ever happened to you, you'd never go OTPLess install again.
And it happened to a flood of people compared to the massively more likely standard user error issues of other bricks.
Why the hell was it removed for only a small number of bricks?
Seriously, there's been more bricks related to the 2.1 method than the OTPLess method. There's no reason to remove with so few bricks. It's only adding unneeded panic.
Still a brick, still worth noting when it happens.How many people have actually bricked from N3DS 2.1 ctrtransfer? The only ones I've heard of downgraded to 2.1 and then left their system in sleep mode on 2.1.