SM-G532M repair question [Answered] - GSM-Forum

Camiuu · 07-09-2018, 01:22

Hi everyone, recently i flashed a g532m and it turns into dead boot, casually i bought an octoplus pro box to do that jobs, i followed the steps and now the computer recognizes the phone like "Mediatek usb port (COM #)" my question is... what i have to do now? i cant do nothing more and im a beginner in octoplus, i will preciate any answer.

There's Log info below.

Model Settings:
Interface : eMMC
Brand : Samsung
Model : SM-G532M
SRF : C:/Program Files (x86)/Octoplus Pro JTAG Software/firmwareFolder/SAMSUNG_SM-G532M_EMMC,srf
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Samsung eMMC Q316BB
Page size : 512 B
Block size : 512 B
Block count : 30777344
Size : 14.68 GB (15028.00 MB)
---------------------------------------------------------------
CID Info

CID : 150100513331364242003511CEF0745D
Manufacturer ID : 0X15
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : Q316BB
Product revision : 0.0
Product serial number : (hex) 3511CEF0
Manufacturing date : 07/2017
---------------------------------------------------------------
CSD Info

CSD : D02701320F5903FFF6DBFFEF8E40400D
CSD structure : CSD version No. 1.2
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: 15 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.7 (for MMC v5.0, v5.01)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x48) 01001000
Boot partition enable : Boot partition 1
(Bus width = 1Bit)
Boot ACK : Boot acknowledge sent during boot operation Bit

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 : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 7692288 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 (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/Q316BB_08_07_2018_21_18_37,bin.
Connect successful.
---------------------------------------------------------------
SW: 1.6.3; FW: 1.24.
P00: GPT (00000000, 00002000) 4 MB
P01: bota0 (00002000, 00002000) 4 MB
P02: nvram (00004000, 00004000) 8 MB
P03: lk (00008000, 00001000) 2048 KB
P04: bota1 (00009000, 00001000) 2048 KB
P05: secro (0000A000, 00003800) 7 MB
P06: seccfg (0000D800, 00000400) 512 KB
P07: efuse (0000DC00, 00000400) 512 KB
P08: tee1 (0000E000, 00003000) 6 MB
P09: bota2 (00011000, 00003000) 6 MB
P10: efs (00014000, 00004000) 8 MB
P11: nvdata (00018000, 00010000) 32 MB
P12: param (00028000, 00004000) 8 MB
P13: recovery (0002C000, 00008000) 16 MB
P14: boot (00034000, 00008000) 16 MB
P15: md1img (0003C000, 00010000) 32 MB
P16: md1dsp (0004C000, 00002000) 4 MB
P17: keystore (0004E000, 00004000) 8 MB
P18: omekeystore (00052000, 00001C00) 3584 KB
P19: proinfo (00053C00, 00001400) 2560 KB
P20: para (00055000, 00000400) 512 KB
P21: persistent (00055400, 00000400) 512 KB
P22: steady (00055800, 00000800) 1024 KB
P23: protect1 (00056000, 00004000) 8 MB
P24: protect2 (0005A000, 00004000) 8 MB
P25: reserve2 (0005E000, 00002000) 4 MB
P26: system (00060000, 00604000) 3080 MB
P27: cache (00664000, 000C8000) 400 MB
P28: hidden (0072C000, 0001E000) 60 MB
P29: userdata (0074A000, 0160E000) 11.03 GB

Kind regards!

Medusa Box · 07-09-2018, 04:30

Hi.

Quote:

i followed the steps and now the computer recognizes the phone like "Mediatek usb port (COM #)

You have posted Software log with the device connection info, please also post here full Software log with "Smart Repair" operation, we will check it in details and will advise You what to do the next.

Camiuu · 07-09-2018, 04:46

Quote:

Originally Posted by Medusa Box

Hi.

You have posted Software log with the device connection info, please also post here full Software log with "Smart Repair" operation, we will check it in details and will advise You what to do the next.

Thank you for reply, here goes...

Model Settings:
Interface : eMMC
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Samsung eMMC Q316BB
Page size : 512 B
Block size : 512 B
Block count : 30777344
Size : 14.68 GB (15028.00 MB)
---------------------------------------------------------------
CID Info

CID : 150100513331364242003511CEF0745D
Manufacturer ID : 0X15
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : Q316BB
Product revision : 0.0
Product serial number : (hex) 3511CEF0
Manufacturing date : 07/2017
---------------------------------------------------------------
CSD Info

CSD : D02701320F5903FFF6DBFFEF8E40400D
CSD structure : CSD version No. 1.2
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: 15 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.7 (for MMC v5.0, v5.01)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x48) 01001000
Boot partition enable : Boot partition 1
(Bus width = 1Bit)
Boot ACK : Boot acknowledge sent during boot operation Bit

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 : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 7692288 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 (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/Q316BB_09_07_2018_00_42_24,bin.
Connect successful.
---------------------------------------------------------------
SW: 1.6.3; FW: 1.24.
P00: GPT (00000000, 00002000) 4 MB
P01: bota0 (00002000, 00002000) 4 MB
P02: nvram (00004000, 00004000) 8 MB
P03: lk (00008000, 00001000) 2048 KB
P04: bota1 (00009000, 00001000) 2048 KB
P05: secro (0000A000, 00003800) 7 MB
P06: seccfg (0000D800, 00000400) 512 KB
P07: efuse (0000DC00, 00000400) 512 KB
P08: tee1 (0000E000, 00003000) 6 MB
P09: bota2 (00011000, 00003000) 6 MB
P10: efs (00014000, 00004000) 8 MB
P11: nvdata (00018000, 00010000) 32 MB
P12: param (00028000, 00004000) 8 MB
P13: recovery (0002C000, 00008000) 16 MB
P14: boot (00034000, 00008000) 16 MB
P15: md1img (0003C000, 00010000) 32 MB
P16: md1dsp (0004C000, 00002000) 4 MB
P17: keystore (0004E000, 00004000) 8 MB
P18: omekeystore (00052000, 00001C00) 3584 KB
P19: proinfo (00053C00, 00001400) 2560 KB
P20: para (00055000, 00000400) 512 KB
P21: persistent (00055400, 00000400) 512 KB
P22: steady (00055800, 00000800) 1024 KB
P23: protect1 (00056000, 00004000) 8 MB
P24: protect2 (0005A000, 00004000) 8 MB
P25: reserve2 (0005E000, 00002000) 4 MB
P26: system (00060000, 00624000) 3144 MB
P27: cache (00684000, 000C8000) 400 MB
P28: hidden (0074C000, 0004B000) 150 MB
P29: userdata (00797000, 06CE3000) 54.44 GB
Repairing from file "C:/Program Files (x86)/Octoplus Pro JTAG Software/firmwareFolder/SAMSUNG_SM-G532M_EMMC,srf".
Write data verification is enabled.

Switched to boot area partition 1.
Writing BOOT1 partition... Done.

Switched to boot area partition 2.
Writing BOOT2 partition... Done.

Switched to user area.
Writing GPT partition... Done.
Writing bota0 partition... Done.
Writing lk partition... Done.
Writing secro partition... Done.
Writing efuse partition... Done.
Writing tee1 partition... Done.
Writing param partition... Done.
Writing recovery partition... Done.
Writing boot partition... Done.
Writing md1img partition... Done.
Writing md1dsp partition... Done.

Smart Repair is successfully complete.

Medusa Box · 07-09-2018, 05:06

Accordingly to your Software log, Repair process was done successfully. Probably, boot loaders in SFR "SAMSUNG_SM-G532M_EMMC.srf" can be not compatible with your phone (boot loaders are older (lower) version, than should be in your phone, and phone can't go into Download Mode because of enabled boot downgrade protection). Try to do "Factory Repair" using proper PIT file and the latest original Samsung firmwares for SM-G532M. Then try to put the phone into Download Mode manually. Also try to put the phone into Download Mode using JIG cable.

Also, look here: http://forum.gsmhosting.com/vbb/f664.../#post12952181.

Camiuu · 07-11-2018, 00:20

Quote:

Originally Posted by Medusa Box

Accordingly to your Software log, Repair process was done successfully. Probably, boot loaders in SFR "SAMSUNG_SM-G532M_EMMC,srf" can be not compatible with your phone (boot loaders are older (lower) version, than should be in your phone, and phone can't go into Download Mode because of enabled boot downgrade protection). Try to do "Factory Repair" using proper PIT file and the latest original Samsung firmwares for SM-G532M. Then try to put the phone into Download Mode manually. Also try to put the phone into Download Mode using JIG cable.

i tryed that after you reply me, and still's on dead boot but my pc recognizes the phone like before... now im downloading a new original rom for that model, i will notify you if i can solve this, thank you!

rebainoor · 07-13-2018, 21:25

yes use a last firmware version and if not going in download mode you can do factory repaire with last combonation firmware
good luck

Camiuu · 07-24-2018, 21:34

Quote:

Originally Posted by rebainoor

yes use a last firmware version and if not going in download mode you can do factory repaire with last combonation firmware
good luck

Thank you, i will try!

Camiuu · 07-29-2018, 10:26

Quote:

Originally Posted by rebainoor

yes use a last firmware version and if not going in download mode you can do factory repaire with last combonation firmware
good luck

Hey! how are you? i tryed again using the last firmware version and then smart repair, now the phone turns on but it stuck in recovery mode with some fails like "dm-verity verification failed" "Failed to mount /cache" and the same with system and efs... what i have to do now? the phone cant be in download mode to flash it, im so confused right now, really i dont know what to do

Greatings!
PD: Please be patient with my english, im from argentina che

Medusa Box · 07-29-2018, 11:17

Try to write EFS backup for SM-G535F (in the Medusa Support Area there are three EFS backup files). Also, if You have Octoplus Samsung Software, after writing EFS backup, try to perform "Repair Security" operation.

Camiuu · 07-29-2018, 22:10

Quote:

Originally Posted by Medusa Box

Try to write EFS backup for SM-G535F (in the Medusa Support Area there are three EFS backup files). Also, if You have Octoplus Samsung Software, after writing EFS backup, try to perform "Repair Security" operation.

How i can write EFS with emmc interface? because my computer doesnt recognizes the phone

Medusa Box · 07-30-2018, 04:28

Please use "Factory Repair" option and select EFS backup file in "*.tar" format instead of firmware file.

Camiuu · 08-03-2018, 06:06

Quote:

Originally Posted by Medusa Box

Please use "Factory Repair" option and select EFS backup file in "*.tar" format instead of firmware file.

There's no EFS Backup for G532M model, i tryed with G532F Efs backup but it still's showing the same errors of " failed to mount" system, cache and efs

07-09-2018, 01:22	#1 (permalink)
Camiuu Junior Member Join Date: Jul 2017 Location: Argentina Posts: 7 Member: 2742114 Status: Offline Thanks Meter: 0	SM-G532M repair question [Answered] Hi everyone, recently i flashed a g532m and it turns into dead boot, casually i bought an octoplus pro box to do that jobs, i followed the steps and now the computer recognizes the phone like "Mediatek usb port (COM #)" my question is... what i have to do now? i cant do nothing more and im a beginner in octoplus, i will preciate any answer. There's Log info below. Model Settings: Interface : eMMC Brand : Samsung Model : SM-G532M SRF : C:/Program Files (x86)/Octoplus Pro JTAG Software/firmwareFolder/SAMSUNG_SM-G532M_EMMC,srf Voltage : 1.8V Bus Mode : 1 bit Bus speed : Auto Connecting... Device : Samsung eMMC Q316BB Page size : 512 B Block size : 512 B Block count : 30777344 Size : 14.68 GB (15028.00 MB) --------------------------------------------------------------- CID Info CID : 150100513331364242003511CEF0745D Manufacturer ID : 0X15 Device/BGA : BGA (Discrete embedded) OEM/Application ID : 0X00 Product name : Q316BB Product revision : 0.0 Product serial number : (hex) 3511CEF0 Manufacturing date : 07/2017 --------------------------------------------------------------- CSD Info CSD : D02701320F5903FFF6DBFFEF8E40400D CSD structure : CSD version No. 1.2 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: 15 ms TRAN speed : 26 MHz READ block length : 512 Bytes WP group enable : YES PERM_WRITE_PROTECT : NO TMP_WRITE_PROTECT : NO --------------------------------------------------------------- EXTCSD Info Revision 1.7 (for MMC v5.0, v5.01) Erase block size : 512 Kbytes Boot1 size : 4096 Kbytes Boot2 size : 4096 Kbytes RPMB size : 4096 Kbytes Partition config : (0x48) 01001000 Boot partition enable : Boot partition 1 (Bus width = 1Bit) Boot ACK : Boot acknowledge sent during boot operation Bit 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 : (0x01) RST_n signal is permanently enabled Partitioning support : Device supports partitioning features Enhanced attribute : Device can have enhanced technological features in partitions and user data area. Max enhanced data size: 7692288 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 (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/Q316BB_08_07_2018_21_18_37,bin. Connect successful. --------------------------------------------------------------- SW: 1.6.3; FW: 1.24. P00: GPT (00000000, 00002000) 4 MB P01: bota0 (00002000, 00002000) 4 MB P02: nvram (00004000, 00004000) 8 MB P03: lk (00008000, 00001000) 2048 KB P04: bota1 (00009000, 00001000) 2048 KB P05: secro (0000A000, 00003800) 7 MB P06: seccfg (0000D800, 00000400) 512 KB P07: efuse (0000DC00, 00000400) 512 KB P08: tee1 (0000E000, 00003000) 6 MB P09: bota2 (00011000, 00003000) 6 MB P10: efs (00014000, 00004000) 8 MB P11: nvdata (00018000, 00010000) 32 MB P12: param (00028000, 00004000) 8 MB P13: recovery (0002C000, 00008000) 16 MB P14: boot (00034000, 00008000) 16 MB P15: md1img (0003C000, 00010000) 32 MB P16: md1dsp (0004C000, 00002000) 4 MB P17: keystore (0004E000, 00004000) 8 MB P18: omekeystore (00052000, 00001C00) 3584 KB P19: proinfo (00053C00, 00001400) 2560 KB P20: para (00055000, 00000400) 512 KB P21: persistent (00055400, 00000400) 512 KB P22: steady (00055800, 00000800) 1024 KB P23: protect1 (00056000, 00004000) 8 MB P24: protect2 (0005A000, 00004000) 8 MB P25: reserve2 (0005E000, 00002000) 4 MB P26: system (00060000, 00604000) 3080 MB P27: cache (00664000, 000C8000) 400 MB P28: hidden (0072C000, 0001E000) 60 MB P29: userdata (0074A000, 0160E000) 11.03 GB Kind regards! Last edited by Octopus box; 07-09-2018 at 04:30.

07-29-2018, 11:17	#9 (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	Try to write EFS backup for SM-G535F (in the Medusa Support Area there are three EFS backup files). Also, if You have Octoplus Samsung Software, after writing EFS backup, try to perform "Repair Security" operation. Last edited by Octopus box; 07-29-2018 at 11:24.

07-09-2018, 05:06	#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	Accordingly to your Software log, Repair process was done successfully. Probably, boot loaders in SFR "SAMSUNG_SM-G532M_EMMC.srf" can be not compatible with your phone (boot loaders are older (lower) version, than should be in your phone, and phone can't go into Download Mode because of enabled boot downgrade protection). Try to do "Factory Repair" using proper PIT file and the latest original Samsung firmwares for SM-G532M. Then try to put the phone into Download Mode manually. Also try to put the phone into Download Mode using JIG cable. Also, look here: http://forum.gsmhosting.com/vbb/f664.../#post12952181.

07-13-2018, 21:25	#6 (permalink)
rebainoor No Life Poster Join Date: Feb 2006 Location: In my LAB Posts: 3,163 Member: 231728 Status: Offline Thanks Meter: 2,104	yes use a last firmware version and if not going in download mode you can do factory repaire with last combonation firmware good luck

07-30-2018, 04:28	#11 (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	Please use "Factory Repair" option and select EFS backup file in "*.tar" format instead of firmware file.