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

[The Catboy]

Well, on the upside the latest nightly should mitigate the garbage as well as fix the unreliability on nonscreeninit.

Turns out in the nightlies I made some stupid mistakes during a refactor - the framebuffer struct being missing would cause problems, which was always the case on nonscreeninit unless FCRAM persisted for long enough to be non-null. There was a few fprintfs pre-screeninit - which caused garbage on SI and immediate hardlocks on Non-SI.

Admittedly, that was a stupid mistake but I think the stable is unaffected by this as it was before that particular change. I made screen brightness an option - that was around when this was introduced since previously the config file was always loaded post-screeninit, and now it's loaded pre-screeninit. =_=

Remember; I never said nightlies were stable.

It's true that that's usually a problem. I've mitigated this by rebasing my screeninit code on newer Luma which does a GPU clear (and sidesteps the issue.) Garbage is gone. Permanently.

Broken nightlies are something to be expected, even Luma3DS has had it's fair share of broken nightlies. But at least you caught it!
Still, I am glad to see there is a fix coming along!

 

[kezkez]

I think it's an actual issue, believe it or not, and actually went and reopened it on github. A few other people can repro it and I finally managed to as well, so I'm doubtful that it's a9lh or a failing SD's fault. Nonscreeninit a9lh seems to tickle it the wrong way, so try renaming to _si.bin and see if that improves the situation (at the cost of garbage which I'm going to fix)

I'm using prebuilts (I'm lazy, heh), which don't include the minicfw nor unified the stage2.

 

[chaoskagami]

I'm using prebuilts (I'm lazy, heh), which don't include the minicfw nor unified the stage2.

Little too late there, grab a nightly. I highly recommend this if you are using one of the bugged nightlies.

 

[kezkez]

Little too late there, grab a nightly. I highly recommend this if you are using one of the bugged nightlies.

I don't like the overhead added by that minicfw and other things, I'll probably rebuild delebile's (it should work with aurora's installer anyway)

 

[thisisallowed]

I tried to run it but it's stuck on Decrypting exefs for firm, what do I do?

 

[chaoskagami]

I tried to run it but it's stuck on Decrypting exefs for firm, what do I do?

Evidently you didn't read the README, particularly the 'reporting issues' part.

Reporting issues
If you think you've found a bug, please do the following first, to save me some time:

• Check if a recently enabled patch is the cause of the issue. If so, you should include this in the report.
• Enable Logging and Verbose in Options then Save Configuration and retrieve the files /corbenik/var/log/boot.log and /corbenik/var/log/loader.log if they exist. I will want them. Do not report bugs without them, unless they are not created with the above enabled.
• Please at least try to reproduce the bug from a clean installation.
• Try to reproduce the problem from another CFW like luma or cakes, optionally.

So first; answer these questions for me:

• O3ds, or N3ds?
• How are you loading Corbenik?
• If you press A at the error, does it shut off the console?
• Have you tried a clean install?
• Do you have logs with Verbose and Logging enabled? If so, please upload them.

 

[thisisallowed]

Evidently you didn't read the README, particularly the 'reporting issues' part.



So first; answer these questions for me:

• O3ds, or N3ds?
• How are you loading Corbenik?
• If you press A at the error, does it shut off the console?
• Have you tried a clean install?
• Do you have logs with Verbose and Logging enabled? If so, please upload them.

N3DS
A9LH V2 stable
No errors, it's just stuck on Decrypting exefs for firm
Where are the logs?
What is a clean install? On a formatted SD card? Then no. I used the n3ds_firm.sh file, copied the arm9loaderhax.bin and the skeith folder

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

Evidently you didn't read the README, particularly the 'reporting issues' part.



So first; answer these questions for me:

• O3ds, or N3ds?
• How are you loading Corbenik?
• If you press A at the error, does it shut off the console?
• Have you tried a clean install?
• Do you have logs with Verbose and Logging enabled? If so, please upload them.

I enabled logging yet no log files
I have wierd 1.82GB nand if that helps

 

[chaoskagami]

Where are the logs?

