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,
  • Like
Reactions: Deleted member 518148, globalc, MissingNo._ and 49 others
Click to expand...
Kobigov

Kobigov

Well-Known Member
Member
Level 3
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
Admiral124 said:
I've tried removing the SD card and it does the same thing. I've also left it for about 15-20 minutes but still nothing. Any suggestions?
Click to expand...

It seems like that should be working, looks the same as mine when it boots. Might just want to wait till tomorrow when we hopefully have something we can actually mess around with lol.
 
KazoWAR

KazoWAR

Well-Known Member
Member
Level 10
Joined
Aug 12, 2008
Messages
1,952
Trophies
1
Age
35
Location
Winter Haven
XP
2,130
Country
United States
I can't build coreboot, no arm compiler found? idk if this has to do with the toolchains but both are in /home/kazo/toolchains named aarch64-linux-gnu and arm-linux-gnueabi. and echo $PATH shows
Code: 
/home/kazo/bin:/home/kazo/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/kazo/toolchains/aarch64-linux-gnu/bin:/home/kazo/toolchains/arm-linux-gnueabi/bin
 
Last edited by KazoWAR,
Kobigov

Kobigov

Well-Known Member
Member
Level 3
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
KazoWAR said:
I can't build coreboot, no arm compiler found? idk if this has to do with the toolchains but both are in /home/kazo/toolchains named aarch64-linux-gnu and arm-linux-gnueabi. and echo $PATH shows
Code: 
/home/kazo/bin:/home/kazo/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/kazo/toolchains/aarch64-linux-gnu/bin:/home/kazo/toolchains/arm-linux-gnueabi/bin
Click to expand...
Make sure the terminal your running in has the path set correctly, I spent like an hour before I realized I was running it in a new terminal without the path set to them. If that's not it idk.
 
TheHomesk1llet

TheHomesk1llet

Also known as "Kupo"
Member
Level 4
Joined
Apr 29, 2013
Messages
210
Trophies
0
Location
Cyberspace
XP
439
Country
United States
I'm running into an issue with running make in imx_usb_loader. I've made sure libusb1.0-0-dev is installed, as well as the rest of the dependencies listed, but it still acts as though it's missing.

Has anyone else encountered this problem and found a solution?
Code: 
kupo@ubuntu:~/imx_usb_loader$ make
cc -o imx_usb imx_usb.o imx_sdp.o  `pkg-config --libs libusb-1.0`
/bin/sh: 1: pkg-config: not found
imx_usb.o: In function `print_devs':
/home/kupo/imx_usb_loader/imx_usb.c:61: undefined reference to `libusb_get_device_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:67: undefined reference to `libusb_get_config_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:87: undefined reference to `libusb_free_config_descriptor'
imx_usb.o: In function `find_imx_dev':
/home/kupo/imx_usb_loader/imx_usb.c:193: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:194: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:196: undefined reference to `libusb_get_device_descriptor'
imx_usb.o: In function `transfer_hid':
/home/kupo/imx_usb_loader/imx_usb.c:262: undefined reference to `libusb_control_transfer'
/home/kupo/imx_usb_loader/imx_usb.c:274: undefined reference to `libusb_interrupt_transfer'
imx_usb.o: In function `transfer_bulk':
/home/kupo/imx_usb_loader/imx_usb.c:321: undefined reference to `libusb_bulk_transfer'
imx_usb.o: In function `do_work':
/home/kupo/imx_usb_loader/imx_usb.c:419: undefined reference to `libusb_get_configuration'
/home/kupo/imx_usb_loader/imx_usb.c:422: undefined reference to `libusb_kernel_driver_active'
/home/kupo/imx_usb_loader/imx_usb.c:423: undefined reference to `libusb_detach_kernel_driver'
/home/kupo/imx_usb_loader/imx_usb.c:425: undefined reference to `libusb_claim_interface'
/home/kupo/imx_usb_loader/imx_usb.c:485: undefined reference to `libusb_release_interface'
imx_usb.o: In function `do_autodetect_dev':
/home/kupo/imx_usb_loader/imx_usb.c:504: undefined reference to `libusb_init'
/home/kupo/imx_usb_loader/imx_usb.c:508: undefined reference to `libusb_get_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:517: undefined reference to `libusb_free_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:560: undefined reference to `libusb_open_device_with_vid_pid'
/home/kupo/imx_usb_loader/imx_usb.c:583: undefined reference to `libusb_close'
/home/kupo/imx_usb_loader/imx_usb.c:594: undefined reference to `libusb_exit'
collect2: error: ld returned 1 exit status
Makefile:29: recipe for target 'imx_usb' failed
make: *** [imx_usb] Error 1
 
