I know Luma3DS has the patches built into the A9LH version and I think the patches should be built into the MenuHAX version. So you should just be able to launch the App if you have the payloads properly set up (basically either not renaming your stock launcher or having changed the payloads yourself.)
I am not sure how menuhax works with Luma3DS, since I don't have any system running MenuHAX
Someone correct me if I'm wrong but iirc you need to have the sysnand twl patched if using emunand. As luma only patches the emunand.Just installed TWL Slot-1 Launcher, but still getting a black screens...
Someone correct me if I'm wrong but iirc you need to have the sysnand twl patched if using emunand. As luma only patches the emunand.
Luma also patches sysNAND, both for TWL and AGB.Someone correct me if I'm wrong but iirc you need to have the sysnand twl patched if using emunand. As luma only patches the emunand.
just copy the boot.3dsx provided with luma3ds menuhax folder and boot it via menuhaxhow do I make this work with CTRBootManager?
Try do downgrade if it fails make a new one and update it and use the firm file like it saysso guys i made a new sd card and redhand because i was getting the nfirm error while trying to downgrade... i guess because while i was doing the Plailect last night i updated to 10.7 than to be safe i updated again and when i was doing that Nintendo mustve did the 11 update at the same time... so today i found out i had 11 on the redhand which was causing the nfirm error i was getting.
So im on part 4 If your RedNAND / EmuNAND has been updated to version 11.0.0 or higher, you must either put the NTR firmware.bin from part 5 into the /luma/ folder or restore your EmuNAND from a backup of an older version to be able to downgrade. This is because 11.0.0's FIRM broke downgrading. im little confuse on this.. Right now my redhand has 9.2 i notice they removed the step in the description for updating to the latest version. So do i still update to 11 than put the firmware.bin in luma than do the downgrade to 2.1?
Try do downgrade if it fails make a new one and update it and use the firm file like it says
You have to edit the config file for it to point to the location of either the luma boot.3dsx or the luma .dat file. If using the dat file it needs an offset of 0x12000 iirc(its been a while)how do I make this work with CTRBootManager?
YupSo do the downgrade when the rehand is on 9.2 first? than if it fails update and do what they say?
dat kept freezing for me but the boot.3dsx works.You have to edit the config file for it to point to the location of either the luma boot.3dsx or the luma .dat file. If using the dat file it needs an offset of 0x12000 iirc(its been a while)
Did you add the offset in the ctr config?dat kept freezing for me but the boot.3dsx works.
Yes continue. It was to clear out twl crap if people had it.K it worked this time downgrading from 9.2 to 2.1 so the nfirm error was indeed from the 11 update... why did i update 2 times last night i probably wouldve had my 3ds hacked by now lol..... do i go threw all the other steps now? also what was the point updating to the new version than downgrading?
Yes continue. It was to clear out twl crap if people had it.
Are you using updated emunand9 and a fixed uncart?just updated the console to fw 11 not sure if its related..
however trying to launch UNCART or emunand 9 luma payloads, they give a black screen..
decrypt9 is working fine..
i even tried to change the file names from x_uncart to start_uncart (which had decript9 before) and they don't work..
got last version of luma3ds, 64 gb sd card 32k cluster
