I have not played my 3DS since early 2019. I was wanting to play animal crossing online, and noticed there has been firmware updates released since then. I was running the newest version of luma and the newest firmware back in January of last year. Is it safe to go ahead and update the firmware? Any considerations or any files that need to be modified before or after?
As long as your on Luma3DS v9.1 or higher it's safe to update
- Joined
- Jul 23, 2018
- Messages
- 6,057
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,170
- Country
- Joined
- Aug 19, 2015
- Messages
- 10,195
- Trophies
- 1
- Location
- Glasgow
- Website
- www.rockstarnorth.com
- XP
- 16,155
- Country
Yes but only using Luma as it has built-in protection but other CFWs like cakes doesn't and updating the system removes all hacks.
D
Deleted User
Guest
If you are using a recent version of Luma3DS CFW, then it is perfectly safe to update.
Last edited by ,
Thank you. I just updated my 3DS because of this advice and now it's bricked. Super cool.
Most likely you just need to manually update Luma on your SD card. This is assuming you actually had B9S installed.
I'm not sure on how I can do this. All I know is that I installed the Luma custom firmware back in mid-2019, but didn't really went on on updating by following the rule of "if it ain't broke, don't fix it".
All I know is that if I turn it on pressing Start this second screen comes up, which I believe is Godmode.
Any help is appreciated. I was mostly a casual user on the homebrew side and have little idea what most of these things do. I'm trying to get the crash dump, but it's a bit hard as my notebook doesn't have an SD slot anymore so I'm having to use other means.
EDIT: turning it on with Select brings it on this Luma3DS menu. It's on v10.0.1 Attached image for reference.
Attachments
Last edited by YukidaruPunch,
lmfao. do you know whatthe definition of bricked is? Theres been dozens of these threads about the console with the PM error. You need the latest luma boot.firm on your sd card root.
Please understand this is not my world. I don't understand a thing about programming, hacking and homebrewing. I'm just an psychologist and teacher living in a third-world country with the most undervalued currency of 2020 who likes playing videogames. This is not something I'm usually familiar with.
Edit: I have updated the boot.firm file in my SD card and now it turns on. There's an icon for Luma 3DS on my system. Should I go ahead, open this and try to update it so it's also updated on my system memory? Is it safe to do so?
Last edited by YukidaruPunch,
Then you would be advised to steer clear of these things in the future. The price you pay for getting this stuff for free is that you're at least going to have to learn how to accurately describe your problem when things go wrong.
I've heard that the Luma updater is broken, but you can update the copy in system memory (the CTRNAND) using
Godmode9, as in https://3ds.hacks.guide/finalizing-setup#section-vi---ctrnand-luma3ds . It is advisable to do so since your 3DS otherwise will be much more effectively "bricked" in the unlikely event that something happens to your SD card slot.
@YukidaruPunch Your first post in this thread is a little reproachful. We all do our best to help with any problems (and as long as you don't start randomly deleting things when encountering problems chances are the problems can be solved). I agree with @Kwyjor that a minimum of reading and learning should be done when using custom firmware. 3DS CFW is as safe and NOOB-friendly as CFW can get. There are so many safety nets that one really has to do some nonsense on purpose to really software-brick a 2|3DS. And then there still is ntrboot.
For future reference:
"Updates are always safe. boot9strap can't be patched through a firmware update." is not a wrong statement. Just incomplete.
B9S uses a vulnerability in the bootROM. → Since it is ROM it can't be updated/fixed.
Luma3DS protects B9S from being overwritten by the official updater. → Access to Luma3DS, GodMode9,… will stay.
B9S tries loading boot.firm from SD first. → Incompatibility with newer official firmware can be fixed. Updating will not do permanent damage (unless the SD reader is shot)
Sometimes short statements like: "Updating with B9S is safe." aren't sufficient. The heavily used phrase "Google it!" could even backfire. A person describing themselves as:
If I would give a 3DS in with the PM error to some random people on the street, I guess many would agree on "It is bricked." after turning it on and off three times. (I might try this)
I like to take feelings in account – which isn't the case when saying (100% correct from technical point of view) :
Good luck and have fun to you all!
For future reference:
"Updates are always safe. boot9strap can't be patched through a firmware update." is not a wrong statement. Just incomplete.
B9S uses a vulnerability in the bootROM. → Since it is ROM it can't be updated/fixed.
Luma3DS protects B9S from being overwritten by the official updater. → Access to Luma3DS, GodMode9,… will stay.
B9S tries loading boot.firm from SD first. → Incompatibility with newer official firmware can be fixed. Updating will not do permanent damage (unless the SD reader is shot)
Sometimes short statements like: "Updating with B9S is safe." aren't sufficient. The heavily used phrase "Google it!" could even backfire. A person describing themselves as:
using a search engine with "Is updating a 3DS with custom firmware safe?" may stumble across: "Updating with B9S is always safe!" (I didn't search this now) and might conclude that there can't be any problems.
My definition of "bricked" is: A device doesn't work (and essentially is as useful as brick or paperweight in its current condition). You know it, I know it, anybody active in the GBAtemp 3DS section knows it: The incompatibility of Luma3DS v10.x (< v10.2.1) can be solved by manually updating boot.firm to latest version.
If I would give a 3DS in with the PM error to some random people on the street, I guess many would agree on "It is bricked." after turning it on and off three times. (I might try this)
I like to take feelings in account – which isn't the case when saying (100% correct from technical point of view) :
(This is from another, older thread)
Good luck and have fun to you all!
- Joined
- Jul 23, 2018
- Messages
- 6,057
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,170
- Country
Yep. Sure have learned my lesson... will always double or triple check before updating my devices, and won't be hasty anymore.Glad everything worked out in the end and we even got a little drama to boot.
Also, Etrian Odyssey is pretty fun!
You will always be safe to update as any issues caused may be fixed easily. The most common issue when updating is the update broke an older version of Luma3DS and you need to update it. My suggestion is just update Luma3DS then update and you will be fine.
universal updater might be able to update luma or you can use the newest luma updater. those would be the easiest ways. have to update luma updater if using an older version as something was wrong with the previous version or the url changed or something. I have both on my 3ds, but I haven't looked if luma can be updated with universal updater. however, I think it can iirc some post.
Similar threads
