RIFF JTAG – Samsung GT-P3113 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

21.02.2013  RIFF JTAG – Samsung GT-P3113 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

Samsung P3113 is based on the OMAP4430 Processor (Cortex-A9 Dual-Core). JTAG pads are very small; professional experience in soldering is required to connect wires to the JTAG interface.
Please note: The initial loader in the Samsung P3113 is XLOADER. Due to OMAP4430’s some peculiar TrustZone security features current resurrector will boot only in case XLOADER is alive. That’s why model name of current resurrector has additional text: ‘XLoader+’. In case XLOADER is damaged (which happens for example after wrong firmware reflash), you will have to use different resurrector DLL – the one with the ‘XLoader-” delimiter.

To resurrect Samsung P3113:

  •  Solder JTAG cable to Samsung P3113 JTAG pads;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung P3113 is selected in the list of models;
  •  Make sure a fixed TCK frequency is selected;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Volume Down’ key and press Power-On.

samsung_galaxy_tab_2_70_2

RIFF JTAG – Samsung GT-P3110 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

21.02.2013   RIFF JTAG – Samsung GT-P3110 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

Samsung P3110 is based on the OMAP4430 Processor (Cortex-A9 Dual-Core). JTAG pads are very small; professional experience in soldering is required to connect wires to the JTAG interface.
Please note: The initial loader in the Samsung P3110 is XLOADER. Due to OMAP4430’s some peculiar TrustZone security features current resurrector will boot only in case XLOADER is alive. That’s why model name of current resurrector has additional text: ‘XLoader+’. In case XLOADER is damaged (which happens for example after wrong firmware reflash), you will have to use different resurrector DLL – the one with the ‘XLoader-” delimiter.

To resurrect Samsung P3110:

  •  Solder JTAG cable to Samsung P3110 JTAG pads;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung P3110 is selected in the list of models;
  •  Make sure a fixed TCK frequency is selected;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Volume Down’ key and press Power-On.

.
samsung_galaxy_tab_2_70_2

RIFF JTAG – Samsung GT-P3100 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

21.02.2013  RIFF JTAG – Samsung GT-P3100 Galaxy Tab 2 7.0 Unbrick – Dead boot repair supported

Samsung P3100 is based on the OMAP4430 Processor (Cortex-A9 Dual-Core). JTAG pads are very small; professional experience in soldering is required to connect wires to the JTAG interface.
Please note: The initial loader in the Samsung P3100 is XLOADER. Due to OMAP4430’s some peculiar TrustZone security features current resurrector will boot only in case XLOADER is alive. That’s why model name of current resurrector has additional text: ‘XLoader+’. In case XLOADER is damaged (which happens for example after wrong firmware reflash), you will have to use different resurrector DLL – the one with the ‘XLoader-” delimiter.

To resurrect Samsung P3100:

  •  Solder JTAG cable to Samsung P3100 JTAG pads;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung P3100 is selected in the list of models;
  •  Make sure a fixed TCK frequency is selected;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Volume Down’ key and press Power-On.

.
samsung_galaxy_tab_2_70

RIFF JTAG – Samsung GT-P5100 Galaxy Tab 2 10.1 Unbrick – Dead Boot repair supported

26.01.2013   RIFF JTAG – Samsung GT-P5100 Galaxy Tab 2 10.1 Unbrick – Dead Boot repair supported

Samsung P5100 is based on the OMAP4430 Processor (Cortex-A9 Dual-Core). JTAG pads are very small; professional experience in soldering is required to connect wires to the JTAG interface.
Please note: The initial loader in the Samsung P5100 is XLOADER. Due to OMAP4430’s some peculiar TrustZone security features current resurrector will boot only in case XLOADER is alive. That’s why model name of current resurrector has additional text: ‘XLoader+’. In case XLOADER is damaged (which happens for example after wrong firmware reflash), you will have to use different resurrector DLL – the one with the ‘XLoader-” delimiter.

