Samsung SM-G361F repair question [Answered] - GSM-Forum

gera5 · 05-12-2018, 12:19

i can recovery this phone ?

Interface : eMMC
Brand : Samsung
Model : SM-G361F
SRF : C:/Program Files/Medusa Pro Software/firmwareFolder/SAMSUNG_SM-G361F_EMMC.SRF
Voltage : 2.6V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Unknown eMMC M MOR
Page size : 512 B
Block size : 512 B
Block count : 262144
Size : 128.00 MB
---------------------------------------------------------------
CID Info

CID : 65646F4D204D4F5212A1000002400219
Manufacturer ID : 0X65
Device/BGA : Device (removable)
OEM/Application ID : 0X6F
Product name : M MOR
Product revision : 10.1
Product serial number : (hex) 240
Manufacturing date : 00/1999
---------------------------------------------------------------
CSD Info

CSD : D07FFF320F59007FF6DB80001E40001D
CSD structure : CSD version No. 1.0
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 80 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : NO
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.0 (for MMC v4.0)
Erase block size : 0 Kbytes
Boot1 size : 0 Kbytes
Boot2 size : 0 Kbytes
RPMB size : 0 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x00) RST_n signal is temporary disabled (default)

Max enhanced data size: 0 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files/Medusa Pro Software/EXT_CSD Backups/M MOR_12_05_2018_11_40_06.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.9; FW: 1.23.

Medusa Box · 05-12-2018, 13:54

As You can see from your Software log, there is a problem with eMMC - eMMC size (capacity) can't be 128.00 MB:

Quote:

Size : 128.00 MB

also next sizes are also incorrect:

Quote:

Erase block size : 0 Kbytes
Boot1 size : 0 Kbytes
Boot2 size : 0 Kbytes
RPMB size : 0 Kbytes

What is eMMC chip exactly in your devcie (brand, part number)?

gera5 · 05-14-2018, 10:54

eMMC chip
Hynix
H9TQ64ABJTMC

Medusa Box · 05-14-2018, 11:13

Unfortunately, "Repair/Write eMMC firmware" operation is not supported for Hynix eMMC chips. In your case only the solution is a chip replacement.

05-12-2018, 12:19	#1 (permalink)
gera5 Freak Poster Join Date: Oct 2000 Location: Kiev Posts: 188 Member: 2448 Status: Offline Thanks Meter: 5	Samsung SM-G361F repair question [Answered] i can recovery this phone ? Interface : eMMC Brand : Samsung Model : SM-G361F SRF : C:/Program Files/Medusa Pro Software/firmwareFolder/SAMSUNG_SM-G361F_EMMC.SRF Voltage : 2.6V Bus Mode : 1 bit Bus speed : Auto Connecting... Device : Unknown eMMC M MOR Page size : 512 B Block size : 512 B Block count : 262144 Size : 128.00 MB --------------------------------------------------------------- CID Info CID : 65646F4D204D4F5212A1000002400219 Manufacturer ID : 0X65 Device/BGA : Device (removable) OEM/Application ID : 0X6F Product name : M MOR Product revision : 10.1 Product serial number : (hex) 240 Manufacturing date : 00/1999 --------------------------------------------------------------- CSD Info CSD : D07FFF320F59007FF6DB80001E40001D CSD structure : CSD version No. 1.0 SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5, 4.51, 5.0, 5.01, 5.1 Data read access time1: 80 ms TRAN speed : 26 MHz READ block length : 512 Bytes WP group enable : NO PERM_WRITE_PROTECT : NO TMP_WRITE_PROTECT : NO --------------------------------------------------------------- EXTCSD Info Revision 1.0 (for MMC v4.0) Erase block size : 0 Kbytes Boot1 size : 0 Kbytes Boot2 size : 0 Kbytes RPMB size : 0 Kbytes Partition config : (0x00) 00000000 Boot partition enable : Device not boot enabled (default) (Bus width = 1Bit) Boot ACK : No boot acknowledge sent (default) Boot bus conditions : (0x00) 00000000 Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default) Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default) Boot mode : Use single data rate + backward compatible timings in boot operation (default) RST_n function : (0x00) RST_n signal is temporary disabled (default) Max enhanced data size: 0 Kbytes Partitions attribute : 0x0 Part setting completed: 0x0 GP partition 1 size : 0 b GP partition 2 size : 0 b GP partition 3 size : 0 b GP partition 4 size : 0 b Enhanced area size : (0x0) 0 b Enhanced area start : (0x0) 0 b ---------------------------------------------------------------Searching Android build info... Not found --------------------------------------------------------------- Backup EXT_CSD saved to file C:/Program Files/Medusa Pro Software/EXT_CSD Backups/M MOR_12_05_2018_11_40_06.bin. Connect successful. --------------------------------------------------------------- SW: 1.5.9; FW: 1.23. Last edited by Medusa Box; 05-12-2018 at 13:55.

05-14-2018, 10:54	#3 (permalink)
gera5 Freak Poster Join Date: Oct 2000 Location: Kiev Posts: 188 Member: 2448 Status: Offline Thanks Meter: 5	eMMC chip Hynix H9TQ64ABJTMC

05-14-2018, 11:13	#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	Unfortunately, "Repair/Write eMMC firmware" operation is not supported for Hynix eMMC chips. In your case only the solution is a chip replacement.