Tutorial  Updated

How to boot Linux on your Switch

THIS GUIDE IS DEPRECATED
THIS IS BETTER https://github.com/natinusala/painless-linux


I've successfully booted ArchLinux using ShofEL2. Here is a quick guide on how to do it - I'll assume you're computer literate and know how to use a terminal / Linux commands / git.
Everything is taken from the README of the ShofEL2 repo so if you want to go even faster, go read that instead.

Thanks to NightHammer1000 and Y2K-x for the help !

There is a simplified and faster version of this tutorial available here, with precompiled binaries so you don't have to build everything : https://github.com/SoulCipher/shofel2_linux

The result

Without a SD card ("waiting for root device mmcblk0p2") : https://photos.app.goo.gl/7y6ut5ObuHMUIMZg2
Stock Arch Linux : https://photos.app.goo.gl/yALqe3zMZRe2dSQf1
Arch Linux with LXDE : https://photos.app.goo.gl/xaEgRqeSi8jvAwpz5
RetroArch running : https://photos.app.goo.gl/vBLPo5wiBto1qiUH3
Arch Linux with GNOME : https://gbatemp.net/attachments/img_0005-jpg.121608/
Arch Linux with KDE : https://gbatemp.net/attachments/img_20180427_121605-jpg.121666/

What works / what doesn't
  • Desktop environment : Gnome, LXDE, KDE
  • Wi-Fi : works
    • You will need to reboot your Switch and run the exploit again to make the Wi-Fi work (it never works on the first boot)
    • Then enter the Network Manager Application and add your network from there
    • If it doesn't work, you will need to edit the configuration on the host computer (see the additional notes at the end of this post)
    • With LXDE : Can cause a kernel panic if used at the same time as Bluetooth
  • Bluetooth : works but Joy-Cons can't be paired
  • Touch screen : works, although LXDE is not very touch-friendly
  • Audio : doesn't work yet
  • GPU acceleration : works (via mesa), with OpenGL (and maybe Vulkan too ?)
  • Joy-Cons : not recognized
  • Volume buttons : working with Gnome but not doing anything since there is no audio device
  • Power button : doesn't do anything, no sleep mode, no graceful shutdown
  • USB : doesn't work
  • Dock : not tested yet, but I bet it doesn't do anything besides charging the battery
  • Power management / battery level : working with Gnome
