Huh strange. Is update.bin correct (aka hekate 4.8)? If yes can you delete sept/payload.bin and try again? Update.bin will be copied there and used.Awesome.
I'm trying to dump PKG1 but it says tsec will run and then re run this part again, I did but it said the same thing.
There will be a homebrew. For reboot to payload, the reboot payload must be hekate.What is custom warmboot binary?
--------------------- MERGED ---------------------------
When working with Atomsphere 084, is it working like this?
Hekate CTCaer 4.8 chain loading sept/payload.bin?
How about Atomsphere 084's reboot to CFW feature? (not reboot to payload).
Would update.bin been involved in this booting process?
--------------------- MERGED ---------------------------
Reboot to a selected boot entry via HOS hb, is there an homebrew for this been released yet
If you are on 6.2.0 it should work. I changed the format a little bit, but it shouldn't parse more than 2 0x10 bytes.Ok, im on 6.2.0 and atmosphere 0.8.4, old dumps works from hekate 4.6 works, new one from 4.8 dont.
Lockpick is latest 1.2. Gonna use biskeydump.
Huh strange. Is update.bin correct (aka hekate 4.8)? If yes can you delete sept/payload.bin and try again? Update.bin will be copied there and used.
Btw just checked and it's working.
There will be a homebrew. For reboot to payload, the reboot payload must be hekate.
If you are on 6.2.0 it should work. I changed the format a little bit, but it shouldn't parse more than 2 0x10 bytes.
I basically removed the redundant extra 2 keys from <= 6.2.0. And now the file is 32 bytes long.
I basically removed the redundant extra 2 keys from <= 6.2.0. And now the file is 32 bytes long.
I think I might revisit that design. The problem is that I don't want to make the boot process slow.Yes, is working, problem was I tried this before they added it to SDFiles(Kosmos) and it didn't work back then (don't know why) but then I downloaded the SDFiles and everything works awesome now!
oof. It was mandatory change though. It shaved a lot of bytes in order to fit everything.^^^ broke Lockpick xD
Afaik kosmos used new atmo without bundling the new loader.ini format. You might want to check that with them.Im on 6.2.0 and i tried the new hekate_ctcaer_4.8.bin along with the new kosmos package and when i inject the payload i get a crash with a black screen i have to hold down the power button for like 10 or so seconds to power it off. I tried loading the fusee-primary.bin with the new kosmos files and atmosphere loads no problem i even deleted the old kosmos package from my sd card before installing the new one.
I think I might revisit that design. The problem is that I don't want to make the boot process slow.
I want it nice and fast. Dunno we'll see.
oof. It was mandatory change though. It shaved a lot of bytes in order to fit everything.
Afaik kosmos used new atmo without bundling the new loader.ini format. You might want to check that with them.
Correct you are thanks for the info.I think I might revisit that design. The problem is that I don't want to make the boot process slow.
I want it nice and fast. Dunno we'll see.
oof. It was mandatory change though. It shaved a lot of bytes in order to fit everything.
Afaik kosmos used new atmo without bundling the new loader.ini format. You might want to check that with them.
so i only have to put the boot.dat from sx os website and a menu in hekate*.ini with the lineFrom the sx os website.
There is an issue in github about this, but I haven't had time to check it.Is is only me or the new 4.8 hekate payload does not show custom bootlogo anymore?
You do need the boot.dat in the root of the sd card. But what I was saying to download from the sx os website is payload.bin - the download button says "Download SX Loader 1.0". Rename that to sxloader.bin or something and put it on your sd card, then configure hekate to chainload it.so i only have to put the boot.dat from sx os website and a menu in hekate*.ini with the line
payload=boot.dat and put it in root of sd
?
So no decompress or anything else is needed ?
You do need the boot.dat in the root of the sd card. But what I was saying to download from the sx os website is payload.bin - the download button says "Download SX Loader 1.0". Rename that to sxloader.bin or something and put it on your sd card, then configure hekate to chainload it.
There is an issue in github about this, but I haven't had time to check it.
Seems like logopath works but not the bootlogo.bmp
f_puts("\ncustomlogo=", &fp);
itoa(h_cfg.customlogo, lbuf, 10);
CTCaer said:Stock is not possible anymore
Now I understood what you meant in github. Check the issue again. It's better to avoid deleting the sanitization, because the buffer is finite and fixed.Code:f_puts("\ncustomlogo=", &fp); itoa(h_cfg.customlogo, lbuf, 10);
missing in config.c?
EDIT: Nope. Not that. Stupid me.
Edit edit... X & y axis flipped. Change sanity check. Wrote on github
It should be pretty safe, but nothing is 100% with nintendo.Before 7.x, I used to go online while preserving my fuses by booting "Stock" in Hekate.
This seemed to be "semi-safe", and it seemed Nintendo didn't care enough about a fuse count mismatch to ban people.
However, @CTCaer said here:
https://github.com/CTCaer/hekate/issues/189#issuecomment-466826549
I wonder how safe going online in the suggested "semi-stock" would be, just to preserve your fuses.
https://gbatemp.net/threads/rekado-payload-launcher-for-android-os.510195/how can i inject this via Android? to 7.0.0
Yes, you're ok to remove it while in hekate's menus.Hi everyone, sorry for the noob question if it is. Is it possible to remove the SD card while in Hekate and then put it back ? (For example, after a NAND backup to copy the backup on my PC). I just want to enter into RCM as little as possible.
I remember Godmode9 had an option like that on the 3DS, so maybe this can be done on the Switch too
Thanks
Yes, you're ok to remove it while in hekate's menus.
in case you haven't found out yet, I updated Lockpick to 1.2.1 on Monday to accept the new filesize.Ok, im on 6.2.0 and atmosphere 0.8.4, old dumps works from hekate 4.6 works, new one from 4.8 dont.
Lockpick is latest 1.2. Gonna use biskeydump.
Yes, you're ok to remove it while in hekate's menus.
How does this not cause corruption as surely the card is mounted? I'm using ExFAT so a bit worried about corruption that's all. Being able to do this would save me plenty of time.Yes, you're ok to remove it while in hekate's menus.
How does this not cause corruption as surely the card is mounted? I'm using ExFAT so a bit worried about corruption that's all. Being able to do this would save me plenty of time.
Sent from my COR-L29 using Tapatalk
You're not writing to the SD card, even though it's mounted, so...
better yet, turn off your console, take it out, then inject hekate again