Hacking Official Corbenik - Another CFW for advanced users (with bytecode patches!)

[chaoskagami]

I copied all four folders that we created from compiling the latest commit.

bits
module
patch
svc

as well as the arm9loaderhax.bin

7b.bin file is in svc.

I am not sure but all my Retroarch cias error out. AGB reboot works awesome, so let me thank you for that. Great job on everything.

Enable logging and upload the logs, then. Are you running nightlies or stables of retroarch, out of curiousity? Also, maybe try with ErrDisp or Unitinfo on.

 

[Deleted member 117573]

Not sure if I am using stable or nightlies, so I am going to delete the one's I have and install the latest stable. I will enable logging and get the logs for you. It may take a few minutes as I have to take my daughter to school. Thanks for all the support.

 

[chaoskagami]

Not sure if I am using stable or nightlies, so I am going to delete the one's I have and install the latest stable. I will enable logging and get the logs for you. It may take a few minutes as I have to take my daughter to school. Thanks for all the support.

So I just went into *my* copy of retroarch, and you're actually right. Something may have broke. I'm looking into it.

 

[Deleted member 117573]

So I just went into *my* copy of retroarch, and you're actually right. Something broke. I'm looking into it.

After installing latest 1.3.4 stable Retroarch cia and verifying SVC Replacement is enabled all my Retroarch cia launch with the exception of Picodrive and GPSP. I think I read somewhere these 2 specific emulators were affected by the 11.0 FW update. I must have been on the nightlies. Not sure what extra GPSP and Picodrive require. Thanks again for your support.

Here is the log file with SVC Replacement enabled.

Edit: https://gbatemp.net/threads/retroarch-emulation-thread-nightly-builds-included.400913/page-189

Seems emulators that use dynarec do not work on 11.0 firm. The recommendation was to use 10.2/10.4 FW with those Retroarch emulators.

 

[chaoskagami]

After installing latest 1.3.4 stable Retroarch cia and verifying SVC Replacement is enabled all my Retroarch cia launch with the exception of Picodrive and GPSP. I think I read somewhere these 2 specific emulators were affected by the 11.0 FW update. I must have been on the nightlies. Not sure what extra GPSP and Picodrive require. Thanks again for your support.

Here is the log file with SVC Replacement enabled.

You have loader disabled. Any specific reason why? 11.0's loader does ASLR which the replacement does not, and the custom loader does absolutely nothing different unless you enable options for it. That might break retroarch, but IDK.

EDIT: It looks like only one retroarch program failed here, and reinstalling fixed it. I suspect this was just a byproduct of my microSD failing, so w/e

 

[Deleted member 117573]

You have loader disabled. Any specific reason why? 11.0's loader does ASLR which the replacement does not, and the custom loader does absolutely nothing different unless you enable options for it. That might break retroarch, but IDK.

I don't use out of region games and such, and never used the cpu patches for any of my games so I just assumed I did not need any of the loader options enabled. Do you recommend enabling and if yes which options should I enable?

 

[chaoskagami]

I don't use out of region games and such, and never used the cpu patches for any of my games so I just assumed I did not need any of the loader options enabled. Do you recommend enabling and if yes which options should I enable?

Enabling loader and nothing else will at least kill the ASLR and Cubic Ninja/OOT checks, so I'd recommend it.

However the current commit produces a loader too large to fit now, so building from master isn't going to work too well unless I add expansion or cut some code down.

 

[Deleted member 117573]

Enabling loader and nothing else will at least kill the ASLR and Cubic Ninja/OOT checks, so I'd recommend it.

However the current commit produces a loader too large to fit now, so building from master isn't going to work too well unless I add expansion or cut some code down.

This CFW is awesome. Everything working great except for GPSP and Picodrive. I have GBA VC so GPSP is unnecessary. As for Picodrive I can live without it, but will hold out hope I can get it working again sometime in the future. Thank you for all the support and effort you put into your CFW. Thank you again.

 

