New BGA254 no connect ic ufs [Answered] - GSM-Forum

thlorkvannak · 10-20-2020, 12:23

i just bought socket BGA254 ufs. it doesn't connect ic ufs at all.What is the problem? How to solve it

Medusa Box · 10-20-2020, 12:43

Hello.

What is the exact model of your UFS/eMMC memory chip?

thlorkvannak · 10-20-2020, 13:04

yes it is correct mark

Medusa Box · 10-20-2020, 13:23

We gonna check with this memory, but make a photo of your socket from both sides and post here. Besides, try to set Gear PWN 1-4 and repeat operation again

thlorkvannak · 10-20-2020, 13:39

Quote:

Originally Posted by Medusa Box

We gonna check with this memory, but make a photo of your socket from both sides and post here. Besides, try to set Gear PWN 1-4 and repeat operation again

Set Gear PWN 1_4 still not connect ic ufs

cinik79 · 10-21-2020, 08:16

Similar problem.

Welcome to Medusa Pro Software version 2.1.4.
Started.
Reader #0: Alcor Micro USB Smart Card Reader 0
Reader #1: Alcor Micro USB Smart Card Reader 1
Reader #2: FT SCR2000 0
Reader #3: FT SCR2000 1
Reader #4: Gemalto e-gate Smart Card 0
Reader #5: Generic EMV Smartcard Reader 0
Loading firmware. Please wait... Done.
Selected UFS interface.
Socket detected!

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : HS Gear 1

Connecting to server. Please wait...
Connection to server successful
Full speed mode!
Connect unsuccessful.
Socket detected!
Socket detected!
Socket detected!

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : PWM Gear 1

Full speed mode!
Connect unsuccessful.

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : PWM Gear 2

Full speed mode!
Connect unsuccessful.

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : PWM Gear 3

Full speed mode!
Connect unsuccessful.

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : PWM Gear 4

Full speed mode!
Connect unsuccessful.

Chip KM8B8001JM-BC01. Phone OPPO Reno2 pass reset need. Chip worked.

Medusa Box · 10-21-2020, 08:37

Hello.

We're know about the problem and researching what may cause it, we'll inform You about possible solutions

cinik79 · 10-24-2020, 23:45

Any solution possible?

Medusa Box · 10-26-2020, 09:17

Quote:

Originally Posted by cinik79

Any solution possible?

Hello.

Please, check your PM

cinik79 · 10-26-2020, 10:46

Thank team for help!

Selected BGA 254 socket.

Model Settings:
Interface : UFS
Gear : PWM Gear 4

Full speed mode!
Connected. Reading information.
Manufacturer name: SAMSUNG
Product name: KM8B8001JM-BC01
Serial Number: 3609fb74c10c
OEM ID: SAMSUNG_OEM_ID
Page size : 4096 B
Block size : 4096 B
Block count : 62486528
Size : 238.37 GB (244088.00 MB)
AttrRefClkFreeq = 0
MaxDataInSize = 4096
MaxDataOutSize = 4096
Connect successful.
---------------------------------------------------------------

Physical partition number: 0

Block count : 61548544 (0x3AB2800)
Size : 234.79 GB (240424.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: ssd (00000006, 00000002) 8 KB
P02: persist (00000008, 00002000) 32 MB
P03: misc (00002008, 00000100) 1024 KB
P04: keystore (00002108, 00000080) 512 KB
P05: frp (00002188, 00000080) 512 KB
P06: cache (00002208, 00010000) 256 MB
P07: system (00012208, 00194000) 6.312 GB
P08: metadata (001A6208, 00001000) 16 MB
P09: odm (001A7208, 00010000) 256 MB
P10: userdata (001B7208, 038FB5F3) 227.9 GB

Physical partition number: 1

Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000380) 3584 KB
P02: xbl_config (00000386, 00000020) 128 KB

Physical partition number: 2

Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xblbak (00000006, 00000380) 3584 KB
P02: xbl_configbak (00000386, 00000020) 128 KB

Physical partition number: 3

Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ALIGN_TO_128K_1 (00000006, 0000001A) 104 KB
P02: cdt (00000020, 00000020) 128 KB
P03: ddr (00000040, 00000100) 1024 KB

Physical partition number: 4

Block count : 851968 (0xD0000)
Size : 3328.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: aop (00000006, 00000080) 512 KB
P02: tz (00000086, 00000400) 4 MB
P03: hyp (00000486, 00000080) 512 KB
P04: modem (00000506, 00010000) 256 MB
P05: bluetooth (00010506, 00000100) 1024 KB
P06: mdtpsecapp (00010606, 00000400) 4 MB
P07: mdtp (00010A06, 00002000) 32 MB
P08: abl (00012A06, 00000100) 1024 KB
P09: dsp (00012B06, 00002000) 32 MB
P10: keymaster (00014B06, 00000080) 512 KB
P11: boot (00014B86, 00004000) 64 MB
P12: cmnlib (00018B86, 00000080) 512 KB
P13: cmnlib64 (00018C06, 00000080) 512 KB
P14: devcfg (00018C86, 00000020) 128 KB
P15: qupfw (00018CA6, 00000010) 64 KB
P16: vendor (00018CB6, 0008C000) 2240 MB
P17: vbmeta (000A4CB6, 00000010) 64 KB
P18: dtbo (000A4CC6, 00001800) 24 MB
P19: imagefv (000A64C6, 00000200) 2048 KB
P20: uefisecapp (000A66C6, 00000200) 2048 KB
P21: recovery (000A68C6, 00006000) 96 MB
P22: oppo_sec (000AC8C6, 00000A00) 10 MB
P23: aopbak (000AD2C6, 00000080) 512 KB
P24: tzbak (000AD346, 00000400) 4 MB
P25: hypbak (000AD746, 00000080) 512 KB
P26: bluetoothbak (000AD7C6, 00000100) 1024 KB
P27: mdtpsecappbak (000AD8C6, 00000400) 4 MB
P28: mdtpbak (000ADCC6, 00002000) 32 MB
P29: ablbak (000AFCC6, 00000100) 1024 KB
P30: dspbak (000AFDC6, 00002000) 32 MB
P31: keymasterbak (000B1DC6, 00000080) 512 KB
P32: bootbak (000B1E46, 00004000) 64 MB
P33: cmnlibbak (000B5E46, 00000080) 512 KB
P34: cmnlib64bak (000B5EC6, 00000080) 512 KB
P35: devcfgbak (000B5F46, 00000020) 128 KB
P36: qupfwbak (000B5F66, 00000010) 64 KB
P37: vbmetabak (000B5F76, 00000010) 64 KB
P38: dtbobak (000B5F86, 00001800) 24 MB
P39: imagefvbak (000B7786, 00000200) 2048 KB
P40: uefisecappbak (000B7986, 00000200) 2048 KB
P41: recoverybak (000B7B86, 00006000) 96 MB
P42: devinfo (000BDB86, 00000001) 4 KB
P43: dip (000BDB87, 00000100) 1024 KB
P44: apdp (000BDC87, 00000040) 256 KB
P45: msadp (000BDCC7, 00000040) 256 KB
P46: spunvm (000BDD07, 00000800) 8 MB
P47: splash (000BE507, 000020A4) 32.64 MB
P48: limits (000C05AB, 00000001) 4 KB
P49: toolsfv (000C05AC, 00000100) 1024 KB
P50: logfs (000C06AC, 00000800) 8 MB
P51: cateloader (000C0EAC, 00000200) 2048 KB
P52: rawdump (000C10AC, 00008000) 128 MB
P53: logdump (000C90AC, 00004000) 64 MB
P54: storsec (000CD0AC, 00000020) 128 KB
P55: multiimgoem (000CD0CC, 00000008) 32 KB
P56: multiimgqti (000CD0D4, 00000008) 32 KB
P57: uefivarstore (000CD0DC, 00000080) 512 KB
P58: secdata (000CD15C, 00000007) 28 KB
P59: catefv (000CD163, 00000080) 512 KB
P60: catecontentfv (000CD1E3, 00000100) 1024 KB

Physical partition number: 5