NightStorm1000

NightStorm1000

Well-Known Member
Member
Level 5
Joined
Mar 2, 2015
Messages
200
Trophies
0
Age
29
XP
538
Country
Austria
TheHomesk1llet said:
I'm running into an issue with running make in imx_usb_loader. I've made sure libusb1.0-0-dev is installed, as well as the rest of the dependencies listed, but it still acts as though it's missing.

Has anyone else encountered this problem and found a solution?
Code: 
kupo@ubuntu:~/imx_usb_loader$ make
cc -o imx_usb imx_usb.o imx_sdp.o  `pkg-config --libs libusb-1.0`
/bin/sh: 1: pkg-config: not found
imx_usb.o: In function `print_devs':
/home/kupo/imx_usb_loader/imx_usb.c:61: undefined reference to `libusb_get_device_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:67: undefined reference to `libusb_get_config_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:87: undefined reference to `libusb_free_config_descriptor'
imx_usb.o: In function `find_imx_dev':
/home/kupo/imx_usb_loader/imx_usb.c:193: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:194: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:196: undefined reference to `libusb_get_device_descriptor'
imx_usb.o: In function `transfer_hid':
/home/kupo/imx_usb_loader/imx_usb.c:262: undefined reference to `libusb_control_transfer'
/home/kupo/imx_usb_loader/imx_usb.c:274: undefined reference to `libusb_interrupt_transfer'
imx_usb.o: In function `transfer_bulk':
/home/kupo/imx_usb_loader/imx_usb.c:321: undefined reference to `libusb_bulk_transfer'
imx_usb.o: In function `do_work':
/home/kupo/imx_usb_loader/imx_usb.c:419: undefined reference to `libusb_get_configuration'
/home/kupo/imx_usb_loader/imx_usb.c:422: undefined reference to `libusb_kernel_driver_active'
/home/kupo/imx_usb_loader/imx_usb.c:423: undefined reference to `libusb_detach_kernel_driver'
/home/kupo/imx_usb_loader/imx_usb.c:425: undefined reference to `libusb_claim_interface'
/home/kupo/imx_usb_loader/imx_usb.c:485: undefined reference to `libusb_release_interface'
imx_usb.o: In function `do_autodetect_dev':
/home/kupo/imx_usb_loader/imx_usb.c:504: undefined reference to `libusb_init'
/home/kupo/imx_usb_loader/imx_usb.c:508: undefined reference to `libusb_get_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:517: undefined reference to `libusb_free_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:560: undefined reference to `libusb_open_device_with_vid_pid'
/home/kupo/imx_usb_loader/imx_usb.c:583: undefined reference to `libusb_close'
/home/kupo/imx_usb_loader/imx_usb.c:594: undefined reference to `libusb_exit'
collect2: error: ld returned 1 exit status
Makefile:29: recipe for target 'imx_usb' failed
make: *** [imx_usb] Error 1
Click to expand...

pkg-config is not installed
 
  • Like
Reactions: lordelan
T

TheKrane

