UFS memory connection troubles, question, discuss thread

[lihua]

Code: -403 ？？？？？

Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3309mV
VCCQ2: 1865mV
Manufacturer: SAMSUNG
ProductName: KM2B8001CM-BB01
SerialNumber: 332991b5ef1d
OemID: SAMSUNG_OEM_ID
Maximum Number of LUs: 8
Number of LUs found: 6
LUN 0:
Block size: 0x1000
Size: 0x3A2E000000 / 232,736,000,000B / 232GB
LUN 1 (Boot A):
Block size: 0x1000
Size: 0x400000 / 0,004,000,000B / 4MB
LUN 2 (Boot B):
Block size: 0x1000
Size: 0x400000 / 0,004,000,000B / 4MB
LUN 3:
Block size: 0x1000
Size: 0x8000000 / 0,128,000,000B / 128MB
LUN 4:
Block size: 0x1000
Size: 0x100000000 / 4,000,000,000B / 4GB
LUN 5:
Block size: 0x1000
Size: 0x60000000 / 1,512,000,000B / 1GB
Number of W-LUs found: 1
W-LUN 0xC4 (REPORT LUNS):
Block size: 0x100
Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0x3B97800000 / 238,376,000,000B / 238GB

Read GPT From LUN 0.
Partition info successfully found
Found Data areas (firmware parts) count is: 13
---------------------------------------------

P0 (SSD) [0x6000 0x2000] Size: 8.0KB
P1 (PERSIST) [0x8000 0x2000000] Size: 32.0MB
P2 (MISC) [0x2008000 0x100000] Size: 1.0MB
P3 (KEYSTORE) [0x2108000 0x80000] Size: 512.0KB
P4 (FRP) [0x2188000 0x80000] Size: 512.0KB
P5 (VM-KYSTORE) [0x2208000 0x100000] Size: 1.0MB
P6 (VM-DATA) [0x2308000 0xa00000] Size: 10.0MB
P7 (VM-SYSTEM) [0x2d08000 0x8000000] Size: 128.0MB
P8 (VM-LINUX) [0xad08000 0x2000000] Size: 32.0MB
P9 (CACHE) [0xcd08000 0x10000000] Size: 256.0MB
P10 (SYSTEM) [0x1cd08000 0x136c00000] Size: 4.855GB
P11 (ODM) [0x153908000 0x10000000] Size: 256.0MB
P12 (USERDATA) [0x163908000 0x38ca6f3000] Size: 227.162GB
------ Android information ------

Detected LINUX(Android) SYSTEM : 0x001CD08000 (4.855GB)
Unable to read prop.plist , code : 2
---------------------------------------------

Detected USERDATA USERDATA : 0x0163908000 (227.162GB)
Unable to mount USERDATA , code : 95
Z3X EasyJtag Software ver. 3.6.1.4
UFS Socket Info.
Serial: 0123512AF7EB3812EE
Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19

Read UFS LUN0, Address:1CD08000 ,Length: 136C00000
Output file :C:\Users\Administrator\Desktop\Reno\LUN0_8G\UFS_K M2B8001CM-BB01332991b5ef1d_LU0_0x1cd08000_SYSTEM_0x136c00000 .bin
Start
Can't read address 0x22308000, Code: -403, Reason: UAP SCSI: Command sense: MEDIUM_ERROR
Read, time taken: 392 sec. Average Reading Speed: 229 kB/s
Done.

[TELEFOONMASTER]

Originally Posted by layder

To remove FRP from UFS chips you need press "Remove FRP"
UserData at most UFS chips is crypted

Samsung G920/G925/N920 have not-crypted userdata

There is no way to decrypt User Data?There are companies offering to decrypt it?

[NoName®]

Originally Posted by lihua