Block count : 65536 (0x10000)
Size : 256.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ALIGN_TO_128K_2 (00000006, 0000001A) 104 KB
P02: oppodycnvbk (00000020, 00000A00) 10 MB
P03: oppostanvbk (00000A20, 00000A00) 10 MB
P04: modemst1 (00001420, 00000200) 2048 KB
P05: modemst2 (00001620, 00000200) 2048 KB
P06: opporeserve1 (00001820, 00000800) 8 MB
P07: opporeserve2 (00002020, 00004000) 64 MB
P08: opporeserve3 (00006020, 00004000) 64 MB
P09: DRIVER (0000A020, 00002000) 32 MB
P10: fsg (0000C020, 00000200) 2048 KB
P11: fsc (0000C220, 00000020) 128 KB
RPMB: Counter of the successful data write requests = 30515.
Reset operation finished

Fast Unlocker · 10-30-2020, 09:31

it is gear problem we just have to change gear speed

lihua · 11-29-2020, 01:21

Quote:

Originally Posted by Medusa Box

Hello.

Please, check your PM

Chip KM8B8001JM-BC01 socket BGA254 ufs doesn't connect ic ufs??? How do??? Thank you!!

lihua · 11-29-2020, 01:32

My new 254 bga-ufs cannot be connected
Chip KM8B8001JM-BC01
Chip KM8B8001CM-BB01
Chip KM8B80018V-B813
Chip skhynix H9HQ16AECMMDAR

Medusa Box · 11-30-2020, 09:41

@lihua
Please, try to add this short BGA254 Fix then repeat operation with fixed socket and give us a result

chalakgogani · 07-08-2021, 23:34

I have same problem and can’t connect ufs 254 with medusa pro 2 and esocket.
Please help me

10-20-2020, 12:43	#2 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,398	Hello. What is the exact model of your UFS/eMMC memory chip?

10-20-2020, 13:23	#4 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,398	We gonna check with this memory, but make a photo of your socket from both sides and post here. Besides, try to set Gear PWN 1-4 and repeat operation again

10-21-2020, 08:16	#6 (permalink)
cinik79 Freak Poster Join Date: Jul 2010 Location: Ukraine, Kharkiv Posts: 100 Member: 1350761 Status: Offline Thanks Meter: 24	Similar problem. Welcome to Medusa Pro Software version 2.1.4. Started. Reader #0: Alcor Micro USB Smart Card Reader 0 Reader #1: Alcor Micro USB Smart Card Reader 1 Reader #2: FT SCR2000 0 Reader #3: FT SCR2000 1 Reader #4: Gemalto e-gate Smart Card 0 Reader #5: Generic EMV Smartcard Reader 0 Loading firmware. Please wait... Done. Selected UFS interface. Socket detected! Selected BGA 254 socket. Model Settings: Interface : UFS Gear : HS Gear 1 Connecting to server. Please wait... Connection to server successful Full speed mode! Connect unsuccessful. Socket detected! Socket detected! Socket detected! Selected BGA 254 socket. Model Settings: Interface : UFS Gear : PWM Gear 1 Full speed mode! Connect unsuccessful. Selected BGA 254 socket. Model Settings: Interface : UFS Gear : PWM Gear 2 Full speed mode! Connect unsuccessful. Selected BGA 254 socket. Model Settings: Interface : UFS Gear : PWM Gear 3 Full speed mode! Connect unsuccessful. Selected BGA 254 socket. Model Settings: Interface : UFS Gear : PWM Gear 4 Full speed mode! Connect unsuccessful. Chip KM8B8001JM-BC01. Phone OPPO Reno2 pass reset need. Chip worked.

10-21-2020, 08:37	#7 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,398	Hello. We're know about the problem and researching what may cause it, we'll inform You about possible solutions

10-24-2020, 23:45	#8 (permalink)
cinik79 Freak Poster Join Date: Jul 2010 Location: Ukraine, Kharkiv Posts: 100 Member: 1350761 Status: Offline Thanks Meter: 24	Any solution possible?

10-26-2020, 10:46	#10 (permalink)
cinik79 Freak Poster Join Date: Jul 2010 Location: Ukraine, Kharkiv Posts: 100 Member: 1350761 Status: Offline Thanks Meter: 24	Thank team for help! Selected BGA 254 socket. Model Settings: Interface : UFS Gear : PWM Gear 4 Full speed mode! Connected. Reading information. Manufacturer name: SAMSUNG Product name: KM8B8001JM-BC01 Serial Number: 3609fb74c10c OEM ID: SAMSUNG_OEM_ID Page size : 4096 B Block size : 4096 B Block count : 62486528 Size : 238.37 GB (244088.00 MB) AttrRefClkFreeq = 0 MaxDataInSize = 4096 MaxDataOutSize = 4096 Connect successful. --------------------------------------------------------------- Physical partition number: 0 Block count : 61548544 (0x3AB2800) Size : 234.79 GB (240424.00 MB) P00: GPT (00000000, 00000006) 24 KB P01: ssd (00000006, 00000002) 8 KB P02: persist (00000008, 00002000) 32 MB P03: misc (00002008, 00000100) 1024 KB P04: keystore (00002108, 00000080) 512 KB P05: frp (00002188, 00000080) 512 KB P06: cache (00002208, 00010000) 256 MB P07: system (00012208, 00194000) 6.312 GB P08: metadata (001A6208, 00001000) 16 MB P09: odm (001A7208, 00010000) 256 MB P10: userdata (001B7208, 038FB5F3) 227.9 GB Physical partition number: 1 Block count : 2048 (0x800) Size : 8.00 MB P00: GPT (00000000, 00000006) 24 KB P01: xbl (00000006, 00000380) 3584 KB P02: xbl_config (00000386, 00000020) 128 KB Physical partition number: 2 Block count : 2048 (0x800) Size : 8.00 MB P00: GPT (00000000, 00000006) 24 KB P01: xblbak (00000006, 00000380) 3584 KB P02: xbl_configbak (00000386, 00000020) 128 KB Physical partition number: 3 Block count : 8192 (0x2000) Size : 32.00 MB P00: GPT (00000000, 00000006) 24 KB P01: ALIGN_TO_128K_1 (00000006, 0000001A) 104 KB P02: cdt (00000020, 00000020) 128 KB P03: ddr (00000040, 00000100) 1024 KB Physical partition number: 4 Block count : 851968 (0xD0000) Size : 3328.00 MB P00: GPT (00000000, 00000006) 24 KB P01: aop (00000006, 00000080) 512 KB P02: tz (00000086, 00000400) 4 MB P03: hyp (00000486, 00000080) 512 KB P04: modem (00000506, 00010000) 256 MB P05: bluetooth (00010506, 00000100) 1024 KB P06: mdtpsecapp (00010606, 00000400) 4 MB P07: mdtp (00010A06, 00002000) 32 MB P08: abl (00012A06, 00000100) 1024 KB P09: dsp (00012B06, 00002000) 32 MB P10: keymaster (00014B06, 00000080) 512 KB P11: boot (00014B86, 00004000) 64 MB P12: cmnlib (00018B86, 00000080) 512 KB P13: cmnlib64 (00018C06, 00000080) 512 KB P14: devcfg (00018C86, 00000020) 128 KB P15: qupfw (00018CA6, 00000010) 64 KB P16: vendor (00018CB6, 0008C000) 2240 MB P17: vbmeta (000A4CB6, 00000010) 64 KB P18: dtbo (000A4CC6, 00001800) 24 MB P19: imagefv (000A64C6, 00000200) 2048 KB P20: uefisecapp (000A66C6, 00000200) 2048 KB P21: recovery (000A68C6, 00006000) 96 MB P22: oppo_sec (000AC8C6, 00000A00) 10 MB P23: aopbak (000AD2C6, 00000080) 512 KB P24: tzbak (000AD346, 00000400) 4 MB P25: hypbak (000AD746, 00000080) 512 KB P26: bluetoothbak (000AD7C6, 00000100) 1024 KB P27: mdtpsecappbak (000AD8C6, 00000400) 4 MB P28: mdtpbak (000ADCC6, 00002000) 32 MB P29: ablbak (000AFCC6, 00000100) 1024 KB P30: dspbak (000AFDC6, 00002000) 32 MB P31: keymasterbak (000B1DC6, 00000080) 512 KB P32: bootbak (000B1E46, 00004000) 64 MB P33: cmnlibbak (000B5E46, 00000080) 512 KB P34: cmnlib64bak (000B5EC6, 00000080) 512 KB P35: devcfgbak (000B5F46, 00000020) 128 KB P36: qupfwbak (000B5F66, 00000010) 64 KB P37: vbmetabak (000B5F76, 00000010) 64 KB P38: dtbobak (000B5F86, 00001800) 24 MB P39: imagefvbak (000B7786, 00000200) 2048 KB P40: uefisecappbak (000B7986, 00000200) 2048 KB P41: recoverybak (000B7B86, 00006000) 96 MB P42: devinfo (000BDB86, 00000001) 4 KB P43: dip (000BDB87, 00000100) 1024 KB P44: apdp (000BDC87, 00000040) 256 KB P45: msadp (000BDCC7, 00000040) 256 KB P46: spunvm (000BDD07, 00000800) 8 MB P47: splash (000BE507, 000020A4) 32.64 MB P48: limits (000C05AB, 00000001) 4 KB P49: toolsfv (000C05AC, 00000100) 1024 KB P50: logfs (000C06AC, 00000800) 8 MB P51: cateloader (000C0EAC, 00000200) 2048 KB P52: rawdump (000C10AC, 00008000) 128 MB P53: logdump (000C90AC, 00004000) 64 MB P54: storsec (000CD0AC, 00000020) 128 KB P55: multiimgoem (000CD0CC, 00000008) 32 KB P56: multiimgqti (000CD0D4, 00000008) 32 KB P57: uefivarstore (000CD0DC, 00000080) 512 KB P58: secdata (000CD15C, 00000007) 28 KB P59: catefv (000CD163, 00000080) 512 KB P60: catecontentfv (000CD1E3, 00000100) 1024 KB Physical partition number: 5 Block count : 65536 (0x10000) Size : 256.00 MB P00: GPT (00000000, 00000006) 24 KB P01: ALIGN_TO_128K_2 (00000006, 0000001A) 104 KB P02: oppodycnvbk (00000020, 00000A00) 10 MB P03: oppostanvbk (00000A20, 00000A00) 10 MB P04: modemst1 (00001420, 00000200) 2048 KB P05: modemst2 (00001620, 00000200) 2048 KB P06: opporeserve1 (00001820, 00000800) 8 MB P07: opporeserve2 (00002020, 00004000) 64 MB P08: opporeserve3 (00006020, 00004000) 64 MB P09: DRIVER (0000A020, 00002000) 32 MB P10: fsg (0000C020, 00000200) 2048 KB P11: fsc (0000C220, 00000020) 128 KB RPMB: Counter of the successful data write requests = 30515. Reset operation finished

10-30-2020, 09:31	#11 (permalink)
Fast Unlocker Product Supporter Join Date: Dec 2004 Location: Furious Team ... GPGIndustries Age: 45 Posts: 10,341 Member: 95960 Status: Offline Sonork: 100.1574721 Thanks Meter: 14,047	it is gear problem we just have to change gear speed

11-29-2020, 01:32	#13 (permalink)
lihua No Life Poster Join Date: Nov 2006 Location: GOOD Posts: 1,235 Member: 388862 Status: Offline Thanks Meter: 107	My new 254 bga-ufs cannot be connected Chip KM8B8001JM-BC01 Chip KM8B8001CM-BB01 Chip KM8B80018V-B813 Chip skhynix H9HQ16AECMMDAR

11-30-2020, 09:41	#14 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,398	@lihua Please, try to add this short BGA254 Fix then repeat operation with fixed socket and give us a result

07-08-2021, 23:34	#15 (permalink)
chalakgogani Junior Member Join Date: Jan 2015 Posts: 1 Member: 2335171 Status: Offline Thanks Meter: 0	I have same problem and can’t connect ufs 254 with medusa pro 2 and esocket. Please help me