Well-Known Member
Newcomer
Level 3
Joined
Apr 24, 2018
Messages
48
Trophies
0
Age
25
XP
251
Country
Austria
TheHomesk1llet said:
I'm running into an issue with running make in imx_usb_loader. I've made sure libusb1.0-0-dev is installed, as well as the rest of the dependencies listed, but it still acts as though it's missing.

Has anyone else encountered this problem and found a solution?
Code: 
kupo@ubuntu:~/imx_usb_loader$ make
cc -o imx_usb imx_usb.o imx_sdp.o  `pkg-config --libs libusb-1.0`
/bin/sh: 1: pkg-config: not found
imx_usb.o: In function `print_devs':
/home/kupo/imx_usb_loader/imx_usb.c:61: undefined reference to `libusb_get_device_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:67: undefined reference to `libusb_get_config_descriptor'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:87: undefined reference to `libusb_free_config_descriptor'
imx_usb.o: In function `find_imx_dev':
/home/kupo/imx_usb_loader/imx_usb.c:193: undefined reference to `libusb_get_bus_number'
/home/kupo/imx_usb_loader/imx_usb.c:194: undefined reference to `libusb_get_device_address'
/home/kupo/imx_usb_loader/imx_usb.c:196: undefined reference to `libusb_get_device_descriptor'
imx_usb.o: In function `transfer_hid':
/home/kupo/imx_usb_loader/imx_usb.c:262: undefined reference to `libusb_control_transfer'
/home/kupo/imx_usb_loader/imx_usb.c:274: undefined reference to `libusb_interrupt_transfer'
imx_usb.o: In function `transfer_bulk':
/home/kupo/imx_usb_loader/imx_usb.c:321: undefined reference to `libusb_bulk_transfer'
imx_usb.o: In function `do_work':
/home/kupo/imx_usb_loader/imx_usb.c:419: undefined reference to `libusb_get_configuration'
/home/kupo/imx_usb_loader/imx_usb.c:422: undefined reference to `libusb_kernel_driver_active'
/home/kupo/imx_usb_loader/imx_usb.c:423: undefined reference to `libusb_detach_kernel_driver'
/home/kupo/imx_usb_loader/imx_usb.c:425: undefined reference to `libusb_claim_interface'
/home/kupo/imx_usb_loader/imx_usb.c:485: undefined reference to `libusb_release_interface'
imx_usb.o: In function `do_autodetect_dev':
/home/kupo/imx_usb_loader/imx_usb.c:504: undefined reference to `libusb_init'
/home/kupo/imx_usb_loader/imx_usb.c:508: undefined reference to `libusb_get_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:517: undefined reference to `libusb_free_device_list'
/home/kupo/imx_usb_loader/imx_usb.c:560: undefined reference to `libusb_open_device_with_vid_pid'
/home/kupo/imx_usb_loader/imx_usb.c:583: undefined reference to `libusb_close'
/home/kupo/imx_usb_loader/imx_usb.c:594: undefined reference to `libusb_exit'
collect2: error: ld returned 1 exit status
Makefile:29: recipe for target 'imx_usb' failed
make: *** [imx_usb] Error 1
Click to expand...

It says pkg-config missing. If you are on Ubuntu/Debian try "sudo apt-get install -y pkg-config" otherwise just google how to install pkg-config on your distro.

EDIT: NightStorm1000 was faster haha
 
KazoWAR

KazoWAR

Well-Known Member
Member
Level 10
Joined
Aug 12, 2008
Messages
1,952
Trophies
1
Age
35
Location
Winter Haven
XP
2,130
Country
United States
i dont even know
Code: 
  AS      bl31/aarch64/runtime_exceptions.S