To resurrect Samsung P5100:

  •  Solder JTAG cable to Samsung P5100 JTAG pads;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung P5100 is selected in the list of models;
  •  Make sure a fixed TCK frequency is selected;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Volume Down’ key and press Power-On.

.
samsung_galaxy_tab2_101

RIFF JTAG – Samsung GT-P5110 Galaxy Tab 2 10.1 WiFi Unbrick – Dead Boot repair supported

25.01.2013 RIFF JTAG – Samsung GT-P5110 Galaxy Tab 2 10.1 WiFi Unbrick – Dead Boot repair supported

Samsung P5110 is based on the OMAP4430 Processor (Cortex-A9 Dual-Core). JTAG pads are very small; professional experience in soldering is required to connect wires to the JTAG interface.
Please note: The initial loader in the Samsung P5110 is XLOADER. Due to OMAP4430’s some peculiar TrustZone security features current resurrector will boot only in case XLOADER is alive. That’s why model name of current resurrector has additional text: ‘XLoader+’. In case XLOADER is damaged (which happens for example after wrong firmware reflash), you will have to use different resurrector DLL – the one with the ‘XLoader-” delimiter.

To resurrect Samsung P5110:

  •  Solder JTAG cable to Samsung P5110 JTAG pads;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung P5110 is selected in the list of models;
  •  Make sure a fixed TCK frequency is selected;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Volume Down’ key and press Power-On.

.
samsung_galaxy_tab2_101

RIFF JTAG – Samsung i9003 Galaxy SL Unbrick, Boot repair supported

28.10.2011  Samsung i9003 Galaxy SL Unbrick, Boot repair supported

Samsung I9003 is based on the OMAP3630 (ARM core is Cortex-A8).
Note, one simple way to connect over JTAG – connect USB cable to PC and insert battery. In this case phone is automatically powered on. But note, in very rare cases it is possible that you will have to hold Power On key during initial connection.
In case after resurrection (after you have tried with both boot versions) the download mode is not initiated (LCD remains blank) do repeat resurrection with ‘Clone Gremlin zone’ option checked.
Please note, in most cases you will be required to insert Samsung I9003 RIFF™ MagicCard into phone’s SD slot before starting resurrection. In case you don’t have such card yet, you can create it on the “Samsung I9003 RIFF™ MagicCard” page of the resurrector settings dialog.
Due to OMAP3630’s some peculiar TrustZone security features current resurrector may fail to boot: if this happens, use Samsung I9003 IRAM resurrector – which works much slower but boots without problems.

To resurrect Samsung I9003:

  •  Solder JTAG cable to Samsung I9003 JTAG pads;
  •  Insert Samsung I9003 RIFF™ MagicCard into phone’s SD slot;
  •  Connect USB cable to phone and PC;
  •  Insert battery;
  •  Make sure Samsung I9003 is selected in the list of models;
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using original Samsung downloader software to restore it to the working state.

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold both ‘Volume Down’ and ‘Home’ keys and press Power-On.

RIFF JTAG – HTC Wizard 200 Unbrick – Boot repair supported

25.08.2011  HTC Wizard 200 Unbrick – Boot repair supported

Resurrection of HTC Wizard 200 is simple. Battery must be connected in order to establish JTAG connection.
Current resurrector works with devices based on G4 MDOC chip.
Resurrector can repair IPL and SPL areas (which areas to repair you can select in popup window).
Please note: DiskOnChip G4 memory has security features, due to which there is a risk of permanently blocking the access to the flash memory while re-flashing the IPL area. Thus be very carefull not to interrupt IPL repair process (in case you have selected IPL area to be repaired).
In case your device has permanently blocked MDOC memory you will see this error:

****************************************************************
Detected a Not Initialized FLASH1 Chip ID: 0x0400/0xFBFF
ERROR: Selected FLASH Chip was not initialized by the DCC Loader
****************************************************************
This can happen due to unknown protection keys used or due to permanently blocked MDOC chip. If latter is true we advise you to solder a new flash memory chip or throw this phone away to the trash bin.
To resurrect HTC Wizard:

  •  Solder JTAG cable to HTC Wizard JTAG pads;
  •  Insert battery and connect USB cable to phone and PC;
  •  Make sure HTC Wizard is selected in the list of models;
  •  Press Power On key
  •  Click Resurrect button;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using known flashing methods.
