GSM-Forum

GSM-Forum (https://forum.gsmhosting.com/vbb/)
-   Easy-Jtag / Easy-Jtag Plus (https://forum.gsmhosting.com/vbb/f672/)
-   -   KM8V7001JM-B810 Solution (https://forum.gsmhosting.com/vbb/f672/km8v7001jm-b810-solution-2923071/)

Asiatic Rebel 11-10-2020 14:28

KM8V7001JM-B810 Solution
 
Oppo CPH2125 Reno 4 Lite UFS Failed
Device is work, only Lock Screen
Please help.

Code:

UFS: Memory Info:
 Connection: UNKNOWN SOCKET TYPE
 Vendor: SAMSUNG
 Name: KM8V7001JM-B810
 S/N: 3c50095f1902
 OEM ID: SAMSUNG_OEM_ID
 Firm Version: 1.2.0.0
 Size: 0x001DCC800000/119,20 GB
 Max LUNs: 8
 LUNs Cnt: 3
 W-LUNs Cnt: 1
 LUNs ReConfig: Enabled

UFS Health Info:
UFS Life Time A: 0x01 -> 0% - 10% Life Time Used
UFS Life Time B: 0x01 -> 0% - 10% Life Time Used
UFS Pre-EOL Info: 0x01 -> Used Less 80% of Reserved Blocks

UFS: LUNs Info:
 LUN 0 (Boot A) -> Size: 1024 Block(s)/4,00 MB
 LUN 1 (Boot B) -> Size: 1024 Block(s)/4,00 MB
 LUN 2 -> Size: 31240192 Block(s)/119,17 GB
 W-LUN 0xC4 (REPORT LUNS) -> Size: 65536 Block(s)/16,00 MB

UFS Init OK
Scanning Data From UFS Chip. Please wait..

Scanning GUID Partition Table from LUN 0

Error Reading Sector: 0, Count: 6, Err: -108/UNKN_ERR
Try Again #1

Error Reading Sector: 0, Count: 6, Err: -504/UNKN_ERR


layder 11-10-2020 17:47

Quote:

Originally Posted by Asiatic Rebel (Post 14263357)
Oppo CPH2125 Reno 4 Lite UFS Failed
Device is work, only Lock Screen
Please help.

Code:

UFS: Memory Info:
 Connection: UNKNOWN SOCKET TYPE
 Vendor: SAMSUNG
 Name: KM8V7001JM-B810
 S/N: 3c50095f1902
 
Scanning GUID Partition Table from LUN 0

Error Reading Sector: 0, Count: 6, Err: -108/UNKN_ERR
Try Again #1

Error Reading Sector: 0, Count: 6, Err: -504/UNKN_ERR


what socket and connection you use?

Asiatic Rebel 11-11-2020 07:40

UFS: Socket Info: EasyJTAG UFS Socket BGA-254 by EasyJTAG

layder 11-11-2020 10:08

Quote:

Originally Posted by Asiatic Rebel (Post 14263796)
UFS: Socket Info: EasyJTAG UFS Socket BGA-254 by EasyJTAG

what connection? ISP/socket ?
what software version, box firmware version?

Asiatic Rebel 11-11-2020 13:13

1 Attachment(s)
Connection with Socket BGA 254

This chip realme, not detect. Software frezee

Quote:

Z3X EasyJtag Software ver. 3.7.0.20
UFS Socket Info.
Serial: 012341**********
Description: EasyJTAG UFS Socket BGA-254 by EasyJTAG 05.08.20

Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3291mV
VCCQ2: 1923mV

Chip Info:
Manufacturer: SAMSUNG
ProductName: KM5V7001DM-B621
SerialNumber: 3b2305ccc71b
OemID: SAMSUNG_OEM_ID
Firmware Version: 9.00
UFS Version: 2.1

Maximum Number of LUs: 8
Number of LUs found: 6
LUN 0:
Block size: 0x1000
Size: 0x1D90000000 / 118,256,000,000B / 118GB
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: 0x2000000 / 0,032,000,000B / 32MB
LUN 4:
Block size: 0x1000
Size: 0x29000000 / 0,656,000,000B / 656MB
LUN 5:
Block size: 0x1000
Size: 0x10000000 / 0,256,000,000B / 256MB
Number of W-LUs found: 1
W-LUN 0xC4 (REPORT LUNS):
Block size: 0x100
Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0x1DCC800000 / 119,200,000,000B / 119GB

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)

Checking LU0 for partitioning

Asiatic Rebel 11-11-2020 15:07

KM5V7001DM-B621 and KM8V7001JM-B810 UFS Chip not support?

please give me an answer, should I return it to the customer?

layder 11-12-2020 16:29

Quote:

Originally Posted by Asiatic Rebel (Post 14265131)
I am try with old firmware and old software but problem not solved

try this, only for check

short this pins and post results


p.s I was remove picture - it is a temp solution

Solution is: https://forum.gsmhosting.com/vbb/f67.../#post14277775

Asiatic Rebel 11-13-2020 07:44

1 Attachment(s)
Quote:

Originally Posted by layder (Post 14265152)
try this, only for check

short this pins and post results


Now connect OK.

I can press key 'Reset Oppo', do you approve?

Quote:

EasyJtag Suite Classic ver.: 3.7.0.20 / wxWidgets 3.1.3-W-U started.
OS ver.: Windows 10 (build 19041), 64-bit edition. Admin rights FAIL
Autorun Agent ver:1.0.0.0
Crash Reporting ver:1.4.0.3
EasyJTAG SPI Plugin ver:1.1.1.13
Android ADB API ver:2.0.0.0
FTDI API ver:3.2.4.0
LibUSB API ver:1.2.6.0
Visual C++ Runtime ver:10.0.30319.1
Setting box Pinout ...

Box Drivers version: 10.0.19041.1
Z3X Card Serial : AA***** , 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 2 serial devices
COM1 ACPI\VEN_PNP&DEV_0501 İletişim Bağlantı Noktası (COM1)
COM5 USB\VID_1781&PID_AAAC&REV_0100&MI_00 USB Seri Cihaz (COM5)
Selected pinout: GEN2 High Speed Pinout
Change EasyJTAG Pinout OK
Z3X EasyJtag Software ver. 3.7.0.20
UFS Socket Info.
Serial: 0123411*******
Description: EasyJTAG UFS Socket BGA-254 by EasyJTAG 05.08.20

Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3305mV
VCCQ2: 1923mV

Chip Info:
Manufacturer: SAMSUNG
ProductName: KM5V7001DM-B621
SerialNumber: 3b2305ccc71b
OemID: SAMSUNG_OEM_ID
Firmware Version: 9.00
UFS Version: 2.1

Maximum Number of LUs: 8
Number of LUs found: 6
LUN 0:
Block size: 0x1000
Size: 0x1D90000000 / 118,256,000,000B / 118GB
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: 0x2000000 / 0,032,000,000B / 32MB
LUN 4:
Block size: 0x1000
Size: 0x29000000 / 0,656,000,000B / 656MB
LUN 5:
Block size: 0x1000
Size: 0x10000000 / 0,256,000,000B / 256MB
Number of W-LUs found: 1
W-LUN 0xC4 (REPORT LUNS):
Block size: 0x100
Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0x1DCC800000 / 119,200,000,000B / 119GB

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)

Checking LU0 for partitioning
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN0 Have 14 partitions
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN1 Have 2 partitions
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN2 Have 0 partitions
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN3 Have 3 partitions
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN4 Have 33 partitions
The protective MBR's 0xEE partition is oversized! Auto-repairing.
LUN5 Have 12 partitions
------ Detected 64 partitions ------
LUN0 (SSD) [0x6000 0x2000] Size: 8.0KB
LUN0 (PERSIST) [0x8000 0x2000000] Size: 32.0MB
LUN0 (MISC) [0x2008000 0x100000] Size: 1.0MB
LUN0 (KEYSTORE) [0x2108000 0x80000] Size: 512.0KB
LUN0 (FRP) [0x2188000 0x80000] Size: 512.0KB
LUN0 (VM-KYSTORE) [0x2208000 0x100000] Size: 1.0MB
LUN0 (VM-DATA) [0x2308000 0xa00000] Size: 10.0MB
LUN0 (VM-SYSTEM) [0x2d08000 0x8000000] Size: 128.0MB
LUN0 (VM-LINUX) [0xad08000 0x2000000] Size: 32.0MB
LUN0 (CACHE) [0xcd08000 0x10000000] Size: 256.0MB
LUN0 (SYSTEM) [0x1cd08000 0x144000000] Size: 5.62GB
LUN0 (VENDOR) [0x160d08000 0x60000000] Size: 1.500GB
LUN0 (ODM) [0x1c0d08000 0x10000000] Size: 256.0MB
LUN0 (USERDATA) [0x1d0d08000 0x1bbf2f3000] Size: 110.986GB
LUN1 (XBL) [0x6000 0x380000] Size: 3.500MB
LUN1 (XBL_CONFIG) [0x386000 0x20000] Size: 128.0KB
LUN3 (ALIGN_TO_128K_1) [0x6000 0x1a000] Size: 104.0KB
LUN3 (CDT) [0x20000 0x20000] Size: 128.0KB
LUN3 (DDR) [0x40000 0x100000] Size: 1.0MB
LUN4 (AOP) [0x6000 0x80000] Size: 512.0KB
LUN4 (TZ) [0x86000 0x200000] Size: 2.0MB
LUN4 (HYP) [0x286000 0x800000] Size: 8.0MB
LUN4 (HYPBAK) [0xa86000 0x800000] Size: 8.0MB
LUN4 (MODEM) [0x1286000 0x9000000] Size: 144.0MB
LUN4 (BLUETOOTH) [0xa286000 0x100000] Size: 1.0MB
LUN4 (ABL) [0xa386000 0x100000] Size: 1.0MB
LUN4 (DSP) [0xa486000 0x2000000] Size: 32.0MB
LUN4 (KEYMASTER) [0xc486000 0x80000] Size: 512.0KB
LUN4 (BOOT) [0xc506000 0x4000000] Size: 64.0MB
LUN4 (CMNLIB) [0x10506000 0x80000] Size: 512.0KB
LUN4 (CMNLIB64) [0x10586000 0x80000] Size: 512.0KB
LUN4 (DEVCFG) [0x10606000 0x20000] Size: 128.0KB
LUN4 (QUPFW) [0x10626000 0x10000] Size: 64.0KB
LUN4 (VBMETA) [0x10636000 0x10000] Size: 64.0KB
LUN4 (RECOVERY) [0x10646000 0x4000000] Size: 64.0MB
LUN4 (DTBO) [0x14646000 0x1800000] Size: 24.0MB
LUN4 (STORSEC) [0x15e46000 0x20000] Size: 128.0KB
LUN4 (OPPO_SEC) [0x15e66000 0xa00000] Size: 10.0MB
LUN4 (SEC) [0x16866000 0x4000] Size: 16.0KB
LUN4 (DEVINFO) [0x1686a000 0x1000] Size: 4.0KB
LUN4 (DIP) [0x1686b000 0x100000] Size: 1.0MB
LUN4 (APDP) [0x1696b000 0x40000] Size: 256.0KB
LUN4 (MSADP) [0x169ab000 0x40000] Size: 256.0KB
LUN4 (SPUNVM) [0x169eb000 0x800000] Size: 8.0MB
LUN4 (DPO) [0x171eb000 0x1000] Size: 4.0KB
LUN4 (SPLASH) [0x171ec000 0x20a4000] Size: 32.640MB
LUN4 (LIMITS) [0x19290000 0x1000] Size: 4.0KB
LUN4 (TOOLSFV) [0x19291000 0x100000] Size: 1.0MB
LUN4 (LOGFS) [0x19391000 0x800000] Size: 8.0MB
LUN4 (STI) [0x19b91000 0x200000] Size: 2.0MB
LUN4 (RAWDUMP) [0x19d91000 0x8000000] Size: 128.0MB
LUN4 (LOGDUMP) [0x21d91000 0x4000000] Size: 64.0MB
LUN5 (ALIGN_TO_128K_2) [0x6000 0x1a000] Size: 104.0KB
LUN5 (OPPODYCNVBK) [0x20000 0xa00000] Size: 10.0MB
LUN5 (OPPOSTANVBK) [0xa20000 0xa00000] Size: 10.0MB
LUN5 (MODEMST1) [0x1420000 0x200000] Size: 2.0MB
LUN5 (MODEMST2) [0x1620000 0x200000] Size: 2.0MB
LUN5 (OPPORESERVE1) [0x1820000 0x800000] Size: 8.0MB
LUN5 (OPPORESERVE2) [0x2020000 0x4000000] Size: 64.0MB
LUN5 (OPPORESERVE3) [0x6020000 0x4000000] Size: 64.0MB
LUN5 (CARRIER) [0xa020000 0x800000] Size: 8.0MB
LUN5 (DRIVER) [0xa820000 0x2000000] Size: 32.0MB
LUN5 (FSG) [0xc820000 0x200000] Size: 2.0MB
LUN5 (FSC) [0xca20000 0x20000] Size: 128.0KB
------------------------------------
Read SYSTEM from LUN0.
The protective MBR's 0xEE partition is oversized! Auto-repairing.
------ Android information ------
Detected LINUX(Android) SYSTEM : 0x001CD08000 (5.62GB)
Short EXT fs info:
Size: 4.982GB
Block size: 4.0KB
Inode size: 256
Inodes: 327040
Short Android info:
Unable to read prop.plist , code : 2
---------------------------------------------
Read USERDATA from LUN0.
The protective MBR's 0xEE partition is oversized! Auto-repairing.
Detected USERDATA USERDATA : 0x01D0D08000 (110.986GB)
Unable to mount USERDATA , code : 95
Userdata Superblock contents::
68DEC806 40DEC677 C8F47906 DE282201 44AB190D 00C9090F 40DCB406 F0AE190D hŞ[email protected]Şwy.Ş(".D... [email protected]ܴ.ğ..;
FC140000 68DEC806 40AC190D D4895101 25000000 40DEC677 40DCB406 19D1C877 ...hŞ[email protected]..ԉQ.%[email protected]Ş[email protected]ܴ..w;
68DEC806 104C4E01 34367D01 78AB190D 00000000 40C9090F 40DCB406 98AF190D hŞ..LN.46}.x[email protected] [email protected]ܴ....;
FC140000 68DEC806 90AC190D D4895101 25000000 40DEC677 40DCB406 19D1C877 ...hŞ....ԉQ.%[email protected]Ş[email protected]ܴ..w;
68DEC806 40DEC677 00000000 19D1C877 00000000 80C9090F 40DCB406 10A25101 hŞ[email protected]Şw.....w..... [email protected]ܴ..Q.;
00000000 B0C9090F 00000000 A8A15101 00000000 00000000 C8F47906 C6A9DF00 .... .....Q.........y.Ʃ.;
00000000 D0C9090F 10AC190D 78B0190D FC140000 68DEC806 00AD190D D4895101 ....Ğ ....x.....hŞ..*..ԉQ.;
25000000 40DEC677 40DCB406 19D1C877 68DEC806 40DEC677 00000000 19D1C877 %[email protected]Ş[email protected]ܴ..whŞ[email protected]Şw.....w;
Done.


Asiatic Rebel 11-13-2020 14:41

Oppo Realme rmx1971 Lock Remove succesfull, very thanks.

sree krishna 11-17-2020 21:17

Hi, layder

Please Move this thread Sticky
and Remove unwanted post for better understand this topic
and close this thread.

Or Make it Your own Tutorial about this Job and make it new sticky thread.

This will help many users.

Thank you layder for Your Kind support.

layder 11-18-2020 12:16

Quote:

Originally Posted by sree krishna (Post 14269104)
Hi, layder

Please Move this thread Sticky
and Remove unwanted post for better understand this topic
and close this thread.

Or Make it Your own Tutorial about this Job and make it new sticky thread.

This will help many users.

Thank you layder for Your Kind support.

At now we are not find the cause of the problem
We need info from topicstarter for R11 soldering and other resistors nominal

lihua 11-27-2020 05:44

KM8V7001JM-B810 Code: -108 can fix???
 
Very many KM8V7001JM-B810 IC can fix???

EasyJtag Suite Classic ver.: 3.7.0.20 / wxWidgets 3.1.3-W-U started.
OS ver.: Windows 10 (build 17763), 64-bit edition. Admin rights OK
Android Explorer ver:1.0.0.13
Autorun Agent ver:1.0.0.0
Crash Reporting ver:1.4.0.3
eMMC Odin ver:1.0.0.6
QUALCOMM Direct ver:1.0.6671.7138
EasyJTAG SPI Plugin ver:1.1.1.13
Android ADB API ver:2.0.0.0
FTDI API ver:3.2.4.0
LibUSB API ver:1.2.6.0
Visual C++ Runtime ver:10.0.30319.1
Setting box Pinout ...

Box Drivers version: 3.0.0.0
Z3X Card Serial : AACC-XXX , 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 2 serial devices
COM1 ACPI\VEN_PNP&DEV_0501 通信端口 (C
COM14 USB\VID_1781&PID_AAAC&REV_0100&MI_00 Easy Jtag Plus Control Port (COM14)
Selected pinout: GEN2 ISP Pinout
Change EasyJTAG Pinout OK
Z3X EasyJtag Software ver. 3.7.0.20
UFS Socket Info.
Serial: 0123571XXXXXXXXX
Description: EasyJTAG UFS Socket BGA-254 by EasyJTAG 16.01.20

Identify UFS Chip.
UFS Chip Voltage: Low
Can't init device, Code: -108, Reason: UTP: response timeout
VCC: 3302mV
VCCQ2: 1916mV

Chip Info:
Manufacturer: SAMSUNG
ProductName: KM8V7001JM-B810
SerialNumber: 28edb6c0d30b
OemID: SAMSUNG_OEM_ID
Firmware Version: 6.10
UFS Version: 2.1
Done.

layder 12-01-2020 12:38

1 Attachment(s)
KM8V7001JM-B810 solution


22R resistors can buy here: https://aliexpress.com/item/32530914...640x640Q90.jpg

Asiatic Rebel 02-25-2021 10:19

3 Attachment(s)
Hi, layder.
I am all Resistor change with 22 Ohm.
Now Read good. But R11 47 Ohm, this change 22 Ohm?

Thank you layder for Your Kind support.

layder 03-02-2021 10:35

Quote:

Originally Posted by Asiatic Rebel (Post 14340116)
Hi, layder.
I am all Resistor change with 22 Ohm.
Now Read good. But R11 47 Ohm, this change 22 Ohm?

Thank you layder for Your Kind support.

where I write about change anower components?


All times are GMT +1. The time now is 04:45.


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2021 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2017 -

Page generated in 0.17581 seconds with 6 queries

SEO by vBSEO