What you'll need
  • A computer running Linux with a blue USB SuperSpeed port, or a Mac
    • A Linux VM can work in theory, but it depends on how the USB passthrough is implemented (apparently VMWare works, VirtualBox doesn't)
  • A USB A-to-C cable (with data support, obviously)
    • be careful as cheap cables were reported to work randomly / not work at all
  • Some time (you know, Linux is kinda large)

Prep work

First, you'll need to install the required toolchains. Open this link and download the tar.gz binaries for
  • aarch64-linux-gnu
  • arm-linux-gnueabi
Be careful to choose the right architecture for your PC (for me it was x86_64 so "gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabi.tar.xz").

Once you have them, extract them somewhere nice and add the "bin" (not "lib" as I previously stated) folder of both toolchains to your PATH ("$ export PATH=$PATH:/path/to/toolchain1/lib:/path/to/toolchain2/lib"). The building process won't work otherwise.

Then, install those dependencies (how to install them and their name might depend on your distribution) :
  • build-essential (sorry I didn't add it it was obvious to me)
  • libssl-dev
  • swig
  • bison
  • pkg-config
  • flex
  • zlib1g-dev
  • python3
  • python-dev
  • python3-pip
  • pyusb 1.0.0 : "$ sudo pip3 install pyusb==1.0.0"
  • libusb-1.0-0-dev

Compiling

Clone each required repository :

Code:
$ git clone https://github.com/fail0verflow/shofel2.git
$ git clone --recursive --depth=1 https://github.com/fail0verflow/switch-coreboot.git coreboot
$ git clone https://github.com/fail0verflow/switch-u-boot.git u-boot
$ git clone --depth=1 https://github.com/fail0verflow/switch-linux.git linux
$ git clone https://github.com/boundarydevices/imx_usb_loader.git

You can grab a coffee or two because Linux has more than 5 million files to download.

Then, build everything :

Code:
$ cd shofel2/exploit
$ make

Code:
$ cd u-boot
$ export CROSS_COMPILE=aarch64-linux-gnu-
$ make nintendo-switch_defconfig
$ make

Code:
$ cd coreboot
$ make nintendo_switch_defconfig
$ make iasl
$ make

If you have a tegra_mtc.bin file error, you'll have to extract it from a Pixel C stock image :
"$ ./build/util/cbfstool/cbfstool bootloader-dragon-google_smaug.7900.97.0.img extract -n fallback/tegra_mtc -f tegra_mtc.bin"

Or you can download it directly from here : https://0w0.st/tegra_mtc.bin (thanks to @CptPotato for uploading this)

You'll have to put it in the "coreboot/src/soc/nvidia/tegra210" directory.

Code:
$ cd imx_usb_loader
$ git reset --hard 0a322b01cacf03e3be727e3e4c3d46d69f2e343e
$ make

The big one :

Code:
$ cd linux
$ export ARCH=arm64
$ export CROSS_COMPILE=aarch64-linux-gnu-
$ make nintendo-switch_defconfig
$ make

If you encounter issues about a missing rule "/lib/firmware/nvidia/tegra210/vic04_ucode.bin" for the target "firmware" you'll have to :
  • install the firmware-misc-nonfree package
  • if you can't install it, or if it still doesn't work, download the package manually from debian sid and extract the file "/lib/firmware/nvidia/tegra210/vic04_ucode.bin" (from the root of your PC, not on the cloned repo) from the DEB (and chmod it if needed)
If you encounter issues about a missing rule "/lib/firmware/brcm/brcmfmac4356-pcie.txt", download this file and put it in "/lib/firmware/brcm/" (from the root of your PC, not on the cloned repo)

Building the rootfs

This is the annoying part. Download the archive / image corresponding to the distribution you want to use :
If it's a tarball you just downloaded

While it's downloading, you'll have to take a microSD card and, using the software of your choice (I used GParted) :
  • remove every existing partition to only have unallocated space on it (do I need to tell you that you're going to loose everything on the card ?)
  • create a tiny FAT32 partition (I chose 200mb but it doesn't matter) - that'll be mmcbkl0p1, you can label it "garbage"
  • create an ext4 partition on the remaining part of the card - that'll be mmcblk0p2, you can label it "rootfs"
  • it's important that the FAT32 partition comes first and the ext4 one comes after - on the Switch, Linux will look for mmcblk0p2, the second partition, if you have scrolling boot logs and then back to RCM it means you did it wrong
Once the rootfs tarball is downloaded, you can simple extract it to the mounting point of the ext4 partition you just created :

Code:
$ tar xvf ArchLinuxARM-aarch64-latest.tar.gz -C /mounting/point/of/ext4/partition && sync
$ cp ArchLinuxARM-aarch64-latest.tar.gz /mounting/point/of/ext4/partition/root && sync

("/mounting/point/of/ext4/partition/root" is the "root" directory on the partition)

Don't forget to properly eject the SD Card !

If "tar xvf" doesn't work for you you can install "bsdtar" and use "bsdtar -xpf" instead

Then you can put the SD card in the console.

If it's a img / bin file you just downloaded

You can simply write it on your SD card using :
  • If you're on Windows, Ether or Win32DiskImager
  • If you're on Linux / Mac OS : "sudo dd if=yourimage.img of=/dev/sdX && sync" where /dev/sdX is the device of your SD card (unmounted)
You will probably want to open a partition manager to resize the ext4 partition once it's flashed, so that it fits your SD card.

Then you can put the SD card in the console.

Booting linux

Run the exploit :

Code:
$ cd shofel2/exploit
$ sudo ./shofel2.py cbfs.bin ../../coreboot/build/coreboot.rom

Your terminal should now be waiting for the Switch to enter RCM mode.

To do so : (I don't have pictures but that's the same method as fusée gelée, just look at some video tutorials)
  • plug the Switch on your PC using the USB A-to-C cable - use a blue SuperSpeed port if you have one
  • shut it down
  • remove the right joy-con
  • using a method of your choice, short the 10th pin of the right joy-con (the last pin on the right, away from the screen, closer to the back) with the ground : that can be pin 1, 2 or 7, that can also be a screw on the joy-con rack or the console's fan - I personnaly stick a RPi jumper wire in the fan and touch the 10th pin on the other side, works everytime (like this)
  • keep the pins shorted and power the Switch while pressing the volume UP button
If it worked, the console will show a black screen and you'll see the exploit running on your terminal. If you see the Nintendo logo, it has failed. You can power off the console and try again.

Then, run those last commands :

Code:
$ cd shofel2/usb_loader
$ ../../u-boot/tools/mkimage -A arm64 -T script -C none -n "boot.scr" -d switch.scr switch.scr.img
$ sudo ../../imx_usb_loader/imx_usb -c .

Linux should then boot on your console - first the boot logs with the penguins, and then an ArchLinux login prompt. Voilà !
Again, if you have the boot logs and then a black screen, it means you did the SD card part wrong.

Additional notes

Hardware graphics acceleration


The most recents image already contain this fix.

To add mesa drivers install this package using pacman :
https://0w0.st/mesa-full-tegra-r101876.bf5e0276b6-1-aarch64.pkg.tar.xz

You will need a working internet connection to do so.

Then, use this script to choose your power profile : https://0w0.st/power.sh

Full speed RAM


According to the blog post ("Linux on Switch boot chain" section), you need to extract a file from a Pixel C factory image in order to have the RAM working at full speed. I didn't do it so I won't cover it here.

Fixing calibration issues of the touch screen (thanks to @Wizardy)

To fix calibration issues of the touch screen, edit the file /usr/share/X11/xorg.conf.d/10-evdev.confg (of the rootfs)

And change the InputClass section to :

Code:
Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "InvertX" "no"
        Option "InvertY" "yes"
        Option "SwapAxes" "yes"
        Option "Calibration" "0 1279 0 719"
EndSection

Wi-Fi

To setup Wi-Fi, mount the rootfs partition on your host PC and edit the configuration for your network in the file "/etc/NetworkManager/system-connections" (if it doesn't exist, take Gigaspot).

To have a working Wi-Fi you must reboot your Switch and run the exploit again each time you power it off

Moving the rootfs to another partition

If you want to move the rootfs to another partition on your SD card, edit the "shofel2/usb_loader/switch.scr" file and replace "/dev/mmcblk0p2" by the partition you want to use.
 
Last edited by natinusala,

ExploitTnT

Devy | YT: DevRin | dev_settings
Member
Joined
Jul 30, 2017
Messages
150
Trophies
0
XP
270
Country
Austria
  • My Brother tries to use this wire, will it work?
    pI0ODbc.jpg
 

marice

Well-Known Member
Member
Joined
Mar 14, 2009
Messages
170
Trophies
0
XP
450
Country
Netherlands
Really? For me it took about 5 - 8 Minutes before he booted, he took ages to transfer. Maybe he not handle my USB Propperly then.
Did you see the same logs as i posted while having a black screen? I did use an ebay usb 3.0 cable though.. did you do too maybe?
 

EpicLPer

Your friendly Austrian IT Guy
Member
Joined
Mar 13, 2015
Messages
1,060
Trophies
0
Age
28
Location
Austria
Website
epiclper.com
XP
1,141
Country
Austria
Trying to run the exploit from VMware will end up in "OSError: [Errno 90] Message too long". Any way to fix this?

Here's the whole log I get:

bfs.bin ../../coreboot/build/coreboot.rom
File descriptor: 9
b''
entry 400168ed
throwing more
Performing hax...
Size: 0x6c68

b'820000000000686c'
b'0200000000000000000000000000000080754f0100000000716c000000000000000000000000000000000000000000000f0f00000000000000'
URB address: 0x14e7810
Traceback (most recent call last):
File "./shofel2.py", line 247, in <module>
rcm.pwn()
File "./shofel2.py", line 205, in pwn
s.ep0_read_unbounded(overwrite_len)
File "./shofel2.py", line 76, in ep0_read_unbounded
fcntl.ioctl(s.fd, USBDEVFS_SUBMITURB, urb)
OSError: [Errno 90] Message too long
 
Last edited by EpicLPer,

natinusala

Win32 error 31 is not an error
OP
Member
Joined
Dec 1, 2012
Messages
1,032
Trophies
0
Age
44
XP
2,914
Country
France
Sending a message too long is the base of the exploit. Your VM's system doesn't allow it. You need to change how USB passthrough is on your VM, I'm afraid there is not much you can do
 

gbazone

Well-Known Member
Member
Joined
Jun 6, 2014
Messages
212
Trophies
0
XP
713
Country
This is currently the most noob-friendly tuto I can make I'm afraid

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



Ermmm.... no you'll need a more rigid wire, not a ponytail

This works fine for me :)

Edit: The wire is copper so it's pretty rigid, though.

L9TlnQV.jpg
 
Last edited by gbazone,

0C-34

Member
Newcomer
Joined
Sep 29, 2016
Messages
6
Trophies
0
XP
138
Country
Italy
i have a problem while building linux, I'm not an espert, so i leave the log here if someone wants to look at it and help me.
Code:
sonno@ubuntu:~/Desktop/linux$ export ARCH=arm64
sonno@ubuntu:~/Desktop/linux$ export CROSS_COMPILE=aarch64-linux-gnu-
sonno@ubuntu:~/Desktop/linux$ make nintendo-switch_defconfig
#
# configuration written to .config
#
sonno@ubuntu:~/Desktop/linux$ make
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/bounds.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
scripts/checksyscalls.sh: line 215: aarch64-linux-gnu-gcc: command not found
Kbuild:72: recipe for target 'missing-syscalls' failed
make[1]: *** [missing-syscalls] Error 127
Makefile:1093: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
 
Last edited by 0C-34,

dj505

Inexperienced Romhacker
Member
Joined
Oct 4, 2014
Messages
556
Trophies
0
Location
Most likely at the arcade
Website
www.youtube.com
XP
844
Country
Canada
i have a problem while building linux, I'm not an espert, so i leave the log here if someone wants to look at it and help me.
Code:
sonno@ubuntu:~/Desktop/linux$ export ARCH=arm64
sonno@ubuntu:~/Desktop/linux$ export CROSS_COMPILE=aarch64-linux-gnu-
sonno@ubuntu:~/Desktop/linux$ make nintendo-switch_defconfig
#
# configuration written to .config
#
sonno@ubuntu:~/Desktop/linux$ make
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/bounds.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
scripts/checksyscalls.sh: line 215: aarch64-linux-gnu-gcc: command not found
Kbuild:72: recipe for target 'missing-syscalls' failed
make[1]: *** [missing-syscalls] Error 127
Makefile:1093: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
Run:
Code:
apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
That should do the trick. You might also need gcc-arm-linux-gnueabi and g++-arm-linux-gnueabi.
 
  • Like
Reactions: 0C-34

ihaveahax

Well-Known Member
Member
Joined
Apr 20, 2015
Messages
6,069
Trophies
2
XP
7,826
Country
United States
So USB3.0 support is needed and not optional? The physical machine I tried it on only has USB2.0 ports, may have to enable USB3.0 support on VMware tomorrow and try it again.
you have to use 3.0 ports right now, and you have to enable it for your virtual machine. try another machine with 3.0 ports.
 

xXDungeon_CrawlerXx

Well-Known Member
Member
Joined
Jul 29, 2015
Messages
2,092
Trophies
1
Age
28
Location
Liverpool
XP
3,720
Country
I have a problem building coreboot.
upload_2018-4-25_3-37-40.png


If you have a tegra_mtc.bin file error, you'll have to extract it from a Pixel C stock image :
"$ ./build/util/cbfstool/cbfstool bootloader-dragon-google_smaug.7900.97.0.img extract -n fallback/tegra_mtc -f tegra_mtc.bin"

I'm sure "/build/util/cbfstool/cbfstool" is not the correct path, it's more likely "/build/util/cbfstool/"
upload_2018-4-25_3-40-12.png


But even with this command, it's not working
upload_2018-4-25_3-41-19.png


Any idea what to do?
 

Kobigov

Well-Known Member
Member
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
Anyone know what's broken here? Did I fuck up the gparted stuff?
 

Attachments

  • Screenshot from 2018-04-24 18-42-58.png
    Screenshot from 2018-04-24 18-42-58.png
    32.9 KB · Views: 338

clank

Well-Known Member
Newcomer
Joined
Jan 24, 2015
Messages
99
Trophies
0
Age
27
Location
/dev/nvme0n1p1
XP
503
Country
Antigua and Barbuda
Mind doing a quick writeup for all users without a USB 3.0 port? (Just the patch part and installing Linux). So that it could be pinned to the first post...
I just followed the instructions, got a couple of the already mentioned errors, but nothing else. Done from a machine running Arch (how do you know somebody runs Arch? blablabla...).

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

Anyone know what's broken here? Did I fuck up the gparted stuff?
Run using sudo, if that doesn't work, try making sure there's no error during the linux build process, it might be the tegra_mtc.bin thingy.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Bunjolio @ Bunjolio: c