Database Users

[Q] Officially Bricked?

Current Status: Brick
Hi,
I tried flashing stock SBF CEE 3.4.2-179-2 (retail central Europe) from here http://sbf.droid-developers.org/umts_jordan/list.php
I get IO and checksum errors resulting in FAIL. Now the phone does not boot.
Boot Loader
Code:
Bootloader
09.10
[B]Code Corrupt[/B]
Battery OK
OK to Program
Connect USB Data Cable
With RSD Lite 5.7 on Windows XP and MotoHelper drivers MotoHelper_2.0.40_Driver_4.9.0.exe
RSD Lite log::
2012/12/20 02:05:45 | -- | ERROR: AP Die ID: 1b10000791b963010000dcff0200
2012/12/20 02:05:45 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/12/20 02:05:45 | -- | ERROR: AP Public ID: 35bc21063d231f528e8ce8e9b9942dcd161967c5
2012/12/20 02:05:45 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 ->(1557)FlashOp
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:13:03 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2012/12/20 02:26:03 | 0 | ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 ->(625)FlashHdlr
Click to expand...
Click to collapse
Based on advice from skeevy420, I tried flashing with sbf_flash on linux.
sbf_flash:
Code:
Index[1]: Unexpected chip 32
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
It looks like writing (or reading) fails, resulting in checksum errors.
More Info:
Verified MD5 of all my downloads
Tried a couple of other SBF from the same version (3.4.2)
Phone is from T-Mobile USA
Can I do something to change brick status?
Do I need a different SBF version?
Does read/write error really means hardware problem, cannot be fixed by software?
Do those IO errors mean driver version problem?
New sbf not compatible with old (old was stock T-Mobile Froyo)?
Accept the fact that the phone is hopeless?
Any help appreciated!

Here's a basic tutorial to flash sbf's with Linux -- RSDLite quit recognizing my Bravo and the Linux sbf_flash tool was the only way to fix it. You may have to install the Linux adb drivers, not sure, but those instructions are on Kayant's Compile CM10 thread (first post).
After flashing, you might have to go to factory recovery and wipe data and cache in order for the phone to boot -- maybe even have to flash a 2nd or 3rd time. I once had to flash the sbf AND wipe data\cache 5 times in a row in order to get my Bravo to boot up after accidentally flashing a Defy boot.img (usually only 1 flash is needed, I do stupid things with my phones)

Thanks, I will give this a try.
Do you install linux on the drive (like dual boot) or boot from a CD? If you boot from a CD, how do you install motorola drivers?
Just did MD5 checksum of all my downloaded files and they are all good.

Tried it with linux, getting similar errors:
Code:
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed

Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium

Just a silly idea: is your USB cable/PC USB port OK? Try it on another PC and with another cable. Use a cable as short as possible and make sure that the phone is the only device connected to the PC via USB including the mouse.
Sent from my MB526 using xda app-developers app

thekguy said:
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, I think you are right.
I tried the omap option, did not help. Any other tweaks I can do to RSD light?
As far as USB, its the stock motorola cable. I disconnected everything from the computer, basically a laptop with nothing around it. I dont think its the problem, I tried over 10 sbfs and they all consistently show the same errors.

I am gonna hijack this thread...
So I believe I bricked the Defy I was supposed to be fixing.
It was acting up, the battery was sometimes showing a ? mark, and the rom it was flashed with was super buggy.
I decided to flash it with this sbf
Code:
T-Mobile_MB525_6.19.0_1FF
from here (Because I had read that it was the stock 2.1 Eclair from T-Mobile, the one the one was running originally.)
Now it won't boot.
Edit: The battery was dead. The cable was faulty so it cause a problem while flashing. Managed to get back at bootloader. Re-trying again but with:
Code:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
EDIT 2: The keyboard is not working so I can't logging into motoblur ._." Frustration... Going to keep flashing to see if its the screen of my phone or the actual program.
Edit 3: It appears it was the screen sensors being dirty. All solved.
-Defy MB525 GREEN LENS-

Any solution for this??

ChavitoArg said:
Any solution for this??
Click to expand...
Click to collapse
Try This
http://forum.xda-developers.com/showthread.php?t=1486731

