Let's try to stay on topic guys
Philosophical discussions of time are not on topic and will be deleted
Philosophical discussions of time are not on topic and will be deleted
How can I use it? I cant find this options un Hekate menu. Do I need to use Atmos ?Yes. Hekate has an option to boot "stock" which disables all kernel patches but keeps your fuses intact.
Check the hekate config template, it has boot entries for booting stock:
https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini
Note that to boot stock on Firmware 7.0.X, you'll need to download atmosphere 0.8.5 and put it on your SD card. It will still boot stock, but the atmosphere files are needed to get around the FW7+ security measures.
If you're on lower firmware you don't need it.
I copied:Yeah, make sure "/atmosphere/fusee-secondary.bin" (latest one) exists on your SD card and use the "Stock All FW" boot entry from the template.
If you have turned on AutoRCM, than you can't simply boot in OFW with just pressing the power button. That's how AutoRCM works: If you boot the switch, your console enter RCM right away. So how and why do you want to boot in OFW? If you update with ChoiDujourNX and boot in OFW without custom payload, your switch will burn fuses to 7.0.1. That's not what you want. So I suggest you to read what you are installing and how it works before you actually do it.Hello guys, firts of all. Sorry for my bad english. Hope you can help me..
My switch is on 7.0.1, atmosphere 8.5 and payload is hekate 4.8.
I turn on autorcm and autoboot to cfw.
Now my switch when is complete off wont turn on to stock fw if i press power button, also i cant enter in recovery mode +- volume and power.
The only whay for turn it on is plugin my Phone and inject payload with nx loader. Switch turn on and enter into atmosphere.
If i remove my sd card switch dont turn on with power button, only with nx loader and payloader to hekate,so i cant access to stock firmware anymore. I Lunch hekate payload without sd, turn off rcm and autoboot. But is not working.
Also in both case with or without the sd, the switch dont charge the battery if i plug the wall adapte.
On hekate screen a red sing show an error message, sleep Mode files missing.
How can i fix this??
If you have turned on AutoRCM, than you can't simply boot in OFW with just pressing the power button. That's how AutoRCM works: If you boot the switch, your console enter RCM right away. So how and why do you want to boot in OFW? If you update with ChoiDujourNX and boot in OFW without custom payload, your switch will burn fuses to 7.0.1. That's not what you want. So I suggest you to read what you are installing and how it works before you actually do it.
I got it second hand, never hacked with oficial 7.0.1 update vía WiFi. Make a 32gb backup and hack de switch Now autorcm is off, i can enter to OFW. When i plug the jig entre rcm and luch the payload atmosphere auto Lunch. The only way to see the hetake menú is injecting the payload in rcm without the sd card. I turn off autoboot but nothing happend
BOOT0
BOOT1
dumps:
fuses.bin
kfuses.bin
tsec_keys.bin
partitions:
BCPKG2-1-Normal-Main
BCPKG2-2-Normal-Sub
BCPKG2-3-SafeMode-Main
BCPKG2-4-SafeMode-Sub
BCPKG2-5-Repair-Main
BCPKG2-6-Repair-Sub
PRODINFO
PRODINFOF
SAFE
SYSTEM
pkg1:
nxloader.bin
pkg1_decr.bin
secmon.bin
warmboot.bin
pkg2:
ini1.bin
kernel.bin
pkg2_decr.bin
dumps:
fuses.bin
kfuses.bin
I'm looking to clean up my system in preparation for switching to SXOS specifically for emuNAND. While looking at my backup folder from before I did any modding, i noticed that i have a bunch of files, but no rawnand.bin. Does this effect my ability to do a full system restore to clean NAND? Here are the files I have:
Code:BOOT0 BOOT1 dumps: fuses.bin kfuses.bin tsec_keys.bin partitions: BCPKG2-1-Normal-Main BCPKG2-2-Normal-Sub BCPKG2-3-SafeMode-Main BCPKG2-4-SafeMode-Sub BCPKG2-5-Repair-Main BCPKG2-6-Repair-Sub PRODINFO PRODINFOF SAFE SYSTEM pkg1: nxloader.bin pkg1_decr.bin secmon.bin warmboot.bin pkg2: ini1.bin kernel.bin pkg2_decr.bin dumps: fuses.bin kfuses.bin
Really hoping i can still do a clean NAND restore with these files. Any input or guidelines appreciated!
Maybe the formatting of your hekate_ipl.ini doesn't match what Hekate 4.8 is looking for?Is there any reason why hekate_ctcaer_4.8.bin won't launch my AMS 0.8.1 CFW over 6.2.0 when the hekate_ctcaer_4.5.bin payload works great on it? Does 4.8 only work with 7.0.0 and above? When I try to launch CFW from the 4.8 payload it just goes right back into RCM mode while it launches fine from the 4.5 payload. I'm injecting the payloads through TegraRcmGui on PC.
Wrong thread. Sig patches have nothing to do with Hekate. Those are either due to the patches themselves or the CFW you are launching with Hekate which is usually Atmosphere.so all sigpatch problems with hekate are fixed now?