RIFF JTAG MEGA GIGA Updates -;)
Resurrecting HTC Click is easy. Phone is auto powered on with USB Data Cable connected to the PC while battery is inside.
There are two different hardware versions exist – one based on the MSM7225 chipset (CLIC10000) and other – on the ESM7225 chipset (CLIC11000). In resurrector settings you can select a desired version.
Resurrector will reflash radio’s boot zone and will re-write PDA’s SPL to 0.52.0001 SPL version.
As well, you can change CID – for this make sure ‘Repair Custom ID’ field is checked in the Resurrection Guide dialog.
To resurrect HTC Click:
- Solder JTAG cable to HTC Click JTAG pads;
To Unlock HTC Click :
- Solder JTAG cable to HTC Click JTAG pads;
Make sure HTC Click is selected in the list of models;
Click Resurrect button;
Select “Unlock Settings” TAB
Select Unlock method
Click “Unlock”
New HTC Desire DLL has additional option to select between reading NCK Code, or direct unlock.
This should also solve “error 0×45″ problem with some of the HW revisions.
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: 0×0400/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 0×00000000 to 0x0017FFFF is rejected by the DCC Loader
Resurrecting ZTE F285 is simple. Phone is auto powered on with USB Data Cable connected to the PC. Battery presence is not required; connection can be established with detached board. Resurrector re-flashes only firmware zone of the phone (0×000000 to 0x60FFFF).
To resurrect ZTE F285:
- Solder JTAG cable to ZTE F285 JTAG pads;
Insert USB Data cable into board and PC;
Make sure ZTE F285 is selected in the list of models;
Click Resurrect button;
Wait till software signals a successful operation completion;
De-solder JTAG wires;
10.03.2011 RIFF JTAG Manager v1.27, RIFF Box Firmware v1.19
Whats new :
RIFF JTAG Manager v1.27
- Fixed access violation bug upon JTAG Manager startup if there is no RIFF Box detected and Cancel button is clicked.
(SDK): more functions are now available (exported) for future Resurrector DLLs;
Added flags for JTAG Manager to be able to retrieve memory chip size from the DCC Loader.
Fixed initialization bug for NOR-related DCC Loadererss
******Engine: added options pocessing ‘/byte’, ‘/word’, ‘/long’ to data.save.binary instruction: thus it’s possible now to read memory through ****** using desired bus access width (8-,16-, or 32-bit widths). For example: “data.save.binary c:\myfile.bin 0×00..0x11FF /word” – will read 0×1200 bytes from memory into myfile.bin file starting from address 0×00 using 16-bit bus accesses.
Note: “Read Memory” button on the JTAG Read/Write page reads memory using 32-bit bus accesses only.
RIFF Box Firmware v1.19
- Added more H/W ****** (*.has) instructions;
Added HTC security processing functions;
Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended
.gif)
المفضلات