hit tracker

Team-Xecuter Presents SX OS v2.5.3

Discussion in 'Underground Nintendo Scene' started by ub3r1337, Jan 2, 2018.

By ub3r1337 on Jan 2, 2018 at 4:06 PM
  1. 283
    53
    28
    ub3r1337

    ub3r1337 NFC-Bank Owner Staff Member Clean-Up Crew MaxConsole News Team

    Joined:
    Jul 2, 2015
    Home Page:
    http://www.nfc-bank.com
    TX is already starting to roll-out fixes for those that sadly updated to v7.0 :)
    [​IMG]

    Team-Xecuter has all hands on deck, after big 'N' throw them a tough one v7.0.0 was released recently, and as you must know by now, its STILL NOT RECOMMENDED TO UPDATE, but for those that didn't see the early warnings signs, or had their Switch consoles automatically updated somehow, there is now light at the end of the tunnel, its not there completely yet, but the hard-working developers at Xecuter today, made the first step towards helping out those that have updated their SysNAND to v7.0.0 :)
    That's all for today. Stay tuned!

    (As usual, please remember all of TX latest releases & apps, can be found on their SX Portal website)

    --< Team-Xecuter - Rocking the Switch in 2019 and beyond! >--



    (What follows below is the last few announcements from TX, click the 'Spoiler' to see the previous details in full.)

    We received plenty of feedback following our recent 2.5.1 beta release.

    So today, we're back with a small bug fix release. But more importantly, many of you have asked us why we're not releasing any STABLE versions of SX OS anymore. Those people can rejoice, SX OS v2.5.2 is an officially supported stable release! This means that both the stable and beta channels are fully in sync now; feature- and functionality-wise.

    This release addresses two small bugs:
    • Fixed issue with installing split XCI / NSP
      Some split content file sizes were causing issues for some people, this is no longer the case!
    • Fixed issue with deleting files after XCI / NSP installation
      Deleting the original XCI/NSP files after installation was introducing some crashes and side effects for certain users. We investigated this issue and are happy to let you know its now a thing of the past!
    That's it for today, people. Keep an eye out for our coming updates!
    Happy New Year, everybody!

    We hope you've all had a smooth transition into the year 2019. Your friends from Team-Xecuter would like to kick off the new year with a small update to SX OS.

    Lets waste no time and see what's new in 2.5.1:

    • LayeredFS compatibility fixes
      It appears we introduced a regression in "LayeredFS" support in 2.5.0. This affected certain game mods like fan translations. This has been tracked down and fixed!
    • Improved Internet Local Wireless Play
      Numerous stability fixes and improvements have been made to the Internet Local Wireless Play functionality.
    • Fixed false positive 'corrupted' message for installer
      The Switch software management menu has an option for verifying the integrity of installed titles. When using this functionality with titles that have been installed through our NSP installer you would always get a message saying the title data is corrupt. This was mostly a false positive as the installed titles worked fine.. but we've hunted down the root cause of this and fixed this cosmetic shortcoming for all new installs!
    • Add support for installing XCI
      You read it right, as of now you can also *install* titles that come in XCI format, just as you would be able to do for any content that comes in NSP format. This is useful for people who would like to access all of their games from the home menu screen instead of going through our menu. Of course you can still play XCI titles without installing as well!
    That's it for today. The year is still young. Hang in there to see what we are cooking up in our labs!
    Another day, another release!

    Your friends from Team Xecuter are back with a fresh release of your beloved SX OS. This new v2.5 beta release introduces two exciting new functionalities that you all have been requesting.

    Let's waste no time on chit-chat, and see what's new in this release:
    • Fixed sleepmode in case of fuse mismatch
      Sleep/standby mode would break when your emuNAND was on a different firmware version than your actual system NAND. This has been resolved now. So from now on you can run the latest and greatest firmware in emuNAND while at the same time keeping a lower firmware on your original system's NAND. Nifty!
    • Added initial support for "Internet Local Wireless Play"
      Many of you have been requesting for us to add support for "local wireless play" tunneling over the internet. We have integrated this functionality into SX OS for you. This currently requires you to use a bit of software, LAN-Play on a computer to facilitate the tunneling. This software can be downloaded from the LAN-Play website: www.LAN-PLAY.com. Check out their project, they are are doing an amazing job. To enable "Internet Local Wireless Play" simply head into the SX Menu and head over to the "options" page. There's a toggle for enabling and disabling this functionality at will now.
    That's all for today. This marks the half-way point of SX OS 2. This year has been amazing and we want to thank the loyal and ever growing TX Switch user community, you guys are the reason this is all possible!

    Our resident hard- and software wizards are hard at work at bringing you even more groundbreaking functionality and products. Keep an eye on us!
    Hot on the heels of our 2.4 beta release!

    We are happy to bring you a small update which fixes some outstanding bugs and introduces some new functionality.
    • Fixed payload menu freeze
      It was reported that since v2.4 the "payload" menu used for launching external payloads was freezing up. This has been fixed, you can now enjoy your external payloads again!
    • Fixed installer incompatibility with recent NSP files
      Some recent NSP content (like the Super Smash Bros update) wasn't installable using our NSP installer. All your recent NSP's will work now!
    • Firmware 4.1 booting again
      A small regression got introduced in SX OS v2.4 leaving users with a (emunand) firmware on 4.1 unable to boot. We wasted no time to figure out the root cause, and SX OS should now be compatible with every firmware version again!
    • White squares on split XCI files
      Some split XCI content was not showing the icons properly, instead rendering a white rectangle. This is a thing of the past now!
    • Add support for split NSP files
      We've had support for splitting XCI content for a while now. This is needed for bigger games for people who enjoy SX OS from a FAT32 formatted microSD card. NSP content is now also supported in a split format. The file extensions used should be in the format of: .ns0, .ns1, .ns2, etc.
    That's it for this small stopgap release. Keep an eye out for our coming updates!
    We are pleased to let you all know that SX OS v2.4 BETA is ready for release.

    First of all, sorry to keep you waiting longer than we initially anticipated. We have been working around the clock to bring you this new release. We want SX OS to be synonymous in your mind with constant quality. We are here to stay and we are here to keep supporting your purchase till end of life.

    Now, lets have a look at what v2.4 brings to the table:
    • Support for firmware 6.2.0
      Nintendo threw us a small curve-ball while we were in the middle of reworking some other parts of SX OS. That being said, SX OS is now fully compatible with the latest official firmware 6.2.0.
    • EmuNAND functionality reworked
      Our initial release of EmuNAND used a storage mechanism that wasn't what a lot of people were looking for. In our last release we decided to switch to using the microSD for EmuNAND storage, which in turn made some users that *did* like the old method of storing EmuNAND on the system NAND unhappy. We have reintroduced the support for EmuNAND-on-system-NAND as well as introduced a third storage method for your EmuNAND partition. You can now also opt to use a separate partition (as opposed to files in the regular (ex)FAT filesystem) as a storage backend for your EmuNAND. With three flavors of EmuNAND storage supported now, all of you can rejoice!
      To recap, you now have three way of settings up EmuNAND now:
      • EmuNAND on system NAND: repurpose part of your Switch internal storage for EmuNAND
      • EmuNAND on microSD as partition: repartitions your microSD card with a separate EmuNAND partition
      • EmuNAND on microSD as files: EmuNAND is stored on microSD as files instead of repartitioning
      WARNING: Setting up your EmuNAND as partition on your microSD card will format your microSD card. After setup nothing but the boot.dat and license.dat will remain.
    • Homebrew R button interfering with ingame L+R buttons fixed
      In the last release we introduced a method of invoking the homebrew launcher for any title by holding down the [R] button during application/game startup, this gives homebrew additional capabilities that it wouldn't normally have. However, this seems to have caused some interference with some games, this has been fixed.
    • Embedded Homebrew Menu
      Previously, you had to copy a `hbmenu.nro` file to your microSD card in order to use the homebrew launcher. This has been fully integrated into the SX OS boot.dat file now. Effectively this means all you need for setup is to copy our boot.dat file, simple!
    That's all we have for now, people. That doesn't mean we're done. Its not over until we have liberated every single console out there. A lot of our current attention is focused on bringing you a solution for these "unhackable" switches. That does not mean we're not improving SX OS as well. Keep those feature requests and bug reports coming!

    Enjoy the festivities this month, and don't forget to pick up a SX Pro / SX OS for your loved ones! :)
    Your favorite superheroes from Team Xecuter are back with another SX OS update.

    In v2.3 beta of SX OS we have some exciting new functionality that you, the community, has been requesting a lot. As you know, we value your feedback and support.. so your wishes are our command!

    Let's have a look at the changelog:
    • SD emuNAND support
      Since the introduction of our emuNAND feature we got a lot of comments about our initial decision to make the emuNAND data live on the actual system NAND. After lots of hard work we are happy to say we now have a workable solution for storing your emuNAND partition data on your microSD card. This has the upside of not using up any space on your Switch. In order to use the new microSD emuNAND system you will *not* have to format your microSD card. Simply enter the TX boot menu by holding Volume-+ while powering on your switch. Head into the options menu and select emuNAND on the left. Users of our existing emuNAND solution will see an option to migrate their existing emuNAND data. The migration process also cleans up the old emuNAND from the system NAND. Painless! We're interested in hearing your feedback about this exciting new functionality.
    • The 'Emutendo' folder
      In addition to the new microSD emuNAND system we also introduce the 'Emutendo' folder on your microSD card. As you've probably noticed, the Switch saves various data to a 'Nintendo' folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the 'Nintendo' folder to 'Emutendo'.
    • Added more directories to scan for content
      By popular demand we have added yet another list of subdirectories that will be scanned on your microSD card (or USB harddisk) for XCI/NSP/homebrew. The directories that have been added are:
      • – /sxos/updates
      • – /sxos/dlc
      • – /switch/updates
      • – /switch/dlc
    • Homebrew menu takeover of any title by holding R
      Homebrew is usually launched from either the TX menu or the Homebrew Launcher menu. Both of these applications run as an 'applet' on the Switch. Applets do not have access to all of the system's memory, and thus any homebrew apps or games launched from here are affected by this as well. The only way to allow full use of the system's memory was to build and install homebrew NSP files. But now we have added another way to give homebrew applications full memory access! You can now hold the (R) button while launching any regular title, and this will launch the Homebrew Launcher Menu. Any homebrew launched from here will run with the same capabilities as a regular Switch game/app. Enjoy!
    • Loading homebrew from USB
      More good news for homebrew lovers. You can now copy homebrew NRO files to your USB harddisk as well, and launch them directly from our SX OS menu.
    • Stability improvements
      Overall stability of many components has been improved. This includes LayeredFS and USB incompatibilities. We have also fixed a bug which would prevent people from launching more than 32 titles.
    • libusbfs update
      Last but not least a small update for developers. We've squashed a small bug in libusbfs pertaining the stat() function. If you had issues with this, grab an updated copy of libusbfs from our website!
    The year 2018 is entering its final months. That does not mean we're taking a break from working on our beloved SX OS though. And yes, also those new 'unhackable' consoles are high up on the agenda. Don't worry, we will deliver.

    Keep sending your feedback and ideas, they're very welcome.

    See you all in the next update!
    Today, we are back with another release of SX OS beta! This update addresses some of the excellent feedback we've had following our v2.2 beta release. We can't thank the community enough for continuously identifying small issues and notifying us about them. Keep the feedback coming!

    Now without further ado, lets have a look at the list of changes:
    • Support for *big* USB drives
      In our last announcement we bragged that you were able to enjoy TERABYTES of content, which was technically correct.. but in practice you were still limited to USB drives with a capacity up to 2TB. This is now a limitation of the past, as you are now able to use storage devices with a capacity of up to a PETABYTE!
    • Fix USB disk directory scanning
      Due to a small bug in 2.2 beta the subdirectories on your USB disk weren't being properly scanned for content. This has been fixed and you can now rely on the same subfolder structure as on your microSD card.
    • Fix USB ethernet and keyboard support
      The introduction of our USB disk support apparently broke support for existing USB peripherals that were supported by Nintendo's firmware. Fixed!
    • Add USB drive write support
      We have enabled write support for USB drives. In practice for SX OS this means that NSP files can now actually be deleted after installation. But this also serves a greater purpose.. keep reading!
    • Eject gamecard on USB eject
      When you disconnect a USB disk while in the main menu the (emulated) Game Card will actually be ejected now. A small detail, but a nice addition nonetheless.
    • Improved LayeredFS support
      LayeredFS suffered from incompatibilities with certain games, this has been addressed and fixed. If you find any more problem titles, let us know!
    • Add support for temporarily disabling LayeredFS by pressing X while launching game/application
      If you want to skip loading your LayeredFS patches you can now hold the X key while launching a game/application. The game/app will start normally without any patches applied.
    • Further improvements to overall system stability..
    .. and other minor adjustments to enhance the user experience. You know the drill! ;-)

    Last but not least, we have some cool news for homebrew devs. We are releasing a little library called `libusbfs` that allows your homebrew to interface with USB disks very easily. You can find the latest library code on our website in the downloads section! We are looking forward to popular homebrew apps adapting support for USB storage.

    That's all we have today. We get many questions daily about supporting "patched" switch consoles. We are working hard on a solution. Stay tuned, friends!
    How do you do, dear SX OS users?

    Today we are back once again with a much anticipated new feature as well as various improvements to existing functionality for SX OS. While this is still labelled as BETA we've had some good success with it internally, we're looking forward to your feedback.

    Lets jump into the list of changes!
    • Docked USB drive support!
    Yes. You read it right. You can now plug a USB mass storage device into your switch' dock and load XCI or install NSP content from there directly. No longer are you limited by the size of your microSD card when playing the switch from the comfort of your couch, but you can now enjoy TERABYTES of content by using external harddisks and such! The filesystem on the drive needs to be either FAT32 or exFAT, and the directories that are being scanned for content are equal to the ones you'd use on the microSD card.
    • Updates to the cheat system
      • More accurate progress indication during cheat search
        People were reporting "freezes" during cheat searches, often times these were just due to impatience and a suboptimal UI from our end. The progress bars are more honest and update more frequently now!
      • Cheat search for exact value requires no initial dump anymore
        For 'exact value' searches a big initial dump file on your microSD is not needed, and since this is often the way people start a cheat search we decided to streamline the cheat finder process a bit. You are now prompted with a question whether you want to start an exact value search or arbitrary value search, in case of the former the process will be much faster.
      • Automatically apply/disable cheats upon toggle
        The interface for "applying" the cheats was a bit counterintuitive, you now no longer have to press the plus (+) button in order to apply cheats. They are automatically applied/disabled once you toggle them. Disabling cheats now properly works as well, so there's no need for having a dummy cheat any more to work around that limitation.
      • Ability to add cheats using the UI
        Identifying memory locations for cheats using just the console is nice, but previously there was no way of adding an actual cheat-code for a location you found to the cheat code library. This has been addressed, and there is now an interface for doing this directly from our menu.
    • Show homebrew NSP icons in TX menu
      Some homebrew NSP titles were not displaying their icons properly. This has been investigated and fixed.
    • Fix error 2345-0021 when in docked mode opening TX menu
      People who play/cheat in docked mode will like this fix. The frequent crashes that happened when opening the TX menu in docked mode are now a thing of the past!
    That's it folks. Enjoy this BETA and let us know what you think. We have more tricks up our sleeves, more rabbits in our tophats. And we only have one gear: FORWARD.
    We received a lot of feedback after the release of SX OS v2.0.

    Today, we are back with *two* new versions of SX OS. Huh? Two new versions? Yes, you read that right.

    As of today, we will be distributing two versions of SX OS. One is the "stable" release which has been extensively stress-tested and the other is the optional "beta" version of SX OS which comes with new functionality that needs to go through a thorough acceptation phase before it will be rebranded as the current stable version.

    We got a lot of feedback from people who didn't like us bumping the version number of SX OS so often for small fixes, and they are right. 99% of our end-users should not be bothered with small (but important) fixes but would rather enjoy a properly vetted build of SX OS.

    With the introduction of the beta channel we hope to address this and introduce new exciting functionality sooner rather than later.

    — What's new in SX OS 2.0.1?
    • Stability improvements
    • Introduction of optional beta updates available through OTA updater
    — What's new in SX OS v2.1 BETA?

    SX OS v2.1 beta introduces our brand new cheat engine and cheat finder. Many people requested a way to cheat in games or aid in finding cheats for games, so it has been high up on the priority list for a while. We're curious to hear your feedback about this initial version of our game cheat addition to SX OS.

    As of now we don't have a big library of game cheats available yet, but we hope the community will come up with some cool ones that they will share publicly. Finding cheats and making (reliable) cheat codes for Switch games can be a laborious task and is in certain aspects a bit more involved than finding cheats for, say, a classic gameboy game!

    For that reason we have written a small reference guide [HERE] for the aspiring cheat hackers out there detailing the format of our cheat codes, caveats that need to be accounted for, and small tips to bring you up to speed.

    — Closing words

    Go update your SX OS to v2.0.1 now by downloading the latest version from our website or using the online updater in SX OS itself. If you're feeling adventurous, give the v2.1 beta a shot, which is also available to you through the online updater in SX OS.

    That's it for today. Enjoy!
    Hello friends! Team Xecuter is happy to bring you the official 2.0 release of your beloved SX OS.

    A lot has happened since the initial release of SX OS a few months ago. This is far from a simple proof of concept custom firmware anymore. With this major update we bring some exciting new functionality to the table. We suggest you grab a beverage of your choice and read on to learn more!
    • EmuNAND
    Lets start with the major new feature in 2.0: EmuNAND.

    Those who have a background in the Nintendo 3DS hacking scene know what this is, but let's quickly elaborate for those of you who are new to the game:

    The Switch uses a NAND Flash storage chip to store all of the system software, as well as your save games and other assets. With EmuNAND we create a shadow copy of this storage from which you can run SX OS. The benefits from doing this are that you keep your SX OS "world" separated from your original firmware. This also means you can keep your switch on an older firmware, while running the latest and greatest firmware inside of your EmuNAND. As we all know, older is better.. when it comes to defeating system security at least. And newer is better when it comes to enjoying the latest content! :)

    Another upside of consolidating your SX OS usage from your original firmware usage is vastly reducing the risk of a network ban. You can run SX OS in EmuNAND, of course with our Stealth Mode enabled, and anything that is littered on the EmuNAND's filesystem is not visible to the switch in Original Firmware mode.

    One thing to note is that SX OS EmuNAND works a bit differently compared to what some of you might think of as "traditional" EmuNAND where the entire NAND is copied to a separate partition on the MicroSD card. With SX OS EmuNAND your EmuNAND partition lives inside of your regular NAND. The primary reason for this is that occupying 32GB of a MicroSD card is a bit wasteful. The secondary reason is by utilizing the existing flash storage we can guarantee performance and reliability.

    You can set up EmuNAND by booting into the SX OS boot menu (hold Volume + during boot) and going into the revamped "Options" menu. There you will find a section called EmuNAND which will guide you through the setup. By default SX OS will allocate 15GB for your EmuNAND partition. If you want to use a different size hit the "advanced" button before creating your EmuNAND.

    SX OS will boot into EmuNAND by default if it finds a valid EmuNAND partition. If you don't want to boot into EmuNAND, there's a button in the SX OS Boot menu which will allow you to continue booting with EmuNAND disabled.
    • NAND Dumping, Restoring, GPT Repair
    As mentioned in the previous section we have revamped our SX OS boot menu's option screen quite a bit. For the tinkerers and advanced users we introduced an easy method of dumping/restoring your NAND flash storage. Another neat addition for people who had an unhappy accident while playing with their NAND is the "GPT Repair" option. This will repair your NAND's partition table if you ever need to. Again, this functionality is for advanced users who know what they're doing only. Please be cautious when using this functionality.
    • LayeredFS working on 6.0
    With our (early) support for 6.0 we introduced a regression where "LayeredFS" would no longer work. This has been corrected and you can now enjoy your game modifications/hacks again on the latest official firmware.
    • Homebrew NSP Compatibility
    We got word that the community has started distributing homebrew titles as NSP files recently. These NSP files cut some corners in the way they are crafted, but we decided to introduce support to make them usable with SX OS anyway. So you can now enjoy your favorite homebrew titles that comes as installable NSP files and launch them directly from the home screen!
    • Closing Words
    Whew, we're sorry for the wall of text. We tried to keep things as concise and easy to understand as possible. SX OS 2.0 is a big and important update, but certainly won't be the last. We know you're all waiting for even more functionality that is in high demand. Rest assured, we work as fast as we can to scrap these items off of the bucket list and bring them to you, the loyal end user, as fast as we can!

    Enough chit-chat, you can update to SX OS 2.0 right *now* by using the built-in updater if you are running SX OS 1.9 or higher. Otherwise head to our website and grab a copy! Enjoy!

    BTW, IF LOOKING FOR A XECUTER SX PRO/GEAR or SX OS, PLEASE CHECK OUT THESE OFFICIAL SPONSORS OF MAXCONSOLE:
    1. MOD3DSCARD --> https://www.mod3dscard.com/home/12-xecuter-sx-gear-mods-nintendo-switch.html
    2. 3DS-FLASHCARD --> https://3ds-flashcard.cc/home/77-xecuter-sx-pro-with-sx-os.html
    3. MODCHIPFRANCE --> https://modchip83.com/en/home/178-purchase-xecuter-sx-pro.html
    4. SWITCHSX.COM --> https://www.switchsx.com
    5. SHOP01MEDIA --> https://www.shop01media.com/index.php?route=product/product&product_id=2199?tracking=55d384d869281
    6. http://jeux-linker.com/accueil/35-switch-sx-xecuter.html (French reseller)
    7. http://stargate3ds.org/home/28-switch-sx-team-xecuter-modchip.html (UK reseller) / (French reseller)
    OR CHECK OUT THE FULL LIST OF OFFICIAL RESELLERS ON TX's SITE: --> https://team-xecuter.com/where-to-buy/
     
    Last edited by a moderator: Jan 31, 2019
    Aburamelian, Leobgood, Jimyb3 and 2 others like this.

