Log Info Konfigurasi IC eMMC/eMCP Xiaomi Redmi 5A MCI3B

Service emmc & Repair guide

Log Info Konfigurasi ic eMMC/eMCP Mi Max 2 OXYGEN

Product name: DF4032 (0x444634303332), rev: 0x01, serial number: 0x2514CB42
Manufacturing date: Nov 2017
CID: 45010044 46343033 32012514 CB42B400
CSD: D00F0032 8F5903FF FFFFFFEF 8A404000
EXT_CSD revision: 1.8 (MMC v5.1)
Capacity: 29.13 GiB(31,281,119,232 bytes)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 29.12 GiB(31,281,119,232 bytes)
Cache size: 4 MiB
Hardware reset function: 1
Partition configuration: 0x38
No boot acknowledge is sent (default)
User area 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: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked

platform: msm8937, cpu abi: arm64-v8a
manufacturer: Xiaomi
hardware: qcom, version: V1
board: QC_Reference_Phone, name: riva [MCG3B]
brand: Xiaomi, model: Redmi 5A
build id: N2G47H, version: 7.1.2 Nougat (N2G47H) (MIUI8)
build date: Tue Oct 24 22:24:28 CST 2017, security patch: 2017-09-01
build description: riva-user 7.1.2 N2G47H V8.5.7.0.NCKCNED release-keys
  • Log ini di ambil dari UFIBOX Dengan adanya ini mudah-mudahan bisa membantu kawan-kawan yang ingin melakukan pergantian ic emmc/emcp bisa menjadi lebih mudah.Bantu share jika artikel ini bermanfaat Terima Kasih
Log Info Konfigurasi IC eMMC/eMCP Xiaomi Redmi 5A MCI3B Log Info Konfigurasi IC eMMC/eMCP Xiaomi Redmi 5A MCI3B Reviewed by Unbrick All Android on July 31, 2019 Rating: 5

No comments:

In between our time repairing phones, we will always give our best to revise and update the post/tutorial whenever we find that there is a mistake in the writings, or a file is missing. So please kindly do let us know. Please read the disclaimer section first before you following the tutorial or downloading any file from us. We hope you understand our policy. Thank you.


Powered by Blogger.