Bricked my Cool 1

kassana69 · Sep 21, 2017 26 2 0

I've never bricked a phone. Installed JUI, and wanted to rollback to EUI via coolpad assistant. Couldn't do that because my PC wouldn't recognise my device, even though it did when flashing to JUI!

So I thought, why don't I flash a recovery via twrp - decided to flash recovery via miflash. Which was successful.

Now the phone doesn't switch on.

When a cable comes on, just two red lights flash.

I have tried to flash official firmware via YGDP and coolpad assistant. Phone is not recognised. uninstalled drivers and reinstalled them. To no avail. What do I do?

sumanta15.05 · Dec 11, 2017 6 0 0

You can flash using QPST, I did that to unbrick my phone.
Extract the CPB and flash using QFIL.
But please do backup your phone internal before that. I fixed my brick but cant fix my baseband as I forgot to take a backup.
It would be a favor if anyone could send their QCN backed up ( in private message , be ensured that I will use my own imei number

)

altrin · Jun 28, 2009 82 12 0

kassana69 said:
I've never bricked a phone. Installed JUI, and wanted to rollback to EUI via coolpad assistant. Couldn't do that because my PC wouldn't recognise my device, even though it did when flashing to JUI!

So I thought, why don't I flash a recovery via twrp - decided to flash recovery via miflash. Which was successful.

Now the phone doesn't switch on.

When a cable comes on, just two red lights flash.

I have tried to flash official firmware via YGDP and coolpad assistant. Phone is not recognised. uninstalled drivers and reinstalled them. To no avail. What do I do?

Official rollback with JUI on the EUI.
Download the archive https://mega.nz/#!n5whhDqA!X9i4VJCgcXhKv5GpgV5Tauhk0YrabFEF5Z85e4wUleg

Password for the archive: coolpadJUI2017

1. Unpack the archive
2. Install the Coolpad download assistent from the archive
3. Start Coolpad download assistent
4. Select init.cpb
5. Connect the phone in the mode bootloader to usb
6. The init.cpb firmware will go
7. After a minute or two, the automatic checking of the ROM.cpb file should go
8. After the verification, the firmware will go.
Done

kassana69 · Sep 21, 2017 26 2 0

How do I do that?

Rinzler46 · Jan 2, 2018 2 0 0

kassana69 said:
I've never bricked a phone. Installed JUI, and wanted to rollback to EUI via coolpad assistant. Couldn't do that because my PC wouldn't recognise my device, even though it did when flashing to JUI!

So I thought, why don't I flash a recovery via twrp - decided to flash recovery via miflash. Which was successful.

Now the phone doesn't switch on.

When a cable comes on, just two red lights flash.

I have tried to flash official firmware via YGDP and coolpad assistant. Phone is not recognised. uninstalled drivers and reinstalled them. To no avail. What do I do?

How u flashed through miflash? If possible can u send me files?? I can't flash TWRP in JUI becoz JUI Chinese rom can't be rooted...

erica butson · Jan 17, 2018 40 16 0

Bricked my coolpad cool 1 after upgrading to JUI and rolling back to EUI

I have upgraded to JUI and didn't like the rom because many apps were failed to run and stopped. Couldn't install Gapps tried with Google Installer and also TWRP. So I decided to roll back and flashed EUI 18S unfortunately it was Chinese rom not the indian version. Decided to install Gapps but couldn't get into recovery.
Hence I thought to flash Indian version stock rom 17S through Coolpad Asisstant. While downgrading to the stock rom on indian version my phone bricked.
I cannot get into recovery. Tried all the combinations. I cannot get the device recognised as fastboot or ADB Devices.
The only way i can get the device recognised is by pressing volume + and volume - and the power button at a time and plug in the USB. The device gets detected in Qualcomm QDLoader mode 9008. I tried flashing stock recovery by QFIL and MIFlash.
But Still didn't work.
After phone. The phone tries to boot but switches off suddenly. I can only get into Qualcomm QDLoader mode 9008. Any suggestion that would help my phone get normal. I think it's hard bricked because it cannot get into recovery nor the fastboot mode. Thank you

