of the Pokémon series
Arbitrary code execution
0x1500 control code arbitrary code execution (Crystal) | Cart-swap arbitrary code execution | Generation I custom map script pointer | Generation I invalid meta-map scripts | Generation I item ("8F", "ws m", "-g m", "5かい", "てへ" etc.) | Generation I move ("-", "TM42") | Generation I Trainer escape glitch text boxes | Generation II bad clone | Generation II Burned Tower Silver | Japanese Crystal Pokémon Communication Center SRAM glitches | Coin Case glitch | Generation II glitch Pokédex sortings | Pikachu off-screen glitch ACE | OAM DMA hijacking | Pikachu glitch emote | Generation III glitch Pokémon summary | Generation III glitch move animation) | Remote code execution | TM/HMs outside of the TM/HM pocket | ZZAZZ glitch Trainer FC
No further extensions
Cloning | Item duplication glitch (Generation I) | Pokémon merge glitch ("Q Glitch", Generation I) | Time Capsule exploit | Bug-Catching Contest data copy glitch (Generation II, Japan only) | Berry glitch | Battle Tower Lati@s glitch (Generation III) | (Mimic) Transform Rage glitch (Generation IV)
Transform held item glitch (Generation IV, Japan only) | Mimic glitch (Generation IV, Japan only)
Buffer overflow techniques
99 item stack glitch | LOL glitch | Rival LOL glitch | Instant LOL glitch | RAM LOL glitch | Out of bounds LOL glitch | blockoobLG | Instant encounter infinite chain glitch | LGFly | Super Glitch (Generation I) | Party remaining HP glitch | Super Glitch (Generation III) | Text pointer manipulation mart buffer overflow glitch | CoolTrainer♀-type move | Double distort CoolTrainer♀ corruption | Yami Shop glitch | Party Pokémon box data shift glitch | Unterminated name glitch item instant encounter (Japanese Red/Green)
Item stack duplication glitch
Generation I expanded items pack (Glitch Rocket HQ maps, Map FE (English and non-English European Yellow) | Map script pointer manipulation (arbitrary code execution | Map script pointer item ball manipulation) | Text pointer manipulation (arbitrary code execution | Item ball manipulation | Mart buffer overflow) | Trainerless instant encounter glitch
Bad clone glitch
????? party overloading (Type 0xD0 move glitch | ????? map corruption | Celebi trick | Celebi Egg trick | Shiny Celebi trick | Glitch move map corruption | Overloaded party map corruption | Glitch Unown (Glitch Unown map corruption) | Duplicate key items glitch (Infinite items and item creation, Expanded Balls pocket (Wrong pocket TM/HMs, Glitch Pokédex categories))
Closed menu Select glitches
Dokokashira door glitch (International) | Fossil conversion glitch (international) | Second type glitch | Skip to Level 100 glitch | Trainer mutation glitch | Walk through walls (International) | Lift glitch | Badge describer glitch
Pomeg data corruption glitch ("Glitzer Popping") | Charm glitch
Broken escalator glitch (Japan only) | Elite Four door glitch (Japan only)
2x2 block encounter glitches
Left-facing shore tile glitch (in-game trade shore encounter trick, Old man trick, Trade link up shore encounter trick, Fight Safari Zone Pokémon trick) | Viridian Forest no encounter grass tiles glitch
Safari Zone exit glitch | RAM manipulation | Out of bounds Glitch City (Generation II) | Slowpoke Well out of bounds corruption (French Gold/Silver/Crystal)
Large storage box byte shift glitch
Storage box remaining HP glitch | Generation I max stat trick
Pikachu off-screen glitch
Trainer corruption glitch
Generation I save corruption | 255 Pokémon glitch | Expanded party encounter table manipulation (Generation I) | Send party Pokémon to a new game (Generation I) | Generation II save corruption | Mailbox glitches | Mystery Gift item corruption | Trainer House glitches
Trainer escape glitch
Death-warp | Ditto trick | Experience underflow glitch | Mew trick | Text box ID matching | Meta-map script activation
Walk through walls
Ledge method | Museum guy method | Rival's effect | Select glitch method (International Select glitch method), Brock Through Walls
Surf down glitch
Grass/rock Surfing glitch (Spanish/Italian only) (adaptions: Submerge glitch (international)) | 8 8 (0x7C) grass/rock surfing glitch (English Red/Blue))
(view, talk, edit)
The SRAM glitch, also known as Save corruption glitch and Save abuse glitch, is a glitch that allows the player to perform the send party Pokémon to a new game or 255 Pokémon glitch as soon as they are in their room.
Keep in mind when attempting this glitch, the timing is very precise (a handful of frames, ie less than a quarter of a second), so emulators and savestates are privileged.
The principle of the glitch is:
- Start a New game
- Play as much as you wish, without saving
- Begin to save the game
- At a very precise moment, power off/reset the console. The timing is version-dependent and is easier on Pokémon Yellow.
The cue is to power off/reset after the "Yes/No" dialog box has disappeared, but before the text changes to "Saving..."
Holding START+SELECT+A+B will not work, as the game prevents soft resets while it is saving.
In Pokémon Red and Blue, the window of opportunity is a few frames only, located right after the box disappears, making the glitch rely more on luck than on timing.
In Pokémon Yellow, there are more frames where the glitch will be successful, and the window is further away from the Yes/No box disappearing, making the glitch more viable on console.
The easiest glitch to perform is the 255 Pokémon glitch; you need to have no save file, then perform the SRAM glitch. If a save file exists (a Continue option exists), go to the title screen (not the where the Continue/New Game/Option menu is present) by pressing B if you are in the menu, hold Select and Down, and press B. The game will prompt you to erase the currently present save file. Accept, and perform the aforementioned steps.
The send party Pokémon to a new game glitch has the only difference that you have to start a new game while a save file from which you wish to import your Pokémon present. However, failing the glitch may render the file unattainable; if the save file is marked as "destroyed", the glitch still has a slight chance to work if attempted again.
If the glitch was successful, a Continue option will be present when the game is started again, and the player will be able to access their Pokémon screen. In the case of the 255 Pokémon glitch, the screen will look like it is blank.
There are two ways the glitch can fail: either when rebooting the game the message "the save file is destroyed!" will appear (the reset happened too early) which will remove the Continue option, or a Continue option will appear but the Pokémon screen cannot be accessed (the reset was too late). Attempting the glitch is still possible.