ctcaer / hekate Goto Github PK

These will not be listed here until implementation.

I used the Fix SD Files Attributes option in tools and when I attempted to run a game that was installed on my SD card (including carts) it would crash immediately after opening. When attempting to reinstall the games, I got error 2005-0004 which is an SD card error. Only way to fix it was to format my SD card on the Switch.

When troubleshooting an LFS related crash, it appears there is a bug with comments..
Tested this with SMO on FW 5.1.0.
Here's my ini file (with the bug):

{-------- Stock -------}
[Stock]
logopath=cfw/custom.bmp

[Stock (SVC perms)]
logopath=cfw/custom.bmp
fullsvcperm=1
debugmode=1
{ }

{-- Custom Firmware --}
[AMS HBL]
kip1=cfw/local/loader.kip
kip1=cfw/local/sm.kip

[AMS HBL (SVC Perms)]
kip1=cfw/local/loader.kip
kip1=cfw/local/sm.kip
fullsvcperm=1

#[LFS (automatic)]
#kip1=cfw/local/loader.kip
#kip1=cfw/local/sm.kip
#kip1=cfw/local/fs_mitm.kip
#fullsvcperm=1
#debugmode=1
#atmosphere=1

[AMS (full)]
secmon=cfw/exosphere.bin
kip1=cfw/exosphere/loader.kip
kip1=cfw/exosphere/sm.kip
kip1=cfw/exosphere/fs_mitm.kip
#kip1=cfw/exosphere/pm.kip
logopath=cfw/exosphere/ams.bmp
atmosphere=1
{ }

In the above example, the LFS (Automatic) entry doesn't show, as expected as its commented out.
However, if you try to load AMS Full, LFS has an instant game crash implying something is off.. removing the commented out pm.kip line resolves the crash.. Looks like there's a bug with using comments in the middle of a boot entry.. (it does not matter if the kip exists or not).

There seems to be an issue where, if you remove a controller, turn it off, slide it back into the console then put it into sleep mode, it'll just give a black screen when trying to exit sleep mode.

Currently on 3.0.0

On hekate, when you go to power off, the screen turn powered off but the console itself isn't powered off until you press power button for 10-12secs.

Thank you for you contribution,but I think the payload.bin size is more and more large. And It will hard to deposit into a MCU like trinket M0. So can we make a branch with a Slim hekate CTCaer. just with base tools, like TX payload.bin?

Using wildcards, you can use one script for 1GB parts and 2GB parts. You can also show progress with pv on unix, given it's installed.
join_linux_macos.sh

#!/usr/bin/env bash
if command -v pv >/dev/null; then
	cat rawnand.bin.* | pv -s 30g > rawnand.bin
else
	cat rawnand.bin.* > rawnand.bin
fi

join_windows.bat

copy /b rawnand.bin.* rawnand.bin

If there's a problem backing up firmware, is there no way to recover it?

Currently, when the SD card cannot be initialized or mounted, a message is displayed on screen for a few seconds and the stock firmware will be booted. Every time this has happened to me, it's because I've forgotten to insert the SD card and it's a waste of my time to power the system off again and restart hekate.

There should be three options (abort-retry-ignore style) if the SD card fails to mount:

• Cancel (return to main menu)
• Retry (try mounting the SD card again, now that the user has had a chance to insert it)
• Boot Stock (the current default)

Could you please add an option to remove autorcm ? Thanks

Hello,

I see that Hekate wants to add more and more functionality (that can be found elsewhere, like gpt restore or NAND restore, etc.) in a restricted size of payload instead of just only be what it's designed for (launching kip, patching them, etc.).

Also, why keep a copy of the splash screen inside of the payload instead of an external support (on SD Card) ?

So i ask, why keep functions that can be find elsewhere at the expense of main usage of hekate ?

Sorry if I look rough, I still have difficulties to express myself in English.

I'm having sleepmode crashes whenever I use version 3.0, leaving it on with backlight and refusing to go back unless powering down completely.

Using freshly compiled atmosphere kips.
[Atmosphere]
secmon=modules/atmos/exosphere.bin
kip1=modules/atmos/loader.kip
kip1=modules/atmos/sm.kip
kip1=modules/atmos/fs_mitm.kip
atmosphere=1

atmos.zip

This would be helpful to the people that cant get 32 bit bmps and will allow for more editing software to be used in creating boot logos. It would also make it easier for anyone to have a custom boot logo without needing to edit an image too much. it would be much easier than trying to get a 32bit bmp image

Some people are different. Don't spit your dummy out when people use your "open source" code for something your opposed to.

Would it be possible to have a feature in the future which allows to boot payload from sd for things like memloader

When hekate is launched, at the bottom of the interface there is power infos,
thoses information never update exept when user do something like pressing Vol.+, Vol.- or Pwr.

Maybe make a auto update all 2 secs ?

The path on the microSD card that backups are saved to should contain a piece that is unique per-device, to avoid collisions when backing up eMMC from multiple consoles.

Sleep mode is not working on 3.0.0 firmware. Both cfw and stock firmware aren't working

Hi I just tried sleep mode with some old payloads I had and this one worked!
Although you need to disable screen lock in Settings, I'm not sure if you are aloud to select a Profile first because I didn't select a profile,
but you can enter the home menu by tapping the screen after launching this Payload with Hekate V2.0 (New Horizons) on your SD.
and enter sleep mode once (You have to enter sleep mode at least once in the home first) you can then wake up from sleep mode
(using the power button to enter sleep mode and wake up only), also you can enter the Homebrew Channel and sleep and wake up.
I tested it, with my Switch on firmware 3.0.2.
Question: Do you think you can update your payload with this one for 3.x support and fix sleep mode with home button or power off and restart or with auto sleep mode?

