Hacking Who hasn't yet installed arm9loaderhax? Why?

[Joom]

I think one of the best reasons to move away Menuhax and EmuNAND is to cut down on SD I/O to increase its lifespan and read speeds. Not to mention it'd be kind of easy for Nintendo to block EmuNAND usage by implementing a way to check the SD for that partition and then performing some kind of shenanigans.

 

[TimX24968B]

I think one of the best reasons to move away Menuhax and EmuNAND is to cut down on SD I/O to increase its lifespan and read speeds. Not to mention it'd be kind of easy for Nintendo to block EmuNAND usage by implementing a way to check the SD for that partition and then performing some kind of shenanigans.

true, but then again, it has been proven that A9LH can be blocked/tampered with by nintendo, yet it hasn't yet.

 

[Joom]

true, but then again, it has been proven that A9LH can be blocked/tampered with by nintendo, yet it hasn't yet.

A completely new hardware revision would be required in order to resolve A9LH. If otherwise I'd like to know.

 

[TimX24968B]

A completely new hardware revision would be required in order to resolve A9LH. If otherwise I'd like to know.

I remember hearing a while back someone mentioned it, yet updates may have been put in to prevent it.

EDIT: posted in my post below is where i saw it.

 

[xtheman]

I remember hearing a while back someone mentioned it, yet updates may have been put in to prevent it.

It is 100% possible to patch a9lh (and technically any exploit) with an update but as hard as it is it isn't worth nintendo time. They likely would worry more about exploits that work on latest firmware like cubic ninja

 

[TimX24968B]

It is 100% possible to patch a9lh (and technically any exploit) with an update but as hard as it is it isn't worth nintendo time. They likely would worry more about exploits that work on latest firmware like cubic ninja

A completely new hardware revision would be required in order to resolve A9LH. If otherwise I'd like to know.

yes. found this old post a while back:

First off, it would take two or more system updates to do it safely. First update they have to update NATIVE_FIRM give arm9 new functions for writing to that region of NAND and verifying it. Then actually creating the secret sector. Since Arm9Loader isn't installed yet, having secret sector present at this stage has no impact on the system as it's not used.

Then the second update will update Native_Firm to the new Arm9Loader version of it and the FIRM partitions would be updated accordingly.

If they can't create secret sector in the same go in the first update, then they'd do it in a second update and move off the Arm9Loader install to the third update.

In theory that would work. but Nintendo seems reluctant to do it.

 

[sniper_x002]

I don't use dsiware, and I only use the retroarch gpsp for gba emulation since it runs near perfect with pokemon emerald. Never had it crash (or played long enough for it to crash).

gpsp should be fine. I'm only talking about gba injection.

 

[metroid maniac]

yes. found this old post a while back:

I think at this point the most sensible approach for Nintendo to take is just to cease using arm9loader altogether

Strip arm9loader from the N3DS FIRM package and just start Kernel9Loader directly from the bootrom. Arm9loader provides no security for them any more.
And nuke the secret sector, just zero it out on every 3DS that happens to have it in its NAND on first boot. No legit consoles will be using it anymore so it'll be safe to remove and all of the "pirates" will now be enjoying bricks if they update naively, since CFWs won't know to patch this new function. Also has the advantage of making downgrades harder since no old N3DS FIRMs will boot on a N3DS unless a secret sector is regenerated from OTP data.

So I think it is possible for Nintendo to kill a9lh with a single update, though CFW devs will catch on quickly and work around it.
But then again, that would require Nintendo to put effort into their security.

 

[Red_Alive]

the procedure is too complicated and the Plailect Guide doesnt make it easier cause its too confusing especially to navigate through

no offence to the creator(s) , they did a fantastic job

 

[John256145]

You owned your 3DS for 4 years. You named it Brad. You loved Brad. And then you bricked him. You two had been through everything together. 2 firmware downgrades, 3 repairs, you're like "Nothing can replace Brad." Then Nintendo calls. And you break into an empty wallet.

I hope anyone gets where I'm going with this.


Menuhax is fine for me, I'm not risking its life again.

 

