Hacking [RELEASE] Kecleon Patch for Luma3DS

  • Thread starter Thread starter sixtails
  • Start date Start date
  • Views Views 56,794
  • Replies Replies 174
  • Likes Likes 58
nice, thanks! Sorry I still have a question lol.
does it work/is it safe to link my NNID when running sysnand while I have it linked to emunand?

Uhh... Yes, it's safe. Just don't run TinyFormat in the first place (just make sure to delete things that look like it gives away hacks, like custom themes, apps, the activity log, etc...). I'm not so sure about re-linking NNID AFTER running TinyFormat.

If you've already ran TinyFormat, you can always restore EmuNAND to SysNAND (backup EmuNAND with EmuNAND9, restore to SysNAND with HourGlass9).
 
Last edited by sixtails,
What do I do if I forgot the combo and need to boot Luma3DS config?

My idea is to boot normal Luma3DS with Hourglass9 payload, inject FBI to H&S and delete Kecleon's config in CTRNAND, but I don't know if I can do this and where it's located.
 
Last edited by Hyoretsu,
What do I do if I forgot the combo and need to boot Luma3DS config?

My idea is to boot normal Luma3DS with Hourglass9 payload, inject FBI to H&S and delete Kecleon's config in CTRNAND, but I don't know if I can do this and where it's located.
Put a regular Luma arm9loaderhax.bin on your root and it will boot with that. So you never need to worry about forgetting the button combo.
 
  • Like
Reactions: sixtails
Put a regular Luma arm9loaderhax.bin on your root and it will boot with that. So you never need to worry about forgetting the button combo.
I want to come back to Kecleon later, because I installed it in my two brothers' 2DSes. But they didn't want me to a9lh their consoles, so I used Kecleon patch to hide a9lh's presence.
 
  • Like
Reactions: Quantumcat
Cool! Could you in the future create an app that hides any selected TitleID? And then hide that app using a computer and configuring bin?

