Hacking Luma3DS - Noob-proof 3DS Custom Firmware

Status
Not open for further replies.

VashTS

Beat it, son
Member
Joined
Mar 14, 2009
Messages
4,308
Trophies
1
Age
39
Location
Upstate NY
XP
3,756
Country
United States
not sure if its luma or a9lh - i just did a9lh and now when i try to play a game online it says i have to update my system...i am using an emunand on latest 11.0 update. was working online prior to a9lh.

i installed the cia files from luma3ds wiki - O3DS AGB.cia, O3DS NATIVE104.CIA AND O3DS TWL.CIA but still same results.
 

astronautlevel

Well-Known Member
Member
Joined
Jan 26, 2016
Messages
4,128
Trophies
2
Location
Maryland
Website
ataber.pw
XP
5,008
Country
United States
not sure if its luma or a9lh - i just did a9lh and now when i try to play a game online it says i have to update my system...i am using an emunand on latest 11.0 update. was working online prior to a9lh.

i installed the cia files from luma3ds wiki - O3DS AGB.cia, O3DS NATIVE104.CIA AND O3DS TWL.CIA but still same results.
Update to Luma v5.5.
 

RocketRobz

Stylish TWiLight Hero
Developer
Joined
Oct 1, 2010
Messages
16,594
Trophies
3
Age
24
XP
20,989
Country
United States
Do A and B buttons not work for payload loading? Holding one of these two buttons just take me to the splash screen.
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
Do A and B buttons not work for payload loading? Holding one of these two buttons just take me to the splash screen.

A and B are reserved for persistence override and booting a second emunand (respectively). Therefore you have to hold L when launching A and B payloads IIRC.

Do I simply replace the old files with the new ones for updating? And should I use the dev version, sounds like it's only for developers.

I would just use the regular version unless you have some specific reason for needing a dev version feature. It's also a good idea to delete your old configuration file from the "luma" folder because the old configuration files are apparently not 100% compatible with 5.5
 
Last edited by Kazuma77,

pbanj

The "friendly" neighborhood sandwich
Member
Joined
Dec 29, 2014
Messages
2,743
Trophies
1
Location
in a ziploc
XP
1,650
Country
United States
A and B are reserved for persistence override and booting a second emunand (respectively). Therefore you have to hold L when launching A and B payloads IIRC.



I would just use the regular version unless you have some specific reason for needing a dev version feature. It's also a good idea to delete your old configuration file from the "luma" folder because the old configuration files are apparently not 100% compatible with 5.5
The old config file issue was fixed a while ago. He can just hold select on boot to make sure.
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
The old config file issue was fixed a while ago. He can just hold select on boot to make sure.

Stable or nightly? Not everyone runs the latest nightly after all. It doesn't hurt anything to delete it, regardless. I always do when I upgrade any CFW just in case.
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
I think it was fixed before the rename. Every time a new option it got added it messed it up. So aurora fixed that issue so the config files wouldn't get messed up anymore.

Well, deleting the config file just fixed an issue for someone updating from 5.4 to 5.5 today. It was booting to SysNAND, and they did not have "SysNAND is updated" selected. So I told them to delete the file and it worked.
 

pbanj

The "friendly" neighborhood sandwich
Member
Joined
Dec 29, 2014
Messages
2,743
Trophies
1
Location
in a ziploc
XP
1,650
Country
United States
Well, deleting the config file just fixed an issue for someone updating from 5.4 to 5.5 today. It was booting to SysNAND, and they did not have "SysNAND is updated" selected. So I told them to delete the file and it worked.
Oh that is odd. Was it only one person?
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
Oh that is odd. Was it only one person?

Yeah, they thought it was the modified Safe A9LH Installer causing it, then they tried 5.4 and it worked, so I suggested deleting the config file. It worked. They're happy. That's all that matters.
 
  • Like
Reactions: pbanj

pbanj

The "friendly" neighborhood sandwich
Member
Joined
Dec 29, 2014
Messages
2,743
Trophies
1
Location
in a ziploc
XP
1,650
Country
United States
Yeah, they thought it was the modified Safe A9LH Installer causing it, then they tried 5.4 and it worked, so I suggested deleting the config file. It worked. They're happy. That's all that matters.
Ya. Just making sure it wasn't wide spread as that would be an actual bug.
 

xtreme1

Well-Known Member
Member
Joined
Nov 14, 2008
Messages
619
Trophies
1
XP
1,446
Country
United States
Are there still issues with sleep mode? I have 5.5 flashed to my sys, and it never seems to come out of sleep mode.
 
D

Deleted User

Guest
it might sound dumb but it might also be the cause of your Problem.. Do you have the "luma" folder on the root of your sd card?
I experienced that issue before & later realized I forgot to move the folder while switching Cards.

Seems like Luma3DS doesn't create/save the configurations if the luma directory doesn't exist.

That doesn't sound dumb at all. After formatting my entire 3DS and starting almost-over, I was able to correct my mistake. My luma folder was in the correct place. I had just messed up backing up and overlapping important 3DS files, which I think sounds even stupider. Good thing those types of files wouldn't cause bricks..
 
  • Like
Reactions: pbanj
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Veho @ Veho: https://www.keepretro.com/products/miyoo-a30