Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by BlackSwordJon, Mar 4, 2017.
Hello, recently i want to know i to remove completely a9lh on my 3ds?
If you have a pre-A9LH backup then restore a backup with Decrypt9 with the option that does NOT say (keep a9lh). This removed A9LH.
Alternatively I think you can use SafeA9LHInstaller to uninstall it but don't quote me on that.
a) Use Decrypt9 to restore a pre-A9LH backup with the force option.
b) Do a ctr-transfer to 9.2 and use safeA9LHinstaller to uninstall.
c) Boot Luma with option "Patch SVC/service/archive/ARM9 access". Use sysDowngrader from HBL to downgrade to 9.2 using CIA pack. Then use safeA9LHinstaller to uninstall.
Options a and c are best to keep your content with the system. If you simply want to return to stock firmware but still use the system as you do now.
Please note, I don't recommend uninstalling A9LH. If you have an issue troubleshoot it first.
I have a sysNand with no a9lh, is that ok?
Yes, just restore that without A9LH protection turned on using Decrypt9
Imagine, i restore my 3ds (sysnand with no a9lh) with Hourglass option " Sysnand restore (keep a9lh)" does it brick my 3ds?
Using Hourglass9 to restore will not remove A9LH and it won't brick your system either. Unless you are using someone else's NAND for some reason.
Also, can the company Of Nintendo patch the Luma+A9lh in the future?
Short answer: no.
Long answer: Current CFWs have FIRM0/1 protection. Which basically protects the processes being exploited for A9LH. Which basically means that no matter what Nintendo throws at the system, those files simply won't be updated and A9LH will remain untouched.
As well Nintendo will not create a targeted update to remove them because that update will brick New3DS's. The update would run a huge risk of bricking unhacked system as well. This was shown to happen when 3DS's were updated with GatewayCFW (which lacks FIRM0/1 protection.) Old3DS's updated and mostly worked, some reported strange bugs afterwards, but nothing officially proven. New3DS's just straight up bricked.
Shouldn't even recommend option B. Option B seems easiest if pre-A9LH backup does not exist, but ctr transfer breaks DS/DSi functionality and if you have no A9LH, you have no way of fixing it. Selling a 3DS or giving a 3DS to a friend that doesn't play DS/DSi games seems like a bad idea.
If i want to update my 3ds firmware to 11.3, before that, do I have to update my luma 3ds updater?
Ah yes, I forgot this can happen on some instances although I've done a CTRTransfer where it did not break TWL. I gues the appropriate thing would be to reinstall the TWL using the troubleshooting steps prior to uninstall.
Luma updater? Huh? After uninstalling A9LH Luma will be obsolete. You also won't be able to uninstall on 11.3 firm.
Well depending on the method you will end up uninstalling A9LH at either 9.2 (options c and b) or with a prior backup at whatever firmware it will be in <11.3 I suppose.
If you go with option b then ensure to check TWL prior to uninstalling A9LH as I corrected above.
No, i am saying it on 11,2 with a9lh, forget about uninstall
Oh yeah if you don't uninstall, sure A9LH+Luma on SysNAND is safe to update to 11.3, but make sure you update Luma first using the updater as you said.
Which option, Install normal version or latest hourly(b1b81c87)?