You should be able to update just from System Settings.Any help for me i want sys updated for my sd who have not emunand
if is there youtubehax yesYou should be able to update just from System Settings.
Are you using TubeDNS by some chance?
You need to set DNS to auto to get updates working.if is there youtubehax yes
Accessing eshop with a region changed NAND is a PITA.Does the newest update allowed us to go to eshop with region-changed NAND? Still got 007-2001 though. My non-region-changed 3DS sometimes does the same.
It looks complicatedAccessing eshop with a region changed NAND is a PITA.
Here's the guide: https://gist.github.com/yifanlu/e80db121d38aceb8cca0e03cefd5853b
Something's wrong on your end. I installed Windows 10 x64 on purpose to test the x64 makerom.exe and it works fine. I haven't tried x86 makerom.exe on neither x86 OS nor x64 OS. The only thing I'm sure of, x64 makerom.exe works on x64 Windows 10 10586.164. It resides in "\devkitPro\devkitARM\bin\" alongside armips.exe and it's in the PATH's list.It worked, I have 64-bits machine but not worked the 64 bit version, but yes the 32 bit one, that's wierd.
Thanks anyway![]()
Something's wrong on your end. I installed Windows 10 x64 on purpose to test the x64 makerom.exe and it works fine. I haven't tried x86 makerom.exe on neither x86 OS nor x64 OS. The only thing I'm sure of, x64 makerom.exe works on x64 Windows 10 10586.164. It resides in "\devkitPro\devkitARM\bin\" alongside armips.exe and it's in the PATH's list.
Err... is that working for EU?Accessing eshop with a region changed NAND is a PITA.
Here's the guide: https://gist.github.com/yifanlu/e80db121d38aceb8cca0e03cefd5853b
@Aurora Wright
Hi! I managed to resolve my problem with pokémon eclat pourpre (stuck on the GBA splash). I just removed the gba boot splash ({{0xD7A12, 0xD8B8A}, { .type1 = 0xEF01 }, 1}), and it works very well now!!
So, yeah, this gba boot splash can cause problems...
Problem solved since we can now choose if we want that aureinand patch the agb_firm to enable or disable the splash screen on the gba boot (before, we didn't have the choice, and there is an incompatibility with that game and the splash)...That is because youre using a modified rom, the problem is the rom itself, not the patch.
Problem solved since we can now choose if we want that aureinand patch the agb_firm to enable or disable the splash screen on the gba boot (before, we didn't have the choice, and there is an incompatibility with that game and the splash)...
Yep! I agree with you! And disable the splash allows you to save 2 seconds of your life on each boot ^^ So it's an indispensable feature!!Yeah, I know that we can choose now, but the problem is not the splash logo, is the modified rom.
I say this because myself modified a Fire Red Rom a while ago, and messed the boot code in the procces, so it gave me that error, freezing at the boot logo, even on the original hardware (EZFlash 3in1 on a GBA SP kicks the same error).
The only way it works is on an emulator or something that can reproduce GBA roms without BIOS bootscreen.
I fixed it rearranging the boot code of my modified rom, and is per rom, not universal, so the fix should be done by the person who modified the rom you are using.
Hope you see my point.
And hope we don't threat that as a compatibility bug @Aurora Wright , is a romhack problem that should be fixed by the rom modifiers lol.
But anyway, having the option to choose is fine as a temporary fix.
Yep! I agree with you! And disable the splash save 2 seconds of your life on each boot ^^ So it's a indispensable feature!!![]()
bb <3Hahaha, you gotta know that having the bootlogo was useful in the day to do many tricks, and I keep that in the patch as a BIG GBA nostalfag hehe, those were the gold days of handheld gaming, and Nintendo still has the crown in that field with the 3DS (Even we are able to play EVERY pokémon game to date on a single handheld now).