I dont have kecleon yet (keyword is yet, when I return home I'll try it) but that would be a really nice Idea that way you can hide your admin tools like fbi, homebrew roms and whatnot in a simple and easy manner.

while the perfect hide is technically better, this kind of a simple hide is enough to keep noobs quiet.
 
I dont have kecleon yet (keyword is yet, when I return home I'll try it) but that would be a really nice Idea that way you can hide your admin tools like fbi, homebrew roms and whatnot in a simple and easy manner.

while the perfect hide is technically better, this kind of a simple hide is enough to keep noobs quiet.

I'm not sure how I can do this selectively, other then trying to patch in new logic to into homemenu. One thing I can do is disable the Signature Check Patch which would remove hide anything that's not signed - IF I recall from PastaCFW days that the homemenu does indeed fail to load an icon on Signature Check Fail. You still might want to change theme/layout and clear Activity Log.
 
I just set up kecleon and wgile I enabled all 4 kecleon options. FBI and stuff is still visible. but I dont see any setting regarding signature checks.

That seems to be not all, it even starts.
 
Last edited by My1,
I just set up kecleon and wgile I enabled all 4 kecleon options. FBI and stuff is still visible. but I dont see any setting regarding signature checks.

I have not implemented it yet. I may try to do it in the next few days, along with rewriting the file system interface and reworking the payload loading logic a bit.

There are ways around it though; There's the full EmuNAND solution. Also you can rename "Nintendo 3DS", which would hide all installed apps (then clear Activity log, remove theme, change layout for a fairly clean setup). Rename to get them back. Another solution is remove everything, and reinstall when you don't need to hide anything anymore.

The problem with these solutions is that their a lot more work then an EmuNAND (and more detectable). But I'll see if I can write a small guide for an EmuNANDless solution as well.
 
Last edited by sixtails,
well there are solutions like that but you cant really do them on the go. for a quick thing this is nice and simple, and it's not like I want to fool specialists on the subject. as a noob-proof solution it's more than enough
 
  • Like
Reactions: sixtails
I found something weird. I disabled the button lock, but I still cannot access any luma payloads (e.g. godmode9 to copy over the kecleon launcher)
 
hey. so how would i get health and safety back? I can't use nus to download it for some reason......
 
depending on what guide you used for homebrew you shoud have a backup in the files9 directory when you coped around with your nand
 
depending on what guide you used for homebrew you shoud have a backup in the files9 directory when you coped around with your nand

Is there a way to get it back? because I didn't dump that.
 
So the Home Menu does not use signature checks to determine if an app will be shown on the Home Menu - it seems that's handled exclusively by Arm9K. So Homebrew cannot be hidden via enabling signature checks.

I found something weird. I disabled the button lock, but I still cannot access any luma payloads (e.g. godmode9 to copy over the kecleon launcher)

Yes, right now the FS interface is a bit of a one trick pony - the payloads will be ran from wherever it finds "config.bin". So if your config.bin is saved in CtrNAND, then your payloads also need to be saved onto CtrNAND (ie, "/rw/luma/payloads"). This is one thing I hope to fix eventually by rewritting the filesystem interface.

If you have payloads though, then there is no reason for you to save "config.bin" to CtrNAND, since your SD card is already "dirty", so I suggest keeping everything on the SD card in that case.
 
I have the config on the CTRnand solely for the reason that when someone takes out the SD card that the locks wont vanish, which is pretty much enough to keep e.g. my sister or whoever I lend this thing from accidentially trying something stupid. it's more like a safety measure.
but kinda sad that the home menu doesnt do sigchecks. one thing that might have been epic would be e.g. if any homebrew cia's could set to some region setting or whatever that is assigned to no 3DS like ever, so just re-enabling the region checks would kick them into oblivion.
I mean if the config is on CTR and there is no way to access it because stuff is locked down by keycombo, it means nobody by accident or malicously can try stupid stuff, even if they would see that it has Luma they couldnt try to add any payloads or whatever I dont want because they couldnt execute them.
 
Last edited by My1,
Kecleon patch is broken on latest nightly of Luma3DS :

Code:
+ git apply kecleon.patch
kecleon.patch:317: trailing whitespace.
    
error: le patch a échoué : source/config.c:83
error: source/config.c : le patch ne s'applique pas
error: le patch a échoué : source/config.h:56
error: source/config.h : le patch ne s'applique pas
error: le patch a échoué : source/main.c:123
error: source/main.c : le patch ne s'applique pas
error: le patch a échoué : source/pin.c:1
error: source/pin.c : le patch ne s'applique pas
error: le patch a échoué : source/pin.h:1
error: source/pin.h : le patch ne s'applique pas

("le patch ne s'applique pas" means "patch doesn't apply" in French)
 
Kecleon patch is broken on latest nightly of Luma3DS :

Code:
+ git apply kecleon.patch
kecleon.patch:317: trailing whitespace.
 
error: le patch a échoué : source/config.c:83
error: source/config.c : le patch ne s'applique pas
error: le patch a échoué : source/config.h:56
error: source/config.h : le patch ne s'applique pas
error: le patch a échoué : source/main.c:123
error: source/main.c : le patch ne s'applique pas
error: le patch a échoué : source/pin.c:1
error: source/pin.c : le patch ne s'applique pas
error: le patch a échoué : source/pin.h:1
error: source/pin.h : le patch ne s'applique pas

("le patch ne s'applique pas" means "patch doesn't apply" in French)

Okay, somethings wrong with my notifications, this didn't show up at all lol.

I am now hosting the entire project on GitHub instead of using diffs. Also note: the 'master' branch is a mirror of Aurura's Luma3DS repository, while the 'kecleon' branch is used for the changes I've made for Kecleon (this is just to make porting changes between the two easier). Don't use the old patch I posted, as that may require manual merging, such as this case.

I have also just ported over the latest Luma3DS commit to Kecleon.

So for building latest Luma3DS-Kecleon that I've tested, something along the lines of:
Code:
git clone https://github.com/sixtails/Kecleon.git
cd Kecleon
git submodule update --init --recursive
Code:
git checkout kecleon
git pull https://github.com/sixtails/Kecleon.git kecleon
git submodule update --init --recursive
make

If you wanted to apply the differences against the latest Luma3DS (which may require manual merging):
Code:
git checkout kecleon
git pull https://github.com/sixtails/Kecleon.git kecleon
git submodule update --init --recursive
git checkout master
git pull https://github.com/AuroraWright/Luma3DS.git master
git submodule update --init --recursive
git checkout kecleon
git merge master
# You may need to do manual merging here.
make
 
Last edited by sixtails,

Site & Scene News

Popular threads in this forum