How did i fix my Hard Bricked Coolpad Cool 1 Device?

This post will help you unbrick coolpad cool 1 device.

Exactly one month after hard bricking my cool 1 .I have successfully unbricked my coolpad cool 1 device, as you’re here you will not find any difficulties unbricking your phones.

Most people use the term “bricked” improperly. A bricked phone means one thing: your phone won’t turn on in any way, shape or form, and there’s nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they’re a lot more common than a truly bricked phone. If your phone is actually bricked, you won’t be able to fix it yourself  You can fix it if it’s a Qualcomm snapdragon chipset. Basically Qualcomm devices are unbrickable even if it’s bricked by your real intentions to brick.

we can unbrick the device and save few bucks rather than buying a new phone.

Some knowledge to the new users if you have bricked your phone for the first time. 

There are basically two types of bricking

1 SOFT brick
2 Hard brick

1: Soft brick

A soft brick, is usually just when you’re phone is stuck in a bootloop, and as the name implies, is caused by a software error, usually the lack of a system to boot from or some other minor software bug that glitching boot. They are easily fixable by reflashing your ROM in recovery.

2: Hard brick

Hard brick is the state of android device that occurs when your device is unbootable without a bootloop. A hard Brick device generally show little to no signs of life. If this happens, you had better to buy a new device since your device is showing you a black or grey screen at this point.

So take a case you flashed new ROM or you have rooted your device or tried to install XPOSED or a audio or any MOD to your ROM and after flashing via TWRP/CWM/any other recovery then reboot your device its stuck in Bootanimation doesn’t boot at all stuck at boot animation (wait for 15mins to confirm ) then we can term it as soft brick there are three ways of fixing it.

Dirty flashing rom i.e. just flash the zip of your current rom thats it your successfully recovered from soft brick. Cheers

Clean flashing rom : this is way recommend for sure result we clean data dalvik cache system and then flash the rom boot it voila done.

Recovering nandroid backup [if backed-up] pretty simple step just hit restore thats it.

Now take case 2 if you had hard bricked you’re android device it can’t go into recovery or fastboot follow the guide.

NOTE: Always take backup do it even if you don’t like because EFS file system all you’re IMEI number are unique and must needed to get back you phone in working condition if something goes wrong. 

In my case the phone was bricked while upgrading to JUI manually and downgrading to EUI. If you had bricked you’re device in any way please follow this steps carefully.

First find out the level of the brick, We know it’s an hard brick but as in what level?

  1. Light Hard brick  : Light hard brick is defined as a hard brick where you can see the led lights glowing when connected to the PC, or the Phone gets detected as Qualcomm QDLoader mode 9008 under COM ports in you’re device manager. In a nutshell if you connect your phone to computer and the phone gets detected in as any device just click on update device manually and install the Qualcomm QDLoader mode 9008 driver manually. If you’re here I’m 100% sure you’re device will be back in working condition.
  2. Medium Hard Brick: Medium hard brick is defines as a hard brick where your phone doesn’t gets detected when you connect to your computer or the phone leds doesn’t glow. In this case we should make the device as Light Hard brick to do that. Watch this video. I have tried it personally and it works for sure. 
  3. Heavy Hard Brick: Congratulations You basically doomed you’re phone. but don’t give up yet, You can try one last method before thwrowing your device in garbage :P. Now you have two options Play dumb and give to service center under warranty if your not under warranty RIP you’re phone apart and do the process carefully.

Heavy Hard Bricked device can be restored if you carefully deal with it. If this following process doesn’t work just sell the display of your phone to other for cheap price.

      • You need to carefully remove the display with of Hot air gun at 100-120 degrees. Be careful display is very sensitive and may break if handled improperly or in a hurry.  Watch this video to know how to remove it.

      • Then remove protective housing on the board make sure you remove all the bolts and mark their position to bolt them back.

        • It is necessary to carefully disconnect from the battery so that the phone is completely turned off. And then it will be easy to remove

      • 4) gently leave the contact with the board so that the board rotates on the reverse side and there is a testpoint (where a red sign is marked)

      • 5) First, without a battery and a cable, you need to keep it short-circuited where the test point is and plug it in a couple of seconds and it will appear in QDLoader mode 9008.
      • I am not responsible for any damage caused to the device.

Now your phone should be detected in Qualcomm Qloader mode 9008. If it’s not detected by the led is glowing. Just connect the device to computer press volume down + volume up + power button same time. Keep pressing those buttons untill Red Led light blinks for 3 times.

If device gets detected as any other driver. Just download Qualcomm drivers from here and update the driver manually.

Flash the Stock rom from QPST/QFIL software and you’re phone will be back to life.

  1. Install QPST software
  2. Flash the rom
  3. Start the device using power button (100% it will work and start hard bricked my device two times already 😛 )

Note: I have seen people on youtube follow my guide posts and do a video as per my instructions and make money. I realized this when my rooting post was copied from an youtuber and made many views. It’s really frustrating!!!.

Hence to download the Flashable ROM just comment you’re email id on the comment section or Personal message me on Facebook I will share you the link.

The Rom is 1.6GB  size when compressed as zip and 3.4GB as when extracted. After downloading the ROM extract it flash it as per this rooting guide same way.

  • Open QFIL select the port which was detected as Qloader 9008,
  • Select flat build as build type path
  • Select Programmer path
  • Load RawProgram
  • Load Patch
  • Hit Download (The phone write the rom to the device and takes more or less 3 to 5 minutes depending on the read/write speed of the device)
  • It should display “Download Success” message after completion. If not follow my rooting guide to install drivers properly. If all the procedure is followed correctly and still the rom isn’t getting flashed to device due to some other errors personal message me for other alternatives.

