If, with any system update, they manage to patch it, you just stay on the last version and spoof games again, like we did pre-a9lh with 9.2. No sweat.
however, you also did say that they can make it harder to re-install. Some noobies here will just give up on the hacking scene.LOL
As I already said, A9LH is impossible to patch without hardware revision xD
however, you also did say that they can make it harder to re-install. Some noobies here will just give up on the hacking scene.
there they go, they just stopped some pirates.
Now, I'm not saying that people are not going to get a hardmod. Obviously, some will, but many temp members are still kids, incapable of earning money yet to ship to other countries for a hardmod, soooo yeah. making it harder to install like you said does kinda help them
But then "don't update to xx.xx version" would always be an option
Theres a difference in Newbies, Lazy and stupid people.Some noobies here will just give up on the hacking scene.there they go, they just stopped some pirates.
Theres a difference in Smart, Lazy and stupid people.
A smart tries to search, read, understand and actually practice the sofmodding.
A lazy person, its the one that always want someone to do it for him.
An theres always the stupid people, who "Accidentally updated", "I got banned from playing online an unreleased game" etc, this last ones deserve to be stopped.
Regarding the sdcard. I'd say every thing that isn't encrypted on it [i.e. Nintendo 3DS folder] is classed as user's data and if you check the EULA they can't touch that.I've been reading about how Al9h + Luma3DS should be able to survive updates, but what about if Nintendo was really trying to remove it? I mean, it seems to me like the "arm9loaderhax.bin" on the SD card or NAND will run every start up. What stops Nintendo from modifying these files? I heard about there being write protection to the FIRM, but I haven't heard of anything that stops them from modifying files on the SD card. What if they made something that every shutdown deleted arm9loaderhax.bin (Making you have to plugin the SD card to your computer every time you want to boot up) or even worse, replace it with their own file that could delete all "not acceptable" content on the SD including EmuNAND. Of course we could patch this out, but this would require a patch to be made. Everyone who updated (who may or may not have a recent backup) would lose all of their stuff. (Assuming Nintendo wants to take a Gateway approach to things)
Or am I completely wrong and would this not work?
Well the way you put it, it seems a restore without "keep A9LH" will remove it. "Restore NAND (keep A9LH)" is simply "restore the backup but skip secret sector and FIRM partitions". [Source]No. With Hourglass9, yes; A9LH is preserved during a restore. With Decrypt9, it has to be specifically told to retain A9LH after a restore.
I've been reading about how Al9h + Luma3DS
Really? That's interesting. Would you mind linking me the EULA?Regarding the sdcard. I'd say every thing that isn't encrypted on it [i.e. Nintendo 3DS folder] is classed as user's data and if you check the EULA they can't touch that.
For completeness I'm not too sure on the legalities of the save files that are in N3DS folder as you have to decrypt them to use them. I know that cartridge saves [that could be gotten to with powersaves] are classed as userdata however.
http://www.nintendo.com/consumer/info/en_na/docs.jspReally? That's interesting. Would you mind linking me the EULA?
This all makes sense, you might be sharing an SD card between your camera and console or PC and console. Nintendo have no right to be messing with stuff not created by the console. Imagine if they caused photos of your child as a baby to be corrupted. You wouldn't be happy.http://www.nintendo.com/consumer/info/en_na/docs.jsp
Maybe I was over/under-reading it yesterday but #4. User Content has 'You own your User Content.'
And as Nintendo only has the contents of Nintendo 3DS encrypted [not sure atm if the 3ds adds any other files/folders to a blank sdcard], they afaik can't definitively state anyother files as malicious [obviously they could compare the sha/md5 of known a9lh.bins but that would require reading data that they have no right to read]
As they haven't encrypted the sdcard as a whole [which they probably couldn't have when the 3ds's were released - might have been doable with the n3ds] - I think they have to acknowledge that the sdcard could have been used for multiple purposes.
Edit: yea I might have been wrong about what falls under "user content" reading #1 again but I think the rest of thebreasoning still stands
What if they made something that every shutdown deleted arm9loaderhax.bin (Making you have to plugin the SD card to your computer every time you want to boot up) or even worse, replace it with their own file that could delete all "not acceptable" content on the SD including EmuNAND.
If your only copy of important photos is on an SD card (or if "only copy" can be used to describe any photos of yours at all, for that matter) then you aren't going to be happy in the near future anyway. Backup your shit, people.This all makes sense, you might be sharing an SD card between your camera and console or PC and console. Nintendo have no right to be messing with stuff not created by the console. Imagine if they caused photos of your child as a baby to be corrupted. You wouldn't be happy.
That doesn't matter. Nintendo has no right to read or tamper with their users' private files.If your only copy of important photos is on an SD card (or if "only copy" can be used to describe any photos of yours at all, for that matter) then you aren't going to be happy in the near future anyway. Backup your shit, people.
But then "don't update to xx.xx version" would always be an option
So if I have a9lh and only use my EmuNAND always at the latest version, I'll be safe forever?Worst case scenario we leave sysnand on the last FW that a9lh works on and use emunand again.