LOLLERS! I love 3DS Memes! <3 Ya!Soon™. No, really, it'll probably be something this week when I find the time.
LOLLERS! I love 3DS Memes! <3 Ya!Soon™. No, really, it'll probably be something this week when I find the time.
School always comes first. No ifs, ands, or kawaii butts!!!New update: v2.2!
Sorry for the lack of an update to the app recently. This is because of a couple of reasons:
* I recently finished my summer classes and I was taking a break from doing anything for a bit before my fall classes started.
* I was having some issues with my build environment (everything but the .CIA was able to be built, bannertool was giving me issues). I finally, obviously, figured it out. Don't ask me how though.
Notes:
* Luma3DS v8.0+ is only to be used with boot9strap v1.2+. Please follow https://3ds.guide/updating-b9s to update to boot9strap v1.2+.
* This will probably be the last update for Luma Updater for awhile. My fall semester of college classes has already started and I'm already feeling the homework pressure.
What's New:
* Removed the latest hourly build text. Why? You can no longer install the latest hourly with the latest version of Luma Updater to the text is useless and therefore has been removed.
* Changed the display text at the bottom of the top screen.
* The following is credit to chenzw95 on GitHub:
* Block all updates from Luma3DS v7.1, which is only compatible with b9s v1.0/v1.1. This is to help with people updating to Luma3DS v8.0+ without updating b9s first.
* Show error codes in hex, for consistency across apps.
* Allow users to restore any backups if they have no internet connection.
* Removed the path changer code because Luma3DS no longer uses it.
Download link: https://github.com/KunoichiZ/lumaupdate/releases/tag/v2.2
Let me know of any issues.
I didn't though. I had the release as a draft originally on the Github releases page and I kept adding commits, then I released the update. That's what the 16 commits are. Only the last commit was made after the actual release and that was the addition of the QR code for v2.2. It's a very weird Github bug/issue/thing and as a result, the release won't have the latest commits. I'll see what I can do about fixing that.School always comes first. No ifs, ands, or kawaii butts!!!
Thanks for the update! I'm curious though, as to why you left 16 commits out of the release. Did they brink things or was in an oversight? In any case, thanks for the update to the updater so I can update!!
Score! I thought it was strange that you had released 2.2 with the 2.2 commits still to be committed. Dumb GitHub. All fixed! Thanks again!I didn't though. I had the release as a draft originally on the Github releases page and I kept adding commits, then I released the update. That's what the 16 commits are. Only the last commit was made after the actual release and that was the addition of the QR code for v2.2. It's a very weird Github bug/issue/thing and as a result, the release won't have the latest commits. I'll see what I can do about fixing that.
EDIT: It should be fixed now...?
It's very strange. I'll just be sure to keep a notepad handy for future release notes to prevent this from happening again. It's a weird GitHub issue and an overlook on my part.Score! I thought it was strange that you had released 2.2 with the 2.2 commits still to be committed. Dumb GitHub. All fixed! Thanks again!
Use an older version of the app. Note: do not come crying back to this thread when you update to an hourly version and your system no longer boots. I don't support the hourlies.Is there a chance that we can get Nightly updates with this app?
Lol thanks. Is better to keep the stable builds then.Use an older version of the app. Note: do not come crying back to this thread when you update to an hourly version and your system no longer boots. I don't support the hourlies.
It is. That was my whole purpose for removing the option to download them because people would update to the hourlies, then complain that Luma Updater caused their system not to boot because it was the last thing they used while "their system was working." I got sick and tired of the complaining and got rid of the feature. Now it's up to the people themselves to either download the hourlies with the hourlies site or use an older version of the app. That way, it's not on me when their system stops booting. All in all, the feature will not be coming back.Lol thanks. Is better to keep the stable builds then.
Oh! I understand now whyit was removed. Well in that case I can try the older version. I imagine the people complaining lol. Thanks!It is. That was my whole purpose for removing the option to download them because people would update to the hourlies, then complain that Luma Updater caused their system not to boot because it was the last thing they used while "their system was working." I got sick and tired of the complaining and got rid of the feature. Now it's up to the people themselves to either download the hourlies with the hourlies site or use an older version of the app. That way, it's not on me when their system stops booting. All in all, the feature will not be coming back.
Try renaming the Nintendo 3DS folder. If that helps, name it back and follow the deleting home menu extdata section of https://3ds.guide/troubleshooting*deep breath*
So, I followed 3ds.guide to put a CFW in my brother's (an 24yo "i don't do technology" type) Old 3ds , this was about about month ago, I used sound hax, safeBS9Installer and boot9strap and I did a backup of his system which he was supposed to save on his computer ( doubt it's still there).
He changed the SD cards twice ( à lá copy the contents and dump into the new card). The second time he did this, all the titles simply didn't show up again. So he started re-downloading everything again, starting with luma updater.
He DLed lumaupdater.cia via QR code with FBI and ran it.
Then he handed his 3ds to me, which showed the "Luma V8.1.1 configuration, press A to select, start to save"
I did a google search which refered me back to the 3ds.guide, I selected "Show NAND or user string...", pressed start, and now...
Blue led on + eternal black screen.
... Help?
Try renaming the Nintendo 3DS folder. If that helps, name it back and follow the deleting home menu extdata section of https://3ds.guide/troubleshooting
Yes, the Nintendo 3DS folder (not the 3ds folder)So... Force a shutdown and rename the 3DS folder?
Yes, the Nintendo 3DS folder (not the 3ds folder)
How much do you value your save data and installed games etc? If you don't value them at all, then do a CTR transfer using Decrypt9, which should fix it. If you do, wait to see if anyone else has some other troubleshooting ideas.When I shut it down it showed a dump error (tried to take a picture but i wasn't fast enough). I renamed the Nintendo 3DS, turned the 3ds on, the blue led is on + black screen.
How much do you value your save data and installed games etc? If you don't value them at all, then do a CTR transfer using Decrypt9, which should fix it. If you do, wait to see if anyone else has some other troubleshooting ideas.
Edit: one more troubleshooting idea: redownload Luma 8.1.1 boot.firm in case yours is corrupted. From https://github.com/AuroraWright/Luma3DS/releases
Also try a new SD card.
Edit: one more troubleshooting idea: redownload Luma 8.1.1 boot.firm in case yours is corrupted. From https://github.com/AuroraWright/Luma3DS/releases
How much do you value your save data and installed games etc? If you don't value them at all, then do a CTR transfer using Decrypt9, which should fix it. If you do, wait to see if anyone else has some other troubleshooting ideas.
Edit: one more troubleshooting idea: redownload Luma 8.1.1 boot.firm in case yours is corrupted. From https://github.com/AuroraWright/Luma3DS/releases
Also try a new SD card.