Oppo A3S "dead" after trying to reset [Answered] - GSM-Forum

AnonDz · 11-02-2018, 17:56

hi i tried to reset the phone with mrt isp tool and it didn't recognize my medusa pro so i desoldered the jumper wires and booted the phone the phone dosent start it only connect to qlm mode i tried to flash it with qfil nothing and now i tried to repair it with factory repair qlm with xml file now the its giving me errors when i try to write the firmware and disconnect directly and this is the log of operation and screenshot

Please disconnect battery and USB cable.

Model Settings:
Interface : eMMC
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Unknown eMMC S0J9F8
Page size : 512 B
Block size : 512 B
Block count : 2097152
Size : 1024.00 MB
---------------------------------------------------------------
CID Info

CID : 13014E53304A3946381003C07AD35533
Manufacturer ID : 0X13
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4E
Product name : S0J9F8
Product revision : 1.0
Product serial number : (hex) 3C07AD3
Manufacturing date : 05/2002
---------------------------------------------------------------
CSD Info

CSD : D05F01328F5913FFFFFFFFEF964000A9
CSD structure : CSD version No. 1.0
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: 50 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.0 (for MMC v4.0)
Erase block size : 0 Kbytes
Boot1 size : 0 Kbytes
Boot2 size : 0 Kbytes
RPMB size : 32640 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)

Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0xFF) 11111111
Boot bus width :
Reset boot bus conditions : Retain BOOT_BUS_WIDTH and BOOT_MODE values after boot operation
Boot mode :

RST_n function : (0x03)

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 0 Kbytes
Partitions attribute : 0xFF
Part setting completed: 0xFF
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 : (0xFFFFFE00) 4096 MB

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/S0J9F8_02_11_2018_17_46_35.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.6.9; FW: 1.24.

suriyas1 · 11-02-2018, 18:38

Quote:

Originally Posted by AnonDz

hi i tried to reset the phone with mrt isp tool and it didn't recognize my medusa pro so i desoldered the jumper wires and booted the phone the phone dosent start it only connect to qlm mode i tried to flash it with qfil nothing and now i tried to repair it with factory repair qlm with xml file now the its giving me errors when i try to write the firmware and disconnect directly and this is the log of operation and screenshot

Please disconnect battery and USB cable.

Model Settings:
Interface : eMMC
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Unknown eMMC S0J9F8
Page size : 512 B
Block size : 512 B
Block count : 2097152
Size : 1024.00 MB
---------------------------------------------------------------
CID Info

CID : 13014E53304A3946381003C07AD35533
Manufacturer ID : 0X13
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4E
Product name : S0J9F8
Product revision : 1.0
Product serial number : (hex) 3C07AD3
Manufacturing date : 05/2002
---------------------------------------------------------------
CSD Info

CSD : D05F01328F5913FFFFFFFFEF964000A9
CSD structure : CSD version No. 1.0
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: 50 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.0 (for MMC v4.0)
Erase block size : 0 Kbytes
Boot1 size : 0 Kbytes
Boot2 size : 0 Kbytes
RPMB size : 32640 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)

Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0xFF) 11111111
Boot bus width :
Reset boot bus conditions : Retain BOOT_BUS_WIDTH and BOOT_MODE values after boot operation
Boot mode :

RST_n function : (0x03)

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 0 Kbytes
Partitions attribute : 0xFF
Part setting completed: 0xFF
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 : (0xFFFFFE00) 4096 MB

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/S0J9F8_02_11_2018_17_46_35.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.6.9; FW: 1.24.

Same problem was i connect oppo A3s via emmc pinout...
Device not connect medusa pro.
Again check device is dead...
Cannot turn on and no qload mode...
Pls help

Sent from my NX591J using Tapatalk

rebainoor · 11-02-2018, 21:14

In your log operation the emmc chip not correctely detected please check all your isp connections
You Can test to repaire it by USB connection in Qualcomm auto detect

zardjuna · 11-03-2018, 02:11

Try to jumper r clk maybe damaged bcause overheat solder

Sent from my Coolpad E501_EU using Tapatalk

Medusa Box · 11-03-2018, 10:55

Hi.

Yes, as You can see from your Software log, You have not connected the device correctly or eMMC has HW problems - eMMC size (capacity) can't be 1024.00 MB:

Quote:

Device : Unknown eMMC S0J9F8
Page size : 512 B
Block size : 512 B
Block count : 2097152
Size : 1024.00 MB

also the next sizes are incorrect:

Quote:

Erase block size : 0 Kbytes
Boot1 size : 0 Kbytes
Boot2 size : 0 Kbytes
RPMB size : 32640 Kbytes

