Hmm its not risky to install on SysNand?If you have the GW cart, you don't need CFW. I use CFW because I don't want to buy a GW cart.
BTW I'm experimenting for installing CIAa on sysnand with a mod of CFW. Stay tuned ...
Hmm its not risky to install on SysNand?If you have the GW cart, you don't need CFW. I use CFW because I don't want to buy a GW cart.
BTW I'm experimenting for installing CIAa on sysnand with a mod of CFW. Stay tuned ...
Hmm its not risky to install on SysNand?
And what utility you'll look for cia on sysnand with modded cfw?? that you can launch app and other immediately after turn on 3ds? XDRetail titles are installed on the SD data of the sysnand (like the eshop does). If you try to install a system update on the sysnand, ... then yes, it's risky.
And what utility you'll look for cia on sysnand with modded cfw??
If you are able to do to a modded cfw maybe you are able also to add plugin support like ntr cfwYou can install CIA with a valid sign on the 3DS and have it on the home screen. If you update the FW they'll stay there, like happens for a 3DS buyed with a bundled game.
I don't play games so it's no use for me, I find more interesting the possibility to install sys update (or maybe in the future custom patchs) on the sysnand; obviously without buying a Gateway.
If you are able to do to a modded cfw maybe you are able also to add plugin support like ntr cfw![]()
If you have rebooted back to the home menu after launching the ds profile while holding L and getting the blue screen on top and lower screen flashes white.......you've booted the cfw.....run the bat to install devmenu. Make sure its in the same directory as the bat file.
Make sure you understand the instructions for installing devmenu and using the cfw...
I actually responded to the wrong thread, but I suppose here is as good of a place as any. Is there any way to check whether I am on CFW? I try injecting .cia files through the network and the terminal returns an error code. That is what makes me think it is not booting to CFW or it is somehow corrupted.
Make a new folder and change the icon zoom in what you suppose to be the emunand. So you can see the differenze with the sysnand homemenu.
An error code in ctrclient may be for not correcty creating the title.db and import.db (to do only if don't have anything downloaded from eshop).
Thank you for helping me narrow it down. Using the method you suggested implies I am correctly booting into the CFW (because the icon sizes change).
However, I am not sure how to proceed from there. I made the blank *.db documents, ran through the instructions, and now the dbs folder contains the import.db and title.db files with 3193 kb of information each.
I could transfer over my eShop files that I backed up, but I would rather keep those on the 9.5 emunand if possible. I just want the CFW for homebrew.

The part of the cfw that starts the ctrserver (the one in the arm11_code.bin loaded pressing the L key) works like the ntr cfw plugins. So yes, it's possible to implement plugins for the CFW too.
I almost completeted the RE of boot.bin, but not started the RE of the arm11_code.bin part (I have the asm decompiled, but no time to analyze it).
My priority is to rewrite the code of the boot.bin using the framework of xerpi linux loader to make the cfw more stable. Then maybe I could try to make a arm 11 plugin to load regionthree and the HB service that enables the use of the HB Launcher.
But it's a long term project, at the actual speed it will took me about a year. Where are people that want try to do this in a shorter time?
