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

[chaoskagami]

Ok, I had these trying to build it again

linking loader.elf
/tmp/ccfqI7Lz.ltrans0.ltrans.o: In function `main':
<artificial>:(.text.startup+0x19e0): undefined reference to `svcCreateCodeSet'
<artificial>:(.text.startup+0x19fc): undefined reference to `svcCreateProcess'
collect2: error: ld returned 1 exit status
/opt/devkitpro/devkitARM/3ds_rules:39: recipe for target '/home/erikus/SOURCES/corbenik/external/loader/loader.elf' failed
make[3]: *** [/home/erikus/SOURCES/corbenik/external/loader/loader.elf] Error 1
Makefile:107: recipe for target 'build' failed
make[2]: *** [build] Error 2
make[2]: Leaving directory '/home/erikus/SOURCES/corbenik/external/loader'
Makefile:24: recipe for target 'loader' failed
make[1]: *** [loader] Error 2
make[1]: Leaving directory '/home/erikus/SOURCES/corbenik/external'
Makefile:78: recipe for target 'external' failed
make: *** [external] Error 2

It looks like that the problem is devkitARM, but i just updated it 2 days ago

If you updated devkitARM, you now have a stable version of ctrulib. Recompile ctrulib from git.

EDIT: As you can see from the source - https://github.com/smealum/ctrulib/blob/v1.1.0/libctru/source/svc.s the stable ctrulib doesn't implement wrappers for those.

 

[Gray_Jack]

If you updated devkitARM, you now have a stable version of ctrulib. Recompile ctrulib from git.

EDIT: As you can see from the source - https://github.com/smealum/ctrulib/blob/v1.1.0/libctru/source/svc.s the stable ctrulib doesn't implement wrappers for those.

Thanks, It worked :3

Btw, I got too bored with so much stability lmao, so... how do I do a rom hack using corbenik?

 

[chaoskagami]

Thanks, It worked :3

Btw, I got too bored with so much stability lmao, so... how do I do a rom hack using corbenik?

The only thing you can do is patch code, so the answer is not yet. For now? LayeredFS, HANS, SaltySD or a custom update are your choices.

I'm still doing RE and research on that front. No promises. It's slow going.

 

[Gray_Jack]

The only thing you can do is patch code, so the answer is not yet. For now? LayeredFS, HANS, SaltySD or a custom update are your choices.

I'm still doing RE and research on that front. No promises. It's slow going.

Thanks :3

 

[chaoskagami]

Why am I still awake

@gnmmarechal is going to hate me for this, but anyways, official nightlies courtesy (ab)use of github's infrastructure and a cron job on my computer. https://github.com/chaoskagami/skeith

These have an alternate prefix of /skeith (and a name change) so they can coexist with stable releases.

 

[gnmmarechal]

Why am I still awake

@gnmmarechal is going to hate me for this, but anyways, official nightlies courtesy (ab)use of github's infrastructure and a cron job on my computer. https://github.com/chaoskagami/skeith

These have an alternate prefix of /skeith (and a name change) so they can coexist with stable releases.

Not going to hate you lel
Gonna update the updater, I suppose. Somehow.
The change in directory will make it somewhat harder. I wonder how I should handle this.

 

[chaoskagami]

Not going to hate you lel
Gonna update the updater, I suppose. Somehow.

Since the releases are actually IN the git repo, you can just fetch from the raw links for the repo like so:
https://github.com/chaoskagami/skeith/raw/master/rel/release.zip
and you will always get the latest.

The commit it's built against is always in the bot's message, so you can probably parse the info output from git commands.

 

[gnmmarechal]

Since the releases are actually IN the git repo, you can just fetch from the raw links for the repo like so:
https://github.com/chaoskagami/skeith/raw/master/rel/release.zip
and you will always get the latest.

no, I know that. But the rest of the updater, I wonder how I should handle it given the directory change.

 

[chaoskagami]

no, I know that. But the rest of the updater, I wonder how I should handle it given the directory change.

I had always intended for the official nightly to be able to coexist with stable, incidentally. I'm not really sure how you should handle it, but, well...sorry? :<

 

[gnmmarechal]

I had always intended for the official nightly to be able to coexist with stable, incidentally. I'm not really sure how you should handle it, but, well...sorry? :<

hum, I'd rather allow the updater to update to the official nightlies than use my own. But, if I can't figure out a way of making the updater update to the latest nightly of Skeith, I guess I'll have to use my own builds x.x.

I'll have to figure how to handle it. Oh well, for today, at the very least, I'll continue use my own nightlies (until I update the updater).

 

[chaoskagami]

hum, I'd rather allow the updater to update to the official nightlies than use my own. But, if I can't figure out a way of making the updater update to the latest nightly of Skeith, I guess I'll have to use my own builds x.x.

I'll have to figure how to handle it. Oh well, for today, at the very least, I'll continue use my own nightlies (until I update the updater).

So you'd have to make the updater update the updater to be able to update with updates? (haha)

My head hurts. Time to sleep for reals.

 

[gnmmarechal]

So you'd have to make the updater update the updater to be able to update with updates? (haha)

My head hurts. Time to sleep for reals.

The updater is capable of updating itself. Btw, before you go to sleep, if I compile the latest commit, does the text default to Corbenik or Skeith?

 

[gnmmarechal]

RIP. It seems free users can only have 1 cron job on the server. Oh well.

Time to change the script I already have so it downloads this as well.

 

[chaoskagami]

The updater is capable of updating itself. Btw, before you go to sleep, if I compile the latest commit, does the text default to Corbenik or Skeith?

Compiling corbenik itself will always produce an output named corbenik.

That's done via manually providing fw_name and fw_folder to make from my cron job/repo.

 

[laharl22]

Since the releases are actually IN the git repo, you can just fetch from the raw links for the repo like so:
https://github.com/chaoskagami/skeith/raw/master/rel/release.zip
and you will always get the latest.

The commit it's built against is always in the bot's message, so you can probably parse the info output from git commands.

this is the build with latest commits ?

 

[gnmmarechal]

Compiling corbenik itself will always produce an output named corbenik.

That's done via manually providing fw_name and fw_folder to make from my cron job/repo.

oh god, Skeith includes locale.

RIP updater users when I update the updater.

 

[chaoskagami]

oh god, Skeith includes locale.

RIP updater users when I update the updater.

Sorry~

It is a separate root, after all. Times like these I wish FAT had symlinks.

 

[gnmmarechal]

Sorry~

It is a separate root, after all. Times like these I wish FAT had symlinks.

I could always keep the option of using Corbenik-UN and give users the choice, though Skeith would be the default. (I'm thinking of me actually, lol, as it's extremely boring to wait 10+mins cuz of locale, and I update every commit with UN.)

 

[laharl22]

why the folder on release are not corbenik now ?

 

[gnmmarechal]

why the folder on release are not corbenik now ?

It's the nightly build, and Chaoskagami wants it to coexist with Corbenik stable.

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

@chaoskagami The lazy way of fixing the updater would be replacing every instance of the word "corbenik" with "skeith" in the updater & server, and make a separate app just for Skeith. Since it's intended for devs anyway, I suppose it wouldn't hurt anyone.
Hum. I'll try to figure something out.




NOW GO TO SLEEP