So, is this the currently accepted and canon O3DS downgrade-to-2.1 procedure?
Did I miss anything?
- Make a sysNAND backup with Decrypt9 or Gateway.
- Install the good ol' 4.x mset pasta in mset.
- Use Gateway launcher to downgrade to 4.x.
- Clone sysNAND to a new emuNAND.
- Use sysUpdater to downgrade to 2.1 on the emuNAND.
- If the downgrade succeeded, write the emuNAND to sysNAND (after stitching the NCSD header back in). Else, rewrite the emuNAND and retry until you no longer have a partial.
- Use ARM9 stuff (Cubic Ninja is public, apparently the cakes guys are working on something based on 2.1 spider with no success) to dump the OTP region to SD card.
- Use ARM9 stuff to restore a sysNAND backup to get back to the original firmware. Alternatively, use ARM9 stuff to implement minipasta on 2.1 and run sysUpdater to get back (which must be recompiled to have matching kernel version stuff, and even then it's dubious whether ctrulib things really will work on 2.1).
SHA-256(buf=0x10012000, size=0x90). So if you wanna brute-force 0x90 bytes of stuff to get the right SHA-256 hash, be my guest. (Pro tip: 16 bytes are currently only feasible with quantum computers, 32 bytes is considered quantum-proof right now)
Naw, you don't have to downgrade emunand it will not load even it is successful. As for downgrading to 2.1 I pasta and sysupdater from 9.x to 4.x to 2.1. The downgrade failed on the 2.1 install somewhere in the middle just remove the ad and boot, it should load.then pasta and sysupdater again.
Last edited by Zyrmkel,









