so i was installing magisk and after the patch the devices rebooted and got stuck at the logo and when i tried to flash the phone it got hard bricked now it does't even shows the logo neither i can get into the recovery or download mode.
tried everything but every time i'm getting the sahara error or the firehose fail error in some versions of qpst, tried various versions of qpst
tried moving the firmware folder to bin folder
tried disabling driver signature enforcement, and booting windows in test mode
i can't boot the phone no nothing at all, the only hope is that the device is shown as 'qualcomm hs-usb qdloader 9008' in the device manager and the charging led lights up
device is also not detected in 'adb devices' or 'fastboot devices'
01:47:56: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:924 Sahara protocol error
01:47:56: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
you need more exclamation marks
Pl
harshk5611 said:
so i was installing magisk and after the patch the devices rebooted and got stuck at the logo and when i tried to flash the phone it got hard bricked now it does't even shows the logo neither i can get into the recovery or download mode.
tried everything but every time i'm getting the sahara error or the firehose fail error in some versions of qpst, tried various versions of qpst
tried moving the firmware folder to bin folder
tried disabling driver signature enforcement, and booting windows in test mode
i can't boot the phone no nothing at all, the only hope is that the device is shown as 'qualcomm hs-usb qdloader 9008' in the device manager and the charging led lights up
device is also not detected in 'adb devices' or 'fastboot devices'
01:47:56: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
01:47:56: ERROR: function: sahara_main:924 Sahara protocol error
01:47:56: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Please use Google "name of phone and hs -usb qdloader" like lenovo a6020a40 not recognized dead hsusb qdloader. There are many old threads and with short search a YouTube. Like this https://forum.xda-developers.com/t/how-to-recover-a-bricked-lenovo-vibe-k5-plus-a6020a46.3420057/
joke19 said:
Pl
Please use Google "name of phone and hs -usb qdloader" like lenovo a6020a40 not recognized dead hsusb qdloader. There are many old threads and with short search a YouTube. Like this https://forum.xda-developers.com/t/how-to-recover-a-bricked-lenovo-vibe-k5-plus-a6020a46.3420057/
Click to expand...
Click to collapse
tried all of them, the qualcomm premium tool shows opening port fail, and the mi flash tool also doesn't worked for me
joke19 said:
Pl
Please use Google "name of phone and hs -usb qdloader" like lenovo a6020a40 not recognized dead hsusb qdloader. There are many old threads and with short search a YouTube. Like this https://forum.xda-developers.com/t/how-to-recover-a-bricked-lenovo-vibe-k5-plus-a6020a46.3420057/
Click to expand...
Click to collapse
so i at least solved the sahara error by replacing the prog_emmc... file with another one which matches my phones chip type which is msm8929, and the firmware was flashed succesfully without any error but still my phone does't boots up.
so finally my phone booted and working perfectly and if anyone else is facing this problem then just replace the Stock rom, download the one according to you msm version like mine was snapdragon msm8929 so at the end of the prog_emmc file there should be your msm version, only that firmware will work for you, the mistake i was doing before was that i was trying to flash firmware which had programmer file as prog_emmc_firehose_8916.mbn but the one that worked for me was the firmware with programmer file as prog_emmc_firehose_8929.mbn because 8929 is my device's msm version. Good luck!
Related
Hi All,
My auxus nuclea N1 got hung while browsing and it shutdown and now it is DEAD and not powering up. I tried to boot it up to recovery mode which did not work, My device does not even show the charging icon when i plug it to the charger.
I tried to flash different kinds of firmwares using SP Flash Tool, But i keep getting the error "4032" with or without the battery.
I have tried the various combinations such as pressing power only; volume up only, volume down, power+volume up , power+volume down. but still the same error; when I click download / firware upgrade, it shows the 100% in red line and after 35-42 secs gives the error.
I am currently using Win-7, but I have also tried with Win-Xp machine and also a different laptop and different cable with the same result.
I have also tried different version of the sp flash tool.
I have tried the 3 different versions of firmware that the company has provided till date but keep getting the same error.
AuxusNucleaN1_20130703
Auxus_Nuclea_N1_20130824
NucleaN1_20131211
I have attached the screenshots of the sp flash tool process I have followed and also the SP flash log files across multiple runs. Plz let me know how to fix this.
SpFlashTool_Screenshots.docx -- contains the screenshots
SP_FT_Logs.zip -- contains the logs of sp flash tool
The complete error is given below:
---------------------------
Smart Phone Flash Tool
---------------------------
Common Hint: For SP Flash Tool issues:
Please supply your tool version, GUI screen shot, and tool logs when you encounter trouble with the latest tool.
How to obtain the tool logs?
1. Run the tool;
2. Press Ctrl+Alt+t(Tool Title Hint: Runtime Trace Mode);
3. [Menu]Help-[SubMenu]Open logs folder.
BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.
---------------------------
OK
I got the same problem to my phone also. What need to do?
we got same problem but im still fixing mine right now
based on my research here is someways to fix it
-Unbrick
https://www.youtube.com/watch?v=0J7gjY3nEuU
-Enable DRAM FAILED
http://forum.xda-developers.com/showthread.php?t=2663680
-unbrick
http://forum.xda-developers.com/showthread.php?t=1943442
-MTK Droid Root & Tools
http://forum.xda-developers.com/showthread.php?t=2160490
-enable_dram_fail
http://forum.xda-developers.com/showpost.php?p=47161578&nocache=1&z=6513086356953772
-LCOLO to GRND
http://forum.xda-developers.com/showthread.php?p=44208574#post44208574
Hi all,
I found VIVO Y51 testpoint and successfully revive my friend's dead phone due to corrupted bootloader (in pursuit of trying to unlock it .. lesson learned *sigh*). So, I would like to share my findings so that it would help others reviving their phone.
You need:
- QPST firmware for your Y51 eg: Y51_PD1510F_EX_A (google it pls)
- open your phone and disconnect battery
- open QPST (make sure you already install the 9008 driver)
- IMPORTANT! make sure you select the file with no_qcn so that it won't erase your imei for download eg: rawprogram_unsparse_no_qcn_PD1510F_EX.xml (I tried other xml and it erased the imei, luckily I have backup the qcn before the bootloader went corrupted)
- connect usb and short the testpoint (refer to attachment)
- when QPST detected port 9008, connect the battery, press download and wait till finish.
- after flashing is complete, disconnect and reconnect the battery. Assemble the phone and boot it normally.
Sorry for unable to write a full step-by-step right now because it is already late at my place (4am).
Thank you
Thank you
I also bricked my y51 and got it replaced it at service center,
But i've figured out how to unlock its bootloader
First we have to upgrade to PDF1510 2.6.7 lollipop 5.1.1 version
then follow the steps in this thread
need help
Hello SIr,
Tried it with my hard bricked vivo y51l. but got the below error. pl help.
Start Download
Program Path:\android\Vivo_Y51_PD1510F_EX_A_1.16.2_LA.BR.1.2.1-01210-8x16.0_msm8939\Firmware\prog_emmc_firehose_8916.mbn
COM Port number:20
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:20
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
It's a common port error
SIDD2506 said:
Hello SIr,
Tried it with my hard bricked vivo y51l. but got the below error. pl help.
Start Download
Program Path:\android\Vivo_Y51_PD1510F_EX_A_1.16.2_LA.BR.1.2.1-01210-8x16.0_msm8939\Firmware\prog_emmc_firehose_8916.mbn
COM Port number:20
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:20
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
Click to expand...
Click to collapse
This happened to me, it's just a port problem.
chamge port it will work.
Will this work on hard bricked vivo y55l? Plss I need help, I tried to flash it but i got errors too. It wont start again after I unplugged it, its dead... I broked it, its my cousin phone... Plss help
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?
Hello,
In last week i got RMX2202 which is after update of DSU.
Phone wasn't rooted so now it's totally brick - Volume Up, Down, Power combination working normally i can put phone into the EDL mode.
I found some stuff like: Qfile, QPST, Qualcom Drivers.
By this software which I found i tried to reflash the phone but still getting error for example:
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
16:01:00: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
16:01:00: ERROR: function: sahara_main:982 Sahara protocol error
16:01:00: ERROR: function: main:320 Uploading Image using Sahara protocol failed
I have stock firmware for this phone: RMX2202GDPR_11_C.17, extracted ofp file via ofp extractor and there is 5 files with rawprogram.xml and 5 files for patch - I should put all of them in Qfil?
I can't put phone into the fastboot mode or recovery because of boot loop.
It's any possibilities to bring phone back via Qfil or i need to find someone with access to MSM Download Tool?
any updates ? cuz i have the same problem too
Hi, problem resolved by MSM Download tool but I had to pay someone to do it. Software needs account where you can't get.