That's really useful thanks for the info!Actually, when you switch back to the current MenuHax, you can have MenuHax Installer copy the old file instead of downloading the new one. After making any necessary hex edits to "menuhax_ropbinpayload.bin", make a copy of it and rename it to "menuhaxmanager_input_payload.bin" (both of these should be on the SD card root). Now, when you install the new MenuHax ROP with MenuHax Manager, it will copy that file over instead of downloading the 2.5 payload file from the Internet.
Even if you want to keep your 2.5 payload, keeping a copy named "menuhaxmanager_input_payload.bin" will enable you to reinstall MenuHax from your existing file should anything happen (someone changes your theme, etc.). No need to be online, and your hex edits remain intact if you're using, say, "auto.3dsx" instead of "boot.3dsx" so that you can have CBM without messing up your other *hax payloads.
Just happened to find that information while looking over the MenuHax ReadMe on Github again, seeing if there was a way to run it offline. Looks like I found something I had missed before (and apparently I'm not the only one).
The easiest thing would be to back up your 3ds folder and delete it then download the homebrew starter pack again and the themehax installer. first install the payload with themehax then backup the payload it puts on your sd card then use menuhax installer and replace the payload with the themehax payload from earlier(must be named the same)i dont get it . i downloaded the zip file and when i extract themehax_installer folder to my 3ds folder in my sd it wont extract.
maybe because there is one file that is also named themehax_installer but doesnt have any file extension. so i tried to rename the folder to themehax_installer1 and it extracted successfully. and when i go to HBL, should i choose menuhax installer? because there are no new options to choose when i put themehax_installer on the 3ds. then what ?
by the way, i also have the folder named menuhax_manager in the 3ds folder. I'm confused if should I remove that and put themehax installer.
please help me
Thanks for this! I will add this to the guide!I have a mixture of results, it seems to work well with ReiNAND coldboot on N3DS fine but can break rxTools coldboot on O3DS.
N3DS Results
N3DS (9.2 sysNAND/10.5 emuNAND via ReiNAND)
Setup: Boot > MenuHax > CTR Boot Manager > ReiNAND
Before: 90% coldboot success (10% freezing at yellow screen)
After: 100% coldboot success
N3DS XL (9.2 sysNAND/10.5 emuNAND via ReiNAND)
Setup: Boot > MenuHax > CTR Boot Manager > ReiNAND
Before: 90% coldboot success (10% freezing at yellow screen)
After: 100% coldboot success
O3DS Results
O3DS (9.2 sysNAND/10.4 emuNAND via rxTools)
Setup: Boot > MenuHax > CTR Boot Manager > rxTools
Before: 50% coldboot success (50% freezing at yellow screen)
After: 0% coldboot success
Alternative setup: Boot > MenuHax > CTR Boot Manager > HB Launcher
Before: 50% coldboot success (50% freezing at yellow screen)
After: 90% coldboot success (10% freezing at white screen)
Symptoms:
O3DS will successfully boot past MenuHax 90% of the time while freezing on a white screen 10% of the time.
If MenuHax successfully passes, the console will go through CTR Boot Manager autoboot and then attempt to rxTools emuNAND but freezes on black screens. 10% of the time the rxTools splash screen will flash once, 90% of the time nothing appears and it just freezes. Holding down R and manually booting rxTools from the CTR Boot Manager menu still works fine.
Reverting and reinstalling the latest version of MenuHax will allow rxTools to work again.
Seems like an issue with rxTools but can't verify if that really is the case.
You got the same results on N3DS & N3DS XL? wow, it's like they are totally the same system apart from the screen. /sI have a mixture of results, it seems to work well with ReiNAND coldboot on N3DS fine but can break rxTools coldboot on O3DS.
N3DS Results
N3DS (9.2 sysNAND/10.5 emuNAND via ReiNAND)
Setup: Boot > MenuHax > CTR Boot Manager > ReiNAND
Before: 90% coldboot success (10% freezing at yellow screen)
After: 100% coldboot success
N3DS XL (9.2 sysNAND/10.5 emuNAND via ReiNAND)
Setup: Boot > MenuHax > CTR Boot Manager > ReiNAND
Before: 90% coldboot success (10% freezing at yellow screen)
After: 100% coldboot success
Whoops, it was supposed to highlight that one unit was on 9.0 sysNAND and the other on 9.2 sysNAND, but I missed that. It's been corrected now.You got the same results on N3DS & N3DS XL? wow, it's like they are totally the same system apart from the screen. /s
Yeah thats an important part to improve boot rate into emunand. I should add that to the guide, I will later.In Ctrbm , I set the autofix from 2 to 0 and my boot rate went from 5/10 to 9/10
Well it clearly says MenuHAX so you need some kind of entry point to use it, why not Browserhax? Works all the way to 10.5Offtopic: Is there anyway to install menuhax without browserhax (or any other exploit)?
Ironfall if you are on 10-10.3, Browser, CubicNinja and Ocarina of Time. These are your only options.Offtopic: Is there anyway to install menuhax without browserhax (or any other exploit)?
Sysnand 9.2. It looks like it may only work on the new 3ds but nothing wrong with trying if it doesnt work reinstall menuhax normallySorry if this is dumb, but by "9.2 menuhax," do you mean my sysNAND must be on 9.2 or emuNAND? I've updated my emuNAND above 9.2 so I'm just wondering.
Also, has anyone tested this on Old 3DS yet?
I have a mixture of results, it seems to work well with ReiNAND coldboot on N3DS fine but can break rxTools coldboot on O3DS.
Symptoms:
O3DS will successfully boot past MenuHax 90% of the time while freezing on a white screen 10% of the time.
If MenuHax successfully passes, the console will go through CTR Boot Manager autoboot and then attempt to rxTools emuNAND but freezes on black screens. 10% of the time the rxTools splash screen will flash once, 90% of the time nothing appears and it just freezes. Holding down R and manually booting rxTools from the CTR Boot Manager menu still works fine.
Reverting and reinstalling the latest version of MenuHax will allow rxTools to work again.
Seems like an issue with rxTools but can't verify if that really is the case.
You need to fool around with the autobootfix in your boot.cfg 8 for the old 3ds and 2 for the new 3ds. It may be worth messing with that with other numbers too. Mine is set to 2 or 3 on my n3ds and i get a 95% bootrate from a cold boot.The same for me but on stock MenuHax payload!
CtrBootManager even hangs in menu with 1 second autoboon while trying to start rxTools or Cakes. Everything works fine on manual boot selection.
So this topic may be fixing the yellow screen case, but the rest is CtrBootMenu and/or CFW compatibility issues.
Using a boot image also helps, so you don't get the pixelated mess on the top screen.