Well yeah, that's true enough.They kinda are, they don't really specify what they do in their update logs.
Well yeah, that's true enough.They kinda are, they don't really specify what they do in their update logs.
Are you still using the Luma Updater? It's been broken (or at least iffy) for quite a while now, it's recommended to use Universal-Updater instead now.I’m on Luma3DS v10.2-9 apparently, is it safe to install the newest Luma3DS before I do a system update?
Edit: I did just that, installed Luma3DS version 11, I had to do it offline manually because for some reason online would give me an error message then reboots the console if I tried to update Luma3DS, (it was as simple as downloading the file on PC from the official github page then copy/paste) then did a system update, seems to be working fine, tested a couple of pre-installed 3DS games, a Japanese 3DS game with an English patch, a GBA vc inject, my SuperCard SD Two with a DS Rom, and tested GodMod, everything seems to work fine.
However, I should mention when I fire up Luma3DS next to the version number it gives me a glitched number but starting it with select on startup it says version 11 but before the update both menus showed the correct version number, not sure what’s the cause of that or if this is something to be concerned about.
Yes and yes, this is the version I used, should I switch to the stable version or is this version good to go?Are you still using the Luma Updater? It's been broken (or at least iffy) for quite a while now, it's recommended to use Universal-Updater instead now.
By "glitched number" do you mean "80aee6fd" or something like that? If so you simply installed the hourly version instead of the stable release. That's the git commit.
I was using 10.2.1 before. I don't think updating Luma to 11.0 is necessary; I just wanted the extra enhancements that have been made since 10.2.1, and now seemed like a good time to do the update. The last time Luma was updated to work around Nintendo's attempts to block CFW was 10.2.1, which fixed Luma on System Version 11.14 (and we're now on 11.16).So from what I’m gathering here it’s safe to update but I need to also update Luma3D or is it unnecessary?
Huh, that version is the stable version... When I installed with Universal-Updater it just said v11.0 (no commit), but it's not really an issue that it says that so you should be fine.Yes and yes, this is the version I used, should I switch to the stable version or is this version good to go?
perhaps they plan to pull a sony by banning a clean switch/3ds from services if the nnid is also linked to a hacked console? main reason why i never put an NSO account on my hacked console before being bannedThey kinda are, they don't really specify what they do in their update logs.
okie dokie! yeah doesnt the universal updater way also clear the boot options in luma? where do I stick it? just wanna make sure i do it right, already has the luma updateIt's quite easy to download 11.0 from GitHub and copy/paste the files to your SD card manually, so I don't see much reason to rely on an external updater program that itself may or may not be up to date.
what about b9s? is it necessary to update it?I was using 10.2.1 before. I don't think updating Luma to 11.0 is necessary; I just wanted the extra enhancements that have been made since 10.2.1, and now seemed like a good time to do the update. The last time Luma was updated to work around Nintendo's attempts to block CFW was 10.2.1, which fixed Luma on System Version 11.14 (and we're now on 11.16).
TY! Yeah that is simple, Why do ppl use the updater if its just drag over?The boot.firm and boot.3dsx files go in the SD card root, where you will be overwriting the old ones.
If you want to, go ahead (boot9strap 1.4 was released a few months ago and makes it easier to trouble issues with boot.firm on SD/CTRNAND). But as long as you're running boot9strap 1.2 and above (which you have to be if you're running Luma 8.0 or above) you're good to go.what about b9s? is it necessary to update it?
The updater used to be the most user-friendly way to copy Luma's boot.firm to CTRNAND. Luma now does that itself as of Luma 11 (and Luma Updater broke anyway) so it's no longer really necessary to use an updater (though, Universal-Updater can update Luma just fine and have Luma take over on the CTRNAND copying front).TY! Yeah that is simple, Why do ppl use the updater if its just drag over?
The boot speed is increased by less than a second, and the LED has various notification patterns in 1.4. I didn't bother updating since those things don't matter to me, and updating requires more than just copying a file onto the SD card, the way it does with Luma.what about b9s? is it necessary to update it?
Maybe they have older 3DS models where accessing the SD card is a pain? I have N2DS, so the SD and cartridge slots are equally accessible.TY! Yeah that is simple, Why do ppl use the updater if its just drag over?
OHHH YEAH THAT FOLLOWS! I have a new 3ds xl myself, needing a screwdriver is lulzThe boot speed is increased by less than a second, and the LED has various notification patterns in 1.4. I didn't bother updating since those things don't matter to me, and updating requires more than just copying a file onto the SD card, the way it does with Luma.
Maybe they have older 3DS models where accessing the SD card is a pain? I have N2DS, so the SD and cartridge slots are equally accessible.
If you want to, go ahead (boot9strap 1.4 was released a few months ago and makes it easier to trouble issues with boot.firm on SD/CTRNAND). But as long as you're running boot9strap 1.2 and above (which you have to be if you're running Luma 8.0 or above) you're good to go.
Ah, no need. ThanksThe boot speed is increased by less than a second, and the LED has various notification patterns in 1.4. I didn't bother updating since those things don't matter to me, and updating requires more than just copying a file onto the SD card, the way it does with Luma.
And you can never trust what people have done. Somebody says they just dragged the new files over, but you never know whether they fat-fingered another key or if they thought 'ooh while I've got the SD card loaded, I'll try this out'. Could be anything.Yeah, most likely SD issue. 11.16 did not change anything relating to that, so it could not have been the cause of the issues.