Hacking RELEASE [Trinket] [Rebug] [Others] [Modchip Software] *NEW* Fusee_Suite UF2 packages

[snoofly]

i use fusee uf2 to run hekate (renamed payload.bin) with config to autoboot into atmosphere (so power on -> atmosphere)
my other hekate options are for stock and sxos (vol - and power on)
no autorcm
not bothered about burning fuses as long as cfw and ofw all work on latest firm so not bothered about downgrading

 

[popy]

@mattytrog: thx a lot for your efforts on this.
Have found some time to try the new Fusee_Suite and it works really good.
Can interrupt the boot proccess, check info, restore license and browse for payload -> nice.
Also the battery level and SD status is present.

And here is my noob question (maybe i am also do something wrong :-) ):
Is it normal when i plug the charge and the consol is off i do not get the charging and SD info symbol's?
On your picture when you have docked the console ill see those symbol's on your switch.

PS.: dont using the dock to charge -> i am charging with different USB-C charges placed in my house.

thx
pOpY

 

[mattytrog]

@mattytrog: thx a lot for your efforts on this.
Have found some time to try the new Fusee_Suite and it works really good.
Can interrupt the boot proccess, check info, restore license and browse for payload -> nice.
Also the battery level and SD status is present.

And here is my noob question (maybe i am also do something wrong :-) ):
Is it normal when i plug the charge and the consol is off i do not get the charging and SD info symbol's?
On your picture when you have docked the console ill see those symbol's on your switch.

PS.: dont using the dock to charge -> i am charging with different USB-C charges placed in my house.

thx
pOpY

Yep. That is the only downside of using a chip in autorcm mode.

This is why we have the usb strap to send the payload as soon as it is unplugged.

The dock can be used and the graphics appear, as the dock doesn't hijack the usb port until after payload injection.

So if using autorcm, if you plug into charge while off, screen will stay black as you are in rcm. The console is still charging though.

As soon as usb is free (when you unplug), the chip senses this and pushes the payload.

 

[popy]

Yep. That is the only downside of using a chip in autorcm mode.

This is why we have the usb strap to send the payload as soon as it is unplugged.

The dock can be used and the graphics appear, as the dock doesn't hijack the usb port until after payload injection.

So if using autorcm, if you plug into charge while off, screen will stay black as you are in rcm. The console is still charging though.

As soon as usb is free (when you unplug), the chip senses this and pushes the payload.

Thx a lot for your detailed answer.
Now it's clear to me, and I will stay on Fusee_Suite.

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

 

[hippy dave]

Baked Nintendo logo in. Shows on first boot. Good or bad idea? Adds a second to boot time...

Just hope you don't go to prison for including copyrighted data

 

[mattytrog]

Just hope you don't go to prison for including copyrighted data

I'll take plenty of lube. Perry Road has plenty of vacancies I hear

 

[hippy dave]

I'll take plenty of lube. Perry Road has plenty of vacancies I hear

Almost every time we drive past that prison, my lady tells me about how it has a pedo wing that overlooks the school playground. Urg.

 

[mattytrog]

I hand drew the Nintendo asset.

The sxos, I'll say it was blawars and I know nothing about it your honour

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

Almost every time we drive past that prison, my lady tells me about how it has a pedo wing that overlooks the school playground. Urg.

Yep. And in other news, Nottingham City Council has employed great white sharks to maintain order in the city swimming pools.

Next week... They are doing shooting lessons in Radford and Hyson green...

 

[metaljay]

@mattytrog curious, now that the chip remains powered all the time the console is on, have you noticed any extended power consumption?
Previously I remember it injecting payload and then turning off, but as your now listening for vol+ all the time it must drawer power

 

[mattytrog]

@mattytrog curious, now that the chip remains powered all the time the console is on, have you noticed any extended power consumption?
Previously I remember it injecting payload and then turning off, but as your now listening for vol+ all the time it must drawer power

Nope. The chip is still in deep sleep No extra power draw at all.

It has always been in "deep sleep". Drawing basically nothing. Even pressing VOL+ (which makes the LED light) doesn`t wake it up - unless you choose an option ofcourse.

One clock is running on the SAMD. Thats all. That senses sleep, successful push, vol press... Thats it. Everything else is dead as a dildo.

With my new meter (an Amprobe), I cannot even measure current draw, since it is too low.

Its a common misconception that the chip powers off. It cannot do that and has never been able to do that. It has always kept one clock running. If you are into your armored-dildo code, take a look under "sleep". Deep sleep is activated which IS off. Nothing can wake it. Only a full power cycle. So, prior to that, we tell it to kill all clocks apart from 1.

But I`d class that as "off".

