Search results

  1. Badablek

    Homebrew RELEASE pFBA: final burn alpha

    + & - to open pfba menu → States → Slot x : if slot is empty, push A to automatically SAVE when a slot is used, push A and pfba will ask you if you want to load (default) or save To exit a game, + & - to open pfba menu → Exit A : select B : cancel/return
  2. Badablek

    Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

    fss0 method is as easy as chainloading fusee. But instead of having "payload=fusee.bin", you will have "fss0=atmosphere\package3" Hekate boot entry should be like this (atmosphere on emuMMC, using sigpatches) : [Atmosphere_emummc] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 With...
  3. Badablek

    Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

    you're using Hekate to chainload fusee. But original fusee does not load KIP patches anymore (since revision 1.7.0). So sigpatches won't work the way it used to be until now. you must use Hekate fss0 method to load directly package3 OR use sys-patch (will work with fusee). ps : you can also use...
  4. Badablek

    18.0.1 crash - Atmosphere

    great news ! (I thought every IPS patching was removed, but now I realize it would be dumb because it won't allow any cheat codes if it was the case...:blush:)
  5. Badablek

    18.0.1 crash - Atmosphere

    nice finding :bow: (but as IPS patching was removed in fusee, this must be used with Hekate + fss0 boot method)
  6. Badablek

    18.0.1 crash - Atmosphere

    yes, since firmware 17.0.0, if your PRODINFO is erased (incognito) or hidden (exosphere), HorizonOS will crash when trying to reach Nintendo servers. Reason why you absolutely need to block it (by using 90DNS or dns_mitm) or unhide/restore your PRODINFO...
  7. Badablek

    Problem after updating

    420000000007E51A → you're using an old (incompatible) version of Tesla. update it. latest firmware does not mean you only have to update atmosphere ! Even more when/if you're using sysmodules like Tesla, MissionControl, etc. you MUST update ALL sysmodules you want to use (or delete if it's not...
  8. Badablek

    18.0.1 crash - Atmosphere

    Hi, you should post the error screen, because it can be a lot of things : an old sysmodule, not compatible 18.0.0+ an hidden/deleted prodinfo without dns_mitm or 90DNS (since firmware 17.0.0+) a theme ... BTW it seems to be a missing/hidden PRODINFO, as Atmosphere boots correctly, then...
  9. Badablek

    help with Updating SX modchip firmware, to install Linux and Android ( Switch Lite )

    As it is explained on github's spacecraft-nx : I upgraded my SX Lite chip this way, some years ago...you must use the USB ribbon sold with the modchip. You can buy it on aliexpress if you don't have it.
  10. Badablek

    Homebrew boot.dat and boot.ini

    Hi, you're not missing anything actually...boot.dat (+boot.ini) is for SX chips (and clones), when you decide to keep SX firmware on it (people, like me, who have reflashed the chip with spacecraft-nx, can directly load payload.bin) boot.dat, for a lot of users, is just SX Gear, which is made...
  11. Badablek

    Homebrew RELEASE MissionControl: Use controllers from other consoles natively via Bluetooth

    actually you just have to...click this link (taken from the official github) :grog: if discord is installed, it will open it if not, it will use your web browser
  12. Badablek

    Tutorial HOMEBREW MENU THEME CUSTOM IMAGES

    I've been rude too, sorry ;) I should have been less direct. I'm using this great tool since a long time, and it's really safe, you don't have to worry about (BTW you are right to check if it's safe or not, obviously). it's closing immediately because you have to use it in command-line. Readme...
  13. Badablek

    Tutorial HOMEBREW MENU THEME CUSTOM IMAGES

    this is asked so nicely :unsure: you obviously don't know how command-line tools work (little hint : readme), neither how hacking tools are often falsely reported as viruses...and BTW, 8/65 is not as bad as you seems to think, but if you're unhappy with it, don't use it, as simple as that ...
  14. Badablek

    Homebrew Homebrew app sys-patch - sysmod that patches on boot

    sys-patch download sys-patch 1.5.1 unzip (root of microSD card) done and for fss0 method, everything is explained ONE message above yours, the one you quoted, actually...did you ever read it ? :unsure:
  15. Badablek

    TMNT Shredder’s Revenge Anniversary Edition

    everything is included on cartridge
  16. Badablek

    Zelda Link's Awakening perf increase?

    Hello, to increase performance, you need to overclock your Switch with sys-clk from its database : and you can disable blur by using No DOF blur mod (this won't change anything about performance, but it will be visually much better)
  17. Badablek

    Homebrew Sometimes my Switch Lite doesn't turn on the screen

    Hi, may I ask if you have put hekate's bootloader folder at the root of your microSD card ? Maybe bootloader/sys/libsys_lp0.bso is missing (or corrupted) ? https://github.com/CTCaer/hekate?tab=readme-ov-file#bootloader-folders-and-files |__ libsys_lp0.bso LP0 (sleep mode) module. Important!
  18. Badablek

    Any way for a pro controller to be recognized as a joy con on modded switch?

    you may have a chance...one day, with MissionControl. it's in the TO-DO list. Maybe you can ask ndeadly if it's still under development :blush: ps : BTW I don't know if it could identify a PRO controller as a joycon (as PRO controller is natively supported by HorizonOS)
  19. Badablek

    Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

    kip1patch=nosigchk → loads ONLY sigpatches kip1=atmosphere/kips/* → loads everything that is in kips folder atmosphere=1 Enables Atmosphère patching. Not needed when fss0 is used. Hekate's guide doesn't explain exactly what it is "patching". I may have misinterpreted it's used to load...
  20. Badablek

    Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

    fss0 needs "kip1patch=nosigchk" in order to load sigpatches but not "atmosphere=1" (chainloading) fusee needs "atmosphere=1" in order to load sigpatches but not "kip1patch=nosigchk" kip1patch=patchname Enables a kip1 patch. Specify with multiple lines and/or in one line with , as separator...
General chit-chat
Help Users
    S @ salazarcosplay: How are you @BigOnYa