---------- Post added at 02:41 PM ---------- Previous post was at 02:33 PM ----------

erica butson said:
I have upgraded to JUI and didn't like the rom because many apps were failed to run and stopped. Couldn't install Gapps tried with Google Installer and also TWRP. So I decided to roll back and flashed EUI 18S unfortunately it was Chinese rom not the indian version. Decided to install Gapps but couldn't get into recovery.
Hence I thought to flash Indian version stock rom 17S through Coolpad Asisstant. While downgrading to the stock rom on indian version my phone bricked.
I cannot get into recovery. Tried all the combinations. I cannot get the device recognised as fastboot or ADB Devices.
The only way i can get the device recognised is by pressing volume + and volume - and the power button at a time and plug in the USB. The device gets detected in Qualcomm QDLoader mode 9008. I tried flashing stock recovery by QFIL and MIFlash.
But Still didn't work.
After phone. The phone tries to boot but switches off suddenly. I can only get into Qualcomm QDLoader mode 9008. Any suggestion that would help my phone get normal. I think it's hard bricked because it cannot get into recovery nor the fastboot mode. Thank you

ztev · Feb 24, 2018 1 0 0

sumanta15.05 said:
You can flash using QPST, I did that to unbrick my phone.
Extract the CPB and flash using QFIL.
But please do backup your phone internal before that. I fixed my brick but cant fix my baseband as I forgot to take a backup.
It would be a favor if anyone could send their QCN backed up ( in private message , be ensured that I will use my own imei number )

Hi,

I tried install TWRP via MiFlash on Letv Cool1 c106 4gb/64 - eui, rom Leree. The operation has completed. But now I have a problem, mobile blinking red light when plugged in PC. I can't turn on it. I think I brick it. What can I do, it is possible to ubrick him ?
Please help me.

Rinzler46 · Jan 2, 2018 2 0 0

how you succeed?? i tried but failed. Can you help me plz

erica butson said:
I have upgraded to JUI and didn't like the rom because many apps were failed to run and stopped. Couldn't install Gapps tried with Google Installer and also TWRP. So I decided to roll back and flashed EUI 18S unfortunately it was Chinese rom not the indian version. Decided to install Gapps but couldn't get into recovery.
Hence I thought to flash Indian version stock rom 17S through Coolpad Asisstant. While downgrading to the stock rom on indian version my phone bricked.
I cannot get into recovery. Tried all the combinations. I cannot get the device recognised as fastboot or ADB Devices.
The only way i can get the device recognised is by pressing volume + and volume - and the power button at a time and plug in the USB. The device gets detected in Qualcomm QDLoader mode 9008. I tried flashing stock recovery by QFIL and MIFlash.
But Still didn't work.
After phone. The phone tries to boot but switches off suddenly. I can only get into Qualcomm QDLoader mode 9008. Any suggestion that would help my phone get normal. I think it's hard bricked because it cannot get into recovery nor the fastboot mode. Thank you

