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

  • Thread starter Thread starter chaoskagami
  • Start date Start date
  • Views Views 286,471
  • Replies Replies 2,153
  • Likes Likes 60
Well, I've come up with a way to bypass the most recent ban but, I need Corbenik to design the patch and I already upgraded to B9S
a way to bypass a ban? other than the 3 big methods? well, it may be worth while then. I'd also like to hear more about this patch. hmu with a pm if you'd like.
 
Well, I've come up with a way to bypass the most recent ban but, I need Corbenik to design the patch and I already upgraded to B9S

By that do you mean a way for those already banned to bypass it or do you mean some kind of stealth patch to prevent being detected/banned in the first place? Because while the second should be relatively easy (either make it so it doesn't send any title data even if streetpass is on make it so that only title ids on a whitelist are sent) I am not sure how you could do the first, make a patch to let people already banned play online again.

a way to bypass a ban? other than the 3 big methods? well, it may be worth while then. I'd also like to hear more about this patch. hmu with a pm if you'd like.

Yeah, I would like to as well. Especially if it is one for people who are already banned rather than a stealth patch to prevent a ban.
 
Last edited by nl255,
By that do you mean a way for those already banned to bypass it or do you mean some kind of stealth patch to prevent being detected/banned in the first place? Because while the second should be relatively easy (either make it so it doesn't send any title data even if streetpass is on make it so that only title ids on a whitelist are sent) I am not sure how you could do the first, make a patch to let people already banned play online again.



Yeah, I would like to as well. Especially if it is one for people who are already banned rather than a stealth patch to prevent a ban.
It was for those already banned but, it's temperamental. It doesn't always work so, it may not be the best way if there are other ways to get around it. Out of 10 tries, I got it to work once through manual RAM editing but the friends list or any other home menu applet unloads NTR CFW so I wasn't able to test the extent of the temp-unban. I also need someone who knows bytecode to program this.
 
Corbenik always say "WARNING: Failed to load/patch TWL (and AGB)" and refuse to boot, no matter whether I put them or not.

(Edit) NVM, it's a Slot0x11Key96 issue. It can be booted after getting the 0x11 key even still displays those warnings.
 
Last edited by MelonGx,
I'm stopping development of Corbenik for a number of reasons. Y'all can hate on me; it is what it is. I hope you can at least understand why. The code will stay up, and anyone is welcome to fork. It's open source; I hope it has a future beyond me.

I originally started coding Corbenik because I thought CFW was neat, and given how the community projects were all open source and everyone seemed friendly, it might be fun to get involved. I also had fun initially coding the thing, working through issues, etc...but that changed over time.

With every change made to software such as arm9loaderhax, boot9strap, etc, it gets harder and harder to keep up unless you're a developer of Luma or developer directly linked to Luma. The lack of standard makes things incredibly hard on me, and frankly, I'm burnt out of dealing with issues.

In the end, I've gotten tired of the project. I've gotten tired of dealing with breakage caused by lack of standards friendly to all software. I'm currently developing a game, and I'd rather devote my time to that.

I no longer find development of Corbenik fun, sad to say. At this point, I'd rather take a step back and just stop; go back to being a normal user.

So, unless someone else continues the project, I'm done. Sorry everyone. I don't mean to let you down, but it's how it is.
 
Last edited by chaoskagami,
It was an honor to have worked with you and to have used Corbenik. I hope someone can pick up the code because the scene needs more than just Luma.
At least we still have ReiNAND and CakesFW. Hopefully they don't fall.
 
Last edited by The Catboy,
I'm stopping development as Corbenik for a number of reasons. Y'all can hate on me; it is what it is. I hope you can at least understand why. The code will stay up, and anyone is welcome to fork. It's open source; I hope it has a future beyond me.

I originally started coding Corbenik because I thought CFW was neat, and given how the community projects were all open source and everyone seemed friendly, it might be fun to get involved. I also had fun initially coding the thing, working through issues, etc...but that changed over time.

With every change made to software such as arm9loaderhax, boot9strap, etc, it gets harder and harder to keep up unless you're a developer of Luma or developer directly linked to Luma. The lack of standard makes things incredibly hard on me, and frankly, I'm burnt out of dealing with issues.

In the end, I've gotten tired of the project. I've gotten tired of dealing with breakage caused by lack of standards friendly to all software. I'm currently developing a game, and I'd rather devote my time to that.

I no longer find development of Corbenik fun, sad to say. At this point, I'd rather take a step back and just stop; go back to being a normal user.

So, unless someone else continues the project, I'm done. Sorry everyone. I don't mean to let you down, but it's how it is.
no worries. someone will pick it up.
 
I'm stopping development as Corbenik for a number of reasons. Y'all can hate on me; it is what it is. I hope you can at least understand why. The code will stay up, and anyone is welcome to fork. It's open source; I hope it has a future beyond me.

I originally started coding Corbenik because I thought CFW was neat, and given how the community projects were all open source and everyone seemed friendly, it might be fun to get involved. I also had fun initially coding the thing, working through issues, etc...but that changed over time.

With every change made to software such as arm9loaderhax, boot9strap, etc, it gets harder and harder to keep up unless you're a developer of Luma or developer directly linked to Luma. The lack of standard makes things incredibly hard on me, and frankly, I'm burnt out of dealing with issues.

In the end, I've gotten tired of the project. I've gotten tired of dealing with breakage caused by lack of standards friendly to all software. I'm currently developing a game, and I'd rather devote my time to that.

I no longer find development of Corbenik fun, sad to say. At this point, I'd rather take a step back and just stop; go back to being a normal user.

So, unless someone else continues the project, I'm done. Sorry everyone. I don't mean to let you down, but it's how it is.
I perfectly understand dude, it's your choice. I only hope others understand your choice...

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

It was an honor to have worked with you and to have used Corbenik. I hope someone can pick up the code because the scene needs more than just Luma.
There is ReiNAND...
 
With every change made to software such as arm9loaderhax, boot9strap, etc, it gets harder and harder to keep up unless you're a developer of Luma or developer directly linked to Luma. The lack of standard makes things incredibly hard on me, and frankly, I'm burnt out of dealing with issues.

In the end, I've gotten tired of the project. I've gotten tired of dealing with breakage caused by lack of standards friendly to all software.
I'd like to weigh in on this point, since I contributed to B9S. B9S chose the FIRM format for payloads because, simply put, it allowed for more flexibility while allowing easy portability for existing payloads (you just had to both specify the offset for a FIRM section and the ARM9 entrypoint as the brahma/A9LH payload offset). If your code made use of ARM11, the entrypoint ARM11 waited on changed from 0x1FFFFFF8 to 0x1FFFFFFC to bring it in line with the one used by Nintendo. In B9S 1.2, assuming your FIRM made use of B9S' screen init functionality (so this didn't even affect Luma as an example), the framebuffers were moved from FCRAM (the CakeBrah offset) to VRAM which is their proper place, and the offset is provided via argv (it's argv[1]) to all payloads to avoid future breakages in case it changes again. Nothing else. Since as far as I know Corbenik didn't make use of screen init and had it built-in, the only required change was the ARM11 entrypoint; if things stopped working it was a bug in corbenik (cache issues? we had plenty of those in older Luma with ARM9 <-> ARM11 stuff). No conspiracies with unfriendly new "standards" or anything that only Luma devs know about...
 
Last edited by Aurora Wright,
I'm rather sure I was flushing cache beforehand, assuming libctr9 did it properly. The code on ARM11 was definitely being jumped to; the entrypoint had already been partially changed for firmlaunches, and was fully changed to 0x1FFFFFFC before any of these other issues came into play.

The firmware would properly boot when jumping to k11, but executing screen init would hang (although deinit worked.) All of this previously worked on arm9loaderhax, but somehow broke on boot9strap. It's probably either as you said, cache-related, or somehow a processor exception. I'm not sure.

I don't think I said anything about any conspiracies. TBH, I'm just tired of keeping up with random breakage. It's on my end, yes. I don't have infinite time, and unfortunately I'm only human (and thus imperfect.)
 
I'm stopping development of Corbenik for a number of reasons. Y'all can hate on me; it is what it is. I hope you can at least understand why. The code will stay up, and anyone is welcome to fork. It's open source; I hope it has a future beyond me.

I originally started coding Corbenik because I thought CFW was neat, and given how the community projects were all open source and everyone seemed friendly, it might be fun to get involved. I also had fun initially coding the thing, working through issues, etc...but that changed over time.

With every change made to software such as arm9loaderhax, boot9strap, etc, it gets harder and harder to keep up unless you're a developer of Luma or developer directly linked to Luma. The lack of standard makes things incredibly hard on me, and frankly, I'm burnt out of dealing with issues.

In the end, I've gotten tired of the project. I've gotten tired of dealing with breakage caused by lack of standards friendly to all software. I'm currently developing a game, and I'd rather devote my time to that.

I no longer find development of Corbenik fun, sad to say. At this point, I'd rather take a step back and just stop; go back to being a normal user.

So, unless someone else continues the project, I'm done. Sorry everyone. I don't mean to let you down, but it's how it is.
Aww, my favorite cfw, it dies, please someone continue this.
 

Site & Scene News

Popular threads in this forum