Separate names with a comma.
Are you sure people are doing this with our movable.sed and not something else?
Like CTRnand transfers and such.
I've helped several people fix their firmware by pm, and I keep seeing movable.sed with all zeros and missing seed header but with 0x30 keyY and aes-cmac. They're either trying to recover data from their Nintendo 3DS folder or return the setup to prior encryption.
Ok, I'll pass this on to bfm's site admin, deadphoenix.
Hope that's good. We both agreed that a gm9 check would likely be more effective though. Noobs will look at the file weeks later and forget where they got it.
Thank you. It won't stop everyone from making this mistake but at least they've been warned and should reduce this number of incidents. I revamped my Type D9 script for this specific brick, but can't release it. Too much rewrite borked it on current GM9. Grrr.