By now you’re device should be back to life and I can’t guarantee that evey thing works. I had to face problems like IMEI number null and Baseband version Null.

If you had backup. No problem just restore the backup

To fix IMEI Personal message me. It works 100% without any problem you need few files and few partition files. When your device was hardbricked and brought back to life the EFS file system will be corrupted and there is a way to fix it. I don’t have time to do a separate post about it. Just contact me through comments or on facebook.

IMEI can be fixed by having stock rom and root permissions with the help of IMEI builder and qcn files.

Disclaimer: I’m not responsible for any damage caused to your device

UPDATE : IMEI Re-builder can be downloaded here

UPDATE: Download the ROM file here

UPDATE: For some reason’s if the blank qcn didn’t work for you. Please ask me for the new one. Blank.qcn works well with old released cool 1 devices. People with new Cool 1 device need another qcn file.
UPDATE: IMEI FIX VIDEO


Proof of Concept :

RELATED ARTICLESMORE FROM AUTHOR

212 COMMENTS

  1. Hello,
    thanks a useful article, and by the way I would like to ask for the following:

    What does the “persist” partition do? In TWRP I still have a message that I can not mount this partition … I tried to mount it in TWRP manually and I can not do it … How to restore everything to be ok?

    • Persist is Ext4 file system partition mounted at /persist location. it has data, display, drm, hlos_rfs,lost+found,rfs and sensors directories,

      Basically it consists of DRM related information, Bluetooth, Graphics, WIFI, Sensors, Mac Address information. with different directories with different user and group’s read/write permissions.

      I think you cannot mount the partition because the “Partition.img” file in the .CPB Stock rom file or the extracted file from CPB to flash from QFIL is corrupted & didn’t flash properly when you flashed the stock rom.
      There are there possible ways to fix this problem as i know. (Take a backup before doing anything)

      1. Format data in TWRP, Formatting data will stop encryption and you could mount system and internal storage in TWRP.
      2. flash the stock rom again if it didn’t work flash modified rom
        3.Extract the Persist.img file and copy it in the persist directory with suitable proper file permissions

  2. Thanks, I solved this by issuing the following command in the terminal available in TWRP, and I found a solution in the xda forum:

    Type following command in twrp terminal ,
    (Do at your own risk,make sure to do backup before proceeding)(this method works for me so I’m writing you)

    make_ext4fs /dev/block/bootdevice/by-name/persist

  5. thank u very much for thelink , but i have a problem that the phone does not complete the installation .
    i hope you can help me if you know how to fix the problem

    Download Fail:FireHose Fail FireHose Fail:Attemped to divide by zero. !!!!!!!!!!!!!!????????

    • Create a new folder in desktop, Extract the stock rom and put in the desktop’s new folder which you have created.. The directory name which i have provided is in russian and sometimes doesn’t work. Let me know if this solved. Use QPST, If the above didn’t work. Copy and paste the stock rom in QPST bin folder and try.

      • Validating Application Configuration
        Load APP Configuration
        COM:3
        SAHARA:True
        SAHARA:C:\Program Files\Qualcomm\QPST\bin\new\prog_emmc_firehose.mbn
        SEARCHPATH:C:\Program Files\Qualcomm\QPST\bin\new
        RAWPROGRAM:
        rawprogram0.xml
        PATCH:
        patch0.xml
        ACKRAWDATAEVERYNUMPACKETS:False
        ACKRAWDATAEVERYNUMPACKETS:100
        MAXPAYLOADSIZETOTARGETINBYTES:False
        MAXPAYLOADSIZETOTARGETINBYTES:49152
        DEVICETYPE:eMMC
        PLATFORM:8×26
        READBACKMODE: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
        Load ARG Configuration
        Process Index:0
        Validating Download Configuration
        Image Search Path: C:\Program Files\Qualcomm\QPST\bin\new
        RAWPROGRAM file path: C:\Program Files\Qualcomm\QPST\bin\new\rawprogram0.xml
        PATCH file path:C:\Program Files\Qualcomm\QPST\bin\new\patch0.xml
        Programmer Path:C:\Program Files\Qualcomm\QPST\bin\new\prog_emmc_firehose.mbn
        Image Search Path: C:\Program Files\Qualcomm\QPST\bin\new
        RAWPROGRAM file path: C:\Program Files\Qualcomm\QPST\bin\new\rawprogram0.xml
        PATCH file path:C:\Program Files\Qualcomm\QPST\bin\new\patch0.xml
        Start Download
        Program Path:C:\Program Files\Qualcomm\QPST\bin\new\prog_emmc_firehose.mbn
        COM Port number:3
        Sahara Connecting …
        Sahara Version:2
        Start Sending Programmer
        Sending Programmer Finished
        Switch To FireHose
        Wait for 3 seconds…
        Max Payload Size to Target:49152 Bytes
        Device Type:eMMC
        Platform:8×26
        Disable Ack Raw Data Every N Packets
        Skip Write:False
        Always Validate:False
        Use Verbose:False
        COM Port number:3
        Sending NOP
        FireHose NOP sent successfully
        Sending Configuration
        Device Type:eMMC
        Platform:8×26
        FireHose Log: logbuf@0x0806D768 fh@0x0806A5D0
        Request payload size 0xc000 is not the same as support payload size, change to 0x100000
        Request payload size 0x100000 is too big, reduce to 0x20000
        FireHose Log: logbuf@0x0806D768 fh@0x0806A5D0
        Set TxBuffer 0x20000, RxBuffer 0x4000
        Firehose configure packet sent successfully!
        ReadBackMode:No_Readback
        Disable read back
        Total Bytes To Program 0xD9F52EA0
        Download Image
        PROGRAM: Replace the partition sectors number 0x2a000 to file size in sector 0x289ad
        PROGRAM: Partition 0, Sector: 131072, Length: 166317 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\NON-HLOS.bin
        FireHose Log: start 131072, num 166317
        FireHose Log: Finished sector address 297389
        PROGRAM: Written Bytes 0x5135a00 (64)
        Program Size: 81.21 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2c8
        PROGRAM: Partition 0, Sector: 393234, Length: 712 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\sbl1.mbn
        FireHose Log: start 393234, num 712
        FireHose Log: Finished sector address 393946
        PROGRAM: Written Bytes 0x59000 (64)
        Program Size: 0.35 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2c8
        PROGRAM: Partition 0, Sector: 394258, Length: 712 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\sbl1.mbn
        FireHose Log: start 394258, num 712
        FireHose Log: Finished sector address 394970
        PROGRAM: Written Bytes 0x59000 (64)
        Program Size: 0.35 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
        PROGRAM: Partition 0, Sector: 395282, Length: 328 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\rpm.mbn
        FireHose Log: start 395282, num 328
        FireHose Log: Finished sector address 395610
        PROGRAM: Written Bytes 0x29000 (64)
        Program Size: 0.16 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
        PROGRAM: Partition 0, Sector: 396306, Length: 328 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\rpm.mbn
        FireHose Log: start 396306, num 328
        FireHose Log: Finished sector address 396634
        PROGRAM: Written Bytes 0x29000 (64)
        Program Size: 0.16 MB
        PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4fb
        PROGRAM: Partition 0, Sector: 397330, Length: 1275 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\tz.mbn
        FireHose Log: start 397330, num 1275
        FireHose Log: Finished sector address 398605
        PROGRAM: Written Bytes 0x9f600 (64)
        Program Size: 0.62 MB
        PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4fb
        PROGRAM: Partition 0, Sector: 401426, Length: 1275 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\tz.mbn
        FireHose Log: start 401426, num 1275
        FireHose Log: Finished sector address 402701
        PROGRAM: Written Bytes 0x9f600 (64)
        Program Size: 0.62 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
        PROGRAM: Partition 0, Sector: 405522, Length: 144 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\hyp.mbn
        FireHose Log: start 405522, num 144
        FireHose Log: Finished sector address 405666
        PROGRAM: Written Bytes 0x12000 (64)
        Program Size: 0.07 MB
        PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
        PROGRAM: Partition 0, Sector: 406546, Length: 144 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\hyp.mbn
        FireHose Log: start 406546, num 144
        FireHose Log: Finished sector address 406690
        PROGRAM: Written Bytes 0x12000 (64)
        Program Size: 0.07 MB
        PROGRAM: Partition 0, Sector: 407570, Length: 32768 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\adspso.bin
        FireHose Log: start 407570, num 32768
        FireHose Log: Finished sector address 440338
        PROGRAM: Written Bytes 0x1000000 (64)
        Program Size: 16.00 MB
        PROGRAM: Partition 0, Sector: 440338, Length: 3072 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\dummy.bin
        FireHose Log: start 440338, num 3072
        FireHose Log: Finished sector address 443410
        PROGRAM: Written Bytes 0x180000 (64)
        Program Size: 1.50 MB
        PROGRAM: Partition 0, Sector: 443410, Length: 3072 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\dummy.bin
        FireHose Log: start 443410, num 3072
        FireHose Log: Finished sector address 446482
        PROGRAM: Written Bytes 0x180000 (64)
        Program Size: 1.50 MB
        PROGRAM: Partition 0, Sector: 655360, Length: 64 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\DDR.bin
        FireHose Log: start 655360, num 64
        FireHose Log: Finished sector address 655424
        PROGRAM: Written Bytes 0x8000 (64)
        Program Size: 0.03 MB
        PROGRAM: Replace the partition sectors number 0xc00 to file size in sector 0x42
        PROGRAM: Partition 0, Sector: 655424, Length: 66 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\nv.tar.mbn
        FireHose Log: start 655424, num 66
        FireHose Log: Finished sector address 655490
        PROGRAM: Written Bytes 0x8400 (64)
        Program Size: 0.03 MB
        PROGRAM: Replace the partition sectors number 0x20 to file size in sector 0x1
        PROGRAM: Partition 0, Sector: 658496, Length: 1 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\sec.dat
        FireHose Log: start 658496, num 1
        FireHose Log: Finished sector address 658497
        PROGRAM: Written Bytes 0x200 (64)
        Program Size: 0.00 MB
        PROGRAM: Replace the partition sectors number 0x19000 to file size in sector 0x17bb0
        PROGRAM: Partition 0, Sector: 658528, Length: 97200 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\splash.img
        FireHose Log: start 658528, num 97200
        FireHose Log: Finished sector address 755728
        PROGRAM: Written Bytes 0x2f76000 (64)
        Program Size: 47.46 MB
        PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x709
        PROGRAM: Partition 0, Sector: 760928, Length: 1801 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\emmc_appsboot.mbn
        FireHose Log: start 760928, num 1801
        FireHose Log: Finished sector address 762729
        PROGRAM: Written Bytes 0xe1200 (64)
        Program Size: 0.88 MB
        PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x709
        PROGRAM: Partition 0, Sector: 762976, Length: 1801 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\emmc_appsboot.mbn
        FireHose Log: start 762976, num 1801
        FireHose Log: Finished sector address 764777
        PROGRAM: Written Bytes 0xe1200 (64)
        Program Size: 0.88 MB
        PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x5223
        PROGRAM: Partition 0, Sector: 765024, Length: 21027 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\boot.img
        FireHose Log: start 765024, num 21027
        FireHose Log: Finished sector address 786051
        PROGRAM: Written Bytes 0xa44600 (64)
        Program Size: 10.27 MB
        PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x6a33
        PROGRAM: Partition 0, Sector: 896096, Length: 27187 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\recovery.img
        FireHose Log: start 896096, num 27187
        FireHose Log: Finished sector address 923283
        PROGRAM: Written Bytes 0xd46600 (64)
        Program Size: 13.27 MB
        PROGRAM: Replace the partition sectors number 0x10000 to file size in sector 0x2481
        PROGRAM: Partition 0, Sector: 1048576, Length: 9345 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\persist.img
        FireHose Log: start 1048576, num 9345
        FireHose Log: Finished sector address 1057921
        PROGRAM: Written Bytes 0x490200 (64)
        Program Size: 4.56 MB
        PROGRAM: Replace the partition sectors number 0x800000 to file size in sector 0x628231
        PROGRAM: Partition 0, Sector: 1179648, Length: 6455857 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\system.img
        FireHose Log: start 1179648, num 6455857
        FireHose Log: Finished sector address 7635505
        PROGRAM: Written Bytes 0xc5046200 (64)
        Program Size: 3152.27 MB
        PROGRAM: Replace the partition sectors number 0x80000 to file size in sector 0x30d1
        PROGRAM: Partition 0, Sector: 9568256, Length: 12497 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\cache.img
        FireHose Log: start 9568256, num 12497
        FireHose Log: Finished sector address 9580753
        PROGRAM: Written Bytes 0x61a200 (64)
        Program Size: 6.10 MB
        PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x8
        PROGRAM: Partition 0, Sector: 10092544, Length: 8 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\MISC.img
        FireHose Log: start 10092544, num 8
        FireHose Log: Finished sector address 10092552
        PROGRAM: Written Bytes 0x1000 (64)
        Program Size: 0.00 MB
        PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x16
        PROGRAM: Partition 0, Sector: 10164224, Length: 22 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\param.bin
        FireHose Log: start 10164224, num 22
        FireHose Log: Finished sector address 10164246
        PROGRAM: Written Bytes 0x2c00 (64)
        Program Size: 0.01 MB
        PROGRAM: Replace the partition sectors number 0xa000 to file size in sector 0x22f0
        PROGRAM: Partition 0, Sector: 10166272, Length: 8944 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\panic.img
        FireHose Log: start 10166272, num 8944
        FireHose Log: Finished sector address 10175216
        PROGRAM: Written Bytes 0x45e000 (64)
        Program Size: 4.37 MB
        PROGRAM: Replace the partition sectors number 0x10000 to file size in sector 0x1cca
        PROGRAM: Partition 0, Sector: 10489344, Length: 7370 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\mdtp.img
        FireHose Log: start 10489344, num 7370
        FireHose Log: Finished sector address 10496714
        PROGRAM: Written Bytes 0x399400 (64)
        Program Size: 3.60 MB
        PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x141
        PROGRAM: Partition 0, Sector: 10616832, Length: 321 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\cmnlib.mbn
        FireHose Log: start 10616832, num 321
        FireHose Log: Finished sector address 10617153
        PROGRAM: Written Bytes 0x28200 (64)
        Program Size: 0.16 MB
        PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x153
        PROGRAM: Partition 0, Sector: 10617344, Length: 339 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\keymaster.mbn
        FireHose Log: start 10617344, num 339
        FireHose Log: Finished sector address 10617683
        PROGRAM: Written Bytes 0x2a600 (64)
        Program Size: 0.17 MB
        PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x141
        PROGRAM: Partition 0, Sector: 10617856, Length: 321 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\cmnlib.mbn
        FireHose Log: start 10617856, num 321
        FireHose Log: Finished sector address 10618177
        PROGRAM: Written Bytes 0x28200 (64)
        Program Size: 0.16 MB
        PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x153
        PROGRAM: Partition 0, Sector: 10618368, Length: 339 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\keymaster.mbn
        FireHose Log: start 10618368, num 339
        FireHose Log: Finished sector address 10618707
        PROGRAM: Written Bytes 0x2a600 (64)
        Program Size: 0.17 MB
        PROGRAM: Partition 0, Sector: 10748944, Length: 0 Sectors, Sector Size: 512 Bytes
        File: C:\Program Files\Qualcomm\QPST\bin\new\userdata.img
        FireHose Log: start 10748944, num 0
        Download Fail:FireHose Fail Attempted to divide by zero.
        Finish Download

    • Does the Led light blink when your connect your device to your computer? How did your device get. Do not worry snapdragon devices are unbrickable i’m sure you can get back your device working by following my guide.

      • Thanks a lot. The phone starts and works very well. 🙂 🙂 🙂
        However, I have a problem with IMEI. He cleared up. Can you help how to restore it?

      • Do you know your IMEI number? If not find it on your box piece. If you know your both IMEI number you can fix it. You have to be on EUI rom to flash IMEI number.

      • Barrow you’re friend’s qcn file. Change the IMEI number of his file and replace with your IMEI number.
        Put the device into USB Diagnostics mode. Flash through QPST server.

      • Download IMEI Re-builder software put you’re IMEI number and build a qcn file and flash it through QPST Server.
        To enter into DIAG MODE.
        Connect the device to your phone or Install an terminal app. Type the following command
        adb shell
        su
        setprop sys.usb.config diag
        exit
        This commands will put your phone in DIAG mode, the QPST software will detect the phone and flash your qcn file rebuilt by your IMEI. Do not flash wrong IMEI 4G doesn’t work.

      • hi. Thank you for your concern, now I’ve got eui5.8 and the phone is working right, though I discover the phone doesn’ t have the imei numbers. I don’t understand very well, if you don’t have a qcn file you cannot restore the imei? I’ve got the numbers from the box, but I don’t have a qcn file. Could you explain how to restore the imeis?
        Thank you!

      • Hi, If you don’t have a qcn file, You can barrow one of your friends or have my qcn file, Rebuild the qcn file replacing my IMEI number with your IMEI number rebuild the file using IMEI re-builder software. Flash the newly built .qcn file to your phone using qpst server in the download mode option.

  11. I fixed my imei no. Didn’t use yours. But the Meid is still yours I’ll change it once I figure out how to.

  13. Hi Jay! My phone is bricked. I need some serious help. It is just blinking after I connect it to PC or charger and “blink” not a continuous emission. I did this after I installed a wrong TWRP maybe. And it is not booting up after that. Tried QFIL, says Sahara error, even though drivers are correct. Tried YGDP, no luck. It’s showing connected in PORT in QFIL, but no luck. Please help me, I am screwed real bad this time and I am panicking since yesterday, there’s no phone. Also, kindly send me the rom link to alokd1205@gmail.com. Eagerly waiting for your reply….. 🙁

    • Hi Alok, I have sent you the ROM link. As you’re here you don’t need to panic. The phone will be come back to life just read the guide carefully and follow the steps one by one.

    • Ahwww, Thank you 🙂 . You’re very kind. The donation will be spent on better construction and maintenance of website

      • Hi, i tried to install the ROM using QFIL – it went and i got message “Download succesful”. But the phone still isn’t booting, and when i try to connect it to PC, PC doesn’t recognize it. What should i do? I can’t even see it through QFIL now.

      • Hmm, i have get it back to being recognized by QFIL. But I can flash ROM, recovery or whatever and it still doesn’t start :/

      • How did you brick you’re device? If this method didn’t work for you. When you’re phone bricked it would have corrupted NAND memory or simply broke some hardware components. It’s good to contact service center if the above method didn’t work.

      • Actually, it worked after few tries. (had to flash ROM for ~4-5 times). Now i have problem with getting second IMEI, on my phone package i have only 1. :/

      • And the second problem I have, it’s that my phone plays only on my left headphone channel. It worked normally before flash. (i bricked it while miflashing and forget to set to save user files, it flashed with delete all and lock).

      • The headphone problem is not related to rom. Play with the headphone jack you will hear it on both sides…check with other headphones.
        You can fix the IMEI number by flashing the qcn file. Use Coolpad assistant and clean flash 5.18s eui rom.

      • i created new qcn file but ,mr jay kumar , phone cant connect to pc or laptop after rooting, only charging if i connects ,if i unroot device it connects easilly in any mode with pc and laptop , your command method is only for rooted devices, right?

      • Hi, Chetan.
        You’re device must be rooted to delete the EFS file system and re-write it by flashing qcn file. I understand the problem you’re facing i was in this situation before, To overcome this issue root you’re phone and install magisk not SuperSu.
        First flash this TWRP Rooting Guide and flash magisk 14.0. flashing 15.x will cause you’re phone to softbrick but after flashing magisk 14.0 you can upgrade.

        Now you will have root permission and also pc gets connected in any mode.

  20. Hello Jay. Quick question, when I flash any other eui version, I get a ringing sound on video and audio recordings, have you experienced this?
    Only 5.8.17s doesn’t have the ringing.

  29. hey bro can i install this rom with twrp in coolpadcool1….my device is bricked…but i have found a way to move files from my pc to it when i am opening twrp

    • Hi,
      Yeah you can flash TWRP recovery in EUI rom. You mean you want to take backup of you’re bricked device through PC? If you can access TWRP,Yes you can take backup. As you have already mentioned that you can access TWRP your device is not completely bricked. Just flash the stock rom in TWRP install Option.

  34. my phone also brick i need your help.
    when i connected to pc Led light blink but after few minutes Led light stop blinking and screen light turn on into gray light.

    • Hi,
      A guy on internet had coolpad r116 had contacted me on facebook, He said it works.
      I don’t have rr116 device i’m not sure,
      But r116 is same as c106, If you it works let me know.
      I have sent you the rom link and the qcn file to your mail ID.

  36. not able to unbrick my coolpad cool 1 🙁 Qloader loaded always getting
    attempted to devide by zero error.. please help..

    • You will unbrick you’re device if you flash my rom. I have sent you the rom link to you’re mail ID, Thanks

  43. my phone is bricked and its not showing anything the phone is not getting on and the pc is not detecting the phone, plz help

      • Sorry, I don’t have coolpad note 3. Take some help over Xda-developers forum. If you’re device is bricked you just need to have a qfil flashable rom link, You can create the flashable rom using cpb extractor.

      • Hello
        thx for the ROM, but I have a problem during install it…
        after start updating by QFIL, when SYSTEM.IMG is writing I have a ERROR:

        17:35:43: INFO: Overall to target 169.000 seconds (18.45 MBps)
        17:35:43: INFO: {percent files transferred 74.36%}
        _____
        | |
        | |         _ __ _ __ ___ _ __
        | | ‘| ‘/ _ | ‘|
        | || | | | | (_) | |
        _        /| || ___/||
        17:35:45: {ERROR: Read 0 bytes from ‘C:\Users\porad\Downloads\UnbrickQFIL\UnbrickQFIL\system.img’}
        _____
        | _|
        | |         _ __ _ __ ___ _ __
        | | ‘| ‘/ _ | ‘|
        | || | | | | (_) | |
        _        /| || ___/|_|
        17:35:45: {ERROR: There are still 1932751 sectors to go}
        Writing log to ‘C:\Users\porad\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’, might take a minute
        Log is ‘C:\Users\porad\AppData\Roaming\Qualcomm\QFIL\port_trace.txt’
        Download Fail:FireHose Fail FHLoader Fail:Process fail
        Finish Download

        Its always in the same time. This file is damage? Could You explain me? Thank You

    • Go through my youtube video. All you have to do is flash .qcn file through QPST server and you’re IMEI numbers will work.
      I have sent you the .qcn file, check you’re mail.

  59. Hello ! Mei name and Sandro, I speak from Brazil, I’m trying to fix my Lego coolpad 1 C103, It’s bricked and it’s just red led flashing when it plugs into the pc, Please you could send me the ROM and the CQN I have 3 phones In this same problem, please help me. Thank you very much.

  64. Hi,
    I’ve shredded a Coolpad C1-U02 R116, with a TWRP installation
    When I press Power and VOL + I will see the Fastboot mode on the screen. On the computer, it is only recognized as an unknown device. Therefore, the Coolpad driver was manually installed, but ADB does not recognize the device. QPST / QFIL does not work either. The connection is via USB, but the device only identifies itself as an unknown device. Is there still a possibility to flash the device with a ROM?

    • Hi, You have to put you’re device in qualcom Qloader 9008 mode in order to view in QPST and QFIL. If you’re device identifies as unknown device i would advise you to download the Google’s Qualcomm Qloader Drivers and updated them manually. The best way to get you’re device in 9008 mode is plug in the USB cable and Press and hold all the three buttons until red led light flashes for 5 seconds.

  65. Please forward me the file at sarthak.vazzracharya@gmail.com
    I have bricked my phone after updating to chinese JUI in rooted the device and flashed miui 10 it asked Password and after 3 times reboot its dead only blinks red light while connected to USB and not detected by coolpad download assistant and YDP but Qfil does in 9008 mode

    • Hi, I understand that MIUI 10 is based on Android 6. Hence you’re device was bricked. I would also like to try MIUI 10 on cool 1 running currently on EUI. Tell me how did the flash go through and have you found any bugs? is the rom stable?

      I have sent the link of the rom to you’re mail id. Please check Thanks.

  69. Hello, where can i find a ROM for QFIL restore ? I have a device c103 0x04 with bootloop, Coolpad Download Manager and YGDP works fine, but bootloop still persist 🙁 Thank in advance

  75. I’ve installed miui 10 rom by mistake on top of jui rom. The phone does not turn on at this time. It appears to be 9008 on the device manager. You can’t get any way to download fashion. can not load rom. Could you please send the rom link.
    afyden@yahoo.co

  76. My friend sent me the link. But when I want to install it with qfil I get the following error. Can you help with this

    Validating Application Configuration
    Load APP Configuration
    COM:4
    SAHARA:True
    SAHARA:C:\Users\binnur\Desktop\1\1\prog_emmc_firehose.mbn
    SEARCHPATH:C:\Users\binnur\Desktop\1\1
    RAWPROGRAM:
    rawprogram0.xml
    PATCH:
    patch0.xml
    ACKRAWDATAEVERYNUMPACKETS:False
    ACKRAWDATAEVERYNUMPACKETS:100
    MAXPAYLOADSIZETOTARGETINBYTES:False
    MAXPAYLOADSIZETOTARGETINBYTES:49152
    DEVICETYPE:eMMC
    PLATFORM:8×26
    READBACKMODE:0
    RESETAFTERDOWNLOAD:False
    MAXDIGESTTABLESIZE:8192
    SWITCHTOFIREHOSETIMEOUT:30
    RESETTIMEOUT:200
    RESETDELAYTIME:2
    FLATBUILDPATH:C:\
    FLATBUILDFORCEOVERRIDE:True
    QCNPATH:C:\Temp\00000000.qcn
    QCNAUTOBACKUPRESTORE:False
    SPCCODE:000000
    Load ARG Configuration
    Process Index:0
    Validating Download Configuration
    Image Search Path: C:\Users\binnur\Desktop\1\1
    RAWPROGRAM file path: C:\Users\binnur\Desktop\1\1\rawprogram0.xml
    PATCH file path:C:\Users\binnur\Desktop\1\1\patch0.xml
    Programmer Path:C:\Users\binnur\Desktop\1\1\prog_emmc_firehose.mbn
    Image Search Path: C:\Users\binnur\Desktop\1\1
    RAWPROGRAM file path: C:\Users\binnur\Desktop\1\1\rawprogram0.xml
    PATCH file path:C:\Users\binnur\Desktop\1\1\patch0.xml
    Start Download
    Program Path:C:\Users\binnur\Desktop\1\1\prog_emmc_firehose.mbn
    COM Port number:4
    Sahara Connecting …
    Sahara Version:2
    Start Sending Programmer
    Sending Programmer Finished
    Switch To FireHose
    Wait for 3 seconds…
    Max Payload Size to Target:49152 Bytes
    Device Type:eMMC
    Platform:8×26
    Disable Ack Raw Data Every N Packets
    Skip Write:False
    Always Validate:False
    Use Verbose:False
    COM Port number:4
    Sending NOP
    FireHose NOP sent successfully
    Sending Configuration
    Device Type:eMMC
    Platform:8×26
    FireHose Log: logbuf@0x0806D768 fh@0x0806A5D0
    Request payload size 0xc000 is not the same as support payload size, change to 0x100000
    Request payload size 0x100000 is too big, reduce to 0x20000
    FireHose Log: logbuf@0x0806D768 fh@0x0806A5D0
    Set TxBuffer 0x20000, RxBuffer 0x4000
    Firehose configure packet sent successfully!
    ReadBackMode:No_Readback
    Disable read back
    Total Bytes To Program 0xD9F52EA0
    Download Image
    PROGRAM: Replace the partition sectors number 0x2a000 to file size in sector 0x289ad
    PROGRAM: Partition 0, Sector: 131072, Length: 166317 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\NON-HLOS.bin
    FireHose Log: start 131072, num 166317
    FireHose Log: Finished sector address 297389
    PROGRAM: Written Bytes 0x5135a00 (64)
    Program Size: 81.21 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2c8
    PROGRAM: Partition 0, Sector: 393234, Length: 712 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\sbl1.mbn
    FireHose Log: start 393234, num 712
    FireHose Log: Finished sector address 393946
    PROGRAM: Written Bytes 0x59000 (64)
    Program Size: 0.35 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2c8
    PROGRAM: Partition 0, Sector: 394258, Length: 712 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\sbl1.mbn
    FireHose Log: start 394258, num 712
    FireHose Log: Finished sector address 394970
    PROGRAM: Written Bytes 0x59000 (64)
    Program Size: 0.35 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
    PROGRAM: Partition 0, Sector: 395282, Length: 328 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\rpm.mbn
    FireHose Log: start 395282, num 328
    FireHose Log: Finished sector address 395610
    PROGRAM: Written Bytes 0x29000 (64)
    Program Size: 0.16 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x148
    PROGRAM: Partition 0, Sector: 396306, Length: 328 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\rpm.mbn
    FireHose Log: start 396306, num 328
    FireHose Log: Finished sector address 396634
    PROGRAM: Written Bytes 0x29000 (64)
    Program Size: 0.16 MB
    PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4fb
    PROGRAM: Partition 0, Sector: 397330, Length: 1275 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\tz.mbn
    FireHose Log: start 397330, num 1275
    FireHose Log: Finished sector address 398605
    PROGRAM: Written Bytes 0x9f600 (64)
    Program Size: 0.62 MB
    PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4fb
    PROGRAM: Partition 0, Sector: 401426, Length: 1275 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\tz.mbn
    FireHose Log: start 401426, num 1275
    FireHose Log: Finished sector address 402701
    PROGRAM: Written Bytes 0x9f600 (64)
    Program Size: 0.62 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
    PROGRAM: Partition 0, Sector: 405522, Length: 144 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\hyp.mbn
    FireHose Log: start 405522, num 144
    FireHose Log: Finished sector address 405666
    PROGRAM: Written Bytes 0x12000 (64)
    Program Size: 0.07 MB
    PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x90
    PROGRAM: Partition 0, Sector: 406546, Length: 144 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\hyp.mbn
    FireHose Log: start 406546, num 144
    FireHose Log: Finished sector address 406690
    PROGRAM: Written Bytes 0x12000 (64)
    Program Size: 0.07 MB
    PROGRAM: Partition 0, Sector: 407570, Length: 32768 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\adspso.bin
    FireHose Log: start 407570, num 32768
    FireHose Log: Finished sector address 440338
    PROGRAM: Written Bytes 0x1000000 (64)
    Program Size: 16.00 MB
    PROGRAM: Partition 0, Sector: 440338, Length: 3072 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\dummy.bin
    FireHose Log: start 440338, num 3072
    FireHose Log: Finished sector address 443410
    PROGRAM: Written Bytes 0x180000 (64)
    Program Size: 1.50 MB
    PROGRAM: Partition 0, Sector: 443410, Length: 3072 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\dummy.bin
    FireHose Log: start 443410, num 3072
    FireHose Log: Finished sector address 446482
    PROGRAM: Written Bytes 0x180000 (64)
    Program Size: 1.50 MB
    PROGRAM: Partition 0, Sector: 655360, Length: 64 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\DDR.bin
    FireHose Log: start 655360, num 64
    FireHose Log: Finished sector address 655424
    PROGRAM: Written Bytes 0x8000 (64)
    Program Size: 0.03 MB
    PROGRAM: Replace the partition sectors number 0xc00 to file size in sector 0x42
    PROGRAM: Partition 0, Sector: 655424, Length: 66 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\nv.tar.mbn
    FireHose Log: start 655424, num 66
    FireHose Log: Finished sector address 655490
    PROGRAM: Written Bytes 0x8400 (64)
    Program Size: 0.03 MB
    PROGRAM: Replace the partition sectors number 0x20 to file size in sector 0x1
    PROGRAM: Partition 0, Sector: 658496, Length: 1 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\sec.dat
    FireHose Log: start 658496, num 1
    FireHose Log: Finished sector address 658497
    PROGRAM: Written Bytes 0x200 (64)
    Program Size: 0.00 MB
    PROGRAM: Replace the partition sectors number 0x19000 to file size in sector 0x17bb0
    PROGRAM: Partition 0, Sector: 658528, Length: 97200 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\splash.img
    FireHose Log: start 658528, num 97200
    FireHose Log: Finished sector address 755728
    PROGRAM: Written Bytes 0x2f76000 (64)
    Program Size: 47.46 MB
    PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x709
    PROGRAM: Partition 0, Sector: 760928, Length: 1801 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\emmc_appsboot.mbn
    FireHose Log: start 760928, num 1801
    FireHose Log: Finished sector address 762729
    PROGRAM: Written Bytes 0xe1200 (64)
    Program Size: 0.88 MB
    PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x709
    PROGRAM: Partition 0, Sector: 762976, Length: 1801 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\emmc_appsboot.mbn
    FireHose Log: start 762976, num 1801
    FireHose Log: Finished sector address 764777
    PROGRAM: Written Bytes 0xe1200 (64)
    Program Size: 0.88 MB
    PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x5223
    PROGRAM: Partition 0, Sector: 765024, Length: 21027 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\boot.img
    FireHose Log: start 765024, num 21027
    FireHose Log: Finished sector address 786051
    PROGRAM: Written Bytes 0xa44600 (64)
    Program Size: 10.27 MB
    PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x6a33
    PROGRAM: Partition 0, Sector: 896096, Length: 27187 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\recovery.img
    FireHose Log: start 896096, num 27187
    FireHose Log: Finished sector address 923283
    PROGRAM: Written Bytes 0xd46600 (64)
    Program Size: 13.27 MB
    PROGRAM: Replace the partition sectors number 0x10000 to file size in sector 0x2481
    PROGRAM: Partition 0, Sector: 1048576, Length: 9345 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\persist.img
    FireHose Log: start 1048576, num 9345
    FireHose Log: Finished sector address 1057921
    PROGRAM: Written Bytes 0x490200 (64)
    Program Size: 4.56 MB
    PROGRAM: Replace the partition sectors number 0x800000 to file size in sector 0x628231
    PROGRAM: Partition 0, Sector: 1179648, Length: 6455857 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\system.img
    FireHose Log: start 1179648, num 6455857
    FireHose Log: Finished sector address 7635505
    PROGRAM: Written Bytes 0xc5046200 (64)
    Program Size: 3152.27 MB
    PROGRAM: Replace the partition sectors number 0x80000 to file size in sector 0x30d1
    PROGRAM: Partition 0, Sector: 9568256, Length: 12497 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\cache.img
    FireHose Log: start 9568256, num 12497
    FireHose Log: Finished sector address 9580753
    PROGRAM: Written Bytes 0x61a200 (64)
    Program Size: 6.10 MB
    PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x8
    PROGRAM: Partition 0, Sector: 10092544, Length: 8 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\MISC.img
    FireHose Log: start 10092544, num 8
    FireHose Log: Finished sector address 10092552
    PROGRAM: Written Bytes 0x1000 (64)
    Program Size: 0.00 MB
    PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x16
    PROGRAM: Partition 0, Sector: 10164224, Length: 22 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\param.bin
    FireHose Log: start 10164224, num 22
    FireHose Log: Finished sector address 10164246
    PROGRAM: Written Bytes 0x2c00 (64)
    Program Size: 0.01 MB
    PROGRAM: Replace the partition sectors number 0xa000 to file size in sector 0x22f0
    PROGRAM: Partition 0, Sector: 10166272, Length: 8944 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\panic.img
    FireHose Log: start 10166272, num 8944
    FireHose Log: Finished sector address 10175216
    PROGRAM: Written Bytes 0x45e000 (64)
    Program Size: 4.37 MB
    PROGRAM: Replace the partition sectors number 0x10000 to file size in sector 0x1cca
    PROGRAM: Partition 0, Sector: 10489344, Length: 7370 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\mdtp.img
    FireHose Log: start 10489344, num 7370
    FireHose Log: Finished sector address 10496714
    PROGRAM: Written Bytes 0x399400 (64)
    Program Size: 3.60 MB
    PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x141
    PROGRAM: Partition 0, Sector: 10616832, Length: 321 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\cmnlib.mbn
    FireHose Log: start 10616832, num 321
    FireHose Log: Finished sector address 10617153
    PROGRAM: Written Bytes 0x28200 (64)
    Program Size: 0.16 MB
    PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x153
    PROGRAM: Partition 0, Sector: 10617344, Length: 339 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\keymaster.mbn
    FireHose Log: start 10617344, num 339
    FireHose Log: Finished sector address 10617683
    PROGRAM: Written Bytes 0x2a600 (64)
    Program Size: 0.17 MB
    PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x141
    PROGRAM: Partition 0, Sector: 10617856, Length: 321 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\cmnlib.mbn
    FireHose Log: start 10617856, num 321
    FireHose Log: Finished sector address 10618177
    PROGRAM: Written Bytes 0x28200 (64)
    Program Size: 0.16 MB
    PROGRAM: Replace the partition sectors number 0x200 to file size in sector 0x153
    PROGRAM: Partition 0, Sector: 10618368, Length: 339 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\keymaster.mbn
    FireHose Log: start 10618368, num 339
    FireHose Log: Finished sector address 10618707
    PROGRAM: Written Bytes 0x2a600 (64)
    Program Size: 0.17 MB
    PROGRAM: Partition 0, Sector: 10748944, Length: 0 Sectors, Sector Size: 512 Bytes
    File: C:\Users\binnur\Desktop\1\1\userdata.img
    FireHose Log: start 10748944, num 0
    Download Fail:FireHose Fail FireHose Fail:Sıfırla bölme girişiminde bulunuldu.
    Finish Download

  82. Hey man can you give mi link for rom coolpad? I had this rom but i clean my computer and everythig go. I used your solution earlier and it is good.

      • I downloaded the rum from your link. I changed the folder name. When I try to set up with Qfil, it gives the sahara error.
        Can you help me? download fail sahara. Phone device manager looks as 9008 and 900e.

  83. I’m reinstalling with qfil. 74% also fails and the phone never turns on. The only HS-USB QDLoader 9008 looks when you can’t get edl fashion. In the device manager. Please help.

Leave a Reply to Jay Kumar Ryan Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.