Ahhh memoriesI still have your otp sitting on a drive somewhere, and maybe even the built 3dsx.
Ahhh memoriesI still have your otp sitting on a drive somewhere, and maybe even the built 3dsx.
I'm confused here...only if we have the OTP, or the hash of the first 0x90 bytes.... and since it would patch this method, you'd have to go back to the old way of obtaining the OTP.... it has other implications as well, which I won't mention here
arm9loader is bundled with FIRM, so we have to change all of FIRM, not just arm9loader (since each section is hashed, and the hashes are signed). Also, not to mention, if they did re-encrypt the secret sector, we'd need to obtain our OTP by DGing to 2.1 and then re-encrypting with aes-ecb to use older versions of FIRM (since the arm9loader there would be expecting ECB, and end up decrypting garbage keys from NAND), that would mean going back to 9.2 wouldn't be possible and we'd need a whole new arm9 exploit to do the process of downgrading to 2.1.I'm confused here...
If the arm9loader is unencrypted, why can't we just write the older version? Unless you're talking about a hardware revision? Or a new version of arm9loader that would re-encrypt the secret sector so that we can't swap keys?
Ah, that makes sense. Thanks for taking the time to explainAlso, not to mention, if they did re-encrypt the secret sector, we'd need to obtain our OTP by DGing to 2.1 and then re-encrypting with aes-ecb to use older versions of FIRM (since the arm9loader there would be expecting ECB, and end up decrypting garbage keys from NAND), that would mean going back to 9.2 wouldn't be possible and we'd need a whole new arm9 exploit to do the process of downgrading to 2.1.
don't forget when you had to build your own installers, or have others build them for you (). I did a9lh on all of my systems when you had to do that.
Are we playing this game?
I did arm9loaderhax before any public releases with a custom key by manually hex editing/encrypting NAND.
Hands down.If we're really playing this game, I found the OTPless vuln :^)
I know you really don't want to but, WAIT. It's still called UnsafeA9LHInstaller for a reason.Hands down.
I see AuroraWright has added support for the New 3DS OTP-less installation on her SafeA9LHInstaller. Well, that's a go signal for me to use the latest Beta release of UnsafeA9LHInstaller.
Don't you think the risk in using this is just as risky as downgrading a N3DS to v2.1? In what I can see, I think this is much safer than doing ctrtransfer to v2.1. There's risk during the transfer proccess, there's risk after the downgrade has been made. Heck, it's even written in BOLD on Plailect's guide. I don't think a person is stupid enough to brick by pressing only one button. Then again, I still haven't tried this yet so I might be that stupid one to brick with a press of a button. hahaI know you really don't want to but, WAIT. It's still called UnsafeA9LHInstaller for a reason.
You are comparing Monster trucks with lemons there. I suggest to wait. No hardmod, no hypebrick. Just wait.Don't you think the risk in using this is just as risky as downgrading a N3DS to v2.1? In what I can see, I think this is much safer than doing ctrtransfer to v2.1. There's risk during the transfer proccess, there's risk after the downgrade has been made. Heck, it's even written in BOLD on Plailect's guide. I don't think a person is stupid enough to brick by pressing only one button. Then again, I still haven't tried this yet so I might be that stupid one to brick with a press of a button. haha
I believe it's called "risky" since not a lot of people haven't tested this yet. Unlike the one on the guide, which has been tested by a lot users. They are just being cautious to avoid newbies getting bricked if somewhat they fucked up somewhere.Don't you think the risk in using this is just as risky as downgrading a N3DS to v2.1? In what I can see, I think this is much safer than doing ctrtransfer to v2.1. There's risk during the transfer proccess, there's risk after the downgrade has been made. Heck, it's even written in BOLD on Plailect's guide. I don't think a person is stupid enough to brick by pressing only one button. Then again, I still haven't tried this yet so I might be that stupid one to brick with a press of a button. haha
I know it doesn't require hardmod at all. But if you failed and bricked your unit (or something like that) while doing the process, since it's still called "Unsafe", you have to do a hardmod to restore your NAND dump.You don't need a hardmod, it's safe.