Hacking WIP [Trinket] [Rebug] [Others] SWITCHBOOT_UF2 / FUSEE_UF2 modchip software

[mattytrog]

sorry but you disunderstood me

In the first topic is written it is save to use SWITCHBOOT with both straps for saving fuses but there are ways to boot to stock without pressing reset on the modchip(simply select reboot normal in hekate).
For me i wanted a save way to get 100% sure to not boot to stock by mistake and burn fuses and that would be maybe AutoRCM.
But for me the disadvantages of AutoRCM in combination with Switchboot + both straps are not clear at the moment.
so what i know (i hope its right)
1. i can not boot to stock without deleting AutoRCM
2. battery drain will be no problem since the usb disconnect cable and the autohosoff=1 option in hekate
3. emmc manipulation could be detected by big N but since its offline it does not matter
4. if my switch gets corrupted and wont boot, its still possible to boot to hekate and restore nand backup
are there any disadvantages i don't know ?

Is there a possibility to remove the reboot(normal) menu entry in hekate or by a option in the ini ?

The reboot normal option still bypasses fuse check. Thus doesn't burn fuses. If you have the joycon and volume version of SWITCHBOOT which you have, it is impossible to burn fuses. The only way you could possibly burn fuses is by holding modchip reset while pressing power on.

 

[Dougiejones]

Hi Dougie!
The dotstar brightness is after the 3rd flash (think it is green on dotstar boards). When you let go of vol during THIRD flash, options will "blink out". You want the FIRST blink. Press vol+ during first blink.

OMG my star is shining finally

The trick happens at about 9 seconds into the flowchart at the third rapid white blink (reset payload and mode status).

At this stage release immediately the Vol+ then wait for the first red + green blink.
Quickly press Vol+ and relase. The white Led starts shining. Choose your Led intensity with quick Vol+ press. Done.
@mattytrog you saved my eyes lol

 

[szczetyk]

to delete

 

[Dougiejones]

Please could someone make a test for me ? THX in advance
I mean a very simple test. Not any soldering required lol
No matter on any config you are as long as you flashed simple_UF2.
It has to deal with the latest Hekate 4.8 and i don't want to spam the topic. That's why i'm looking a test feedback.
Someone ?

As nobody showed up... @mattytrog in your Hekate's 4.8 mod saving settings doesn't work beyond reboot...at least text brightness changes.
I'm posting here because it has to deal with UF2 as i tested this mod injected as payload into the Switch of a friend whom got SX Pro and it works.

 

[mattytrog]

As nobody showed up... @mattytrog in your Hekate's 4.8 mod saving settings doesn't work beyond reboot...at least text brightness changes.
I'm posting here because it has to deal with UF2 as i tested this mod injected as payload into the Switch of a friend whom got SX Pro and it works.

Ok Dougie.

What doesn't save? Can you give me example?

 

[Dougiejones]

What doesn't save? Can you give me example?

THX dude to take of your time. For instance Options\Backlight. Changes are immediately stored and effective but after reboot not.
Quick backup and normal backup work. Modchip infos too.

Going forward : testing Trinket test_boot_text_disabled trying to enable\disable....

EDITED : Trinket test_boot_text_disabled/enabled flashed and tested. It works flawlessly.
Notice that on boot text disabled the Vol -pressed function still remains

 

[mattytrog]

THX dude to take of your time. For instance Options\Backlight. Changes are immediately stored and effective but after reboot not.
Quick backup and normal backup work. Modchip infos too.

Going forward : testing Trinket test_boot_text_disabled trying to enable\disable....

EDITED : Trinket test_boot_text_disabled/enabled flashed and tested. It works flawlessly.
Notice that on boot text disabled the Vol -pressed function still remains

Yep thats the idea! The vol+ function still there, its just silenced from view.

