Easyjtag plus 2 tool issue

Question

Hello i have issue when I try to connect with easyjtag plus2 with ufs153 and on classic tool no issue it's work how I can fix pls?

Answer 1

Hello. Seems like chip not supported in plus software.

Comments

I have a lot of friend use plustool 2 with same chip and all work...

---

Where are classic log???

---

started.
OS ver.: Windows 11 (build 22621), 64-bit edition. Admin rights FAIL
Easy JTAG Autorun Agentver:1.0.0.0
CrashSender library ver:1.4.0.3
Curl binary ver:7.56.1.0
EasyJTAG binary ver:3.8.0.6
EasyJTAG SPI Plugin ver:1.1.1.13
LibUSB Library ver:1.2.6.0
WinFSP SDK ver:1.12.22301.0
Setting box Pinout ...

Box Drivers version: 3.0.0.0
Z3X Card Serial : AAF1-D632 , ver: 22
Z3X Card Activation [JTAGPLUS] : ACTIVATED
Z3X Card Activation [LG] : NOT ACTIVATED
Z3X Card Activation [SAMS] : NOT ACTIVATED
Z3X Card Activation [JTAG] : ACTIVATED

For more information press F1 to open local help or visit our wiki

Found 1 serial devices
COM4 USB\VID_1781&PID_AAAC&REV_0100&MI_00 Easy Jtag Plus Control Port (COM4)
Z3X EasyJtag Software ver. 3.8.0.6
UFS Socket Info.
Serial: 0123AFCBBD587A13EE
œ²·
Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3332mV
VCCQ2: 1894mV
Chip Info:
Manufacturer: SAMSUNG
ProductName: KLUBG4G1ZF-B0CQ
SerialNumber: 0x48626BECB5197EB79D94134AE6815342574843303152
OemID: SAMSUNG_OEM_ID
Firmware Version: 5.2.0.0
UFS Reference Clock: 26MHz
UFS Version: 2.1
Maximum Number of LUs: 8
Number of LUs found: 4
   LUN 0:
      Block size: 0x1000
      Size: 0x746400000 / 29,100,000,000B / 29GB
   LUN 1:
      Block size: 0x1000
      Size: 0x400000 / 0,004,000,000B / 4MB
   LUN 2 (Main Boot A):
      Block size: 0x1000
      Size: 0x400000 / 0,004,000,000B / 4MB
   LUN 3 (Boot B):
      Block size: 0x1000
      Size: 0x400000 / 0,004,000,000B / 4MB
Number of W-LUs found: 1
   W-LUN 0xC4 (RPMB):
      Block size: 0x100
      Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0x74FC00000 / 29,252,000,000B / 29GB
RPMB:
 Counter: 10046
Health:
 Device life time method A: 0x01 (0%-10% device life time used)
 Device life time method B: 0x01 (0%-10% device life time used)
 Pre End of Life: 0x01 (Used less then 80% of reserved blocks)
