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

[Svaethier]

This is incorrect for CakesFW as well as Corbenik. Neither need a path changer. All you need to do is to rename the arm9loaderhax.bin.

EDIT: Also, looking through the thread he only said that the path changer was needed for Luma.

Yes you can but you need to patch it with pathchanger since ShadowNAND will only load /homebrew/boot.bin and not arm9loaderhax.bin
That is what he said to someone on his thread :/

Edit: OK, just making sure I can use corbenik with shadowNAND. Thanks for the help.

 

[Shadowhand]

Yes you can but you need to patch it with pathchanger since ShadowNAND will only load /homebrew/boot.bin and not arm9loaderhax.bin
That is what he said to someone on his thread :/

To make it clear, reboot patches do NOT go through ShadowNAND. You can have an arm9loaderhax.bin in the root of your SD as well as the same file as boot.bin in /homebrew/, and Luma will work without pathchanger.

 

[chaoskagami]

Yes you can but you need to patch it with pathchanger since ShadowNAND will only load /homebrew/boot.bin and not arm9loaderhax.bin
That is what he said to someone on his thread :/

Edit: OK, just making sure I can use corbenik with shadowNAND. Thanks for the help.

Corbenik does not require a path changer, since it directly uses a pre-patched firmware file from its' own directory. The reboot patch never hits the actual corbenik code.

To make it clear, reboot patches do NOT go through ShadowNAND. You can have an arm9loaderhax.bin in the root of your SD as well as the same file as boot.bin in /homebrew/, and Luma will work without pathchanger.

Thanks, by the way. ShadowNAND is kind of neat. I may end up using it as a secondary someday.

 

[Shadowhand]

Corbenik does not require a path changer, since it directly uses a pre-patched firmware file from its' own directory. The reboot patch never hits the actual corbenik code.



Thanks, by the way. ShadowNAND is kind of neat. I may end up using it as a secondary someday.

Thank you. I'll be trying to implement external loader/injector loading so devs have a nice thing to test with without lots of hassle. Also A9NC support is on its way.

 

[Svaethier]

OK I renamed corbenik's loaderhax bin to boot.bin and it boots now.

 

[chaoskagami]

Thank you. I'll be trying to implement external loader/injector loading so devs have a nice thing to test with without lots of hassle. Also A9NC support is on its way.

Corbenik will still be my primary, but who doesn't like the idea of a backup CFW in the NAND? Especially since I've killed two microSDs at this point. Being able to boot and play carts without a working SD would be a godsend. I'm waiting for it to stabilize a bit first and hopefully have ShadowNAND be the fallback option - because, you know, CFW dev and all.

A9NC will sadly be of limited utility to me since there's a lot more than just the binary needed to test here. Corbenik isn't really self-contained.

 

[Svaethier]

Both this cfw and shadowNAND are awesome things, can't wait for ShadowNAND to mature in the near future and for whatever new things corbenik will come out with in future builds not sure if you guys hear this as much as you should but thank you for all that you have done so far!

 

[chaoskagami]

Unfortunate news - @AuroraWright's latest arm9loaderhax push that merged SI and non-SI appears to have busted Corbenik somehow. If you're using shadowNAND, delebile's fork or an older version of his, you'll remain unaffected.

Screeninit has a few issues (garbage on bottom screen from not clearing it), but that doesn't seem to be the root cause here.

I'm not yet sure why this is happening, but just a quick FYI for anyone. I'm not sure if anyone will hit this or not. Let me know.

 

[chaoskagami]

0.1.1 is up.

More minor changes to enhance stab-- okay, let's not go there again.
This is a small release:

• Add a chainloader to Corbenik. This is optional and can be cut out at compile time. Depending on which build people prefer, I'll only build one or the other during release at some point. The option to disable will remain in the source. For now, the default build is done with CHAINLOADER=1 (That's enabled.)
• Fixed a bug with garbage on the framebuffer with screeninit (I think. Please test!)
• A small number of grammatical/spelling issues were rectified by @gnmmarechal. For the fact that I never once touched spellcheck and don't use autocompletion, that's pretty good all things considered.
• A few changes to patches and an experimental one based on some of @Subv's work on the svc permission check in contrib. This may be a severe security hazard, but has some use. Use caution.

This release is fairly minor. If you have no interest in chainloading, and do not use a no-screeninit arm9loaderhax payload, you do not need to update. No core features have changed. Patches do not need to be updated.