To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold ‘Camera’ key and press ‘Power ON’ button.

Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended.

RIFF JTAG – Qtek 9000 (HTC Universal) Unbrick – Boot repair supported

15.07.2011  Qtek 9000 (HTC Universal) Unbrick – Boot repair supported

Current resurrector works with Qtek 9000 with MDOC G3 memory version. In order to establish JTAG connection charged battery is required. In some cases you will need to press power on key during initiating connection.
Please note, in case the Download Mode Initiation resurrection way is selected in the resurrector popup settings window, battery must be charged enough in order for phone to enter download mode.

Current resurrector offers 2 ways to resurrect the phone:

  •  WAY1: Writing SPL code directly into the MDOC memory (there are 2 hardware versions of the Qtek 9000 exist: boards with G4-type MDOC memory and boards with G3-type MDOC memory; current resurrector contains DCC Loader for G3 MDOC memory; thus for G4 version you need to use other resurrector)

 

  •  WAY2: Initiating DOWNLOAD MODE without touching MDOC contents;

MDOC G3 memory has security features, due to which there is a risk of permanently blocking the access to the flash memory while re-flashing the IPL loader. Current resurrector will not touch the IPL zone, but it is possible you’re already holding such killed device in hands. If it is so you will see this error:

****************************************************************
Detected a Not Initialized FLASH1 Chip ID: 0x0200/0xFDFF
ERROR: Selected FLASH Chip was not initialized by the DCC Loader
****************************************************************
In this case resurrection of your device is not possible. We advise you to solder a new flash memory chip and then use resurrector with IPL re-flash enabled.
To resurrect Qtek 9000 G3:

  •  Solder JTAG cable to Qtek 9000 G3 JTAG pads;
  •  Insert battery and connect USB cable to phone and PC;
  •  Make sure Qtek 9000 G3 is selected in the list of models;
  •  Click Resurrect button;
  •  In popup window select desired way of resurrection;
  •  Wait till software signals a successful operation completion;
  •  Disconnect USB cable, de-solder JTAG wires;

To enter download mode:

  •  Disconnect PC cable;
  •  Insert battery;
  •  Hold both ‘Light’ key (the one near to the volume slider) and ‘Power On’ key and press with stylus the reset hole-button.

Additional info:

  •  The DiskOnChip G3 memory type has security features. Access to both protected partitions (as IPL loader area) is done using password 00000000.
  •  IPL re-flash is intentionally switched off in this resurrector. While re-flashing the IPL area there is a risk of permanently blocking the memory chip.
  •  Memory is two DiskOnChip (MDOC) G3 cascaded chips, IDs are 0x0200; capacity is 64Mb+64Mb); though current DCC Loader was tested to read/write correctly only the SPL zones.

 

Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended.

RIFF JTAG – Toshiba Portege G900 Unbrick, Dead Boot repair supported

14.03.2011 Toshiba Portege G900 Unbrick, Dead Boot repair supported

Resurrection of Toshiba Portégé G900 PDA part is not hard. Battery is required for successful HALT operation. If USB Data Cable is connected phone is auto powered on when battery is inserted.
If during connect operation (“Establish communication with the phone…”) after 2-3 passes there is still no success (progress bar keeps running from 0 to 100% and so on) then remove battery and insert it again. If USB cable is not connected then press and hold Power On key.
Current resurrector re-flashes only the EBOOT and secondary EBOOT area, and will not re-write IPL area (though write of this area is supported too).
Please note: DiskOnChip G4 memory has security features, due to which there is a risk of permanently blocking the access to the flash memory while re-flashing the IPL areas. Current resurrector will not touch the IPL zone, but it is possible you’re already holding such killed device in hands. If it is so you will see this error:
****************************************************************
Detected a Not Initialized FLASH1 Chip ID: 0x0400/0xFBFF
ERROR: Selected FLASH Chip was not initialized by the DCC Loader
****************************************************************

