Homebrew [PSA] SafeB9SInstaller will fail if the 3DS ran CTRTransfer 9.2 previously.

[pixelmasher]

Edit:
- CTRTransfer 9.2 to sysnand
- No A9HL.
- No Luma3DS
- Using SafeB9SInstaller 0.0.6

Did you format your SysNAND after the CTRTransfer?

 

[linuxares]

Well since a CTRTransfer doesn't involve the console unique files, that's probably the issue.
You aren't suppose to use a CTRTransfer image more than for that time being.

https://www.reddit.com/r/3dshacks/comments/4zhe4a/ctrtransfer_what_it_is_and_why_it_works_and_why/

 

[DestinySky]

Did you format your SysNAND after the CTRTransfer?

Yes, I did.

 

[linuxares]

Did you keep your Nand backup before the downgrade?

 

[DestinySky]

Did you keep your Nand backup before the downgrade?

No.

 

[linuxares]

No.

Well then, got any game with 11.X on it?
http://www.3dsdb.com/ - try using this website to look up what games you own that can upgrade that 3DS.

 

[DestinySky]

any games with > 9.2 update should works too yea?

 

[The Catboy]

What kind of proof?
A screenshot?

Like multiple tests to with the same results, error logs, multiple users experiencing the same error, etc.

 

[DestinySky]

Like multiple tests to with the same results, error logs, multiple users experiencing the same error, etc.

Well, it happened on 3 x 3DSes of mine.
The other 3DS that is downgraded via sysdowngrader instead of CTRTransfer works fine.

 

[The Catboy]

snio

Ah, I am replying on my phone, so please excuse me if I didn't read that, just trying to help. Right, so that does seems pretty decent evidence to say there has to be a connection. You might want to bring this to the attention of Plailect. That way if this can be replicated, it can be added to the Guide

 

[DestinySky]

@Plailect
Any idea?

 

[Plailect]

1. This error is almost certainly unrelated to any kind of CTRTransfer as that error is unrelated to the CTRNAND partition.
2. This error is caused by an inability of SafeB9SInstaller to access the SHA register (a hash of the first 0x90 bytes of the encrypted OTP), which is needs to decrypt the secret sector in order to restore it to stock.
   
3. I'd wager this error is due to some kind of non-standard or old arm9loaderhax implementation being installed.
4. This error can always be fixed just by placing the aeskeydb.bin from Updating to boot9strap in the /boot9strap/ folder on your SD card, then running the installer again. This fix works because this aeskeydb.bin contains the OTP key and IV from Boot9 to allow us to encrypt and hash the copy of the first 0x90 bytes of the decrypted OTP that Boot9 places in ITCM on boot. This means we do not need access to the SHA register at all.
5. Bonus: This also means that having Boot9 allows us to install A9LH without downgrading to 2.1.0. This is, of course, made irrelevant by the fact that sighax and boot9strap exist.

From Updating to boot9strap:

 

[Drakia]

1. This error is almost certainly unrelated to any kind of CTRTransfer as that error is unrelated to the CTRNAND partition.
2. This error is caused by an inability of SafeB9SInstaller to access the SHA register (a hash of the first 0x90 bytes of the encrypted OTP), which is needs to decrypt the secret sector in order to restore it to stock.
   
3. I'd wager this error is due to some kind of non-standard or old arm9loaderhax implementation being installed.
4. This error can always be fixed just by placing the aeskeydb.bin from Updating to boot9strap in the /boot9strap/ folder on your SD card, then running the installer again. This fix works because this aeskeydb.bin contains the OTP key and IV from Boot9 to allow us to encrypt and hash the copy of the first 0x90 bytes of the decrypted OTP that Boot9 places in ITCM on boot. This means we do not need access to the SHA register at all.
5. Bonus: This also means that having Boot9 allows us to install A9LH without downgrading to 2.1.0. This is, of course, made irrelevant by the fact that sighax and boot9strap exist.

From Updating to boot9strap:

OP said those consoles never had a9lh on them though, he stopped at the CTRTransfer to 9.2 for some reason

 

[Plailect]

OP said those consoles never had a9lh on them though, he stopped at the CTRTransfer to 9.2 for some reason

Wut. That error should only ever trigger while on a9lh. If a9lh isn't defected, it skips that all together. Must be a bug that it's detecting a9lh being installed when it isn't...

 

[OrGoN3]

As per title,
SafeB9SInstaller will error out and unable to proceed.

Error:

Crypto Status - FIRM crypto fail

Edit:
- CTRTransfer 9.2 to sysnand , then formatted the sysnand using the 3DS Setting Format System Memory.
- No A9HL.
- No Luma3DS
- Using SafeB9SInstaller 0.0.6

Why not just finish the guide, how it originally was, for A9LH? Once A9LH is on there, do a system update, get all of the right files back on there and then do B9S.

Are you using Plailect's guide? If so, where did you start and which entrypoint were you using? If you say 2xrsa I'm leaving.

 

[DestinySky]

Why not just finish the guide, how it originally was, for A9LH? Once A9LH is on there, do a system update, get all of the right files back on there and then do B9S.

Are you using Plailect's guide? If so, where did you start and which entrypoint were you using? If you say 2xrsa I'm leaving.

Some 3ds using browserhax and some using menuhax to boot to homebrew channel and then run Decrypt9's Auto CTRTransfer to v9.2
These are super old 3ds, not using any guide - Just entrypoints -> homebrew channel -> Decrypt9's Auto CTRTransfer to v9.2

 

[Jayro]

I think OP needs to start at the 9.2 section of the guide, and begin there.

 

[OrGoN3]

Some 3ds using browserhax and some using menuhax to boot to homebrew channel and then run Decrypt9's Auto CTRTransfer to v9.2
These are super old 3ds, not using any guide - Just entrypoints -> homebrew channel -> Decrypt9's Auto CTRTransfer to v9.2

Ok, so as I said, finish going A9LH and then go B9S. *hax entrypoints don't work 100% of the time. Good luck!

 

[DestinySky]

Well, if I can go b9s directly without doing a9hl, I rather do so.
I'm exploring if I can skip a9hl.

 

[Plailect]

Well, if I can go b9s directly without doing a9hl, I rather do so.
I'm exploring if I can skip a9hl.

Just put the key db in the boot9strap folder like I said and the installer will work.