New version coming...
With Lockpick included. Get all your device keys from within Hekate.
Unused tools cleaned up to make space. Coming either tonight or tomorrow. Check OP for your download.
New version coming...
With Lockpick included. Get all your device keys from within Hekate.
Unused tools cleaned up to make space. Coming either tonight or tomorrow. Check OP for your download.
Yes you need Trinket / Rebug UF2. @Post 2.
Then you need Atmosphere.
Either launch directly from Hekate menus or rename fusee-primary to payload.bin for fully automatic boot.
I`m sure we have been through this the other night. Puzzled I am!
u said trinket/debugYes you need Trinket / Rebug UF2. @Post 2.
Then you need Atmosphere.
Either launch directly from Hekate menus or rename fusee-primary to payload.bin for fully automatic boot.
I`m sure we have been through this the other night. Puzzled I am!
--------------------- MERGED ---------------------------
can I install the old method 1n 2 the the four wire install thanks
--------------------- MERGED ---------------------------
N do u rename atmosphere to payload.bin on sd card
Yes. Install however you like.
Use the Trinket / Rebug file. Then you can either build your own Kosmos SD card, or just use Atmosphere. Rename fusee-primary to payload.bin and it will launch every time.
OK... Think we are good to go with a release. But before I do, could someone do a test with this TRINKET/ REBUG UF2?
Sept supported.
To dump keys on FW 7 on, you will need the sept folder in SD root.
If you have a "payload.bin" set up, you will need to hold vol- to get to menu each boot.
Remember, if you have ran sept, rebooted and not caught the menu in time, you will get a black screen.
If testing key dump feature (credit to shchmue for Lockpick), I recommend not having a payload.bin set up
EDIT: Last minute change. Redownload below file.
In dumping key process, reboot is taken care of automatically now.
So, if on 7.0.0 or 7.0.1 and you have sept folder, you can use this correctly now.
Sept supported.
To dump keys on FW 7 on, you will need the sept folder in SD root.
If you have a "payload.bin" set up, you will need to hold vol- to get to menu each boot.
Remember, if you have ran sept, rebooted and not caught the menu in time, you will get a black screen.
If testing key dump feature (credit to shchmue for Lockpick), I recommend not having a payload.bin set up
EDIT: Last minute change. Redownload below file.
In dumping key process, reboot is taken care of automatically now.
So, if on 7.0.0 or 7.0.1 and you have sept folder, you can use this correctly now.
Last edited by mattytrog,
Looks pretty good to me. I just poked around a bit, tested Lockpick_RCM and the about screen. Not sure if they're intended, but I have a bunch of blank lines in the about screen under the payload and mode info:
EDIT: Also, the previous version I was running (maybe a test) had info like USB strap detection status. Will that be coming back, or is that supposed to be where the blank lines are?
Last edited by feral,
Yeah the black space with the dashes is a placeholder for more information. It makes my life easier as Simple-UF2 cuts and creates the payload on the fly on the chip, when the chip boots.Looks pretty good to me. I just poked around a bit, tested Lockpick_RCM and the about screen. Not sure if they're intended, but I have a bunch of blank lines in the about screen under the payload and mode info:
EDIT: Also, the previous version I was running (maybe a test) had info like USB strap detection status. Will that be coming back, or is that supposed to be where the blank lines are?
I've changed a bit more code, placing a sept check (I know hekate does it, but I didn't want lockpickrcm to create any problems in dumping PKG for example).
So if sept isn't active, payload.bin will run.
Got to finish placing strap detection code there but that's two minutes.
Will be tomorrow now. All chips will be finished and pushed. Thanks for testing!
Last edited by mattytrog,
Amazing work. Will be ever possible to update the modchip from SD? Sometimes it's difficult to press the reset button with closed housing.
Another question: I used a new revision of Hekate (as payload.bin, to not open the Switch every Hekate release) that has autoboot to CFW, and I can get to Hekate menu pressing Vol-. What Hekate menu will I get pressing vol- with the oncoming Simple-UF2 update, the SD one or the Modchip one?
Another question: I used a new revision of Hekate (as payload.bin, to not open the Switch every Hekate release) that has autoboot to CFW, and I can get to Hekate menu pressing Vol-. What Hekate menu will I get pressing vol- with the oncoming Simple-UF2 update, the SD one or the Modchip one?
Yes it will be possible. However, you will still need to double-press reset to get into bootloader (SWITCHBOOT UF2) update mode.
Unless I open the USB serial twice at 1200 baud. Should do same job. However, in host mode, this is doubtful.
Anyway, final screenie. Making UF2s now. Or shortly.
Unless I open the USB serial twice at 1200 baud. Should do same job. However, in host mode, this is doubtful.
Anyway, final screenie. Making UF2s now. Or shortly.
OK... 0.9.9r4 Changelog:
- Latest Hekate changes (4.9.1)
- Derive all keys from within Hekate / Simple-UF2 thanks to Shchmue`s Lockpick which a modified version is built-in
- Strap detection properly implemented - Upon finding strap, the check routine is locked and stored as true
- RCMX86 gremlins "should" be a thing of the past. But then again maybe not
- Adjustable DotStar brightness for dotstar equipped boards
- *LiveRCM is disabled in this version as I have nobody to test it may add it in next "release")
- Sept required if using FW 7+ and you wish to derive keys
- Power-on text (looking for payload) removed as per user request
- Uploading shortly
What do you need help with testing mate? I’ve got some time now if you need toOK... 0.9.9r4 Changelog:
- Latest Hekate changes (4.9.1)
- Derive all keys from within Hekate / Simple-UF2 thanks to Shchmue`s Lockpick which a modified version is built-in
- Strap detection properly implemented - Upon finding strap, the check routine is locked and stored as true
- RCMX86 gremlins "should" be a thing of the past. But then again maybe not
- Adjustable DotStar brightness for dotstar equipped boards
- *LiveRCM is disabled in this version as I have nobody to test it
- Sept required if using FW 7+ and you wish to derive keys
- Power-on text (looking for payload) removed as per user request
- Uploading shortly
Just this "LiveRCM" feature I have made. Too late for this version now.
What it does, is, in conjunction with Atmosphere`s reboot-to-payload feature, enables and disables autoRCM on the fly.
So, should big N query it, BCT should look original. During hard power-down, autoRCM will be re-enabled. This is REALLY meant for the old method 1 (4-wire) users. And maybe to a lesser extent, dongles.
It is attempting to eliminate the need for a jig but keeping a legit looking emmc on show. But, how it actually works in practice remains to be seen. But it is working well here...
Last edited by mattytrog,
Don’t usually need spoon feeding, but tell me how to do it and I can test on multiple switches?
Would anybody have a high res scan of the PCB like in the instructions but without the markings by chance? I messed up a pad and need to repair it, but it's simply too small to see with the gear I have at home, but a scanned board would be insanely easier... I was a dummy and accidentally pulled on a wire and ripped out the v+ resistor and one of the pads
Very kind of you sir! I will do tomorrow. Brain fogging over tonight! 0.9.9r4 now online.
--------------------- MERGED ---------------------------
In ther modchip thread there are pictures. May be better off to take it to that thread and upload some pictures? I can give you help.Would anybody have a high res scan of the PCB like in the instructions but without the markings by chance? I messed up a pad and need to repair it, but it's simply too small to see with the gear I have at home, but a scanned board would be insanely easier... I was a dummy and accidentally pulled on a wire and ripped out the v+ resistor and one of the pads
I should probably add that if anyone is after a generic version of this Hekate then it is in my git in post 2.
It's just a standard bin file that you can launch with any dongle/software.
Changes over normal hekate are getting a bit long now. This isn't meant to be better than the official one, but my take on it and some useful additional features. Maybe.
In summary...
Thank you to everyone who has tested this.
It's just a standard bin file that you can launch with any dongle/software.
Changes over normal hekate are getting a bit long now. This isn't meant to be better than the official one, but my take on it and some useful additional features. Maybe.
In summary...
- New font/colour scheme
- Designed to integrate with modchip but is just fine stand-alone.
- Launch payloads from SD root as well as /payloads folder
- Quick backup and restore - boot 0/1 or JUST prodinfo which are kept in a different folder. Designed to be a quick recovery from a malicious file
- Payload.bin chainloader upon first boot. No need to go into hekate to select your payload. Just dump payload.bin on SD root and you are ready to go
- Screenshot feature
- Derive all console keys to a file on SD.
Thank you to everyone who has tested this.
Yep it will do. Reboot. And it will appear. It will only update upon first press. You need to reboot to see changes. Try that.
--------------------- MERGED ---------------------------
Make sure you have joycon plugged in when HOS is booted for strap detection
--------------------- MERGED ---------------------------
Strap detection info everybody who may be interested...
As the payload is loaded, modified and sent on-the-fly according to chip values, you will need to reboot to Hekate to see any changes.
Also, strap detection works by actually sensing a keypress or a joycon detection.
So, for example... First boot...
VOL+ strap Undetected
Joycon strap undetected
All you need to do is press vol+ button. If strap is present and working, info screen will be updated on next boot (however of course it will still work. Just the cosmetic info won`t be updated until you restart).
Same with joycon. Once you have booted into HOS and detached / attached joycon, strap test result will be updated next time you boot.
@mattytrog
Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2,
but the new Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2 does not work for me anymore,
but the previous one already...
When I flash the new UF2, everything looks fine in the beginning,
but as soon as I turn off the console,
all LEDs light up and the console stays black when I want to start the CFW.
Always start the console with + button and power for the CFW
Please help
Thank you and best regards
Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2,
but the new Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2 does not work for me anymore,
but the previous one already...
When I flash the new UF2, everything looks fine in the beginning,
but as soon as I turn off the console,
all LEDs light up and the console stays black when I want to start the CFW.
Always start the console with + button and power for the CFW
Please help
Thank you and best regards
Similar threads
-
Psionic Roshambo
-
K3Nv2
-
The Real Jdbye
*is birb* -
realtimesave
-
-
-
-
-
-
-
@
Psionic Roshambo:
I'm curious.... Is PCSX2 compatible with normal web cams emulating the EyeToy....
-
-
-
@
Psionic Roshambo:
Just looked it up and yes you can use web cams on PCSX2 to play EyeToy games lol
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
