Hacking RELEASE CTCaer's Hekate w/ Battery Desync Fix

[Lumince]

Thanks dude hopefully I can fix it's on charge now leaving it there for a bit to see if it helps

You'll have to open up your switch and unplug the battery and replug it back it to re sync it and allow it to boot... No amount of charging will fix this, but you can try!

 

[ShadowXin225]

I have a tri wing screwdriver but it doesn't unscrew the screws for some reason :/

 

[subcon959]

It has to be the right size plus some of the screws are really crap and strip very easily so be careful.

Also, I think it's fine to compile things for yourself to test but it might be best to wait for devs to decide when something is ready for public release. I was playing with this last night to test the nand dump verification but didn't share it with anyone just in case there were bugs.

 

[ShadowXin225]

I can't actually open it because the screws are fked it's a triple 0 triwing screw driver as well fek

 

[subcon959]

Yeah, I have a feeling Nintendo used easily stripped screws on purpose. Some people had luck using small drill bits but I would not feel confident trying that myself.

 

[tivanh]

Yeah, I have a feeling Nintendo used easily stripped screws on purpose. Some people had luck using small drill bits but I would not feel confident trying that myself.

You'll need to find the correct size 'extractor' drill bit. They normally come in packs and are quite expensive for the high tensile steel ones. They work very well though and will solve the problem without much effort.

A good tradesman always has the right tools, right....

 

[ShadowXin225]

Help I can get to the battery via the right rail if I open it only problem is the heat plate

--------------------- MERGED ---------------------------

But yet again the screws are fucked

 

[Clydefrosch]

jesus man stop abusing your switch already.

 

[iBlackSunday]

CTCaer, could we get an official release from you so we know that there aren't any issues with the release. I never compile any sources simply because I know the reason why they are only commits is because there are a bunch of other things that need to be fixed. Would you agree this source is stable enough to be an official release (2.4?)

 

[APartOfMe]

Help I can get to the battery via the right rail if I open it only problem is the heat plate

--------------------- MERGED ---------------------------

But yet again the screws are fucked

You only need to unscrew the middle screws on the joy-con rails.

 

[subcon959]

CTCaer, could we get an official release from you so we know that there aren't any issues with the release. I never compile any sources simply because I know the reason why they are only commits is because there are a bunch of other things that need to be fixed. Would you agree this source is stable enough to be an official release (2.4?)

If you understand then why are you asking that question? He will release it when it's free of bugs and ready to be released.

 

[CTCaer]

I tweeted you about the problem on Monday. What I basically did was plugging off USB before hekate told me to. It ended up not bootable. I charged it for 2h and still nothing. Then I decided to open up my switch, disconnect the battery by hand, reconnect it after 1 minute and then it booted again. So it looks like plug off USB too early makes this a bit buggy, but still fixable

AutoRCM or not?

I'm trying to find out if this is because of this or the USB thing.
(AutoRCM, btw, matters to USB only and not the battery charger.)

Still it's very strange. Only a a power usb cable is enough to re-enable it.
But if autorcm is at fault here, I have a mitigation in mind.

By the way, what's your twitter handle if you don't mind? (send it via PM)

-------------------------------

Anyone that has this problem and is going to open the cover as a final resolution, PM me. I can produce a payload that we can check what is happening.


EDIT:
------------------------

CTCaer, could we get an official release from you so we know that there aren't any issues with the release. I never compile any sources simply because I know the reason why they are only commits is because there are a bunch of other things that need to be fixed. Would you agree this source is stable enough to be an official release (2.4?)

The source currently is not stable at all. I'm committing bytes and bits, so I don't have to do it all in one. I have still hundreds of lines of code locally.
But as always, a new bug arises and stops me from release..

 

[mattytrog]

AutoRCM or not?

I'm trying to find out if this is because of this or the USB thing.
(AutoRCM, btw, matters to USB only and not the battery charger.)

Still it's very strange. Only a a power usb cable is enough to re-enable it.
But if autorcm is at fault here, I have a mitigation in mind.

By the way, what's your twitter handle if you don't mind? (send it via PM)

-------------------------------

Anyone that has this problem and is going to open the cover as a final resolution, PM me. I can produce a payload that we can check what is happening.


EDIT:
------------------------


The source currently is not stable at all. I'm committing bytes and bits, so I don't have to do it all in one. I have still hundreds of lines of code locally.
But as always, a new bug arises and stops me from release..

