I'm working on making it optional but it's taking time.Until I can find a way to make updating boot.firm on CTRNAND optional, I've disabled it and disabled showing the commit after the version of "Current installed version" because it was showing the commit number plus a random number that's not supposed to be there. Please redownload v2.1.
Reason why? #BlameReddit
Take all the time you need. And I thank you for that.I'm working on making it optional but it's taking time.
I have a question. After updating Luma3DS to the latest build using LumaUpdater v2.1, my N3DS(11.4 with boot9stram + Luma3DS v7.1) doesn't turn on anymore. When I press the power button, the blue light turns on for a second, and then the system immediately shuts off.
Did I mess something up, and did my 3DS get hardbricked? I have a NAND backup, but I can't restore it because I can't even access GodMode9. Maybe it has something to do with CTRNAND?
Here's my lumaupdater.log
https://pastebin.com/qrbE0RLE
I don't have lumapudater.cfg on the root of my SD card.
Try taking out the SD Card and putting it back in. This usually happens to me and I discovered that taking out the SD Card and putting it back in fixes it. If that doesn't work, try this:I have a question. After updating Luma3DS to the latest build using LumaUpdater v2.1, my N3DS(11.4 with boot9stram + Luma3DS v7.1) doesn't turn on anymore. When I press the power button, the blue light turns on for a second, and then the system immediately shuts off.
Did I mess something up, and did my 3DS get hardbricked? I have a NAND backup, but I can't restore it because I can't even access GodMode9. Maybe it has something to do with CTRNAND?
Here's my lumaupdater.log
https://pastebin.com/qrbE0RLE
I don't have lumapudater.cfg on the root of my SD card.
I followed this guide, so I think I have CTRNAND Luma3DS.
https://3ds.guide/updating-to-boot9strap#section-iv---ctrnand-luma3ds
Try rolling back by putting the official luma 7.1 firm.bin on your SD card root. If Firm.bin is corrupted there's nothing to launch the GodMode9 payload.
Try allowing us to toggle it using lumaupdater.cfg.Until I can find a way to make updating boot.firm on CTRNAND optional, I've disabled it and disabled showing the commit after the version of "Current installed version" because it was showing the commit number plus a random number that's not supposed to be there. Please redownload v2.1.
Reason why? #BlameReddit
Try rolling back by putting the official luma 7.1 firm.bin on your SD card root. If Firm.bin is corrupted there's nothing to launch the GodMode9 payload.
THANK YOU SO MUCH!! That worked! I thought I was literally doomed because I didn't know how it works and thought that the console tries to read the corrupted "boot.firm" on CTRNAND first (then the one on SD card), and there is no way to access CTRNAND without hardmodding...Try taking out the SD Card and putting it back in. This usually happens to me and I discovered that taking out the SD Card and putting it back in fixes it. If that doesn't work, try this:
Downloading right to CTR-NAND has been made optional in the latest commit.Try taking out the SD Card and putting it back in. This usually happens to me and I discovered that taking out the SD Card and putting it back in fixes it. If that doesn't work, try this:
--------------------- MERGED ---------------------------
Try allowing us to toggle it using lumaupdater.cfg.
Downloading right to CTR-NAND has been made optional in the latest commit.
Yes it does.Great, does it also download to SD at the same time?
The latest hourly is/was broken (I'm not sure if any new hourlies have come out yet). That's why you had that issue. I experienced the same thing when testing the new optional CTRNAND feature.THANK YOU SO MUCH!! That worked! I thought I was literally doomed because I didn't know how it works and thought that the console tries to read the corrupted "boot.firm" on CTRNAND first (then the one on SD card), and there is no way to access CTRNAND without hardmodding...
Yes it does.
The latest hourly is/was broken (I'm not sure if any new hourlies have come out yet). That's why you had that issue. I experienced the same thing when testing the new optional CTRNAND feature.
For the time being, yes.So if you want to be safe don't install hourlies?
No there is not and probably won't be.Is there an option to only do latest official to CTRNand and nightlies to SD ? Seems like that's the best way to do rolling updates by default.
That's not up to me though. That's up to astronautlevel to do. They just gave me the link where their hourly builds are.I think I see what's going on with the latest nightlies being broken. The nightlies now build commits for branches other than master, and those branches are often more experimental (the gpu branch exists to work on something known to be broken for example)
If there's some way you can avoid downloading non-master nightlies (or make it optional) that would probably help.
Leave an issue on the GitHub.That's not up to me though. That's up to astronautlevel to do. They just gave me the link where their hourly builds are.