ROM Hack Need Help N3DS CFW setup

[GreatCrippler]

That's really unusual. You pressed Start to save the config after checking the box, and it booted into a home menu and yet still didn't display the System Version properly?

Can you post another downgrade log, just in case?

Unfortunately I can't get into it very often. It almost always black screens. So restarting to check anything is getting really annoying.

 

[CrispyYoshi]

Unfortunately I can't get into it very often. It almost always black screens. So restarting to check anything is getting really annoying.

What do you see whenever it crashes? Like, describe exactly what you see from the moment you power on until the moment it crashes: It might not even be Luma3DS, but rather Menuhax itself.

Are you using CTRBootManager? Do you have a timer on it, and is it set to the default time if you are using it?

 

[GreatCrippler]

What do you see whenever it crashes? Like, describe exactly what you see from the moment you power on until the moment it crashes: It might not even be Luma3DS, but rather Menuhax itself.

Are you using CTRBootManager? Do you have a timer on it, and is it set to the default time if you are using it?

It's not crashing, it's just not booting. Just a black screen. Have gone back and forth between CTR, and normal CN HBL, but it just won't start very often.

 

[CrispyYoshi]

It's not crashing, it's just not booting. Just a black screen. Have gone back and forth between CTR, and normal CN HBL, but it just won't start very often.

I'm not sure what you're referring to. What is "CTR", "it", and what do you see when you turn on the console?

 

[GreatCrippler]

I'm not sure what you're referring to. What is "CTR", "it", and what do you see when you turn on the console?

CTRbootmanager is what i mean by CTR. The system boots fine, it just won't boot into Luma. If I select Luma from HBL, or let CTR try to boot it 4/5 I get a black screen. Nothing else. On the rare occasion it does start, I am not seeing anything different in the system version number.

 

[CrispyYoshi]

CTRbootmanager is what i mean by CTR. The system boots fine, it just won't boot into Luma. If I select Luma from HBL, or let CTR try to boot it 4/5 I get a black screen. Nothing else. On the rare occasion it does start, I am not seeing anything different in the system version number.

But at some point, you've managed to get in the Luma3DS menu, ticked the Sys/Emu Checkbox, and pressed Start to save the config?

Try deleting config.bin in SD:/luma/ and see if it will boot you into the Luma Config menu next time you boot luma.

But alternatively, run Homebrew Launcher, run downgrade_check, and post your log again, because another frankenfirmware might be causing problems too.

 

[GreatCrippler]

But at some point, you've managed to get in the Luma3DS menu, ticked the Sys/Emu Checkbox, and pressed Start to save the config?

Try deleting config.bin in SD:/luma/ and see if it will boot you into the Luma Config menu next time you boot luma.

But alternatively, run Homebrew Launcher, run downgrade_check, and post your log again, because another frankenfirmware might be causing problems too.

I assume if the expected install, and the installed version are different, I have a problem? A lot less this time, but still 2... Ugh, lol

 

[CrispyYoshi]

I assume if the expected install, and the installed version are different, I have a problem? A lot less this time, but still 2... Ugh, lol

Not necessarily, as long as they aren't important to the downgrade process.

But otherwise, your next best bet is to delete all of your homebrew stuff and re-install everything cleanly back from the start of Step #18 (copy the contents of starter.zip to your root again, though, and skip the SysNand backup if you've already done it): https://github.com/Plailect/Guide/wiki/Part-2-(Downgrading)

 

[GreatCrippler]

Not necessarily, as long as they aren't important to the downgrade process.

But otherwise, your next best bet is to delete all of your homebrew stuff and re-install everything cleanly back from the start of Step #18 (copy the contents of starter.zip to your root again, though): https://github.com/Plailect/Guide/wiki/Part-2-(Downgrading)

Yea, tried to redo the downgrade, and told me it was already done.

Edit: After trying the downgrade again, for no good reason, I booted mini pasta, and then Luma from it. Came right up. >.> See if I am in the clear now.

 

[CrispyYoshi]

Yea, tried to redo the downgrade, and told me it was already done.

Then you are either already running Luma3DS properly or there is something wrong with your folder structure. It sometimes crashes because Menuhax entrypoint isn't as stable as A9LH. You could consider setting up lesshax, which is a slightly modified version of menuhax that crashes about 15% less or so, but I'd recommend getting LumaCFW/CTRBootManager working and then continuing through with Part4/5 of the guide.

Try to follow the part 2 steps again just in case there's something wrong with your SD structure.

 

[GreatCrippler]

Then you are either already running Luma3DS properly or there is something wrong with your folder structure. It sometimes crashes because Menuhax entrypoint isn't as stable as A9LH. You could consider setting up lesshax, which is a slightly modified version of menuhax that crashes about 15% less or so, but I'd recommend getting LumaCFW/CTRBootManager working and then continuing through with Part4/5 of the guide.

Try to follow the part 2 steps again just in case there's something wrong with your SD structure.

Fair, I have emunand updating now. I will try to get it working with CTRbootmanager after. I am still using CN, not menuhax. Wasn't going to switch until i had it working well.

 

[CrispyYoshi]

Fair, I have emunand updating now. I will try to get it working with CTRbootmanager after. I am still using CN, not menuhax. Wasn't going to switch until i had it working well.

Wait, you are running emunand? If you have a working emunand and CTRBootmanager functional, you're already ready for part 4: https://github.com/Plailect/Guide/wiki/Part-4-(Getting-the-OTP)

EDIT: Well, if updating your emunand doesn't also update your sysnand, then you're definitely running emunand. Then yes, definitely start on part 4 if that's the case.

 

[GreatCrippler]

Wait, you are running emunand? If you have a working emunand and CTRBootmanager functional, you're already ready for part 4: https://github.com/Plailect/Guide/wiki/Part-4-(Getting-the-OTP)

Got there from normal HBL and CN. Will get back to CTRbootmanager next

Put CTRbootmanager Back. Keeps freezing when it tries to open "Luma3DS.dat"

Restarted, and it booted the second time. Hmm.

 

[CrispyYoshi]

Got there from normal HBL and CN. Will get back to CTRbootmanager next

Put CTRbootmanager Back. Keeps freezing when it tries to open "Luma3DS.dat"

Restarted, and it booted the second time. Hmm.

Can I see your boot.cfg? Also, do you have a file called "ropbinpayload_menuhax_...." on your root? Can you copy/paste the whole filename here?

 

[GreatCrippler]

Can I see your boot.cfg? Also, do you have a file called "ropbinpayload_menuhax_...." on your root? Can you copy/paste the whole filename here?

Appreciate it, but I am good. Thanks so much for the help. It's working fine.

 

[CrispyYoshi]

Appreciate it, but I am good. Thanks so much for the help. It's working fine.

Glad you got it sorted out, then! Good luck with the rest of the guide!