How to create your own sigpatches.

****************************************************************************************
:switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch:
Hello there, with all the fuss created by the DCMA plea of the N to iTotalJustice, I think this little compendium will help somebody.

For now the sigpatches for all firmware and Atmosphère can be downloaded from Sigpatches for Atmosphere (Hekate, fss0, fusee & package3) thread here on GBATemp :D

@mrdude is working on new set of programs running in Windows and will not need Python at all, keep an eye on his thread.
And @dogcsty is working on a Homebrew capable of generate the sigpatches on the console directly.
Booth applications are getting almost end-user maturity.

@mrdude release the Sigpatch IPS Creator, allowing to generate any new patches for any firmware and Atmosphère without need of updating the software.

For using the new Sigpatch IPS Creator you need:

  1. Download the latest version from github.
  2. Right click the recent downloaded file, and select properties:
    1661373682261.png
    , then unblock the file:
    1661373835973.png
    , this is a «security» measure of windows, marking down the downloaded files as insecure even if they are safe.
  3. Extract the file to a folder on your hard drive, by example c:\IPSCreator
    1662496908803.png
  1. At the first run of "IPS_Patch_Creator.exe " you may get a warning:
    1661374018518.png
    because is a «unrecognized app» meaning MrDude has not payed thousands of dollars to Microsoft for «authenticate» the app, so you should press «Run anyway» button to run the program. If you don't trust you can use a real antivirus (no defender) and check the file.
  2. At the first start of the program, you are welcomed with a few configurations:
    1661374242114.png
    By now you can choose the defaults and press «Save» button.
    This configurations are for future firmwares, more explanation on the post by MrDude. After press «Save» you are asked to save the config
    1661374387434.png
    press yes to commit the config to disk.
  1. The program require you to provide the encryption set of keys for the console. There are several ways to get them:
    1. using Lockpick_RCM, follow the guide:https://gbatemp.net/threads/how-to-get-switch-keys-for-hactool-xci-decrypting.506978/ OR https://nh-server.github.io/switch-guide/user_guide/emummc/making_emummc/
    2. Inside the program on the «Help» -> «Online Information», there are a set of cypher URLs one of them is very useful.
    3. Using web search.
  2. When you run the program without the needed keys, it prompts:
    1661377417544.png
    , if you press "yes" a KEYS.DAT file is created for you on the tools sub-folder, you can edit the file and put the values or use the KeyData tab to write the values of your PROD.KEYS file:
    1661377600726.png
You can use the tabs «Loader», «ES», «ES2», «FS» and «NFIM» to create the patches.
On each tab there is a button named «Make Patch», you can use the button to browse for the needed files or folder, also you can drag and drop to that button the files or folder from an explorer window.
On each you can generate a different set of patches:

Loader
On this tab you can generate the patches set for Atmosphère.
Loader Patch are Required for:
  • Running NRO Forwarders and Installed homebrews.
  • Running Installed XCI games.

Loader patch not required to:
  • Run (some) previously installed NSP. (if valid tickets exist)
  • Run non installed homebrew.
  • Install NSP/XCI - (but will not run these if a valid ticket does not exist).
In order to create the patches, you need to provide the path to fusee-secondary.bin or package3 file. Could be an official one or compiled by yourself.
Only Atmosphère 0.8.5 and newer are supported.
1662498674563.png

The generated patches are on the folder \atmosphere\kip_patches\loader_patches and the file \bootloader\patches.ini relative to the folder where IPS Patch Creator is run.

ES & ES2
ES patches stand for Eticket Services.
ES Patches are required to:
  • These are needed for run and install raw and untouched NSP files either dumped from Nintendo's CDN or someone's console.
  • ES patches are additionally needed to run pirated commercial NSPs.
ES Patches are NOT required to:
  • Run installed XCI
  • Run installed NRO forwarders.
  • Run homebrew
  • Install XCI files.
For creating the patches, you need to provide the path to the folder with the files of a firmware for console.
Works only for firmware 9.0.1 and above.

Both tabs generate the same sigpatches, using different algorithms, ES uses an algorithm what patches only on a spot, is traditionally know as «Alternate».
ES2 uses the original algorithm which patches on three different spots. Both of them works the same and is up to you which one to use, is more a manner of preference because they are equivalent.
1662500122439.png

The sigpatches are generated on the sub-folder \atmosphere\exefs_patches\es_patches\ where the IPS Patch Creator is run.

