Main Menu





Search Wiki


Pomeg glitch
 Page | Discussion | View source | History

From Glitch City Laboratories

Revision as of 10:58, 15 August 2010 by Torchickens (talk | contribs)
Jump to: navigation, search
Major glitches of the Pokémon series

GB.png Arbitrary code execution GB.png

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

Bulbasaur.png No further extensions Bulbasaur.png

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)

Bruno.png Buffer overflow techniques Bruno.png

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)

Ball.png Item stack duplication glitch (Generation I) Ball.png

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

PC.png Bad clone glitch (Generation II) PC.png

????? 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))

Lab pass.png Closed menu Select glitches (Japanese Red/Green) Lab pass.png

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

Gromeg berry.png Pomeg glitch (Generation III) Gromeg berry.png

Pomeg data corruption glitch ("Glitzer Popping") | Charm glitch

Darkrai.png Voiding (Generation IV) Darkrai.png


Broken escalator glitch (Japan only) | Elite Four door glitch (Japan only)

Lying old man.png 2x2 block encounter glitches (Generation I) Lying old man.png

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

Glitchtile.png Glitch City Glitchtile.png

Safari Zone exit glitch | RAM manipulation | Out of bounds Glitch City (Generation II) | Slowpoke Well out of bounds corruption (French Gold/Silver/Crystal)

RBYPC.png Large storage box byte shift glitch RBYPC.png

Storage box remaining HP glitch | Generation I max stat trick

Pikachu.png Pikachu off-screen glitch Pikachu.png

Trainer corruption glitch

Tereka.png SRAM glitches Tereka.png

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

Ditto.png Trainer escape glitch Ditto.png

Death-warp | Ditto trick | Experience underflow glitch | Mew trick | Text box ID matching | Meta-map script activation

Brock.png Walk through walls Brock.png

Ledge method | Museum guy method | Rival's effect | Select glitch method (International Select glitch method), Brock Through Walls

Surf.png Surf down glitch Surf.png

Grass/rock Surfing glitch (Spanish/Italian only) (adaptions: Submerge glitch (international)) | 8 8 (0x7C) grass/rock surfing glitch (English Red/Blue))

(view, talk, edit)
This article is incomplete. Please feel free to add any missing information about the subject. It is missing: {{{1}}}.

The Pomeg glitch or Pomeg Berry glitch is an oversight regarding the Pomeg Berry's ability of lowering HP EVs, such that if the player uses a Pomeg Berry at a relatively low amount of HP, there is a possibility that the relevant Pokémon's hitpoints will drop below zero and roll down from (2^16)-1 or 65535 HP due to hitpoints being a signed, two byte integer.

The consequences of the glitch vary between the game which it was exploited on, although the ability for the player to reduce a Pokémon's HP to essentially 'negative HP' via a Pomeg Berry has not been amended and if at all at least since the release of Pokémon HeartGold and SoulSilver.


  1. A Pomeg berry; ideally several of them.
  2. A Pokémon with at least 10 HP EVs
  3. A Pokémon with a relatively low amount of HP; this will depend on the level of the Pokémon, and can be a higher value if the Pokémon has more than 110 HP EVs.


  1. Obtain a Pokémon with a relatively low amount of HP and at least 10 HP effort values.
  2. Use a Pomeg Berry such that the amount of HP that the Pokémon has drops below -1 (65535) or lower.


Once a Pokémon receives an abnormal amount of HP, the glitch can be exploited to abuse many other oversights in the game engine, or "sub-glitches".

Pokémon Ruby and Sapphire

Using a recovery item

Only within Pokémon Ruby and Sapphire, if the player uses a recovery item on any Pokémon with essentially 'negative HP', if the recovery item would roll the Pokémon's HP back to zero, instead of the game keeping the Pokémon's HP at zero it will instead set the Pokémon's HP to its natural maximum.

Pokémon Emerald

Battling with an Egg

