Misc Dangerous Syswipe in HATS pack

  • Thread starter Thread starter auggiethecat
  • Start date Start date
  • Views Views 1,975
  • Replies Replies 7
  • Likes Likes 2

auggiethecat

Member
Newcomer
Joined
Jul 15, 2024
Messages
17
Reaction score
14
Trophies
1
XP
170
Country
United States
tl;dr: There is a dangerous syswipe script that comes with HATS pack, so it may be on your system already and appear after updates. Check and see if you have TegraExplorer version 4.2.1. If you do, it's highly recommended that you remove the payload (sdmc:/payloads/TegraExplorer) along with the sdmc:/scripts folder, and replace it with the official release. Known issues with this modified syswipe include unsafe battery calibration values (overcharging the battery) on Switch Lite consoles, and stock/OFW failing to boot afterwards on all models.


Hey all! Recently, I've seen more and more cases of people using a modified version of TegraExplorer’s syswipe script. With some investigation, this script originates from this fork of TegraExplorer by sthetix, and it is in his pack without most users' or helpers' knowledge. Below are the major issues with this version:

1. Removes Critical System Save
When attempting to reset the console, there are some system saves that cannot be removed, or else the console won't boot for a variety of reasons. The original script preserves some saves. This fork does not preserve one of the most important saves: the DeviceSettings save 8000000000000053. This save includes battery calibration data. When it is removed, the system initializes it to values that are unsafe for Switch Lites, as it causes it to overcharge. At best, this will significantly decrease the lifespan of any battery put in the console. At worst, this is a fire hazard.

This fork also adds 80000000000000d1 (erpt) and 8000000000000047 (exFAT) to the list of preserved saves. The original syswipe script also used to preserve these as well, but this was intentionally changed in the same commit that added indexer save reconstruction. When asked why, the author stated:
"I’ve seen many times [SciresM] say that it was not the best idea to keep the erpt save…About the exfat, no real reason besides the fact that you don’t need to keep it". - JeffVi

2. Removes Indexer Save Reconstruction
In the the commit message that changed the syswipe, it's mentioned that it "Removed dangerous manual indexer rebuild logic that caused save corruption", but the developer and maintainer of TegraExplorer notes that it’s "not dangerous, just inaccurate". (For more information on this indexer save and why it needs to be reconstructed, read this writeup from the developer of Atmosphère, SciresM)
Due to the removal of the reconstruction, attempting to boot stock/OFW after performing the syswipe (like many guides instruct) will result in a black screen. This behavior has caused, and will continue to cause people to search for drastic recovery methods, many of which can be actively harmful and irrecoverable. Stock/OFW will boot normally after booting sysCFW, but this adds Atmosphère as an undocumented hard dependency on doing a syswipe.

3. Removes Error Handling
As a more minor point, this fork removes the check to see if it has actually removed the data in the user partition. If this fails with the original script, it will tell you "Dir deletion failed". This fork does not.
This can happen with resized user partitions and in a couple other cases and can be very relevant to recovering or resetting the console. Failing to properly remove the user directories can also be a sign that deeper recovery steps are needed.


The original syswipe script does not have these issues. The changes introduced provide no documented benefit while introducing documented risk. Whether you are a helper, or a user, it is strongly advised to verify that the original TegraExplorer is being used. If the version is reported as 4.2.1, it is likely this fork, and should be removed, along with the scripts it uniquely stores in the sdmc:/scripts directory, and replaced with the official release. If you instruct someone to perform a syswipe, or perform one yourself, please make sure that the official one is used and not this fork.
 
Last edited by auggiethecat,
This is also on a github gist for a more sharable link as well as better archival.
here
Your link here appears to be broken.

In regards to the battery system save being deleted, that reads from your description that it is an issue with the Lite only? Are there methods to resolve the wrong calibration on Lites?

I've done a syswipe on V1 switches and it may have been with this fork. Are there still concerns we should be aware of now if the wipe seems to have completed correctly?
 
Last edited by timidIntense,
Your link here appears to be broken.
Fixed! Didn't even notice, sorry about that.
In regards to the battery system save being deleted, that reads from your description that it is an issue with the Lite only? Are there methods to resolve the wrong calibration on Lites?
That is the main concern, yes. I am not sure about the impact on other console types, as this isn't my research; I'm just communicating it. Additionally, It was much before my time. Also, a good reminder that we don't know a lot about the switch, including all of the things the device settings save stores. This save could have important data that will cause problems eventually, just in a way that's not visible. If any one knows more about this save, feel free to contact me! I would love to learn more about it!
I've done a syswipe on V1 switches and it may have been with this fork. Are there still concerns we should be aware of now if the wipe seems to have completed correctly?
Yes, but I'm glad it did work at least. If you have a nand backup, or emummc/sysmmc that hasn't been wiped, it would be best to take the device settings save from that, and restore it to what was wiped. Additionally, you should probably delete the erpt save. (Also, I can help you more/provide more specifics).
Post automatically merged:

Grabbing my popcorn to watch the defenders roll into this thread.
I've actually been pleasantly surprised! I haven't seen too many people doing that when I posted it in other places.
 
Last edited by auggiethecat,
  • Like
Reactions: SuffahBish
Shittix is a known tard in this scene, ignore and carry on.
Grabbing my popcorn to watch the defenders roll into this thread.
How dare you insult teh great sthetix?!! do you know how much he has done for the switch community? he saved* my switch using his nand flasher tool (it can't go online anymore, but no matter) after some idiot gave me a dangerous tegra explorer script which deleted necessary system saves from my switch lite and caused it to burn my house down. he also cured my dog's cancer and rebuilt my house after the fire out of the kindness of his very large and veiny, throbbing heart!

what have you ever done for the switch community except whine on gbatemp? come back when you develop a softmod for the mariko and not a moment sooner you philistine!
 
  • Like
Reactions: SuffahBish
For an update, 4.2.2 was released recently. It does not fix any of the mentioned issues. Tegraexplorer-ext 4.2.2 (the new fork name), changes a bunch of cosmetic/menial things.

Nothing has changed with the syswipe script. It's the same as 4.2.1, but with a new branding, a new hat, and most saddening to me, a donation link.
The original developer commented:
Makes me sad
Same kind of toxicity that made me lose interest in developing for switch
It truly is sad that we have community made tools that have had hundreds, if not thousands of hours of research and development, and one guy swoops in, rebrands it for himself, and makes money off it, and lose developers partially because of it. Maybe someday that'll change.
 
  • Like
Reactions: SuffahBish

Site & Scene News

Popular threads in this forum