Bad Update is the currently documented software-only exploit for Xbox 360 dashboard/kernel 17559 (also written as 2.0.17559). It can start unsigned code and legitimate homebrew without opening the console or soldering, but it is not a permanent softmod: shutting down or rebooting clears the modified state, so you must run the exploit again after the retail system starts.
You need a USB flash drive and a supported trigger game. The project README currently lists Rock Band Blitz; it marks Tony Hawk’s American Wasteland as deprecated. Confirm your dashboard, console revision, and the live README before copying anything, because package contents and compatibility notes can change.
As an Amazon Associate I earn from qualifying purchases.
What “software exploit” means on an Xbox 360
Bad Update takes advantage of a vulnerability in the Xbox 360 software stack, including the hypervisor layer that normally enforces the retail execution model. When the trigger succeeds, the console can load unsigned programs and homebrew during that session. You do not need to remove the case, install a modchip, or solder wires.
The important distinction is persistence. Bad Update changes the running system only; it does not install a permanently modified boot path. The project README states this plainly: This exploit is NOT persistent!
A normal restart or complete power-off returns the console to its retail state. That behavior is a design limitation, not an installation failure.
#1 Best Overall
- USB-C 2-in-1 storage OTG: The Lexar JumpDrive Dual Drive D40E features USB Type-A and Type-C connectors in a slim, portable form factor for easy device compatibility
- Transfer speeds up to 100MB/s: Based on internal testing, performance may vary depending upon the host device, interface, and usage conditions. 1MB=1,000,000 bytes
- Plug and Play: Widely compatible with USB Type-C smartphones, tablets, laptops, Macs, and traditional Type-A devices, no software installation required. The 360° swivel design allows for easy switching between connectors without the hassle of losing a cap
- Durable & Compact: The Lexar D40E USB memory stick features a metal enclosure, withstands temperatures from 0° to 50° C (32°F to 122°F), and is lightweight at 26g with dimensions of 70.4 x 16.9 x 11.7mm
- Security & Warranty: Securely protects files using an advanced security software solution with 256-bit AES encryption. Backed by a Lexar 3-year limited warranty
This guide is about lawful homebrew, software preservation, accessibility experiments, and understanding the hardware. An exploit does not grant permission to copy games you do not own, defeat someone else’s access controls, or distribute copyrighted content.
Check compatibility before you prepare files
1. Verify the dashboard and kernel number
Bad Update’s documented release targets dashboard 17559. ConsoleMods describes the same target as kernel/dashboard 2.0.17559. Read the number on the Xbox 360’s System Information screen rather than relying on the console’s model name or the age of an old guide.
- 17559 / 2.0.17559: the documented target for Bad Update.
- Any other number: do not assume the exploit applies. The available documentation does not establish a safe downgrade path from a newer retail dashboard, and forcing files intended for another version can simply fail.
Record the complete number before downloading a package. A guide that says only “latest dashboard” may be stale or may be describing a different exploit.
2. Identify the console revision
ConsoleMods lists Bad Update for the three broad Xbox 360 families—Phat, S, and E—when they are running 2.0.17559. This is unusually broad coverage for late hardware. In particular, Winchester-based E consoles are excluded from the JTAG and RGH hardware methods described by ConsoleMods, while Bad Update remains the documented software option at the supported dashboard.
Revision compatibility does not override the dashboard requirement. Treat both facts as a pair: identify the physical revision, then verify that its installed kernel is 2.0.17559.
3. Confirm the trigger game
The current Bad Update README requires a supported game trigger and lists Rock Band Blitz. It marks Tony Hawk’s American Wasteland as deprecated. If an older tutorial tells you to obtain or configure Tony Hawk, do not follow that procedure without checking the current project notes; deprecated instructions may refer to files or behavior that the maintainers no longer support.
What you need
- An Xbox 360 on dashboard/kernel 17559. This is the documented software target.
- A compatible console revision. Phat, S, and E revisions are listed for Bad Update at that dashboard.
- A USB flash drive. The project identifies a USB stick as a prerequisite. It does not specify a brand, capacity, speed rating, or a universally tested model, so no particular drive can be presented as guaranteed.
- A supported trigger game. The current README lists Rock Band Blitz; verify the exact release notes before using any other title.
- The current project files and instructions. Follow the Xbox360BadUpdate project README for the release that matches your dashboard. File names and the required folder layout are implementation details that can change.
There is no fixed accessory specification or price in the project requirements. A USB flash drive is the only named accessory, and the documentation does not endorse a capacity, brand, or model. Treat any shopping link as a way to locate a generic accessory, not as a guarantee that a particular product has been tested.
Keep your original save data and retail files intact. Do not delete system content merely to make room for an exploit package, and do not assume that a package copied from an older tutorial has the same layout as the current release.
Prepare without damaging the retail setup
Make a short inventory before touching the console. Write down the complete dashboard number, whether the machine is a Phat, S, or E revision, and which trigger game you actually have. This prevents a common mistake: treating a model name as proof of compatibility while overlooking the kernel requirement.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
Use the project’s current release notes as the single reference for the package layout. Do not merge a folder from one release with executable files from another, and do not rename files simply to make them look tidier. The trigger depends on the expected names and locations. If an archive utility adds an extra top-level folder, compare the resulting USB layout with the README before launching the game.
Protect ordinary data on the USB drive. Copy personal files elsewhere, because any format or storage-configuration prompt can affect existing contents. If the Xbox 360 offers to configure the drive as console storage, pause and check the README’s instruction for that release rather than accepting automatically.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Run Bad Update from the current documentation
The project’s README is the authority for the exact package and trigger sequence. The safe workflow below explains what each stage is for without inventing commands or unsupported file names.
- Write down the version. On the System Information screen, confirm that the dashboard/kernel is 17559 (2.0.17559). Stop if the number differs.
- Read the release notes first. Obtain the current Bad Update package from the project’s own documentation and check its stated requirements. Do not combine files from different releases or from an archived tutorial.
- Prepare the USB drive exactly as specified. Format or arrange it only as the README directs, then copy the supplied folders and files without renaming them. The documentation’s layout is part of the exploit trigger; a visually similar folder structure is not enough.
- Connect the USB drive to the console. Use the port and storage-selection steps described by the current README. If the Xbox 360 asks to configure the drive as console storage, do not proceed until you understand whether that action would erase the exploit files.
- Launch the supported trigger game. Use the game and entry point named by the current release. Do not substitute a title because an old video shows a different method.
- Start the trigger sequence. Follow the on-screen or README instructions precisely. A successful run should return you to the documented homebrew or unsigned-code environment; it does not permanently replace the retail dashboard.
- Load only software you understand and are entitled to use. Test a known legitimate homebrew application first. Keep notes about which step succeeded so you can repeat the process later.
- Repeat after every reboot or shutdown. When the console powers on normally, the exploit state is gone. Reconnect the prepared USB drive and run the documented trigger again.
Do not improvise a “persistent” patch. The project explicitly says Bad Update cannot be made persistent. Attempts to alter system files to force persistence are outside the documented method and can leave the console unable to boot.
What a successful session looks like
A successful trigger does not replace the dashboard permanently or create a new boot menu that appears every time the console starts. Instead, the retail operating system boots first, and the supported game-based sequence creates a modified session. Homebrew is available only after that sequence has completed.
Plan around that lifecycle. If you intend to demonstrate an application, start the console, connect the prepared USB drive, launch the supported game, and then load the application. If you restart while troubleshooting, expect to repeat the trigger rather than assuming the previous state remains in memory. Keeping a written checklist of the release, game entry point, and successful step can make repeat sessions predictable.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the temporary state can and cannot do
What it enables
During a successful session, Bad Update can enable unsigned code and homebrew. That makes it useful for applications created by the community, preservation work, development experiments, and other software that the retail dashboard would not launch.
What it does not change
- It does not permanently modify the boot chain.
- It does not survive a reboot or power loss.
- It does not turn every Xbox 360 dashboard into a compatible target.
- It does not make a Winchester console compatible with JTAG or RGH.
- It does not provide a legal basis for downloading commercial games or bypassing copyright protections.
Because the retail operating system starts before you trigger Bad Update, the experience differs from a console with a persistent hardware modification. Convenience depends on how often you reboot and whether the applications you want can run within the temporary session.
How Bad Update compares with other Xbox 360 modification paths
The following distinctions come from the current ConsoleMods compatibility and getting-started guides. “Persistent” describes whether a modified environment can start automatically; it does not describe whether every application or dashboard feature is available.
Rank #3
- What You Get - 2 pack 64GB genuine USB 2.0 flash drives, 12-month warranty and lifetime friendly customer service
- Great for All Ages and Purposes – the thumb drives are suitable for storing digital data for school, business or daily usage. Apply to data storage of music, photos, movies and other files
- Easy to Use - Plug and play USB memory stick, no need to install any software. Support Windows 7 / 8 / 10 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, compatible with USB 2.0 and 1.1 ports
- Convenient Design - 360°metal swivel cap with matt surface and ring designed zip drive can protect USB connector, avoid to leave your fingerprint and easily attach to your key chain to avoid from losing and for easy carrying
- Brand Yourself - Brand the flash drive with your company's name and provide company's overview, policies, etc. to the newly joined employees or your customers
| Path | Documented fit | Hardware work | Persistence and limitations |
|---|---|---|---|
| Bad Update | Phat, S, and E revisions on dashboard/kernel 2.0.17559, according to ConsoleMods; the project README identifies dashboard 17559. | Software-only; no case opening or soldering is required for the documented method. | Temporary. A USB drive and supported game trigger are required, and the exploit must be run again after shutdown or reboot. |
| JTAG/RGH | Board- and bootloader-specific. Not every revision supports every method. | Requires soldering and hardware installation. | Can provide a persistent modified startup and a more fully controlled operating environment. Winchester E consoles are not compatible with JTAG or RGH. |
| King Kong exploit | Limited to dashboard/kernel 2.0.4532 or 2.0.4548, according to ConsoleMods. | Uses a modified game-based exploit rather than the current Bad Update workflow. | Legacy and narrow: it boots Linux through a modified game and does not provide general homebrew outside Linux. The reviewed guide documents no retail downgrade path to the vulnerable dashboard. |
These are different categories, not interchangeable names. Bad Update is a current software-only session exploit. JTAG and RGH are hardware-dependent modifications intended to provide a persistent modified startup when the board and bootloader qualify. King Kong is an older, tightly limited path tied to two specific dashboard/kernel versions and a Linux use case.
Recommended Free Tools
Choose the route that matches your goal
Bad Update is the practical choice when
- Your console is on 2.0.17559.
- You have a Phat, S, or E revision and do not want to open it.
- You are comfortable repeating a short trigger after each restart.
- Your objective is legitimate homebrew or software experimentation rather than a permanently modified boot environment.
JTAG or RGH is worth investigating when
- You need a persistent modified startup.
- You accept soldering, disassembly, and board-specific installation work.
- Your motherboard and bootloader are confirmed compatible by a current hardware guide.
Do not select JTAG or RGH solely because a console is an E model. Winchester E systems are specifically excluded from those methods in the ConsoleMods exploit chart.
The King Kong route is relevant only to a narrow legacy case
If a console is already on 2.0.4532 or 2.0.4548 and your goal is the Linux capability documented for that exploit, the older path may be of historical interest. It is not a general substitute for Bad Update on 17559, and the available guide does not document a normal retail downgrade route.
Troubleshoot the common failure modes
The trigger does nothing
- Recheck the complete dashboard/kernel number. A one-digit difference is enough to make a package inapplicable.
- Confirm that the USB contents match the current README exactly and that files were not renamed by a computer or archive utility.
- Use the currently listed trigger game. Tony Hawk’s American Wasteland is marked deprecated; an old tutorial using it may no longer describe the supported path.
- Read the release notes again before changing the console. The project’s requirements can change, while videos and forum posts remain online.
It worked, then disappeared
That is the expected behavior after a reboot or power-off. Bad Update is non-persistent, so start the retail console, reconnect the prepared USB drive, and repeat the documented trigger sequence.
The console is a Winchester E
At dashboard 2.0.17559, ConsoleMods lists Bad Update for E revisions, while its exploit chart excludes Winchester from JTAG and RGH. Verify the dashboard and follow the Bad Update documentation rather than attempting a hardware method that the chart rules out.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsAn old guide asks for a different dashboard
Do not downgrade or mix exploit packages based on an unverified tutorial. The current Bad Update target is 17559, and the King Kong documentation covers only 2.0.4532 or 2.0.4548. The reviewed material does not establish a safe retail downgrade procedure.
You are choosing a USB drive
A USB flash drive is required, but the project does not publish a tested brand, capacity, or model in the documented prerequisites. Treat compatibility as something to verify with the current README and your own non-critical test data, not as a promise attached to a particular product.
The Xbox asks to configure the USB
Stop at that prompt until you have checked the current instructions. Configuration can change how the console recognizes the device and may affect existing files. The safe response is not to guess, but to follow the release-specific storage steps and keep a backup of anything important.
You are tempted to make it permanent
Do not treat a script, patched system file, or forum modification as an extension of the documented exploit. The project states that Bad Update is not persistent and cannot be made persistent. A persistent modified startup belongs to the separate, hardware-dependent JTAG/RGH category and requires its own compatibility assessment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- GOOD VALUE PACKAGE - 1 Pack 32GB Memory Stick USB 2.0 Flash Drives with great cost performance and high quality.
- BIG CAPACITY - The available capacity: 29.10GB-29.8GB, You can save the data of movies, music, photos, designs, programs, manuals, handouts in a high speed.Good performance in digital data storing, transferring and sharing with families, friends, workmates, clients and machines.
- EASY TO USE & PLUG AND WORK - Support windows 7 / 8 / 10 / Vista / XP / 2000 / ME / NT Linux and Mac OS, Compatible with USB2.0 and below.
- TWISTTURN DESIGN & EASY CARRY - The metal clip rotates 360° round the ABS plastic body which with rubber oil skin feeling finish. The capless design can avoid lossing of cap, and providing efficient protection to the USB port.
- WARRANTY & SUPPORT - SIMMAX logo is laser printed on the USB connector surface, our products are of good quality and we promise that any problem about the product within one year since you buy.
Use the exploit responsibly
Keep a clear separation between homebrew development and commercial content. Run applications whose licensing and provenance you understand, preserve your own discs and saves, and avoid distributing copyrighted files. If a homebrew author supplies installation or support instructions, use those instructions rather than modifying the exploit package yourself.
Document your own setup: dashboard number, console revision, trigger game, package release, and the point at which the trigger succeeded. Those notes make a temporary exploit manageable without encouraging unsafe changes to the system. When the project publishes a new release, recheck compatibility before replacing a working USB layout.
Frequently asked questions
Is Bad Update a permanent Xbox 360 softmod?
No. It is a non-persistent software-only exploit. Rebooting or powering off returns the console to its retail state, and the trigger must be run again.
Which dashboard does it support?
The documented target is dashboard/kernel 17559, also written as 2.0.17559. Do not assume a newer or older number works, and do not downgrade based on an unverified tutorial.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Does it work on Phat, Slim, and E consoles?
ConsoleMods lists Phat, S, and E revisions for Bad Update at 2.0.17559. You still need to verify the exact dashboard. Hardware revision alone is not enough.
What game is currently supported?
The project README currently lists Rock Band Blitz. It marks Tony Hawk’s American Wasteland as deprecated, so older videos using Tony Hawk may no longer describe the supported route.
Can a Winchester E use RGH or JTAG instead?
ConsoleMods excludes Winchester E consoles from JTAG and RGH. At 2.0.17559, Bad Update is the documented software option for that revision, subject to the live project requirements.
Do I need to solder?
No soldering or case opening is required for the documented Bad Update workflow. JTAG and RGH are different hardware methods and do require soldering and board-specific installation.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCan I use any USB stick?
A USB flash drive is required, but the project does not name a guaranteed brand, capacity, speed, or model. Follow the current README and avoid treating an untested drive as assured compatible.
Best Value
- 【16GB Flash Drive】USB flash drives with 16GB capacity, meet your needs of daily use on work, school, home and travelling for photos, music, videos, files storage and transfer. IMEASON thumb drives can be used to store different files, easy to data backup.
- 【Metal Swivel Cap Design】USB thumb drive is metal swivel cover provides extra protection for the usb thumbdrive connector, no usb drive cap to lose; keychain design makes it easier to carry without worrying lose it.
- 【Wide Compatibility】USB drive supports Windows 7/8/10/11 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, also Supports USB 2.0 and 1.1 ports. USB Stick support TV, desktop, notebook computer, car, audio and other device. The USB Memory Stick is your great data storage and transfer companion with traveling and working.
- 【Easy to use】usb memory stick is plug and play without any software installation. Just simply plug the Flashdrive into the port of your USB-compatible devices such as computer, laptop to start data storage or transmission.
- 【What You Get】16 GB USB Flash Drive Thumb Drive, The default format of the usb storage flash drive is FAT32.
Does Bad Update let me play copied commercial games?
The exploit’s documented purpose is enabling unsigned code and homebrew. It does not provide legal permission to copy, download, or distribute commercial games or other copyrighted material.
Bottom line
For an Xbox 360 on dashboard/kernel 17559, Bad Update is the documented software-only route to unsigned code and homebrew across Phat, S, and E revisions. It avoids soldering but is intentionally temporary: use the supported USB and game trigger, follow the current project README, and expect to run it again after every reboot. If you require an automatic, persistent modified startup, you are looking at a separate, hardware-dependent JTAG/RGH decision—not a setting that Bad Update can provide.
Frequently Asked Questions
Is Bad Update permanent?
No. It is non-persistent and must be triggered again after every reboot or shutdown.
What dashboard is required?
The documented target is dashboard/kernel 17559, also written as 2.0.17559.
Which Xbox 360 revisions are listed as compatible?
ConsoleMods lists Phat, S, and E revisions at 2.0.17559.
What trigger game does the project list?
The current README lists Rock Band Blitz and marks Tony Hawk’s American Wasteland as deprecated.
Does Bad Update require soldering?
No. It is software-only; JTAG and RGH are separate solder-based methods.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can Winchester E consoles use RGH or JTAG?
ConsoleMods excludes Winchester E consoles from both hardware methods.
What USB drive should I buy?
The project requires a USB flash drive but specifies no brand, capacity, speed, or guaranteed model.
Can this be used to copy commercial games?
No. Use it for lawful homebrew and preservation, and respect copyright and licensing.
The Bottom Line
Bad Update is the documented software-only Xbox 360 exploit for dashboard/kernel 17559. It supports Phat, S, and E revisions without soldering, but it is temporary: a USB drive and supported game trigger are required again after each reboot.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
