Develop Bugs

Lenovo Vibe P1 Hard Brick

Well, I managed to hard brick my Vibe P1.
The phone doesnt turn on, it doesnt charge, pretty much nothing is working.
I did manage to get into download mode once by holding volume up and inserting the USB into the PC, but I cant get into the download mode anymore.

NeptunePH said:
Well, I managed to hard brick my Vibe P1.
The phone doesnt turn on, it doesnt charge, pretty much nothing is working.
I did manage to get into download mode once by holding volume up and inserting the USB into the PC, but I cant get into the download mode anymore.
Click to expand...
Click to collapse
Update: I can now get into download mode but I still cant unbrick the device.
Any help is appreciated.

NeptunePH said:
Update: I can now get into download mode but I still cant unbrick the device.
Any help is appreciated.
Click to expand...
Click to collapse
Reflashed with qfil?

Starchm said:
Reflashed with qfil?
Click to expand...
Click to collapse
I tried QFIL yet no matter how many times I try, which USB cable I use, which PC Port I use, or no matter what ROM I try I always get the same error:
Download Fail:System.Exception: "Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail"
I found a "fix" which says to disable driver validation mode, but it doesnt work. Nothing I try works. Not even the Lenovo Moto Assistant flash thing.

NeptunePH said:
I tried QFIL yet no matter how many times I try, which USB cable I use, which PC Port I use, or no matter what ROM I try I always get the same error:
Download Fail:System.Exception: "Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail"
I found a "fix" which says to disable driver validation mode, but it doesnt work. Nothing I try works. Not even the Lenovo Moto Assistant flash thing.
Click to expand...
Click to collapse
Flash an really old lollipop rom with qfil, disable driver validation, use windows 7 32 bit official cable + usb2.0

Starchm said:
Flash an really old lollipop rom with qfil, disable driver validation, use windows 7 32 bit official cable + usb2.0
Click to expand...
Click to collapse
Could you please link me to a ROM to make sure im flashing the right one?

NeptunePH said:
Could you please link me to a ROM to make sure im flashing the right one?
Click to expand...
Click to collapse
https://forum.xda-developers.com/vibe-p1/development/lenovo-vibe-p1-stock-rom-custom-rom-t3306484 #4

Starchm said:
https://forum.xda-developers.com/vibe-p1/development/lenovo-vibe-p1-stock-rom-custom-rom-t3306484 #4
Click to expand...
Click to collapse
Nope, I still get the Sahara error thing.

NeptunePH said:
Nope, I still get the Sahara error thing.
Click to expand...
Click to collapse
disable driver validation, use windows 7 32 bit official cable + usb2.0

Starchm said:
disable driver validation, use windows 7 32 bit official cable + usb2.0
Click to expand...
Click to collapse
I did disable driver validation, I am using the usb2.0 cable+port, Im using win10 64 bit since I dont have a win7 32 bit key lying around.

Try to enter fastboot mode.Once you entered delete whole system partitions except efs1 and efs2 partitions.After this qfil will work just fine. I'm bricking my p1 everytime and fixing it like this.

HELP!!! Hard Brick Hydrogen

My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys

seti007 said:
My phone is hard bricked. No LCD, no charging LEDs. Only showing up in EDL mode as Qualcomm Hs-USB QDLoader 9008 in the device manager. It happened when I tried to install the latest MIUI 9 weekly rom 7.9.15 from xiaomi.eu. I've spent the last few hours trying everything I could find. I can get MiFlash to see the device but I get different errors depending on the version of Mi Flash. Ive opened the phon eup, tried with/without the battery, tried shorting the two pins on the mobo mentioned in this thread
https://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
I've tried three different computers, windows 10, windows 7 both 64 bit. Disabled driver verification. Tried many different global ROMs but still get the following errors depending on the version of miflash:\
-cannot read from COM port
-Reached the end of the file. (0x80070026: ReadRobust failed)
-cannot receive hello packet
Bottom line is that the phone is in a weird state and doesn't seem to communicate properly with the miflash tool.
Anyone have any clue what else i can try? I hate to lose my beloved mimax!
Thanks guys
Click to expand...
Click to collapse
What happens by trying to go into TWRP?
Enviado desde mi MI MAX mediante Tapatalk

