What do you mean? What actually happens?I found a bug on 0.11 version, on the screen to enter the pin. Every time we tap on a key (like A, B, X, Y L, R etc) the screen «bug».
What do you mean? What actually happens?I found a bug on 0.11 version, on the screen to enter the pin. Every time we tap on a key (like A, B, X, Y L, R etc) the screen «bug».
"If you have neither sha.bin nor a NAND backup
If you have neither of these files then unfortunately your 3DS is essentially bricked, as you will not be able to bypass the PIN lock unless you can somehow remember your PIN. This is why the installation instructions stress the need to back up both of these files safely during 3DSafe installation."
This is not true by the way, because A9LH Stage 2 is not encrypted so you can just replace it with an hardmod
This is mostly to make it inconvenient for a thief if they happened to steal a 3DS which had a problem mounting CTRNAND for some reason. They would be able to re-flash a different payload, but wouldn't be able to do anything else until they did this. This means that if somebody stole a 3DS in such a condition, they would only be able to use it if they knew about 3DS hacking.I didn't test it but I noticed in the code that if 3dsafe is unable to mount the CTRNAND partition it will boot safearm9loaderhax installer and let you install a new a9lh fork.
This behaviour seems strange though, why not just boot a payload from SD?
I don't think anyone using 3dsafe is concerned about anyone performing a hardware attack on the console to gain entry, mind.
@Aurora Wright
True. I'm not sure how to go about describing that, since it could enable a hacker to disable the PIN lock on a stolen 3DS.
That's actually a really good idea. It does, however, introduce an extra burden on the user during installation (i.e. to encrypt the payload first).As a suggestion;
Encrypt stage2 with the OTP hash when installing it with safea9lhinstaller, and stage1 decryts with the same hash on boot.
Or perhaps perform a hash over stage2, encrypt the stage2 hash with the OTP hash, and use that to verify the integrity of stage2.
This is an unlikely scenario though, I think anyone who knows how to NAND mod a console and inject a stage2 payload into NAND won't need to steal one
That's actually a really good idea. It does, however, introduce an extra burden on the user during installation (i.e. to encrypt the payload first).
Also true. I could bundle the modified version with the release, and the built-in one could handle it too (though it would need to know whether the user was installing a 3DSafe payload). I'll consider this for a future release.I'm sure a minor mod to safea9lhinstaller could do either of those things at install time.
I can answer this.I'm not sure why only minor FIRM downgrades are possible (11.0 -> 10.4 but not 11.0 -> 9.2).
I can answer this.
It has to do with how the home menu actually checks for the kernel version. There are three parts of the kernel version - MAJOR VER . MINOR VER - REVISION VER. If the Minor Ver is lower than the required Minor Ver, the application won't boot. You can install a 10.4 nfirm (2.50-11, rev might be wrong) because the minor ver (50) is the same as the required minor ver by the home menu. However, the 9.0.0 nfirm (2.46-0) has a lower minor version than the version required by the 11.1 home menu.
I don't think that has to do with this because the same thing happened to me before I used this. Custom themes are probably the issue.Sometimes when coldbooting OR rebooting, the screen stays black on the HOME Menu for around 5 seconds then cuts back on. I'm using 0.10 on a USA o3DS.
How do you know it's on the home menu if the screen is black?Sometimes when coldbooting OR rebooting, the screen stays black on the HOME Menu for around 5 seconds then cuts back on. I'm using 0.10 on a USA o3DS.
I can test this either tonight or tomorrow night with an 11.0.0-33U USA O3DS. Most likely tonight.I did think about this and considered making it so you had to enter the old PIN before changing it. The problem here is that if you forget the PIN, you can bypass it but then wouldn't be able to change it. To be honest, you shouldn't be walking around with your OTP on your SD card anyway so this problem should never occur. If you're bypassing the PIN, you should then be changing it and immediately deleting the OTP anyway. If you leave it on the SD card, 3DSafe becomes pointless whether you can change the PIN or not.
@gamesquest1 @metroid maniac @ghostpotato @Skyshadow101
I hope you don't mind me tagging you all, but you were all kind enough to report back your test results. Before going to 1.0, I've just uploaded one more beta version. If you could give this a try I would really appreciate it. This version removes the OTP bypass and replaces it with SHA bypass. So, if you could try the following and let me know the outcome I would be really grateful:
- Update to 3DSafe 0.11
- Put otp.bin on the root of your SD card and verify that it no longer bypasses the PIN lock
- Enter 3DSafe settings
- Press L to dump the sha.bin to the root of your SD card
- Reboot your 3DS and check it bypasses the PIN lock
- Delete sha.bin from the SD card, reboot, and ensure the bypass no longer occurs
If you could let me know about each of those steps and whether each worked I would really appreciate it.
Why would I list it on 3DSafe's thread if the problem has nothing to do with 3DSafe...?I don't think that has to do with this because the same thing happened to me before I used this. Custom themes are probably the issue.
I can hear the sounds and even start an application before I actually see the screen. Maybe this has something to do with wonky screeninit code carrying over into the actual OS?How do you know it's on the home menu if the screen is black?
It happened to me a lot before I used this, so it could just be a normal problem with some versions of arm9loaderhax.Why would I list it on 3DSafe's thread if the problem has nothing to do with 3DSafe...?
And no, this happens without an SD Card inside in the first place.
Even if it was a theme, it would permanently hang, not just go for a few seconds then pop back on.
Well weird haha. I used every single version of it, Delebile's, Aurora v2/v3, ShadowNAND, and this one.It happened to me a lot before I used this, so it could just be a normal problem with some versions of arm9loaderhax.