Homebrew Can't decide between Arm9loaderhax and Menuhax!?!

[perspex]

arm9loader seems more for 3ds enthusiasts who want complete control of their system. As a guy who just wants to play roms and occasional online play i think menuhax and luma3ds is a much easier and safer option(safer in the sense of the installation process).

 

[RemixDeluxe]

Once you have your OTP you'll always be able to (re)install A9LH, getting OTP however won't be possible on the latest firmware once they block the hardmod/DSiWare downgrade methods. The exploit itself isn't patchable without a new hardware revision but without OTP it won't do much good.

arm9loader itself can be patched and you arent guaranteed to be safe throughout future firmware updates. Thats the part your misunderstanding, whether you have your OTP still or not is besides the point.

 

[Ironknight]

arm9loader itself can be patched and you arent guaranteed to be safe throughout future firmware updates. Thats the part your misunderstanding, whether you have your OTP still or not is besides the point.

Theres a simple solution: Wait until a hardmodded user confirms its safe before updating.

 

[RemixDeluxe]

Theres a simple solution: Wait until a hardmodded user confirms its safe before updating.

You still need to proceed with caution with each passing firmware update and always make a backup.

When a new update happens, check in with the temp and get at least 2-3 confirmations of it being safe.

 

[Ironknight]

When a new update happens, check in with the temp and get at least 2-3 confirmations of it being safe.

Thats what I was saying.

 

[The Catboy]

A9LH, trust me.
Menuhax is simpler to set up, but it's basically crap. Once you get A9LH set up, you won't be disappointed.

 

[perspex]

im actually in a funny situation here, i'm deciding on all this. When im not really sure what fw my new 3ds xl is gonna be on. I called the ebay dealer and got the serial number, its QW4066 US model black, after some research i found a QW4060 and QW4067 blacks on fw 9.9, but there was a QW4070 and QW4072 that had fw 10.7. Im not sure, if im gonna get a 9.9 console or a 10.7 console, it'll mostly be 9.9 i think.

 

[fikatr]

if you want to accidentally update sysnand and got fucked use menuhax

 

[The Catboy]

arm9loader itself can be patched and you arent guaranteed to be safe throughout future firmware updates. Thats the part your misunderstanding, whether you have your OTP still or not is besides the point.

Actually that's mostly incorrect. Current FIRM0/1 protection methods have made it almost completely impossible to patch out A9LH through a simple firmware update. It would basically fall onto human error (such as running your CFW without FIRM0/1 protection turned on or lacking a FIRM0/1 protection) to allow Nintendo patch out A9LH, which would result in a brick. Of course, since all CFW running on A9LH have FIRM0/1 protection, it's safe to say that Nintendo can't patch it out through a simple update.

 

[RemixDeluxe]

Actually that's mostly incorrect. Current FIRM0/1 protection methods have made it almost completely impossible to patch out A9LH through a simple firmware update. It would basically fall onto human error (such as running your CFW without FIRM0/1 protection turned on or lacking a FIRM0/1 protection) to allow Nintendo patch out A9LH, which would result in a brick. Of course, since all CFW running on A9LH have FIRM0/1 protection, it's safe to say that Nintendo can't patch it out through a simple update.

Yep, this is why I thank my lucky stars every night we have talented devs like @Aurora Wright to keep everything in check every step of the way and every passing firmware update. Even patched back in svc for downgrading on 11.0 (never know if you need it again for whatever reason)

 

[The Catboy]

Yep, this is why I thank my lucky stars every night we have talented devs like @Aurora Wright to keep everything in check every step of the way and every passing firmware update. Even patched back in svc for downgrading on 11.0 (never know if you need it again for whatever reason)

It also helps that Nintendo just can't update to remove it.
There's a reason that updating without FIRM0/1 protection results in a brick. And that reason is because each A9LH is custom made for each system. Which means, Nintendo just can't make an all-in-one removal update to get rid of it. Trying to would simply result in bricking the targeted system and could even result in bricking system that don't even have A9LH installed. It's just too risky an update to take for Nintendo.
The only way for them to update is for them to ask you to send them your OTP and create a removal tool that way. Which is again, something they just can't do.
Not to mention recent mini-CFWs like ShadowNAND and LumaNAND (not the official name) have added another layer of protection to the system. Nintendo is pretty fucked with A9LH, which is why I heavily recommend going with it.

Setting it up maybe a song and dance, but it's totally worth the effort for that much protection.

 

[DarkSynopsis]

I suggest trying out Arm9loaderhax on your O3DS once you have your N3DS setup to where you like and if from there you decide it has its advantages do it on the N3DS, I ran through the process on my old 2DS after having Menuhax setup for months and all worked out fine since then I've done my N3DS and 2 O3DS without any problems.

Assuming you are familiar with downgrading which is likely its not really that different getting A9LH setup now, I mean Menuhax already means you are on Step 4 of the guide, like halfway there!

I mainly wanted to get A9LH installed so GBA VC didn't require installing to Sys/Emu, and that Menuhax load time was killing me wanting to boot up DS titles.

 

[Swiftloke]

Actually that's mostly incorrect. Current FIRM0/1 protection methods have made it almost completely impossible to patch out A9LH through a simple firmware update. It would basically fall onto human error (such as running your CFW without FIRM0/1 protection turned on or lacking a FIRM0/1 protection) to allow Nintendo patch out A9LH, which would result in a brick. Of course, since all CFW running on A9LH have FIRM0/1 protection, it's safe to say that Nintendo can't patch it out through a simple update.

Funny thing. Gateway doesn't have FIRM protection.

 

[perspex]

arm9loader seems the best way to go, but its just the fear you know...im already spending a lot of dough getting another 3ds, that too being from india im ending up paying around 270$ for something thats worth 200$. The guide says its more complicated for new 3ds, cos it was never designed to go into 2.1.0 fw, if something goes wrong and i end up with a 270$ potato...im gonna lose it.

 

[Wojton]

Getting OTP however won't be possible on the latest firmware once they block the hardmod/DSiWare downgrade methods.

Unless Nintendo employees visit every hardmod user in the world and unsolder the wires from their NAND chip, I don't see that happening.

 

[Swiftloke]

Unless Nintendo employees visit every hardmod user in the world and unsolder the wires from their NAND chip, I don't see that happening.

Fixing the known-plaintext exploit, meaning we can't write native_firm even with a hardmod.

 

[Wojton]

Fixing the known-plaintext exploit, meaning we can't write native_firm even with a hardmod.

Well, I stand corrected then. Good to know this can happen.

 

[The Real Jdbye]

Unless Nintendo employees visit every hardmod user in the world and unsolder the wires from their NAND chip, I don't see that happening.

Easy. They just have to update the minimum kernel version in the system titles and the system will brick if FIRM is downgraded.

Fixing the known-plaintext exploit, meaning we can't write native_firm even with a hardmod.

That could also happen, but the thing I mentioned is more likely to happen first I think.

 

[The Catboy]

Funny thing. Gateway doesn't have FIRM protection.

Which is why it bricks and why I call Gateway, "Brickwait."

 

[Swiftloke]

Which is why it bricks and why I call Gateway, "Brickwait."

Exactly.
Edit: 1200 posts woo