If the select few Luma "devs" put as much time into programming as they do into making propaganda for this thread, they might actually make a decent CFW.
kinda like Chaos and their website design lelIf the select few Luma "devs" put as much time into programming as they do into making propaganda for this thread, they might actually make a decent CFW.
Being a longer time user of Luma and now trying to see wether this is better for me, I think Luma is better due to more user friendliness, it's a good cfw that is easy to set up and does what it has to do. Reinand just feels pointless right now for me due to the lack of functionability in certain regards.If the select few Luma "devs" put as much time into programming as they do into making propaganda for this thread, they might actually make a decent CFW.
Firm prot has been fixed if you payed any attention to the useful posts in this thread. And svc0x7B is unneeded.kinda like Chaos and their website design lel
but if Rei could spend more than 5 seconds bashing other in private he may actually fix his own bugs Like Firm Prot, add SVC backdoor to fix his shit and also add Dev flags to his github
fixed that for youkek prot has finally been fixed if you paid any attention to the useful posts in this thread. And svc0x7B is unneeded.
svc0x7B is used by BootNTR and retroarch core emulators for dynarec. Although right now you can use an old firmware this will probably change soon, as all Nintendo has to do now is update either homemenu or errdisp to look for the new firmware version.Firm prot has been fixed if you payed any attention to the useful posts in this thread. And svc0x7B is unneeded.
It's actually needed by RetroArch's dynarec and NTR (if it ever supports 11.0, that is).And svc0x7B is unneeded.
well yea, i firmlaunch an older firm.. once games are even out that requires me to update to 11+, i'll worry about svc thing then.svc0x7B is used by BootNTR and retroarch core emulators for dynarec. Although right now you can use an old firmware this will probably change soon, as all Nintendo has to do now is update either homemenu or errdisp to look for the new firmware version.
Once that happens it will probably become necessary to reintroduce svc0x7B
CFW would have to patch that lockdown. Not a big issue.One issue that popped up with this, is that new apps could test svcBackdoor (think menu for example) and if it succeeds it could lockdown the system, because svcBackdoor isn't supposed to exist in 11.0 FIRMs
Retroarch uses it and tries now to get a working build without it and NTR also needs it but doesn´t work with newer native firms, but are discussing to use just the backdoor to be independent of the native firm. So I wouldn´t say that it is useless but not everyone needs it. Regardless it is still nice to have. At least that is how I understood this matter.Firm prot has been fixed if you payed any attention to the useful posts in this thread. And svc0x7B is unneeded.
You know, this project's source is open, you can always contribute.kinda like Chaos and their website design lel
but if Rei could spend more than 5 seconds bashing other in private he may actually fix his own bugs Like Firm Prot (on time- because he did say he copied code yet somehow didnt in process), add SVC backdoor to fix his shit and also add Dev flags to his github
The problem is that because the kernel minor revision was updated in 11.0 (2.50 -> 2.51), we won't be able to firmlaunch older NFIRMs if they update homemenu, errdisp, or any other critical system components because they'll refuse to boot due to the outdated firmware minor revision.well yea, i firmlaunch an older firm.. once games are even out that requires me to update to 11+, i'll worry about svc thing then.
i did it got closed because rei couldnt write files with the code implemented for dev work.You know, this project's source is open, you can always contribute.
False. It's against GPL to remove headers from source files which say that the file is GPLed, while he just had a small "all rights reserved" (which makes no sense, as by placing a source file under GPL it's no longer "all rights reserved"...). And regardless, I removed it from all the files (and even my own name).The point is, its against GPL to modify the names added to it. Well in this case, it was more of a moral issue than a legal one. But Tux decides to make baseless accusations when clearly they've done worse, and theres actual proof behind it.
Yea, good point. Well ill consider it.The problem is that because the kernel minor revision was updated in 11.0 (2.50 -> 2.51), we won't be able to firmlaunch older NFIRMs if they update homemenu, errdisp, or any other critical system components because they'll refuse to boot due to the outdated firmware minor revision.
I'm not obligated to accept PRs. Maybe provide something worth looking over.i did it got closed because rei couldnt write files with the code implemented for dev work.
which is fixed by adding several #ifdef #endi
For what it's worth, we were privately collaborating on that elsewhere. There was no ill intent.
So how does one go about updating to firmware 11? I still got the error updating to the latest firmware? Do I need to downgrade the emu and and upgrade it again?