payload 3.0.2.zip

There's a new issue with verification.

Currently it tries to parse a u64 number with a u32 storage.
This way it tries to compare the wrong eMMC segment with the correct SD one.

A fix is planned for release ASAP!
It's currently in testing, by users that had this problem.

when playing around with the SD mounting/device handling/FSFat i noticed that trying to dump package1 twice made it hang/crash. no error on SD mounting so it either hangs somewhere else

didn't have time to look yet, im gonna try and get my changes done first

It still says 3.1 at the top when you launch it :P

I wanna update to the latest FW, but I also wanna continue using the HBL.

Will this work on the latest FW?

It would be nice to have this fuction to disable the BATFET.

As probably more and more people are going to install an internal modchip connecting it to the BQ24193's SYS pins (15&16), it would be really greate to be able to disconnect the power so the modchip can't drain the battery if you plan not using your console for an extended period of time, want to ship it or whatever.

Making sure that the battery is fully charged and there is an external power source connected to the console, like it was done in the reset_pmic_fuel_gauge_charger_config() function before turning off the BATFET, should also be (re)implemented.

I'm on 5.1, and whenever I try to "launch firmware" it says that my SD (2GB, if this could be the problem) isn't in a "Fat" format. I tried Fat, Fat32 and exFat by now, but it's always the same problem. Any idea what could I do?

Given the Switch's propensity to utilizing the microSD over the eMMC for storage purposes, it's common to find that the on-board storage is largely unused.
Having the option to perform backups on a file level would significantly cut down the time required to perform a backup over block-level backups (Especially so for SAFE and USER).

In the newest version you added the ability to remove the archive bit for files to solve an issue with HBMenu loading files. This is a brilliant idea and I'm super glad it's there. I was able to reproduce the issue and solve it with this boot option.

However, there is an issue where now none of my legit downloaded games work. Based on the post here, I believe the solution might be to skip the Nintendo directory when turning off the archive bit. I haven't tried the solution there to see if it worked for me (I don't have a windows computer handy) but if you whip up a new build, I'll be happy to test.

Pretty self explanatory, horizon expects the archive bit to be set on nca folders, part files and savedata, so it'd be best not to clear it on Nintendo folder or anything inside.

With the use of sdfiles updater hekate-ipl.ini is often overwritten with a new version. I would like to see an external file that is also parsed after hekate-ipl.ini that will allow for custom boot menu entry’s and autoboot that doesnt go away when sdfiles are updated.

Although we have nx-shell, a File Manager built into Hekate would be cool.

So, recently I took a backup to a 16GB microSD card. It split them into 15 parts due to size limitations, I had to swap the card around and reboot to hekate various times etc, and when I wanted to restore them using a 64GB microSD card today (on exFAT ofc), I simply copied all 15 files to the microSD card, but found out that hekate doesn't support just reading them all.

This would be pretty nice to have so that other people can avoid what I am forced to do right now (which is removing 32gb of backups from microSD, combining them and then copying again, wasting a couple hours in the process due to my laptop's lack of sdxc support).

If you want I can try to write support for this and send a PR.

any reason why this is the only info you cant dump to an sd card is tsec keys?

if included itd make it so this project: https://github.com/tesnos/kezplez-nx/releases no longer needs a seperate (and possibly to be outdated) hekate file

Not sure if this is at all on the roadmap or even within the scope of this project but it would be pretty convenient to have one bootloader that can dual-boot Horizon and Linux. Ideally it would be able to read everything it needs from SD without needing coreboot to be piped over USB. Would it be as simple as having Hekate replace the role of CBFS described here https://fail0verflow.com/blog/2018/shofel2/#linux-on-switch-boot-chain?

Regardless it would be ideal to have some solution for internal hardmods like with the Trinket M0 that don't have the flash capacity for all the parts necessary to boot Linux. Also sorry if this sounds like a bunch of nonsense, I'm not too experienced with this boot-level stuff.

Hope to bring a repair machine with a formatter when reinstalling the restore program, to ensure that the machine bad program empty to prevent it from being ban,3.0.0 repair failed rawnand.bin. is a backup of 00-14, black screen, but can enter rcm. hope to have a repair tool, thank you

it could be really cool for have a log with parts of the switch connected:

The gamecard module is connected to the motherboard

The sd module is connected

Screen is connected

etc

Thanks if you can

用的join_15_2GBparts_windows 是不是需要返厂了，黑屏进不去系统

Use custom splashscreen on manual launched firmware by user.
For now, when you manually select a firmware there is no bootscreen (But fully works on autoboot).

My SanDisk Ultra 128GB microSDXC works perfectly with the switch OFW, and my computer, but hekate 'failed to init SD card' (after a couple second pause) whenever i try to print SD info or start CFW etc.

I've tried formatting it as fat32, and exfat, with a variety of different tools and operating systems, including the switch itself.

Are there still SD cards that don't work properly with Hekate yet?

(5.1.0 with exFAT update, and your latest hekate fork release)

If there is a horizontal menu, the experience will be much exhanced.

But it is hitting files within the /switch folder.

I've compiled a new .bin from the most recent master branch to test the archive bit update. It doesn't seem to be working when I use the 'switch folder only' option. From what I can understand of your code, I think it might be opening the /switch folder to list all files and unsetting the archive bit for those files inside, but it doesn't actually unset the bit for the /switch folder itself.

I was able to verify by loading up a windows computer and unsetting the archive bit for only that folder, then everything worked for me. Homebrew and Switch games.