I am having same problems flashing my defy. Tried different kinds of sbf using rsd lite but keep getting error verifying group code checksums from code 33 onwards...then flashing fails.
Any solutions??

[Q] Errors when attempting to SBF reset

So I Found my old Droid X earlier this week the battery was bad so I got a new one and I attempted to restore the device using tomsgt123's (RootJunky) video (I can't post links ) and RSDlite must have froze on me because it got stuck and 98% of something to do with ram (I can't find a log so I can't rely be more specific) and then I let it sit thinking it was just taking a while and I came back nothing was on the program and my device just says code corrupted battery low cannot program.
So what I am wondering is if I can retry If i can manage to get the battery charged or if this thing just became a brick
I should also mention that when I pressed start on RSDlite my battery was fully charged
Thank You in advance if you can help me.
Edit I found a log actually
2014/07/04 10:51:29 | -- | ERROR: AP Die ID: 1e300210fa903a0a0000d8ff0100
2014/07/04 10:51:29 | -- | ERROR: BP Die ID: 0000000000000000b55432890485
2014/07/04 10:51:29 | -- | ERROR: AP Public ID: 2469367a1407acd048a3f1e89f054bd90523fa08
2014/07/04 10:51:29 | -- | ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
2014/07/04 11:14:29 | 0 | ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR ->(970)RDLOp
2014/07/04 11:14:29 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2014/07/04 11:14:31 | 0 | ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257 ->(625)FlashHdlr

Motorola Drivers are not installed on windows.
Install drivers or use DX (MB810) ezSBF & Root 2.3.4/4.5.621

Ill Try
Ok, Thanks I thought I had the drivers installed already though as Ive already done some work on other motorola devices this week. But I'm ordering a battery charger should be here in a couple days and I'm going to try the live CD method Ive already burned the CD so Thanks

Droid RAZR M: Qflash Utility Help

QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .

[HowTo] Flash a stock ROM

Flash guide ZUK Z2 Pro - （Z2121）(QPST/QFIL):
-------------
Preamble:
This upgrade your Phone to Z2 Pro_CN_OPEN_USER_Q01002.1_M_ZUI_1.9.038_ST_160503 version, for example. Use the latest version of the software or the version for the actual operation.
Backup your data before processing the flash, in order to avoid loss of data!
-------------
--You'll need a USB-C data cable to proceed--
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Theoretical it is possible to recover a bricked via this method. I you do this for the first time you need to download some tools. Without downloading and installing the tools this procedure will take about 4 minutes.
1.1 Download flashtool Download flashtool and ZUK USB driver
Code:
Download Flashtool
###REQUIRED### (QPST 2.7.434)
https://www.androidfilehost.com/?fid=24591000424948456
Download USB Drivers
###REQUIRED### (ZUK)
https://www.androidfilehost.com/?fid=24659325368664618
optional (Qualcomm normally installed by QPST flashtool setup)
https://www.androidfilehost.com/?fid=24591020540824824
Download and extract ADB and fastboot
Code:
###REQUIRED###
https://www.androidfilehost.com/?fid=24671318762848778
**Attention**
If you have Windows 8, 8.1, 10 installed, you have to disable driver verification.
See post #13 http://zukfans.eu/community/threads...://club.lenovo.com.cn/thread-1811698-1-1.html
ROM Source: http://club.lenovo.com.cn/thread-1812430-1-1.html​