FS
FS is short for fs_nosigchk.
FS Patches required to:
  • Run installed XCI/NRO forwarders, and will give a corruption error when trying to run the installed XCI or NRO forwarder if no fs patches are applied or are wrong (you will also need to reinstall the game or nro forwarder if this happens).
  • The FS patches allow the usage of converted NSP files, such as homebrew on NSP files or converted XCI files.
  • FS patches are required to install/run NSP and XCI (without needing to convert the header) files.
Fs Patches not required to:
  • Run installed NSP files with valid tickets.
  • Run Homebrew
  • Install NSP/XCI - (with a valid header)
Only firmware 9.0.1 and above is supported.
1662500405307.png

The generated IPS files are on the sub-folder \atmosphere\kip_patches\fs_patches and the file \bootloader\patches.ini

NFIM
The NFIM patches, know as nfim_ctest, where «ctest» is short for Connection Test, are patches for skip the internet connection test, So you can play on a LAN without being online.
All current firmware versions are supported.
1662500667281.png

The patches are generated on the sub-folder \atmosphere\exefs_patches\nfim_ctest\

Once all the patches you want are generated, you can copy the folders atmosphere and bootloader to the root of your SD Card.

A very helpful feature is the possibility of upload the patches to your console using FTP, before you can use, you need to config the connection data:
1661379908766.png
,
1661379931932.png
,
1661379974097.png
once you put the correct IP address of your console and the user/password to connect you can push "save".

Then use the ftp feature to send the patches:
1662500827396.png
.



If you like to generate the patches directly on the console, @dogcsty is working on a Homebrew for that.

----To Do: add steps for the Homebrew ----


:switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch:
****************************************************************************************

With these new applications the use of the Old Python scripts is deprecated and useful only for historians :D

If you really want run the scripts you can use the
This steps help you to build a new version of sigpatches if new firmware or Atmosphère is released or if you compile Atmosphère from source and make changes like add a new bootlogo @binkinator explain us how to do that on https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-9839714

First at all thank you very much to @mrdude for his hard work, really to him belong all the credit.

On the thread Info on SHA-256 hashes on FS patches mrdude explain how the patches are created and share with all of us his work and his scripts to create new sigpatches.

For that scripts works you need Python, first step get python:

Download and install Python, for Windows you can use https://www.python.org/downloads/, but be sure of select the option «Add Python 3.XX to PATH».
1659196452425.png

After you have a Python environment working, open a command line (CMD.EXE) and execute the next commands, in order to get the prerequisites of the scripts:

Code:
python.exe -m pip install --upgrade pip
pip install bitstring

Download the latest version of the scripts on the thread (https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/post-9783677) for now they are on the post # 205.

Uncompress the file «AutoIPS-Patcher.zip» on a local folder, for example, «C:\AUTOIPS», must look like:
1659196724938.png


Then copy your prod.keys file to the folder «c:\AutoIPS\scripts\» and rename it «keys.dat» IMPORTANT IF YOU USE EXPLORER BE SURE THE EXTENSIONS AREN'T HIDDEN, SO YOU DON'T END WITH keys.dat.keys file instead of keys.dat

Tip from @User154 ,
you can get your prod.keys files using Lockpick_RCM, follow the guide: https://nh-server.github.io/switch-guide/user_guide/emummc/making_emummc/

Get the files for the firmware you want to create, darthsternie it's you pal, or you can use NXDumpTool, TegraExplorer or GoldLeaf to dump the current firmware to the SD Card on your console. Extract all files to a local path, by example, «C:\FW1412», your folder must look like:
1659197200014.png

Download the latest Atmosphère files from https://github.com/Atmosphere-NX/Atmosphere/releases , and extract «atmosphere\package3» to a local path, by example: «C:\ATM132».

On a command line go to the folder where you extract AutoIPS and execute the command «Python MENU.PY»:

Bash:
C:\AutoIPS>python menu.py
=========================================================================
Make sure you have keys.dat in the scripts folder. Menu/Scripts by MrDude
=========================================================================
1.Make Atmosphere-NX Loader Patch
2.Make ES Patch and FS Patches
3.Make ES Patch
4.Make Alt Beta ES Patch
5.Make ES NFIM Patch
6.Make FS Patches
7.Toggle Debug info
8.NCA info
9.Exit/Quit

What would you like to do?

I recommend to select the option «7» in order to enable information on screen.

