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

  • Thread starter Thread starter chaoskagami
  • Start date Start date
  • Views Views 287,556
  • Replies Replies 2,153
  • Likes Likes 60
Do you have reboot enabled, out of curiousity? Maybe dev2 causes the console to immediately firmlaunch reboot. I know Luma automatically applies reboot hooks, so maybe that's the issue here. If reboot hooks aren't applied, you would end up back in the menu on firmlaunch.

I'll admit I've never messed around with anything aside from AltMenu in Config, but can you try that?
Yes I have reboot enabled, also tried it without reboot enabled, same thing happens so here's a log file, maybe this will help figure out the problem.
 

Attachments

Yes I have reboot enabled, also tried it without reboot enabled, same thing happens so here's a log file, maybe this will help figure out the problem.

Try disabling the TWL and AGB patches. There's known issues with them right now on O3DS.
 
Try disabling the TWL and AGB patches. There's known issues with them right now on O3DS.
I could try that, without reboot patch the screen does light up for a quick second before going black then back to configuration menu.

Edit: so agb and twl patches conflict with dev menu stuff I guess as it boots up fine with them disabled.
 
Last edited by Svaethier,
  • Like
Reactions: chaoskagami
I could try that, without reboot patch the screen does light up for a quick second before going black then back to configuration menu.

Please try it. I know you have an o3ds from the logs - there would be two underscores if it needed to test the arm9bin.

There's been multiple people in the thread who have reported weird problems with reboot and the AGB/TWL patches on o3ds, and that's the next thing I'm going to try and fix once I get my O3DS all set up.
 
Edit: so agb and twl patches conflict with dev menu stuff I guess as it boots up fine with them disabled.

They don't conflict. TWL and AGB are just buggy at the moment on O3DS. Glad to see it works now, though. I plan to heavily test and fix this before next release, so this won't be an issue by then.
 
  • Like
Reactions: Temptress Cerise
They don't conflict. TWL and AGB are just buggy at the moment on O3DS. Glad to see it works now, though. I plan to heavily test and fix this before next release, so this won't be an issue by then.
That's odd. If I remember correctly, the patterns in O3DS and N3DS AGB/TWL FIRMs are the same, at least guiding myself by Steveice10's gist

Or is there other reason for this? 23 pages and I still haven't checked out the entire source...
 
That's odd. If I remember correctly, the patterns in O3DS and N3DS AGB/TWL FIRMs are the same, at least guiding myself by Steveice10's gist

Or is there other reason for this? 23 pages and I still haven't checked out the entire source...

Right now, I don't have them implemented as dynamic - I'm using `seek` since there isn't enough context on some patterns (I need to get more for them by poking thru in a hex editor.)

Otherwise, they're exactly the same. The plan is to stop being lazy and convert to dynamic with the `find` opcode to squash this once and for all (and also search in the correct sections rather than relative to the firm image)

EDIT: Also, technically some patterns differ in TWL firm by a byte.
 
Last edited by chaoskagami,
Any reason devunit info patch crashes back to the configuration screen? I'm trying something with the menu to dev2 instead of prod with config app on my 3DS.
dev2 changes the memory layout if I remember correctly, reboot hooks not being applied right away is probably the issue

edit: somehow missed this whole page
 
Last edited by ketal,
Right now, I don't have them implemented as dynamic - I'm using `seek` since there isn't enough context on some patterns (I need to get more for them by poking thru in a hex editor.)

Otherwise, they're exactly the same. The plan is to stop being lazy and convert to dynamic with the `find` opcode to squash this once and for all (and also search in the correct sections rather than relative to the firm image)

EDIT: Also, technically some patterns differ in TWL firm by a byte.
Can't you do something along the lines of:

Code:
... header goes here

rel agb

... patches in common go here

test n3ds
jmp (location where N3DS patches are stored)

... (patches for O3DS go here)
jmp (location of final nop)

... (patches for N3DS go here)

nop (just to work as a sort of label)

Maybe there's something wrong with it, to be honest I'm not that familiar with the VM yet and haven't memorized all of it's opcodes (not that there are too many)
 
Can't you do something along the lines of:

Code:
... header goes here

rel agb

... patches in common go here

test n3ds
jmp (location where N3DS patches are stored)

... (patches for O3DS go here)
jmp (location of final nop)

... (patches for N3DS go here)

nop (just to work as a sort of label)

Maybe there's something wrong with it, to be honest I'm not that familiar with the VM yet and haven't memorized all of it's opcodes (not that there are too many)

That's how the old one worked (with static offsets via seek). Go check git, I pushed code this morning. I'm doing something similar but it needs more testing.

Also, n3ds is an opcode not an operand to test.

To be clear, TWL is the problem with dynamic, not AGB. The AGB ones are simple but the patterns differ for some in TWL and there's nothing unique usable as context. I suspect the actual crashes are caused by something wrong in the assembler.
 
Last edited by chaoskagami,
That's how the old one worked (with static offsets via seek). Go check git, I pushed code this morning. I'm doing something similar but it needs more testing.

Also, n3ds is an opcode not an operand to test.

To be clear, TWL is the problem with dynamic, not AGB. The AGB ones are simple but the patterns differ for some in TWL and there's nothing unique usable as context.
When I meant "N3DS / O3DS patches go here" I meant dynamic ones, with find. As well as the ones were they have patterns in common
 
When I meant "N3DS / O3DS patches go here" I meant dynamic ones, with find. As well as the ones were they have patterns in common

I know what you meant. I just already pushed it to git. Way ahead of you. ;p
 
  • Like
Reactions: Wolfvak
I built the latest commit, but when I configure it I am getting the following screen:
Error.jpg


Here is the log file:
 

Attachments

I built the latest commit, but when I configure it I am getting the following screen:
View attachment 52555

Here is the log file:

I broke something temporarily in the find opcode. Please pull. Also, don't expect git to be stable. It may build, but working...is another issue. I'd prefer people only report issues against the stable. If you experience catastrophic boot failure with git, chances are I already know.

That one was fixed by f15899f5.
 
Last edited by chaoskagami,
Latest commit built and AGB working for me N3DS XL. Haven't tested TWL patches. Great work.

Edit: TWL patch from latest commit did not work, however I copied the twl_fix.vco from the 0.0.8 release to the patch directory and TWL works. I can play my blocked NDS flashcarts (GW blue and R4i (DSTT clone))
 
Last edited by Deleted member 117573,
I have been using the AGB and TWL since it was first introduced and it doesn't seem to be giving me any hassles. :unsure: Although at this rate as soon as I post this, something will happen.
Dirty or Clean Install? Clean Install it should hang with AGB Bootscreen on and enabled, at least on o3DS.
 
  • Like
Reactions: chaoskagami
Dirty or Clean Install? Clean Install it should hang with AGB Bootscreen on and enabled, at least on o3DS.
Clean install, AGB Bootscreen enabled, games working just fine. I am not using the latest commit though, I am just using 0.0.8.
 
Last edited by The Catboy,
I noticed that, but I thought I was hallucinating. No clue, honestly. And you're actually the first one to mention it. Congrats. :toot:

Either way, it doesn't affect anything negatively so it's not high on my list to fix. Oh, and I should mention that left and right deliberately skip up and down by five.

Thanks! ;)

Always doing a clean install after a new build and I have big problems selecting the options and patches every time but only on that one unit. It always jumps two or three selections ;)
 

Site & Scene News

Popular threads in this forum