help need coz i m new in medusa

[gmjony]

i have g530fz hang on logo..cant flash.odin says there is no pit partition.now what is the procces?

[Medusa Box]

Hello.

Have You used (selected) PIT file when tried to write firmware via Odin?

[gmjony]

Originally Posted by Medusa Box

Hello.

Have You used (selected) PIT file when tried to write firmware via Odin?

yessssssss.but no luck

[vikas mahajan]

Is it boot in recovery or not...

Sent from my HONOR 8 PRO using Tapatalk

[Medusa Box]

g530fz hang on logo..cant flash.odin says there is no pit partition

Have You used (selected) PIT file when tried to write firmware via Odin?

yessssssss.but no luck

Most likely, device has HW issue(s) (problem with eMMC flash chip), but You can try to connect it and do "Factory Repair".


To repair SM-G530FZ, try to do the following:

1. Install the latest version of Medusa Pro Software (http://medusabox.com/eng/download/software).
2. Download and install SRF (Smart Repair File) for SM-G530H "SAMSUNG_SM-G530H_EMMC_P1J95K.srf" from the Support Area (via "Download *.srf" button in Software).
3. Select "eMMC" option in Software.
4. Select Samsung SM-G530H in Software's list (model will appear in Software's list after SRF installation).
5. Solder all necessary eMMC wires accordingly to Software manual ("Help" or "Pinout" button in Software). EMMC pinout of SM-G530FZ should be similar (or the same) as for SM-G530H.
6. Press "Connect" button in Software.
7. When device will be connected successfully, do "Factory Repair" ("Factory repair" tab in Software) using proper PIT file and the latest Samsung firmware for SM-G530FZ.
8. Post here the result.

Also please make backup (read Full flash) before to do repairing.

[gmjony]

Model Settings:
Interface : eMMC
Brand : Samsung
Model : SM-G530H
SRF : C:/Program Files/Medusa Pro Software/firmwareFolder/SAMSUNG_SM-G530H_EMMC_P1J95K.srf
Voltage : 2.0V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Micron eMMC P1J95K
Page size : 512 B
Block size : 512 B
Block count : 15269888
Size : 7.28 GB
---------------------------------------------------------------
CID Info

CID : FE014E50314A39354B1336456F3222CF
Manufacturer ID : 0XFE
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4E
Product name : P1J95K
Product revision : 1.3
Product serial number : (hex) 36456F32
Manufacturing date : 02/2015
---------------------------------------------------------------
CSD Info

CSD : D06E01320F5913FFFFFFFFEF92400071
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: 6 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.6 (for MMC v4.5, v4.51)
Erase block size : 8192 Kbytes
Boot1 size : 2048 Kbytes
Boot2 size : 2048 Kbytes
RPMB size : 2048 Kbytes

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

Boot bus conditions : 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)

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 3817472 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...Ok

Disk/Image size : d2000000 bytes
Device sector size : 512 bytes
Partition offset : 376832
Number of sectors : 3063808
Device Manufacturer : samsung
Device Platform : msm8916
Build ID : LRX22G
Display Build ID : LRX22G.G530FZXXU1BQD2
Release ID : 5.0.2
Device Model : SM-G530FZ
Device Name : grandprimeltexx
Architecture ABI : armeabi-v7a
Architecture ABI2 : armeabi
Architecture ABI List : armeabi-v7a,armeabi
Build Description : grandprimeltexx-user 5.0.2 LRX22G G530FZXXU1BQD2 release-keys

Backup EXT_CSD saved to file C:/Program Files/Medusa Pro Software/EXT_CSD Backups/P1J95K_19_10_2017_13_37_04.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.4.6; FW: 1.22.
P00: GPT (00000000, 00002000)
P01: apnhlos (00002000, 00007800)
P02: modem (00009800, 0001CB80)
P03: sbl1 (00026380, 00000400)
P04: ddr (00026780, 00000040)
P05: aboot (000267C0, 00001000)
P06: rpm (000277C0, 00000400)
P07: qsee (00027BC0, 00000400)
P08: qhee (00027FC0, 00000400)
P09: fsg (000283C0, 00001800)
P10: sec (00029BC0, 00000020)
P11: pad (00029BE0, 00005420)
P12: param (0002F000, 00005000)
P13: efs (00034000, 00007000)
P14: modemst1 (0003B000, 00001800)
P15: modemst2 (0003C800, 00001800)
P16: boot (0003E000, 00006800)
P17: recovery (00044800, 00007800)
P18: fota (0004C000, 00002802)
P19: backup (0004E802, 000037EE)
P20: fsc (00051FF0, 00001800)
P21: ssd (000537F0, 00000010)
P22: persist (00053800, 00004000)
P23: persdata (00057800, 00004800)
P24: system (0005C000, 002EC000)
P25: cache (00348000, 00096000)
P26: hidden (003DE000, 00005000)
P27: userdata (003E3000, 00AACFD8)

Selected pit file: E:/g530fz/Nueva carpeta/GRANDPRIMELTE_EUR_OPEN.pit

Open file "E:/g530fz/G530FZXXU1BOJ2_G530FZWIN1BOI1_5.0.2_ITALY_HOME/G530FZXXU1BOJ2_G530FZWIN1BOI1_G530FZXXU1BOI2_HOME. tar.md5".


Writing MBR...Done.
Writing primary GPT...
ERROR[012]: Write error.
At sector 8.
Disconnected.

[Medusa Box]

As You can see from your Software log, there is a problem with eMMC chip - Software can't write data to it:

ERROR[012]: Write error.
At sector 8.

Try to connect the device with different Bus speed values and try to repeat "Factory Repair" operation. If the problem is still the same, You can try to replace eMMC chip to Samsung eMMC and then do repair again.