Flash guide ZUK Z2 Pro internal SD-Card:
---This method only works, if your phone is able to boot---
Note:
Code:
Usually no data will be wiped. But to be save do a backup first.
##############A T T E N T I O N##############
DO NOT TRY TO FLASH VIA THIS METHOD, IF YOUR PHONE HAS A CUSTOM FIRMWARE *¹ !
If you try this nevertheless you phone will be bricked!​
#########################################
Information
If your phone has a official ROM/Firmware installed but it is rooted etc. it will work without bricks.
Let's get started
1.0 Download Firmware/ROM (.QSB)
Code:
###REQUIRED###
https://www.androidfilehost.com/?w=files&flid=94094
1.0.1 Extract the .7z file with ROM/Firmware you downloaded at 1.0
1.0.2 Connect the phone via USB-C cable to your computer and create a folder called "sdfuse" at the root of your internal storage.
1.0.3 Copy all the exctracted .qsp files into the sdfuse folder.
1.0.4 Shutdown the phone.
1.0.5 Hold down the volume- button and power on the phone. At second vibration release the power button, but still hold the volume- button. Now the developer recovery menue should be shown.
1.0.6 Select "Sd update" and confirm with power button.
1.0.7 Hit "apply" or "OK" with tapping on it. Now the flashing procedure will start immediatly. After this was successful hit the reboot button and you're done.
*¹ You flashed a Custom ROM via TWRP means Custom Firmware / Custom ROM. Furthermore if your merchant flashed a ROM with multilanguage support (more than English and Chinese) and it's unable to gain OTA update (non rooted - if you don't know what this is you are not rooted!) your device running on a Custom Firmware!

###################
FAQ:
Q: Is it possible to install via SD-Card update even if my bootloader is unlocked and my phone is rooted?
A: Yes, see video to convince yourself:
https://www.youtube.com/watch?v=-TwhMjePiTE
Q: It is'nd possible to get OTA updates alway got promting "No internet connection" how to fix this?
A: If you 1st try to delete data and cache from "Sys Upd" and reboot your phone, try again. If this will not solve this problem try to connect via Chinese VPN-Server. Head over to this thread: http://zukfans.eu/community/threads/ota-update-solution-for-noobs-like-me.192/
Thank you Donát Szabó for your support!
Q: How to install Google Play Store?
A: Download and install the APKs in this package: https://www.androidfilehost.com/?fid=24671318762848780
Q: I'm having trouble to get Google Play Store working, Error: "Can't download app.. XYZ can't be downloaded. Try again, and if the proble continues, get help toubleshooting. (Error retrieving information from server. [DF-DLA-15])
A: 1st update Google Play Store via "apkmirror.com". If the problem still occurs:
1. delete your Google Account from your mobile phone(Sync Data first!)
2. delete data and cache from Google Play Services and Google Play store (APP)
3. reboot your phone
4. singn in to your Google Account and try again to intall APPs from Google Play Store APP.
Q: How to get Google Contacts sync woking?
A: Download and install the APKs in this package: https://www.androidfilehost.com/?fid=24671318762848780
Q: I got this message: "Fail to load contents.xml: Invaild Path for Meta Build CONTENT XML, ignored: C:\...\...\contents.xml" how do I fix this?
A: Maybe the folder names are to long (NTFS ~200 caracters), rename the folder with the contents.xml located in to "abc" for example.
Q: I need a password to extract the archive.
A: Try "club.lenovo.com.cn" without the potation marks.
Q: I can press the Download-Button ... but the download failed with error:
"Download Fail:Sahara Fail: QSahara Server Fail: The name of directory is invalid
Finish download"
A: Try to close and reopen QFIL again, also unplug and replug your phone.
Still not fixed? Reboot your PC, Phone.
Q: While flashing process I got error: "Download Fail: Sahara Fail:QSaharaServer Fail: Process Fail". How to fix this?
A: You need to copy the ROM files into a short named folder and filename on the root of a harddrive.
Q: I still have issues with QFIL/QPST: "Download Fail: Sahara Fail:QSaharaServer Fail: Process Fail". Any solution?
A: Try this short tutorial: http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
(Thanks syedtahir16)
Q: How to relock the bootloader, if I unlocked it?
A: You only need to open a command promt and fastboot.exe. Type "fastboot oem lock" into that command promt while the phone has to be in fastboot mode.
Q: Were to get into fastboot mode?
A: Open a command promt and type in "adb reboot-bootloader". In return your phone has to be connected via USB and "USB debugging" must be enabled.
Q: How do I change the language from Chines to English?
A: Click this video, this will show you how to:
Q: How can I start into TWRP?
A: Try to download this TWRP: https://www.androidfilehost.com/?fid=24591000424960393
Reboot into Fastboot Mode and run this command: fastboot -i 0x2b4c boot recovery.img
Q: Is there a secret menu, where I can test there components?
A:Yes, try *#*#1111#*#*
Q: I'm unable to access the developer recovery where I'm flashing the Sdupdate. Is there a detailed manual?
A: Take a look here: http://zukfans.eu/community/index.php?posts/6160
(Thanks to schupfer)
###################​

