J200F Emmc program problem

osom

I writed emmc file but

Boot version: 1.04, FW version: 1.10 (Mar 26 2017 14:24:34)
Insertion test... Done.
Init bus...
VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 4MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: FN12MB (0x464e31324d42), rev: 0x00, serial number: 0x5E35EC60
Manufacturing date: Kas 2015
CID: 15010046 4E31324D 42005E35 EC60B23A
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.7 (MMC v5.0, v5.01)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 512 KiB
User area: 7.28 GiB(7,818,182,656 bytes)
Cache size: 64 MiB
Partition configuration: 0x48
Boot acknowledge is sent during the boot operation
Boot partition 1 is enabled for boot
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x01
Bus width: x4 (sdr/ddr), boot mode: sdr(default), reset bus width to x1 sdr(default)
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

ANDROID ROM info:
WARNING: could not read build.prop, system part might be corrupted !

How ı can repair this problem_?

Aidin01

osom this error because your dump file maybe is 256 mb or 512 mb and the lenght is not enough to reading the build.prop of android system file but its not important because your dump have bootloader and can turn on your phone and after that you can flash it in download mode

osom

Phone not open Download mode
Dead phone is now

ProOFF

Try this dump..

GulHassan

n9005 same problem

WARNING: could not read build.prop, system part might be corrupted !

ddilshod93

GulHassan
Flashing with pit file latest flash file in factory tap.

GulHassan

ddilshod93

try but phone stil in same condation qualcom 9008 mode

madgoeslim

GulHassan Still in 9008 mode can be many possibility. Dump files noot good, bad emmc, bad replacement, bad connection, damage resistor, etc.

SANDYARDYANSAH

madgoeslim hello master
do u can helpme?, when iam tryng fill dump with ufi ANDROID System Info couldn't appear,,
how to fix this problem? please helpme

elmahdy11

after i download 2 dumps for n9005
when i try to choose one of them it give me this error

ANDROID ROM info:
WARNING: could not read build.prop, system part might be corrupted !

madgoeslim

elmahdy11 The try to write full dump, and identify again, then you can see what different between Dump Size Mystery 👻

ubaiudllah

samsung j200f similar emmc (phone) Need
how to fixed this problem
////////////////////////////
Insertion test... Done
VCC, VCCQ not properly connected
Init bus...
VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 4MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: Card (removable) - High density MMC
Manufacturer ID: 0x65 (Unknown)
Product name: MMOR (0x4d204d4f5212), rev: 0xA1, serial number: 0x00000615
Manufacturing date: Apr 2017
CID: 65646F4D 204D4F52 12A10000 06154430
Bad CID detected, eMMC might be damaged !!!
CSD: D07FFF32 0F59007F F6DB8000 1E40001C
Bad CSD detected, eMMC might be damaged !!!
EXT_CSD revision: 1.5 (MMC v4.41)
Partition info:
Boot1: 2048 KiB
Boot2: 2048 KiB
RPMB: 128 KiB
User area: 1.83 GiB(2,197,796,421,632 bytes)
Partition configuration: 0x78
Boot acknowledge is sent during the boot operation
User area is enabled for boot
Partitioning support: 0x03
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

madgoeslim

ubaiudllah Product name: MMOR

Then read the log below:

ubaiudllah CID: 65646F4D 204D4F52 12A10000 06154430
Bad CID detected, eMMC might be damaged !!!
CSD: D07FFF32 0F59007F F6DB8000 1E40001C
Bad CSD detected, eMMC might be damaged !!!

madgoeslim

SANDYARDYANSAH Hi,

ANDROID System Info is reading from build.prop inside system partition.
If Android System Info is not appear, it could be system partition corrupt, or not complete.
Some dump files maybe only read in little size, ex: 256MiB or 512MiB may not contain full system partition, so Android Systrm Info will also not appear, but it doesn't mean that this dump files is not good.