If you have digital purchases from eShop from before CFW installation, you should avoid opening eShop. It will rebuild your ticket db and remove unsigned cia installation.
Sent from my Nexus 5X using Tapatalk
Basically, it is the Aurora's implementation of ShadowNAND, where Aurora is also one of the contributors.
This is probably a much lighter version of what ShadowNAND would be. It will allow you to get to sig-patched SysNAND without SD card.
Sent from my Nexus 5X using Tapatalk
I mixed a few guides, but essentially by creating an 9.2 emunand, then force an install of 10.3 US update (plus additional files not included in the update) using SysUpdater, then manually deleting the JP titles with FBI. Also, I initially used my O3DS SecureInfo_A, but now I'm using the...
I am currently using the screen-init version of Aurora's A9LH fork. It appears that GW refuses to load my region-changed emunand (JP->US).
Chainloading through Luma works flawlessly with my standard US O3DS and N3DS XL.
It's the screen init version, I think. I turned off the show splash image on no-screen-init option, and it still shows up. Splash brightness control is also not working.
Not the most practical solution, but I've been using NTR savegame plugin to transfer out saves from Gateway to cia or Sky3DS+. I find that it is the most reliable way.
I see... The way I tested it last time was by uninstalling the update using DevMenu (which I installed previously with DevMenu as well) and redownloaded it using the update prompt.
Am I right to say that due to my previous install using DevMenu, that updated my ticket, thus I can download the...
Sorry for bringing this matter back... I think yifanlu's patch is still useful to a certain extent (I have a region-converted JP N3DS to US).
While it's true that I can't download anything from eShop, it still allows me to download update for games from home menu. Basically it allows anything...
Oh shit... I used a separate mSD card to setup, which I promptly reformatted once I'm done... I'm afraid I no longer have the log...
TBH, the reason I'm reporting this is that I was pretty scared when it is showing that message. I thought that it might be flashing the wrong size.
This is what...
It says "Restoring EmuNAND. Size (MB): 1240MB", when in fact I'm restoring a 1.8GB sysNAND using a 1.8GB backup image.
It's not a emuNAND->sysNAND cloning. It's just a pure sysNAND restore. I have confirmed the size of the backup image is in fact 1.8GB, created using EMUNAND9.
EDIT: just...