This can happen due to unknown protection keys used or due to permanently blocked MDOC chip. If latter is true we advise you to solder a new flash memory chip or throw this phone away to the trash bin.

To resurrect Toshiba G900 PDA part:

  • Solder JTAG wires to the Toshiba G900 PDA pads;
  • Connect USB cable to phone and PC;
  • Make sure Toshiba G900 PDA is selected in the list of models;
  • Insert battery and click Resurrect button;
  • Wait till software signals a successful operation completion;
  • Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using known flashing methods.

To enter USB download mode:

  • Disconnect PC cable;
  • Insert battery;
  • Hold ‘Left soft’ key (which is exactly above the Dial key) and press ‘Power ON’ button. In few seconds you should see red download screen.

To enter SD-card download mode:

  • Disconnect PC cable;
  • Insert battery;
  • Hold ‘D’ key and press ‘Power ON’ button.

Additional info:

  • Phone has DiskOnChip G4 memory type, which has security features. It has two password protected partitions (Password1 = 12345678, Password2 = 00000000);
  • IPL re-flash is not performed in this resurrector on purpose. While re-flashing the IPL area there is a risk of permanently blocking the memory chip.
  • Any write access (Erase or Write) on MDOC NAND memory range 0x00000000 to 0x0017FFFF is rejected by the DCC Loader. For full image writing convenience access to that range will not rise any error, data will just be ignored and reported as if it was written successfully, thus you still can write full image files using ‘Auto FullFlash Size’ checked.

Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended.

RIFF JTAG – ASUS P526 Unbrick, Dead Boot repair supported

10.03.2011   ASUS P526 Unbrick, Dead Boot repair supported

Resurrection of ASUS P526 is slightly complicated. JTAG pads are very small and sensitive thus extreme care must be taken when soldering wires to the board. Battery must be connected in order to establish JTAG connection.
Current resurrector re-flashes only the IPL area, and will not re-write MDOC XLOADER area (though write of this area is supported too).
Please note: DiskOnChip G4 memory has security features, due to which there is a risk of permanently blocking the access to the flash memory while re-flashing the XLOADER areas. Current resurrector will not touch the XLOADER zone, but it is possible you’re already holding such killed device in hands. If it is so you will see this error:
****************************************************************
Detected a Not Initialized FLASH1 Chip ID: 0x0400/0xFBFF
ERROR: Selected FLASH Chip was not initialized by the DCC Loader
****************************************************************

This can happen due to unknown protection keys used or due to permanently blocked MDOC chip. If latter is true we advise you to solder a new flash memory chip or throw this phone away to the trash bin.

To resurrect ASUS P526:

  • Solder JTAG cable to ASUS P526 JTAG pads;
  • Insert battery and connect USB cable to phone and PC;
  • Make sure ASUS P526 is selected in the list of models;
  • Click Resurrect button;
  • Wait till software signals a successful operation completion;
  • Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally, you can flash it using known flashing methods.
If phone not enters download mode after resurrection then it means XLOADER was damaged too but memory chip is still usable. In this case repeat resurrection using RAM Downloader Mode and when USB connection is established reflash the phone with official firmware.

To enter download mode:

  • Disconnect PC cable;
  • Insert battery;
  • Move ‘Lock’ slider down, hold ‘OK’ key (on the left) and press ‘Power ON’ button. In few seconds you should see TriColor picture.

Additional info:

  • Phone has DiskOnChip G4 memory type, which has security features. It has two password protected partitions (Password1 = 12345678, Password2 = 00000000);
  • XLOADER re-flash is not performed in this resurrector on purpose. While re-flashing the XLOADER area there is a risk of permanently blocking the memory chip.
  • Any write access (Erase or Write) on MDOC NAND memory range 0x00000000 to 0x0017FFFF is rejected by the DCC Loader

Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended.