The jump table is a frankenstein made of Brahma's jump table, roxas75's jump table, and bootstrap's.
I literally had the three files open, copy/pasted and compared what I though was best.
Still no pasta here.
The jump table is a frankenstein made of Brahma's jump table, roxas75's jump table, and bootstrap's.
I literally had the three files open, copy/pasted and compared what I though was best.
Still no pasta here.
oh alright, I thought it was pasta code. sorry for having called you a liar!
- Joined
- Oct 7, 2007
- Messages
- 4,447
- Trophies
- 3
- Age
- 36
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,829
- Country
Ok tested this thing when I woke up. In sysnand mode, eshop spoof app doesn't work. I'm assuming because it boots 9.6 patched native firm. I would suggest you find a way of live patching 9.2 for sysnand mode at some point. Some folks might want to use eShop. That and the ability to boot into another CFW while in the Cakes would be convenient. 
For me I guess it doesn't matter. I have an early test build that boots sysnand using 9.2 firm. It's not in a user friendly form though and I patched 9.2 firm myself.
I sent him 9.2 patched firm awhile back when I first made it. I'm sure he'll find a way of incorperating it. (hint look at Pasta code. It doesn't use firmlaunch to launch new native firm yet.)
Pasta is open source. There's no harm in using some of it to get sysnand mode working correctly.
EDIT: Just tested and just like with rxMode, DSiWare/GBA VC will work from emunand provided you also have a copy installed to sysnand.
For me I guess it doesn't matter. I have an early test build that boots sysnand using 9.2 firm. It's not in a user friendly form though and I patched 9.2 firm myself.
I sent him 9.2 patched firm awhile back when I first made it. I'm sure he'll find a way of incorperating it. (hint look at Pasta code. It doesn't use firmlaunch to launch new native firm yet.
)Pasta is open source. There's no harm in using some of it to get sysnand mode working correctly.
EDIT: Just tested and just like with rxMode, DSiWare/GBA VC will work from emunand provided you also have a copy installed to sysnand.
Last edited by Apache Thunder,
Well, theoretically, if you don't need emuNAND, it should be as easy as changing the signature patch to http://pastebin.com/wdSUNt1a and replace 00000049 with 00000038 NATIVE_FIRM.Ok tested this thing when I woke up. In sysnand mode, eshop spoof app doesn't work. I'm assuming because it boots 9.6 patched native firm. I would suggest you find a way of live patching 9.2 for sysnand mode at some point. Some folks might want to use eShop. That and the ability to boot into another CFW while in the Cakes would be convenient.
Ok tested this thing when I woke up. In sysnand mode, eshop spoof app doesn't work. I'm assuming because it boots 9.6 patched native firm. I would suggest you find a way of live patching 9.2 for sysnand mode at some point. Some folks might want to use eShop. That and the ability to boot into another CFW while in the Cakes would be convenient.
For me I guess it doesn't matter. I have an early test build that boots sysnand using 9.2 firm. It's not in a user friendly form though and I patched 9.2 firm myself.
I sent him 9.2 patched firm awhile back when I first made it. I'm sure he'll find a way of incorperating it. (hint look at Pasta code. It doesn't use firmlaunch to launch new native firm yet.
Pasta is open source. There's no harm in using some of it to get sysnand mode working correctly.
The problem with that is that the signature patching location differs per firmware. I don't want to have different signature patches for every possible FIRM.
I've also tried to implement the brahma stuff, to continue booting the current FIRM, and it mostly requires changes to the jump_table, but it breaks booting it from the SD card. Though, admittedly, I didn't look much.
I hope the eShop spoofing can be implemented in any other way.
- Joined
- Oct 7, 2007
- Messages
- 4,447
- Trophies
- 3
- Age
- 36
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,829
- Country
Well one way is simply having users download a firmware.bin from CDN that is of the 9.2 version and adding extra code to use that with the specific patches for it.
Of coarse that firmware.bin will have a different name. Like firmware2.bin or something. (and that one could be placed in cakes folder instead since rxTools wouldn't use it)
Of coarse that firmware.bin will have a different name. Like firmware2.bin or something. (and that one could be placed in cakes folder instead since rxTools wouldn't use it)
- Joined
- Oct 7, 2007
- Messages
- 4,447
- Trophies
- 3
- Age
- 36
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,829
- Country
I think the next big project is getting this to boot from 9.x MSET. Then the road to getting it on the n3DS will become much easier.
Sorry to disappoint, but I'm more interested in CIA installation right now.
CIA installation via network?
BTW how to you exactly achieve that, it's a feature on your CFW but nothing is said about that on the first page.
BTW how to you exactly achieve that, it's a feature on your CFW but nothing is said about that on the first page.
Easier method for obtaining firmkey.bin.
Start rxTools, under Decryption Options choose Decrypt Title Keys.
Open rxTools\decTitleKeys.bin under rxTools in a hex editor, copy the 16 bytes after 0004013800000002 to a new file, save it as firmkey.bin
Example with the keys censored, in this case it'd be the line "BBBB...."
Start rxTools, under Decryption Options choose Decrypt Title Keys.
Open rxTools\decTitleKeys.bin under rxTools in a hex editor, copy the 16 bytes after 0004013800000002 to a new file, save it as firmkey.bin
Example with the keys censored, in this case it'd be the line "BBBB...."
Similar threads