bl31/aarch64/runtime_exceptions.S: Assembler messages:
bl31/aarch64/runtime_exceptions.S:184: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:192: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:197: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:202: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:216: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:220: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:224: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:228: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:242: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:246: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:250: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:258: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:272: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:276: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:280: Error: non-constant expression in ".if" statement
bl31/aarch64/runtime_exceptions.S:288: Error: non-constant expression in ".if" statement
Makefile:614: recipe for target '/home/kazo/coreboot/build/3rdparty/arm-trusted-firmware/bl31/runtime_exceptions.o' failed
make[1]: *** [/home/kazo/coreboot/build/3rdparty/arm-trusted-firmware/bl31/runtime_exceptions.o] Error 1
src/arch/arm64/Makefile.inc:181: recipe for target 'build/bl31.elf' failed
make: *** [build/bl31.elf] Error 2
 
TheHomesk1llet

TheHomesk1llet

Also known as "Kupo"
Member
Level 4
Joined
Apr 29, 2013
Messages
210
Trophies
0
Location
Cyberspace
XP
439
Country
United States
Yikes, now i'm getting something different when trying to make the firmware image:
Code: 
make[1]: *** No rule to make target '/lib/firmware/brcm/brcmfmac4356-pcie.txt', needed by 'firmware/brcm/brcmfmac4356-pcie.txt.gen.o'.  Stop.
Makefile:1048: recipe for target 'firmware' failed
make: *** [firmware] Error 2

Everything else seems to compile fine, though.
 
NightStorm1000

NightStorm1000

Well-Known Member
Member
Level 5
Joined
Mar 2, 2015
Messages
200
Trophies
0
Age
29
XP
538
Country
Austria
TheHomesk1llet said:
Yikes, now i'm getting something different when trying to make the firmware image:
Code: 
make[1]: *** No rule to make target '/lib/firmware/brcm/brcmfmac4356-pcie.txt', needed by 'firmware/brcm/brcmfmac4356-pcie.txt.gen.o'.  Stop.
Makefile:1048: recipe for target 'firmware' failed
make: *** [firmware] Error 2

Everything else seems to compile fine, though.
Click to expand...
Read the first Post again
 
Kobigov

Kobigov

Well-Known Member
Member
Level 3
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
TheHomesk1llet said:
I read through it pretty thoroughly. I'm not getting the error shown below the make command for the firmware image.
Click to expand...

"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)"
 
0C-34

0C-34