Samsung SSR.
SSR version: 0
Descriptor Length: 76
UFS Descriptor Type: 10
Max Erase Cycle SLC: 9
Min Erase Cycle SLC: 0
Avg Erase Cycle SLC: 3
Max Erase Cycle MLC: 8
Min Erase Cycle MLC: 4
Avg Erase Cycle MLC: 6
Read Reclaim Count: 8
Init. Bad Block: 21
Runtime Bad Block: 0
Remain Reserved Block: 59
Patch trial Count: 0
Patch Release Date: 0
Written Data: 1077
Open Count: 2025
Patch Count: 0
LVD Count: 0
PON Init Count: 26018
SPOR init Count: 0
Read Data: 0
Written WB data: 0
Ignored WB data: 0
Written RPMB0 data: 0
Written RPMB1 data: 0
Written RPMB2 data: 0
Written RPMB3 data: 0
HPB Read CMD Count: 0
HPB Hit Count: 0
Checking LUs for partitioning
LUN0 Have 32 partitions
LUN1 Have no partitions
LUN2 Have no partitions
LUN3 Have no partitions
------ Detected 14 partitions ------
LUN0 (BOOT_A) [0x100000 - 0xb00000] Size: 0xa00000(10.0MB)
LUN0 (BOOT_B) [0xb00000 - 0x1500000] Size: 0xa00000(10.0MB)
LUN0 (HYP_A) [0x1500000 - 0x1700000] Size: 0x200000(2.0MB)
LUN0 (DTB_A) [0x1700000 - 0x1800000] Size: 0x100000(1.0MB)
LUN0 (KERNELDOM0_A) [0x1800000 - 0x2600000] Size: 0xe00000(14.0MB)
LUN0 (INITRAMFSDOM0_A) [0x2600000 - 0x3000000] Size: 0xa00000(10.0MB)
LUN0 (SYSTEMDOM0_A) [0x3000000 - 0x19200000] Size: 0x16200000(354.0MB)
LUN0 (SYSTEM2DOM0_A) [0x19200000 - 0x1aa00000] Size: 0x1800000(24.0MB)
LUN0 (KERNELDOMU1_A) [0x1aa00000 - 0x1bd00000] Size: 0x1300000(19.0MB)
LUN0 (DTBDOMU1_A) [0x1bd00000 - 0x1be00000] Size: 0x100000(1.0MB)
LUN0 (INITRAMFSDOMU1_A) [0x1be00000 - 0x1c800000] Size: 0xa00000(10.0MB)
LUN0 (SYSTEMDOMU1_A) [0x1c800000 - 0x31c00000] Size: 0x15400000(340.0MB)
LUN0 (SYSTEM2DOMU1_A) [0x31c00000 - 0x33400000] Size: 0x1800000(24.0MB)
LUN0 (ALIGN1) [0x33400000 - 0x33500000] Size: 0x100000(1.0MB)
------------------------------------
Read SYSTEM from LUN0.
------ Android information ------

Detected LINUX(Android) SYSTEMDOM0_A : 0x0003000000 (354.0MB)
Unable to mount SYSTEM , code : 95
---------------------------------------------

Read SYSTEM from LUN0.
------ Android information ------

Detected LINUX(Android) SYSTEM2DOM0_A : 0x0019200000 (24.0MB)
Short EXT fs info:
Size: 23.632MB
Block size: 4.0KB
œž·
œž·
Short Android info:
Unable to read prop.plist , code : 2
---------------------------------------------

Read SYSTEM from LUN0.
------ Android information ------

Detected LINUX(Android) SYSTEMDOMU1_A : 0x001C800000 (340.0MB)
Unable to mount SYSTEM , code : 95
---------------------------------------------

Read SYSTEM from LUN0.
------ Android information ------

Detected LINUX(Android) SYSTEM2DOMU1_A : 0x0031C00000 (24.0MB)
Short EXT fs info:
Size: 23.632MB
Block size: 4.0KB
œž·
œž·
Short Android info:
Unable to read prop.plist , code : 2
---------------------------------------------

Done.

---

Any idea friend?

---

Wait for updates.

---

Is there a date planned? I can't work at the moment...

---

Hello i have issue when I try to new box easyjtag plus2 not run

Answer 2

It seems like you're experiencing a technical issue related to connecting an EasyJTAG Plus2 with UFS153 using the Classic Tool. Troubleshooting such technical problems can be complex and often require specific knowledge of the hardware and software involved. Here are some general steps you can take to troubleshoot the issue:

Check Connections:

• Ensure that all physical connections are secure. Check the cables, connectors, and any adapters to make sure they are properly connected.
• Confirm that the UFS153 and EasyJTAG Plus2 are powered on and receiving power as needed.

Driver Installation:

• Make sure that the necessary drivers for your UFS153 and EasyJTAG Plus2 are correctly installed on your computer. Check the manufacturer's website for the latest driver versions and installation instructions. scratch geometry dash

Answer 3

Your blog never disappoints. Always find it very helpful. URL