The logs are at /skeith/var/log/*. Of course, this is also in the README. =_=

What is a clean install? On a formatted SD card? Then no. I used the n3ds_firm.sh file, copied the arm9loaderhax.bin and the skeith folder
I enabled logging yet no log files

A "clean install" is where if you have previously had it installed, you delete it before updating.

Anyways, I know at this point you didn't read the README. It's not a 'here's how to use' thing, it's more of a manpage, so please just read it, for both your sake and mine.

Anyways, not having log files makes no sense. I'll have to do a checkover of the code when I can (e.g. not right now.) The weird 1.82GB nand has nothing to do with it, afaik. Let me just restate; nightlies are not expected to work all the time.

 

[thisisallowed]

The logs are at /skeith/var/log/*. Of course, this is also in the README. =_=



A "clean install" is where if you have previously had it installed, you delete it before updating.

Anyways, I know at this point you didn't read the README. It's not a 'here's how to use' thing, it's more of a manpage, so please just read it, for both your sake and mine.

Anyways, not having log files makes no sense. I'll have to do a checkover of the code when I can (e.g. not right now.) The weird 1.82GB nand has nothing to do with it, afaik. Let me just restate; nightlies are not expected to work all the time.

I did read the readme, but just the installing and setup part. I double posted due to being stupid and not reading the other part.
Also forgot to mention, is the 11key96.key supposed to be 16 bytes? It may be it...

 

[chaoskagami]

I did read the readme, but just the installing and setup part. I double posted due to being stupid and not reading the other part.
Also forgot to mention, is the 11key96.key supposed to be 16 bytes? It may be it...

16 bytes is correct. The content should start with 42 3F. You have it located at /skeith/share/keys/11Key96.key or /slot0x11key96.bin, correct?

 

[thisisallowed]

16 bytes is correct. The content should start with 42 3F. You have it located at /skeith/share/keys/11Key96.key or /slot0x11key96.bin, correct?

Yes

 

[chaoskagami]

Yes

Okay, I'll look into this a bit later, since it sounds like a bug to me. I don't have any answers at the moment, but it should not be softlocking on that message, tbh, and didn't while I was testing.

Again, git isn't expected to be stable. *shrug*

 

[thisisallowed]

Okay, I'll look into this a bit later, since it sounds like a bug to me. I don't have any answers at the moment, but it should not be softlocking on that message, tbh, and didn't while I was testing.

Again, git isn't expected to be stable. *shrug*

I used the stable on my 1.82GB nand New 3DS and got this
Config file loaded.
Saving config...
Loading firmware...
FIRM load triggered.
Loading NATIVE_FIRM
Loaded FIRM off filesystem
Read firmkey from filesystem.
Decrypting FIRM
Decrypting FIRM container
Decrypting ExeFs for FIRM
Data abort.
cpsr:800000df sp:27effef0 lr:0000ffff
r0:23f05648 r1:e4f9aa00 r2:e4f9aa00 r3:0000ffff
r4:10009000 r5:e4f9aa10 r6:059fee60 r7:e4f9aa00
r8:e4f9aa00 r9:10000000 r10:0000ffff r11:10000000
r12:27efff48
Cannot continue. Halting.

 

[Elveman]

(resolved?)

 

[chaoskagami]

(resolved?)

No, I can't reproduce it the bug by @thisisallowed. Kind of impossible to fix a bug without an obvious cause.

The only thing I can think of is that the FIRM he's providing is corrupt somehow.

 

[astronautlevel]

No, I can't reproduce it the bug by @thisisallowed. Kind of impossible to fix a bug without an obvious cause.

The only thing I can think of is that the FIRM he's providing is corrupt somehow.

I'm actually getting the exact same error on my n3ds using the latest stable version.

 

[thisisallowed]

I'm actually getting the exact same error on my n3ds using the latest stable version.

I fix
Don't Use ftpd

 

[chaoskagami]

I'm actually getting the exact same error on my n3ds using the latest stable version.

Can you post the sha256sum of the FIRMs?

This is really troubling to me because I literally cannot determine a possible cause in my code, nor can I reproduce it.

 

[astronautlevel]

Can you post the sha256sum of the FIRMs?

This is really troubling to me because I literally cannot determine a possible cause in my code, nor can I reproduce it.

Yeah, looks like the nfirm was somehow corrupted while I was transferring files onto my new SD card.

Sorry, that should've been like the first thing I checked, but I'm pretty sleep deprived right now >.>

 

[chaoskagami]

Yeah, looks like the nfirm was somehow corrupted while I was transferring files onto my new SD card.

Sorry, that should've been like the first thing I checked, but I'm pretty sleep deprived right now >.>

I've done that before, but yeah. I kind of figured. I may want to do better error checking, regardless. >_<