After reboot not saving... Hmmm... That is a Hekate problem. I`ll take a look this afternoon.

 

[josete2k]

As I metioned last day, I can't boot the switch with efuses mismatching...

I downgraded from 7.0.1 to 6.1.0 and hekate can't boot 6.1.0 from its menu even SXOS can do it. I'd swear that 4.6 could boot firmwares with efuses mismatch... isn't it?

I have no SD inserted when launching hekate from modchip's memory.

 

[mattytrog]

As I metioned last day, I can't boot the switch with efuses mismatching...

I downgraded from 7.0.1 to 6.1.0 and hekate can't boot 6.1.0 from its menu even SXOS can do it. I'd swear that 4.6 could boot firmwares with efuses mismatch... isn't it?

I have no SD inserted when launching hekate from modchip's memory.

Just tested here.

Upgraded bench unit to 7.0.1, 9 fuses burnt...

rawnand restore back to 6.2.0... Boots without a problem.

Is SXOS using emunand? if so, that is how it can boot.

 

[FunThomas]

I have a problem with a state that my switch reaches and i dont know what it is...

I had a switch 3.0 with trinket when i selected in hekate to reboot normal it rebooted to stock fw.
i updated to 3.01 with ChoiDujourNX and AutoRCM enabled. When i now select in hekate to reboot normal it hangs with a black screen and i need to hold power 12 sec to shut it down to be able to turn it on again.
I disabled AutoRCM in hekate and the state is the same and in this state it's not in RCM mode and from PC i can not send any payload.
In this hanging state the modchip reacts to vol+ button and turns on short press first blue light and then green.

Is this the state when i have unburned fuses and horizon os stock hangs because of unburned fuses and don't run in any shutdown and stays in this state forever?

 

[Dougiejones]

Is this the state when i have unburned fuses and horizon os stock hangs because of unburned fuses and don't run in any shutdown and stays in this state forever?

No on the contrary. If your efuses count is lower than the recommended OFW Version AND you boot onto OFW without AutoRCM it will boot onto Horizon but they will burned and you simply just can't downgrade to any previous state.

The opposite situation (seems to me your case) if your efuse's count is too high regarding your OFW Version then blackscreen...Simply because the original bootloader catch the mismatch and don't allow to boot further.

Plz correct me if i'm wrong

 

[FunThomas]

Now something burned my 4th. fuse and i have now 4 fuses burnt and now it reboots again to stock and i can not reach the state before

but i was never in full stock horizon home screen and i never pressed reset on the mod chip

 

[Dougiejones]

Now something burned my 4th. fuse and i have now 4 fuses burnt and now it reboots again to stock and i can not reach the state before

but i was never in full stock horizon home screen and i never pressed reset on the mod chip

Something ? What is something ? What have you done ? Seems to be a lack of informations here...
What's your setup ? Is it Legacy Method ? Method 3 ? Which straps are soldered ? Which Simple_UF2 version did you flash ?
Emunand ?

I will try to help. Cheers

 

[FunThomas]

i am using trinket and switchboot for both straps (all straps connected)
What is something ?
I did only tried the reboot to normal in hekate and got the black screen as described above. Made the hard shutdown (12 sec) since normal shutdown did not work. And powered on again.
And i tried this procedure more times.

And as i saw your message regarding the fuse count i was looking in hekate and saw now it were 4 fuses burned and i tried again the reboot to normal and now it worked.

Now with the 4 fuses burned i turned AutoRCM on in hekate and the reboot to normal stucks again at the same point but if i disable AutoRCM it works to reboot to normal.

But with this experience i am not sure if it is safe to don't use AutoRCM to save fuses and use only the modchip with both straps with switchboot.

i don't know what led me or the switch to burn fuses if that should not be possible in this configuration.

 

[mattytrog]

Now something burned my 4th. fuse and i have now 4 fuses burnt and now it reboots again to stock and i can not reach the state before

but i was never in full stock horizon home screen and i never pressed reset on the mod chip

Hmmm... Very strange. Fuses should NOT burn. The only possible way those fuses could have burned (if its one that I fitted) is if the reset button was pressed or caught.

Where did you get your 3.0.1 firmware from?

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

I`m thinking its the "reboot normal" that has done something. Looking into this as we speak.

 

[Dougiejones]

I did only tried the reboot to normal in hekate and got the black screen as described above. Made the hard shutdown (12 sec) since normal shutdown did not work. And powered on again.
And i tried this procedure more times.

Yep and for me it's the same. This option's chose it Reboots into RCM. As Simple_UF2 includes Hekate's prevent efuses burning...
Wrong sorry. By mi side if i choose " Reboot to Nomal " from Hekate 4.8 it reboots to stock FW

Now with the 4 fuses burned i turned AutoRCM on in hekate and the reboot to normal stucks again at the same point but if i disable AutoRCM it works to reboot to normal.

I'm gonna to take a look at my Hekate's AutoRCM option state.

EDITED : " Tools\AutoRCM\Status : Disabled! "

 

[mattytrog]

Yep. Reboot normal burnt the fuse. Maybe.

Investigations ongoing.

 

[FunThomas]

Where did you get your 3.0.1 firmware from?

i got it from Darthsternie's webpage and after flashing it, only 3 fuses were burned so no one was burned after updating and it was checked and ok in ChoiDujourNX.

when i have AutoRCM now on and reboot to normal in hekate i get into rcm and i can connect from my pc and see it is in rcm mode

in the old state after updating to 3.01 and not burned any new fuses i was in a state that looked the same (display off and short press shutdown not working) but i could not connect from pc -> so it was not rcm.

 

[mattytrog]

ok... if you disable autorcm, do you still boot to hekate?

 

[FunThomas]

ok... if you disable autorcm, do you still boot to hekate?

if i disable AutoRCM then i boot normal to horizon os with fuse count fitting to fw version 4 fuses for 3.01 FW