In Pokémon Emerald, the Pomeg glitch is often exploited to allow unhatched Eggs to battle and is perhaps one of the most well known examples of Pomeg Berry "sub-glitches". To perform this trick, the player should only have an Egg in his or her party and another Pokémon with a relatively low amount of HP (which the Pomeg Berry will be used on). The player must then use the Pomeg Berry such that its HP depletes below -1 (65535) and use any healing item such as a Potion. Regardless of the value, as long as the recovery item would in theory increase the Pokémon's HP to at least zero, the Pokémon's HP will then stay at zero.

The player cannot simply use the Pomeg Berry to deplete the Pokémon's HP to zero from a valid amount of HP as this will activate a black out; hence the Pokémon's HP must be depleted to at least -1 (65535) first. By switching the Egg as the first 'Pokémon' in the party, and entering a battle, the Pokémon inside the egg will battle (with an egg-colored sprite), and can gain experience points in this way. The Pokémon inside of the Egg is capable of leveling up, hence it is possible to hatch an Egg into a Pokémon in a secondary or final evolutionary stage. An Egg will count as a 'fainted Pokémon' if the Pokémon inside of the Egg faints in battle and the player wins.

Partially sending out an opponent's Pokémon

(Reported by Hall of Origin forums)

A phenomenon unique to Pokémon Emerald's game engine allows the player to send out an opponent's Pokémon. To perform this trick, the player should only have two Pokémon in his or her party; one which is fainted and another with a relatively low amount of HP to take advantage of the Pomeg glitch. If the player exploits the Pomeg glitch to deplete the Pokémon's HP to at least -1 (65535) and uses a recovery item to increase it back to zero (once reaching zero, the item will not recover any more health) the player will not black out and gains the ability of entering a battle for one turn before blacking out again.

By entering a trainer battle and using a Revive on the second Pokémon however, for reasons unclear after the first Pokémon falls the game will act as if the trainer is going to switch Pokémon. If the player attempts to switch a Pokémon but then cancels, he or she will send out a Pokémon with the defined species data, as stored in the game's RAM of the next opponent's Pokémon. The Pokémon is not identical, for example the Pokémon's type is often different.

Unlimited damage

(Reported by Hall of Origin forums)

Backsprite palette swapping

(Reported by Hall of Origin forums)

Sending out a "?"

(Reported by Hall of Origin forums)

Draining move problem

(Reported by Hall of Origin forums)

Recovering a Pokémon with 'negative HP' in battle

Pokémon FireRed and LeafGreen

Sending out a "óË {é Áî"

Reported by VaeporSage

Verified by VaeporSage


óË {é Áî is an unexplained phenomenon similar to B óË Án.

óË {é Áî will be 'sent out' by the player if he or she trades a Pokémon with an amount of HP between -32767 (32768) and -1 (65535) HP, acquired from the Pomeg glitch in another version to Pokémon FireRed or Pokémon LeafGreen. If the player heals the Pokémon such that it rises and stops at zero HP; the steps from the "sending out an opponent's Pokémon" sub-glitch in Pokémon Emerald presumably become possible, although the end result is different. If these steps are performed by the player, he or she will send out an invalid Pokémon with an unknown identifier, with the name "óË {é Áî", associated with a never ending battle animation of Conversion.

Status screen errors

If a Pokémon with "negative HP" is traded to Pokémon FireRed and LeafGreen from another version, the status screen becomes unstable when the information regarding that Pokémon is stored into the game RAM. If the status of the relevant Pokémon is viewed and the player switches to another Pokémon, the game will often freeze, this might suggest that in FireRed and LeafGreen, the pointers used in the status screen for an amount of HP too large will not hold the amount of HP on the status screen for a previous Pokémon but rather change the value of another unrelated byte, causing instability.

Reported by VaeporSage

Verified by VaeporSage

Pokémon Colosseum

Pokémon XD: Gale of Darkness

Pokémon Diamond and Pearl

Sending out a placeholder of identifier 000

Reported by VaeporSage

Verified by Various

Pokémon Battle Revolution


  1. Shedinja cannot be used to exploit the Pomeg glitch regardless of its effort value in hitpoints because its HP will always remain at 1.
  2. If the Pokémon receiving 'negative HP' knows or learns the move Softboiled, it can be used to restore the hitpoints of many Pokémon, without the need of large amounts of recovery items.

External links

  1. [1] Hall of Origin's article on the Pomeg glitch.