JTAG Manager 1.90 Direct JTAG Access to Flash Memory (DirectProgramming.dll) v1.06

Status
Not open for further replies.

sarfrazhusain

Friend's Martview
Aug 1, 2018
233
155
Unnao Uttar Pradesh India
Skype
sarfraz.husain1
Sonork ID
100.1608386
PayPal:

Donate money to this user
JTAG Manager 1.90
---------------------------
- added Removable Storage direct Read/Write feature.
This is mixed to USB Read/Write page. To access Removable Storage, select "Removable Storage Device" as Source
To work as before, with connected Phone to USB, select "USB Bootable Device" as Source.
- fixed bug: when reading DISK partitions, parsed with emmc plugin, clicking STOP in the middle didn't work. Now can terminate read operation.
- fixed internal bug which could lead to damaging the model names in resurrectors list
- fixed bug in reset strategy in some cases when setting Reset Strategy manually
- fixed text scrolling problem in logging windows




Direct JTAG Access to Flash Memory (DirectProgramming.dll) v1.06
-------------------------------------
- Reset Strategies are implemented in the same way as it is done in JTAG Manager
- plugin is updated to be compatible with current JTAG Manager
- Windows 10 High DPI support is added to plugin interface


eMMC Partition Table FullFlash Image Files Processing Plugin (eMMCDiskPartitions.dll) v5.14
-------------------------------------
- fixed LZ4 size leak which caused not-complete loading of LZ4 unpacked partitions
- after injecting image with file system layout into any partition, the Contents Explorer is updated, and thus, files of injected data can be browsed
- improved slightly the EFI parsing. Backup area size now not fixed, 0x21, but is deducted from EFI header
- improved parsing Firmware when parsing firmware from binary GPT file: GPT_BACKUP is also attempted to be loaded from sgpt.bin file
- improved Adjust GPT feature. Auto-expanding last partition will not be done in case the last partition is a relative one.
- added detection of F2FS and EROFS File Systems. Full support of these file systems for Content Explorer is yet to come.
- fixed some cases for expanding 0-sized entries when parsing XML via [Parse Official Firmware] button.
When AutoExpand option is checked [Menu/Options/Auto expand expandable partitions], memory size is assumed from selected memory size,
In case AutoExpand is not checked, default memory size 512GB is assumed for expanding 0-sized entry
 
Status
Not open for further replies.
Top