I'm from Brazil, I came to ask for help, I'm going to use google translator. My phone was in infinite boot, it only starts in fast boot mode, I unintentionally formatted and deleted the system folder. I tried to pass the rom through qfil, it identifies the device but the error appears: sahara protocol failed, at the time of the download. I've tried all possible ways and all the tutorials on the internet but I can't solve the problem. My phone died without a system and I don't know how to solve it, is there another method to flash the rom? could you help me, a light, please!
From 4PDA and using Google Translate:
Faced the problem "download fail sahara fail qsaharaserver fail process fail"
All standard solution methods:
0) Check if the firewood is installed
1) QFIL must be run on behalf of the Administrator.
2) The path to the folder with the firmware is too long and / or contains the Cyrillic alphabet - unzip the firmware along the path C: / firmware and sew again.
3) Use the original cable for firmware;
4) Change the computer or USB port and sew again;
5) Download QFIL from the header, remove the QFIL that is installed now, clean the Program Files (x86) \ Qualcomm, ProgramData \ Qualcomm, AppData \ Roaming \ Qualcomm folders, install QFIL version 2.7.453 and sew again.
6) In Qualcomm’s device manager, the driver may have a triangle with an exclamation mark, reinstall it in the "without certificate authentication" mode and without rebooting, sew the firmware.
7) The file system type is emmc a not ufs, change to ufs, restart QFIL and try to flash the firmware again.
8) Turn on flight mode on the computer
9) Turn off antiviruses
10) After all the described reboot, if it didn’t help
, then didn’t help and in one video from YouTube I saw a way 11) In the Configuration check “Use verbose”
and it worked, I hope it helps
Click to expand...
Click to collapse
Thank you so much for your answer. After two insistent days looking for the solution in various videos, tutorials and everywhere, I finally got it, by sheer luck. I uninstalled the 64-bit qualcomm usb and installed the 32-bit one. I checked these options in the settings: Reset state machine, use verbose and auto preserve partitions. In preserve mode I selected: option 1 and preserved list: option 2. And to my surprise when I clicked on download, everything went well.
Related
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Axis76 said:
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Click to expand...
Click to collapse
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
droidinterest said:
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
Click to expand...
Click to collapse
Yep. Tried using several versions of the drivers downloaded from different places and used USBDeview to remove/reinstall them. The error still comes back and haunt me.
maybe this can help you
No luck.... formatting is not working in sp flash tool (4010 error) and the preloader in the thread is not for my phone.....
Anyone able to help pls....?
Axis76 said:
Anyone able to help pls....?
Click to expand...
Click to collapse
have you use google my brother ? google is our true friend.
but i glad if i can help you:angel:
you can visit this for factory rom
or you can visit lenovo forum
or you can go to needrom
Yeah. Google had been my fren, but no more after googling for 2 weeks without a solution. Trust me. I had looked thru most solutions found in google and had tried without any success before I post here.
All those stock roms of all release numbers I had already tried as mentioned above, with sp flash tools (tried many versions of that also.) ALL attempts are stucked with the errors mentioned above. The sp flashtool simply just fills the red status bar, and stopped with one of the errors in my 1st post.
I've even checked the chinese forums. My situation seems to be this:
The partition table of the flash memory had been reformatted thanks to the custom rom flashed via sd card. That's why it always returns a format flash error when I attempt to flash back to the stock rom which uses a different format range using sp flash tools. The only way out is to do a clean format of the flash memory. But I haven't find a way to do that via sp flash tool or mtk droid tool.
My only recourse is on of the following:
1. If I can restore the custom recovery (via adb in recovery mode(no fastboot) or meta mode) and make it workable to do another sd card flash with a custom rom. I have no idea why the options in my custom recovery went missing. It was working before I flashed the custom rom. I guess that accursed rom somehow erased my custom recovery during boot.
2. If I can somehow be able to do a complete flash format with the correct format parameters using some tools. Sp flash tools had failed me so far.
Anyone is able to help in these directions? Many thanks....
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
anyone can help......?
Axis76 said:
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
Click to expand...
Click to collapse
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
droidinterest said:
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
Click to expand...
Click to collapse
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Axis76 said:
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Click to expand...
Click to collapse
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
droidinterest said:
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
Click to expand...
Click to collapse
Already tried this. I had tried on 2 pcs. Windows 7 and windows xp (no digital signature). Same errors occur in both pcs. I really don't know what is going on with this phone. Nothing seems to work.
PS: Have been running the program as administrator all along also.
Sent to a phone repair shop and its at worst state than before now. Unable to power on. Connecting phone to computer and tried using sp flashtool now gives 4032 error (Enable Dram failed).
Any hope with reviving this phone now?
leno p780 in bootloop
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
AshishKhalkho2013 said:
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
Click to expand...
Click to collapse
Hi, first, do you have SP Flash Tool installed on your PC and have the drivers installed? If yes, download the stock ROM of your choice from here and flash it with via SP Flash Tool, and your phone should be revived.
Flashing methods are clearly stated in case if you don't know how to do it.
lenovo p780 not booting
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
somu12345 said:
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-brick-t2782696/post53395430
WHAT CAN I DO___???
hardware
Axis76 said:
anyone can help......?
Click to expand...
Click to collapse
check on hardware, there must be trouble with your flash chip ic, try to rehot it first.
if doesn't work that mean your flash chip ic completely dead
Seems this device has no support anywhere. I spent the last 28 hours trying to fix my problem with no luck it went as follows:
-The device rom had a lot of adware related to something called: com.android.ser
-To get rid of it I rooted it successfully using FrameRoot
-I used some malware cleaners and deleted some sytem apps reported by them including com.android.ser
-My big mistake: I felt I need to clean more, and thought Mediatek apps are another source of adwares and deleted them, the device crashed and when rebooted stuck in bootloop.
-I went into recovery and deleted cache + data , didn't work
-installed ADB and tried sideload (which is an available option in the stock recovery) a ROM which I found here. It pushed the rom up to 100% but immediately failed after that.
-used fastboot app. It connected successfully, could restart the device from there but when I try to flash system.img it fails.
-USB debugging in developer options were most probably not enabled as I remember. Unknown sources was enabled.
Help is appreciated.
Update: Resolved. I'm posting the solution below, which is generic for Mediatek Devices, just ensure you use your own device's ROM, recovery,boot,...etc
(please note we are working on Windows)
(This Video has most of the below notes)
1- From device manager manually install Mediatek USB VCOM drivers and ADB, , installing PDANet (free PC application)helps a lot for some of driver installation, which was true in my case. Installation of PDA Net should be while device is connected and in normal mode (The boot loop in my case).
2-Download Smart Phone Flash Tool
3- You need what is called the "scatter file" for your device. In my case it was included in the ROM zip. There is also a tool to create one called "MTK Droid Tools".
4- open the scatter file, and make sure each image type is assigned to the corresponding image file. In my case the assignment was done automatically as the scatter was included with the ROM zip.
5- Shut down the device (use a needle or pin to reset in case of Ainol Numy 3G AX10)
6-Keep the device disconnected
7-click download on SP Flash tool
8- connect the device. The counters of download start counting and when done (about 5min), a small window with green sign pops up.
9- if download does not start try to fix your drivers. Sometimes you need to uninstall-reinstall drivers. Sometime you need to try from different sources.
10- tell me if this post was helpful
So i installed TWRP and flashed a xiaomi android one
It worked ok, some apps were weird
Tried to do the latest update for flyme with TWRP
It installed ok, but after restart it would boot to logo screen and turn off
Fastboot or recovery do not work
All phone does is turn on on 10 sec pwr button press and nothing else
Meizu M6 Note M721H is the version, tried qualcom but gives all bunch of errors and i cannot seem to find a way out
Requesting assistance please
Thankyou in advance
+1
Same problem here.
Folks, "a bunch of errors" is not exactly an accurate description that allows anyone to help you out.
However. Today, after I've tried to restore the TWRP backup of my "devinfo" partition with the intention of relocking my bootloader, I've bricked my Meizu M6 Note (unable to boot OS or the recovery) and subsequently spent about 3 hours googling for a working solution, I've tried reflashing the stock firmware using QFIL (also QPST and a few other tools), but I either got the infamous "Switch to EDL" errors:
Switch To EDL
Code:
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
This was due to the fact that my device was recognized as the Qualcomm (...) 900E device, so I had to go to Device Manager and "Update driver", then manually select the correct one from the list, which was "Qualcomm HS-USB QDLoader 9008" (version 2.1.2.2, but older ones might work as well). After that, QFIL gave me the also infamous "Sahara protocol" errors:
Code:
ERROR: function: is_ack_successful:1121 SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED
ERROR: function: sahara_start:895 Exiting abruptly
ERROR: function: sahara_main:924 Sahara protocol error
ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
However when this error occured, I was able to go to fastboot mode, by pressing the Volume down (-) key and trying to flash the stock firmware again. After this, my phone displayed "fastboot mode" at the bottom of the screen in green. However because bootloader was locked again, I wasn't able to run or flash a TWRP recovery. At this point I was out of ideas.
Thankfully, I've ended up finding an excellent Russian guide by VladimirVVK of 4PDA fame (thanks Vladimir!):
Code:
hxxps://4pda.ru/forum/index.php?showtopic=843179&st=5620#entry69341915
...where a certain UnbreakM6NoteMinimum.rar was uploaded, that included everything I needed to get out of the boot loop. I've reuploaded the file, so hopefully you'll be able to download it, and follow the instructions inside INSTRUCTIONS.TXT (there's a Russian and English version as well):
Code:
hxxps://mega.nz/#!N5ZEFaAb!ez3F4pCJPPs9jFODI2a9_QH8tiGD3GQfDtOP4xkEuDo
My only tip is, that if you find it difficult to put your device into "download mode" (which is NOT fastboot mode) because you're not able to turn it off properly and you can't get into the "Partition manager", do this:
1. Start QFIL
2. Choose Flat Build under "Select build type"
3. Click browse under "Select programmer", select prog_emmc_firehose_8953_ddr.mbn (you can use the file from UnbreakM6NoteMinimum.rar)
4. Connect your device, wait until it shows up as "9008"
5. Start pressing Volume up (+) and Volume down (-) at the same time
6. In upper menu go to "Tools" - "Partition manager", confirm the dialog.
7. Repeat process 5 and 6 until you see the partition manager.
8. Continue the guide in INSTRUCTIONS.TXT (steps 5 and 6 there).
After that, my device was out of the bootloop, however the OS still didn't boot completely (I was running crDroid before the whole kerfuffle), the boot animation started and continued for a couple of minutes then I saw a blank screen. However, now that the original Meizu recovery was restored and I was able to boot into it by holding down Volume up and the Power button. The Meizu recovery mounted an empty 2GB partition on my PC, I was able to copy the stock Flyme 7.0.1.0G stock ROM update.zip on it and flash it after that. My phone is now working again.
Good luck everyone!
Sorry about the "hxxp" links, but I'm not (yet) allowed to link external URLs per xda-developers policy.
meizu m6 note stuck on fast boot
plz help me
I fouund the solution
The 8953ddrmbn file not worked for me so i tried another mbn file from this pack and it worked fine :
mega.nz/#!5cwEWbTa!JQtI1mQslzUMNOgJd13DpxpmLjXTdA6V6tWWp5I0kng
My phone Not Showing 9008 in QFIL
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Tinyhafij001 said:
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Click to expand...
Click to collapse
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
geekborg said:
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
Click to expand...
Click to collapse
Unfortunately I replaced devcfg with devinfo and after that i cant start my device again or switch it to edl 9008
any help ????plz
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?
A hard brick is where your phone starts to bootloop but you cannot enter recovery nor fastboot. A hard brick is caused where you flashed a incompatible ROM/Recovery/Firmware,etc. If you ever hard bricked your phone then this thread can unbrick your phone. Any OS is supported. Linux, Mac and Windows. Now to get started, install this softwares:
SP Flash Tool
Python 3
Virtual Box (MacOS)
You also need knowledge in bash, python (I am not responsible if the steps did more damage than you hard bricking your device)
For users who's doing this guide in MacOS. Make a Windows 10 Virtual machine then download SP Flash tool in it. Download MTK Driver here in the Virtual Machine then run it.
And maybe sure to drain your phone's battery first before doing something.
After installing, download this link below (Code > Download ZIP):
Bypass (Bypasses MediaTek's Security inorder to flash)
Payloads (So that the bypass can work)
Download Stock ROM here then extract it. (For MacOS users, download it in the Virtual Machine.)
(Credits to the owners who made this scripts)
After downloading, unzip the 2 files and in the exploits_collection folder (Payloads), copy the two files and folder named "default_config.json5" and "payloads" then put it to the bypass_utility folder (Bypass). Once done, open terminal and type following:
pip install pyusb json5
Also for MacOS users, dont run it in the Virtual Machine you made or else it wont be recognized.
Run the script and just like i said you must drain the battery first or else it will error in SP Flash Tool. After running you will see a message that says "Waiting for device". Hold Volume Down then plug your phone (Volume Up or Volume Down+Up if not recognized) then you should see a message that says "Protection Disabled". DO NOT UNPLUG IT OR TOUCH IT
python main.py
If ur running in MacOS > Launch the Windows 10 Virtual Machine, open SP Flash Tool.
If ur running in Linux, Windows > Open SP Flash Tool
Open SP Flash Tool then go to Options in top left, go to Connection, press UART. If your phone is connected and bypassed, you should see a option in the selection COM. Then go back. Press Select in "Scatter Loading File", locate to the Stock ROM you downloaded then go to images. You should see a file named "Scatter" in the end of it then select it. The Flash Tool will read it then you can press download. It if succeed, you will see a checkmark window popped. Then reboot the phone. If you dont like the Stock ROM, fastboot is back again and you can flash anything you'd like. Any problem? Check out FAQ below
FAQ
1. When flashing, an error popped up saying STATUS_RAM_EXEPTION
You din't drained the phone's battery. If you did not, you have to wait a couple days. You can check if its drained by holding the power button.
2.I cannot detect my phone while bypassing.
Close VirtualBox or any softwares that is catching any USB devices.
3.Cannot find device in VirtualBox
Download the extension pack after downloading then go to VirtualBox, press ur Windows 10 Virtual Machine, press Settings in the top, go to Ports then USB then choose "USB 3.0". Press OK
4.I cannot find my question here
Comment down below.
Sorry for the wrong grammar i placed in this thread.