Hacking why can't gba games boot from emunand

[Sketchy1]

*this reply was swallowed by a black hole*

 

[Sketchy1]

Another common argument is that emunand is outdated. But you can go to the github repo and still see the menuhax payload for Luma, so therefore its still in active development for emunand. If the dev felt "hey its obsolete emunand can smd" then there wouldn't be a payload for it.
Active development = still current, otherwise it would have stopped ages ago. When you see all emunands end up like rxtools or cakes, then come see us and argue "its obselete"

--------------------- MERGED ---------------------------

No idea why it came up repeatedly sorry >_<

 

[lordofthereef]

You don't need to update to 9.2. Just follow https://3ds.guide/ and your good.

Thank you. One other thing, as mentioned I have gateway and as such my sysnand has been altered in such a way that it boots gateway mode when entering DS profile. Do I need to restore to default or can I just go from here? I do have a nand backed up.

As far as I can tell the guide says just go for it.

 

[xtheman]

Thank you. One other thing, as mentioned I have gateway and as such my sysnand has been altered in such a way that it boots gateway mode when entering DS profile. Do I need to restore to default or can I just go from here? I do have a nand backed up.

As far as I can tell the guide says just go for it.

Just start it. The guide will tell you exactly what to do no matter what setup you have. Thats why everyone recommends it so much.

 

[Krakatau]

Apparently showing interest in how something works makes you a kid now

No it doesn't make you a kid. But hacksn5s4 is a kid.

 

[annoyingcalc]

If they could bypass the FIRM patches that protect A9LH on SysNAND, it also stands to reason that they could break the EmuNAND patches.

IMO the only real additional safety that EmuNAND on A9LH provides is that you have an extra copy of your NAND in case something goes wrong. And a NAND backup, or using SysNAND but keeping an EmuNAND around both provide the same.

My point isn't that they can't break EmuNAND. They can. My point is, if you lose EmuNAND, you can create a new one or restore from backup since you're on SysNAND 9.2. If you lose a9lh, you're dead.

The security EmuNAND provides is that If it completely breaks, and a9lh is removed, you still have SysNAND 9.2 and can reinstall a9lh.

 

[Cuphat]

My point isn't that they can't break EmuNAND. They can. My point is, if you lose EmuNAND, you can create a new one or restore from backup since you're on SysNAND 9.2. If you lose a9lh, you're dead.

The security EmuNAND provides is that If it completely breaks, and a9lh is removed, you still have SysNAND 9.2 and can reinstall a9lh.

And my point was that if they can bypass the FIRM protection patch and remove A9LH, then they can also bypass the EmuNAND patch and straight up update SysNAND from EmuNAND anyway.

Neither situation is likely, by the way.

 

[annoyingcalc]

And my point was that if they can bypass the FIRM protection patch and remove A9LH, then they can also bypass the EmuNAND patch and straight up update SysNAND from EmuNAND anyway.

Neither situation is likely, by the way.

It is not likely, however possible. Updating SysNAND would not happen instantly. Because there's the risk of someone turning off their ds they will not do it in the background, and so there would be a popup that alerts the user of them upgrading, which would at least allow the user to hard shutoff (Possibly brick) their ds instead of updating. It's by no means a perfect solution, but it's safer this way. (The best solution is to not update until many others have, or verify the update is not made to allow patching a9lh)

 

[Halvorsen]

A9lh+emunand master race

 

[HyperT]

My point isn't that they can't break EmuNAND. They can. My point is, if you lose EmuNAND, you can create a new one or restore from backup since you're on SysNAND 9.2. If you lose a9lh, you're dead.

The security EmuNAND provides is that If it completely breaks, and a9lh is removed, you still have SysNAND 9.2 and can reinstall a9lh.

You're equating a9lh to emunand???
Lets straighten that up first. We can equate a9lh to menuhax and emunand [which by necessity is cfw-dependant] to cfw'd sysnand.

If emunand is corrupted you can fix/recreate from sysnand - if you corrupt sysnand with a9lh you fix/restore with hourglass9.

If menuhax is corrupted you re-install it. If a9lh is removed [stock firms installed] you can restore if your savy enough to add an exploit into DS settings which you can use to simply restore a9lh.

If a9lh is removed via nfirms being corrupted i.e. bricked then this would likely affect both setups [as well as stock users]

 

[NEO117]