Then you can select the option «1» to generate sigpatches for Atmosphère, when asked for the «fusee-secondary.bin or package3» files, write down the path where Atmosphère was extracted, on this example: «c:\ATM132\package3».

You can use the option «2» to generate sigpatches for the firmware, when asked for the firmware path, use the one where you extract firmware files, on this example: «C:\FW1412».

Tip from @masagrator, also you can drag from a File Explorer window the folder of firmware and the package3 file to the command line window, then the full path is written for you on the command line, avoiding typos.
record_1.png

For Windows 10 and Windows 11 this ONLY works if you start the CMD as normal user, if your CMD.EXE was started as Administrator, do not work because explorer ALWAYS run as standard user and a standard user window can not send data to a Administrator one.

Tip from @subcon959 : if you put package3 in the scripts folder and then put the firmware files in a folder called firmware and put that in the scripts folder too, then you can just press enter when the menu asks for them instead of dragging or typing anything.
W09lAnk.jpg
TESTED AND WORKS LIKE A CHARM!


The next examples shows the result of the executions:
1659197808475.png



1659197914104.png


If everything goes well you end with the folder «c:\AutoIPS\scripts\output» inside that folder should be a folder named «Atmosphere» that folder should be copied to the root of your SD card; and a file called «patches.ini» which goes to the «SD:/BOOTLOADER» path of your SD Card.

Its possible to see a bunch of Warnings «[WARN]» about to match key, some like:
1659317316418.png

are WARNINGS and you need no to worry about that, it's just you have more keys on the Keys.dat file than needed so ignore them.

If you get errors, verify the location of the «KEYS.DAT» file and the path you give for the Atmosphère files and firmware folder. DO NOT ADD EMPTY SPACES AT END OF THE PATHS.

-Edit 1:-
Correcting a typo and adding suggestions from other users; the great of this community!
And trying to be sure the credit goes to @mrdude him is the one what make the hard work and investigation.

-Edit 2-
add a video of dragging names and UAC restriction. and the good news from MrDude.

-Edit 3-
Adding new homebrew app.

-Edit 4-
Creating steps for the new App., To do: steps for console homebrew.
 

Attachments

  • 1661377712209.png
    1661377712209.png
    36.2 KB · Views: 188
  • 1661380064400.png
    1661380064400.png
    27 KB · Views: 181
  • 1661380748979.png
    1661380748979.png
    12.6 KB · Views: 204
Last edited by impeeza,

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
6,511
Trophies
2
XP
6,152
Country
United States
Man this guide is frustrating. I dropped the contents of my `prod.keys` into the KeyData tab of IPS and hit "Write Keys" which saved this in `tools/keys.dat`. I then went to darthsternie's website and downloaded Firmware 14.1.2. I extracted the zipped content into a directory. Then back in IPS I went to the ES2 (and tried this on the ES) tab, and hit Make Patch and specified where I had extracted the firmware data to. It then popped up with a couple of error dialogue boxes and ultimately generated this:

Code:
Possible nca files to check between 410000 bytes and 500000 bytes: 6

0450e376470f98b8a8a065787cfa410a.nca
43772e89bbf8147fef94a4e8d81f4810.nca
54483bde4be6587b769ee26be53dd81a.nca
57bbb7896fc1e2ac7dbaee9ae689a8b3.nca
723d50550863bd4fa1474ff1dac32dba.nca
97b4de164997b6713f93e6adde8071df.nca

Files to process: 6
Files to process: 5
Files to process: 4
Files to process: 3
Files to process: 2
Files to process: 1
ES title found in 97b4de164997b6713f93e6adde8071df.nca (472064 bytes)
Skipped: 0 files

SDKVersion:14.3.0.0

Trying to extract main from 97b4de164997b6713f93e6adde8071df.nca

Trying to get the Build ID for the ips patch
Searching for ES2 ips patches

