Ir a contenido


No te pierdas nada a la vez que nos apoyas desde las redes sociales.

Últimos comentarios

Información del archivo

  • Añadido el: Apr 02 2010 13:46
  • Actualizado el: Dec 03 2011 12:18
  • Tamaño: 304.53K
  • Visitas: 4043
  • Descargas: 723

Descargar XNand Healer GUI 0.71

Captura de pantalla

1. Copy XNandHealer.exe to a folder of choice e.g. C:\Nandpro

2. Requires .Net Framework 3.5

3. Requires Nandpro + associated drivers (best results with 2.0b, not tested with 3.0)

4. Extract MultiBuilder to a folder of choice e.g. C:\Nandpro\MultiBuilder
   Download from one of these locations:
Version 0.2:
Version 0.3:

  NOTE: Multi builder (run.exe) is not used/invoked by XNH. It is required as a convenient
        package containing all files necessary to run ggBuild.

5. (Optional) Requires FindSecData 0.62 by boby2pc for Uncrippling

Initial setup

1. Run XNandHealer GUI.
2. Under Settings, confirm the locations of Nandpro.exe, python.exe & ggBuild.exe
   (both in ~MultiBuilder\Data\ folder) and optionally FindSecData.exe
3. On the Read Tab, Select the Working directory where your NAND images, logs and fuses will go

Instructions for correct NAND dumping

1. Select the desired interface (LPT or USB) and click Detect
2. Under the Read Tab: Click "Read Selected...", choose which "read slots" you want and
   click OK to begin. For big block Jaspers, you may only want to read the first 64MB rather
   than the full image. You can use the default filenames or rename them first.
3. Once all reads are complete, Observe the integrity icon against each dumped image.
   GREEN TICK = Good dump, no errors or remapped blocks
   EXCLAMATION = Good dump, but contains bad blocks. Only attempt to fix if you're not getting exact matching dumps.
   RED CROSS = Contains ECC error blocks i.e. read errors. Click "Fix Selected..." to re-dump the offending blocks.
4. Select and fix image if there are any errors

Instructions for Glitch Hack (once glitching hardware is installed)

1. Connect NAND programmer and dump the NAND as per NAND dumping instructions
2. Under Build XeLL Reloaded Tab, select a previously dumped NAND image and click "Build XeLL"
3. Click "Write XeLL To NAND" and let it complete
4. Remove NAND programmer, connect ethernet cable to console and boot console from eject button (take
   note of assigned IP)
5. Enter assigned IP address in the box (e.g. and click "Get CPU Key from IP".
   "fuses.txt" will be created in the working directory.
6. Under "Build Glitch Image" Tab, select a dumped NAND image and click "Build Glicth Image"
   (IMPORTANT! For jaspers, make sure that the Model Type is correct)
7. Reconnect NAND programmer and click "Write Glitch Image To NAND" and let it complete.
   (No need to remap any bad blocks, ggBuild will have already done it)
8. Remove NAND programmer, and enjoy your glitch-hacked console.

NOTE: Currently, dashlaunch patches will be applied by default. Advanced options will come in a
      later revision.

Instructions to Uncripple

1. Under Write Tab: Select a NAND image file and click FindSecData. A list of recommended
   patches will be displayed.
2. Select the first in the list and click Write NAND, and you're done!
   In some cases you may need to keep going through the list of patches until it works.


* The fastest most convenient and most reliable way to ensure correct image dumps
* Automated creation and flashing of XeLL Reloaded and ggBuild image
* Able to detect and fix any errors in a NAND dump, making this an excellent aid to JTAG'ing / RGH'ing
* Automatically remap bad blocks - e.g. remap your freeBOOT image to match the original
* Supports all NAND types, small block and big block
* Tell at a glance if your console has an expolitable "CB" for JTAGging
* Provides automated process to uncripple using the existing excellent
   tools: Nandpro and FindSecData
* Recognises and supports uncrippling for all NAND types 16MB, 256MB, 512MB
* Automatically shows if NANDs are identical at a glance as soon as they're dumped
* Previews the exact write commands to be used before writing
   (Nothing is written back to the NAND without the user seeing the commands first)
* Easily manage folders containing lots of NAND dumps if you're handling multiple


* Block numbers of Big Block NANDs are shown in blue to distinguish them from blocks numbers
   of small block NANDs. I did this because Nandpro always deals in small block sizes, even when
   reading and writing big block images. Therefore, if you plan to use Nandpro natively based on
   any block numbers read out from XNH, then make sure to multiply big block values (shown in blue)
   by 8 before plugging them into Nandpro

* Sometimes Nandpro 2.0d and 2.0e will refuse to read a virtual nand file. I don't
   know why it reads some and not others but the only solution I've found that works is to use 2.0b

Novedades de la versión 0.71 (Ver lista de cambios completa)

  • - Fixed the problem of not building XeLL if there was a space in the Working Directory pathname
  • - Carry out the glitch hack from start to finish using one application!
  • - Creation of image_00000000.ecc (XeLL) for Glitch Hack based on original nand dump
  • - Creation of full Glitch Hack image (using ggBuild) for all model types
  • - One-click CPU key retreival from XeLL over LAN (and creation of fuses.txt)
  • - One-click CPU key retreival from fuses.txt file
  • - Added support for trinity NAND image analysis

comments powered by Disqus