Cheers Mattytrog, I look forward to testing. I've also updated argon-nx mod, and posted the source code for it in the thread if you want to see what I've done. Obviously not a patch on your skills - but it does the job, and is faster than before as the touchsreen code has been modded to prevent a constant loop freezing the app + lots of other code changes.
Good man! I haven`t got the skills. I did have long ago but now just relying on bits and pieces of information I recover from this damaged hard drive that I call a "brain".
Will check your code out and it will be in v1.3.2 as a new option. Too late for v1.3.1 as I have 3 quarters done it
v1.3.1 up if anyone interested
Thanks for the update, I have a couple of points:
In the payloads folder,
fusee-primary.bin
atmosphere.bin
These are both atmosphere payloads - I just renamed fusee-primary.bin to atmosphere.bin to make it easier to identify icons/logos.
Also for memloader you need to add the ini files for it to the root of your sd card, unless this is your own modded version and you have them located elsewhere.
I'll test in a bit, probably tomorrow though - but thanks for posting.
In the payloads folder,
fusee-primary.bin
atmosphere.bin
These are both atmosphere payloads - I just renamed fusee-primary.bin to atmosphere.bin to make it easier to identify icons/logos.
Also for memloader you need to add the ini files for it to the root of your sd card, unless this is your own modded version and you have them located elsewhere.
I'll test in a bit, probably tomorrow though - but thanks for posting.
Don`t worry about any of that...
It will boot argon.bin and everything will be passed over to that.
If people have argon folder, then they are good. Argon can look for whatever it likes...
Switchboot is basically saying when you turn on...
"I`ve found Argon... Not running anything else, just argon"
Thanks for the awesome work mattytrog! Long time lurker, recently installed RCMx86 and loving it over the sx pro.
One issue I'm having is any form of usb transfer seems to fail. Tinfoil 1.55 and the older version. nxmtp also doesn't work, it seems to hang on all usb queries.
I'm using switchboot v1.3.1
I've connected usb, vol+ and joycon straps. Is there a way to temp disable usb strap via software to test if this is causing issue?
I've just found another issue, my right joycon isn't recognizing it's connected to the console, I've tried a couple and both with the same issues.
It makes the clicking switch noise when the joycons are locked though.
I've set it to auto boot to SX os and it works fine. When I don't have an SD card inserted it boots to 1.3.1 loader.
and when I boot to 1.3.1 it says all 3 straps are installed.
Any suggestions?
One issue I'm having is any form of usb transfer seems to fail. Tinfoil 1.55 and the older version. nxmtp also doesn't work, it seems to hang on all usb queries.
I'm using switchboot v1.3.1
I've connected usb, vol+ and joycon straps. Is there a way to temp disable usb strap via software to test if this is causing issue?
I've just found another issue, my right joycon isn't recognizing it's connected to the console, I've tried a couple and both with the same issues.
It makes the clicking switch noise when the joycons are locked though.
I've set it to auto boot to SX os and it works fine. When I don't have an SD card inserted it boots to 1.3.1 loader.
and when I boot to 1.3.1 it says all 3 straps are installed.
Any suggestions?
Last edited by madturbo123,
D
Deleted User
Guest
Use goldleaf 0.5 with zdiag drivers and goldtree
Joycon issue is def soldering - Happened to me and retouching points fixed issue
You're right about the joy con, got it sorted.
As for the usb issue, still the same problem even with zadig drivers, goldtree and using goldleaf on the switch.
To disable the USB strap, you can disconnect from USB and disable either by:
flashing UF2 and as soon as you have drag and dropped it,
or
disconnect from USB or hold vol+ for EXACTLY 18 seconds which will reset the chip. I say exactly 18 seconds, as the RCMX86 has no LED...
If it had LED, you would be able to just use the options on vol+.
So... Grab a stop watch...
press stopwatch start and vol+ at exactly the same time... Hold for 18 seconds and release.
If it does turn out to be the issue, I will disable the USB strap in RCMX86. It will be the USB / serial logic chip on the RCMX86 (that we never ever ever use) that is causing the problems
So the FW displayed for current fuse is v8.0.1. No other changes. If you have already updated, no need to change...
Do a diff and you will see only a 8.0.0 has been changed to 8.0.1.
So, no new version number, just a cosmetic change.
Last edited by mattytrog,
Yep.thanks a lot i wil try this new version,
hekate have update the version to 4.10.1
Just a fix for certain Sandisks. Will be merged in next update (probably tonight when we get back from swimming)
I've tried both ways of disabling the usb strap.
flashing UF2 & disconnect trick - This takes away my vol+ strap according to 1.3.1 menu
holding vol+ for 18 seconds does nothing for me.
So uh, at the risk of sounding extremely stupid considering I know absolutely nothing about this stuff...but, would it be possible to just use a file and have your code use that file to compile your version of the bootloader?
Lol gonna leave it anyways, but that sounded stupid after I read it so let me see if I can explain better
In the means to help with you or us having to update our modchips with every hekate update would it be possible to just create a bootloader process that uses...lets say SAMD/hekate.bin...to decrypt/utilize during its startup which then links your features through. That way, we would only have to FTP or whatever the updated and renamed hekate.bin to the switch.
I am not sure what exactly changes source/code wise with every hekate update and not sure if this is a viable/better idea, whether to complex, take up to much room on the chips memory or whatever but figured I would throw it out there anyways because if this would free up space space you could add more feature like building in memloader or something cool.
LET THE FLAMING BEGIN!!!
Lol gonna leave it anyways, but that sounded stupid after I read it so let me see if I can explain better
In the means to help with you or us having to update our modchips with every hekate update would it be possible to just create a bootloader process that uses...lets say SAMD/hekate.bin...to decrypt/utilize during its startup which then links your features through. That way, we would only have to FTP or whatever the updated and renamed hekate.bin to the switch.
I am not sure what exactly changes source/code wise with every hekate update and not sure if this is a viable/better idea, whether to complex, take up to much room on the chips memory or whatever but figured I would throw it out there anyways because if this would free up space space you could add more feature like building in memloader or something cool.
LET THE FLAMING BEGIN!!!
It doesnt take vol strap away. It is just unrecorded until you press it. Press it and it will update on next boot.
If it does nothing, then double-check soldering on RCMX86 chip. The chip should be disabled in code once it goes to sleep.
Thats all I can suggest.
If there are problems, it HAS to be the USB logic chip causing a conflict. This has happened before.
--------------------- MERGED ---------------------------
No flaming in this thread, mate!So uh, at the risk of sounding extremely stupid considering I know absolutely nothing about this stuff...but, would it be possible to just use a file and have your code use that file to compile your version of the bootloader?
Lol gonna leave it anyways, but that sounded stupid after I read it so let me see if I can explain better
In the means to help with you or us having to update our modchips with every hekate update would it be possible to just create a bootloader process that uses...lets say SAMD/hekate.bin...to decrypt/utilize during its startup which then links your features through. That way, we would only have to FTP or whatever the updated and renamed hekate.bin to the switch.
I am not sure what exactly changes source/code wise with every hekate update and not sure if this is a viable/better idea, whether to complex, take up to much room on the chips memory or whatever but figured I would throw it out there anyways because if this would free up space space you could add more feature like building in memloader or something cool.
LET THE FLAMING BEGIN!!!
The reason the chip firmware updates is because of the modchip info display. You cannot carry the information over from the chip to a bin file (unless you use maybe a txt file. I`ll look into it).
However, use the Fusee-UF2 and use what payload you like as an alternative.
Hi matty i love your work and i have a big problem i cant any more flashing the trinket m0 via usb C cable the pc doesnt recognize the switch but i can normal start the cfw and power off the switch .
Now i must every time resolder the trinket and must use the solder point usb on the trinket :/ was here a method for use my usb c cable for flashing the trinket ( uf2 files ) i was very happy when i can know the solder point for ?
Its after updating to 7.0.1 = no usb Flashing on trinket m0 with usb c cable allowed
Big greets
Kermit
i cant any more flashing the trinket m0 via usb C cable the pc doesnt recognize the switch but i can normal start the cfw and power off the switch .Now i must every time resolder the trinket and must use the solder point usb on the trinket :/ was here a method for use my usb c cable for flashing the trinket ( uf2 files ) i was very happy when i can know the solder point for ?
Its after updating to 7.0.1 = no usb Flashing on trinket m0 with usb c cable allowed
Big greets
Kermit
Have you try double press on the trinket button?Hi matty i love your work and i have a big problem
Now i must every time resolder the trinket and must use the solder point usb on the trinket :/ was here a method for use my usb c cable for flashing the trinket ( uf2 files ) i was very happy when i can know the solder point for ?
Its after updating to 7.0.1 = no usb Flashing on trinket m0 with usb c cable allowed
Big greets
Kermit
Yes i pressed 2x the button and than its blinkin 2x red lights , i see on switch charging logo on the corner with a X but i was push out the usb cable and reconnect it again = nothing happened it is so after updating to 7.0.1 before was working .
Is your trinket flashable without problem with the switch and usb C cable ?
greets
kermit
Is your trinket flashable without problem with the switch and usb C cable ?
greets
kermit
Similar threads
