D
Depends. Do you want to?If Im still on fw 11.2 and 6.6
Should I update?
lg
Did you download the 11.2 payload and rename to 11.4? I did and it works perfect with latest Luma
--------------------- MERGED ---------------------------
Homebrew Launcher work with O3ds also as long as you get 11.2 payload and rename to OLD 11.4
Congrats on the 7.0 release!
Now, if GW would just update their launcher to work on 11.4, I can finally end that stupid, nagging "please update now!" screen that seems to happen every time I open my 3DS now.
Last time I tested this, I tested it with Luma3DS to a private CFW and I also tested this with Luma3DS to Corbenik. All of them worked for me.
I don't have any clean systems to test withWell what I meant is that if the one who's "hosting" the game has no CFW at all, will the receiving end still be able to receive it even if it's a different region console, if the receiving end has Luma?
Yes, install a9lh and update to 11.4.Is it possible for Luma to do something about the stupid update nag? Like an option to delete whatever file does that on Emunand?
Use the arm9loaderhax.bin from v7 and all the other files you need from v6.6, at least for nowSo menuhax is really broken right now ?
Use the arm9loaderhax.bin from v7 and all the other files you need from v6.6, at least for now
so I just replace the arm9loaderhax.bin in my 6.6 setups, right?
but then do I have luma 7?
No you always need the arm9loaderhax.bin, read the wiki...No, you have 6.6 and a .bin file in the root that you aren't even using. If you're on MenuHax, you're using the .3dsx file only. If you have A9LH, you're using the .bin file only. But why would anyone still be using MenuHax now? A year ago, I could see it, because installing A9LH was a bit tricky and time-consuming, though it was perfectly safe even as of April of last year. However, in the past year they've also made installing A9LH dead simple. There's no longer any excuse for holding onto Menuhax as your main exploit any more than 4.5 firmware and MSET. The extra speed and especially the brick protection make upgrading a no-brainer.
I don't use the lame .3dsx but it doesn't make sense. .bin = a9lh only, .3dsx = your lame entrypointNo you always need the arm9loaderhax.bin, read the wiki...
https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-upgrade
No you always need the arm9loaderhax.bin, read the wiki...
https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-upgrade
Doesn't seem so (note: they all have luma 7):Well what I meant is that if the one who's "hosting" the game has no CFW at all, will the receiving end still be able to receive it even if it's a different region console, if the receiving end has Luma?
Did you download the 11.2 payload and rename to 11.4? I did and it works perfect with latest Luma
--------------------- MERGED ---------------------------
Homebrew Launcher work with O3ds also as long as you get 11.2 payload and rename to OLD 11.4
Well if you know better than the person who actually coded the CFW what are you doing here?I don't use the lame .3dsx but it doesn't make sense. .bin = a9lh only, .3dsx = your lame entrypoint
Sent from my Nexus 5 using Tapatalk
Yes, that's enough to have luma v7so I just replace the arm9loaderhax.bin in my 6.6 setups, right?
but then do I have luma 7?
Redfeme coded luma? Topu kekoWell if you know better than the person who actually coded the CFW what are you doing here?
Do whatever you want, but stop spreading misinformation, pleaseI don't use the lame .3dsx but it doesn't make sense. .bin = a9lh only, .3dsx = your lame entrypoint
Sent from my Nexus 5 using Tapatalk