I flashed eu rom yesterday?
What exactly happened??

Thanks for the answer guys following are my responses.
Albertkuba said:
What happens by trying to go into TWRP?
Absolutely nothing happens with any button combination. The screen remains dark. When I unplug the battery and plug it back in ic the computer recognizing it as an edl device 9008
Enviado desde mi MI MAX mediante Tapatalk
Click to expand...
Click to collapse
hassan_eldhraawy said:
I flashed eu rom yesterday?
What exactly happened??
Click to expand...
Click to collapse
I had Nigel's lineage ROM running perfectly on my phone. I got an itch to Try out the new MIUI 9. Downloaded the latest ROM and then the latest Superuser. Installed both of them and tore up. The ROM installed fine without any error messages. While installing SuperSU the phone just died. it was plugged into power so not sure why the screen just went dark.

Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...

nijel8 said:
Chek http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Do "Guide on how to recover “Qualcomm HS-USB QDLoader 9008” MODE", Fastboot MIUI rom has all files needed for QFill:
MIUI 9 Global Beta ROM(fastboot) 7.9.15
1 - images/prog_emmc_firehose_8976_ddr.mbn
2 - images/rawprogram0.xml
3 - images/patch0.xml
in fastboot mode run flash_all.bat
Let us know how it went...
Click to expand...
Click to collapse
Thank you Nigel for your input. I will give this a try and get back with you.

Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(

seti007 said:
Hi Nigel, I followed the guide exactly as indicated using windows 10. I get an error at the end when I hit download in Qfil. My phone is in the OLD “Qualcomm HS-USB QDLoader 9008” mode.
QFIL LOG:
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
EDIT: I would like to add that I have driver signing off and tried a win 10 and 7 computer with the exact same results. I'm beginning to think that my phone is pretty much a lost casue :,(
Click to expand...
Click to collapse
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...

nijel8 said:
Is this screenshot real? Why are you using 8675_W00 device firmware files from the guide literally!? Use miui rom link I gave you for hydrogen...
Click to expand...
Click to collapse
You have a keen eye Nigel. Yes I messed up the first time and used the wrong folder. Afterwards, I tried this with the proper folder with the correct firmware from the link you provided. Tried putting it in root drive and renamed the folders so there were no spaces. Even tried a newer fastboot firmware but still the same result. Looking around on google, apparently the Sahara error is very common and no real solution.
Thanks again for your help Nigel.

Hi Nigel, I'm wondering if you or anyone else who feels up to the challenge would be willing to work on this phone? I can send it to you with a self addressed envelope. I'm willing to pay for your time. I have exhausted all options but nothing has helped. would be great to have my phone back . If anyone is willing to take me up on this, please pm me. Thanks

PLEASE HELP H815 HARD BRICK no fastboot, no 9008 and no recovery USU

Hi People,
I manage to brick my LG G4 H815.
The phone was fine and I flashed this https://forum.xda-developers.com/g4/development/rom-h-rom-g6-port-t3660459 after that my phone simply didn't turn on not even an LG logo only black screen but it does vibrate when I try to power it up. When I plugged it into the PC I get nothing t doesn't detect the device at all.
I tried the 9008 drivers and still nothing.
PLEASE HELP!
*edit: also forgot to mention also download mode doesn't work*

if it's bricked you can force it to qualcomm 9008 mode by shorting the test point pins then use qfil

nardndoka said:
Hi People,
I manage to brick my LG G4 H815.
The phone was fine and I flashed this https://forum.xda-developers.com/g4/development/rom-h-rom-g6-port-t3660459 after that my phone simply didn't turn on not even an LG logo only black screen but it does vibrate when I try to power it up. When I plugged it into the PC I get nothing t doesn't detect the device at all.
I tried the 9008 drivers and still nothing.
PLEASE HELP!
*edit: also forgot to mention also download mode doesn't work*
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212
When your device is UsU'd as your title suggests ensure you follow post 2 there as well
Sent from my OnePlus 6T using XDA Labs

qfil problem
steadfasterX said:
https://forum.xda-developers.com/g4/general/guide-proper-h815-unbrick-qfil-files-t3709212
When your device is UsU'd as your title suggests ensure you follow post 2 there as well
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
I got my phone to a 9008 state, installed the drivers QPST with vcredist and NET Framework I replaced the files like you mentioned the USU files and I get this weird error in the log file
-
Start Download
Program Path:C:\Users\Jon\Desktop\h815_full_working_7a3ae5809224d\flashing\prog_emmc_firehose_8992_lite.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
-

Ok. I fixed it now thanks

nardndoka said:
Ok. I fixed it now thanks
Click to expand...
Click to collapse
what did you do ?

Question oneplus 9 pro msm tool error

hi there i have a oneplus 9 pro that is bricked i onlu can see it connected to the pc and nothing else no screen no nothing and when i connect it to the pc it shows the qualcom driver now i did used the msm ubrick tools all variants and i get all the time after 10 seconds the error of firehose getufsinfo failed i tried evrything to get past that error and theree is no any luck at all any help please or any suggestions so i can unbrick my device and also i tried the india msm and the eurobe msm and th global and there is no any result passing this error

edl Qualcomm 9008

Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help

Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.

Strephon Alkhalikoi said:
Can't help you with the pins. I can however tell you that based upon my experiences with my Lenovo tablet, using Xiaomi's MiFlash software proved a lot more reliable than Qualcomm's tools when trying to restore the firmware through the low level interface.
Click to expand...
Click to collapse
i will give it a try thank you, is it the same way for xiaomi to short pins in order to get to edl test mode ?

I don't know.

Well, there has to be a reason that the phone ended up in this state.
My guess is a hardware fault, and if that's the case, you'll need to replace the motherboard.
Some phones can end up this way if you do something stupid while flashing a rom, but I've never heard about that on a Pixel.

code777 said:
Hi all
well in a nutshell a friend's good old pixel 2 xl finally had the issue of black screen and only qbulk being detected by the PC.
After a bit of googling i found a Qualcomm loader and some firehose files from github.
However it fails on with error sahara protocol cannot establish connection.
I read that maybe i needed to short pins on the board to go into edl test mode, but dont know which ones i have attached a picture
Any suggestions would help
Click to expand...
Click to collapse
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.

SubwayChamp said:
If your device is not properly detected, because it is not properly in EDL mode, then, there's not a tool that can detect it or work with.
When the kernel refuses to start because of a failed upgrade or something, then the device enters automatically to Qualcomm/EDL mode, but the first you'll see, it is detected in device manager as QBulk or Qualcomm HS-UB-Diagnostics 900E, then you have to update the drivers to Qualcomm HS-USB QDloader 9008 to get it.
This is an example of my other device, by fortune my P2XL is working fine besides the bootloader can't be unlocked.
Click to expand...
Click to collapse
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated

code777 said:
Hello, i think i installed it correctly tried on two different computers with one "unsigned" driver with the windows drive signature turned off and then with a driver from Microsoft's own website which is signed i still gate the same issue.
Tired with couple of version of QPST with the latest i found being QPST_2.7.496, tried with a couple of firehose files there is a github repo with most of them 8916 often pops up in google 2xl topics and one zip which was named 2XL had in it prog_ufs_firehose_8998_ddr.elf not sure if its the correct one :
ERROR: function: rx_data:246 Error occurred while reading from COM port
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
So i am stuck to this point now , ANY suggestions will be appreciated
Click to expand...
Click to collapse
To start with, the correct installation of these drivers is mandatory, otherwise, you can't advance further, if you have a message of success, then it's done, if not, you may redo the steps.
Microsoft doesn't own any of the needed drivers here. All relies on Qualcomm, it contains the lot of variants, from all of them, one is all you need.
If the issue is with QPST, I saw a QPST thread in XDA, just search for it.