Code: -403 ？？？？？

Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3309mV
VCCQ2: 1865mV
Manufacturer: SAMSUNG
ProductName: KM2B8001CM-BB01
SerialNumber: 332991b5ef1d
OemID: SAMSUNG_OEM_ID
Maximum Number of LUs: 8
Number of LUs found: 6
LUN 0:
Block size: 0x1000
Size: 0x3A2E000000 / 232,736,000,000B / 232GB
LUN 1 (Boot A):
Block size: 0x1000
Size: 0x400000 / 0,004,000,000B / 4MB
LUN 2 (Boot B):
Block size: 0x1000
Size: 0x400000 / 0,004,000,000B / 4MB
LUN 3:
Block size: 0x1000
Size: 0x8000000 / 0,128,000,000B / 128MB
LUN 4:
Block size: 0x1000
Size: 0x100000000 / 4,000,000,000B / 4GB
LUN 5:
Block size: 0x1000
Size: 0x60000000 / 1,512,000,000B / 1GB
Number of W-LUs found: 1
W-LUN 0xC4 (REPORT LUNS):
Block size: 0x100
Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0x3B97800000 / 238,376,000,000B / 238GB

Read GPT From LUN 0.
Partition info successfully found
Found Data areas (firmware parts) count is: 13
---------------------------------------------

P0 (SSD) [0x6000 0x2000] Size: 8.0KB
P1 (PERSIST) [0x8000 0x2000000] Size: 32.0MB
P2 (MISC) [0x2008000 0x100000] Size: 1.0MB
P3 (KEYSTORE) [0x2108000 0x80000] Size: 512.0KB
P4 (FRP) [0x2188000 0x80000] Size: 512.0KB
P5 (VM-KYSTORE) [0x2208000 0x100000] Size: 1.0MB
P6 (VM-DATA) [0x2308000 0xa00000] Size: 10.0MB
P7 (VM-SYSTEM) [0x2d08000 0x8000000] Size: 128.0MB
P8 (VM-LINUX) [0xad08000 0x2000000] Size: 32.0MB
P9 (CACHE) [0xcd08000 0x10000000] Size: 256.0MB
P10 (SYSTEM) [0x1cd08000 0x136c00000] Size: 4.855GB
P11 (ODM) [0x153908000 0x10000000] Size: 256.0MB
P12 (USERDATA) [0x163908000 0x38ca6f3000] Size: 227.162GB
------ Android information ------

Detected LINUX(Android) SYSTEM : 0x001CD08000 (4.855GB)
Unable to read prop.plist , code : 2
---------------------------------------------

Detected USERDATA USERDATA : 0x0163908000 (227.162GB)
Unable to mount USERDATA , code : 95
Z3X EasyJtag Software ver. 3.6.1.4
UFS Socket Info.
Serial: 0123512AF7EB3812EE
Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19

Read UFS LUN0, Address:1CD08000 ,Length: 136C00000
Output file :C:\Users\Administrator\Desktop\Reno\LUN0_8G\UFS_K M2B8001CM-BB01332991b5ef1d_LU0_0x1cd08000_SYSTEM_0x136c00000 .bin
Start
Can't read address 0x22308000, Code: -403, Reason: UAP SCSI: Command sense: MEDIUM_ERROR
Read, time taken: 392 sec. Average Reading Speed: 229 kB/s
Done.

MEDIUM_ERROR is a error, very specific to Samsung UFS memory. MEDIUM_ERROR caused if UFS chip is unable to read internal NAND page or unable to correct ECC errors. Generally such error caused by changing chip environment like power level. MEDIUM errors gone if you erase chip contents. Samsung UFS may have some vendor commands for internal recalibration. Currently we working on them.

[tony_k]

verified UFS chip (samsung S7) ang got following message, any way to solve it
======================================
UFS Chip Voltage: Low
Can't init device, Code: -118, Reason: This chip is temporary unsupported
VCC: 3298mV
VCCQ2: 1816mV
Manufacturer: SKHYNIX
产品名称: HBG4a
SerialNumber: 0x03A0A456AB6D
OemID: 01AD
Done（完成）。

[layder]

Originally Posted by tony_k

verified UFS chip (samsung S7) ang got following message, any way to solve it
======================================
UFS Chip Voltage: Low
Can't init device, Code: -118, Reason: This chip is temporary unsupported
VCC: 3298mV
VCCQ2: 1816mV
Manufacturer: SKHYNIX
产品名称: HBG4a
SerialNumber: 0x03A0A456AB6D
OemID: 01AD
Done（完成）。

this chips temporary disabled - this chips is sometimes dead after 3-5 operations

[sovservice]

Z3X EasyJtag Software ver. 3.6.1.17
UFS Socket Info.
Serial: 01237D77F52D1F31EE
Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19

