Nice, thank you mate!Yes, since it's only updating the file that enables screen init.
Nice, thank you mate!Yes, since it's only updating the file that enables screen init.
https://gbatemp.net/threads/tutorial-swap-sysnand-and-emunand-arm9loaderhax-only.415724/Thanks!!!, that worked a treat!!
So if there a more straigh forward guide to follow for swapping nands?, as i just couldnt boot into CFW after i had formatted the sysnand with tinyformat??
So is the best thread to follow if I want to go down that route.Way faster boot time, 100% boot rate, and you can update sysNAND if you want to.
The guides are pretty straightforward IMO, I already got 2 o3DS running ARM9LoaderHax without any problems during the setup. If you follow the guides properly, you won't find major issues IMO.So is the best thread to follow if I want to go down that route.
I've got new 3ds on reinand currently and old 3ds on rxtools, will it be straight forward following a tutorial to convert them to using AL9 hax and aureinand?
Thanks, this worked. Now I do get a screen (for like less than a second) and it disappears.. It's not correct though. I'll check if the splash screen is valid
I'm not sure why this is not working for me. Does a9lh mess it up or something?https://github.com/svanheulen/downgrade_check run this and copy the contents of the log
Thanks going to give this a go, sounds like it will be greatThe guides are pretty straightforward IMO, I already got 2 o3DS running ARM9LoaderHax without any problems during the setup. If you follow the guides properly, you won't find major issues IMO.
Basically, you need to follow this to get your OTP, then this to make your ARM9LoaderHax installer. After that just install it and get AuReiNAND.
Are you using the proper firmware files?It was working fine, but now it gets stuck on the booting image.
Yes, I didn't delete anything.Are you using the proper firmware files?
Do you have the updatedsysnandflag?Yes, I didn't delete anything.
I'll assume no then.What is that?
There's two, right?I'll assume no then.
Just try dragging over all the files again (including that proper firmware files).
firmware.bin and firmware90.bin. Make sure to use the one for your system (o3ds or n3DS).There's two, right?