But can it properly reinstall DLC after it has been automatically deleted by the eshop? Because while 1.4.17 could install DLC just fine, it couldn't reinstall it properly for some reason. Only Devmenu2x could.
Hacking Luma3DS - Noob-proof 3DS Custom Firmware
- Thread starter Aurora Wright
- Start date
- Views 2,727,174
- Replies 19,840
- Likes 261
- Status
But can it properly reinstall DLC after it has been automatically deleted by the eshop? Because while 1.4.17 could install DLC just fine, it couldn't reinstall it properly for some reason. Only Devmenu2x could.
I have the same impressions as you. I'm also using devmenu 11.4 because I feel the new FBI is slower to install and to load folders and such.
BTW, i just checked last commit and wow at this: 253 additions and 7,552 deletions. That looks like some serious code cleanup.
BTW, i just checked last commit and wow at this: 253 additions and 7,552 deletions. That looks like some serious code cleanup.
Moved from ReiNAND to Luma3DS 5.4 and I have few problems:
First, the brightness on the top screen seems kinda off, the whole image is not as sharp as it used to be.
Secondly, after the initial setup using the config menu, I cannot re-enter the menu. Holding SELECT like crazy, at boot or in the home menu, but nothing happens.
Last time I tried AuReiNAND, it was 5.0 or 5.1 it worked properly. Now 5.4 doesn't.
I'm using Menuhax to boot directly into the CFW EmuNAND 10.7.0-32.
First, the brightness on the top screen seems kinda off, the whole image is not as sharp as it used to be.
Secondly, after the initial setup using the config menu, I cannot re-enter the menu. Holding SELECT like crazy, at boot or in the home menu, but nothing happens.
Last time I tried AuReiNAND, it was 5.0 or 5.1 it worked properly. Now 5.4 doesn't.
I'm using Menuhax to boot directly into the CFW EmuNAND 10.7.0-32.
In response to your first question, that has nothing to do with CFW. Check your brightness or just ignore it, because it's a placebo.
As for your second point, getting back into the config menu can be a pain when using menuhax. The best way is probably to delete config.bin in /luma/
Thank you for the quick reply!
It's really not a placebo, because i tried to change the brightness and switching between the 5 levels takes 2-3 seconds to change, while before it was instant. Could it be from the Screen-init brightness settings in the config menu? I think I changed the default 4x to 1x.
As for the config menu, does this have to to with something in the newer versions, because at 5.0 it worked perfectly, everytime. Whats the best filemanager that have a CIA installer, so I can delete the config.bin file without removing the microSD card everytime (with a New 3DS that's a pain in the ass).
I have installed a9lh+Luma3DS.
I cant open Friends List and Miiverse (In the top bar of home menu bottom screen). It gets stuck in the splash screen.
I have to power off to go back to hoke menu
Anybody have a solution? Thank you.
Sent from my ASUS_Z00AD using Tapatalk
I cant open Friends List and Miiverse (In the top bar of home menu bottom screen). It gets stuck in the splash screen.
I have to power off to go back to hoke menu
Anybody have a solution? Thank you.
Sent from my ASUS_Z00AD using Tapatalk
Nope, you don't need to do any of that now since it now reads NATIVE_FIRM from the ctrnand itself. Just be sure "autoboot sysnand", "sysnand is updated", and "force a9lh detection" are enabled. The "show current nand" option is not required but is useful to make sure everything is working right before doing a system update.
Update: If you want to use NTR then you need to put the NTR firmware.bin in the luma folder, but if you don't use NTR then you don't need any of the firmware bins.
Last edited by nl255,
About a recent changelog:
Why would this be more understandable? The first option tells you exactly what it does, it uses the baked in firm of the sysNAND as default, while the other option tells you a condition, that the sysANND is updated.
Why would this be more understandable? The first option tells you exactly what it does, it uses the baked in firm of the sysNAND as default, while the other option tells you a condition, that the sysANND is updated.
It was probably changed because there were people that were using that option even though they weren't using an 'updated SysNAND' set up and causing problems for themselves because they failed to read the wiki and know what that option was before turning it on.
this, i get everytime i try to boot the browser
Attachments
I have no idea wtf that says lol. Load the eshop and tell me if it prompts for an update.
it said that an error had ocurred and tell me to reboot the system, but the error is the same and the eshop dont ask me for update you login atm in reply you
- Status
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
If your not getting your pills from Psi's discount drugs who knows what your swallowing!+1 -
@
Psionic Roshambo:
Shawnita used to get her pills from some other street pharmacist and after switching to The Psi Discount plan she now only has to swallow two things a day!+1
-
-
-
-
-
-
-
-
