Related
So I was going through the rooting process for the second time on my ATT Moto X and while in bootloader flashing 4.2.2 something went wrong and it wasn't fully flashed. There was no error, it just said "Done" on bootloader. So I restarted the phone and ever since then the phone has had a black screen, although when I plug it into my computer it recognizes it. With that said, I've tried to use RSD Lite but it just fails to put it into fastboot mode, and it does not come up under either fastboot devices or adb devices.
Not sure what else I could do from here. Holding the power button and volume down button to get into bootloader doesn't work either. Does anyone here have any ideas?
TsterT said:
So I was going through the rooting process for the second time on my ATT Moto X and while in bootloader flashing 4.2.2 something went wrong and it wasn't fully flashed. There was no error, it just said "Done" on bootloader. So I restarted the phone and ever since then the phone has had a black screen, although when I plug it into my computer it recognizes it. With that said, I've tried to use RSD Lite but it just fails to put it into fastboot mode, and it does not come up under either fastboot devices or adb devices.
Not sure what else I could do from here. Holding the power button and volume down button to get into bootloader doesn't work either. Does anyone here have any ideas?
Click to expand...
Click to collapse
Can you clarify a few things?
First, have you been on 4.2.2 this entire time, or were you attempting to 'downgrade'?
Next, when you "turn on" the device, you say it has a black screen...does it light up at all, or vibrate?
And third, when you say the device is 'recognized' by the PC, how is it recognized? When you go to Device Manager, do you see a listing for "qhsusb_bulk"? If not, what is the device listed as?
Sorry I didn't specify those things in the original post, but I appreciate you taking the time to respond.
I was originally on 4.4 and was in the process of downgrading to 4.2.2 post-camera.
The phone does not light up or vibrate or anything, but I can hear it connect on my computer. Not that this is the computer making the sound, not the phone.
And third, my phone comes up as a listing on RSD Lite v6.5.1. It does not provide any information, it just says it is connected. My device is listed as "Qualcomm HS-USB QDLoader 9008 (COM4)"
TsterT said:
Sorry I didn't specify those things in the original post, but I appreciate you taking the time to respond.
I was originally on 4.4 and was in the process of downgrading to 4.2.2 post-camera.
The phone does not light up or vibrate or anything, but I can hear it connect on my computer. Not that this is the computer making the sound, not the phone.
And third, my phone comes up as a listing on RSD Lite v6.5.1. It does not provide any information, it just says it is connected. My device is listed as "Qualcomm HS-USB QDLoader 9008 (COM4)"
Click to expand...
Click to collapse
OK, I understand. There may be hope for you but it will require patience and exacting precision. Don't get your hopes up TOO much, but I will attempt to help you.
Normally, it is NOT possible to downgrade, but (thankfully) 4.4 > 4.2.2 Post-Camera is the one exception.
First, I realize that RSD Lite shows "Qualcomm HS-USB QDLoader 9008 (COM4)", but I need you to open Device Manager and tell me what it says in there. If you aren't familiar with how to get there, simply press the start button, and type 'device manager' (without quotes, of course). It should show up under "Control Panel", assuming you are on Windows 7.
Also, tell me for sure which version of Windows your PC is running.
Then we can proceed further.
"Qualcomm HS-USB QDLoader 9008 (COM4)" is from Device Manager. RSDLite simply lists the model as "QHSUB_DLOAD"
I am running Windows 8.1 64bit
TsterT said:
"Qualcomm HS-USB QDLoader 9008 (COM4)" is from Device Manager. RSDLite simply lists the model as "QHSUB_DLOAD"
I am running Windows 8.1 64bit
Click to expand...
Click to collapse
Ah, OK. This is good news.... "QHUSB_DLOAD"
Basically, you have somehow corrupted your bootloader.
Please reference this thread: http://forum.xda-developers.com/showpost.php?p=49876179&postcount=1
If you follow the instructions exactly, we should be able to force your phone into fastboot mode. From there, we can manually flash back to 4.4
Remember, there are no guarantees with this, and I don't even know if it has been attempted or is possible in Windows 8. So if you aren't successful, get your hands on a Windows 7 PC, and try again.
If you get stuck, post back here and I will attempt to help.
Sweet man, I really appreciate your help. I'll try all of that and report back here when done. Thank you again.
TsterT said:
Sweet man, I really appreciate your help. I'll try all of that and report back here when done. Thank you again.
Click to expand...
Click to collapse
One last comment: Do NOT use a USB 3.0 port for this. Only use a USB 2.0 port. Good Luck, and let us know how it works out....
Hell ya, it worked like a charm. Back into bootloader. Thank you again for helping me so quickly. You're awesome.
TsterT said:
Hell ya, it worked like a charm. Back into bootloader. Thank you again for helping me so quickly. You're awesome.
Click to expand...
Click to collapse
Welcome!!! Glad it went so smoothly for you. Remember to give 'thanks' to the OP of the De-Bricking thread I linked you to.
:good:
Help please
Help please
hi Bro
I followed ur step bcz my phone got stuck on the 4th step
http://forum.xda-developers.com/moto...t1060-t3118342
when i did the 4th step it got lack for around 30 min and nothing happens i quit the application and the phone is still in black screen
i have attached images with error what i get
i have moto xt1060
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Connect phone to computer.
Take off battery. And wait.
Is your pc can detect your device on bootloader mode?
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Or google "Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 (if you have the right kind of rom)"
And use that method.
Yes
nhmanas said:
Is your pc can detect your device on bootloader mode?
Click to expand...
Click to collapse
My pc sees the phone in QDLoader 9008 mode
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
I don't know what that is but flash stock rom again via fastboot
General Mobile 4G Dual cihazımdan Tapatalk kullanılarak gönderildi
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
I shall try but I pray it works. I am literally stuck in Android Development without my phone, Emulators aren't good enough
My dear sir you are a freaking genius
You my friend are a genius. I dont know where you acquired these files. It works like brand new. Thank you sir. Thank you thank you thank you!!!!!!!!!!!!!!!!
One Problem.
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
The phone wont turn on with battery in. It only turns on when I use usb without battery
yasteellutch said:
The phone wont turn on with battery in. It only turns on when I use usb without battery
Click to expand...
Click to collapse
Try flash stock rom via fastboot from here
http://builds.cyngn.com/factory/crackling/cm-12.1-YOG4PAS33J-crackling-signed-fastboot.zip
FindYanot said:
Open https://cloud.mail.ru/public/NExC/qxFwsmmmV/Wileyfox Swift/Recover SW/
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction https://mega.nz/#!YUFiXRwI!PlPCplXY31Rje57IfmWucTbRY6d56nSU6de46cQxIqU
Click to expand...
Click to collapse
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
dabotsonline said:
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
Click to expand...
Click to collapse
Would you mind posting those files, why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Sent from my SM-N920I using Tapatalk
hmsq said:
... why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Click to expand...
Click to collapse
I have those files as well, and get the same problem even when removing the battery.
hmsq said:
Would you mind posting those files...
Click to expand...
Click to collapse
Will do when I have a chance!
Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?
https://www.youtube.com/watch?v=uxrhJkSZc6E
Already tried that. Doesn't seem to change a thing.
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>
k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.
Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv
Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Had allready done that also. Gave it another try without success
k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:
Bro please help my device in bricked
k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img
Hello everyone,
I recently stopped using my Nokia 8 in favor of my new iPhone 11. However, I wanted to keep it just so I have an emergency Android phone. I found an article that says that there is a possible way to update Nokia 8 via TWRP. Of course, I didn’t trust it, so I backed up my phone via TWRP. Here are the steps I took after back up:
- I deleted everything from the device including the OS, excluding SD
- I tried installing the image but it failed
- I then restored my backup
However, phone won’t boot even after I restored my backup. I followed these instructions (forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646/) to flash the stock firmware, but the OST LA program keeps giving me 0xc3b9 something like tool func not ready. Can anyone help me? Thanks in advance!
- I have my bootloader unlocked, if anyone’s wondering.
EDIT: I have followed the steps with more care, and I managed to advance to the flashing process, but it gets a new error; 0xc6DA
EDIT 2: I realized I don't have critical unlocked. I can't access my unlock.key since download link expired long ago. Is there any way I can unlock the critical at this moment?
Does your computer recognize your device in 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
How do I enter 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
UPDATE: It's recognized as HS-USB Diagnostics 9008
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
dongvatm said:
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
Click to expand...
Click to collapse
Do you have a link for OST LA 6.2.8 and its patch?
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
dongvatm said:
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
Click to expand...
Click to collapse
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
RaleBurazer said:
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
Click to expand...
Click to collapse
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
Yes, I do have that driver, and my phone is shown as 9008 device in device manager while I’m in EDL, however I get an error which said that image upload using Sahara protocol failed. Is there any fix for that?
QDloader 9008 not HS USB diagnostic 9008
dongvatm said:
QDloader 9008 not HS USB diagnostic 9008
Click to expand...
Click to collapse
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
You must download Qualcomm Usb driver. Use google to find it. Good luck
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
Does it work?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
dongvatm said:
Does it work?
Click to expand...
Click to collapse
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
RaleBurazer said:
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
Click to expand...
Click to collapse
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
dongvatm said:
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
Click to expand...
Click to collapse
Now I managed to get rid of Sahara upload error, but I again got 0xc6DA error
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Optimus_Toaster said:
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
Update on the whole situation:
I managed to get to the download mode, and flash OREO NOVEMBER boot image on it. It successfully booted into Pie that I previously had installed. When I tried to follow the instructions given in the quoted post, I install November OTA successfully, but when I try to install December update, it says that I should use the 488K package. After I do that, it aborts the installation because there is no driver directory found. I think “Okay, November is fine” but when I try to reboot it goes into EDL. I again managed to flash the OREO boot image, and boot again into PIE (how is this possible?)
Also sidenote: WiFi doesn’t work. It didn’t work even after the first time I flashed Oreo boot. Can anyone perhaps provide me with a stock Pie boot image? Or does anyone know any other solution?
Back to stock - the aftermath
Hi all,
https://forum.xda-developers.com/showthread.php?t=4081895
(please read first and last post)
In short: I found some sketchy Android 10 update for Nokia 8, tried it out, did not work. Tried to restore my TWRP backup, did not work. Tried to bring back stock firmware via OST LA, did not work. I then flashed stock Oreo November 2018 boot image, and got into my Pie, but WiFi wasn't working. I then flashed pre-Magisk-rooted pre-TWRP-installed boot image, and WiFi works. However...
When my phone boots, it boots with Android logo instead of Nokia's
My phone is detected as Dual SIM, even tho it is not.
When I try to flash OTAs via TWRP, it doesn't work
I am looking for a solution on how to remove the Dual SIM problem and how to make my phone again boot with a classic Nokia logo. Any help? Thanks in advance!
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
lukegonewild said:
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
Click to expand...
Click to collapse
It sounds like you've corrupted your bootloader. Have you already used this guide? I suggest asking for support there.
I fixed it already, it works with 11.9.9.
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
marcelhdhd said:
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
Click to expand...
Click to collapse
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
lukegonewild said:
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
Click to expand...
Click to collapse
Thanks for your reply, but I managed to find the problem a few hours later. It was a bad USB-C cable.
Head -> Table