[chaoskagami]

I'll probably make another release soon; it seems stable, and enough has changed to warrant it. The releases are going to start slowing down.

Most of the obvious broken stuff has since been resolved, and now I'm going to be entirely focused on adding new things here and there, code cleanup, and rewriting the assembler + documenting stuff. I'll go ahead and say that the bytecode format (what's implemented anyways) is also probably stabilized, so future releases won't necessarily need updated patches for any future releases.

EDIT: @stl25 - It looks like at some point during refactoring, svcBackdoor stopped working properly. It's not your fault, I guess.

EDIT: Wow, apparently backdoor has been broken since before release #1. Fail. I'm about to partially revert it.

 

[chaoskagami]

Release time. https://github.com/chaoskagami/corbenik/releases/tag/v0.0.8

• Fixed svcBackdoor, which I apparently broke before I even did release 1. Major oversight. You'll now not blackscreen on retroarch or other applications.
• Courtesy @Wolfvak, code sections can be loaded off the SD now.
• Misc fixes to cache (they were reversely named compared to the rest of corbenik)
• TWL patches were merged together.
• AGB Bootscreen was split out as optional for games that don't pass the logo check.
• SysModule segment resizing should work now - we in-place expand the FIRM image. (I need to PR to Cakes, too - remind me @mid-kid.) This means you can use 10.2 FIRM (but seriously, don't.)
• Configuration should be saved manually prior to booting now - this is because I was repeatedly writing it all over, and there's no real correct way to determine when to save. A dedicated menu option was added.
• Stability.

 

[Temptress Cerise]

Release time. https://github.com/chaoskagami/corbenik/releases/tag/v0.0.8

I am really exited for "Stability." Is this akin to Nintendo's OFW Stability updates? We can't have enough of that~ <3

Anyways, I'll be downloading this in a bit.

 

[chaoskagami]

I am really exited for "Stability." Is this akin to Nintendo's OFW Stability updates? We can't have enough of that~ <3

Anyways, I'll be downloading this in a bit.

There's actually quite a few bugs fixed that I simply forgot, therefore 'stability'.

Maybe a bit different from Nintendo's definition.

 

[Dylan the Tactician]

holy crap am i the only a9lh user that still regularly uses homebrew launcher

 

[chaoskagami]

holy crap am i the only a9lh user that still regularly uses homebrew launcher

The only reason I ever boot it at this point is one or two 3dsx-only homebrew, honestly. Everything else I use is CIA. I doubt you're the only one though.

 

[astronautlevel]

holy crap am i the only a9lh user that still regularly uses homebrew launcher

3dslink is invaluable for testing

 

[chaoskagami]

3dslink is invaluable for testing

I don't see much difference from socketpunch + FBI.

 

[Dylan the Tactician]

WHAT ABOUT HANS AND... HANS!

AND SCREENSHOTS M8S!

--------------------- MERGED ---------------------------

Also I've found FTBrony much more stable on 3dsx version

 

[3xkrazy]

@chaoskagami

Not sure if I missed it or not - do you plan on integrating an arm9 chainloader? It's the main reason why I switched to Luma3ds from CakesFW.

 

[chaoskagami]

WHAT ABOUT HANS AND... HANS!

AND SCREENSHOTS M8S!

It's a CFW. I can implement a FB grab for the purpose of showing the menu, but there's not much to look at, really.

@chaoskagami

Not sure if I missed it or not - do you plan on integrating an arm9 chainloader? It's the main reason why I switched to Luma3ds from CakesFW.

No, that's not in the plans. That's the job for another tool.

 

[Temptress Cerise]

There's actually quite a few bugs fixed that I simply forgot, therefore 'stability'.

Maybe a bit different from Nintendo's definition.

Am I suppose to be doing a clean install or an update?

On a clean install it hangs at Patching firmware. Even with the step through and logging options checked, I am not getting any meaningful info.

Doing an update (just overwriting the files, this doesn't happen and it boots fine)