Not mentioned there is that reverse emuNAND was removed for now. I have a better solution on the way.

 

[DjoeN]

@chaoskagami

So i updated corbenik to latest build and have reproduced my error again.
Removing the config file and rebooting into menu fixed it.

 

[chaoskagami]

@chaoskagami

So i updated corbenik to latest build and have reproduced my error again.
Removing the config file and rebooting into menu fixed it.

The culprit is 'Disable SVC Permission Checks' it seems. Turn it off. It apparently doesn't work here either.

WOOOOOOOOOOOOOOOLFVAAAAAAAAAAAAAAK. @Wolfvak.

EDIT: Looks like it was relative to the wrong segment. By the way, none of you should be enabling that anyways. It's a security risk and doesn't benefit you at the moment.

 

[Wolfvak]

The culprit is 'Disable SVC Permission Checks' it seems. Turn it off. It apparently doesn't work here either.

WOOOOOOOOOOOOOOOLFVAAAAAAAAAAAAAAK. @Wolfvak.

EDIT: Looks like it was relative to the wrong segment. By the way, none of you should be enabling that anyways. It's a security risk and doesn't benefit you at the moment.

I did say it was completely untested, didn't I?
Also, you should really clean the screen before running Corbenik's menu - I tested a BA9 payload that didn't clear the screen on exit.
It was hilarious

 

[chaoskagami]

I did say it was completely untested, didn't I?

You did, come to think of it. Eh, whatever.

 

[Wolfvak]

Corbenik will still be my primary, but who doesn't like the idea of a backup CFW in the NAND?

Also, I'd like to point out KGB was technically the first public CFW on stage2

SUPPORT THE ORIGINAL, NOT THE IMITATION! /s

 

[chaoskagami]

Also, I'd like to point out KGB was technically the first public CFW on stage2

SUPPORT THE ORIGINAL, NOT THE IMITATION /s

I almost wanted to point that out in the thread over there when Tux said 'Give Aurora Credit' but I chose not to. No sense stirring waves. Nice rxShit/Gateway reference, btw. That line at the end of the readme, man. Gets me every time. ;P

As an aside, KGB is still set as private on github, so I couldn't clone and test if I wanted to. How's it going, by the way? :/

(Edit: Actually, that's probably better off in PMs, isn't it? OT and all.)

 

[Wolfvak]

I almost wanted to point that out in the thread over there when Tux said 'Give Aurora Credit' but I chose not to. No sense stirring waves. Nice rxShit/Gateway reference, btw. That line at the end of the readme, man. Gets me every time. ;P

As an aside, KGB is still set as private on github, so I couldn't clone and test if I wanted to. How's it going, by the way? :/

It's open now, and it wasn't private, I completely removed it lol.
I've been fighting against N3DS decryption but thanks to Cakes' source I think I figured it out properly. 9.2 and 11.0 work perfectly, and loader is replaced with yifanlu's.
I strongly advise against using it with 9.5, in case anyone reads this.

 

[chaoskagami]

It's open now, and it wasn't private, I completely removed it lol.
I've been fighting against N3DS decryption but thanks to Cakes' source I think I figured it out properly. 9.2 and 11.0 work perfectly, and loader is replaced with yifanlu's.
I strongly advise against using it with 9.5, in case anyone reads this.

Good to know. Still an altstage2? Are you using a9lh v2 with the new key (for more storage? If so, I need to update one console.)

 

[Wolfvak]

Good to know. Still an altstage2? Are you using a9lh v2 with the new key (for more storage? If so, I need to update one console.)

You can use it standalone (useful for testing without a hardmod) or as an altstage2. I have no idea what you mean about the "(for more storage?)" part - that only benefits stage1 (and not by a lot).

 

[chaoskagami]

You can use it standalone (useful for testing without a hardmod) or as an altstage2. I have no idea what you mean about the "(for more storage?)" part - that only benefits stage1 (and not by a lot).

I'm nearing snooze-o-clock. Why was I thinking that the new key benefited stage2...?

Anyways, good to know. I'll probably set it up as an altstage2 as a backup. ShadowNAND is still a bit too invasive for other CFW devs at the moment.

 

[Svaethier]

OT: shadowNAND works wonders for me.
On Topic: thanks for the chainloader, now I can get rid of ctrbootmanager