Wii Softmod Guide
Earlie Schwoyer
Homebrew can be run for free on all Nintendo DSi consoles, regardless of firmware version or region. All you need is an entry point and an SD card to store your homebrew. The main entry point used in this guide is called Memory Pit, but there are other entry points you can use if Memory Pit is unusable.
This guide is a start to finish how to softmod a xbox (upgrade a softmodeded hdd too) and also how to TSOP flash any xbox (excluding mb v1.6) including flashing winbond & sharp tsop chips. All the files needed are included in the video description. I DIDNT MAKE ANY OF THE TOOLS FULL CREDITS GO TO THE DEVS, I just collected them all in one place.
Right now, your best alternative is to follow switch.hacks.guide. This guide will walk you through rolling your own Switch CFW setup, including obtaining all files from their original sources. This is the best option to learn about what you are installing on your Switch, the guide is excellent, and the folks at Nintendo Homebrew have a great team of helpers if you get stuck.
Please note that while code and content for SDSetup, homebrew.guide, and PegaScape are released under permissive licenses, logos and graphical assets are copyrighted. If you want to host a public replacement, just change the names and you are good to go!
The NVIDIA Quadro family of professional graphics cards are very, very expensive. They are generally 2-5X more expensive than their gaming counterparts, the NVIDIA GeForce graphics cards. But everyone knows that Quadro and GeForce graphics cards are virtually identical in hardware.
It all revolves around the driver support for professional 3D applications like 3ds Max or Maya. Quadro drivers allow the Quadro to be used to accelerate the rendering operations of such professional 3D applications while GeForce drivers do not. This is the basis for the premium prices NVIDIA (and ATI) charge for their professional-grade graphics cards.
Obviously, you cannot just use Quadro drivers with your GeForce graphics cards. After all, it represents the thin red line between a really, really fat profit margin and just a "normal" profit margin. NVIDIA Quadro drivers are designed to detect the presence of an NVIDIA Quadro graphics card. It will not install if a GeForce card is detected instead.
However, there is an easy way to soft-mod (modify in software) a NVIDIA GeForce desktop graphics card into a NVIDIA Quadro professional graphics card. We will show you just how to do it in this guide.
Before we start, you need to understand that soft-modding your GeForce card into a Quadro will not improve your graphics card's gaming performance in any way. All it does is enable hardware acceleration of professional 3D applications like 3ds Max.
There have also been some reports that modded GeForce cards may suffer some drop in gaming performance. It is not unknown if this is a problem that affects all Quadro cards, or just modded GeForce cards. It is also not known if the reported problems are really due to the use of older drivers.
To summarize , unless you really need the Quadro's ability to accelerate the rendering process in a professional 3D application, you should not soft-mod your GeForce graphics card into a Quadro. Otherwise, read on!
If you like our work, you can help support out work by visiting our sponsors, participate in the Tech ARP Forums, or even donate to our fund. Any help you can render is greatly appreciated!
This guide will cover installing ARK-4 on the PSP and general usage to cover the basics of this newer custom firmware(CFW). It is a successor to PRO and ME with additional features and being actively updated. Some quality of life features are added such as a custom launcher, file explorer, and an impressive plugin management system.
These next steps will install ARK as a temporary custom firmware meaning if you turn off your PSP you will have to launch the ARK Loader application to regain CFW functionalities. You can complete this step for the temporary CFW to try things out if you are unsure before making it permanent.
Any PSP can now use the cIPL method of making ARK-4 permanent. This is a quick additional step so if your PSP turns off you still retain custom firmware. You also have the ability to restore the PSP if it soft bricks.
Additionally, ARK-4 can be installed to the flash to run without a memory card. This is a full flash installation. It is not needed to make ARK-4 permanent. It is not required so it is not covered in this guide.
Prepare to set aside a minimum of an hour to follow this guide. This is specifically for you to carefully read and understand each page for safe execution for the safety and longevity of your Switch console. Some required device backups can also take around ten to thirty minutes to create, depending on your Switch model and your microSD card specifications.
On the Switch in particular, you need CFW to run almost all available homebrew. Some first-gen ("V1") consoles can run homebrew for free, while all other ("patched") consoles require specialized hardware installation beforehand.
Custom operating systems (OSes) are alternative system software installations, like Android or Linux, that install alongside the default Switch OS. These are usually perfect for powerusers who want to extend the functionality of their console beyond that of a gaming console, transforming Nintendo Switch to a full-fledged hybrid tablet or desktop. These custom OSes run completely independent of the Switch OS, meaning that anything you do in a custom OS cannot be reported back to Nintendo. Custom operating systems are not "emulated"; they run natively on the Switch's Tegra X1 SoC.
This guide will give you the opportunity to set aside space on your microSD to install these custom OSes onto, if you desire. It is important to note that these installations are optional; you do not need to install any custom OS in order to complete this guide and install Atmosphre. However, it is better to decide sooner rather than later, as the installation process involves formatting your microSD card.
fusee-gelee is currently the most widespread software entrypoint of launching custom firmware. It utilizes a vulnerability in the bootROM of the first-generation Switch systems, allowing us to boot the console via any payload we choose, instead of only ones that Nvidia and Nintendo authorize. The result allows full baremetal control over your console, including system storage backups, recovery, custom firmwares, and custom operating systems.
Acknowledge that EVERY time you modify your system, there is always the potential for an UNRECOVERABLE brick. A brick is a damaged device that no longer functions; something that becomes as "useful as a brick". On the Switch, they're rare, but still a possibility -- so make sure you read the directions carefully before performing them, and follow them EXACTLY.
If you choose the emuMMC path introduced later in the guide, you will also need a microSD card that is at least 128 gigabytes. In this path, it'll be important to disable the Automatic Save Data Cloud function beforehand, as well as making sure the Switch is set as the primary console.
If you must use a smaller microSD card, you can choose to use the sysCFW path, after assuming the risks involved.
Additionally, on a V1 "unpatched" Switch, you will need a way to access the ReCovery Mode (this will be further explained in the "Entering RCM section"). While possible with household tools, you may want to shell money out for a "jig" that inserts into the Joy-Con rail to reliably enable RCM.
Custom firmware is not permanently installed and does not change anything on your console simply by running it. It will be entirely unloaded upon rebooting the console. However, CFW does allow you to make permanent changes to your console at your own will, so be responsible and cautious with the abilities enabled by CFW.
If something doesn't make sense while you follow the guide, please reach out and ask for clarification rather than fumble around on your own. If your English isn't the best, use a translator such as Google Translate to submit your questions, so we can help.
Note: We are not currently, historically, or will we ever be, associated with Anton Retro, sthetix, Ely M., or other derivative or YouTube/TikTok guide publishers, especially any that claim relation to us.
Q: What are the differences between "first-generation" ("V1") consoles and "patched" consoles when it comes to running homebrew?
A: Once you boot into Horizon, not much. The primary things to keep in mind is that only V1 consoles support Atmosphre's "Reboot to Payload" function, but modchips automatically load payloads during reboots on their own.
Q: What is Horizon?
A: Horizon is the name of the Switch's operating system. It is sometimes called "HorizonNX", because it is actually a derivative version of the Nintendo 3DS's operating system of the same name.
Q: Why is it called Atmosphre?
A: Atmosphre "runs on top of the Horizon" operating system. Each layer of Horizon's security is referenced via the atmosphere's different layers. For example, the EL1 "kernel" reimplementation is called mesosphre, while the EL3 "TrustZone" reimplementation is called exosphre.
Learn more about ARM Exception Levels here.
Q: What exactly is the "emuMMC path," and why is it recommended for the microSD card to be at least 128GB for this path?
A: The purpose of an emuMMC/emuNAND is to give you a safe place to use custom firmware functions without Nintendo catching sight. As it is an offline clone of your internal storage ran entirely from your microSD card, you will need to set allocate up to 64GB on your microSD card for it (depending on the size of your internal storage), plus a duplicate your of digital game data (emuMMC uses a separate Nintendo folder for game installs).
Q: Why do I need to set my console as primary before starting this guide?
A: The Switch will otherwise try to connect to Nintendo servers before starting apps, which can lead to unexpected delays and make emuMMCs completely unusable.