Hello Friends,
recently i did factory reset to oppo a5 cph1809 with ufi box. after factory reset phone got dead and now userarea partitions are also not getting detected. i made short to clk resistor but of no use. this my oppo a5 log. experts please suggest some solution
Connection status: EHCI:HUB:HUB:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number:
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
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: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: RD64MB (0x524436344d42), rev: 0x01, serial number: 0xCFD2D4FC
Manufacturing date: May 2018
CID: 15010052 4436344D 4201CFD2 D4FC552C
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 29.12 GiB(31,268,536,320 bytes)
Cache size: 64 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
Custom moviNAND command is not supported for this device(MMC51).
Detected: SAMSUNG moviNAND KMRD60004M-BXXX/32G
recently i did factory reset to oppo a5 cph1809 with ufi box. after factory reset phone got dead and now userarea partitions are also not getting detected. i made short to clk resistor but of no use. this my oppo a5 log. experts please suggest some solution
Connection status: EHCI:HUB:HUB:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number:
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
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: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: RD64MB (0x524436344d42), rev: 0x01, serial number: 0xCFD2D4FC
Manufacturing date: May 2018
CID: 15010052 4436344D 4201CFD2 D4FC552C
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 29.12 GiB(31,268,536,320 bytes)
Cache size: 64 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
Custom moviNAND command is not supported for this device(MMC51).
Detected: SAMSUNG moviNAND KMRD60004M-BXXX/32G