[xtheman]

You owned your 3DS for 4 years. You named it Brad. You loved Brad. And then you bricked him. You two had been through everything together. 2 firmware downgrades, 3 repairs, you're like "Nothing can replace Brad." Then Nintendo calls. And you break into an empty wallet.

If you bricked before you have a hardmod and you can make a backup before installing a9lh then if you brick you can unbrick.

 

[nervx]

Hi, can you please explain how you do this router exploit?

Read from post 55 onward. If you get it to work let me know.
http://gbatemp.net/threads/browserh...or-a9lh-installing.442973/page-3#post-6714765

 

[Jechticknight]

I'm in the middle of TRYING to get armloader on here and have a problem.

After moving and creating and drawing the pentagram, I'm up to the point where I need to install armloaderhax and since im on new 3ds, i need to enter through homebrew launcher (which no longer opens through pressing down on the dpad - first sign of Uh Oh)

Only thing..SafeArm or whatever its called doesn't even show up in homebrew launcher so...im effectively stuck.

system turns on and works so yay! but...stuck in the process through the plailect process..

So if i echo that persons sentiment about the process seeming kind of convoluted...but..uh...anyone else go through this?

 

[TheCyberQuake]

I'm in the middle of TRYING to get armloader on here and have a problem.

After moving and creating and drawing the pentagram, I'm up to the point where I need to install armloaderhax and since im on new 3ds, i need to enter through homebrew launcher (which no longer opens through pressing down on the dpad - first sign of Uh Oh)

Only thing..SafeArm or whatever its called doesn't even show up in homebrew launcher so...im effectively stuck.

system turns on and works so yay! but...stuck in the process through the plailect process..

So if i echo that persons sentiment about the process seeming kind of convoluted...but..uh...anyone else go through this?

You should probably post that to the actual safea9lhinstaller thread
http://gbatemp.net/threads/safea9lhinstaller.419577/
Also be sure you actually have safea9lhinstaller's .3dsx file in the 3ds folder. If you follow the guide exactly you shouldn't have any issues. Usually issues like this are caused by reading the guide absent-mindedly and skipping steps on accident.

 

[Jechticknight]

Thanks! Doing so now, and going to retry my steps.

You should probably post that to the actual safea9lhinstaller thread
http://gbatemp.net/threads/safea9lhinstaller.419577/
Also be sure you actually have safea9lhinstaller's .3dsx file in the 3ds folder. If you follow the guide exactly you shouldn't have any issues. Usually issues like this are caused by reading the guide absent-mindedly and skipping steps on accident.

 

[Arkansaw]

It is a trap to get people to update past 9.2 -> more bricks -> demand for hardmod services

sysnand is insurance for everything else, not a9lh or anything that increases the risk of bricking

 

[TheCyberQuake]

It is a trap to get people to update past 9.2 -> more bricks -> demand for hardmod services

sysnand is insurance for everything else, not a9lh or anything that increases the risk of bricking

Except I've installed a9lh to over 10 devices now with no issues and enjoy CFW sysNAND on the latest firmware.
I don't know what you are going on about but it's more a conspiracy theory based off of nothing but your misguided beliefs

 

[Arkansaw]

Except I've installed a9lh to over 10 devices now with no issues and enjoy CFW sysNAND on the latest firmware.
I don't know what you are going on about but it's more a conspiracy theory based off of nothing but your misguided beliefs

the issue will come later when you cannot remove a9lh from the latest firmware, so you are getting that much closer to bricking

 

[Deleted User]

the issue will come later when you cannot remove a9lh from the latest firmware, so you are getting that much closer to bricking

Someone hasn't done there research.Even if someone's NAND bricks,a9lh loads before the sysnand thanks to the otp.bin.With this you can restore a NAND backup and get back before the brick without a hardmod.

 

[Arkansaw]

Someone hasn't done there research.Even if someone's NAND bricks,a9lh loads before the sysnand thanks to the otp.bin.With this you can restore a NAND backup and get back before the brick without a hardmod.

which is completely unnecessary without a9lh or updating sysnand