You're equating a9lh to emunand???
Lets straighten that up first. We can equate a9lh to menuhax and emunand [which by necessity is cfw-dependant] to cfw'd sysnand.

If emunand is corrupted you can fix/recreate from sysnand - if you corrupt sysnand with a9lh you fix/restore with hourglass9.

If menuhax is corrupted you re-install it. If a9lh is removed [stock firms installed] you can restore if your savy enough to add an exploit into DS settings which you can use to simply restore a9lh.

If a9lh is removed via nfirms being corrupted i.e. bricked then this would likely affect both setups [as well as stock users]

And if gateway fucks up on sysNAND and gives you a blue screen? Is that recoverable with A9LH too?

 

[xtheman]

And if gateway fucks up on sysNAND and gives you a blue screen? Is that recoverable with A9LH too?

Its not because it messes the console's critical files because they are assholes.

 

[NEO117]

Its not because it messes the console's critical files because they are assholes.

Hellooooooo EmuNAND, and eventually goodbye Gateway. LOL

 

[Sketchy1]

Hellooooooo EmuNAND, and eventually goodbye Gateway. LOL

Lml ikr? Gateway actually purposely put a kill code in their flashcards to brick people who used clones of their card. I don't think their right in bricking peoples 3ds, but I guess there premise is correct, cause its not fair I pour so much work into a card and sell it for one price, then the minuet I release it you swoop in and take the same card tech and fw, slap on your sticker, sell it for cheaper, then call it yours.

 

[NEO117]

Lml ikr? Gateway actually purposely put a kill code in their flashcards to brick people who used clones of their card. I don't think their right in bricking peoples 3ds, but I guess there premise is correct, cause its not fair I pour so much work into a card and sell it for one price, then the minuet I release it you swoop in and take the same card tech and fw, slap on your sticker, sell it for cheaper, then call it yours.

Imagine if publishers outright destroyed your hard drive if they detected pirated games on it (or worse, if you happen to own the physical version of an old game instead of the re-release on steam and they detected that as piracy). It's not right from any angle, especially if it triggers incorrectly like it happened with 2.1(?). Honestly, it would be really easy to sue them over this, but I don't think anyone would be crazy enough to actually say "These people who make a device for piracy make me real scared because if I use another card to pirate they will damage my 3ds."

 

[Sketchy1]

Imagine if publishers outright destroyed your hard drive if they detected pirated games on it. It's not right from any angle, especially if it triggers incorrectly like it happened with 2.1(?). Honestly, it would be really easy to sue them over this, but I don't think anyone would be crazy enough to actually say "These people who make a device for piracy make me real scared because if I use another card to pirate they will damage my 3ds."

No I'm only saying the general idea to defend your software, bricking someone over it is downright terrible. Software defence is fine by me because it isnt right to steal my hard work (ironic ik, especially cause this comes from a company that thrives off of stealing a game devs hard work) and that's actually the reason they can't exactly be sued for it. The card itself is outlawed, plus breaks the EULA, so neither the law or big N is gonna help ya

 

[NEO117]

No I'm only saying the general idea to defend your software, bricking someone over it is downright terrible. Software defence is fine by me because it isnt right to steal my hard work (ironic ik, especially cause this comes from a company that thrives off of stealing a game devs hard work) and that's actually the reason they can't exactly be sued for it. The card itself is outlawed, plus breaks the EULA, so neither the law or big N is gonna help ya

Yep. That's pretty much it. It sucks but oh well.

 

[GerbilSoft]

Imagine if publishers outright destroyed your hard drive if they detected pirated games on it

How about games that install a ridiculously terrible kernel driver that allows any program to run arbitrary code in the kernel?

 

[annoyingcalc]

You're equating a9lh to emunand???
Lets straighten that up first. We can equate a9lh to menuhax and emunand [which by necessity is cfw-dependant] to cfw'd sysnand.

If emunand is corrupted you can fix/recreate from sysnand - if you corrupt sysnand with a9lh you fix/restore with hourglass9.

If menuhax is corrupted you re-install it. If a9lh is removed [stock firms installed] you can restore if your savy enough to add an exploit into DS settings which you can use to simply restore a9lh.

If a9lh is removed via nfirms being corrupted i.e. bricked then this would likely affect both setups [as well as stock users]

Yes, it would be removed, but if you still have a SysNAND on 9.2 you can reinstall it.