So, as some of you might know, OTPless has very rare bricks occurring, this doesn't make it unsafe, but I'd like to get to the bottom of it anyway.
The reason must be random ARM9 memory and/or FCRAM corruption in the middle of the MCU reboot, but I have never had it happen myself, so I don't know which is corrupting and how often.
You can help me test this way: get the archive here: https://transfer.sh/15yTbC/tester.zip, copy arm9loaderhax.bin and the "test" folder on the root of the SD (don't use bootloaders), press SELECT and just wait. You won't see anything but it'll keep rebooting and checking that the memory doesn't corrupt, so there isn't any operation which might cause a brick.
The screens won't power on again until there's a failure, to prevent damage.
If it fails, send me the files in the test folder and tell me how many attempts it took for the failure (it'll be printed on screen).
(for GPL compliance: this is just a modified SafeA9LHInstaller source, source.c is included and replaces installer.c).
The reason must be random ARM9 memory and/or FCRAM corruption in the middle of the MCU reboot, but I have never had it happen myself, so I don't know which is corrupting and how often.
You can help me test this way: get the archive here: https://transfer.sh/15yTbC/tester.zip, copy arm9loaderhax.bin and the "test" folder on the root of the SD (don't use bootloaders), press SELECT and just wait. You won't see anything but it'll keep rebooting and checking that the memory doesn't corrupt, so there isn't any operation which might cause a brick.
The screens won't power on again until there's a failure, to prevent damage.
If it fails, send me the files in the test folder and tell me how many attempts it took for the failure (it'll be printed on screen).
(for GPL compliance: this is just a modified SafeA9LHInstaller source, source.c is included and replaces installer.c).
Last edited by Aurora Wright,