I`ve tested the payload via an internally modded (trinket) switch. I am using SX loader as the primary loader. AutoRCM enabled.

My findings running the payload after SX loader (through the menu):

• The switch does appear dead after using.
• It ISNT dead though. It is in RCM. Though a special form it seems of RCM. Looks like the PMIC stays in a disabled state. Therefore it won`t even boot from the Trinket.
• The trinket won`t even make it boot It looks like, because the trinket is running at 3v3. It needs at least 4.7 volts ish to kick it out of this vegatative state. Bit like how a powerbank stops its batteries becoming completely discharged.
  
• It will boot and full service restored upon sending a payload from the PC. Or once an external payload sender with decent voltage is plugged in. Look in TegraRCMsmash for "found" to check if it is in RCM.

So no, the switch isn`t dead. And the payload / theory works. Battery successfully recalibrated. Clock is reset though.

Doesn`t make a difference how long you leave it connected to USB.

I find it very useful, bearing in mind you need to be near an external decent powered payload.

 

[scionae]

Ran the payload and I had no problems, battery recalibrated and clock reset. I just left it there sitting for 5 minutes while charging and ran the SX payload via PC. All good! (yes, I have AutoRCM)

 

[Tigeris tiger]

Awesome! I was just minutes from tearing down my switch to fix it and happen to see this. I am running AutoRCM and did have to hold the power down for a little bit. Reconnected my cable and turned right on. Of course reset the time and what not. But seems to be working.

 

[CTCaer]

I`ve tested the payload via an internally modded (trinket) switch. I am using SX loader as the primary loader. AutoRCM enabled.

My findings running the payload after SX loader (through the menu):

• The switch does appear dead after using.
• It ISNT dead though. It is in RCM. Though a special form it seems of RCM. Looks like the PMIC stays in a disabled state. Therefore it won`t even boot from the Trinket.
• The trinket won`t even make it boot It looks like, because the trinket is running at 3v3. It needs at least 4.7 volts ish to kick it out of this vegatative state. Bit like how a powerbank stops its batteries becoming completely discharged.
  
• It will boot and full service restored upon sending a payload from the PC. Or once an external payload sender with decent voltage is plugged in. Look in TegraRCMsmash for "found" to check if it is in RCM.

So no, the switch isn`t dead. And the payload / theory works. Battery successfully recalibrated. Clock is reset though.

Doesn`t make a difference how long you leave it connected to USB.

I find it very useful, bearing in mind you need to be near an external decent powered payload.

That should be correct. Because the datasheet also talks about plugging an adapter to enable it.
But other users said that they tried that and also tried through PC to send the payload.

 

[Leanny]

AutoRCM or not?

I'm trying to find out if this is because of this or the USB thing.
(AutoRCM, btw, matters to USB only and not the battery charger.)

Still it's very strange. Only a a power usb cable is enough to re-enable it.
But if autorcm is at fault here, I have a mitigation in mind.

By the way, what's your twitter handle if you don't mind? (send it via PM)

AutoRCM was enabled. I DM you the handle

 

[Joom]

My user is not GalaxyYT...

Glad to see naive YouTubers conducting the hype train yet again. It's so scummy it's not even funny. "Gotta get them views for someone else's work, man. Gotta make sure I slap my logo all over it and nonchalantly credit the dev in the description, maaaaan."

 

[CTCaer]

AutoRCM was enabled. I DM you the handle

The other one that powered-on right away had AutoRCM?

Additionally,
For the switch with AutoRCM:
So you charged it, after that, how you tried to send the payload?

Normally the way to go for autorcm is:
Payload.
Remove usb.
Run fix.
Press PWR for 12-15s to completely power off again. (This should be optional though...)
Connect wall adapter or PC (you need a source that can give ~500mA and more. Smartphones are ~200mA max and other even less)
Normally from a complete power off, you have to press [PWR] or [PWR + VOL UP](for no autorcm) to switch on again.
Run the payload so you can boot into HOS.

Normal procedure for NO AutoRCM:
Payload.
Remove usb.
Run fix.
Connect usb with adequate charge capabilities (~500mA+).
It will boot to HOS if enough charge, otherwise red battery icon charging screen.

Glad to see naive YouTubers conducting the hype train yet again. It's so scummy it's not even funny. "Gotta get them views for someone else's work, man. Gotta make sure I slap my logo all over it and nonchalantly credit the dev in the description, maaaaan."

My problem is not that this was compiled, released and used.
It's open source, everyone can do anything, as long as he includes or links to the source code that can produce the exact same binary.

My problem is that, without reading, they assume that I released this binary.

 

[Joom]

My problem is not that this was compiled, released and used.
It's open source, everyone can do anything, as long as he includes or links to the source code that can produce the exact same binary.
.

I don't have a problem with this, either. I promote this. The community takes responsibility for free bug testing, and anyone should be free to read and compile the code at whim. My problem lies with hype that drives noobs into console ruining bugs by having them run alpha stuff and PoCs.