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

  • Thread starter Thread starter chaoskagami
  • Start date Start date
  • Views Views 287,545
  • Replies Replies 2,153
  • Likes Likes 60
Mizuki and CakesFW :)
(forgett RxTools! because they are not A9LH compatible ATM!)
 
Last edited by ,
Yes. 0.0.9 works. :)

Are you absolutely 100% sure it works in 0.0.9? Because as I sit here testing, it ain't working in ANY revision even going back to 0.0.6. Ugh.

EDIT: @Orkna - Okay, so there's a very odd set of conditions to trigger this, so it's either an ordering issue or a global variable conflict. Can you test master now? It *should* work.
 
Last edited by chaoskagami,
Are you absolutely 100% sure it works in 0.0.9? Because as I sit here testing, it ain't working in ANY revision even going back to 0.0.6. Ugh.

EDIT: @Orkna - Okay, so there's a very odd set of conditions to trigger this, so it's either an ordering issue or a global variable conflict. Can you test master now? It *should* work.

Yes. master works now! Thank you!
 
Yes. master works now! Thank you!

Ayy, good. One less bug now. I'm going to hopefully finetune delays now, so hopefully the next few commits will fix your random jumping around.
 
  • Like
Reactions: Orkna
Last edited by hii915,
we need a tutorial on this for the semi newbs :)

I just cannot find the firmkey anywhere :(

This really isn't intended for newbies at all, so I'm not going to attempt to paint it as such. It just isn't.

I'd prefer anyone who considers themselves a newb in any sense not use it - there's nothing wrong with the other options for CFW. They're safer, stable, and there's no risk of bricking. This on the other hand is experimental and still quite unstable, but by the same token is extremely powerful in the right hands.

Anyways, the firmkey is the same as the one used in Cakes which is usually named `firmkey.bin` there. Since Plailect removed Cakes from the Guide, the links are no longer there to the files, and github doesn't expose wiki history without going back in revisions.

It IS still possible to boot another CFW and reboot into Corbenik to get the firmkeys. I think D9 also may be able to decrypt FIRMs as well (going by the commit log.)
 
This really isn't intended for newbies at all, so I'm not going to attempt to paint it as such. It just isn't.

I'd prefer anyone who considers themselves a newb in any sense not use it - there's nothing wrong with the other options for CFW. They're safer, stable, and there's no risk of bricking. This on the other hand is experimental and still quite unstable, but by the same token is extremely powerful in the right hands.

Anyways, the firmkey is the same as the one used in Cakes which is usually named `firmkey.bin` there. Since Plailect removed Cakes from the Guide, the links are no longer there to the files, and github doesn't expose wiki history without going back in revisions.

It IS still possible to boot another CFW and reboot into Corbenik to get the firmkeys. I think D9 also may be able to decrypt FIRMs as well (going by the commit log.)
thanks
 
thanks!

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


I just cannot find the firmkey anywhere :(
That ISO site -> CFW Discussions -> CakesFW -> later pages -> build 175 (if not mistaken). Although think twice before installing it - Luma provides you with great features while removing the risk of bricking
 
  • Like
Reactions: chaoskagami
I already had a firmkey.bin from my original O3DS hack so I went through all the info I could find to see how it was obtained, using the old one to test my results. Of course, after ages of not working I realised I was obtaining the N3DS firmkey and they were different.

Bah humbug. :blink::blush:

@chaoskagami want me to write up how I got them?

O3DS key SHA1: 9fc07590adfb2c9fc8ab6e0e0f654233dbf3a02f
N3DS key SHA1: daafdb699a48877dd6b33d92c48e37632c8928bf

(shout at me if those are not correct)
 
Last edited by Kirtai,
I already had a firmkey.bin from my original O3DS hack so I went through all the info I could find to see how it was obtained, using the old one to test my results. Of course, after ages of not working I realised I was obtaining the N3DS firmkey and they were different.

Bah humbug. :blink::blush:

@chaoskagami want me to write up how I got them?

O3DS key SHA1: 9fc07590adfb2c9fc8ab6e0e0f654233dbf3a02f
N3DS key SHA1: 83afe00855407b2e9ce5c610cfa1a933d4a10bf5

(shout at me if those are not correct)

IDK about the O3DS one. The N3DS sha1 is definitely wrong. N3DS and O3DS use different firmkeys.

Code:
[17:13:25 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/native.key
daafdb699a48877dd6b33d92c48e37632c8928bf */media/sd/corbenik/keys/native.key
[17:17:29 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/agb.key 
9ff90dc848b81e5c91a4e1e01c915db0f24d487f */media/sd/corbenik/keys/agb.key
[17:17:37 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/twl.key 
7b8597cce5b817346f9c9e5dfc071b6156d80af3 */media/sd/corbenik/keys/twl.key
 
Last edited by chaoskagami,
IDK about the O3DS one. The N3DS sha1 is definitely wrong. N3DS and O3DS use different firmkeys.

Code:
[17:13:25 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/native.key
daafdb699a48877dd6b33d92c48e37632c8928bf */media/sd/corbenik/keys/native.key
[17:17:29 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/agb.key
9ff90dc848b81e5c91a4e1e01c915db0f24d487f */media/sd/corbenik/keys/agb.key
[17:17:37 !!! voile Corbenik] # sha1sum -b /media/sd/corbenik/keys/twl.key
7b8597cce5b817346f9c9e5dfc071b6156d80af3 */media/sd/corbenik/keys/twl.key
Yes, you're right. I somehow copied the SHA1 of the file after editing but before saving it.
Sorry about that and fixed my post
 
Yes, you're right. I somehow copied the SHA1 of the file after editing but before saving it.
Sorry about that and fixed my post

I am curious about how you obtained them, though. To be clear, there was no Cakes/Luma/Decrypt9 involved?
 

Site & Scene News

Popular threads in this forum