Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by nooby89, Dec 3, 2016.
So the question is in the title
Its far more common to brick doing the 2.1 ctr transfer
Can you please stop with the . threads and add info in the first post.
He removed it because @Aurora Wright couldn't recreate and therefor track down what was causing the otpless bricks. So Aurora had to push updates to safea9lhinstaller in hopes that no one would brick but each time a new brick was reported. So otpless was deemed unsafe and therefor removed.
Actually make a thread. This isn't the ask section.
And it was removed because of minority of bricks.
That's the second thread with a . ,so , sorry anyway.
There reports bricking a N3DS on 2.1 were because of user error.
There's an explanation about the cause of the OTPLess brick ?
Nobody knows why they are happening. Not even the dev of safea9lhinstaller
Not a certain one.
Just move on from it tbh it got removed
The OTPLess brick can be restore via a harmod ?
But doesn't the installation of A9LH also have a chance of brick ? Or am I missing something
All bricks of ctrtransfer are known. Nobody knows why anyone is bricking with OTPless. Which one sounds better?
It seems the previous OTPLess method carried greater risk idk.
The installation of A9LH in 2.1 is a lot safer and there has been so less report bricks.
If you have a nand backup preotpless which the guide makes iirc
If you power off you 3DS in the 0.00001 second of the installation, maybe it can brick.
— Posts automatically merged - Please don't double post! —
But if you attemp a OTPLess installation on a 2DS/3DS, this will brick ?
Because he (a guy) haves a 2DS and after the installation of arm9loaderhax (he was in 2.1.0-4), his console bricked.
He can't open Luma3DS menu or any payloads... It's like a OTPLess brick.
It can be possible ?
If you tried a OTP-Less install in O3DS, the installer simply told you it didn't work.
You can't otpless on 2ds/o3ds it will error you out. The 2ds brick is likely due to a firm breaking which is really rare but can happen
You could fix that by adding some actual content to the thread.