Hacking COMPLETED BASIC MODCHIP / DONGLE UF2 SD BOOT FILES. Trinket / Rebug / RCMX86 / Others

joaomconde · Dec 3, 2018

hi guys, just wanted to say am in the same situation... first time modding such a "hard" project, now am stuck on black screen, but no problem, can access SWITCHBOOT folder (hopefully will be fixable via it) and i am patient so i just wanted to thank matty for such comprehensive guide!
Also, 3 questions now that i have the hard part done: How should i deal with the metal backplate? not install it or simply cut it? Also, i feel my connections are too fragile.. are they not? how should i proceed making them stronger? and at last, my trinket m0 is completely free should i glue it or something? how should i do it?

Again thanks for all.

mattytrog · Dec 3, 2018

New version pushed to github. No UF2s built yet.

Changelog:

It isn't fucked any more... Black screen bug resolved.
Simplified with just 6 modes now.
Hekate is payload 1 by default built in. Modes 1,3,4 and 6.
1.nx changed to look for start.bin instead of 0.nx. indication graphic updated.
0 folder just has 8 nx files now. These can be replaced with ones from the "unusednxfiles" folder.
Changes to flash storage so the lock up problem (which I had a report on) is fixed.

Devices supported:

Trinket/Gemma/itsybitsy/feather/Rebug/RCMX86/R4S.

Look on my git and build yourself or wait until I've made some UF2s

https://github.com/mattytrog/All-In-One-Nintendo-Switch-SAMD-Launcher-for-SAMD-21-modchips

snam11 · Dec 3, 2018

great job, and i hope as soon i'll get this bad boy

Code:

https://github.com/euclala/RCM-X86/tree/master/internalDongle

you can add support for it!

iriez · Dec 3, 2018

mattytrog said:
New version pushed to github. No UF2s built yet.

Changelog:

It isn't fucked any more...

Simplified with just 6 modes now.

Hekate is payload 1 by default built in. Modes 1,3,4 and 6.

1.nx changed to look for start.bin instead of 0.nx. indication graphic updated.

0 folder just has 8 nx files now. These can be replaced with ones from the "unusednxfiles" folder.

Devices supported:

Trinket/Gemma/itsybitsy/feather/Rebug/RCMX86/R4S.

Look on my git and build yourself or wait until I've made some UF2s

https://github.com/mattytrog/All-In-One-Nintendo-Switch-SAMD-Launcher-for-SAMD-21-modchips

Thanks mattytrog. Im going through the main.ino right now and digesting the changes. In reference to this section, does nxpart1.h (and 2/3) have to be present in order for this to write to flash? I ask because I don't use any of the payload increase options, so I really only ever need to flash a specific payload. Also, can you enable downloads on all the .h and .ino files? As of right now i have to click raw, copy/paste and rename files in order to get them.

//includes
#include "hekate.h"
#include "nxpart1.h"
#include "nxpart2.h"
#include "nxpart3.h"
#include "usb_setup.h"
#include "modes.h"
#include "boards.h"

mattytrog · Dec 3, 2018

iriez said:
Thanks mattytrog. Im going through the main.ino right now and digesting the changes. In reference to this section, does nxpart1.h (and 2/3) have to be present in order for this to write to flash? I ask because I don't use any of the payload increase options, so I really only ever need to flash a specific payload. Also, can you enable downloads on all the .h and .ino files? As of right now i have to click raw, copy/paste and rename files in order to get them.

//includes
#include "hekate.h"
#include "nxpart1.h"
#include "nxpart2.h"
#include "nxpart3.h"
#include "usb_setup.h"
#include "modes.h"
#include "boards.h"

You can leave them out. But I`d leave them in. Build it on mode 1 (for Hekate) instead. It is just wasted space otherwise. Can`t fit anything else in there unless you remove Hekate. If you would like a custom version with 3 payloads built in (as long as its all under 220k ish) I can.

