Oppo A3S dead after factory reset by isp plz can any expert help
- Thread starter Xsa-Scorpion
- Start date
shamsul haq
Junior Member
bhupenderbanga
Friend's Martview
- Sep 25, 2018
- 127
- 220
Deepesh Sharma
Friend's Martview
you need to reprogram your device using rawprogram factory file
Roshan123
Active Member
allready writing full flash raw programe its take long time but after that no luck still dead i dont know where can find the problem its about factory reset or same short whene solder pin i cant understand where is the problem efect this option (factory reset ) still work or not to pass live phone at dead phone its confus
this is same trying to revive i m still waiting same suggestion to doing
and phone cant detect mode QLM (EDL)
log for write full flash latest VERSION (CPH1803EX_11_A.12)
this is same trying to revive i m still waiting same suggestion to doing
and phone cant detect mode QLM (EDL)
log for write full flash latest VERSION (CPH1803EX_11_A.12)
Code:
Connection status: EHCI:HUB:USB 2.0 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8840-1802
Boot version: 1.04, FW version: 1.12 (Jun 7 2018 00:06:47)
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: QE63MB (0x514536334d42), rev: 0x03, serial number: 0xD89BD472
Manufacturing date: juil. 2018
CID: 15010051 4536334D 4203D89B D47275F0
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: 14.56 GiB(15,634,268,160 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
ANDROID System Info:
platform: msm8953, cpu abi: arm64-v8a
manufacturer: OPPO
board: msm8953, name: CPH1803
brand: OPPO, model: CPH1803(OPPO A3s)
build id: OPM1.171019.026, version: 8.1.0 Oreo (CPH1803EX_11_A.12)
build description: msm8953_64-user 8.1.0 OPM1.171019.026 eng.root.20180927.160930 release-keys
crypto state: encrypted?
Custom moviNAND command is not supported for this device(MMC51).
Selected: [SAMSUNG] KMQE60013M-B318/16GB+LPDDR3 16Gb (BGA221)
Connection status: EHCI:HUB:USB 2.0 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8840-1802
Boot version: 1.04, FW version: 1.12 (Jun 7 2018 00:06:47)
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: QE63MB (0x514536334d42), rev: 0x03, serial number: 0xD89BD472
Manufacturing date: juil. 2018
CID: 15010051 4536334D 4203D89B D47275F0
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: 14.56 GiB(15,634,268,160 bytes)
Processing file: "gpt_backup0.bin"... Skipped
Processing file: "gpt_main0.bin"... Applying patch: Update last partition 65 'userdata' with actual size in Primary Header....Done.
Applying patch: Update Primary Header with LastUseableLBA....Done.
Applying patch: Update Primary Header with BackupGPT Header Location....Done.
Applying patch: Update Primary Header with CRC of Partition Array....Done.
Applying patch: Zero Out Header CRC in Primary Header....Done.
Applying patch: Update Primary Header with CRC of Primary Header....Done.
Writing PrimaryGPT at 0x00000000 (34 sectors)... Done in 0.902 s
Processing file: "persist.img"... Writing sparse image persist at 0x01705000 (65536 sectors)... Done in 11.811 s
Processing file: "emmc_fw.bin"... Writing opporeserve1 at 0x03705000 (8192 sectors)... Done in 8.669 s
Processing file: "marketname.xml"... Writing marketname at 0x03B24800 (1 sectors)... Done in 0.055 s
Processing file: "opporeserve2.img"... Writing sparse image opporeserve2 at 0x03F05000 (131072 sectors)... Done in 12.062 s
Processing file: "sbl1.mbn"... Writing sbl1 at 0x08308000 (853 sectors)... Done in 0.902 s
Processing file: "rpm.mbn"... Writing rpm at 0x08388000 (342 sectors)... Done in 0.362 s
Processing file: "tz.mbn"... Writing tz at 0x08408000 (3048 sectors)... Done in 3.222 s
Processing file: "devcfg.mbn"... Writing devcfg at 0x08608000 (78 sectors)... Done in 0.083 s
Processing file: "sbl1.mbn"... Writing sbl1bak at 0x08648000 (853 sectors)... Done in 0.902 s
Processing file: "rpm.mbn"... Writing rpmbak at 0x086C8000 (342 sectors)... Done in 0.361 s
Processing file: "tz.mbn"... Writing tzbak at 0x08748000 (3048 sectors)... Done in 3.505 s
Processing file: "devcfg.mbn"... Writing devcfgbak at 0x08948000 (78 sectors)... Done in 0.083 s
Processing file: "adspso.bin"... Writing dsp at 0x08988000 (32768 sectors)... Done in 34.947 s
Processing file: "sec_smt.dat"... Writing sec at 0x0A188000 (1 sectors)... Done in 0.083 s
Processing file: "emmc_appsboot.mbn"... Writing aboot at 0x0A18C000 (1417 sectors)... Done in 1.589 s
Processing file: "emmc_appsboot.mbn"... Writing abootbak at 0x0A28C000 (1417 sectors)... Done in 1.697 s
Processing file: "NON-HLOS.bin"... Writing modem at 0x0A38C000 (262144 sectors)... Done in 4 mins 38.461 s
Processing file: "dtbo.img"... Writing dtbo at 0x1238C000 (16384 sectors)... Done in 17.318 s
Processing file: "vbmeta.img"... Writing vbmeta at 0x12B8C000 (8 sectors)... Done in 0.010 s
Processing file: "boot.img"... Writing boot at 0x12B9C000 (131072 sectors)... Done in 2 mins 19.314 s
Processing file: "recovery.img"... Writing recovery at 0x16B9C000 (131072 sectors)... Done in 2 mins 20.024 s
Processing file: "logo.bin"... Writing LOGO at 0x1BB00000 (1538 sectors)... Done in 1.773 s
Processing file: "DRIVER.ISO"... Writing DRIVER at 0x1DB00000 (46476 sectors)... Done in 49.301 s
Processing file: "cache.img"... Writing sparse image cache at 0x1FB00000 (524288 sectors)... Done in 14.314 s
Processing file: "mdtp.img"... Writing mdtp at 0x30980000 (34782 sectors)... Done in 36.919 s
Processing file: "lksecapp.mbn"... Writing lksecapp at 0x33000000 (113 sectors)... Done in 0.119 s
Processing file: "cmnlib_30.mbn"... Writing cmnlib at 0x33020000 (418 sectors)... Done in 0.447 s
Processing file: "cmnlib64_30.mbn"... Writing cmnlib64 at 0x33120000 (526 sectors)... Done in 0.689 s
Processing file: "keymaster64.mbn"... Writing keymaster at 0x33220000 (531 sectors)... Done in 0.688 s
Processing file: "lksecapp.mbn"... Writing lksecappbak at 0x33320000 (113 sectors)... Done in 0.119 s
Processing file: "cmnlib_30.mbn"... Writing cmnlibbak at 0x33340000 (418 sectors)... Done in 0.554 s
Processing file: "cmnlib64_30.mbn"... Writing cmnlib64bak at 0x33440000 (526 sectors)... Done in 0.688 s
Processing file: "keymaster64.mbn"... Writing keymasterbak at 0x33540000 (531 sectors)... Done in 0.688 s
Processing file: "dpAP.mbn"... Writing apdp at 0x33800000 (26 sectors)... Done in 0.148 s
Processing file: "system.img"... Writing sparse image system at 0x3F000000 (7030784 sectors)... Done in 1 hour 52 mins 1.626 s
Processing file: "vendor.img"... Writing sparse image vendor at 0x115900000 (2161408 sectors)... Done in 31 mins 44.400 s
Processing file: "userdata.img"... Writing sparse image userdata at 0x158000000 (15728640 sectors)... Done in 1 hour 42 mins 45.211 s
Writing boot partition config to 0x38... Done.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++i think after flash by raw programme whene finished, set Auto config boot to 0x38, see last line in log bro ...
shamsul haq
Junior Member
my handset also dead but i hard work set on but hang on logo
here is procces
1-- connect phone emmc and info
2--formate emmc
3-- write extracsd file backup
4--write rawprobram0 only one area any one like first file
5--info
6-- disconnect
7--flash msm downlode tools
Lainlain
Junior Member
- Jan 16, 2019
- 2
- 3
check clk connection in 0ohm resistor. if this is damage, direct conncet with jumper wire. ok
Attachments
-
ab.jpg
bulti
Junior Member
- May 5, 2019
- 1
- 1
i'm no lucky.
i try jumper clk only but still 9008.
i try jumper cmd only still 9008.
i try jumper both still 9008.
i direct isp again & write full backup(condition pattern lock) > write success > but still 9008.
i check in condition 9008 > cmd about 1.789V, clk 0V, data0 1.789V
i want to question, how volt in cmd, clk & data0 if normally?
bro u have to check all the resistance with magnifying glass they may be short ... bcz it also happened with me and when i checked that 2 resistance were short when i untouch both of them my phones turned on...
Hanifmalaysiamari
Junior Member
- Oct 9, 2018
- 4
- 3
a3s 1803 if use ufi box factory reset almost done failed adjust clock to 48 mhz then factory reset again hope this hopeful i try it and done
you mean #7 7--flash msm downlode tools
need paid service after all?
sourabh kalra
Active Member
