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

  • Thread starter Thread starter chaoskagami
  • Start date Start date
  • Views Views 287,167
  • Replies Replies 2,153
  • Likes Likes 60
It's a region check bypass. I should probably rename it for clarity.



I quoted the wrong post and it's too late now, but are you sure you had emuNAND disabled?
Yes, completely sure. I even double-checked before sending the log. If you want, I can take a picture with my phone to show you...
 
Yes, completely sure. I even double-checked before sending the log. If you want, I can take a picture with my phone to show you...

Well, reading the log through, you had emuNAND ticked, went out of the configuration, went in, went out, went in, disabled emuNAND, then booted. At least from how it looks, anyways. It was off during the actual boot process in the end of that log.

Either way, a picture is unhelpful; it won't tell me anything the log doesn't. I'll add this to the list of things I need to look into.
 
  • Like
Reactions: Gray_Jack
Well, reading the log through, you had emuNAND ticked, went out of the configuration, went in, went out, went in, disabled emuNAND, then booted. At least from how it looks, anyways. It was off during the actual boot process in the end of that log.

Either way, a picture is unhelpful; it won't tell me anything the log doesn't. I'll add this to the list of things I need to look into.
Weird, I never went back into the config after ticking Verbose and Logging. I also had never touched the EmuNAND option...
 
"Firmlaunch failed, returning to menu"

nvm, I had to add FIRMs and CETKs lol
 
Last edited by ,
So I decided to update the the latest working nightly but it doesn't boot pokemon moon, just black screens. The old stable corbenik build boots the game just fine, same setup that's in the stable is in the nightly build too :/
So you did something wrong, cause it boots just fine with the latest commits, but I dunno what you did wrong
 
Last edited by Svaethier,
I even took my firm files from corbenik folder putting them inside my skeith to see if that helps, that doesn't even help. I use the corbenik updater app too but I doubt that causes any issues.
Well, I never used the updater, so I dunno if there is a bug in it or something like it
Talk to @gnmmarechal
 
for an unknown reason, high memory games stopped working for no apparent reason once. It was fixed by doing a fresh install.I don't think it is related to the updater, but I cannot really tell you what it is. The updater grabs files from the Jenkins server, too.
It could be an issue related to doing a dirty installation instead of a clean one, I don't know. The updater just moves the old files to a different directory, downloads and extracts Skeith/Corbenik and moves the native/agb/etc to the new directory, then moves the payloads to the new /boot subdirectory.


Additionally, I tried to reproduce the issue, I couldn't. The updater seems to be working fine. It could be due to the settings not being cleared between installations if you choose "keep config" in the updater, but it is working for me.

Sent from my cave of despair where I collect souls
 
Last edited by gnmmarechal,
I tried even doing a clean install by deleting skeith folder and a9lh bin then copying over a fresh one then transferring the twl, agb and firm files from my corbenik folder to it, same thing happens unfortunately. Someone said something could be broken with how high memory games are handled with o3ds systems with this nightly build.
 
I tried even doing a clean install by deleting skeith folder and a9lh bin then copying over a fresh one then transferring the twl, agb and firm files from my corbenik folder to it, same thing happens unfortunately. Someone said something could be broken with how high memory games are handled with o3ds systems with this nightly build.
It works fine for me.

Sent from my cave of despair where I collect souls
 
Last edited by Svaethier,
Well I'm not sure what I could be then, can't be any of the options I have as the same ones work fine with the corbenik setup I have, my firm files aren't bad otherwise skeith wouldn't boot, nothing on my SD root can't be causing this I doubt even though its a big mess.

My SD root and skeith/lib/firmware folder:
http://imgur.com/r178FcN
http://imgur.com/k6LLUIw
http://imgur.com/BlTCpjK
http://imgur.com/H63uC4p
http://imgur.com/jeuuen0
http://imgur.com/G2a61WO
Try setting it up from scratch using the bash script included in the archive, if you can't run it, open it with notepad, download the files and place them in the correct place manually.
 
The Mystery Machine patches don't seem to be working, tested on Moon and Y. Have they not been updated for the latest Pokemon update, or have I screwed up somewhere?
 
The Mystery Machine patches don't seem to be working, tested on Moon and Y. Have they not been updated for the latest Pokemon update, or have I screwed up somewhere?
Have you entered the codes that are on the mystery machine website?
 
Yes, of course I have. That's why I'm posting here, because it doesn't work.

It throws up the standard 'this is not a valid code' or whatever error.
After you inputed the code, did you fill the rest with zeros?
X/Y OR/AS does that automatically, S/M does not.
 

Site & Scene News

Popular threads in this forum