What 3DS type, if it's 2DS maybe it's diffrent (I don't think so but it might just be?)
It is a 2DS yes. But I can't see why it would be different.
What 3DS type, if it's 2DS maybe it's diffrent (I don't think so but it might just be?)
It is a 2DS yes. But I can't see why it would be different.
What 3DS type, if it's 2DS maybe it's diffrent (I don't think so but it might just be?)
Mine also just gives a black screen when you enter the CFW, it wont boot to the system screen. Mines on 4.3.0 -10E the same
I can load it successfully (the payloader) but when I try to run it the top screen stays black.
FW 4.3.0-10E
Not sure about this one. Have you region changed, flashed emuNAND over sysNAND, updated sysNAND from GW mode, anything like that? Maybe the FIRM version is not correct for that firmware because you did any of those things in the past.9.2.0-20E aka. 9.2
The FIRM is the same, I think. So it should work. Maybe brahma itself doesn't work with it?It has a slightly diffrent FW (Wifi controls only software for instance) which might make the offsets in memory different which would mean it wont work. Again I don't know for sure but it could very well be the case.
Can no one help me with my issue of the payloader? I can load it successfully but when I try to run it the top screen stays black.
Yeah dunno.It has a slightly diffrent FW (Wifi controls only software for instance) which might make the offsets in memory different which would mean it wont work. Again I don't know for sure but it could very well be the case.
Not sure about this one. Have you region changed, flashed emuNAND over sysNAND, updated sysNAND from GW mode, anything like that? Maybe the FIRM version is not correct for that firmware because you did any of those things in the past.
The FIRM is the same, I think. So it should work. Maybe brahma itself doesn't work with it?
Here's my custom version/s Separate versions for each firmware we have offsets for...so:N3ds 9.0-9.2O3ds 9.0-9.2O3ds 8.0-8.1O3ds 4.1-4.5Full Menu VersionJust pick the one you want, put the CFW_Loader folder in your /3ds folder and run it from ninjhax. Screen will change colour a few times and boot into home menu. Unless you pick the Full menu version of course, then you just do the samebut pick you version when the menu loads. Enjoy!Attached Files:
CFW_Loader.zip
File size:682.2 KBViews:59
Okay I got a few questions I really hope someone can ask and help me out on this regard:
1) I have my CN copy QR code used by that of Gateway's launcher. Is there a way I can delete that QR code so I can use it for Ninjhax instead since I am now using the MSET exploit to run GW's emuNAND?
2) Is there a way I can use this in conjunction with GW's emuNAND in anyway?
Wouldn't PastaCFW collide with GW in some form?
3) Do I have to run PastaCFW everytime I want to play any DSiWare/GBA VC titles? (This means CN -> HBL -> Run Bra-thing -> Open CIA)
Or can I simply open them up from sysNAND after doing the initial PastaCFW setup and installing the CIAs to sysNAND?
The L+R+X+Y combo, where do I have to do it?1. L+R+X+Y
2. Yes as this is sysNAND only (so no collisions)
3. Yes after each reboot of the system
The L+R+X+Y combo, where do I have to do it?
Right in CN's menu or somewhere else?
As for the rest of the answers, thank you, kind user.
@ LaronX im on a 9.2.0-20e 3dsxl and ive used shadowtrances version
@ Reecey you need to load the cfw then reload ninjhax and install the devmenu cia with FBI
Great!Just in the main menu will do
Again, it's all explained in the op, even with video tutorials.How do you install the devmenu? anyone please
This should now detect the right firmware version automatically. If the firmware is unsupported it will display an error and refuse to load the CFW.
Simply replace the arm9payload.bin file from the OP with this one, load brahma and the arm9payload as usual, and press START to load the CFW once you have verified that the detected firmware version looks correct. When enough people confirm it's working, I will make it autoboot the CFW by default so there is no need to press START.
If people have any problems with it detecting the wrong version, simply tell me the contents of the "FIRM: KERNEL:" line, which firmware it detects and which firmware you actually have and I'll have it fixed shortly. Unless there are errors in the list on 3dbrew that shouldn't be an issue though.
Edit: Added source