hmm. I guess you could say that. Soft hacking wise, with the current knowledge we have, it is impossible to hack 5.0 for now. The workaround will work for every firmware to date though.
Hacking [RCM] hekate-ipl for 5.0.x + working hb menu
hmm. I guess you could say that. Soft hacking wise, with the current knowledge we have, it is impossible to hack 5.0 for now. The workaround will work for every firmware to date though.
Speaking of which, one last question tho, does the paperclip method work with any kind of paperclip? or does it have to be an exclusively 3D printed one?
You're just shorting two pins. You can use literally anything you want.
doesn't even have to be a paperclip anything conductive that grounds the two pins.
Awight, just being extra cautious since I dont wanna risk using a material that could possibly damage the pins.
I was using a paperclip and scratched the right rail every time I wanted to launch a fuseé payload. I ended up buying a 3D printed jig on eBay for $4 US, first class shipping included.
Here’s the link: https://www.ebay.com/itm/Pre-installed-Pins-Nintendo-Switch-RCM-Jig-/263652815683
Last edited by Dread_Pirate_PJ,
you could just solder a wire between the test pins on the joycon mainboard like i did. super easy, as shown in this pic
although if you're not using a micro switch or something to ground the joycons only when you wanna enter rcm mode, the joycon only works in wireless mode.
although if you're not using a micro switch or something to ground the joycons only when you wanna enter rcm mode, the joycon only works in wireless mode.
Hey,
A fair few Samsung micro SD cards refuse to mount due to the differing voltage they run at. There's a fix in this hekate branch here: https://gbatemp.net/threads/rcm-payload-hekate-mod-raw-full-nand-backup.502604/
Any chance of this fix being added to yours? I have 5.0.2 and 256gb Samsung SD I'd very much like to use.
Not sure if atmosphere already has the fix or not.
Is it normal for the switch to just power off when it goes into sleep mode or you press the button to enter sleep when using this?
- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,482
- Country
EDIT:
It was ExFAT causing issues. If in doubt, use FAT32.
Original post:
I'm having a few read/write issues with homebrew, can someone please check/confirm my hunch?
I set up the SD contents on my PC, with a /switch/ folder containing the Checkpoint .nro file, then copied it to two consoles:
- Switch running 4.x, 32GB FAT32 micro SD card
- Switch running 5.x, 128GB ExFAT micro SD card
I then launched the appropriate version of Hekate (the one from this thread for the 5.x console, the one from the 4.x thread for the 4.x console), achieving different results.
- On the 4.x console, HB menu loads successfully and I was able to launch Checkpoint and backup my saves.
- On the 5.x console, HB menu loads successfully, however it fails to detect the /switch/ folder at all.
For the 5.x console, I bypassed this initial issue by renaming Checkpoint.nro to hbmenu.nro and moving it to the root of the SD card. Checkpoint then launches successfully, but whenever I try to backup any save it will trigger the generic system error message and prompt me to shut down.
Checkpoint failed to write the folders used for save backup, so I manually added those and tried again, this time either I get a message saying that saves were successfully backed up, or the same error message prompting me to power down. Either way, no saves were dumped to the folders I made.
It seems that on the 5.x console, homebrew can read NAND, but is unable to read any content from the SD card, and any attempt to write to the SD card will cause an error.
I can fathom that this is due to two possible issues:
- Homebrew simply isn't running normally on 5.x because it's still early stages and errors are to be expected.
- Homebrew is having trouble working with ExFAT SD cards.
Currently I'm leaning towards scenario #2, but what do you think? I'm going to re-run this test with a FAT32 card instead, after work today.
It was ExFAT causing issues. If in doubt, use FAT32.
Original post:
I'm having a few read/write issues with homebrew, can someone please check/confirm my hunch?
I set up the SD contents on my PC, with a /switch/ folder containing the Checkpoint .nro file, then copied it to two consoles:
- Switch running 4.x, 32GB FAT32 micro SD card
- Switch running 5.x, 128GB ExFAT micro SD card
I then launched the appropriate version of Hekate (the one from this thread for the 5.x console, the one from the 4.x thread for the 4.x console), achieving different results.
- On the 4.x console, HB menu loads successfully and I was able to launch Checkpoint and backup my saves.
- On the 5.x console, HB menu loads successfully, however it fails to detect the /switch/ folder at all.
For the 5.x console, I bypassed this initial issue by renaming Checkpoint.nro to hbmenu.nro and moving it to the root of the SD card. Checkpoint then launches successfully, but whenever I try to backup any save it will trigger the generic system error message and prompt me to shut down.
Checkpoint failed to write the folders used for save backup, so I manually added those and tried again, this time either I get a message saying that saves were successfully backed up, or the same error message prompting me to power down. Either way, no saves were dumped to the folders I made.
It seems that on the 5.x console, homebrew can read NAND, but is unable to read any content from the SD card, and any attempt to write to the SD card will cause an error.
I can fathom that this is due to two possible issues:
- Homebrew simply isn't running normally on 5.x because it's still early stages and errors are to be expected.
- Homebrew is having trouble working with ExFAT SD cards.
Currently I'm leaning towards scenario #2, but what do you think? I'm going to re-run this test with a FAT32 card instead, after work today.
Last edited by NekoMichi,
Can anyone else. confirm this method works in the img for the mod because I have never heard of it or can I google it? He’s saying you can solder the two end test pads together or use a wire maybe, it’s above the pins it’s under the black sponge on the rail.
Last edited by Reecey,
- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,482
- Country
Soldering pads for 9 and 10 will work if you re-assemble the full Joy-Con along with the main board circuitry. If you just want to use the rail part, you'll need to bridge pad 7 to 10.
So if I solder a small piece of wire between the two he’s circled in the picture that will 100% work? You might need to zoom in on the picture to see the circled pads properly. The reason I’m asking this I have a brand new right assembly rail in front of me now and I was going to solder a small wire between the two he’s circled but I want to make sure it works.. I’m sure if I heat the solder pads up again I can drop a wire between the two connecting them both.
You say pads 7 & 10 are they the ones he’s circled in the photo or 9 & 10? I am connecting the joy con back together fully?
I was going to drop a wire in it, it looks to close to the other pads to drop solder between the two to connect, just in case I catch the other pad that’s very close to pad 10.
What’s the best way to get the black sponge off? Tried tweezers not working it seems very stubborn.
Last edited by Reecey,
Can somebody explain to me how I use this? If I'm understanding right I gotta enter rcm mode then boot fluss glee then boot into this?
You don't need to actually boot the fusee test payload if that's what you mean. You send this payload instead.
Solder suckers work a treat I have one myself and used one for years on fruit machines. I can assure everyone that will work a treat to get your solder off and they work well!
Similar threads
