nope, native_firm doesnt break it.I would assume 9.6 will boot in emunand if you manually updated via CIAs and avoid the update relating to NATIVE_FIRM? I would assume 9.6 has an update to NATIVE_FIRM as that's probably the only thing that usually breaks emunand.
Only thing you can do is decrypt the fat16 partition of your current 9.6 emunand (don't worry, it doesn't have to be in a bootable state to do this as long as sysnand still works.
Then use a program like WinImage to open the fat16 image and extract the data, private, and dbs folders. Then backup your 9.6 emunand (because gateway may still release an update to fix it...Unless your on a n3DS, then you're ***ked and it will be a long *** time before you can use that copy of your emunand again.
Then manually update that new emunand to 9.5 via CIA files (as long as you do this while in emunand, you won't get bricked). Then extract and decrypt that copy of emunand (rxTools is your best bet here. Don't bother with the time consuming xorpad stuff.
Then you succesfully transfered your NNID and other info to the newly created 9.5 emunand.
Long story short you'll have to search around and ask questions because I don't have the time to fully explain the process. Needless to say you are in for a bad time. Might be easier for you to just wait for Gateway at this point. Unless you are on a n3DS, then there's a legitimate reason why you should really try and do what I just said.
But for the n3DS you have to wait till Karl/OSKA gets release for it as there currently is no xorpad/decryption homebrew for n3DS nand/emunand yet. So your basically ***ked for awhile.
i did not know that but have tried installing 9.6 native_firm and that is not the one that bricks it. i guess its a mystery for now.Are you sure about that? Installing NATIVE_FIRM CIAs via DevMen/Game Rom doesn't fully install it correctly (which is why updating via game rom/cias on sysnand causes a brick).
The firm1/firm0 partitions are not updated or not updated correctly when updating via CIAs/Game rom.
But for emunand I suppose it isn't much of an issue since it doesn't care about the firm0/firm1 partitions quite as much as sysnand does.
i did not know that but have tried installing 9.6 native_firm and that is not the one that bricks it. i guess its a mystery for now.Are you sure about that? Installing NATIVE_FIRM CIAs via DevMen/Game Rom doesn't fully install it correctly (which is why updating via game rom/cias on sysnand causes a brick).
The firm1/firm0 partitions are not updated or not updated correctly when updating via CIAs/Game rom.
But for emunand I suppose it isn't much of an issue since it doesn't care about the firm0/firm1 partitions quite as much as sysnand does.
i did not know that but have tried installing 9.6 native_firm and that is not the one that bricks it. i guess its a mystery for now.Are you sure about that? Installing NATIVE_FIRM CIAs via DevMen/Game Rom doesn't fully install it correctly (which is why updating via game rom/cias on sysnand causes a brick).
The firm1/firm0 partitions are not updated or not updated correctly when updating via CIAs/Game rom.
But for emunand I suppose it isn't much of an issue since it doesn't care about the firm0/firm1 partitions quite as much as sysnand does.
Not really. You might be able to spoof higher version numbers on older titles to downgrade emunand, but it won't work for sysnand I believe. Besides, you have to be able to boot into 9.6 emunand before you can downgrade if you had thought about trying it this way. You can't do it from sysnand. Gateway doesn't patch sig checks for sysnand/emunand contents, so downgrading emunand like this would probably brick emunand as well because...lol..Gateway. Not sure why they didn't do their patches correctly.
It continues to raise the question of whether or not the Sky3DS is all that blockable. I mean, one could argue that this was primarily a feature update and not so much an antipiracy update, but they still stuck their generic message in there implying that they did what they could to hold pirates back even further. Of course, we have only had the Sky for all of about six-ish months, but I mean, if the Sky3DS was simple to block or even a little complex, I think even Nintendo would have figured it out after about half a year.
You likely can't downgrade it this way even with Gateway as version spoofing likely breaks the file signetures of the installed firmware files. Gateway doesn't patch sig checks for firmware files. So even emunand will probably be bricked if you tried this.
You can't do anything with them if they aren't in CIA format because CIA format is the container format DevMen uses to install new content. The files 3DNUS downloads are just CXI files with a certificate file. The CXI file gets placed into a CIA container. You can't install it properly without them being in CIAs.
He probably installed each CIA one at a time and rebooted. Once he got the first brick that's it. Though his list is quite a bit shorter then the full list of updated CIAs. I might try and narrow this down further. I plan to backup my emunand before I start. Then I will install just NATIVE_FIRM (and do it proper using the special homebrew I have). If that doesn't brick I will install the safe list. Confirm that it still works and then make a separate backup of that.
Then I will install what's remaining on the list one at a time and after many reboots I will eventually run into one that bricks it. Then I will note down all the ones I had installed prior ot that brick, restore my second backup, install those. Make a new backup overwriting the second backup, then skip the CIA that bricked and continue along until it bricks again. Rinse and repeat.
)
