So if want to be on 11.0 and use NTR I need to install Luma? And thus far, I can safely install Luma, then update to 11.0 (making sure to have a backup as always) and then continue mostly as usual, even though I'm not on A9LH?
But wouldn't this need both an arm11 and an arm9 kernel exploit so we can patch the system and modify (minver = 0 for everything) or even bypass that list? Or is that the "software workaround" you are talking about?
Can I ask what the future likelihood of breaking a9lh with updated sysnand would be? Could at any time be a whisker away from a brick and I always come here first anyway to check out anything new, but is there anything specific to look out for?
"Downgrading in general, regardless of any arm11 kernel exploits (like svchax) released in the future, has been broken (possibly permanently). The firmware now contains a hardcoded list of minimum versions, and will not let us install a system title of a lower version than in the list, even if we have permission to install our own titles. This will make downgrading on 11.0.0's firmware impossible if no software workaround is found."
But wouldn't this need both an arm11 and an arm9 kernel exploit so we can patch the system and modify (minver = 0 for everything) or even bypass that list? Or is that the "software workaround" you are talking about?
Well cfw could do it just like they added svcBackdoor though it isn't a high priority right now since the NTR/10.2 firmware.bin workaround still works.
Yeah you are absolutely right, but given how easy is for ninty to break that workaround, having that figured out was nice and reassuring. Now we can just put svcbackdoor back when it's needed.
It would probably be just as easy to fix ninty's breaking of that workaround by modifying the module version checks to make the 10.2 nfirm work regardless of what the modules supposedly require. The only way to actually break the workaround would be for them to make the system modules rely on new functions not present in the 10.2 nfirm.
From what I'm reading, looks like you think that through. If you feel like it, go for it. Try to figure out if what you are saying may work or fail.
What am I trying to say is if you don't feel like things are being done well, no one is gonna stop you to constructively fix them.
Complaining about decisions made by devs usually takes you nowhere. Even if you have a perfect valid reason to complaining about.
I wasn't making any complaints about the cfw devs or their work. I was replying to your statement about ninty fixing the workaround, the point is they really can't because the devs can just unfix it just as easily.
It was about the priority of features in the first place if I'm not mistaken (correct me please).
So I understand you have a different opinion on the order in which features should be worked on and delivered. Perhaps I streched a little bit too much the word complain but I think I managed to make the point.
Yes.Can you still update your Rxtools emuNAND firmwarw to 11.0? Just want to be safe.!
EDIT: sysNAND: 9.2
EmuNAND: 10.7
- Currently, there is a hardmod workaround to flash an older firm to NAND and re-enable downgrading, but this could possibly be fixed in 11.1.0 and it's only fortunate that it hasn't been fixed yet.
If I'm on version 11 with A9LH and Luma3DS, what would happen if I restored my NAND with my 10.7 backup? Is this still possible?
Nothing, I've done this many times since I updated to 11.0 after messing with my sysNAND a lot (including a few bricks!). It is completely safe to restore a 10.7 NAND after updated to 11.0 with Decrypt9!
Any user of the Guide (or Luma3DS + NTR firmware bin in general) will be completely unaffected by most of these changes since the NTR firmware bin replaces 11.0.0's firmware with a lower version firmware.
Thanks, going to update it later when I get home.!