D
Hacking Luma3DS - Noob-proof 3DS Custom Firmware
- Thread starter Aurora Wright
- Start date
- Views 2,727,142
- Replies 19,840
- Likes 261
- Status
Depends. Do you want to?
If yes, then update, if no, then don't.
So, that works? I tried it with the 11.3 one and it did not. I will try the 11.2. This is mainly what's been keeping me from updating my everyday use units (NTR selector certainly got updated fast this time).
EDIT: Confirmed. This seems to work. I haven't tried many apps yet, so I can't be certain everything loads without any issues, but, so far, so good. Thanks for the tip. Since the 11.3 one had failed to work, I guess I just assumed that trying the rest would be pointless. Well, I guess that will teach me to give up too soon.
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.
You should know how long it takes GW to release stuff by now. The best solution is probably to just to clean the nag (if this is on SysNAND) using the aforementioned trick, back your 11.2 NAND up, and restore it to EmuNAND if you still have an EmuNAND partition (I was keeping a 9.2 just in case I ever needed old exploits, but apparently 11.2 has become the new 9.2). If not, you may need to backup your card, format it for EmuNAND, and then restore the contents first. Then you can update your SysNAND to 11.4 for use with Luma (and the latest Skeith if you have it installed), and use your 11.2 EmuNAND with GW (and the current stable Corbenik and Cakes 190, if you have them installed). It has the bonus effect of eliminating the nag from the GW software since you are launching it with an EmuNAND like it wants you to. There should be no negative side effects from having linked NANDs with them both running CFW. The only down side is the extra step you'll have to take to get new installs to show up on both NANDs. But it's not that difficult having D9 extract the tickets from one and inject them to the other.
It should go without saying I'm assuming you have A9LH installed. There really aren't any excuses left to still be using MenuHax (just like there's no reason to keep using KMEAW 3.55 on the PS3, though someone out there probably still is). As a main exploit anyway. If you want to use it to load HBL from an EmuNAND by just holding L, I can see that.
Then again, since there's nothing that needs 11.4 (I don't believe they added any new functions, and it's easy to bypass superficial requirements), you could just try to fix the nag and stay on 11.2 a little longer. I think d0k3 has another way to remove the nag that works with any NAND. Of course, as with most things, you want to make a backup first, and any attempt on a SysNAND should be with A9LH installed. The people that really benefit from the 11.4 update are the ones on 11.3, because that had a bug that was causing slowdown (probably a new protection measure with unintended side effects).
Last edited by Kazuma77,
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?
- Joined
- Jan 11, 2016
- Messages
- 811
- Trophies
- 0
- Age
- 32
- Location
- Wherever my imagination decides.
- Website
- fr3quency.deviantart.com
- XP
- 823
- Country
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.
Last edited by Kazuma77,
No you always need the arm9loaderhax.bin, read the wiki...
https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-upgrade
- Joined
- Jan 11, 2016
- Messages
- 811
- Trophies
- 0
- Age
- 32
- Location
- Wherever my imagination decides.
- Website
- fr3quency.deviantart.com
- XP
- 823
- Country
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
OK, maybe it does load the .bin file. It's been a while since I looked at how it works for Menuhax, because just like MSET, I have no use for such instructions. All of my 3DSes have been A9LH for over a year now. Decided to try it on one unit, ended up converting them all before the week was over. And that was back when you had to downgrade an EmuNAND to 2.x (never saw why Decrypt9 couldn't just inject the 2.x files into an existing dump, but now we have movable NAND dumps). Now all you have to do is backup your NAND, install the transferable 2.1 image with D9, install A9LH, and restore your NAND back. It's so easy now that it's not even funny.
Most other CFWs have a separate .dat file for Menuhax or are self-contained (as is the case with Mini Pasta). Having not seen the .dat for a while, I assumed the .3dsx had become self-contained. Well then, guess that will load 7.x, but it's hard to say if it will work 100% correctly. I can't test it regardless.
Last edited by Kazuma77,
- Joined
- Jan 11, 2016
- Messages
- 811
- Trophies
- 0
- Age
- 32
- Location
- Wherever my imagination decides.
- Website
- fr3quency.deviantart.com
- XP
- 823
- Country
I can't seem to get LayeredFS to work, I recreated the RomFS in H:\luma\titles\000400000007AF00\romfs\ and enabled game patching, but nothing changes.
- Status
Similar threads
-
-
-
@
Xdqwerty:
something about ea reverse engineering the genesis so they could make their games there+1 -
-
@
BakerMan:
if they get permission from 4j (the studio who helped put minecraft on consoles), they could put the console edition tutorial worlds in the game, as seeds+1
and i mean all of them (if not, maybe a few highlights, like TU1, TU31, and TU69) -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