Half-bricked
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
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:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.

password for rom z2 pro
hello, when extracting the Rom you ask me what a password, send me through my email [email protected]

Hello,
If you read the entire post, you will find it I promise .
FAQ is always your best friend.

I am also having the same issue. I am currently on mokee custom rom. I want to return to stock and can enter edl mode. Phone is detected as usb-qdloader 9008. Tried QPST tool on 2 different computers, both have the same sahara fail error. Any help guys?

You need to extract all ROM files into drive C using a short folder name
e.g. C:\zuk\
no subfolders

Mathisou said:
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
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:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.
Click to expand...
Click to collapse
Please help me. I have the same . Even short path c/zuk dont work

Wow thank you for posting this!

Mathisou said:
Hello,
I just recieved my new phone and wanted to update it right away but at this end I got it bricked , so fast...
At first, I followed your 2nd method via internal-sd.
Everything went ok until the reboot.
Unfortunately, it gets stuck at the ZUK logo.
Nothing moving forward.
So then I used the first method, QPST/QFIL one.
But here comes a new problem, at one point, I get the following error message:
Download Fail: Sahara Fail:QSaharaServer Fail: Process fail.
Could you please help me to make it works?
Here is the complete log:
Validating Application Configuration
Load APP Configuration
COM:7
SAHARA:True
SAHARA:
SEARCHPATH:C:\
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
METABUILD:C:\abc\abc\contents.xml
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
Meta Build Content XML Path: C:\abc\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\abc\.\
Search File: patch0.xml
search form search path:C:\abc\abc\.\
Search File: patch1.xml
search form search path:C:\abc\abc\.\
Search File: patch2.xml
search form search path:C:\abc\abc\.\
Search File: patch3.xml
search form search path:C:\abc\abc\.\
Search File: patch4.xml
search form search path:C:\abc\abc\.\
Search File: patch5.xml
search form search path:C:\abc\abc\.\
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\abc\.\rawprogram5.xml
PATCH file path:C:\abc\abc\.\patch0.xml
PATCH file path:C:\abc\abc\.\patch1.xml
PATCH file path:C:\abc\abc\.\patch2.xml
PATCH file path:C:\abc\abc\.\patch3.xml
PATCH file path:C:\abc\abc\.\patch4.xml
PATCH file path:C:\abc\abc\.\patch5.xml
Process Index:0
Meta Build Content XML Path: C:\abc\contents.xml
Search File: prog_ufs_firehose_8996_ddr.elf
search form search path:C:\abc\.\
Search File: rawprogram_unsparse0.xml
search form search path:C:\abc\.\
Search File: rawprogram1.xml
search form search path:C:\abc\.\
Search File: rawprogram2.xml
search form search path:C:\abc\.\
Search File: rawprogram3.xml
search form search path:C:\abc\.\
Search File: rawprogram_unsparse4.xml
search form search path:C:\abc\.\
Search File: rawprogram5.xml
search form search path:C:\abc\.\
Search File: patch0.xml
search form search path:C:\abc\.\
Search File: patch1.xml
search form search path:C:\abc\.\
Search File: patch2.xml
search form search path:C:\abc\.\
Search File: patch3.xml
search form search path:C:\abc\.\
Search File: patch4.xml
search form search path:C:\abc\.\
Search File: patch5.xml
search form search path:C:\abc\.\
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse0.xml
RAWPROGRAM file path: C:\abc\.\rawprogram1.xml
RAWPROGRAM file path: C:\abc\.\rawprogram2.xml
RAWPROGRAM file path: C:\abc\.\rawprogram3.xml
RAWPROGRAM file path: C:\abc\.\rawprogram_unsparse4.xml
RAWPROGRAM file path: C:\abc\.\rawprogram5.xml
PATCH file path:C:\abc\.\patch0.xml
PATCH file path:C:\abc\.\patch1.xml
PATCH file path:C:\abc\.\patch2.xml
PATCH file path:C:\abc\.\patch3.xml
PATCH file path:C:\abc\.\patch4.xml
PATCH file path:C:\abc\.\patch5.xml
Start Download
Program Path:C:\abc\prog_ufs_firehose_8996_ddr.elf
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:C:\abc\prog_ufs_firehose_8996_ddr.elf 'Current working dir: C:\Users\Jean-François\AppData\Roaming\Qualcomm\QFIL
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:\abc\prog_ufs_firehose_8996_ddr.elf
20:42:54: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:42:54: ERROR: function: sahara_main:854 Sahara protocol error
20:42:54: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Update of 18/98 => everything is now solved.
I changed from my laptop to my HTPC and everything went fine... My Zuk Z2 pro works again!!!! I am so happy.
Click to expand...
Click to collapse
I'm running into the exact same issue. Did you do anything different on the new machine? Unfortunately I do not have another machine to try.. Any helps would be great
EDIT: I was able to get this work. The trick is to click "Download Content" as sooooooon as you hit enter on "adb reboot edl"
And once I did that, I did not get the Sahara error but another random error. Tried a different port on my laptop and it worked perfectly