---------- Post added at 02:41 PM ---------- Previous post was at 02:33 PM ----------

Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\jay\Desktop\QFILRecovery\prog_emmc_firehose.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\jay\Desktop\QFILRecovery
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Search path not exist, ignored: C:\Users\jay\Desktop\QFILRecovery
Invalid programmer path, ignored: C:\Users\jay\Desktop\QFILRecovery\prog_emmc_firehose.mbn
Process Index:0
Programmer Path:C:\Users\jay\Desktop\UnbrickOfficial\recovery\prog_emmc_firehose_652.mbn
Image Search Path: C:\Users\jay\Desktop\UnbrickOfficial\recovery
Image Search Path: C:\Users\jay\Desktop\UnbrickOfficial\recovery
RAWPROGRAM file path: C:\Users\jay\Desktop\UnbrickOfficial\recovery\rawprogram0.xml
PATCH file path:C:\Users\jay\Desktop\UnbrickOfficial\recovery\patch0.xml
Start Download
Program Path:C:\Users\jay\Desktop\UnbrickOfficial\recovery\prog_emmc_firehose_652.mbn
***** Working Folder:C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\jay\Desktop\UnbrickOfficial\recovery\prog_emmc_firehose_652.mbn
19:49:35: Requested ID 13, file: "C:\Users\jay\Desktop\UnbrickOfficial\recovery\prog_emmc_firehose_652.mbn"
19:49:35: 349340 bytes transferred in 0.250000 seconds (1.3326MBps)
19:49:35: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
19:49:35: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
19:49:39: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram0.xml --search_path=C:\Users\jay\Desktop\UnbrickOfficial\recovery --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
19:49:39: INFO: Current working dir (cwd): C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
19:49:39: INFO: Showing network mappings to allow debugging
19:49:39: INFO:
19:49:39: INFO: Trying to store 'rawprogram0.xml' in string table
19:49:39: INFO: Looking for file 'rawprogram0.xml'
19:49:39: INFO: User wants to talk to port '\\.\COM3'
19:49:39: INFO: Took 0.00000000 seconds to open port
19:49:39: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
19:49:39: INFO: If you don't want this, use --dontsorttags
19:49:39: INFO: Looking for file 'recovery.img'
19:49:39: INFO:
Total to be tansferd with <program> or <read> is 16.10 MB
19:49:39: INFO: Sending <configure>
19:49:39: INFO: TARGET SAID: '[email protected] [email protected]'
19:49:39: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
19:49:39: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
19:49:39: INFO: In handleProgram('recovery.img')
19:49:39: INFO: Looking for file 'recovery.img'
19:49:39: INFO: =======================================================
19:49:39: INFO: {<program> FILE: 'C:\Users\jay\Desktop\UnbrickOfficial\recovery\recovery.img'}
19:49:39: INFO: {<program> (16.10 MB) 32980 sectors needed at location 896096 on LUN 0}
19:49:39: INFO: =======================================================
19:49:39: INFO: TARGET SAID: '[email protected] [email protected]'
19:49:39: INFO: TARGET SAID: 'start 896096, num 32980'
19:49:40: INFO: Overall to target 0.735 seconds (21.91 MBps)
19:49:40: INFO: {percent files transferred 100.00%}
19:49:40: INFO: TARGET SAID: 'Finished sector address 929076'
19:49:40: INFO:
19:49:40: INFO: =======================================================
19:49:40: INFO: ==================== {SUCCESS} ========================
19:49:40: INFO: =======================================================
19:49:40: INFO: {percent files transferred 100.00%}
19:49:40: INFO: ==============================================================
19:49:40: INFO: Files used and their paths
19:49:40: INFO: 1 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
19:49:40: INFO: 2 'C:\Users\jay\Desktop\UnbrickOfficial\recovery\rawprogram0.xml'
19:49:40: INFO: 3 'C:\Users\jay\Desktop\UnbrickOfficial\recovery\recovery.img'
19:49:40: INFO: _ (done)
19:49:40: INFO: | |
19:49:40: INFO: __| | ___ _ __ ___
19:49:40: INFO: / _` |/ _ \| '_ \ / _ \
19:49:40: INFO: | (_| | (_) | | | | __/
19:49:40: INFO: \__,_|\___/|_| |_|\___|
19:49:40: INFO: {All Finished Successfully}
19:49:40: INFO: Overall to target 0.844 seconds (19.08 MBps)
19:49:40: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
***** Working Folder:C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
19:49:40: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=patch0.xml --search_path=C:\Users\jay\Desktop\UnbrickOfficial\recovery --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
19:49:40: INFO: Current working dir (cwd): C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
19:49:40: INFO: Showing network mappings to allow debugging
19:49:41: INFO:
19:49:41: INFO: Trying to store 'patch0.xml' in string table
19:49:41: INFO: Looking for file 'patch0.xml'
19:49:41: INFO: User wants to talk to port '\\.\COM3'
19:49:41: INFO: Took 0.00000000 seconds to open port
19:49:41: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
19:49:41: INFO: If you don't want this, use --dontsorttags
19:49:41: INFO: Sending <configure>
19:49:41: INFO: TARGET SAID: '[email protected] [email protected]'
19:49:41: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
19:49:41: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
19:49:41: INFO: TARGET SAID: 'Patched sector 16 with 03A3DFDE'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071341 with 03A3DFDE'
19:49:41: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFDE'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDE'
19:49:41: INFO: TARGET SAID: 'Patched sector 1 with 03A3DFFF'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFFF'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 03A3DFDF'
19:49:41: INFO: TARGET SAID: 'crc start sector 2, over bytes 7680'
19:49:41: INFO: TARGET SAID: 'Patched sector 1 with 77C000D3'
19:49:41: INFO: TARGET SAID: 'crc start sector 61071327, over bytes 7680'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 77C000D3'
19:49:41: INFO: TARGET SAID: 'Patched sector 1 with 00000000'
19:49:41: INFO: TARGET SAID: 'crc start sector 1, over bytes 92'
19:49:41: INFO: TARGET SAID: 'Patched sector 1 with FEA83C6E'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 00000000'
19:49:41: INFO: TARGET SAID: 'crc start sector 61071359, over bytes 92'
19:49:41: INFO: TARGET SAID: 'Patched sector 61071359 with 42876C66'
19:49:41: INFO: ==============================================================
19:49:41: INFO: Files used and their paths
19:49:41: INFO: 1 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
19:49:41: INFO: 2 'C:\Users\jay\Desktop\UnbrickOfficial\recovery\patch0.xml'
19:49:41: INFO: _ (done)
19:49:41: INFO: | |
19:49:41: INFO: __| | ___ _ __ ___
19:49:41: INFO: / _` |/ _ \| '_ \ / _ \
19:49:41: INFO: | (_| | (_) | | | | __/
19:49:41: INFO: \__,_|\___/|_| |_|\___|
19:49:41: INFO: {All Finished Successfully}
19:49:41: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.437 seconds (0.00 Bps)
Writing log to 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
***** Working Folder:C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
19:49:42: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --setactivepartition=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
19:49:42: INFO: Current working dir (cwd): C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
19:49:42: INFO: Showing network mappings to allow debugging
19:49:42: INFO: User wants to talk to port '\\.\COM3'
19:49:42: INFO: Took 0.00000000 seconds to open port
19:49:42: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
19:49:42: INFO: If you don't want this, use --dontsorttags
19:49:42: INFO: Sending <configure>
19:49:42: INFO: TARGET SAID: '[email protected] [email protected]'
19:49:42: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
19:49:42: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
19:49:42: INFO: Sending <setbootablestoragedrive>
19:49:42: INFO: TARGET SAID: 'Set bootable drive to 0.'
19:49:42: INFO: ==============================================================
19:49:42: INFO: Files used and their paths
19:49:42: INFO: 1 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
19:49:42: INFO: _ (done)
19:49:42: INFO: | |
19:49:42: INFO: __| | ___ _ __ ___
19:49:42: INFO: / _` |/ _ \| '_ \ / _ \
19:49:42: INFO: | (_| | (_) | | | | __/
19:49:42: INFO: \__,_|\___/|_| |_|\___|
19:49:42: INFO: {All Finished Successfully}
19:49:42: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.062 seconds (0.00 Bps)
Writing log to 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\jay\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
Download Succeed
Finish Download

need help

wesley-raf · Mar 2, 2018 3 0 0

My calls are mute, I do not hear anyone calling.

I tried this procedure but my phone is not identified by Colpad Download, I installed JUI but my phone is muted in calls I do not hear anything in calls and anyone who calls me does not hear me.
How can I open a TOPIC to see if someone helps me solve this?

Palm Trees · Mar 2, 2018 at 8:27 PM

Off-topic, but if you haven't signed already, please do so https://www.change.org/p/coolpad-kernel-sources-for-cool1 and let's hope the kernel sources are released soon

wesley-raf · Mar 2, 2018 3 0 0

how to use QFIL to install CBP?

sumanta15.05 said:
You can flash using QPST, I did that to unbrick my phone.
Extract the CPB and flash using QFIL.
But please do backup your phone internal before that. I fixed my brick but cant fix my baseband as I forgot to take a backup.
It would be a favor if anyone could send their QCN backed up ( in private message , be ensured that I will use my own imei number )

my phone is not identified by COOL ASSISTANT but QFIL identifies it, how do I give DOWNGRADE using QFIL? : eek:

wesley-raf · Mar 2, 2018 3 0 0

Restore Coolpad Cool 1 Bricked

kassana69 said:
I've never bricked a phone. Installed JUI, and wanted to rollback to EUI via coolpad assistant. Couldn't do that because my PC wouldn't recognise my device, even though it did when flashing to JUI!

So I thought, why don't I flash a recovery via twrp - decided to flash recovery via miflash. Which was successful.

Now the phone doesn't switch on.

When a cable comes on, just two red lights flash.

I have tried to flash official firmware via YGDP and coolpad assistant. Phone is not recognised. uninstalled drivers and reinstalled them. To no avail. What do I do?

Recovery for COOL1 deleted.

First of all, you need to download the necessary files:
GROSSOSHOP / MIFLASH driver / COOLPAD / ROOM recovery driver / Installation ROOM / EUI_TWRP_6.0.1.
• 1º install all drivers and MIFLASH
Remember that your device is erasing and only flashes the red light when connected to your computer, if your cell phone is in this state is a good sign as we will be able to get it to be identified to install the room;
2º HOW TO MAKE THE APPLIANCE IDENTIFIED ON THE PC

With the installed drivers connect your cell phone to your computer, open the Control Panel go to Device Manager and leave the screen open to observe: now with the phone connected we will press together the volume +, volume - and Power button together and secure them until the phone is identified by the system on the DEVICE MANAGER page (for the phone to be identified it may be necessary to keep pressing the buttons for more than 60 seconds, if it is not identified at the end of 120 seconds repeat the process of tightening buttons until the system identifies them).
• In case the system identifies but does not automatically install the driver it is necessary to perform a forced installation:

3º Forced driver installation:
With Device Manager open, we have the device to the computer, it has not been installed correctly for which it is necessary to perform the forced installation procedure. If the installation is not successful, the WINDOWS DRIVER DIGITAL SIGNATURE may be active and the installation of a set to first of all will disable it:
• Then type in the Windows search field and query by CMD, right-click and select to run as administrator with the command prompt open in administrator mode enter the following command without the quotes "bcdedit / set loadoptions DDISABLE_INTEGRITY_CHECKS "Ready a driver signature to be disabled, let's now forge a driver installation.
Right-click on the identified device but it is not recognized and select UPDATE DIVER, now on PROBE DRIVER SOFTWARE ON THE COMPUTER, click PERMIT THAT I CHOOSE ON A LIST OF AVAILABLE DRIVERS IN MY COMPUTER now in NEXT and on click in WITH THE DISK; Browse to your local disk where the driver was installed, LENOVO folder, normally installed in the directory: C: \ Program Files (x86) \ LenovoUsbDriver \ Navigate to a subfolder SERIAL and select the following file -Lenovo_ser click open and then In OK, Look for Qualcomm HS-USB QDLoader 9008 and confirm installation, prompt your device is now correctly connected and available and available for MIFLASH.
4º USING MIFLASH

Now with the drivers properly installed open the MIFLASH 1 click on REFRESH 2 select the folder of the recovery room that must be unzipped and 3 click on FLASH wait until the process finishes "in my case presented error at the end of the installation, but did not interfere , the process was enough so that I could already open the recovery mode of the mobile. "

• With the MIFLASH still open now press the Power button, volume - and volume + again until you make the identification noise on your computer again, in MIFLASH search for the EUI_TWRP_6.0.1_V1_ADVANCED_CUOCO92 folder and select the twrp subfolder and a REFRESH from your device should be recognized by MIFLASH, now click on FLASH and wait for the end of the installation.

With the twrp installed enter into recovery mode on your cell phone by pressing the Power buttons and the volume + button, click Wipe, Format Data, type yes and confirm this will delete your cell partition. Go back to twrp home screen click on Mount Disable MTP and then on ENABLE MTP, you can now transfer files to your mobile phone, transfer to the device's internal memory to android rom 6.0.1 COOL1_C106_R3_5.8.018S_ROW_BB72-CUOCO92_2 as soon as the transfer finish go back to the twrp menu screen go to INSTALL select the room wait for the installation "now without errors" and your device will start normally after a few minutes.

I can not post the download links the site does not allow me to be a new user, but to those who want to send me a private message that I forward the download links :good:

erica butson · Jan 17, 2018 40 16 0

Unbrick you're phone using this detailed guide on pantomath site

IMEI restore. Coolpad phones are unbrickable. Follow this guide

vulturext · Dec 5, 2012 303 43 58

sumanta15.05 said:
You can flash using QPST, I did that to unbrick my phone.
Extract the CPB and flash using QFIL.
But please do backup your phone internal before that. I fixed my brick but cant fix my baseband as I forgot to take a backup.
It would be a favor if anyone could send their QCN backed up ( in private message , be ensured that I will use my own imei number )

do you have a baseband backup? I bricked mine and flashed a baseband given in forum. Now i can no longer get 4g LTE connection. Device is C103. I need a QCN.

kishan nagrecha · Sep 29, 2016 2 0 0

Hii my cool 1 c103 has been bricked stuck in the penguin logo no fastboot mode no recovery mode also not getting detected in qdloader 9008 in pc help me guys when i connect my phone to pc the phone gets connected in android bootloaader interface help me someone not recognized in qfill only red light blinks in screen penguin logo no recovery mode no fastboot

sumanta15.05 · Dec 11, 2017 6 0 0

QCN

vulturext said:
do you have a baseband backup? I bricked mine and flashed a baseband given in forum. Now i can no longer get 4g LTE connection. Device is C103. I need a QCN.

I fixed mine using a qcn file from a Chinese or Russian site.
Google for c103 qcn and there would be a link for the QCN. It's around 100-200kb.

vulturext · Apr 21, 2018

kishan nagrecha said:
Hii my cool 1 c103 has been bricked stuck in the penguin logo no fastboot mode no recovery mode also not getting detected in qdloader 9008 in pc help me guys when i connect my phone to pc the phone gets connected in android bootloaader interface help me someone not recognized in qfill only red light blinks in screen penguin logo no recovery mode no fastboot

keep pressing power+vol up+vol down until it got detected. Install all the drivers first.

Zauq · May 9, 2018 at 8:09 AM

sumanta15.05 said:
I fixed mine using a qcn file from a Chinese or Russian site.
Google for c103 qcn and there would be a link for the QCN. It's around 100-200kb.

Thanks.... Found the QCN of C103 online and flashed it, problem solved.

---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------

If anyone needs QCN of C103, the same can be downloaded from the following link.

https://mega.nz/#!FQp0jC6L!UiczUgnYjK4CIPpv05ifN_VzBcH9m50G_OTACHAVlqw

Password - Coolpas [email protected]

I am not the owner of the file but downloaded the same from the following link

http://forum.gsmdevelopers.com/cool...coolpad-cool-1-c103-root-twrp-qcn-tested.html

I had the issue of no network and the above given QCN resolved the issue. Hence I am posting links here to help others.

chandunss · May 18, 2018 1 0 0

imei and qcn restored however network signal is not showing

I have recovered to eui ( c-103) from hard brick using qfil. however my imei numbers and network signals went off. I was able to get back my imei using imei write softwares and restore qcn etc. However , i still my network status is showing disabled. Please help me in this regard

Zauq · Mar 25, 2014 122 31 0

chandunss said:
I have recovered to eui ( c-103) from hard brick using qfil. however my imei numbers and network signals went off. I was able to get back my imei using imei write softwares and restore qcn etc. However , i still my network status is showing disabled. Please help me in this regard

Which qcn file you restored??

Bricked my Cool 1

Member

Member

Senior Member

Member

New member

Member

New member

New member

New member

Senior Member

New member

New member

Member

Senior Member

New member

Member

Senior Member

Senior Member

New member

Senior Member