Tutorial More-or-less Catch-All Tutorial

[Kylezo]

11. Menuhax should now lead you to the CTRBootManager screen.

I've got a blackscreen freeze on this step. What do? Debug runs and everything, screen flashes colors, then black.

/e: dropped boot.cfg from ctrbootmgr zip into root. This was not noted anywhere in the guide.

new problem:

16. Advanced > Install FBI > emuNAND > Inject FBI.
17. Open rxTools.

what happens for step 16b when it says "Choose source action: B. Keep X. Delete"?

I can no longer get into HBL and ctr crashes to blackscreen freeze if I don't select an action within a few seconds. If I choose HBL, it loads up some pretty colors on bottom screen then freezes.

 

[gangs_08]

Someone tried to downgrade a 2DS ? Was it successful / brickrate ?

 

[gangs_08]

Pingo released that tool to fix ttp files. Should i use a fixed tpp file or the untouched downloaded one for my region? (Do i need a tpp file for this tutorial here? It istn in the description)

 

[dragon9580]

Hey, i had some cia installed in my 3ds afterwards i decided to unlink my sysnand and emunand through tinyformat now all my cia have disappeared from the home screen . But it still occupies space in my sd card

 

[RitzMalh]

After I was having issues with trying to install CFW, I wiped everything (format 3DS + SD). I am trying to use rxTools but it keeps telling me that no emuNAND is found on my SD. I've created emuNAND with EmuNAND9 and my sdcard successfully lost ~2GB. Is my fresh 3DS with no NNID causing EmuNAND creation to fail? If no, does anyone have any other ideas?

Im on o3DS with 9.2 (downgraded from 10.3).

 

[gangs_08]

i downloaded the cia files 6 times with different browsers and got everytime this checksum:
File Name: 9.2.0-20E-O3DS.ttp
MD5: 977CE39D70F6EA34172CCACA51813D7A
SH1: 9FEEE8D420759FFED3A34922739F6A526ACB26C8

doesnt match with the tutorial one. why??

 

[Clydefrosch]

i downloaded the cia files 6 times with different browsers and got everytime this checksum:
File Name: 9.2.0-20E-O3DS.ttp
MD5: 977CE39D70F6EA34172CCACA51813D7A
SH1: 9FEEE8D420759FFED3A34922739F6A526ACB26C8

doesnt match with the tutorial one. why??

the checksums are for the non ttp files floating around. the ones you'd use with sysupdater. even though, the ttp file is basically just a renamed .zip file too.

 

[Funkentanz]

Hello, I am really new to all this so please excuse my (maybe) noobish questions. To my situation. I have an O3DS EU. It was on FW 10.3 I installed Menuhax and had some fun with the Homebrew Channel. Yesterday I decided to downgrade my firmware to 9.2. All went smooth. My 3DS is on 9.2 now. So I installed rxtools and now I have an EmuNand on 10.3 with the two Nands unlinked. But how do I get the Homebrew Channel again? I made a Backup from my SD Card before I made a System Format, can I just copy the Backup back to the SD Card and have my games and savestates back?

 

[vree]

What I should do:

10. Rename the Homebrew Menu's boot.3dsx to HBL8.3dsx and drop CTRBootManager's boot.3dsx into your SD card root (N3DS USERS: SKIP STEPS 11-16, YOU'LL HAVE TO INJECT FBI MANUALLY WITH THIS) 11. Menuhax should now lead you to the CTRBootManager screen. From here, you can launch rxTools or the Homebrew Launcher. 12. Hold L while opening rxTools to enter the rxTools Menu 13. Advanced > Install FBI > emuNAND > Check TMD. Note down the Region and the Version.

What I see:
1)Check TDM: Opening S... FAILED Opening S... FAILED

What am I missing here???

EDIT: still stuck here and I read on just to see what I need to do when I get past this. BUT it says this:

From the rxTools .zip, go to release/Tools/fbi_injection and drag and drop fbi_inject.app and fbi_inject.tmd from the corresponding region and TMD to your SD card root.

There isn't even an rxtools.ZIP fil or anything like that :S

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

I registered just to exress my frustration with your guide. If you were near me, I would punch you so hard(like Saitama) that you'd have a hole in your face.

I've been trying for 3 hours now with those shitty guides in here. I'm stuck at step 12, where you check emuNAND's TMD. For some reason, while I followed your guide, I get errors saying:
"Opening S...
Failed!
Opening S...
Failed!
Press A to continue"

I'm pretty sure I got a European version as my firmware is 9.2.0-20E. Thing is, EU has 3 different versions so I'm not sure which one to use.

If you want to make a guide, do it right and provide solutions to the foreseen Errors that shit-noob users like me might encounter.

Also, your skills at making guides suck big time. 0% extensive/detailed. To install a CFW you need to see us as fking babies.