main_dec was not found, unable to search for patches :-(

Missing es patch directories created
Couldn't find patch offsets so ES2 ips patch was not written

Finished - time taken: 6.987 seconds

What happened? I don't see anything that I messed up on, interpreted incorrectly, followed improperly, etc.

I just went through it all on a fresh machine with my other brain cell tied behind my back. No issues.

They work on my Switch as well.

Mine grabbed the exact same .nca as yours. Same file size too:

ES title found in 97b4de164997b6713f93e6adde8071df.nca (472064 bytes)

Possible nca files to check between 410000 bytes and 500000 bytes: 6

0450e376470f98b8a8a065787cfa410a.nca
43772e89bbf8147fef94a4e8d81f4810.nca
54483bde4be6587b769ee26be53dd81a.nca
57bbb7896fc1e2ac7dbaee9ae689a8b3.nca
723d50550863bd4fa1474ff1dac32dba.nca
97b4de164997b6713f93e6adde8071df.nca

Files to process: 6
Files to process: 5
Files to process: 4
Files to process: 3
Files to process: 2
Files to process: 1
ES title found in 97b4de164997b6713f93e6adde8071df.nca (472064 bytes)
Skipped: 0 files

SDKVersion:14.3.0.0

Trying to extract main from 97b4de164997b6713f93e6adde8071df.nca
Nca main extracted - trying to decrypt it now....

Decryption complete, uneeded file removed: main
Uneeded file removed: main.npdm

Trying to get the Build ID for the ips patch
Build ID: 621351EB04199CF0B7A899896C451F2FD1B7A1CE

Searching for ES2 ips patches

Wildcard search pattern3 found at offset: 0x00066398
Possible patch3 offset location: 0x00066394
Wildcard search pattern2 found at offset: 0x00066D44
Possible patch2 offset location: 0x00066D40
Wildcard search pattern1 found at offset: 0x00066364
Possible patch1 offset location: 0x00066360

Patch 1 = 0x09000014 will be written to the ips file
Patch 2 = 0x1F2003D5 will be written to the ips file
Patch 3 = 0x08000014 will be written to the ips file

ES2 ips patch written

Decrypted file removed: main_dec

Finished - time taken: 3.672 seconds

Might try downloading the firmware again?

Are you certain your prod.keys are up to date?

I used the _0d keys...

e: maybe you have an old copy of hactool.exe in your PATH? Just thinking out loud of what else it could be.
 
Last edited by binkinator,

ghostbitxd

Well-Known Member
Newcomer
Joined
May 1, 2020
Messages
78
Trophies
0
Age
40
XP
195
Country
United States
I just went through it all on a fresh machine with my other brain cell tied behind my back. No issues.

They work on my Switch as well.

Mine grabbed the exact same .nca as yours. Same file size too:

ES title found in 97b4de164997b6713f93e6adde8071df.nca (472064 bytes)

Possible nca files to check between 410000 bytes and 500000 bytes: 6

0450e376470f98b8a8a065787cfa410a.nca
43772e89bbf8147fef94a4e8d81f4810.nca
54483bde4be6587b769ee26be53dd81a.nca
57bbb7896fc1e2ac7dbaee9ae689a8b3.nca
723d50550863bd4fa1474ff1dac32dba.nca
97b4de164997b6713f93e6adde8071df.nca

Files to process: 6
Files to process: 5
Files to process: 4
Files to process: 3
Files to process: 2
Files to process: 1
ES title found in 97b4de164997b6713f93e6adde8071df.nca (472064 bytes)
Skipped: 0 files

SDKVersion:14.3.0.0

Trying to extract main from 97b4de164997b6713f93e6adde8071df.nca
Nca main extracted - trying to decrypt it now....

Decryption complete, uneeded file removed: main
Uneeded file removed: main.npdm

Trying to get the Build ID for the ips patch
Build ID: 621351EB04199CF0B7A899896C451F2FD1B7A1CE

Searching for ES2 ips patches

Wildcard search pattern3 found at offset: 0x00066398
Possible patch3 offset location: 0x00066394
Wildcard search pattern2 found at offset: 0x00066D44
Possible patch2 offset location: 0x00066D40
Wildcard search pattern1 found at offset: 0x00066364
Possible patch1 offset location: 0x00066360

Patch 1 = 0x09000014 will be written to the ips file
Patch 2 = 0x1F2003D5 will be written to the ips file
Patch 3 = 0x08000014 will be written to the ips file

ES2 ips patch written

Decrypted file removed: main_dec

Finished - time taken: 3.672 seconds

Might try downloading the firmware again?

Are you certain your prod.keys are up to date?

I used the _0d keys...

e: maybe you have an old copy of hactool.exe in your PATH? Just thinking out loud of what else it could be.

I downloaded the firmware and compared the checksum to the one listed on the site, and it matches.

You mention prod.keys being "up to date". The prod.keys I'm using are the ones I originally dumped when I initially modded my Switch. I assumed that those keys would always be the same and would never change - maybe that's what is messing me up? I guess I'll redump them and try again.

I'm not sure what you mean when you say `0d` keys. I basically just took my entire prod.keys and put it in IPS' keys.dat.

Either way, let me redump the prod.keys and try and report back.
 

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,076
Trophies
1
Age
56
XP
8,219
I downloaded the firmware and compared the checksum to the one listed on the site, and it matches.

You mention prod.keys being "up to date". The prod.keys I'm using are the ones I originally dumped when I initially modded my Switch. I assumed that those keys would always be the same and would never change - maybe that's what is messing me up? I guess I'll redump them and try again.

I'm not sure what you mean when you say `0d` keys. I basically just took my entire prod.keys and put it in IPS' keys.dat.

Either way, let me redump the prod.keys and try and report back.
You're not supposed to use your prod.keys, you're supposed to fill in the template that's provided by the program.
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
6,511
Trophies
2
XP
6,152
Country
United States
I downloaded the firmware and compared the checksum to the one listed on the site, and it matches.

You mention prod.keys being "up to date". The prod.keys I'm using are the ones I originally dumped when I initially modded my Switch. I assumed that those keys would always be the same and would never change - maybe that's what is messing me up? I guess I'll redump them and try again.

I'm not sure what you mean when you say `0d` keys. I basically just took my entire prod.keys and put it in IPS' keys.dat.

Either way, let me redump the prod.keys and try and report back.

If you look at the keys template you will see the progression from _00 to _0d

aes_kek_generation_source =
aes_key_generation_source =
header_key =
key_area_key_application_00 =
key_area_key_application_01 =
key_area_key_application_02 =
key_area_key_application_03 =
key_area_key_application_04 =
key_area_key_application_05 =
key_area_key_application_06 =
key_area_key_application_07 =
key_area_key_application_08 =
key_area_key_application_09 =
key_area_key_application_0a =
key_area_key_application_0b =
key_area_key_application_0c =
key_area_key_application_0d =
package1_key_00 =
package1_key_01 =
package1_key_02 =
package1_key_03 =
package1_key_04 =
package1_key_05 =
package2_key_00 =
package2_key_01 =
package2_key_02 =
package2_key_03 =
package2_key_04 =
package2_key_05 =
package2_key_06 =
package2_key_07 =
package2_key_08 =
package2_key_09 =
package2_key_0a =
package2_key_0b =
package2_key_0c =
package2_key_0d =

New keys are added during a major firmware release. If you're using an older version of prod.keys to get your values...you will not be able to decrypt newer versions of firmware.

You're not supposed to use your prod.keys, you're supposed to fill in the template that's provided by the program.

Hactool won't care...you can over-feed it values...it will just complain and move on. I just dumped my entire prod.keys content inside and let'er rip. Works a treat!
 
  • Like
Reactions: impeeza

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,076
Trophies
1
Age
56
XP
8,219
Hactool won't care...you can over-feed it values...it will just complain and move on. I just dumped my entire prod.keys content inside and let'er rip. Works a treat!
Since I made the program and modded hactool (for use in this tool) I kind of know what I am talking about. When you use prod.keys it takes far longer as it tries each key to decrypt. When you use the template it's far faster for extraction because there's less keys to check through.

If you don't believe me - try using prod.keys for the template and check the time it takes. Now just use the keys in the template and check the time it takes - you'll see a vast difference.
 
  • Like
Reactions: impeeza

ghostbitxd

Well-Known Member
Newcomer
Joined
May 1, 2020
Messages
78
Trophies
0
Age
40
XP
195
Country
United States
If you look at the keys template you will see the progression from _00 to _0d

aes_kek_generation_source =
aes_key_generation_source =
header_key =
--snip--
key_area_key_application_0d =
package1_key_00 =
--snip--
package2_key_0d =

New keys are added during a major firmware release. If you're using an older version of prod.keys to get your values...you will not be able to decrypt newer versions of firmware.

That definitely looks like my issue. I don't even have any 0d keys. Thanks for clarifying, and again, when I get a chance to redump my keys then I'll report back and see if it works fine.

Since I made the program and modded hactool (for use in this tool) I kind of know what I am talking about. When you use prod.keys it takes far longer as it tries each key to decrypt. When you use the template it's far faster for extraction because there's less keys to check through.

If you don't believe me - try using prod.keys for the template and check the time it takes. Now just use the keys in the template and check the time it takes - you'll see a vast difference.

Thanks for making the tool! I think bink was simply saying that dumping the contents of prod.keys in there works - which it seems as though it does, it just takes longer.
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
6,511
Trophies
2
XP
6,152
Country
United States
Since I made the program and modded hactool (for use in this tool) I kind of know what I am talking about. When you use prod.keys it takes far longer as it tries each key to decrypt. When you use the template it's far faster for extraction because there's less keys to check through.

If you don't believe me - try using prod.keys for the template and check the time it takes. Now just use the keys in the template and check the time it takes - you'll see a vast difference.

I believe you. Just saying that wouldn’t be the cause of this error. It would still work… ✌️
 

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,076
Trophies
1
Age
56
XP
8,219
Just reporting back. After upgrading my switch to the latest FW, and then dumping prod.keys, the IPS tool was able to generate the patches without issue. Thanks @binkinator
You could have saved yourself a lot of time if only you'd actually clicked on the help/online information tab!

tc1eEHr.png
 

pofehof

Well-Known Member
Member
Joined
Oct 23, 2019
Messages
169
Trophies
0
Age
33
XP
355
Country
United States
The scripts and stuff needs to be updated for the new keys introduced in 15.0
That explains why it isn't working for me. I keep on getting can't find "FS.kip1-fat.dec' or 'main_dec was not found' errors. Guess we need to wait for Lockpick to update.
 

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,076
Trophies
1
Age
56
XP
8,219
That explains why it isn't working for me. I keep on getting can't find "FS.kip1-fat.dec' or 'main_dec was not found' errors. Guess we need to wait for Lockpick to update.
You need to update your keys with key 0E so you can decrypt the files, also I need to update the program and I'll get around to it when I get around to it. PS there's already patches released.
 
Last edited by mrdude,
  • Like
Reactions: peteruk and pofehof

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
279
Trophies
1
Age
46
XP
1,185
Country
Netherlands
You need to update your keys with key 0E so you can decrypt the files, also I need to update the program and I'll get around to it when I get around to it. PS there's already patches released.
They actualy updated them just now again since it was missing the nfim patch.
 
  • Like
Reactions: binkinator

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • BakerMan
    The snack that smiles back, Ballsack!
  • Veho @ Veho:
    I thought it was an actual xBox at that price.
  • Sicklyboy @ Sicklyboy:
    I wanna grab a 360 Slim and a 360 E one of these days. Missed the boat of getting them at their lowest though, once they were discontinued. Could've got them for cheap back when I was a broke 20 something working at Target, but then again, I was a broke 20 something working at Target
  • Veho @ Veho:
    Being broke is no fun.
  • K3Nv2 @ K3Nv2:
    @Sicklyboy, $150 isn't that bad for a jtag slim on ebay
  • Veho @ Veho:
    I only wish it was actually playable.
  • Veho @ Veho:
    There's a guy on the Tube of You that makes playable mechanical arcade games out of Lego. This could work on the same principle.
  • Veho @ Veho:
    Just a couple of guys taking their manatee out for some fresh air, why you have to molest them?
  • Veho @ Veho:
    Stupid Chinese shop switched their shipping company and this one is slooooooow.
  • LeoTCK @ LeoTCK:
    STOP BUYING CHINESE CRAP THEN
  • LeoTCK @ LeoTCK:
    SUPPORT LOCAL PRODUCTS, MAKE REVOLUTION
  • LeoTCK @ LeoTCK:
    THEY KEEP REMOVING LOCAL SHIt AND REPLACING WItH INFERIOR CHINESE CRAP
  • LeoTCK @ LeoTCK:
    THATS WHY MY PARTNER CANT GET A GOOTWEAR HIS SIZE ANYMORE
  • LeoTCK @ LeoTCK:
    HE HAS BIG FOOT AND BIG DUCK
  • LeoTCK @ LeoTCK:
    d*ck i mean*
  • LeoTCK @ LeoTCK:
    lol
  • Veho @ Veho:
    Mkay.
  • Veho @ Veho:
    I just ordered another package from China just to spite you.
  • SylverReZ @ SylverReZ:
    Communism lol
  • SylverReZ @ SylverReZ:
    OUR products
  • The Real Jdbye @ The Real Jdbye:
    @LeoTCK actually good quality products are dying out because they can't compete with dropshipped chinese crap
    +1
  • BakerMan @ BakerMan:
    @LeoTCK is your partner/bf the sascrotch or smth?
    BakerMan @ BakerMan: @LeoTCK is your partner/bf the sascrotch or smth?