Hacking Pasta CFW - A CFW that allows unsigned CIA to be installed on Old and New 3DS! (required ninjhax)

  • Thread starter Thread starter capito27
  • Start date Start date
  • Views Views 1,427,042
  • Replies Replies 6,595
  • Likes Likes 123
Status
Not open for further replies.
It is a 2DS yes. But I can't see why it would be different.

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.
 
  • Like
Reactions: Margen67
What 3DS type, if it's 2DS maybe it's diffrent (I don't think so but it might just be?)

It shouldn't 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 :unsure:
I can load it successfully (the payloader) but when I try to run it the top screen stays black.
FW 4.3.0-10E

Did either of you downgrade with the GW launcher? Maybe that causes issues, since it's not a full downgrade. Also read below.
9.2.0-20E aka. 9.2
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.

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.
The FIRM is the same, I think. So it should work. Maybe brahma itself doesn't work with it?
 
  • Like
Reactions: Margen67 and Reecey
Ive got it working now the guy above just use the files from page 1 dont use the others they dont work on 4.3.0 10E. Mines boots but how do you install the devmenu?
 
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.
Yeah dunno.

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?

I didn't I didn't only modification I ever did was ninjhax and that was just a GB emulator and the coin thing.
 
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?
 
@ LaronX im on a 9.2.0-20e 3dsxl and ive used shadowtrances version

Here's my custom version/s :)
Separate versions for each firmware we have offsets for...so:​
N3ds 9.0-9.2​
O3ds 9.0-9.2​
O3ds 8.0-8.1​
O3ds 4.1-4.5​
Full Menu Version​
Just 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:


@ Reecey you need to load the cfw then reload ninjhax and install the devmenu cia with FBI
 
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?

1. L+R+X+Y
2. Yes as this is sysNAND only (so no collisions)
3. Yes after each reboot of the system
 
  • Like
Reactions: Margen67
@ 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

Thanks man, whats FBI? I'm only a GW user all this CFW business is brand new to me, am a virgin! I could do with some links/help etc..
 
  • Like
Reactions: Margen67
capito27 As people have mentioned, it would be a very good idea to put this up on GitHub. I can help manage the repo if you like :)
Better if people can make pull requests to get their changes merged into one codebase, rather than a bunch of people creating their own modded version of it. It makes collaboration much easier too :)
 
valyr: I did that. When starting the loader I the the message:

" AN error has occurred, forcing the software to close. The system will now restart. (Unsaved data may be lost)"

After it restarted I tried again but it kept saying the same. I tried both the version in the folder saying 9.0-9.2 and the one in the Menu_version folder.
 
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

Tested this and it worked fine on my N3DS running 9.0.0.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum