UFS memory connection troubles, question, discuss thread - Page 19 - GSM-Forum

giaguaro · 07-13-2023, 08:01

Hello, need help with isp ufs connection , sm-g991B connection like photos.erro log attached (bga254 socket tested with some ufs in socket reads well, and tested isp on g975f also reads ok). RST pin connected to VCCQ on , the only mds I've done to the socket was bypass R4 and R4 . resistors are all 47ohm (tryed with 22 ohm, same result)

Looking for EasyJTAG box...
EasyJTAG API ver. 3403
EasyJTAG Box Serial = 8AB721F96FE227FD
Card Serial = AA04DC7D
EasyJTAG Box Firmware = 2,5301

Changelog:
05-05-2021 (ver 1.6.6.0)

Add: New keys for Oppo unpack
Fix: Bugs that have been found through your crash report

05.05.2021 (ver 2.0.1.0)

Add: Vendor LG
Add: Mediatek Preloader Parser
Add: OnePlus Unpacker
Add: Xiaomi Custom EDL Authorization
Add: Xiaomi Remove Mi Account (only Qualcomm)

No updates

Operation: Connect to Z3X EasyJtagPlus

Setting Interface to EasyJtag2/UFS ISP
Setting IO Levels to Low
Setting Frequence to 66 Mhz

Socket Information :
Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22
Socket Serial: 01236C2CE1A37786EE
Socket Type: UFS_SOCKET_BGA_254

Can't init device. Error: -57. Reason: Unknown error: -57

Operation: Connect to Z3X EasyJtagPlus

Setting Interface to EasyJtag2/UFS ISP
Setting IO Levels to Low
Setting Frequence to 66 Mhz

Socket Information :
Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22
Socket Serial: 01236C2CE1A37786EE
Socket Type: UFS_SOCKET_BGA_254

Can't init device. Error: -57. Reason: Unknown error: -57

Operation: Connect to Z3X EasyJtagPlus

Setting Interface to EasyJtag2/UFS ISP
Setting IO Levels to Low
Setting Frequence to 66 Mhz

Socket Information :
Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22
Socket Serial: 01236C2CE1A37786EE
Socket Type: UFS_SOCKET_BGA_254

Can't init device. Error: -56. Reason: Unknown error: -56

Operation: Connect to Z3X EasyJtagPlus

Setting Interface to EasyJtag2/UFS ISP
Setting IO Levels to Low
Setting Frequence to 66 Mhz

UFS Init Failed. Error: -113. Reason: Unknown error: -113

Operation: Connect to Z3X EasyJtagPlus

Setting Interface to EasyJtag2/UFS ISP
Setting IO Levels to Low
Setting Frequence to 66 Mhz

Socket Information :
Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22
Socket Serial: 01236C2CE1A37786EE
Socket Type: UFS_SOCKET_BGA_254

Can't init device. Error: -57. Reason: Unknown error: -57

https://ibb.co/LRMgsmh
https://ibb.co/0cv3HRF
https://ibb.co/YLSxfbZ

mkalam · 05-05-2024, 11:08

when I want to connect handset with isp through bga254 socket i m getting this error..
here is log
Found 2 serial devices
COM26 USB\VID_1781&PID_AAAC&REV_0100&MI_00 USB Serial Device (COM26)
COM21 USB\VID_05C6&PID_9008&REV_0000 Qualcomm HS-USB QDLoader 9008 (COM21)
Selected pinout: GEN2 ISP Pinout
Change EasyJTAG Pinout OK
Z3X EasyJtag Software ver. 3.8.0.6
UFS Socket Info.
Serial: 01231C74D1C62752EE
Can't open link, Code: -56, Reason: BOX: Chip not connected
Done.
Z3X EasyJtag Software ver. 3.8.0.6

please tell me where I'm wrong or there is any problem with socket.
I'm using rxop txop rxon txon and gnd and for vcc and vccq using cable for samsung A236e

mkalam · 05-06-2024, 07:44

Quote:

Originally Posted by mkalam

when I want to connect handset with isp through bga254 socket i m getting this error..
here is log
Found 2 serial devices
COM26 USB\VID_1781&PID_AAAC&REV_0100&MI_00 USB Serial Device (COM26)
COM21 USB\VID_05C6&PID_9008&REV_0000 Qualcomm HS-USB QDLoader 9008 (COM21)
Selected pinout: GEN2 ISP Pinout
Change EasyJTAG Pinout OK
Z3X EasyJtag Software ver. 3.8.0.6
UFS Socket Info.
Serial: 01231C74D1C62752EE
Can't open link, Code: -56, Reason: BOX: Chip not connected
Done.
Z3X EasyJtag Software ver. 3.8.0.6

please tell me where I'm wrong or there is any problem with socket.
I'm using rxop txop rxon txon and gnd and for vcc and vccq using cable for samsung A236e

@layder please reply

layder · 05-06-2024, 15:44

to connect eMMC chip we need:
1) GND line
2) VDD (2.8, 3,3) - main chip power
2) VDDQ (1,8, 2.8) - for logic levers same as CPU

and at least three lines are required for operation.

4) reference frequency - clock (CLK)
5) command line - CMD
6) and data lines (1-4-8)

CLK and CMD work in pairs, through them commands are sent to the chip.
Data lines are used for data exchange

Accordingly, we have 2 main errors in eMMC connectiong:
1) CMD Timeout error - chip not answer to Command line
2) Data line error - not connect D0 line

At UFS chip all are different and more complicated

Fist different:

We need from 2 to 3 power VDD lines
We need same 1-2 VDDI capacitors
and some chips have few blocks of memory, and his power may be not connected at inside of chip. at this chips need 2-4 soder wires for one VDD lene and many GND lines

Second:
1) UFS chip use 4/8 lines for data (like Ethernet) - 2/4 for TX and 2/4 for RX
2) for 1Ghz (HS - High speed mode) connection need use CLK (not use at Z3x EasyJTAG Plus box)

when box try to conect to UFS chip at first it need "open link" for this use small freq (I'm not sure, like 1-4 Mhz) and 4 lines TX/RX
after box set UFS chip to LS (Low Speed) mode (Z3x box use LS4 mode, 66Mhz)
at this mode CLK line not use

-56 error - is main UFS error, box can not established base connect with UFS chip (like at eMMC - "CMD Timeout error")

some UFS chip need connect CLK line to Ground for set UFS chip to LS mode

some UFS chip need connect RST line to 1.8v for RST line set not be active

some UFS chips like UFS 4.0 need additional power for chip and UFS sockets adapter needs to be modified

at usially you need understand, what probles at you case

but I cant understand you case (type of connection, type of UFS chips, etc).

mkalam · 05-14-2024, 15:56

Quote:

Originally Posted by layder

you use socket or wires connection?
it's may be prroblem with first moorc revisions ufs socket - it's no so good

Layder I'm using wires connection and I'm getting same error when I'm writing bl file for A528B bit-1. Repartioning not done everytime error.
It was also happening when I was writing fsg partition.
also getting error when erasing luns.

here is log

Operation: Writing by Vendor (Samsung)
Write/Erase check: Disabled
BlockSize: Auto

Unpacking files into: C:\Program Files\Z3X\EASYJTAGPLUS\Temp\
Unpacking : dspso.bin.lz4
Unpacking : dspso.bin
Unpacking : NON-HLOS.bin.lz4
Unpacking : NON-HLOS.bin
Unpacking : xbl.elf.lz4
Unpacking : xbl.elf
Unpacking : xbl_config.elf.lz4
Unpacking : xbl_config.elf
Unpacking : aop.mbn.lz4
Unpacking : aop.mbn
Unpacking : tz.mbn.lz4
Unpacking : tz.mbn
Unpacking : hypvm.mbn.lz4
Unpacking : hypvm.mbn
Unpacking : abl.elf.lz4
Unpacking : abl.elf
Unpacking : km41.mbn.lz4
Unpacking : km41.mbn
Unpacking : devcfg.mbn.lz4
Unpacking : devcfg.mbn
Unpacking : qupv3fw.elf.lz4
Unpacking : qupv3fw.elf
Unpacking : cpucp.elf.lz4
Unpacking : cpucp.elf
Unpacking : quest.fv.lz4
Unpacking : quest.fv
Unpacking : testvector.fv.lz4
Unpacking : testvector.fv
Unpacking : storsec.mbn.lz4
Unpacking : storsec.mbn
Unpacking : vbmeta.img.lz4
Unpacking : vbmeta.img
Unpacking : uefi_sec.mbn.lz4
Unpacking : uefi_sec.mbn
Unpacking : imagefv.elf.lz4
Unpacking : imagefv.elf
Unpacking : shrm.elf.lz4
Unpacking : shrm.elf
Unpacking : apdp.mbn.lz4
Unpacking : apdp.mbn
Unpacking : sec.elf.lz4
Unpacking : sec.elf
Unpacking : bksecapp.mbn.lz4
Unpacking : bksecapp.mbn
Unpacking : vaultkeeper.mbn.lz4
Unpacking : vaultkeeper.mbn
Unpacking : tz_iccc.mbn.lz4
Unpacking : tz_iccc.mbn
Unpacking : tz_hdm.mbn.lz4
Unpacking : tz_hdm.mbn
Unpacking : tz_kg.mbn.lz4
Unpacking : tz_kg.mbn
Unpacking done

Backuping a partition table. Please, wait ...
Backup path: \Backups\PartitionTable\PartitionTable_20240514_20 1725\
Backuping done

Repartitioning ...
Rom: LUN 0, Part: PrimaryGPT, Address: 000000000000, Filename: From Memory
Rom: LUN 0, Part: BackupGPT, Address: 001DA8BFB000, Filename: From Memory
Rom: LUN 1 (Main Boot A), Part: PrimaryGPT, Address: 000000000000, Filename: From Memory
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #1
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #2
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #3

Repartition failed. Operation canceled

it is the problem because of wires connection or something else..RXON wire is thin other than all wires because print on board was broken mistakenly so I scrached print and paste the thin wire on that so it is the problem with that??

SAJONDUTTA · 05-15-2024, 08:37

oppo a53 cph2127 hang on logo after flash use emmc file manager flash success but set dead ufs

mkalam · 05-15-2024, 10:09

Quote:

Originally Posted by SAJONDUTTA

oppo a53 cph2127 hang on logo after flash use emmc file manager flash success but set dead ufs

1.Read Dump ( Read lun0 1gb and 1 2 3 4 5 full)
2.Read Chip Config
3.Erase All Luns
4.Write Chip Config
5.Write Dump
6.Write flash file via usb or in jtag

Done ✅

mkalam · 05-16-2024, 08:42

Quote:

Originally Posted by mkalam

Layder I'm using wires connection and I'm getting same error when I'm writing bl file for A528B bit-1. Repartioning not done everytime error.
It was also happening when I was writing fsg partition.
also getting error when erasing luns.

here is log

Operation: Writing by Vendor (Samsung)
Write/Erase check: Disabled
BlockSize: Auto

Unpacking files into: C:\Program Files\Z3X\EASYJTAGPLUS\Temp\
Unpacking : dspso.bin.lz4
Unpacking : dspso.bin
Unpacking : NON-HLOS.bin.lz4
Unpacking : NON-HLOS.bin
Unpacking : xbl.elf.lz4
Unpacking : xbl.elf
Unpacking : xbl_config.elf.lz4
Unpacking : xbl_config.elf
Unpacking : aop.mbn.lz4
Unpacking : aop.mbn
Unpacking : tz.mbn.lz4
Unpacking : tz.mbn
Unpacking : hypvm.mbn.lz4
Unpacking : hypvm.mbn
Unpacking : abl.elf.lz4
Unpacking : abl.elf
Unpacking : km41.mbn.lz4
Unpacking : km41.mbn
Unpacking : devcfg.mbn.lz4
Unpacking : devcfg.mbn
Unpacking : qupv3fw.elf.lz4
Unpacking : qupv3fw.elf
Unpacking : cpucp.elf.lz4
Unpacking : cpucp.elf
Unpacking : quest.fv.lz4
Unpacking : quest.fv
Unpacking : testvector.fv.lz4
Unpacking : testvector.fv
Unpacking : storsec.mbn.lz4
Unpacking : storsec.mbn
Unpacking : vbmeta.img.lz4
Unpacking : vbmeta.img
Unpacking : uefi_sec.mbn.lz4
Unpacking : uefi_sec.mbn
Unpacking : imagefv.elf.lz4
Unpacking : imagefv.elf
Unpacking : shrm.elf.lz4
Unpacking : shrm.elf
Unpacking : apdp.mbn.lz4
Unpacking : apdp.mbn
Unpacking : sec.elf.lz4
Unpacking : sec.elf
Unpacking : bksecapp.mbn.lz4
Unpacking : bksecapp.mbn
Unpacking : vaultkeeper.mbn.lz4
Unpacking : vaultkeeper.mbn
Unpacking : tz_iccc.mbn.lz4
Unpacking : tz_iccc.mbn
Unpacking : tz_hdm.mbn.lz4
Unpacking : tz_hdm.mbn
Unpacking : tz_kg.mbn.lz4
Unpacking : tz_kg.mbn
Unpacking done

Backuping a partition table. Please, wait ...
Backup path: \Backups\PartitionTable\PartitionTable_20240514_20 1725\
Backuping done

Repartitioning ...
Rom: LUN 0, Part: PrimaryGPT, Address: 000000000000, Filename: From Memory
Rom: LUN 0, Part: BackupGPT, Address: 001DA8BFB000, Filename: From Memory
Rom: LUN 1 (Main Boot A), Part: PrimaryGPT, Address: 000000000000, Filename: From Memory
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #1
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #2
Error writing at address: 000000000000 , error: -407, UAP SCSI: Command sense: DATA_PROTECT ... Retry #3

Repartition failed. Operation canceled

it is the problem because of wires connection or something else..RXON wire is thin other than all wires because print on board was broken mistakenly so I scrached print and paste the thin wire on that so it is the problem with that??

@Layder plzz reply..

akamah · 05-18-2024, 16:56

easy jtag ufs worth nothing
buying easy jtag is a waste of money

akamah · 05-20-2024, 17:07

Z3X EasyJtag Software ver. 3.8.0.6
UFS Safe Mode is disabled...
UFS Socket Info.
Serial: 01234C99C71B4FB6EE
Identify UFS Chip.
UFS Chip Voltage: Low
VCC: 3293mV
VCCQ2: 1922mV
Chip Info:
Manufacturer: SKhynix
ProductName: H9HQ53AECMMDAR
SerialNumber: 0x0D9920187AA7
OemID: 01AD
Firmware Version: 0.04
UFS Reference Clock: 19.2MHz
UFS Version: 2.1
Maximum Number of LUs: 32
Number of LUs found: 6
LUN 0:
Block size: 0x1000
Size: 0xE98800000 / 58,392,000,000B / 58GB
LUN 1 (Main Boot A):
Block size: 0x1000
Size: 0x800000 / 0,008,000,000B / 8MB
LUN 2 (Boot B):
Block size: 0x1000
Size: 0x800000 / 0,008,000,000B / 8MB
LUN 3:
Block size: 0x1000
Size: 0x2000000 / 0,032,000,000B / 32MB
LUN 4:
Block size: 0x1000
Size: 0x40000000 / 1,000,000,000B / 1GB
LUN 5:
Block size: 0x1000
Size: 0xA000000 / 0,160,000,000B / 160MB
Number of W-LUs found: 1
W-LUN 0xC4 (RPMB):
Block size: 0x100
Size: 0x1000000 / 0,016,000,000B / 16MB
Full size: 0xEE6800000 / 59,616,000,000B / 59GB
RPMB:
Counter: 6488
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)
Write UFS Firmware.
Input file :C:\Program Files\Z3X\EASYJTAG\UFS Firmware\SKhynix-H9HQ53AECMMDAR.bin
Chip already has newest firmware
Update Firmware
Can't write firmware to chip, Code: -405, Reason: UAP SCSI: Command sense: ILLEGAL_REQUEST
Done.

