No don't do it.
You can ctrtranfer directly to 2.1 and make nand backups directly on 11.X
Get Decrypt9
Get backup
Go to 2.1
Install a9lh
Get to 11.2
OK my fault...
No don't do it.
You can ctrtranfer directly to 2.1 and make nand backups directly on 11.X
Or even better: (N3DS only)Get Decrypt9
Get backup
Go to 2.1
Install a9lh
Get to 11.2
OK my fault...
Or even better: (N3DS only)
- Launch OTPless A9LH installer
- Install
- ???
- Profit
http://knowyourmeme.com/memes/profitThe ??? is for seeing if brick or just waiting for its birthday?
That seems interesting. I thought that NFIRM would block older installations with the minversion at first, even in safe FIRM. But now it makes better sense to me. Just need to be 100% sure before doing anything. My irl friend has 11.2 and I was going to do the DSiWare dg with my cfw 2ds, but I decided to wait it out and see if anything were to come up, AND JUST LIKE THIS, it happened!! Amazing, and heavenly. :$$$$I believe this is to do with the safe firm not having 11.x title checks and the exploit to get access to safe-firm is k11. And once in the safe-firm you have arm9 access to the system or at least can downgrade titles as the downgrade block isn't there.
*ninja'd a few times
That seems interesting. I thought that NFIRM would block older installations with the minversion at first, even in safe FIRM.
Actually there's no need to hurry. Soundhax is offline so Nintendo can't force you to update to 11.3. You can sit on 11.2 happily for as long as you want (not like when you need browserhax for homebrew - Nintendo can just force you to update to use the browser).IMPORTANT TO ALL USERS: DG USING THIS METHOD ASAP WHEN IT RELEASES CUZ NINTENDO WILL LIKELY PATCH THIS OUT WITH 11.3 IN A SHORT AMOUNT OF TIME!
That seems interesting. I thought that NFIRM would block older installations with the minversion at first, even in safe FIRM. But now it makes better sense to me. Just need to be 100% sure before doing anything. My irl friend has 11.2 and I was going to do the DSiWare dg with my cfw 2ds, but I decided to wait it out and see if anything were to come up, AND JUST LIKE THIS, it happened!! Amazing, and heavenly. :$$$$
IMPORTANT TO ALL USERS: DG USING THIS METHOD ASAP WHEN IT RELEASES CUZ NINTENDO WILL LIKELY PATCH THIS OUT WITH 11.3 IN A SHORT AMOUNT OF TIME!
That's the rational answer, but just wait for their brother/cousin/dog to "accidentally" update...Actually there's no need to hurry. Soundhax is offline so Nintendo can't force you to update to 11.3. You can sit on 11.2 happily for as long as you want (not like when you need browserhax for homebrew - Nintendo can just force you to update to use the browser).
I meant as in safefirmlauncherhax being patched in 11.3, not soundhax. Also I was just trying to make sure to announce it just in case people may update to 11.3 and not be alarmed beforehand just as a precautionary.Actually there's no need to hurry. Soundhax is offline so Nintendo can't force you to update to 11.3. You can sit on 11.2 happily for as long as you want (not like when you need browserhax for homebrew - Nintendo can just force you to update to use the browser).
Yea you're right in terms of the documentation etc. but does the safe-firm act like a normal firm? In which case it wouldn't have the 11.x nfirm title-downgrade-block [even though that fact is irrelevant as this gives an arm9 access exploit right]Not exactly.
Firmlaunchhax is the arm9 exploit people use in 9.2, but you need K11 access to patch some K11 function calls (I believe this is for the hooks)
https://yifan.lu/2015/01/17/reversing-gateway-ultra-stage-3-owning-arm9-kernel/
(Incase people didn't know)
There is another version of the firmware called SAFE_MODE_FIRM that is used by the system updater where firmlaunchhax has not been patched. We also need K11 access to boot into this mode (I assume). So the idea is too boot into this firmware run Firmlaunchhax then downgrade using the K9 access we now have to 2.1 and install A9LH.
Your reasoning implies safefirm was updated with the antidowngrade feature of 11.0, which it wasn't (its latest update, ignoring the port to N3DS, was to disable OTP in 3.0)Yea you're right in terms of the documentation etc. but does the safe-firm act like a normal firm? In which case it wouldn't have the 11.x nfirm title-downgrade-block [even though that fact is irrelevant as this gives an arm9 access exploit right]
I'm not a expert on the matter but If the downgrade checks were not in place I think you would only be able to install / uninstall titles to the SAFE_FIRM ? Which may be useful I suppose. I don't think there has been to much research into the topic.Yea you're right in terms of the documentation etc. but does the safe-firm act like a normal firm? In which case it wouldn't have the 11.x nfirm title-downgrade-block [even though that fact is irrelevant as this gives an arm9 access exploit right]
Think you've mis-read I implied that it hasn't been updated [the firmlaunchhax of nfirm was patched with 9.5 - safe-firm wasn't]; and was querying the other implications.Your reasoning implies safefirm was updated with the antidowngrade feature of 11.0, which it wasn't (its latest update, ignoring the port to N3DS, was to disable OTP in 3.0)
I see where you are coming from, even without Firmlaunchhax (Assuming the downgrade checks were not in place) we could have *potentially* downgraded/upgraded the necessary titles to enable the Firmlaunchhax then just use safehax.Think you've mis-read I implied that it hasn't been updated [the firmlaunchhax of nfirm was patched with 9.5 - safe-firm wasn't]; and was querying the other implications.
I see where you are coming from, even without Firmlaunchhax (Assuming the downgrade checks were not in place) we could have *potentially* downgraded/upgraded the necessary titles to enable the Firmlaunchhax then just used the exploit.