Try to re-solder eMMC wires, make each of them as short as possible (max. 3-5 CM length) and try to connect again. Try to connect the device with different Bus speed values and higher (try 2.0-2.4V) Voltage level. If the problem is still the same, probably, eMMC has HW issue(s).

alrsbs · 07-03-2019, 19:58

-Searching Android build info...
Not found what is this problem

ferouz kassim · 07-04-2019, 12:36

reson for this is emmc not well conncted probbly voltage supply is low and ofcourse while emmc is soldered it has tto be emergency qlm port reason is clk has been soldered so if it doesnt connect on desolder phone should be ohkay kindly check connection

11-02-2018, 17:56	#1 (permalink)
AnonDz Freak Poster Join Date: Aug 2014 Location: algeria Posts: 373 Member: 2232889 Status: Offline Thanks Meter: 91	Oppo A3S "dead" after trying to reset [Answered] hi i tried to reset the phone with mrt isp tool and it didn't recognize my medusa pro so i desoldered the jumper wires and booted the phone the phone dosent start it only connect to qlm mode i tried to flash it with qfil nothing and now i tried to repair it with factory repair qlm with xml file now the its giving me errors when i try to write the firmware and disconnect directly and this is the log of operation and screenshot Please disconnect battery and USB cable. Model Settings: Interface : eMMC Voltage : 1.8V Bus Mode : 1 bit Bus speed : Auto Connecting... Device : Unknown eMMC S0J9F8 Page size : 512 B Block size : 512 B Block count : 2097152 Size : 1024.00 MB --------------------------------------------------------------- CID Info CID : 13014E53304A3946381003C07AD35533 Manufacturer ID : 0X13 Device/BGA : BGA (Discrete embedded) OEM/Application ID : 0X4E Product name : S0J9F8 Product revision : 1.0 Product serial number : (hex) 3C07AD3 Manufacturing date : 05/2002 --------------------------------------------------------------- CSD Info CSD : D05F01328F5913FFFFFFFFEF964000A9 CSD structure : CSD version No. 1.0 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: 50 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.0 (for MMC v4.0) Erase block size : 0 Kbytes Boot1 size : 0 Kbytes Boot2 size : 0 Kbytes RPMB size : 32640 Kbytes Partition config : (0x00) 00000000 Boot partition enable : Device not boot enabled (default) Boot ACK : No boot acknowledge sent (default) Boot bus conditions : (0xFF) 11111111 Boot bus width : Reset boot bus conditions : Retain BOOT_BUS_WIDTH and BOOT_MODE values after boot operation Boot mode : RST_n function : (0x03) Partitioning support : Device supports partitioning features Enhanced attribute : Device can have enhanced technological features in partitions and user data area. Max enhanced data size: 0 Kbytes Partitions attribute : 0xFF Part setting completed: 0xFF 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 : (0xFFFFFE00) 4096 MB ---------------------------------------------------------------Searching Android build info... Not found --------------------------------------------------------------- Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/S0J9F8_02_11_2018_17_46_35.bin. Connect successful. --------------------------------------------------------------- SW: 1.6.9; FW: 1.24. Last edited by Medusa Box; 11-03-2018 at 10:56.

11-02-2018, 21:14	#3 (permalink)
rebainoor No Life Poster Join Date: Feb 2006 Location: In my LAB Posts: 3,163 Member: 231728 Status: Offline Thanks Meter: 2,104	In your log operation the emmc chip not correctely detected please check all your isp connections You Can test to repaire it by USB connection in Qualcomm auto detect

11-03-2018, 02:11	#4 (permalink)
zardjuna Freak Poster Join Date: Nov 2016 Location: INDONESIA Posts: 116 Member: 2650126 Status: Offline Thanks Meter: 42	Try to jumper r clk maybe damaged bcause overheat solder Sent from my Coolpad E501_EU using Tapatalk

07-03-2019, 19:58	#6 (permalink)
alrsbs No Life Poster Join Date: Oct 2011 Location: srilanka Age: 32 Posts: 553 Member: 1674096 Status: Offline Thanks Meter: 49	-Searching Android build info... Not found what is this problem

07-04-2019, 12:36	#7 (permalink)
ferouz kassim No Life Poster Join Date: May 2014 Location: UGANDA Posts: 801 Member: 2185549 Status: Offline Thanks Meter: 535	reson for this is emmc not well conncted probbly voltage supply is low and ofcourse while emmc is soldered it has tto be emergency qlm port reason is clk has been soldered so if it doesnt connect on desolder phone should be ohkay kindly check connection