Phoenix 254 · 05-29-2024, 18:52

Hi guys I keep getting error can't init device error 56 ufs how to solve issue?

07-13-2023, 08:01	#271 (permalink)
giaguaro Insane Poster Join Date: Jan 2008 Location: California USA Posts: 74 Member: 693376 Status: Offline Thanks Meter: 5	sm-g991b ufs isp connection error with bga254 socket Hello, need help with isp ufs connection , sm-g991B connection like photos.erro log attached (bga254 socket tested with some ufs in socket reads well, and tested isp on g975f also reads ok). RST pin connected to VCCQ on , the only mds I've done to the socket was bypass R4 and R4 . resistors are all 47ohm (tryed with 22 ohm, same result) Looking for EasyJTAG box... EasyJTAG API ver. 3403 EasyJTAG Box Serial = 8AB721F96FE227FD Card Serial = AA04DC7D EasyJTAG Box Firmware = 2,5301 Changelog: 05-05-2021 (ver 1.6.6.0) Add: New keys for Oppo unpack Fix: Bugs that have been found through your crash report 05.05.2021 (ver 2.0.1.0) Add: Vendor LG Add: Mediatek Preloader Parser Add: OnePlus Unpacker Add: Xiaomi Custom EDL Authorization Add: Xiaomi Remove Mi Account (only Qualcomm) No updates Operation: Connect to Z3X EasyJtagPlus Setting Interface to EasyJtag2/UFS ISP Setting IO Levels to Low Setting Frequence to 66 Mhz Socket Information : Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22 Socket Serial: 01236C2CE1A37786EE Socket Type: UFS_SOCKET_BGA_254 Can't init device. Error: -57. Reason: Unknown error: -57 Operation: Connect to Z3X EasyJtagPlus Setting Interface to EasyJtag2/UFS ISP Setting IO Levels to Low Setting Frequence to 66 Mhz Socket Information : Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22 Socket Serial: 01236C2CE1A37786EE Socket Type: UFS_SOCKET_BGA_254 Can't init device. Error: -57. Reason: Unknown error: -57 Operation: Connect to Z3X EasyJtagPlus Setting Interface to EasyJtag2/UFS ISP Setting IO Levels to Low Setting Frequence to 66 Mhz Socket Information : Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22 Socket Serial: 01236C2CE1A37786EE Socket Type: UFS_SOCKET_BGA_254 Can't init device. Error: -56. Reason: Unknown error: -56 Operation: Connect to Z3X EasyJtagPlus Setting Interface to EasyJtag2/UFS ISP Setting IO Levels to Low Setting Frequence to 66 Mhz UFS Init Failed. Error: -113. Reason: Unknown error: -113 Operation: Connect to Z3X EasyJtagPlus Setting Interface to EasyJtag2/UFS ISP Setting IO Levels to Low Setting Frequence to 66 Mhz Socket Information : Socket Mark: EasyJTAG UFS Socket BGA-254 by EasyJTAG 12.10.22 Socket Serial: 01236C2CE1A37786EE Socket Type: UFS_SOCKET_BGA_254 Can't init device. Error: -57. Reason: Unknown error: -57 https://ibb.co/LRMgsmh https://ibb.co/0cv3HRF https://ibb.co/YLSxfbZ Last edited by giaguaro; 07-13-2023 at 08:06.

