Don't tell anybody about the hack and they won't even notice it's there, just be sure to install the latest possible stable versions of GodMode9 and Luma3DS to the NAND before you sell it.
Uh, earlier in the thread, it was said a modded NAND backup cannot unmod a console.System transfer doesn't remove A9LH, and you can back up your NAND and uninstall A9LH easily despite a non-functional top screen.
Hourglass9, though outdated, has very few menu options and someone could probably help you navigate to dump your NAND, and uninstalling A9LH is as simple as running SafeA9LHInstaller as a payload, then pressing Start and inputting the button combo to uninstall A9LH.
Someone on A9LH/willing to read the source code will have to help you with that, though, because I've already forgotten what the Hourglass9 menu+SafeA9LHInstaller button combo looks like to give you precise details.
I think I might not have been clear: the NAND backup is a safety measure in case something goes wrong (which it shouldn't, but you never know)Uh, earlier in the thread, it was said a modded NAND backup cannot unmod a console.
I know System Transfer doesn't remove A9LH.
I'll ask this in the help threads.
Which I don't know the button combo.I think I might not have been clear: the NAND backup is a safety measure in case something goes wrong (which it shouldn't, but you never know)
You can uninstall A9LH using SafeA9LHInstaller itself, and you don't need to be able to see your top screen to be able to do that as long as you know the button combo to uninstall it after you press Start to initiate it.
I understand why you are upset, but please do not take your frustration out on me, especially because I am trying to help you.Which I don't know the button combo.
Yes, that is correct. However, please consider what @Lacius stated in a previous message:so to sumarize is download the firm that matches my model and version renamed to firm0.bin copy it to godmode9 on the virtual drive accept and reboot ?
thanks in advance
If someone tries to remove B9S on a console that, for example, was unbanned in part by generating a new SecureInfo_A, removing B9S will result in a brick. The original SecureInfo_A needs to be restored first.
That's it? Alright, I have the installer, going to try now.I understand why you are upset, but please do not take your frustration out on me, especially because I am trying to help you.
I looked up the source code: As soon as SafeA9LHInstaller boots up, you press Start, then Up, Down, Left, Right, B, A, START, SELECT
After you do that, you can press any button and it should shut off, uninstalling A9LH.
All you need is arm9loaderhax.binThat's it? Alright, I have the installer, going to try now.
--------------------- MERGED ---------------------------
Alright, I have SafeA9LHInstaller.dat, /3ds/SafeA9LHInstaller, and arm9loaderhax.bin. Which one do I use and where do I put it?
Thanks! It worked.All you need is arm9loaderhax.bin
For simplicity purposes, copy it to your SD root so it runs on boot without holding any buttons, but otherwise run it as a Luma payload in SD:/luma/payloads/.
No, don't do that, it's a bad idea and dishonest to the buyer.Don't tell anybody about the hack and they won't even notice it's there, just be sure to install the latest possible stable versions of GodMode9 and Luma3DS to the NAND before you sell it.
That's a pretty big assumption.Sooner or later Nintendo will release an update that breaks CFW and then they will be left with a brick since they don't know to update Luma.
That's why you also send a note explaining the mods with it and put no return address on the package.No, don't do that, it's a bad idea and dishonest to the buyer.
Sooner or later Nintendo will release an update that breaks CFW and then they will be left with a brick since they don't know to update Luma.
If it's possible, then it's unethical to leave CFW on without telling the recipient. Doesn't matter how unlikely it is, just that it is possible.That's a pretty big assumption.
0) Make sure you have a functional NAND backup before you start, in case anything goes wrong.
1) Download the .firm for your matching firmware+model on 3ds.guide's hardmod page: https://3ds.guide/installing-boot9strap-(hardmod)
**If you download and flash the wrong one, you will hardbrick.
2) Rename the .firm to firm0.bin and copy it to your SD card
3) Boot up GodMode9 and copy/paste the firm0.bin from your SD to the SysNand Virtual (S:/ ) drive. Heed all of the warnings.
**The system will warn you several times and also tell you that your super small ~300kbish file is nowhere near the entire 4mb you're replacing. This is fine: Do it anyway (as long as you're 100% sure it's the right file)
4) Reboot and perform a system update to clean your firm1.
care to elaborate on what exactly happened?My n3dsxl is brick. Rip