BTW nxpart1,2 & 3 is probably around 42kb, give or take. Thats 8 payloads in 42kb, just over 5k per payload. Not worth removing. You don`t have to use them at all! Just forget they are there. I wouldn`t go ripping them out. Just don`t use the 0 folder and in mode 1, its just a "normal" Hekate UF2.

noX1609 · Dec 3, 2018

mattytrog said:
New version pushed to github. No UF2s built yet.

Changelog:

It isn't fucked any more... Black screen bug resolved.

Simplified with just 6 modes now.

Hekate is payload 1 by default built in. Modes 1,3,4 and 6.

1.nx changed to look for start.bin instead of 0.nx. indication graphic updated.

0 folder just has 8 nx files now. These can be replaced with ones from the "unusednxfiles" folder.

Changes to flash storage so the lock up problem (which I had a report on) is fixed.

Devices supported:

Trinket/Gemma/itsybitsy/feather/Rebug/RCMX86/R4S.

Look on my git and build yourself or wait until I've made some UF2s

https://github.com/mattytrog/All-In-One-Nintendo-Switch-SAMD-Launcher-for-SAMD-21-modchips

Thank you for your great work, looking forward using this when the UF2 Files are finished/created

Acide0 · Dec 3, 2018

Hi, could I got more informations to setup the files. I got the trinket install with a permanent 5v and I use the old system with the 0 folder and inside the payload(reinx) named start.bin.

To use the new method with the .nx files what I need to do ? Flash the new uf2 file(when it will be availible) to the trinket ?

After how the nx files work ?

I want to start the atmosphere payload thank you.

Edit:

So finally with the new uf2 files and I couple of testing I have figured out on how the thing work.

mattytrog · Dec 3, 2018

OK... Started using "version" numbers. You know, like the big boys use. I just use them internally before I piss around with my code. Got to start doing things properly Mattytrog!

Latest "release" is v0.8.1... Yep. I`ve molested this that much, thats where I am at. Or I was before I had to rewrite a load... UF2s are there in the zip.

Any senior developers, please don`t give me a hard time over the way I do things... My coding skills are still stuck in 1993 with a little bit of 2018 thrown in.

Gismor · Dec 3, 2018

When i will use only single payload is this example right?

First i can delete in the folder "0" 2.nx - 8.nx file
only i have the 1.nx file.
Second part i copy my payload for example the "reinx.bin" in the folder unusedNXfile and i rename the "reinx.bin" to "1.nx"
and thats all.

do i understand this right?
why i need this folder"nxfilessparebackup"
thanks for helping me =)

mattytrog · Dec 3, 2018

Gismor said:
When i will use only single payload is this example right?

First i can delete in the folder "0" 2.nx - 8.nx file
only i have the 1.nx file.
Second part i copy my payload for example the "reinx.bin" in the folder unusedNXfile and i rename the "reinx.bin" to "1.nx"
and thats all.

do i understand this right?
why i need this folder"nxfilessparebackup"
thanks for helping me =)

Sorry. That is rather unclear of me. Apologies!

Right... If using the new version (0.8.1 I think its on), and you are using a single payload ONLY (ie "mode2" UF2, all you need is 1.nx now. Rename your "ReiNX.bin" to "start.bin" and place in 0 folder. Thats all.

I`ve been doing a lot of chopping and changing of files and stuff over the weeks and months.
But it is now staying like this. How 0.8.1 is setup, I think is the simplest and covers all usage scenarios. If anyone is using an old version, then thats fine. Upgrade if you wish. No need to though.

Feel free to delete any nx`s you aren`t using. I`ve made a new table I`m about to upload.
In the unusedNXfiles folder... You can put a different NX file there to run "start.bin" from the root of SD rather than the 0 folder.

@Gismor If ever you are unsure what files you need, just eject your SD card and power on. It will tell you