05-05-2024, 11:08	#272 (permalink)
mkalam Junior Member Join Date: Sep 2016 Location: UP,India Posts: 21 Member: 2621650 Status: Offline Thanks Meter: 0	ufs254 socket isp problem when I want to connect handset with isp through bga254 socket i m getting this error.. here is log Found 2 serial devices COM26 USB\VID_1781&PID_AAAC&REV_0100&MI_00 USB Serial Device (COM26) COM21 USB\VID_05C6&PID_9008&REV_0000 Qualcomm HS-USB QDLoader 9008 (COM21) Selected pinout: GEN2 ISP Pinout Change EasyJTAG Pinout OK Z3X EasyJtag Software ver. 3.8.0.6 UFS Socket Info. Serial: 01231C74D1C62752EE Can't open link, Code: -56, Reason: BOX: Chip not connected Done. Z3X EasyJtag Software ver. 3.8.0.6 please tell me where I'm wrong or there is any problem with socket. I'm using rxop txop rxon txon and gnd and for vcc and vccq using cable for samsung A236e

05-06-2024, 15:44	#274 (permalink)
layder Product Supporter Join Date: Jun 2002 Location: Belarus Age: 47 Posts: 3,191 Member: 13148 Status: Offline Thanks Meter: 2,952	to connect eMMC chip we need: 1) GND line 2) VDD (2.8, 3,3) - main chip power 2) VDDQ (1,8, 2.8) - for logic levers same as CPU and at least three lines are required for operation. 4) reference frequency - clock (CLK) 5) command line - CMD 6) and data lines (1-4-8) CLK and CMD work in pairs, through them commands are sent to the chip. Data lines are used for data exchange Accordingly, we have 2 main errors in eMMC connectiong: 1) CMD Timeout error - chip not answer to Command line 2) Data line error - not connect D0 line At UFS chip all are different and more complicated Fist different: We need from 2 to 3 power VDD lines We need same 1-2 VDDI capacitors and some chips have few blocks of memory, and his power may be not connected at inside of chip. at this chips need 2-4 soder wires for one VDD lene and many GND lines Second: 1) UFS chip use 4/8 lines for data (like Ethernet) - 2/4 for TX and 2/4 for RX 2) for 1Ghz (HS - High speed mode) connection need use CLK (not use at Z3x EasyJTAG Plus box) when box try to conect to UFS chip at first it need "open link" for this use small freq (I'm not sure, like 1-4 Mhz) and 4 lines TX/RX after box set UFS chip to LS (Low Speed) mode (Z3x box use LS4 mode, 66Mhz) at this mode CLK line not use -56 error - is main UFS error, box can not established base connect with UFS chip (like at eMMC - "CMD Timeout error") some UFS chip need connect CLK line to Ground for set UFS chip to LS mode some UFS chip need connect RST line to 1.8v for RST line set not be active some UFS chips like UFS 4.0 need additional power for chip and UFS sockets adapter needs to be modified at usially you need understand, what probles at you case but I cant understand you case (type of connection, type of UFS chips, etc). Last edited by layder; 05-06-2024 at 15:54.

05-20-2024, 17:07	#280 (permalink)
akamah Freak Poster Join Date: Sep 2018 Location: korea Posts: 130 Member: 2863121 Status: Offline Thanks Meter: 8	SKHYNIX-H9HQ53AECMMDAR ufs firmware update failed Z3X EasyJtag Software ver. 3.8.0.6 UFS Safe Mode is disabled... UFS Socket Info. Serial: 01234C99C71B4FB6EE Identify UFS Chip. UFS Chip Voltage: Low VCC: 3293mV VCCQ2: 1922mV Chip Info: Manufacturer: SKhynix ProductName: H9HQ53AECMMDAR SerialNumber: 0x0D9920187AA7 OemID: 01AD Firmware Version: 0.04 UFS Reference Clock: 19.2MHz UFS Version: 2.1 Maximum Number of LUs: 32 Number of LUs found: 6 LUN 0: Block size: 0x1000 Size: 0xE98800000 / 58,392,000,000B / 58GB LUN 1 (Main Boot A): Block size: 0x1000 Size: 0x800000 / 0,008,000,000B / 8MB LUN 2 (Boot B): Block size: 0x1000 Size: 0x800000 / 0,008,000,000B / 8MB LUN 3: Block size: 0x1000 Size: 0x2000000 / 0,032,000,000B / 32MB LUN 4: Block size: 0x1000 Size: 0x40000000 / 1,000,000,000B / 1GB LUN 5: Block size: 0x1000 Size: 0xA000000 / 0,160,000,000B / 160MB Number of W-LUs found: 1 W-LUN 0xC4 (RPMB): Block size: 0x100 Size: 0x1000000 / 0,016,000,000B / 16MB Full size: 0xEE6800000 / 59,616,000,000B / 59GB RPMB: Counter: 6488 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) Write UFS Firmware. Input file :C:\Program Files\Z3X\EASYJTAG\UFS Firmware\SKhynix-H9HQ53AECMMDAR.bin Chip already has newest firmware Update Firmware Can't write firmware to chip, Code: -405, Reason: UAP SCSI: Command sense: ILLEGAL_REQUEST Done.

05-15-2024, 08:37	#276 (permalink)
SAJONDUTTA No Life Poster Join Date: Dec 2008 Location: bangladesh Posts: 1,919 Member: 926902 Status: Online Sonork: 100.1655575 Thanks Meter: 517	oppo a53 cph2127 hang on logo after flash use emmc file manager flash success but set dead ufs

05-18-2024, 16:56	#279 (permalink)
akamah Freak Poster Join Date: Sep 2018 Location: korea Posts: 130 Member: 2863121 Status: Offline Thanks Meter: 8	easy jtag ufs worth nothing buying easy jtag is a waste of money

05-29-2024, 18:52	#281 (permalink)
Phoenix 254 Junior Member Join Date: Jan 2024 Location: Kenya, kiambu Age: 30 Posts: 1 Member: 3055413 Status: Offline Thanks Meter: 0	Hi guys I keep getting error can't init device error 56 ufs how to solve issue?