Hacking Ways Nintendo Can Kill A9LH?

  • Thread starter Thread starter OldGlass
  • Start date Start date
  • Views Views 11,157
  • Replies Replies 97
The chance that nintendo releases a new 3ds device is so so small. The 3ds is at the end of its lifespan. Chances are that the NX will be the next gen for both the wii u and the 3ds.

Will NX be uncrackable? That's a big question.
I will be off a bit, I need to reinstall Ubuntu.
 
It definitely appears they have moved their security team's priorities to the NX which will be the successor to the Wii-U.
Maybe you just meant the NX will be the next Nintendo console, but Nintendo's President has already gone on record saying that the NX will NOT be the Wii U "successor". I'm assuming this means the console won't be using the gimmicks Wii and Wii U did.
 
It's perfectly legal.
You are violating their terms of use by modifying your system in such ways.
Therefore they have the right to remove all their software from the system as long as they don't physically damage your Hardware, which they wouldn't.
(I asked a friend who is studying law about this.)

Also most A9LH Users use it for pirating games etc. So if it comes to it the A9LH user would lose anyway.

However, creating a "brick arm9loaderhax.bin" on the root of the SD card would only affect Users, whi didn't mess around with the path or name of the file.
I personally load it as "launcher.bin". Therefore a brick file arm9loaderhax.bin wouldn't do shit.

And messing with the Arm9 Kernel could affect legit users as well, and is therefore not really an option.

They could surely implement complicated checks and do whatever modifications, but none of that is 100%.
Exactly: 'gateway style code' means bricking, and that's illegal.
 
Will NX be uncrackable? That's a big question.
I will be off a bit, I need to reinstall Ubuntu.
I know this: nothing is uncrackable. It will take quite some time. It has taken a long time for the 3DS scene to arrive where we are now. Heck, we don't even have the (full?) bootroms yet. If there is one thing I learned from coding at school; no code is perfect. Devs are bound to make mistakes that lead to exploits. The big question here is how long it would take to crack the NX. But so far, we don't even know what exactly the NX is. Is it the follow up for the Wii U? Or for the 3DS? Or for both? We don't know. We'll just have to wait for Nintendo to properly announce it.
 
Yeah I'm pretty sure the NX is the successor. But for "business" reasons, Nintendo won't say that. They don't want their Wii-U sales to sink even further when people stop buying the Wii-U and wait for the NX to come out.
 
Yeah I'm pretty sure the NX is the successor. But for "business" reasons, Nintendo won't say that. They don't want their Wii-U sales to sink even further when people stop buying the Wii-U and wait for the NX to come out.
You could be right. I mean, they are pretty much strait-up refusing to talk about its hardware specs. Nintendo is being VERY secretive about the NX for some strange reason.
 
Yeah they are even pulling a Twilight Princess 2.0 by releasing Zelda: Breath of the Wild on both Wii-U and NX at the same time. (and I bet the delay of the game's release is directly tied to the delay of the NX. They want this game to be a launch title for the NX and putting it out on Wii-U first would remove the incentive for people to get a NX. They are expecting this game to be a console seller)
 
It will take quite some time. It has taken a long time for the 3DS scene to arrive where we are now. Heck, we don't even have the (full?) bootroms yet.

Nah. Unless you are gonna fund the bootrom re, it won't happen. It's quite pricey, any possible information obtained is highly confidential and most likely you'll have trouble finding someone willing to help (even paying the costs). And you'll lose that 3ds unit forever. Oh and it's not reliable: you could pay, lose the 3ds unit and not get a single clue of anything because it borked in the process.

Luckily enough, a dead (bricked) system also works.
 
Update 11.1

Prem/Unrecoverable brick :
Check for *.bin file on root of sd card (luma folder, 3DS folder, ect)
If found, set 1 byte in the nand to true.
Check for the byte, then run fine for about a week
After a week, if the byte is true, do the LED permabrick thingy that cannot be fixed with a hardmod
This would give time for everyone using the h4x to update thinking that it is safe.

Recoverable brick:
OR, during update
check hash of firm1,
Atempt to write to firm1,
check hash,
if the hash changed, work as normal,
If hash hasn't changed, retry 5 times,
if it still failed, refuse to boot.
 
The only way for Nintendo to kill A9LH would be to find a way around FIRM protection and update it.
They can also detect it and refuse to update, that doesn't kill A9LH but that will cut you of most of the services.
They cannot make your console unusable.

Imagine you pimp your car and go to the constructor for a software update and it prevents you for starting the engine just because you changed the exhaust. Not possible.
They can refuse to update the software and prevent you to go to any garage/vendor from the company but they cannot make your car unusable even if what you did to it is illegal. They'll have to call the police though but that's another issue.
This might not be the best analogy but you got the idea.
 
The only way for Nintendo to kill A9LH would be to find a way around FIRM protection and update it.
They can also detect it and refuse to update, that doesn't kill A9LH but that will cut you of most of the services.
They cannot make your console unusable.

Imagine you pimp your car and go to the constructor for a software update and it prevents you for starting the engine just because you changed the exhaust. Not possible.
They can refuse to update the software and prevent you to go to any garage/vendor from the company but they cannot make your car unusable even if what you did to it is illegal. They'll have to call the police though but that's another issue.
This might not be the best analogy but you got the idea.
That's a nice theory and all.... but google the Wii update 4.2. They already INTENTIONALLY tried to brick anyone with the HBC installed. (ended up bricking innocent people too. lol idiots.)
 
That's a nice theory and all.... but google the Wii update 4.2. They already INTENTIONALLY tried to brick anyone with the HBC installed. (ended up bricking innocent people too. lol idiots.)
4.2 wasn't an intentional brick. They updated boot2, which they hadn't done up to that point outside of the factory. If everything went well, this would have simply removed bootmii/boot2.

Unfortunately, Nintendo's boot2 update code was buggy. IIRC, they ended up fixing unhacked Wiis broken by this update for free, including systems that were out of warranty.

EDIT: Also, Boot2 is encrypted using the common key, not a system-specific key (unlike 3DS), so it's possible to reflash Boot2 using a NAND programmer.
 
Last edited by GerbilSoft, , Reason: +reflash
4.2 wasn't an intentional brick. They updated boot2, which they hadn't done up to that point outside of the factory. If everything went well, this would have simply removed bootmii/boot2.

Unfortunately, Nintendo's boot2 update code was buggy. IIRC, they ended up fixing unhacked Wiis broken by this update for free, including systems that were out of warranty.
Ah, I see. I was mistaken on their intentions.
 
That's a nice theory and all.... but google the Wii update 4.2. They already INTENTIONALLY tried to brick anyone with the HBC installed. (ended up bricking innocent people too. lol idiots.)
It's not a theory, that's the law at least in the EU and USA. There is of course some variation depending of the country or state especially in the EU. But the main idea is they cannot intentionally disable the console.

For the update it's different of what some of you suggest, which is that they'll kill your console and tell you to shove it up your ass.
 
Yeah I'm pretty sure the NX is the successor. But for "business" reasons, Nintendo won't say that. They don't want their Wii-U sales to sink even further when people stop buying the Wii-U and wait for the NX to come out.
The NX has been announced as far back as 2014 I believe. Never in the history of video gaming have I ever seen a company announce their successor so early before.
 

Site & Scene News

Popular threads in this forum