Hacking MenuHax stuck at yellow screen occasionally what to do?

[subcon959]

You should try the Wii U exploit if you think this is unstable.

 

[SomeGamer]

You should try the Wii U exploit if you think this is unstable.

Or browserhax.

 

[subcon959]

Or browserhax.

Browserhax was about 1 in 3 for me when I used it so not too bad.

However, when I first tried the Wii U hack I went over 100 attempts before it finally worked.

 

[soulskeeper]

Oh yeah, that's true.

Something you could try too is menuhax 2.0 but with the *hax 2.1 ropbin payloads.
Should be able to rename the ropbinpayload_menuhax.bin that you got from installingt hemehax 1.2/1.3 offline, then reinstall menuhax 2.0, then delete the 2.5 ropbin payload that was downloaded when you installed menuhax 2.0 and replace it with your *hax 2.1 payload.

The 2.1 payloads seem to have higher success rate than 2.5 and you lose nothing from using 2.1 on menuhax to boot rxTools so it's worth a shot.

Menuhax 2.0 had a much higher success rate than the previous versions did (it failed aaaaaaalllll the time when you manually used *2.5 payload on menuhax 1.2/1.3, lol), so coupled with 2.1 payloads is probably best. It also boots a tiny bit faster, hehe.

what if I got menuhax 2.0 already installed how should go from there to use the 2.1 payload?

 

[Deleted-236924]

Install 1.2 or 1.3 offline to get the 2.1 ropbin payload, then you rename it to something else.
Then you re-install menuhax 2.0 and rename the 2.1 payload to what the 2.5 payload was named.

 

[soulskeeper]

Install 1.2 or 1.3 offline to get the 2.1 ropbin payload, then you rename it to something else.
Then you re-install menuhax 2.0 and rename the 2.1 payload to what the 2.5 payload was named.

without uninstalling the current menuhax?

 

[Deleted-236924]

Probably a good idea to uninstall the menuhax 2.0 before installing 1.2/1.3 otherwise it might cause problems once you install another one over it, for example I kept getting a black screen telling me an error has occurred at some point after I installed 1.2 or 1.3 don't remember which. Ended up having to start normally into sysnand, uninstalling themehax, then using browserhax to get back into HBL to re-install menuhax properly.

 

[WeedZ]

I've found that every entry point fails in the same way every so often.
Getting stuck on a yellow screen or sometimes a white screen. Happened with oot3dhax, with menuhax, with cubic ninja, with browserhax (that one is already especially unstable), and with yellows8's homebrew launcher loader. Sometimes even just when resetting HBL with L+R+B+Down key combo, regardless of entry point. I think it's just a general unstability with the payloads and the exploit in general. Since it crashes some stuff it might not be possible to guarantee 100% success rate every time so we'll just have to deal with it.

I have an almost 100% fail rate with ninjhax 2.5 on a 10.3U. It will boot after installation, but after that I have to reinstall the exploit or it fails. What's weird is I get a green screen.

 

[soulskeeper]

Probably a good idea to uninstall the menuhax 2.0 before installing 1.2/1.3 otherwise it might cause problems once you install another one over it, for example I kept getting a black screen telling me an error has occurred at some point after I installed 1.2 or 1.3 don't remember which. Ended up having to start normally into sysnand, uninstalling themehax, then using browserhax to get back into HBL to re-install menuhax properly.

can't I just get the payload from you and use it instead of my current payload XD?

 

[Deleted-236924]

I have OLD9.2U payload so unless you are using a north american O3DS on 9.2 sysnand, you wouldn't be able to.
And I can't really make the payloads myself because the installer autodetects firmware, so I can't choose to build ropbin payload for your firmware.

 

[soulskeeper]

I have OLD9.2U payload so unless you are using a north american O3DS on 9.2 sysnand, you wouldn't be able to.
And I can't really make the payloads myself because the installer autodetects firmware, so I can't choose to build ropbin payload for your firmware.

got a usa 9.2 FW o3DS is that ok?

 

[Deleted-236924]

For OLD9.2.0-20U then this should work.
I've modified it to run nhax.3dsx instead of boot.3dsx so either change your boot.3dsx to nhax.3dsx, or open it in HxD yourself to change it to... whatever you want, really. Long as it's 4-characters long.

 

[soulskeeper]

For OLD9.2.0-20U then this should work.
I've modified it to run nhax.3dsx instead of boot.3dsx so either change your boot.3dsx to nhax.3dsx, or open it in HxD yourself to change it to... whatever you want, really. Long as it's 4-characters long.

Thanks mate you're the best

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

just tested it and it works MUCH better! also Thanks for everyone alse who helped !

 

[Naxster]

Oh yeah, that's true.

Something you could try too is menuhax 2.0 but with the *hax 2.1 ropbin payloads.
Should be able to rename the ropbinpayload_menuhax.bin that you got from installingt hemehax 1.2/1.3 offline, then reinstall menuhax 2.0, then delete the 2.5 ropbin payload that was downloaded when you installed menuhax 2.0 and replace it with your *hax 2.1 payload.

The 2.1 payloads seem to have higher success rate than 2.5 and you lose nothing from using 2.1 on menuhax to boot rxTools so it's worth a shot.

Menuhax 2.0 had a much higher success rate than the previous versions did (it failed aaaaaaalllll the time when you manually used *2.5 payload on menuhax 1.2/1.3, lol), so coupled with 2.1 payloads is probably best. It also boots a tiny bit faster, hehe.

Could you please help me with this?
Is it possible for me to do it with my 2DS? or is it only for O3ds?
I've followed this guide Launching rxTools at boot - Menuhax! But i don't quite understand what this hemehax 1.2/1.3 offline is.. Where do i get it?
Also my ropbinplayload is called: ropbinpayload_menuhax_EUR11272_old3ds should i do something with that?

 

[Deleted-236924]

It works on any 2DS or 3DS model as long as you can run menuhax.

Themehax offline
Not sure if that is 1.2 or 1.3, but they'll both give you a *hax 2.1 payload when you install it so it doesn't matter.

When you get the ropbin payload installed to the root of your SD card after installing themehax offline, get it and rename it to something else. Then after you're re-installed menuhax 2.0, you can name your 2.1 payload "ropbinpayload_menuhax_EUR11272_old3ds.bin" and menuhax 2.0 will load *hax 2.1

 

[Naxster]

It works on any 2DS or 3DS model as long as you can run menuhax.

Themehax offline
Not sure if that is 1.2 or 1.3, but they'll both give you a *hax 2.1 payload when you install it so it doesn't matter.

When you get the ropbin payload installed to the root of your SD card after installing themehax offline, get it and rename it to something else. Then after you're re-installed menuhax 2.0, you can name your 2.1 payload "ropbinpayload_menuhax_EUR11272_old3ds.bin" and menuhax 2.0 will load *hax 2.1

Thank you for the reply!

Just so i understand, is this what i should do?
1. I will have to remove/delete my current menuhax
2. put the themehax in my SD root
3. launch homebrew channel
4. install themehax offline (what should i rename?)
5. re-install menuhax and, click "install" inside it, and also choose a button to configure
6. rename the payload
7. done?

 

[Deleted-236924]

3ds folder is the same as the one on root, you put themehax_installer in /3ds/

After you installed themehax offline, rename your ropbinpayload_menuhax.bin file to something else because menuhax 2.0 installer will delete it if you don't rename it.

Then once you've installed menuhax 2.0 again, you just rename the 2.1 ropbin payload the same name as the one that was produced by menuhax 2.0 installer. Then it'll load into *hax 2.1 instead of *2.5 which is better boot rate in my experience.

 

[Naxster]

3ds folder is the same as the one on root, you put themehax_installer in /3ds/

After you installed themehax offline, rename your ropbinpayload_menuhax.bin file to something else because menuhax 2.0 installer will delete it if you don't rename it.

Then once you've installed menuhax 2.0 again, you just rename the 2.1 ropbin payload the same name as the one that was produced by menuhax 2.0 installer. Then it'll load into *hax 2.1 instead of *2.5 which is better boot rate in my experience.

Should i still add the boot.3dsx from CtrBootManager and replace the boot.3dsx that i got from the folder "starter"?

EDIT: It worked!! I love you!!!
Thank you very much!

Is it possible to replace the rxTools logo with something else? Such as the 3DS logo

 

[s3r1alpari4h]

This happens to me often.
The yellow screen means: Menuhax failed to load boot.3dsx from your SD card.
Some things that have caused this for me was holding L too long after the menu hax logo came up (can't confirm this was the actual problem) but I usually just reboot and try again. It's a real annoyance sometimes but it just happens...

 

[Deleted-236924]

This happens to me often.
The yellow screen means: Menuhax failed to load boot.3dsx from your SD card.
Some things that have caused this for me was holding L too long after the menu hax logo came up (can't confirm this was the actual problem) but I usually just reboot and try again. It's a real annoyance sometimes but it just happens...

When it fails to load boot.3dsx is much later on, after the black debug screen with the scrolling text. If it fails to load a .3dsx file it will hang on a red screen.
Yellow screen is just general *hax 2.5 instability it hasn't even gotten to the point where it would load a .3dsx file yet. *hax 2.1 did not have that problem, however the entry point exploit itself can fail and hang on a white screen every so often which may be the fault of the entry point itself, or just a different fault with payloads that makes it hang earlier than yellow screen. What makes me believe white screen is a fault on the entry point's part is because white screen happened regardless of payload (yellow screen only ever happened with *hax 2.5, never got that issue with 2.1 payloads.)

Keep in mind this works by crashing parts of the system and all, not always 100% reliable and things don't always work 100% as intended and we get crashes or hangs. All things considered the success rate is really high still. Also keep in mind 2.5 is still in beta so it should be expected to be less stable than 2.1 was.