That's because of incompatibilities with content in sd card. Especially if you updated these.
Just redownload them.
I had everything ready to push.@CTCaer 6.0 is out OwO
Woah, really? I guess they had that original 6.0 set for release around when the direct was pushed back! Night!I had everything ready to push.
But it's a new revision. Don't know what's broken yet.
For now I'll go to sleep at last.
Tomorrow we'll see.
I had everything ready to push.
But it's a new revision. Don't know what's broken yet.
For now I'll go to sleep at last.
Tomorrow we'll see.
Yesit's possible, with 4.1, to boot sxos ?
It's not just enough, it's a full restore/downgrade.Backup BOOT0/1 and rawnand is enough to potential downgrade?
Hooray!! Cheers for the quick work!!hekate v4.1 is now released!
hekate v4.1 is now released!
Check changelog for more..
(The features guide will be updated in the next days to accommodate v4.0 and v4.1)
It could be in the future. (Actually, it's an old request and I forgot to check this xD)The update is much appreciated!
Also if we could have the "autoboot" option for payloads chainbooting, that will be golden!
Not being here for so long (work issues) so @CTCaer if I update to 6.0.0 does Hetake works? Sorry for my ignorance... thanks mate for everythingIt could be in the future. (Actually, it's an old request and I forgot to check this xD)
For now use a tiny .ini with the boot entry name and the payload key. And throw it inside /bootloader/ini.
It will show up in the autoboot option menu.
Not being here for so long (work issues) so @CTCaer if I update to 6.0.0 does Hetake works? Sorry for my ignorance... thanks mate for everything
What crash? Where/when?trying to boot sxos and crash. . help
That's the auto power off if the power off was initiated from HOS. I have a mitigation for ppl that don't want it in an issue in github. Use this for now.Each time I inject the payload with TegraRCM I get the Hedake -IPL splash screen then it just fades to black and hangs. No menu is comming up
Hmm where's the problem here? That's normal. Hekate sees the power off from hos and powers off completely.I have a question regarding
I'm new to AutoRCM and I plan to use it for 6.0 update.
- Auto full power off when the device woke up from HOS' power off
Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).
I have applied autorcm and now if I 'turn off' from HOS does that mean the device is fully off ?
I tried to use my r4s dongle after i turned it off and I see a hekate logo for a second and then a black screen also my r4s led turns off too.
I tried to turn on the device with no dongle attached and i don't see anything. it only turns on when the dongle is attached.
sorry this may seem a little bit complicated English is not my first language.
thanks