My Gapps sync are not working!
When i put my login information the google account isn´t syncing!

question
Sorry I am new to this. I purchased a yuk z2 pro 6gb ram 128gb storage and it comes with the international custom ROM put on by the reseller. I would like to change it back to the original oem rom. Is this the directions to follow? If this is the wrong directions can you please show me the correct directions.
Thanks

Zuk Z2 pro bricked
Hello,
thank you for this very detailed description of the process!
I did try it and something went wrong, I do not know where I went off protocol, yet now my phone is unresponsive.
It is fully loaded.
LED is blue, screen black.
Long pressing Vol up plus power -> short vibration and green LED, ZUK logo appears shortly, then screen is black and LED blue again.
When USB is conneted, QFIL 2.0.0.4 does recognize a phone. Chirp on the PC. QUALCOMM HS-USB Diagnostics 900E (COM5) in top line of QFIL
When I try to flash, however, it shows:
"Switch to EDL
Download fail: switch to EDL FailFailed to switch to Emergency Download mode
Finish download."
To me, this seems as a complete brick event.
Could someone of the experts please help me to revive the phone?
Thanks!

Google Tap & Go
Hi,
I would like to get all my apps, and settings back from my One Plus on cm13 to My brand new Zuk Z2 Pro.
How do i make it ?
Must i flash it ?
Thanks

What I understand, you can use miFlash to Flash the qfil according to htt p://www.androidbrick.com/zuk-z2-z2-pro-qpst-qfil-miflash-rom-flashing-guide/

I become always this failer when I will flash my Bricked Z2 Pro
PATCH file path:\zuk\Z2121_CN_OPEN_USER_Q01017.1_M_ZUI_2.3.044_ST_161013_qpst\.\patch5.xml
Process Index:0
Start Download
COM Port number:10
Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download

Qfil won't recognize zuk z2 pro. Do you have any idea why ?

How do I install these qualcomm drivers ? They aren't executable

I successfully flashed the device according to the logs, but I'm still stuck with a test mode boot loop. I guess my phone is good for the garbage?

Bricked my Cool 1

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?

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 )

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?
Click to expand...
Click to collapse
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

How do I do that?

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?
Click to expand...
Click to collapse
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...

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
Click to expand...
Click to collapse
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

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 )
Click to expand...
Click to collapse
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.

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
Click to expand...
Click to collapse
need help

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?

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

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 )
Click to expand...
Click to collapse
my phone is not identified by COOL ASSISTANT but QFIL identifies it, how do I give DOWNGRADE using QFIL? : eek:

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?
Click to expand...
Click to collapse
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:

Unbrick you're phone using this detailed guide on pantomath site
IMEI restore. Coolpad phones are unbrickable. Follow this guide

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 )
Click to expand...
Click to collapse
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.

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

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.
Click to expand...
Click to collapse
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.

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
Click to expand...
Click to collapse
keep pressing power+vol up+vol down until it got detected. Install all the drivers first.

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.
Click to expand...
Click to collapse
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.

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

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
Click to expand...
Click to collapse
Which qcn file you restored??