Also mode table added. OP being updated. Should be semi-correct now. I`m sure someone will want my scalp if not :rofl2:

Gismor · Dec 3, 2018

thanks a lot will try it tommorow

its "mode2" a DualBoot or boot it default in the CFW?

mattytrog · Dec 3, 2018

Gismor said:
thanks a lot will try it tommorow
its "mode2" a DualBoot or boot it default in the CFW?

Its both, and neither...

Depends how you have got your straps / UF2 bootloader set up.

We published a load of bootloaders not so long ago. Not sure if you were aware. No more permanent power needed.

Take a look in OP of "Internal modchip" thread in Tutorials section for more info

joaomconde · Dec 3, 2018

flashed the new UF2, its working perfectly not! thanks!!

Also, 3 questions now that i have the hard part done: How should i deal with the metal backplate? not install it or simply cut it? Also, i feel my connections are too fragile.. are they not? how should i proceed making them stronger? and at last, my trinket m0 is completely free should i glue it or something? how should i do it?

mattytrog · Dec 3, 2018

joaomconde said:
flashed the new UF2, its working perfectly not! thanks!!

Also, 3 questions now that i have the hard part done: How should i deal with the metal backplate? not install it or simply cut it? Also, i feel my connections are too fragile.. are they not? how should i proceed making them stronger? and at last, my trinket m0 is completely free should i glue it or something? how should i do it?

Hello!

flashed the new UF2, its working perfectly not! - not? or now? (typo?) I hope it is working

Right... lets attack this...

How should i deal with the metal backplate? not install it or simply cut it?

Cut it. Like this...

Also, i feel my connections are too fragile.. are they not?

Only you can answer that. What size wire did you use? Use A TINY BIT of epoxy on various points where your wires go if you are worried. Never apply to bare components... Only ever to the green parts of the PCB.

and at last, my trinket m0 is completely free should i glue it or something? how should i do it?

Stick it to the RAM shield. Use double-sided tape. Make sure the Trinket is COMPLETELY isolated from the metal of the shielding... ie make sure your tape is covering the whole underside of the Trinket.

joaomconde · Dec 3, 2018

mattytrog said:
Hello!

flashed the new UF2, its working perfectly not! - not? or now? (typo?) I hope it is working

TYPO!! i meant now!! will not edit it so your reply makes sense!

thanks for the rest of the tips, will try cut the metal.

"What size did you use?" honestly, i dont know, used wires from old bluetooth laptop component. Was going to use the inside wires from an ethernet cable but found they were AWG24 and read in your guide that was too thick, so i used this ones wich are much (MUCH) thinner, also they are made of multiple even thinner wires. Seems fragile but also seems it can last as long they dont suffer forces pulling them. Using the tape to stick the chip should also help it.

Again, thanks for it all!

mattytrog · Dec 3, 2018

joaomconde said:
TYPO!! i meant now!! will not edit it so your reply makes sense!

thanks for the rest of the tips, will try cut the metal.

"What size did you use?" honestly, i dont know, used wires from old bluetooth laptop component. Was going to use the inside wires from an ethernet cable but found they were AWG24 and read in your guide that was too thick, so i used this ones wich are much (MUCH) thinner, also they are made of multiple even thinner wires. Seems fragile but also seems it can last as long they dont suffer forces pulling them. Using the tape to stick the chip should also help it.

Again, thanks for it all!

Thanks for feedback.

Wires should be fine. I use awg40 a lot. That's hair thin!

Well done!

joaomconde · Dec 4, 2018

all done! can you just give a look to see if everything looks all right? (cant get better pictures, but just want a general look)
I put tape under it. Should i put over it too?

PSxed · Dec 4, 2018

mattytrog said:
Here you go gents. @Osmiza @PSxed

To run Atmosphere as a temporary solution...
I`m assuming you are using the 0 folder version of the chainloader... (0.nx + start.bin error when ejecting SD. CHECK THIS!)

Steps:

1) Download this file
2) Put your SD card in PC
3) Rename your current 0.nx file to something else (ie old0.nx)
4) In the download attached is a replacement 0.nx
5) Drag it to your 0 folder
6) Make sure BCT.ini, atmosphere folder and fusee-secondary are in the root of SD where they should be...
7) Put SD back in switch. Should boot.

This is a temporary solution until I have figured out whats happening. Looks like a hwinit problem.

I see that there's a dedicated atmosphere package now. Any major differences from this specific package you created for me a while back?

mattytrog · Dec 4, 2018

PSxed said:
I see that there's a dedicated atmosphere package now. Any major differences from this specific package you created for me a while back?

No but I am just about to upload the latest! Hang on

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

0 folder updated with atmosphere fusee-primary in UnusedNXfiles. Rename to your desired nx (ie 1.nx) and put Atmosphere on SD card as usual.

subcon959 · Dec 4, 2018

I haven't messed with this stuff for months, and got a new pc since then, and now having a dog of a time getting access to trinketboot. I'm using the same usb cable that worked previously so I assume that the issue is the new usb ports? I can get the trinketboot drive to appear but it vanishes again instantly, so I can't flash anything to it. Very frustrating.

Hacking COMPLETED BASIC MODCHIP / DONGLE UF2 SD BOOT FILES. Trinket / Rebug / RCMX86 / Others

Member

You don`t want to listen to anything I say.

Well-Known Member

Well-Known Member

You don`t want to listen to anything I say.

B9S freak ;)

Well-Known Member

You don`t want to listen to anything I say.

Well-Known Member

You don`t want to listen to anything I say.

Well-Known Member

You don`t want to listen to anything I say.

Member

You don`t want to listen to anything I say.

Member

You don`t want to listen to anything I say.

Member

Attachments

Well-Known Member

You don`t want to listen to anything I say.

@!#?@!

Similar threads

Popular threads in this forum