Can't open link, Code: -56, Reason: BOX: Chip not connected
Сделано.

Help. Hardware 2.50

[layder]

Originally Posted by sovservice

Z3X EasyJtag Software ver. 3.6.1.17
UFS Socket Info.
Serial: 01237D77F52D1F31EE
Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19

Can't open link, Code: -56, Reason: BOX: Chip not connected
Сделано.

Help. Hardware 2.50

You was see a text: Chip not connected.

What help you need?

[sovservice]

Originally Posted by layder

You was see a text: Chip not connected.

What help you need?

The chip is in the socket

[layder]

Originally Posted by sovservice

The chip is in the socket

check if socket pins is clear, test balls of UFS chip, test power at socket pins
try ahother chip, try socket position (UFS254/153)
retunt socket to seller

[kamreikia]

hi


problem with me

Description: EasyJTAG UFS Socket BGA-153 by EasyJTAG 19.05.19

Identify UFS Chip.
UFS Chip Voltage: High
Can't init device, Code: -113, Reason: UTP: Failed to NOP request
VCC: 3299mV
VCCQ2: 2805mV
Done.

socket easyjtag ufs 153

[MOORC]

1.Fixed some mircon bug on Icfriend socket.
Mircon BGA153

2.plese sure your socket is like this pins. If now same. Please change a new one from your resller




从我的 iPhone 发送，使用 Tapatalk

[MOORC]

Originally Posted by kamreikia

hi


problem with me

Description: EasyJTAG UFS Socket BGA-153 by EasyJTAG 19.05.19

Identify UFS Chip.
UFS Chip Voltage: High
Can't init device, Code: -113, Reason: UTP: Failed to NOP request
VCC: 3299mV
VCCQ2: 2805mV
Done.

socket easyjtag ufs 153

Don’t use VCCQ2 2.8V


从我的 iPhone 发送，使用 Tapatalk

[MOORC]

Originally Posted by love edition

Pls help me ! I buy UFS socket ICFriend 2in1 (Ver new) by Moorc but speed read and write very slow. (6xxkB/s to 7xxkB/s) How to solve the problem ?

Please change a new computer. Will be up to 2.5MB/S. My computer is I5


从我的 iPhone 发送，使用 Tapatalk

[MOORC]

Originally Posted by davoodc

I BUY UFS 153 ADAPTOR YESTERDAY

NOW MY BOX READ AND WIRTE OPERATION ARE ABOUT 500 KB/s



IS IT NORMAL FOR UFS CHIPSET?????



ITS VERY SLOWLY

Need a better computer


从我的 iPhone 发送，使用 Tapatalk

[MOORC]

Originally Posted by Gaelymateo2

i have activated my box, latest version and i have Morc Adpters





But when i want to read a UFS give this error.



With EMMC and ISP works normal.



The problem is when i want to read a memory UFS.





Box Drivers version: 3.2.0.0

Z3X Card Serial : AAD1-FXXX , ver: 22

Z3X Card Activation [JTAGPLUS] : ACTIVATED

Z3X Card Activation [LG] : NOT ACTIVATED

Z3X Card Activation [SAMS] : NOT ACTIVATED

Z3X Card Activation [JTAG] : ACTIVATED





Found 1 serial devices

COM5 USB\VID_1781&PID_AAAC&REV_0100&MI_00 MediaTek USB VCOM (Android) (COM5)

Selected pinout: GEN2 High Speed Pinout

Change EasyJTAG Pinout OK

Z3X EasyJtag Software ver. 3.6.1.2

UFS Socket Info.

Serial: 0123C09D037CXXXXX

Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19



Can't open link, Code: -56, Reason: BOX: Chip not connected

Done.



Z3X EasyJtag Software ver. 3.6.1.2

UFS Socket Info.

Serial: 0123C09D037CC85BEE

Description: EasyJTAG UFS Socket 3 in 1 by MOORC 15.05.19



Can't open link, Code: -56, Reason: BOX: Chip not connected

Done.





Can you help me, please.







in Easy jtag plus does not enable me frequency and bus width https://ibb.co/Byg2nbJ



Or i need to buy another activation? where buy that activation?

Please use 3.6.17. And sure 2 pictures thanks


从我的 iPhone 发送，使用 Tapatalk