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

[doggomando]

IT WORKS NOW! It boots me to black screen...

 

[chaoskagami]

Maybe because i haven't name it correctly, i renamed firmkey.bin to native.key.
EDIT: nvm

Just to be clear, native_firm, twl_firm, and agb_firm have different keys, and the keys are different between o3ds and n3ds. The keys for twl_firm and agb_firm should be named twl.key and agb.key, respectively.

About this https://github.com/chaoskagami/corbenik/wiki/Building
Everything builds just fine on Windows, the only thing that won't work as-is are the bash scripts,
but those are nothing crucial.

That's cool. Well, I guess given cygwin you can probably build then.

IT WORKS NOW! It boots me to black screen...

What patches did you enable, what firmware are you using as native, what system software is on your sysnand, etc? You can just kill the power if it crashes like that, btw. It won't hurt anything.

Also, please upload loader.log if you have it in the folder.

(Corbenik is a little slower to boot than other CFWs, too.)

 

[DjoeN]

Nice, if you build with "make full" it takes a little longer to build but you get the locales folder and all gameid files
(like in the release.zip )

Note:
Everything builds fine under Windows 10 now by just copying python.exe to python2.exe (not renaming, cause some other projects need python.exe) in the \python27 folder.

 

[chaoskagami]

Nice, if you build with "make full" it takes a little longer to build but you get the locales folder and all gameid files
(like in the release.zip )

Note:
Everything builds fine under Windows 10 now by just copying pyhton.exe to python2.exe (not renaming, cause some other projects need python.exe) in the \python27 folder.

Apparently my makefiles were better written than I thought. Oh, you could also use mklink for python2. People seem to forget that NTFS does hardlinks/symlinks.

On the locales: they're only generated for games that have one language supported to prevent any false positives. The langemu code isn't terribly well tested, so use it at your own peril for now. For people wanting to add custom files, some of the values are different because I'm planning to switch to proper locale names like en_US/ja_JP/zh_CN eventually.

 

[DjoeN]

Apparently my makefiles were better written than I thought. Oh, you could also use mklink for python2. People seem to forget that NTFS does hardlinks/symlinks.

...

You learn something everyday , so i looked up and read up on mklink. (Never knew about mklink)
- so i removed my 'python2.exe' in the folder c:\python27
- started a cmd with admin rights in c:\python27 folder
- typed 'mklink python2.exe c:\python27\python.exe' to create a hardlink
- this created a 0byte python2.exe in the python27 folder
- wiped corbenik folder on my d: and git cloned and ran make all

Worked perfect
Thanks for this info

(I know i could aswell leave the copy of python.exe as python2.exe there, but i like to try out new stuff everyday )

 

[chaoskagami]

Okay, making another release now.

Notable additions:
* EmuNAND support (only one right now, but this is due to lack of menu, not code)
* Screen-init for people with non-screeninit a9lh
* Loader now has rel commands for the other segments due to an oversight
* I fixed up some very wrong offset code that somehow worked before.

 

[laharl22]

Okay, making another release now.

Notable additions:
* EmuNAND support (only one right now, but this is due to lack of menu, not code)
* Screen-init for people with non-screeninit a9lh
* Loader now has rel commands for the other segments due to an oversight
* I fixed up some very wrong offset code that somehow worked before.

thanks the noob i am wait this emunand support yeahhh.when you will add cetk support for decrypt fw ?

 

[chaoskagami]

thanks the noob i am wait this emunand support yeahhh.when you will add cetk support for decrypt fw ?

Next release I'll re-add it, but you still need a native firmkey to boot. There's no way around that.

(I probably should have waited to release, since I just added multiple emunand support. Oh well. As an aside, does anyone here have more than 10 Emunands? I set that as the max, but it's an arbitrary limit.)

 

[laharl22]

the option need to not unchek uncheked automaticly how to fix ?the cross when i chek dispareaer at the rebbot and my emunand black screen

 

[chronoss]

Okay, making another release now.

Notable additions:
* EmuNAND support (only one right now, but this is due to lack of menu, not code)
* Screen-init for people with non-screeninit a9lh
* Loader now has rel commands for the other segments due to an oversight
* I fixed up some very wrong offset code that somehow worked before.

Emunand work well but "Autoboot" doesn't work

 

[chaoskagami]

Autoboot with EmuNAND, specifically? Yeah, I noticed that afterwards. The config file isn't getting saved just from ticking that, so next boot it doesn't use emunand. As a workaround, check the option called 'Reconfigured? (DO NOT UNCHECK' to force resaving the config and cache.

That was another oversight that I fixed in the subsequent commit. I can make another release since there's been another bunch of fixes, but it's getting to the point where I really need to slow down. If I keep releasing, there's going to keep being bugs.

 

[laharl22]

release today?for me it boot on sys but on emunand black screen

 

[chaoskagami]

release today?

Sure. I mean, the issue is fixed in git (sort of) so I can do so.

I'm practically releasing every commit now though, so this is going to slow down. It's better if I fix every bug reported between them rather than just one known one.

EDIT: DONE.

 

[a9lh-1user]

Thanks for that CFW!
The best i've seen in a long time with many room for more great stuff to come.

 

[chronoss]

Autoboot with EmuNAND, specifically? Yeah, I noticed that afterwards. The config file isn't getting saved just from ticking that, so next boot it doesn't use emunand. As a workaround, check the option called 'Reconfigured? (DO NOT UNCHECK' to force resaving the config and cache.

That was another oversight that I fixed in the subsequent commit. I can make another release since there's been another bunch of fixes, but it's getting to the point where I really need to slow down. If I keep releasing, there's going to keep being bugs.

Doesn't work

 

[gnmmarechal]

I'm making an Updater for this based on my easyRPG Updater.

Sent from my Nokia 3310 using Tapatalk

 

[chaoskagami]

Doesn't work

Enable Logging and upload the logs then, please? 'Doesn't work' doesn't help me fix stuff.

EDIT: Also, what version is your emunand? I've only tested 9.2 - 11.0.

I'm making an Updater for this based on my easyRPG Updater.

Sent from my Nokia 3310 using Tapatalk

Go ahead, I guess? Just don't be surprised if I write an official updater someday.

 

[Wolfvak]

I'm making an Updater for this based on my easyRPG Updater.

Sent from my Nokia 3310 using Tapatalk

Seeing how alpha this is, besides the fact that it doesn't work for everyone I'd say you should wait until it's a bit more mature. The author himself has said that a lot of things might change, and as such it'd break the updater.

It's your call anyways

 

[chaoskagami]

Seeing how alpha this is, besides the fact that it doesn't work for everyone I'd say you should wait until it's a bit more mature. The author himself has said that a lot of things might change, and as such it'd break the updater.

It's your call anyways

I would honestly prefer people just manually updated, anyways. There's a reason I haven't seen autoupdaters for cakes.

If the bytecode changes, that needs to get refetched too, and configuration information might need to be nuked between versions. It's not as simple as Luma.

 

[gnmmarechal]

I would honestly prefer people just manually updated, anyways. There's a reason I haven't seen autoupdaters for cakes.

If the bytecode changes, that needs to get refetched too, and configuration information might need to be nuked between versions. It's not as simple as Luma.

Its LUA, I can easily implement something as a clean install. I can mark an update as incompatible with the latest and force deletion of current settings upon extraction of the new files

Sent from my Nokia 3310 using Tapatalk