yes. Restoring sysnand won't touch emunand.Okay, so if i restore my sysnand, my emunand will still be there and i just have to run homebrew to reinstall a9lh with my otp?
yes. Restoring sysnand won't touch emunand.Okay, so if i restore my sysnand, my emunand will still be there and i just have to run homebrew to reinstall a9lh with my otp?
Okay, so if i restore my sysnand, my emunand will still be there and i just have to run homebrew to reinstall a9lh with my otp?
You wereYes.
So why would renaming arm9loader.bin to launcher.dat not work?
I think what i did was renamed stage2_2 to stage 2 so it set the default load as gatewayDunno what went wrong, if its your fault or not, can't examine your broked nand.
You were
And posting 1 word replies is actually against the rules. Don't know how often that rule is enforced... just sayin'.
So why would renaming arm9loader.bin to launcher.dat not work?
Even luma3ds.dat huhFixed.
Well, Launcher.dat's payload is probably somewhere in the middle of the file, not at the start, so, it's extremely unlikely to work.
Even luma3ds.dat huh
Easy Install using safeA9LHinstaller
This allows to have three stage 2 inside nand to load them
using button combinations while powering your console on!
(snip)
Hate to repeat information, but it's easy to get lost in fast moving threads. @liomajor I think it can be confirmed that this works on all Toshiba NANDs and fails on Samsung NANDS. Do you have an idea of what to do to make it work on a Samsung NAND?Using @liomajor Easy Installer and @Kazuma77 alternate stage1 payload to make gateway boot using A I can confirm the following consoles as working
- n3DS EUR v11.0.0-33 + AL9H updated through arm9loaderhax.bin
- 2DS EUR v11.0.0-33 + AL9H updated through arm9loaderhax.bin
Excellent job to both of you for providing such a great solution to the community
So i tried restoring with 4.0 and 3.7.1 i get NAND.BIN errorDifferent offset. I've tried loading Launcher.dat with a boot manager and offset 0x12000 before. It failed.
Hate to repeat information, but it's easy to get lost in fast moving threads. @liomajor I think it can be confirmed that this works on all Toshiba NANDs and fails on Samsung NANDS. Do you have an idea of what to do to make it work on a Samsung NAND?
and @CreAtor135 on the OP, somebody must be confused and thought they were in GW mode instead of CFW. Flash carts do NOT work in GW emunand.
So i tried restoring with 4.0 and 3.7.1 i get NAND.BIN error
What do you mean, i cant even get to the system. When i turn it on its red screen and boots to gateway without pressing any buttonsI might have an idea. Just did an fc/b of my before and after NAND dumps. Found another set of 00s that got overwritten. Another payload if you will. Location is 0x0B21F000 - 0X0B221FFF. Payload is 12288 bytes exactly. What do you make of this, @liomajor?
That's not good. Only way out then is a cart/ROM update (preferably in the 9.3 to 9.9 range -- before the browser checks). Only attempt it with 4.0a. If you try it with 3.7.1 it will brick you.
What do you mean, i cant even get to the system. When i turn it on its red screen and boots to gateway without pressing any buttons
Yeah i dont own a gateway cart, and classic mode just stays at a black screen.So, you can't enter GW mode? You mean, you have no cart. I hope you know someone you can borrow one from. If not, you could be facing a hard mod.
Yeah i dont own a gateway cart,
I dont know, this was a big fucking mistake. I had my 3ds perfect.
Why exactly did you even attempt ANY of this? Why are you in this thread? I can't even...