I'd be thankful if you could tell me what to do to get past the TMD shit error. Thanks and sorry for shitposting and frustration. <3

Did you find solution? I'm also stuck here. I'm not really sure what you mean by 3 versions. But I'm also stuck here

 

[Gwstas]

Did you find solution? I'm also stuck here. I'm not really sure what you mean by 3 versions. But I'm also stuck here

Not yet. I left my O3DS to my gf's house because her laptop reads my SDXC microSD card. What I meant with 3 versions, is that if you go to rxTools/Tools or something like that, you will find a folder named "fbi_injection" or something similar. There are 3-4 versions of that inside the folder. I don't know if you can use whichever version you want, but better not do this...


Anyway, can anyone help in here? Or are you going to keep touching your tits? (I'm telling this to the guys that actually know how to fix those errors)

 

[V0ltr0n]

As much as i love touching my tits, ill try to help. Did you write down the info when u did check tmd in the previous step? That tells u which version to use on your current step. I know it's frustrating, but i would suggest not to get nasty about it as it may turn ppl off from helping you. I understand the tut is a little lacking in detail, but many ppl have used it with success after a little extra help. Including me. The OP is very kind and helped me out via pm, so you could also try that if you are still stuck.

 

[Gwstas]

As much as i love touching my tits, ill try to help. Did you write down the info when u did check tmd in the previous step? That tells u which version to use on your current step. I know it's frustrating, but i would suggest not to get nasty about it as it may turn ppl off from helping you. I understand the tut is a little lacking in detail, but many ppl have used it with success after a little extra help. Including me. The OP is very kind and helped me out via pm, so you could also try that if you are still stuck.

Screw it I did it myself. Thanks for the help though. For anyone having issues, download the firmware.bin from a certain ISO site. It will help with the TMD version and sht. I had 3077 version but I don't know which one you might have. ggwp

 

[Sgt. Lulz]

-whatever-

Screw it I did it myself. Thanks for the help though. For anyone having issues, download the firmware.bin from a certain ISO site. It will help with the TMD version and sht. I had 3077 version but I don't know which one you might have. ggwp

I've heard so many reports of 'database does not exist' errors which I elaborated upon in the last guide it's not even funny.
I've said time and time again to redownload files and try the alternate version if you run into errors, but nobody ever listens. I've had plenty of people follow the guide successfully (save for a few shortcomings caused by lackluster research which I will admit is kinda my fault), but getting the blame pinned on me when the guide tries to cover all bases without droning on and covering LITERALLY every single base there is to possibly cover ain't fun.

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

This was not noted anywhere in the guide.

Yes it was.

boot.cfg:
-dummy text-

1. Place the rxTools folder and boot.cfg in your SD card's root.

This is beyond a joke now.
If nothing is working then you've probably got corrupted files. Replace boot.3dsx, boot.cfg and HBL8.3dsx.

There isn't even an rxtools.ZIP fil or anything like that :S

rxTools Nightly (Older nightlies reccomended for safety purposes, don't use the alpha nor the stable); Mirror
If you have blackscreening issues on boot, try this version of rxTools instead.

Yes there is.
Redownload firmware.bin to probably-fix FBI errors.
Unless you're on a N3DS, then reread that bloody part of the guide because I explicitly clarified that N3DS users can't use FBI injection and have to inject it manually.


Let me put it this way: There's a certain limit to how much something can be idiot-proofed before it just becomes plain unfit for consumption. I know some people would want to have their hand held throughout the entirety of the guide, but that's not gonna happen. I'm gonna have to ask you to use your heads for a while, because I can't account for every SINGLE possible scenario.

 

[Gwstas]

Succesfully updated emuNAND to 10.3.0-28E. When you go into Settings to update the emuNAND, check the top screen to see if it says RX.

So, now, the final step is to coldboot. I haven't checked a guide or what it REALLY is, but I believe it boots directly into emuNAND when you press the power button?


Also, does anyone have a good guide on how to coldboot? (ofc I can Google and watch videos, but you guys know your sht here and I'd trust what you recommend)



Edit: btw this guide was easy 100%. 9/10 would use again. Just get the firmware.bin from that ISO site.

 

[Sgt. Lulz]

Also, does anyone have a good guide on how to coldboot? (ofc I can Google and watch videos, but you guys know your sht here and I'd trust what you recommend)



Edit: btw this guide was easy 100%. 9/10 would use again. Just get the firmware.bin from that ISO site.

"Coldboot" is somewhat of a red herring, since the console isn't actually coldbooting to CFW. Rather, it's booting to OFW before being hijacked by the exploit to boot CFW.
Just open the Homebrew Menu through CTRBootManager, open Menuhax_Manager, hit Install and you're all set.
As for the bugged firmware.bin:
Could you send me the search term or the URL you used to get that firmware.bin over Private Messaging?
I'd like to look into what the difference between the one downloaded through my batch script and that one is that's making the FBI injector choke up.

 

[Gwstas]

Just open the Homebrew Menu through CTRBootManager, open Menuhax_Manager, hit Install and you're all set.

I have done that, but I was wondering if there was a way to at least boot directly into rxtools(in which you select boot into emuNAND by pressing Y button).

Is there a way so that when I press the power button, it boots directly into CTRBootManager or even better into rxTools without having to press the L button?
This video says something about an automatic themehax(go @ 3:34): - Is it the droid I'm looking for?

 

[Sgt. Lulz]

I have done that, but I was wondering if there was a way to at least boot directly into rxtools(in which you select boot into emuNAND by pressing Y button).

Is there a way so that when I press the power button, it boots directly into CTRBootManager or even better into rxTools without having to press the L button?
This video says something about an automatic themehax(go @ 3:34): -huge video- - Is it the droid I'm looking for?

Right, that.
There's a button in menuhax_manager that reads 'Configure/check haxx trigger button(s)'.
Just set it to Type2 and follow the onscreen instructions to configure the untrigger you want to be holding to not load Menuhax.
The boot.cfg in the tutorial is set to autoboot after 3 seconds, so all you'd have to do is power on and wait for it to load.
You can set it to 1 second or even 0 seconds for full-automatic boot if you so desire.

 

[Gwstas]

Right, that.
There's a button in menuhax_manager that reads 'Configure/check haxx trigger button(s)'.
Just set it to Type2 and follow the onscreen instructions to configure the untrigger you want to be holding to not load Menuhax.
The boot.cfg in the tutorial is set to autoboot after 3 seconds, so all you'd have to do is power on and wait for it to load.
You can set it to 1 second or even 0 seconds for full-automatic boot if you so desire.

I did it and it didn't work. I deleted the files created from the menuhax in sdcard, booted into HombrewLauncher through the browser, selected menuhax, selected delete(the 2nd option I presume) and selected "Configure/check haxx trigger button(s)" Then selected Type 2, touched the touchscreen WITHOUT holding any button. When I turned it on again it didn't work. It booted into sysNAND and not into eg HomebrewLauncher. Then I repeated the above steps and tried with Type1 but it didn't work again.

AllI did was NOT hold any button and JUST touch the touchscreen(to configure your option). Am I doing something wrong? o.0;


Edit: Guys, don't rename HomebrewLauncher's boot.3dsx to HBL8.3ds because you WON'T be able to boot into it through CTRmanager. Rename it into boot_hb.3dsx. =)

 

[waldtroll]

1)Check TDM: Opening S... FAILED Opening S... FAILED

Hey! Firstly, Thanks for the great tutorial! I've also found the solution to that problem (checking TDM):

The (mirror) link to the RxTools Nightly firmware seems to have an older/buggy version in it. I've tried your tutorial with Nightly build 83afbb6, and it worked! No problems at all. Took me a while to figure out, but it should work!

Thanks again!

 

[Sgt. Lulz]

I did it and it didn't work. I deleted the files created from the menuhax in sdcard, booted into HombrewLauncher through the browser, selected menuhax, selected delete(the 2nd option I presume) and selected "Configure/check haxx trigger button(s)" Then selected Type 2, touched the touchscreen WITHOUT holding any button. When I turned it on again it didn't work. It booted into sysNAND and not into eg HomebrewLauncher. Then I repeated the above steps and tried with Type1 but it didn't work again.

AllI did was NOT hold any button and JUST touch the touchscreen(to configure your option). Am I doing something wrong? o.0;


Edit: Guys, don't rename HomebrewLauncher's boot.3dsx to HBL8.3ds because you WON'T be able to boot into it through CTRmanager. Rename it into boot_hb.3dsx. =)

Type2 boot's description states that Menuhax should trigger ONLY when the PAD button(s) AREN'T being held, which means you're supposed to hold SOMETHING before tapping the bottom screen to add a trigger button. By not holding any buttons, you're effectively telling it that it shouldn't trigger when nothing is not being held, which is kind of asinine.

I wouldn't reccomend renaming it to boot_hb.3dsx. That filename is for the default CTRBootManager boot.cfg, which differs from the one in the OP.
I stated to name it HBL8.3dsx because otherwise Yellows8's Homebrew Launcher Loader payload can't be edited to work with the Homebrew Launcher from the getgo, as the filename can't be any length other than 9 characters or the address space will shift around and break.

Hey! Firstly, Thanks for the great tutorial! I've also found the solution to that problem (checking TDM):

The (mirror) link to the RxTools Nightly firmware seems to have an older/buggy version in it. I've tried your tutorial with Nightly build 83afbb6, and it worked! No problems at all. Took me a while to figure out, but it should work!

Thanks again!

Well shit.
Noted.
I guess I'll have to wait for the buildserver to start existing before I can keep linking people to it.