Hi everyone,
I have used guides posted on this forum for years now and it has helped me much in making my devices my own. First I wanted to thank everyone on this forum for the great content.
Now we get to my problem. Yesterday I tried to unroot my phone because I want to sell it. It is a European OP8Pro and I had rooted OOS global with magisk and custom recovery. I followed this guide here: https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/
In the Process there were a couple partitions that the tool was unabled to flash but it does not create any logs. I dont remember which ones it wasnt abled to do.
After the tool ran it rebooted my phone and the only thing I am abled to access is EDL or Qualcomm CrashDump Mode.
The next logical Step for me was using the MSMTool to flash everyting again which has worked for me in the past.
Now I haved tried alot of things to get this to work including different qualcomm drivers, different OOS Versions, different USB Ports, different USB Cables, disabeling SHA256 check, different PCs. Nothing worked for me. The MSMTool always fails with Firehose Communication Handshake Failed after 25s. It also seems that the phones disconnects during the process after downloading the Firehose Binary.
Now I am down the Rabbithole with Qualcomm QFIL and flashing the Firehose firmware but I dont know if I am right and the sources for that are quite dubious. I will include the MSMTool log maybe some OP Guru will guide me to the right way to fix this mess.
Thank in advance
Iredecent
[9944][05-18 09:15:06.121]<4> MetadataVersion=2,CryptVersion=1,[9944][05-18 09:15:06.121]<4> m_bIsPackImage=1
[9944][05-18 09:15:06.139]<4> Set Proc Mode 1
[9944][05-18 09:15:06.291]<4> ATO element doesn't exist. Skip.
[9944][05-18 09:15:06.299]<4> Project Name: 19811
[9944][05-18 09:15:06.300]<4> Factory ID:
[9944][05-18 09:15:06.300]<4> Image Version: instantnoodlep_15_E.34_210201
[9944][05-18 09:15:06.301]<4> Skip SHA256 Check: No
[9944][05-18 09:15:06.301]<4> HW CHK: No
[9944][05-18 09:15:06.302]<4> RF CHK: No
[9944][05-18 09:15:06.303]<4> PRJ CHK: No
[9944][05-18 09:15:06.303]<4> MDL CHK: Yes
[9944][05-18 09:15:06.304]<4> ATO build: No
[9944][05-18 09:15:06.305]<4> Load upd cfg failed. continue.
[9944][05-18 09:15:06.305]<4> config: 1
[9944][05-18 09:15:06.305]<4> Tool version verified! (V5.1.75)
[9944][05-18 09:15:06.305]<4> project 19811 not support boot mode feature
[9944][05-18 09:15:06.305]<4> project 19811 enable fuse
[9944][05-18 09:15:06.315]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[9944][05-18 09:15:06.329]<4> Skip multi-image identify: 0
[8356][05-18 09:15:10.982]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[8356][05-18 09:15:32.187]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[10160][05-18 09:15:33.647]<4> [0] SetComStep: 1
[13920][05-18 09:15:33.648]<4> [1] SetComStep: 1
[6464][05-18 09:15:33.648]<4> [2] SetComStep: 1
[6464][05-18 09:15:33.648]<4> [2] GetComStep: 1
[6464][05-18 09:15:33.653]<4> CID = -1
[6464][05-18 09:15:33.653]<4> Non TMO group
[6464][05-18 09:15:33.660]<4> [3] Set device as UFS
[6464][05-18 09:15:33.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[8356][05-18 09:15:43.404]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[6464][05-18 09:15:43.654]<4> [3] [SP][208] Reset Sahara
[8356][05-18 09:15:43.655]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Just to be clear, did you follow al the steps and do you use the firmware as provided in this thread?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
KaiseRRUby said:
Just to be clear, did you follow al the steps and do you use the firmware as provided in this thread?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yep, I followed that guide and searched the thread for my problem but nothing that worked for others has resolved my problem and nobody had the exact same problem. Also going into fastboot which solved the communication issue for others is not an option because fastboot isn't working on my device.
Is your fastboot working?
varunpilankar said:
Is your fastboot working?
Click to expand...
Click to collapse
No it isn't. The only things I am abled to access are Crashdump mode and EDL.
When you connect to EDL mode what do you see on Device Manager?
Also, which port are you using to device your device? USB 3.0 or 2.0?
varunpilankar said:
When you connect to EDL mode what do you see on Device Manager?
Also, which port are you using to device your device? USB 3.0 or 2.0?
Click to expand...
Click to collapse
When I connect my device in EDL I see Something QLoader 9008. I don't know the exact thing off the top of my head. This should be the right thing from my research on the topic.
I've tried multiple ports USB 2.0, 3.0, 3.1 even USB-C to USB-C.
Try to connect to EDL mode using USB 2.0 and press 'Enum' while in MSMTool, tell me what do you get
varunpilankar said:
Try to connect to EDL mode using USB 2.0 and press 'Enum' while in MSMTool, tell me what do you get
Click to expand...
Click to collapse
I'm getting COM5 Connected. Then I press Start and its the same error with the exact same logfile I posted above.
You mean "Sahara Communication Failed" right?
varunpilankar said:
You mean "Sahara Communication Failed" right?
Click to expand...
Click to collapse
No, the exact message being displayed is Firehose Communication Handshake Failed in red colour
iredecent said:
No, the exact message being displayed is Firehose Communication Handshake Failed in red colour
Click to expand...
Click to collapse
That's coz of Sahara Communication Failed. Are you running the program as administrator?
Trying checking this link:
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Let me find something more concrete, till then you can try the above link and keep us posted
I found one similar issue faced by oppo user, who was able to solve this problem by using the below method:
EDL MODE VIA RECOVERY (OPPO QUALCOMM)
1. Turn off your Phone
2. Go to recovery Mode (Press Power and Volume down)
3. Once in recovery mode, connect your phone to pc/laptop
4. Scoll down, Find VER1.2 and tap 3x times or more..
5. Message will Pop up and click ok
6. Phone Auto Turn Off!
varunpilankar said:
That's coz of Sahara Communication Failed. Are you running the program as administrator?
Trying checking this link:
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Let me find something more concrete, till then you can try the above link and keep us posted
Click to expand...
Click to collapse
I will try this later when I am at home and will keep you updated.
varunpilankar said:
I found one similar issue faced by oppo user, who was able to solve this problem by using the below method:
EDL MODE VIA RECOVERY (OPPO QUALCOMM)
1. Turn off your Phone
2. Go to recovery Mode (Press Power and Volume down)
3. Once in recovery mode, connect your phone to pc/laptop
4. Scoll down, Find VER1.2 and tap 3x times or more..
5. Message will Pop up and click ok
6. Phone Auto Turn Off!
Click to expand...
Click to collapse
Yeah I've seen this, there are a coupe of videos on this. Doesn't work for me because I am not abled to access recovery
iredecent said:
I will try this later when I am at home and will keep you updated.
Click to expand...
Click to collapse
Sure
iredecent said:
Yeah I've seen this, there are a coupe of videos on this. Doesn't work for me because I am not abled to access recovery
Click to expand...
Click to collapse
Alright.
I'll share more once I hear back from you.
varunpilankar said:
Alright.
I'll more once I hear back from you.
Click to expand...
Click to collapse
.....
iredecent said:
Yeah I've seen this, there are a coupe of videos on this. Doesn't work for me because I am not abled to access recovery
Click to expand...
Click to collapse
A couple of things, did you make sure to change the target in msm tool? Like, for 8 pro IN2025 we have to click target and change to O2. Also, I see this line...
6464][05-18 09:15:33.653]<4> Non TMO group
That means non T-Mobile. Maybe nothing but are you 100% sure you are using the right msm tool for your device? Not using one plus 8 msm tool for 8 pro and vicversa?
iredecent said:
Hi everyone,
I have used guides posted on this forum for years now and it has helped me much in making my devices my own. First I wanted to thank everyone on this forum for the great content.
Now we get to my problem. Yesterday I tried to unroot my phone because I want to sell it. It is a European OP8Pro and I had rooted OOS global with magisk and custom recovery. I followed this guide here: https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/
In the Process there were a couple partitions that the tool was unabled to flash but it does not create any logs. I dont remember which ones it wasnt abled to do.
After the tool ran it rebooted my phone and the only thing I am abled to access is EDL or Qualcomm CrashDump Mode.
The next logical Step for me was using the MSMTool to flash everyting again which has worked for me in the past.
Now I haved tried alot of things to get this to work including different qualcomm drivers, different OOS Versions, different USB Ports, different USB Cables, disabeling SHA256 check, different PCs. Nothing worked for me. The MSMTool always fails with Firehose Communication Handshake Failed after 25s. It also seems that the phones disconnects during the process after downloading the Firehose Binary.
Now I am down the Rabbithole with Qualcomm QFIL and flashing the Firehose firmware but I dont know if I am right and the sources for that are quite dubious. I will include the MSMTool log maybe some OP Guru will guide me to the right way to fix this mess.
Thank in advance
Iredecent
[9944][05-18 09:15:06.121]<4> MetadataVersion=2,CryptVersion=1,[9944][05-18 09:15:06.121]<4> m_bIsPackImage=1
[9944][05-18 09:15:06.139]<4> Set Proc Mode 1
[9944][05-18 09:15:06.291]<4> ATO element doesn't exist. Skip.
[9944][05-18 09:15:06.299]<4> Project Name: 19811
[9944][05-18 09:15:06.300]<4> Factory ID:
[9944][05-18 09:15:06.300]<4> Image Version: instantnoodlep_15_E.34_210201
[9944][05-18 09:15:06.301]<4> Skip SHA256 Check: No
[9944][05-18 09:15:06.301]<4> HW CHK: No
[9944][05-18 09:15:06.302]<4> RF CHK: No
[9944][05-18 09:15:06.303]<4> PRJ CHK: No
[9944][05-18 09:15:06.303]<4> MDL CHK: Yes
[9944][05-18 09:15:06.304]<4> ATO build: No
[9944][05-18 09:15:06.305]<4> Load upd cfg failed. continue.
[9944][05-18 09:15:06.305]<4> config: 1
[9944][05-18 09:15:06.305]<4> Tool version verified! (V5.1.75)
[9944][05-18 09:15:06.305]<4> project 19811 not support boot mode feature
[9944][05-18 09:15:06.305]<4> project 19811 enable fuse
[9944][05-18 09:15:06.315]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[9944][05-18 09:15:06.329]<4> Skip multi-image identify: 0
[8356][05-18 09:15:10.982]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[8356][05-18 09:15:32.187]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[10160][05-18 09:15:33.647]<4> [0] SetComStep: 1
[13920][05-18 09:15:33.648]<4> [1] SetComStep: 1
[6464][05-18 09:15:33.648]<4> [2] SetComStep: 1
[6464][05-18 09:15:33.648]<4> [2] GetComStep: 1
[6464][05-18 09:15:33.653]<4> CID = -1
[6464][05-18 09:15:33.653]<4> Non TMO group
[6464][05-18 09:15:33.660]<4> [3] Set device as UFS
[6464][05-18 09:15:33.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[8356][05-18 09:15:43.404]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[6464][05-18 09:15:43.654]<4> [3] [SP][208] Reset Sahara
[8356][05-18 09:15:43.655]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&15f15702&0&4#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Click to expand...
Click to collapse
I know that this happend years ago, but... were you able to find a solution ? I have exactly the same problem with my OnePlus 8 Pro
Related
Hi all,
After reading on letv.re that some people managed to brick their devices and were looking for a fix, I started to check more and more about the issue. What happened to some was that the phone would switch itself off and enter into Qualcomm Recovery Mode and would be seen when connected to a computer as “Qualcomm HS-USB QDLoader 9008”. For others, by flashing wrong files the phone would end up in the same state. Luckily a fix had been found, and it was shared by ParasiTe_RemiX.
DISCLAIMER
Given that maybe nothing will happen to your warranty and this is an unbricking tool, there are small chances that your device might get bricked for good, and I feel the need to say that I am not responsible for any damage caused by following these instructions. Any modification that you do to your phone you're doing at your OWN RISK.
Keep in mind that if your phone goes by itself in the QDLoader mode, it’s better to try some combinations below before flashing it using this method:
1) Keep the power button pressed for about 2 minutes, or
2) Keep the power button + Vol up pressed for about 2 minutes, or
3) Keep the power button while connecting the phone to a wall charger, or
4) Bring the phone into a bright light and press the power button (or power button + Vol up) for about 2 minutes, or
5) Keep the phone charging for more than 24 hours and repeat all the steps above.
If nothing works and you are willing to fix it and you’ll give up all your files, then this fix is for you. Or if you have flashed some wrong files and there is no Fastboot, nor Recovery, this is to be followed. Or if you want to reset your phone to a “factory state”, this is the way to go, and by that I mean if you want to check that your fingerprint sensor is working, or you have some other issues, it’s good to revert it this way.
What you will need:
a) A Windows computer
b) FlashOne program - the flashing program for the software
c) QFIL files for X820 (looks like some dev software dating April,2016)
IMPORTANT – YOU WILL LOSE ALL YOUR FILES ON THE PHONE, PHOTOS, MUSIC, APP DATA, INTERNAL STORAGE WILL BE WIPED.
So if your phone is in this Qualcomm Recovery mode, you can just connect it to the computer, and jump to step 3, if not, and you simply want to flash it, start from step 1.
1) To enter Qualcomm Recovery mode, first turn off the phone and go to step 2
2) Keep pressed Vol Up (+) and Vol Down (-) together and connect the phone by USB cable to the computer.
3) You will see that the computer will install drivers for "Qualcomm HS-USB QDLoader 9008".
4) Unzip FlashOne and start "main.exe". Once you've opened the flashtool you'll see "Flash Type". Here select "Qualcomm - flash dead phone".
5) Select your phone - "COM ..." from "Select device" - here should be the same COM ... as it shown in Device Manager under Ports (COM & LPT) > "Qualcomm HS-USB QDLoader 9008 (COM ...)"
6) Select File "LeMax2QFIL.zip" from the folder where it is saved
7) Press "Flash" in the lower part of the window
8) Once completed, disconnect the phone and power it up
9) Go to Settings – Storage format the internal storage.
To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
That's it. More info you will find in FlashOne program, actually it's almost like I've described it here.
You will be reverted to a "dev" version of the phone, somewhere with April build date. Keep in mind that it's EUI 5.6 and the kernel is different than EUI 5.8. Update it to latest EUI with stock recovery and then install the custom recovery of your choice.
Most of the guys install a recovery for 5.6 on EUI 5.8 or vice versa and then they get the blue LED. That's why you should read the instructions for each recovery and make sure you know which one you're flashing.
Download files:
Mega:
https://mega.nz/#F!0gwgxbxD!-iud2O-6uZ0F3Geofz-NyA
Google Drive:
FlashOne:
FlashOne1.9.zip
drive.google.com
QFIL:
Lemax2QFIL.zip
drive.google.com
TWRP: https://forum.xda-developers.com/le-max-2/development/twrp-root-14s-rom-x820-t3382221
https://mega.nz/#!Jl4DATLI!Z08l-0SWc98C1qUGDEOcTsj96DlY627B7nHtlKCp6qw
https://mega.nz/#!slYmEJ6K!Onc5pjb3teB9J6AunZnEe-k6mDJwQ2tQwUt0X51AudI
Stock Recovery (not tested) and needs an EUI ROM to be instaled as update.zip:
https://mega.nz/#!B0ZGgSQB!33UG9jpEL6b_zJm4M01yRpI0x4uHA4Q1XzaS0ntXVSI
Edit: Post updated.
Thanks
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
rapiteu said:
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
Click to expand...
Click to collapse
Honestly, I did this restoration of the phone about a month ago. I encountered some issues with the stock recovery but I can't remember what I did to fix it. I think I installed 017s at that time, directly from the dev software. Restarting the phone to recovery I think didn't work. I believe you should turn it off and then start it to recovery directly. I remember I wanted to download 015s, 016s, and even I gave up and wanted to install TWRP for 5.6 EUI but the stock recovery at some point worked. Try to turn off the phone (not restart) and then switch on in recovery. And check erase data as well.
valy_cta said:
1) To enter Qualcomm Recovery mode, turn off the phone. Keep pressed vol up and vol down and turn on the device by pushing the power button.
Click to expand...
Click to collapse
Hello, I just wanted how does it look to see the phone in its normal state but cannot switch it on againg form normal opration. Is there eny key combination. It looks like bricked just now
regard Filozof71
OK, it works. Need press power button ober one minute. Uff
Leeco X910 brick
Hello, my leeco x910 is bricked...
Black screen, no led, no sound nothing just usb connection is ok for flashing 9008 mode..
Is possible to obtain the good .mbn file for flashing?
Please help me
Best regards
valy_cta;69439085
1) To enter Qualcomm Recovery mode said:
Hello, I'm on Windows 7, I enter #3 point above but I can see only QUSB_BULK device under devices manager but Windows 7 does not have any drivers for it. I tried to dwonload some but withous success. Has anybody runover rhis instruction? Uder which Windows version?
OK. Under Windows 10 it works means it installs the phone as Qualcomm HS-USB QDLoader 9008 and its visible in FlashOne program.
Great appreciation to valy_cta!
regards Filozof71
Click to expand...
Click to collapse
Problem
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
link
bruno araujo said:
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
Click to expand...
Click to collapse
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
UP
UP
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
Click to expand...
Click to collapse
slawin wynterz said:
UP
Click to expand...
Click to collapse
He fixed his phone finally.
OP updated.
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg[/QUOTE
thank you, now I could install clean ROM
Click to expand...
Click to collapse
hard brick LeEco Le Max 2
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
beachboys1970 said:
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
Click to expand...
Click to collapse
Reboot phone, after power on one time flash it.
Did you find a fix for this? I am struggling with Lemax x910
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
valy_cta said:
He fixed his phone finally.
OP updated.
Click to expand...
Click to collapse
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: 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
Reboot phone (long press volume "-"), after power on (long press volume "+" "-" and power) and just one time flash it.
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: 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
I don't think that you can flash a X910 with X820 files, although I never tried and never heard someone to do so, the results might not be too good.
That error was due to the fact that he was not pressing the buttons properly before connecting to computer. Keep Vol up and Vol down and connect the phone. It should be switched off before.
Good luck!
Thanks very much
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Can you press the power button for at least 1 minute?
If you have it connected and it shows in computer as Qualcomm... 9008, it's ok. Maybe the files are detected as not being for your phone.
If you suddenly found the phone in such way and you didn't flash something that broke it, try to restart it as shown in the op. If not, try to discharge the battery fully that to flash something that it doesn't belong.
bil20 said:
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Click to expand...
Click to collapse
I just long press button "-" and it diconnected after 15-20 sec.
Help to restore bootloader on Nokia 6
What happened? We are no magicians
ZeroPointMax said:
What happened? We are no magicians
Click to expand...
Click to collapse
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...
Evgeny_14 said:
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...
Click to expand...
Click to collapse
Oops, you bricked your device. You cannot flash another region if that was your intention... You can either go to customer support or try to make a USB flash cable to force the files onto your device (pls use original firmware for your device). I know that this was mentioned in the forum before but I cannot remember where exactly and I don't know if it is actually working. If it fails, your device is pretty much ******...
Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354
Nokia 6 (TA-1003) bootloader restore how?
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno
desesperated
richardpimenov2001 said:
Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354
Click to expand...
Click to collapse
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.
grandroid7 said:
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno
Click to expand...
Click to collapse
I had exactly the same thing. . You must send the phone to the service.
Maxpowers88 said:
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.
Click to expand...
Click to collapse
I dont know if this would help you guys or not but this is portable one,
You dont need to configure any sahara file or anything, just select mbn file then xml and hit download
This tool helped me alot for so many other phone which gave me sahara error
Find the tool in the attachment
Hope this will help you
Hit thanks button if you find this helpful
Happy flashing
jurek09 said:
I had exactly the same thing. . You must send the phone to the service.
Click to expand...
Click to collapse
Hello,
I just got two used note3 phones from different sellers and try to install twrp.
The phones run Android 5.0
I can boot into Bootloader, into (stock) recovery and into system.
But neither with Linux/heimdall nor with Windows/Odin I can talk to the phone or flash a twrp recovery.
Under Linux a
Code:
heimdall print-pit --no-reboot --verbose --resume
results in this:
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
. . .
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
. . .
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving packet.
Releasing device interface...
When I boot into bootloader mode it shows
ODIN MODE
then then the normal information and ends with
UDC START
(see attachment)
Does anybody know what's wrong here?
Thanks in advance
Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??
JJEgan said:
Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??
Click to expand...
Click to collapse
Please provide PIT FILE 32GB before you get this problem. Its your cases like me get this one. Put this pit file on colum PIT and then put this your firmware blablabla.md5.tar then flash it.
OP be very carefull re PIT .
Flashing can brick your phone.
JJEgan said:
OP be very carefull re PIT .
Flashing can brick your phone.
Click to expand...
Click to collapse
Im trying this step and look success almost done.
Post the Odin log? Tried different USB cables and USB ports?
JJEgan said:
Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??
Click to expand...
Click to collapse
I had the Samsung drivers installed, but still had an unknown SM Bus controller.
Solved this now (it's a freshly installed windows 7 only for this task)
Now the phone shows up in Odin, but I am unsure how to continue.
I downloaded N9005XXSGBPL6_N9005DBTGBOI1_N9005XXUGBOJ1_HOME from sammobile which contains a file named N9005XXSGBPL6_N9005DBTGBOI1_N9005XXUGBOJ1_HOME.tar.md5
I guess I have an "old" model ans so selected this file for "AP" and hit GO. Attached is the screenshot of the result:
When I now restart the phone I get a Message:
"Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again".
that's weird to ma as Samsung suggests SmartSwitch for models with Android5. But SmartSwitch says "model not supported".
Kies tries to conect forever.
In Odin under "Options" neither "Re-Partition" nor "Nand Erase" is checked. Is this correct?
I'm pretty clueless now
Try a different version of Odin, USB cables, and USB ports.
audit13 said:
Try a different version of Odin, USB cables, and USB ports.
Click to expand...
Click to collapse
I already did change cable and port (and even the computer). Don't know where to get a different Odin version.
However, it's hard for me to imagine how a different USB cable should solve a size problem.
But I don't know, what that "size" error actually means.
I have always had good success with Odin 3.07: https://www.google.ca/url?sa=t&rct=...ad-odin-3-07&usg=AOvVaw0Rcrx5CDctRzS99UIaD36F
If a stock firmware cannot be flashed via Odin/Windows, you may have to have the phone force flashed using alternative hardware such as an Octopus box: https://octopusbox.com/
audit13 said:
I have always had good success with Odin 3.07: https://www.google.ca/url?sa=t&rct=...ad-odin-3-07&usg=AOvVaw0Rcrx5CDctRzS99UIaD36F
Click to expand...
Click to collapse
OK, I got this version now. Unfortunately it produces the same error as posted above. Size error upon flashing hidden.img
. . . hours later. . .
I found a pit file here https://www.sammobile.com/forum/showthread.php?t=30482
And with the HLTE_EUR_OPEN.pit I was able to flash that stock Android5. So at least the phone is alive again. :good:
What I don't understand: My phone came with a N9005BTUGBOJ1 ROM which seems to be British Telecom, Right? But I am in Germany. Is that of any relevance to me?
However. Now I'm back at step one, flashing TWRP and finally LineageOS
That worked fine
So obviously I bricked my phone with Heimdall. With Odin v3.04 flashing has been a pretty straight forward process. The new Odin build failed at the hidden partition.
The "only" problem left is that LineageOS doesn't recognize my SIM-card. :crying:
N9005BTUGBOJ1 ROM
That looks like the CSC not rom .
CSC is customer services basically local network details like APN .
No British Telecom network .
BTU modem is the generic UK modem for non branded devices .
JJEgan said:
N9005BTUGBOJ1 ROM
That looks like the CSC not rom .
CSC is customer services basically local network details like APN .
Click to expand...
Click to collapse
Maybe I used the wrong naming term. Phone status shows this:
Baseband version: N9005XXUGBOj1
The name of the stock ROM I flashed is N9005XXSGBPL6_N9005BTUGBOJ1_N9005XXUGBOJ1_HOME.tar.md5
JJEgan said:
No British Telecom network .
BTU modem is the generic UK modem for non branded devices .
Click to expand...
Click to collapse
Thank you for the clarification. Which one is suitable for Germany? Does it matter at all? With the stock firmware telephony seems worked normally. Only with LineageOS no SIM-Card is detected.
After a failed attempt to enable a Google Camera HDR+ port, I've found myself unable to boot and with a locked bootloader. I would also be happy if the bootloader could be unlocked, but I have no access to the Android settings and "fastboot oem unlock" refuses to act; and the XiaoMi unlock tool falsely claims that the device is already unlocked "and there is no need to unlock again". So my only hope is flashing a ROM in EDL mode with XiaoMi Flash. Unfortunately, it's easier said than done.
First of all, initially my Win7 64-bit systematically tried to load the wrong Qualcomm driver, namely "Qualcomm HS-USB Diagnostics 900E", which doesn't work. After forcing a driver update (which requires unticking the "Show compatible hardware" box: why??) I finally managed to convince Windows to load the "Qualcomm HS-USB QDLoader 9008". The loading is only achieved if the USB cable is plugged in after a fresh phone reset with Up and Down volume keys both pressed (or, in Fastboot mode, after invoking "fastboot oem fastboot-edl" with fastboot_edl), but that's OK. Then, clicking the "Refresh" button in XiaoMi Flash' window, I see the line mentioning the COM port (COM6 in my case). Unfortunately, if I then press "Flash" the operation ends in error ("[14:09:30 COM6]:sahara read end error with status:9"). The log file reads:
Code:
[14:09:30 COM6]:MiFlash 2016.12.22.0(Release)
[14:09:30 COM6]:[COM6]:start flash.
[14:09:30 COM6]:received hello packet
[14:09:30 COM6]:download programmer C:\CDs\XiaomiMiA1\tissot_images_V9.6.4.0.ODHMIFE_8.0\images\prog_emmc_firehose_8953_ddr.mbn
[14:09:30 COM6]:sahara read end error with status:9
[14:09:30 COM6]:[14:09:30 COM6]:sahara read end error with status:9
[14:09:30 COM6]:flashSuccess False
[14:09:30 COM6]:isFactory False CheckCPUID False
[14:09:30 COM6]:before:flashSuccess is False set IsUpdate:True set IsDone True
[14:09:30 COM6]:after:flashSuccess is False set IsUpdate:false set IsDone true
Any idea? Am I using a wrong version of the QDLoader driver (2.1.2.2 25/03/2016) and/or of XiaoMi Flash (2016.12.22.0(Release)), and, if so, which one is known to work with a Mi A1?
i had the same problem i tried to instal gcam but i was usin a costom rom and my phone got bricked, my only hope was EDL mode but i did know how to do it, i just went to the service xiaomi and the fixed i recomend to you do the same, go to xiaomi service.
I do not know if you already tried this procedure, if you have not done it it would be worth giving it a look.
http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
good luck.
teacapan said:
I do not know if you already tried this procedure, if you have not done it it would be worth giving it a look.
...
good luck.
Click to expand...
Click to collapse
Thank you. I also tried that method ("deep flash engineering cable") but the results were the same: and from what I understand that's just one of the several ways of putting the phone in EDL mode, just like the reset with "Volume Up" and "Volume Down" keys both pressed, the "test point method" (which requires opening the phone), the "fastboot oem reboot-edl" command while the phone is in fastboot mode, or the "adb reboot edl" command while Android is running. My phone does go in EDL mode (which is why the QDLoader drivers gets loaded and Xiaomi Flash duly "sees" the phone); unfortunately something seems to go wrong during the Sahara protocol communication between Xiaomi Flash (through the QDLoader 9008 USB driver) and the phone. I suspect that there is some incompatibility between the Xiaomi Mi A1 EDL software and the particular version of QDLoader driver I used, but I already tried two different versions with the same negative results. If someone here has successfully used this method with a Xiaomi Mi A1, please let me know the version of the QDLoader driver that was used...
otto81709 said:
i had the same problem i tried to instal gcam but i was usin a costom rom and my phone got bricked, my only hope was EDL mode but i did know how to do it, i just went to the service xiaomi and the fixed i recomend to you do the same, go to xiaomi service.
Click to expand...
Click to collapse
I did, in the Hong Kong service centre in Mongkok, but, after testing it, a the technician (not a very smart one IMHO) said that "it can't be turned on and the only solution is to replace the main board", which, as I don't have the original purchase receipt, would cost me HKD 1,000...
Hi everyone. Need some help.
How can i unbrick my ZenFone Max Pro M2 (ZB631KL)
Issues - after programm stuck, phone was restarted, and then - Black screen, zero reaction. No indication.
PC show's - qualcomm hs-usb qdloader 9008.
I tried QFIL with [firmware27]ZQL1820_Factory_201812071630_ChangeFlash.zip
But failed. Always one of two errors
1. sahara_rx_data:276:Unable to read packet header. Only read 0 bytes
2. Download Fail:FireHose Fail:FHLoader Fail: File dosn't exist.
What i can do without hardware flash ?
Thank for answers!
Closed. I done it. Phone is alive
How did u do that..can u pls tell me
antizack said:
Hi everyone. Need some help.
How can i unbrick my ZenFone Max Pro M2 (ZB631KL)
Issues - after programm stuck, phone was restarted, and then - Black screen, zero reaction. No indication.
PC show's - qualcomm hs-usb qdloader 9008.
I tried QFIL with [firmware27]ZQL1820_Factory_201812071630_ChangeFlash.zip
But failed. Always one of two errors
1. sahara_rx_data:276:Unable to read packet header. Only read 0 bytes
2. Download Fail:FireHose Fail:FHLoader Fail: File dosn't exist.
What i can do without hardware flash ?
Thank for answers!
Click to expand...
Click to collapse
Pls share your knowledge to us master :[
1. Use QPST. QFIL without QPST will not work. U'll get error (File not found or file not exist)
2. Use QPST v 2.7.495
With 2.7.496 i was getting error - 0 bytes readed
3. Important. Use windows 7. I don't know why - a wasn't able to flash on win 10 with USB 2.0 port or usb-hub.
I currently have Win 8.1, I think I'll try with that, if it doesn't work, I can always make a new partition and install win 7 there. Anyway I have never heard of QPST and QFIL, so I'll do some researches on that.
Thank you for your time, we really appreciate. I'll let you know if I manage to unbrick my device.
Be careful. When u'll flash, don't forget to check couple times all settings in QFIL.
I'm talking about xml files.
antizack said:
Be careful. When u'll flash, don't forget to check couple times all settings in QFIL.
I'm talking about xml files.
Click to expand...
Click to collapse
I don't understand where I have to get the files I need. I saw I need the firmware, I guess, but I don't understand what's up with the XML file. Where did you get them? Sorry if I'm disturbing you again.
NoobNotMaster69 said:
I don't understand where I have to get the files I need. I saw I need the firmware, I guess, but I don't understand what's up with the XML file. Where did you get them? Sorry if I'm disturbing you again.
Click to expand...
Click to collapse
Hello colleague, I also have the same problem, I tried some programs, but they didn't work, but I still haven't tried this QPST_2.7.495, but I need the flash, because I deleted the ones I had here. if you found it, give me the link.