The only physical way to COMPLETELY kill the chip is to have a on-off switch. No. Messy, trampy solution.

You will notice absolutely ZERO increase in current draw as it hasn`t increased since we started this shit 18 months ago.

 

[popy]

@mattytrog: thx again for new Fusee_Suite, really enjoying it.
Any chance to get your modded hekate from SwitchBoot?
I miss a few features like Backup/Restore, Fuse Count with corresponding min. FW version, ...

thx a lot

 

[mattytrog]

@mattytrog: thx again for new Fusee_Suite, really enjoying it.
Any chance to get your modded hekate from SwitchBoot?
I miss a few features like Backup/Restore, Fuse Count with corresponding min. FW version, ...

thx a lot

I`m purposely not putting features like that into Fusee_Suite.


Regarding Fusee_Suite:
The aim of Fusee_Suite is to act as a prebootloader, prior to loading Hekate / Switchboot / SXOS.
It is made to be completely immune to any updates. Should we REALLY be updating the SAMD every time a new FW comes out?


Regarding Switchboot:
I removed certain features and replaced other features to make it more modular for faster updates. Now Fusee_Suite is at this stage, Switchboot will be a bin file only.
I was also feeling brave and submitted a PR for some of my features. I don`t really know github etiquette, but my PR went down like a lead balloon. Too many changes apparently, which I fully understand.


A new (and final... maybe) version is coming. As usual, no need to update if you don`t need to.

But Fusee_Suite UF2 is gaining some of Switchboots features:

• Rename any file to "payload.bin, or payload<x>.bin, or bootloader/update(the three that Fusee looks for). So if you wanted your SXOS "payload.bin" out of the way, you can select to rename it to update.bin and put it in "bootloader" folder out of the way.
  
• Launch built-in SAMD21 update mode (requires an SD card) - you can also just use the VOL+ button to force chip into update mode. No SD required.
• Launch my Memloader mod (Tidy_Memloader - just the same as normal memloader, but it is moved into a folder keeping SD root tidy)
• Safe backup / restore of BOOT0/1/PRODINFO for Sysnand. Hekate / Switchboot deals with other backups, so not duplicating it.
• OEM style Nintendo graphic that comes up straight away and displays while batt status etc is worked out. (Just hold down PWR to pause boot and enter the prebootloader)

Fusee_Suite already has these features:

• Flat battery bootloop management - if using SXOS, or Hekate with a autoboot option with autoRCM, you will know the score with bootloops - this will help IMMENSELY. Displays OEM style battery icon until sufficient charge to prevent bootloop (set at 5%)
  
• Straps found are displayed (hold down vol-).
• payload1.bin can be changed to payload2.bin, payload3.bin etc etc by pressing vol+ as usual
• Select between perma-boot and dual-boot from vol+

Remember, the aim of Fusee-Suite is to go on your chip and forget it exists. For example, if you put your Switch away for a year, come back to it in a years time, you will STILL be able to boot latest Atmosphere / SXOS without issue. We all update our files from within CFW itself, don`t we?

 

[popy]

I`m purposely not putting features like that into Fusee_Suite.


Regarding Fusee_Suite:
The aim of Fusee_Suite is to act as a prebootloader, prior to loading Hekate / Switchboot / SXOS.
It is made to be completely immune to any updates. Should we REALLY be updating the SAMD every time a new FW comes out?


Regarding Switchboot:
I removed certain features and replaced other features to make it more modular for faster updates. Now Fusee_Suite is at this stage, Switchboot will be a bin file only.
I was also feeling brave and submitted a PR for some of my features. I don`t really know github etiquette, but my PR went down like a lead balloon. Too many changes apparently, which I fully understand.


A new (and final... maybe) version is coming. As usual, no need to update if you don`t need to.

But Fusee_Suite UF2 is gaining some of Switchboots features:

• Rename any file to "payload.bin, or payload<x>.bin, or bootloader/update(the three that Fusee looks for). So if you wanted your SXOS "payload.bin" out of the way, you can select to rename it to update.bin and put it in "bootloader" folder out of the way.
  