Comments

Discussion in 'Underground Nintendo Scene' started by ub3r1337, Jan 2, 2018.

  • Thread Status:
    Not open for further replies.
    1. 48
      0
      6
      Starjudy1990

      Starjudy1990 Loyal Member

      Joined:
      May 24, 2018
      Retailer selling XS OS without an account or address / Safe/Fast(or instant) delivery to get SX OS license?
       
    2. 1
      0
      1
      carlchina

      carlchina Loyal Member

      Joined:
      Nov 5, 2018
      Location:
      shanghai
      Update to SXOS 2.2.1, Third party typec to hdmi adapter Not available

      Switch crash and black screen
       

      Attached Files:

    3. 32
      5
      8
      KhenemetHeru

      KhenemetHeru Loyal Member

      Joined:
      Aug 12, 2013
      running SX OS 2.2.1 on switch 6.1; I had maybe 15 or so XCI games on my HDD, a 2tb WD My Passport, exfat/default cluster size, games loaded and ran fine. Added a few more, no problem. Added a bunch more, there's 63 XCIs on it now (all were copied one by one, so as to avoid any corruption like on SD card) - no NSPs on the drive anywhere. I click Album, it starts scanning the games, and boom, crashes to that 2168-0002 error. Is there a limit to the number of XCIs the menu can scan?
       
    4. 31
      2
      8
      True-Blue

      True-Blue Loyal Member

      Joined:
      Jan 16, 2012
      No . I have 415 real xci files and it scans for me . Takes about 45 seconds
       
    5. 21
      2
      3
      a7mag3ddon

      a7mag3ddon Loyal Member

      Joined:
      Mar 4, 2017
      Might i make a slight suggestion if it hasnt already been, can TX use a file on the switch to store the games list on HDD instead of scanning the drive everytime? then maybe have a PUSH A to update Database option? would be much quicker and cleaner.
       
    6. 81
      9
      8
      ISOHaven

      ISOHaven Loyal Member

      Joined:
      Apr 21, 2005
      Home Page:
      http://
    7. 213
      44
      28
      LupinIII

      LupinIII Developer

      Joined:
      Aug 21, 2005
      Well, that's a nice addition.

      What I'd really like to see now are some extra features for the installer. Tinfoil has the ability to bypass artificial system update requirements when installing an update, for example. And the much maligned "n1dus" has the ability to install an XCI directly (however it tends to choke on XCIs with merged updates and DLC). Obviously, in combination with apps like NSC Builder that can convert NSPs to XCIs (and vice versa) and also repack existing XCIs (and NSPs) with updates and DLCs, having the flexibility to mount OR install XCIs will easily make them the format of choice going forward.

      Of course, if TX wants to completely end the asinine debate about which NCA container format is better, they could also add the option to MOUNT NSPs. Then there's no more need to worry about formats at all. Just take whatever comes out first and use it as is. Then you would only need to run a converter if you're doing USB mounting. Which I definitely will be at some point, because that's what modern soft modding is all about. Having your complete collection available at boot, and being able to pick and load any game at the drop of a hat. And there's just no microSD card big enough for that.

      Though I'm not sure putting NSP on equal footing as XCI is in TX's best interest. But the closed-minded arguments from those poor kids who can't afford SX OS sure get old fast. Saying things like "XCI is a pay format" or that it's "only for piracy" for two of the lamest I've heard recently (if you think that's funny, the person who said these things actually considers themself an objectivist, ROFL). No, .XCI is an open standard, just like .NSP is, and just happens to be the native format of dumped carts, much like .NSP just happens to be the native format of eShop content. As for the "only for piracy" nonsense, well, it's not like the official devkit's documentation declares anywhere in it that the "official" format for homebrew projects is NSP or anything (maybe that's because it's a CLOSED SYSTEM that homebrew isn't officially even allowed on in the first place). Retroarch works JUST FINE as an XCI, I might add. Anyway, hopefully TX and Vertigo can put an end to this nonsense once and for all by adding support for installing XCI files. Maybe they could even collaborate with each other (unlikely I guess, but stranger things have happened, last week's elections being a perfect example -- fyi, being someone that actually has a pre-existing condition, I'm going to take it extremely personally when they don't deliver).
       
      Last edited: Nov 15, 2018
    8. 111
      19
      18
      rory2005

      rory2005 Staff Member Clean-Up Crew

      Joined:
      Jan 24, 2012
      GaryOPA likes this.
    9. 81
      9
      8
      ISOHaven

      ISOHaven Loyal Member

      Joined:
      Apr 21, 2005
      Home Page:
      http://
      What's up with SX OS? Last stable release is pretty old now.
       
    10. 25,596
      2,240
      113
      GaryOPA

      GaryOPA Master Phoenix Admin Staff Member Top-Dog Brass

      Joined:
      Mar 18, 2006
      Media:
      1,371
      Occupation:
      Design Eng.
      Location:
      Tropical Island
      Home Page:
      http://www.O-P-A.biz
      first post updated with v2.3 news
       
    11. 1
      0
      1
      ccwork888

      ccwork888 Loyal Member

      Joined:
      Nov 18, 2018
      Location:
      SX OS
      i am switching back to 2.2.1 beta. please give the option to install emunand to system memory or microsd. i prefer emulate on system memory.
       
    12. 48
      0
      6
      Starjudy1990

      Starjudy1990 Loyal Member

      Joined:
      May 24, 2018
      wow, nice news, SX OS License is easily my best purchase for the switch.
       
    13. 25,596
      2,240
      113
      GaryOPA

      GaryOPA Master Phoenix Admin Staff Member Top-Dog Brass

      Joined:
      Mar 18, 2006
      Media:
      1,371
      Occupation:
      Design Eng.
      Location:
      Tropical Island
      Home Page:
      http://www.O-P-A.biz
    14. 213
      44
      28
      LupinIII

      LupinIII Developer

      Joined:
      Aug 21, 2005
      OK, I'm enjoying the new homebrew option. I have an HB Menu Loader XCI, but this is much more convenient.

      The new EmuNAND implementation looks interesting. The one thing they failed to mention is how much space it takes, though. The old implementation let you pick a size in 5 GB increments IIRC, but, I just tried creating one on a card with 11 GB free and it said there was not enough space. So, does it eat a full 30 GB now? If so, that would be a hard sacrifice to make.

      Anyway, nice going, guys. You've outdone yourselves once again. Very impressive update.

      I'd still like to see the installer add an option to patch firmware requirements. Though they could improve upon the original by having it patch the meta data instead of using the current placeholder method. That would mean if the update is dumped later (speaking of which, an easy-to-use installed title dumper would be nice), it would still be patched. And, of course, the ability to install XCIs would provide an extra degree of flexibility. No need to convert your cart dumps if you decide you want to install them (I won't even consider doing that until Nintendo gives us folders, but I know I don't speak for everyone).

      Conversely, being able to mount base game NSPs in the loader would be convenient too. Though I'm not sure how easy that would be to implement.

      Also, as more games come out with LAN play (Diablo III makes for a very good case for it in and of itself), a LAN tunnel that runs entirely on the Switch and requires no PC app would be nice. Not that there's a lot of public wifi with UPNP enabled, but it would be more convenient when taking it to a friend's house.
       
    15. 213
      44
      28
      LupinIII

      LupinIII Developer

      Joined:
      Aug 21, 2005
      I just wanted to ask, does EmuNAND currently support exfat? I recently got around to trying it and, it gives me a black screen when I boot with EmuNAND enabled. And I'm not the only person this has happened to. Several others have reported the same. Now, if I disable EmuNAND from the boot menu, the system boots normally. So, it must be unable to read the NAND backup in the "sxos\emunand" folder or something.

      And again, cloning the user partition seems wasteful. I would keep the current implementation as a "full" option for those that want a "proper" implementation, but, some of us would like a "partial" option that does not clone the user partition, and simply uses the original. I mean, I guess you could install games or updates to the emulated user partition, but I'd rather just use the real one, and have more free space on my microSD card.

      This would avoid save issues as well, since they would all still be getting written to the real NAND. As it is, if you decide to delete your EmuNAND, and you forget to backup your saves with something like Checkpoint or Edizon, well, there goes all the progress you made while playing on EmuNAND. So, as far as I'm concerned, using the real NAND's user partition would be a much better and safer alternative.

      Also, an option to boot EmuNAND without patches might be helpful. If they can get 6.2 running in an EmuNAND, even without the usual patches, and have an option to create a clean EmuNAND, well, there you go. You could use EmuNAND on 6.2 for your legit games, and disable it for backup loading on 6.1 or lower. That would be an acceptable workaround for most people until a new exploit can be found. Of course, then they'd want to change the default boot option for EmuNAND to disabled instead of enabled. This could even be helpful to those trying to crack 6.2.
       
      Last edited: Nov 22, 2018
    16. 25,596
      2,240
      113
      GaryOPA

      GaryOPA Master Phoenix Admin Staff Member Top-Dog Brass

      Joined:
      Mar 18, 2006
      Media:
      1,371
      Occupation:
      Design Eng.
      Location:
      Tropical Island
      Home Page:
      http://www.O-P-A.biz
      If you having black screen issues, trying replacing the boot0 and boot1 files in emunand directory with ones from your nand backup, for some reason depending on how emunand was created these two files have the wrong flags set in them.

      Yes, having 'partial' would be nice. -- it has been requested to be put back in place for those not wishing to have full 32gb user space.

      And yes, right now having emunand on 6.1 is partial fix for those that updated to 6.2 on their sysnand, you can use emunand 6.1 as your sx os cfw, and sysnand as 6.2, but currently with sx os 2.3 beta, when you do that you need to remove autorcm and allow nintendo to burn your 8 fuses, and then doing so means sleep mode does not work when in emunand, and of course you need to use the jig to boot up each time into emunand.

      Hopefully in few days, we will see a better fixed emunand 6.1 solution for 6.2 sysnand, but it will be a while before you will see actual 6.2 cfw, nintendo did a good job this time around, in changing the bootchain and moving the device key generation.
       
    17. 213
      44
      28
      LupinIII

      LupinIII Developer

      Joined:
      Aug 21, 2005
      Ah, so, boot0 and boot1 backups from Hekate should fix it? OK. I'm planning to test it again soon, so, I'll try that next time. Thanks.

      Well, what I was actually suggesting was to turn that partial fix on it's ear and do the opposite of what you're suggesting. Let EmuNAND run in OFW mode (no CFW patches, just the fuse protection and NAND read/write redirection). If 6.2 will work from an EmuNAND, even if it has to be an "unpatched" EmuNAND, then we could instead keep the real NAND on 6.1. No burned fuses or sleep mode issues. Maybe it's not what TX had in mind when they created the feature. But it may be the better option at this point.

      And yes, I've seen the initial reports. Frankly, I never really felt like I needed EmuNAND before because I have zero interest in Nintendo's online service. I didn't need a "legit" NAND. Now if at some point I'm going to need one if I want to play any new games in the coming months, that's different. But I want to do it the right way. And updating my real NAND to 6.2 just like Nintendo wants me to doesn't look anything remotely like the right way to me. Everyone assumed that the best approach was going to be to keep the real NAND clean, and run CFW and backups on the emulated one. I get that, with conventional PC warez scene wisdom being to test in a VM or sandbox. But VMs can also work the other way around. If your host OS gets a virus and your Office VM doesn't, you've still saved yourself a considerable amount of time.

      Consider this. Which is easier and safer to restore to a clean state? The actual NAND, or the EmuNAND? Most of us that aren't already banned will need to generate a clean NAND somehow. Because pre-3.2 Hekate dumps cannot be trusted. But we didn't know that at the time. So, by the time we had reliable NAND dumping, most of us had already installed NSPs. So, many of us are going to need a solution to clean the "clean" NAND. It's probably safer and easier to try to do that via EmuNAND right?

      Besides, getting 6.2 running under a modified boot process at all would arguably be a good first step. It may even lead to an alternate way around TSEC being found. Maybe a "stealth" module could slip past the boot sequence undetected, and snag master key 6. I admit, I don't know enough about how the system works to know if that would work or not. Just putting the idea out there.

      EDIT: Well, looks like I won't be needing EmuNAND yet after all, though I still want to get it working in case I do some day (there's always next time). Also, it looks like I somewhat called it -- the solution WAS to trick TSEC into performing it's boot routine, and grab the keys afterward. "TSEC's key is only used at boot, so, do they even need to crack it at all?" was the first thought that ran through my head when I read that report from Scires. Though I have to admit, I got my question answered MUCH faster than I was expecting to.
       
      Last edited: Nov 24, 2018
      KhenemetHeru likes this.
    18. 1
      0
      1
      lisa-txswitch

      lisa-txswitch Loyal Member

      Joined:
      Nov 28, 2018
      Location:
      hongkong
    19. 65
      3
      8
      Jimyb3

      Jimyb3 Loyal Member

      Joined:
      Mar 29, 2018
      Can anyone explain me, why there are 3 different way to make Emunand? And which is the best way?
       
    20. 81
      9
      8
      ISOHaven

      ISOHaven Loyal Member

      Joined:
      Apr 21, 2005
      Home Page:
      http://
      It doesn't get any simpler than the release notes.

      1) EmuNAND on system NAND: repurpose part of your Switch internal storage for EmuNAND
      2) EmuNAND on microSD as partition: repartitions your microSD card with a separate EmuNAND partition
      3) EmuNAND on microSD as files: EmuNAND is stored on microSD as files instead of repartitioning

      IMO, #2 sounds like a major PITA and for me I would rather leave the switch alone so #1 is out as well. I'd rather the files just be on my memory stick. Simple. Many people cried about that because they can't afford a larger stick and they want their entire stolen collection on their stick....lame. Remove one game, done! Not a BFD.
       
      Last edited: Dec 13, 2018
      Jimyb3 likes this.
    Thread Status:
    Not open for further replies.

Share This Page