Member
Newcomer
Level 2
Joined
Sep 29, 2016
Messages
6
Trophies
0
XP
138
Country
Italy
S3RG said:
when I run the exploit I get "invalid coreboot.rom".
I've recompiled it a few times and get the same thing, seems to make fine though, no errors there. something I'm doing wrong?
Click to expand...
same problem here :(
Cattura.PNG
 
  • Like
Reactions: S3RG
xXDungeon_CrawlerXx

xXDungeon_CrawlerXx

Well-Known Member
Member
Level 13
Joined
Jul 29, 2015
Messages
2,092
Trophies
1
Age
28
Location
Liverpool
XP
3,722
Country
Any idea what to do?
The RCM Mode on the Nintendo Switch boots (stays at black Screen). VMWare shows the device as "NVidia APX" before using the commands to boot Linux.
After that, as NVidia USB Device.

I end up with "Could not open device vid=0x0955 pid=0x701a"

upload_2018-4-25_13-1-14.png
 
davidux22

davidux22

Member
Newcomer
Level 1
Joined
Apr 25, 2018
Messages
8
Trophies
0
XP
109
Country
Italy
Someone can help me with this error ?

Code: 
davidux22@davidux22-MS-7A12:~/shofel2/exploit$ export PATH=$PATH:/home/davidux22/aarch64/bin:/home/davidux22/gnueabi/bin

davidux22@davidux22-MS-7A12:~/shofel2/exploit$ make
arm-linux-gnueabi-gcc -march=armv4t -mthumb -Wall -Werror -Os -MMD -ffreestanding -fno-common    -fomit-frame-pointer -nostdlib -fno-builtin-printf -fno-asynchronous-unwind-tables -fPIE -fno-builtin -fno-exceptions -Wl,--no-dynamic-linker,--build-id=none,-T,romhax.ld -std=gnu11 -c -o obj/cbfs.o cbfs.c
Assembler messages:
Fatal error: invalid -march= option: `armv4t'
Makefile:23: recipe for target 'obj/cbfs.o' failed
make: *** [obj/cbfs.o] Error 1
 
  • Like
Reactions: ArtEze
T

TheKrane

Well-Known Member
Newcomer
Level 3
Joined
Apr 24, 2018
Messages
48
Trophies
0
Age
25
XP
251
Country
Austria
xXDungeon_CrawlerXx said:
Any idea what to do?
The RCM Mode on the Nintendo Switch boots (stays at black Screen). VMWare shows the device as "NVidia APX" before using the commands to boot Linux.
After that, as NVidia USB Device.

I end up with "Could not open device vid=0x0955 pid=0x701a"

View attachment 121286
Click to expand...

Try "sudo ../../imx_usb_loader/imx_usb -c ." as the last command.
 
  • Like
Reactions: lordelan, Kobigov and xXDungeon_CrawlerXx

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Homebrew  duckstation for Switch

Can you trade in a banned switch for an unbanned one?

Why is Atmosphere so dominant?

Crosscode Hacking thread

Hacking  Weird findings from that DQ trilogy switch port

Migswitch backups without certificate files

switch change sd card, but android start fail

Hacking Hardware  Picofly on "old" Samsung EMMC glitching fails sometimes

General chit-chat
Help Users
  • BakerMan
    I rather enjoy a life of taking it easy. I haven't reached that life yet though.
  • SylverReZ @ SylverReZ:
    @Materia_tofu, We do learn a lot from plenty of talented individuals.
  • Materia_tofu @ Materia_tofu:
    this is true! i learned how to make soundfont remixes from a friend back in 2021
     +1
  • BakerMan @ BakerMan:
    Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.
     +2
  • Veho @ Veho:
    That's a relief to hear. Do you know what happened?
  • SylverReZ @ SylverReZ:
    @BakerMan, Any idea what happened? I hope that your brother's doing good.
  • BakerMan @ BakerMan:
    Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
  • BakerMan @ BakerMan:
    He couldn't eat until after his MRI, when he had a bomb pop.
  • BakerMan @ BakerMan:
    What matters now is that he's doing alright.
  • Veho @ Veho:
    But you still don't know what it was?
  • Veho @ Veho:
    Has he had seizures before?
  • The Real Jdbye @ The Real Jdbye:
    apparently stress can cause seizures, my brother had one during a test once
  • The Real Jdbye @ The Real Jdbye:
    never had one before that, and never had one since
  • Veho @ Veho:
    https://i.imgur.com/bG1pQld.mp4
     +1
  • Psionic Roshambo @ Psionic Roshambo:
    https://www.youtube.com/watch?v=_9PnFJMnYT0
  • Redleviboy123 @ Redleviboy123:
    Question about game texture chanching Do i need an own game id?
  • The Real Jdbye @ The Real Jdbye:
    @Veho for those that want to
    experience being sonic the hedgehog
  • Veho @ Veho:
    Ah, you mean
    furries.
  • The Real Jdbye @ The Real Jdbye:
    well, sonic fans are a whole separate thing from furries
  • The Real Jdbye @ The Real Jdbye:
    like bronys
  • The Real Jdbye @ The Real Jdbye:
    sonic porn is too weird even for me
  • Dumpflam @ Dumpflam:
    bruh
  • Dumpflam @ Dumpflam:
    guys how do i delete a post
  • The Real Jdbye @ The Real Jdbye:
    you don't
  • The Real Jdbye @ The Real Jdbye:
    you can report it and request deletion
  • BakerMan @ BakerMan:
    Also, no, that was his first time having a seizure, and hopefully the last
    BakerMan @ BakerMan: Also, no, that was his first time having a seizure, and hopefully the last