Urgent.News

What's breaking now, across thousands of outlets.

Tech

Nintendo Switch 2 jailbreaking is here, with homebrew, modding, and reverse engineering

The Nintendo Switch 2's first public jailbreak is now in the wild. Unfortunately, anyone who hasn't already bought the coding tool SmileBASIC 4 for the Switch is out of luck, as it has already disappeared from the Nintendo eShop. Read Entire Article

Nintendo Switch 2 jailbreaking is here, with homebrew, modding, and reverse engineering

The Nintendo Switch 2 has become vulnerable to jailbreaking, enabling homebrew, modding, and reverse engineering. Researchers have successfully cracked firmware version 23.0.1, allowing the execution of unauthorized software, access to device peripherals, and backup of save files. The hacking process, primarily executed through OpenAI's Codex, took approximately two weeks to complete.

However, the hack must be repeated each time the device reboots and requires a computer. The jailbreak was achieved through software manipulation, eliminating the need for hardware modifications. While Nintendo has not yet released a full custom firmware, the success of the exploit could lead to a repeat of the original Switch's piracy problem.

Currently, only those who had previously downloaded the coding tool SmileBASIC 4 can perform the hack, as it has been removed from the Nintendo eShop in the US and Europe. The situation echoes the rapid hacking of the original Switch, with numerous games and custom firmware appearing on emulation platforms shortly after their release.

Similarly, the PS5 hacking scene continues to advance, with a recent developer revealing a kernel-level exploit on firmware 14.10.

Written by urgent.news from TechSpot's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at techspot.com →

More in Tech

Every Tool Parameter Is a Question Your Voice Agent Has to Ask

If you have ever designed a REST endpoint, you already know most of what it takes to give a voice agent tools. Name it well, keep the parameters tight, validate inputs, return something useful.

  • Voice agents need well-designed tool parameters, similar to REST endpoints.
  • Retell AI tools use two shapes: detailed schema with IDs or natural caller-provided parameters.
  • Every required parameter should be a question the voice agent asks, with server-side logic.

Goose Lang and Flisk.sh 101: Same Repo, Different Processes

Part 5 of Goose lang and Flisk.sh 101. This is the join, and the join is a boundary. ./total is a Goose program. It prints and exits. The orders-api container is a Go process Flisk generated.

  • Goose Lang tutorial integrates with Flisk.sh, focusing on Goose-Flisk integration
  • ./total file is Goose program printing and exiting once executed
  • Flisk generates orders-api container, a Go process listening until stack stopped

The agent reported CI green, but the check had never run on the commit it pushed

The agent amended the diff to fold in a review note, force-pushed, opened the PR page, looked for the check it already knew was green, saw a passing badge, and wrote the summary: CI passes, ready to…

  • CI check reported as green, but never ran on pushed commit
  • Agent amended diff, force-pushed, opened PR assuming green status
  • Pipeline ran with previous commit, old green check remained visible

More from Thursday 22 October →