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.
Related
I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]
yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
I don't think ur swift is bricked
when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.
I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....
void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot
yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?
See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.
Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly
cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks
xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week
Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response
Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew
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
Hi all,
After installing Masik 3.6 my device has ended up as a dead brick. The screen is blank and i'm unable to boot to twrp or fastboot.
The only sign of life is when i plug into a PC its listed as Qualcomm HS-USB QDLoader 9008 (COM5) which i assume is EDL.
I have tried flashing the stock rom image through the MiFlash software but its failing with various errors:
System IO exception. The requested resource is in use
Write time exceeded
can not read from port COM5
Drivers are installed correctly and i'm running it in administrator mode. I have tried different USB ports even a different machine both with the same result of errors.
I've been at it for hours and i am need of help please.
Thanks
Solved in the end i just had to keep trying through MiFlash. No idea why it was such a pain but it just worked on the 100th or so attempt so all i can say to anyone in the same situation is keep on trying.
hey guys, yeah i managed to brick my almost new phone, because i was dumb enough to fiddle around with tz files and whatnot in adb. i've used this forum to customize pretty much every single one of my phones before, but Xiaomi broke me lol.
Now my phone is a paperweight, I can't enter recovery, download mode, it's not recognized by fastoot, mi flash tool etc. I've tried pretty much everything i read on the internet, but i couldn't find a single guide for this particular phone so i had to mix and match every tip, so far no success.
my pc recognizes this device as Qualcomm HS-USB QDLoader 9008. I've read around that this is a good thing and I can reflash my software using QFIL, but I'm getting a Sahara Server Fail. Process stops right after trying to read the firehose file "ERROR: function: is_ack_successful:1134 SAHARA_NAK_INVALID_DEST_ADDR" which leads me to believe i've got a wrong file
this is likely because what i did was just download the official firmware and use prog_firehose_ddr.elf from there.
I tried doing this entire process in Win 10 test mode and i have disabled driver signatures, because some guides required that. I'm using the latest version of QFIL.
Now my questions are:
1. How do you enter EDL mode in this particular phone? I haven't found one particular way so i fiddled with what works - what i do is press Power and VOL- at the same time, this disconnects my phone from the PC, the LED starts blinking and when it stops blinking after about 15-20 seconds my PC recognizes the phone again. I've got a feeling this isn't the right way to do this, but when the LED is blinking my phone simply is not recognized by my PC.
2. What about the drivers? If my PC detects my phone, does it mean i've got proper Qualcomm drivers installed? I've read that some phones are super picky about those drivers, but i''ve reinstalled them a couple of times from different sources and i still get the error
3. Is there a way to download a proper firehose file for this phone from somewhere? i've found packages containing plenty of firehose files, but for some reason none of them seemed like they would be viable for this phone, i'm unsure if it's because of naming scheme of these files or what. Some guides require the programmer to be in .mbn extension, but the one i got is .elf
Thanks in advance for any ideas, I'm at the end of my rope here but I'm not ready to give up and take it to repairman just yet
Seems like I succesfully bricked my OP9Pro. Tried to restore in MSMDownloadTool v4.0. Oneplus 9 Pro LE2123.
Phone is detected correctly in Windows device manager(QDLoader 9008, I get to EDL by holding Vol+ and Vol- buttons and connecting the cable). When I try to flash, MSM breaks on Sahara communication failed(FH: 258).
Qualcomm drivers are from Windows Update Center(I connect my phone in EDL mode, click Update and in optional updates section there is the needed driver - Qualcomm Incorporated - Ports).
What should I do?
I saw a python EDL workaround script, but I'm not sure if helps me or if it even works (saw it somewhere on xda, the only thing I remember that it was in some of oneplus's devices thread and the sript name was edl.py, sorry
Tried on one laptop(Acer Nitro< none of the ports gave a succesful result). Gonna try on my second(Asus ROG GL702VMK, it seems to have better ports connection). Gonna write an update message.
I can't get to fastboot, recovery, etc. Phone seems to give no signs of life, there is even no charging notification when the cable is connected(but maybe phone isn't turned off actually, not sure)
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Shooter7889 said:
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Click to expand...
Click to collapse
Thanks for advice, I got further but now it stopped on Param Preload with "Device not match image"
I use MSMDownloadtool for EU and my phone is EU version(LE2123)
So, I am kinda happy cuz I booted to system.
I used this guide(https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/). Used MSM Download tool with Indian f/w.
Then I tried to return to EU version, but I got the same param preload error. I used this version of MSM and it flashed successfully.
So now I guess the issue is solved. Thanks @Shooter7889 for ur advice with lite firehose
Uncheck "check sha256" for mismatch device issue. Or find correct msm. You're welcome. I had same issue after bricking my 9pro and not being able to run msm successfully.