• Launch built-in SAMD21 update mode (requires an SD card) - you can also just use the VOL+ button to force chip into update mode. No SD required.
• Launch my Memloader mod (Tidy_Memloader - just the same as normal memloader, but it is moved into a folder keeping SD root tidy)
• Safe backup / restore of BOOT0/1/PRODINFO for Sysnand. Hekate / Switchboot deals with other backups, so not duplicating it.
• OEM style Nintendo graphic that comes up straight away and displays while batt status etc is worked out. (Just hold down PWR to pause boot and enter the prebootloader)

Fusee_Suite already has these features:

• Flat battery bootloop management - if using SXOS, or Hekate with a autoboot option with autoRCM, you will know the score with bootloops - this will help IMMENSELY. Displays OEM style battery icon until sufficient charge to prevent bootloop (set at 5%)
  
• Straps found are displayed (hold down vol-).
• payload1.bin can be changed to payload2.bin, payload3.bin etc etc by pressing vol+ as usual
• Select between perma-boot and dual-boot from vol+

Remember, the aim of Fusee-Suite is to go on your chip and forget it exists. For example, if you put your Switch away for a year, come back to it in a years time, you will STILL be able to boot latest Atmosphere / SXOS without issue. We all update our files from within CFW itself, don`t we?

Thx for your detailed posts. Now I understand the aim of Fusee_Suite and totally agree with you.

Thx for your efforts

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

 

[mattytrog]

V4 in OP.

That should be IT for Fusee_suite.

Fingers crossed it gets bumped up occasionally or stickied maybe?

Shame for it to get buried.

Some decent changes in V4.

Thanks for a corking year on this site and making pissing around with this console jolly good fun.

Happy New Year!

Matty, Mrs Matty and Junior Matties

 

[Romain80200]

V4 installed.
All option are working good except it is still write v3_1219 in the info.

 

[mattytrog]

Oops. Forgot.

Will correct that in next couple of hours

 

[mattytrog]

V4 typo corrected.

 

[peteruk]

@Cyan This is pretty much the final suite now, is there any possibility we could have this as a sticky thread please ?

 

[mattytrog]

Great work! I need some noob advices as this is the first time I hack a switch (already checked and it's not patched). It's for a kid, so I need something simple to operate and was thinking to buy the RCMx86. I thought about using the dual boot mode, so to have the original untouched fw to be able to play original games online and the CFW on emunand with blocked access to Nintendo's servers. I can solder the Vol+ strap no problem. Now:
1.What configuration do you think is the best? I was thinking chipRCM + dual boot mode.
2. It would be nice to not burn the fuses when starting OFW, will this happen in dual boot mode using this firmware for the chip?
3. Is there any advantage in choosing autoRCM vs chipRCM? I read the switch has some trouble charging in autoRCM mode
4. If I chose PermaCFW, is there an option to launch the OFW from, say, Atmosphere, like from a menu or something?
Sorry for the long question and thank you for your patience

Sorry I missed your question there!

To answer your questions:

1. Personally, now we have working emuNAND and the fact that Fusee cannot be patched, there is no reason to save fuses(on OG switches).emuNAND will still be bootable.
2. In dual-boot mode, yes fuses will burn. They have to so you get a stock boot.
3. Chip RCM cannot be disabled by ANY Nintendo update. If it is active, it stays active regardless what you do to your Emmc. Thus, your Emmc isn`t touched. No bytes are corrupted or changed as in "soft" autoRCM.
4. Thats for the Atmosphere / Hekate / SXOS boys to sort out. Hekate ofcourse has the option to boot "stock", overriding your fuse count. Are Nintendo checking for this? No idea. I am not putting a "stock" boot option in this (other than dual-boot) as it requires constant updates due to new fuse counts/ different pkg1 versions etc etc. All we are doing here, is organising your payload, managing the battery.
5. When new versions come out, you don`t need a PC to update. Just use whichever online updater you are using... You can then go into Fusee-Suite and sort out your payload. Delete old ones / Set new ones etc etc...

 

[metaljay]

@mattytrog V4 working as expected, noticed that if go to browse, then go to any menu, that when pressing back it doesn't go back to the previous menu but rather that boot loader, is that intentional?
it also hides the text and just see the battery icon and SD status (rather than seeing info/browse), have to press blindly to get it to show text again (hope that makes sense?) both VERY minor, but for a noob its not the simplest for my snowflake generation haha

(PS, not a fan of the bootlogo, purely because I have a red Nintendo logo to tell me its in EmuMMC and seeing the black one confuses me that I'm booting into stock lol)