Homebrew [Release] CHMM2 - Custom Home Menu Manager 2

  • Thread starter Thread starter Rinnegatamante
  • Start date Start date
  • Views Views 921,332
  • Replies Replies 2,512
  • Likes Likes 110
You can't, it is oversight in CHMM2.5 currently for automatically false detecting the mode for unlinked emunand users such as ourselves. This is why currently I am not using CHMM2.5


https://gbatemp.net/threads/release...kages-with-custom-and-official-themes.401081/
I can't use the Howeling Theme Tool because I don't have admin access on my pc :/

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

https://github.com/Rinnegatamante/CHMM2/blob/master/source/index.lua#L235

CHMM2 checks for "yhemeManage.bin"; if it exists, then it uses "menuhax mode" and will install themes in a way that won't break menuhax. this is why you have go to to menuhax_manager and delete there (in the NAND you want to disable it for) to fix it.
Will this mess up my menuhax for booting?
 
I can't use the Howeling Theme Tool because I don't have admin access on my pc :/

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


Will this mess up my menuhax for booting?
if your NANDs are unlinked, deleting it from emunand won't do anything to sysnand menuhax
 
I can't use the Howeling Theme Tool because I don't have admin access on my pc :/

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


Will this mess up my menuhax for booting?
Yes. This is why it is silly there is no option for user to manually switch this since I know creator of this tool knows about how themehax is being used by some, I am sure. This is why this feature, while nice, should have had user manual input for it, in tandem with automatic detection. Nothing wrong with automatic detection but it can be so wrong.
 
Yes. This is why it is silly there is no option for user to manually switch this since I know creator of this tool knows about how themehax is being used by some, I am sure. This is why this feature, while nice, should have had user manual input for it, in tandem with automatic detection. Nothing wrong with automatic detection but it can be so wrong.
except it won't mess up sysnand menuhax if your NANDs are unlinked and you go to delete it in emunand. extdata is not shared across unlinked NANDs.
 
except it won't mess up sysnand menuhax if your NANDs are unlinked and you go to delete it in emunand. extdata is not shared across unlinked NANDs.

The problem is we are talking about deleting the payload binary of themehax, that is not in EXTdata it is quite clearly in root of your memory card. Do not call me stupid if I say deletion of a binary makes execution of said binary impossible. While the nands are not linked anymore the detection of said BIN still happens and that would mean a broken menuhax. I do not know even how can you mix between extdata and menuhax payload in root of your card this freely.
 
The problem is we are talking about deleting the payload binary of themehax, that is not in EXTdata it is quite clearly in root of your memory card. Do not call me stupid if I say deletion of a binary makes execution of said binary impossible. While the nands are not linked anymore the detection of said BIN still happens and that would mean a broken menuhax. I do not know even how can you mix between extdata and menuhax payload in root of your card this freely.
So.. what do I do lol
 
The problem is we are talking about deleting the payload binary of themehax, that is not in EXTdata it is quite clearly in root of your memory card. Do not call me stupid if I say deletion of a binary makes execution of said binary impossible. While the nands are not linked anymore the detection of said BIN still happens and that would mean a broken menuhax. I do not know even how can you mix between extdata and menuhax payload in root of your card this freely.
...it doesn't delete the ropbin payload at the root. if it does, then it won't delete them for other system versions.
 
...it doesn't delete the ropbin payload at the root. if it does, then it won't delete them for other system versions.
I'm guessing this file was taken over to emuNAND when I made it and it cloned sysNAND to emuNAND, but maybe I'm wrong? And I have to delete it within emuNAND?
 
in fact, I just tested deleting menuhax from sysnand and the file "ropbinpayload_menuhax_USA12288_new3ds.bin" was not deleted
 
...it doesn't delete the ropbin payload at the root. if it does, then it won't delete them for other system versions.
but the problem is that CHMM2 is making an detection for that bin. Going into menuhax manager won't do much when that bin in root of your card is what CHMM2 is detecting. Like said; this is why CHMM2.6 should stick to this feature, but make it manually switchable. You already said it detects the mode by looking for a BIN and I know neither of us does not have 10.3 payload, but only the 9.2 one for sysnand. This is not a unlinked nand problem as much as CHMM2 uses very simple detection method so unlinked nand users get this forced menuhax mode which does not do good for us. This is why I switched to using CIA theme builder for now.
 
but the problem is that CHMM2 is making an detection for that bin. Going into menuhax manager won't do much when that bin in root of your card is what CHMM2 is detecting. Like said; this is why CHMM2.6 should stick to this feature, but make it manually switchable. You already said it detects the mode by looking for a BIN and I know neither of us does not have 10.3 payload, but only the 9.2 one for sysnand. This is not a unlinked nand problem as much as CHMM2 uses very simple detection method so unlinked nand users get this forced menuhax mode which does not do good for us. This is why I switched to using CIA theme builder for now.
if you actually read one of my earlier posts, it looks for yhemeManage.bin in ext data of the NAND you're using it in. this gets deleted when you delete menuhax. the ropbin does not.
 
if you actually read one of my earlier posts, it looks for yhemeManage.bin in ext data of the NAND you're using it in. this gets deleted when you delete menuhax. the ropbin does not.
Alright, I was mixing the two, sorry for the confusion. I have not used menuhax much at all myself and did not know it leaves such traces since used to be that simple way to get rid of it is to just switch theme in main menu.
 
  • Like
Reactions: ihaveahax
Alright, I was mixing the two, sorry for the confusion. I have not used menuhax much at all myself and did not know it leaves such traces since used to be that simple way to get rid of it is to just switch theme in main menu.
the switch to separate files for themes (yhemeManage.bin, yodyCache.bin, etc.) is likely due to shufflehax for 10.2 and 10.3. this is yellows8's decision, not Rinnegatamante's or mine's. detecting yhemeManage.bin is simply the easiest way to tell if someone's using menuhax. :)
 
the switch to separate files for themes (yhemeManage.bin, yodyCache.bin, etc.) is likely due to shufflehax for 10.2 and 10.3. this is yellows8's decision, not Rinnegatamante's or mine's. detecting yhemeManage.bin is simply the easiest way to tell if someone's using menuhax. :)
Sure, I was not thinking something like that exists since like said, for me, poweruser but a user nevertheless; it seems easiest "uninstall" of the menuhax is to just switch a theme, this is what I have been doing to get rid of it myself.
 
Q) I get "cannot initialize Sound module" error when using CIA/3DS version, how can i solve?
A) You need a DSP firmware (dspfirm.cdc) to use CHMM2 as CIA/3DS version. You can dump it using DSP Firmware Dumper, uncart, braindump or Decrypt9.

Noob question, where put the dspfirm.cdc and whats is the best tool to dump the file?
 

Site & Scene News

Popular threads in this forum