UPDATE: Turns out "Firehose getufsinfo failed" is basically your memory is dead. Got RAM replaced and it started working just fine again, without any loss of data. It was a hardware issue.
hi, My Oneplus 7 Pro (GM 1911) is bricked to the point that the volume/power buttons don't boot me into fastboot anymore.
I tried using the MSM tool. The first time it loaded until the point it got stuck at "Param Preload". Since then, at every try, it goes as far as 'Firehose GetUFSinfo Failed' at the 7 seconds point and disconnects automatically. The Power/Volume buttons however work when I connect the phone to the PC. Fastboot doesn't work, it just helps reconnect to the PC without removing the USB C cable. And when that happens, it again disconnects at the 7-second point at "Firehose GetUFSinfo Failed".
When I disconnect and reconnect my phone either by physically removing the USB C cable or by pressing the volume buttons/power buttons, I get the "Firehose GetUFSinfo Failed" error, but when I don't do that and click on the 'ENUM' option in the top left of MSM tool, the device is shown as connected again, and then when I click start I get the "Sahara Connection Failed. Please try again after power off phone (PBL:6)" error.
At this point, I've used several different drivers, USB ports (3.0 and 2.0), and different OOS files. This happened out of nowhere, I had OOS beta of about 2021 installed.
Try disabling driver signature on Windows. Reinstall the MSM drivers and try again. That worked for me
@soka said:
Try disabling driver signature on Windows. Reinstall the MSM drivers and try again. That worked for me
Click to expand...
Click to collapse
did you have the 'firehose getufsinfo failed' error? because someone I just spoke to said that the error means that the storage chip is dead and software isn't gonna do anything. I would need a motherboard replacement
Not really sure, about the "getufsinfo failed" part. Was some firehose error.
Hi,
What do you have in the Port COM section in your windows console device manager ?
Did you try :
- another sure USB cable ?
- another computer ?
ie : I had to change from a computer using a USB-C to USB-C port to an old one using a tradtional USB port to make msm work
I have the same issue with un-bricking oneplus7t "Firehose getufsinfo failed"... nothing is working for me.. tried everything, now i don't know what to do.
Related
HI,
i have Amilogic M805, Wifi is AP6212
on the board is: Netxeon MK808Q_V10-20140822
On the cover is MINI TV form android Quad - Core MK808B Plus
If i tried USB_Burning_Tool
I have error [0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
Why ?
czmirage said:
HI,
i have Amilogic M805, Wifi is AP6212
on the board is: Netxeon MK808Q_V10-20140822
On the cover is MINI TV form android Quad - Core MK808B Plus
If i tried USB_Burning_Tool
I have error [0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
Why ?
Click to expand...
Click to collapse
I had the same problem with S905 when use defective usb flashing cable. and try redownload firmware
Such_A_Victor said:
I had the same problem with S905 when use defective usb flashing cable. and try redownload firmware
Click to expand...
Click to collapse
i try 2 cables and 2 computers
windows 10 64bit
a windows xp 32bit
same error.
I had same problem with M8S android box, through trial and error and an hour of pulling my hair out, I tried this, Amlogic burning tool, Toothpick method and male to male usb cable. (Leave toothpick in AV hole )After releasing the toothpick and pressing start the error comes up after 2% I quickly pressed the toothpick in again to see what would happen and boom it started to burn the firmware on, maybe luck i dont know but box back up running.. Hope it works for others..Des
how you fix that error? Romcode/Initialize DDR/Read initialize status/USB Control Setup Error
Same problem with MXIII 4k =(
Had the same problem, shortened the USB cable (that i made myself) to 15Cm, then it worked, signal integrity ?
first put the rom you will use, then press start, only then plug the device into the USB port. Worked with me having the same problems.
work for me... redownload firmware
Code4power, a link please for download the img
Had same issue with MXS Plus unit.... Tried a different USB-USB cable and now up and running. MANY THANKS TO ALL ON HERE
uncheck erase flash and bootloader in amlogic tool and that should fix your problem
renzenar said:
uncheck erase flash and bootloader in amlogic tool and that should fix your problem
Click to expand...
Click to collapse
Worked like a charm. Thanks
thank youuuu
renzenar said:
uncheck erase flash and bootloader in amlogic tool and that should fix your problem
Click to expand...
Click to collapse
THanks its work for me
I cannot get past that error. I have tried 3 different computers and various different versions of the burning tool as well as unchecking the boxes suggested above. So frustrating.
x96pro +
Awkomo said:
I cannot get past that error. I have tried 3 different computers and various different versions of the burning tool as well as unchecking the boxes suggested above. So frustrating.
Click to expand...
Click to collapse
I had the same issues as described above, and I simly just changed the cable lenght from 1.5m to 30cm and the box started flashing itself from the burning tool!
I got a shorter cable but it still does it for me
So guys after going crazy did this - Tried the Nand Method on a95x. Sequence - Upload your image to USB burning tool (don't hit start) - connect USB A to A cable (didn't connect) - Flash Pins 5-6 or 6-7 - Now USB tools see's the box but don't hit start yet - because usb power is not enough to burn it - Now insert the toothpic to hit the reset button - Now connect power while toothpic is inserted - Viola - the box starts burning - This is a sure to work method - everytime.
jahjahjah said:
So guys after going crazy did this - Tried the Nand Method on a95x. Sequence - Upload your image to USB burning tool (don't hit start) - connect USB A to A cable (didn't connect) - Flash Pins 5-6 or 6-7 - Now USB tools see's the box but don't hit start yet - because usb power is not enough to burn it - Now insert the toothpic to hit the reset button - Now connect power while toothpic is inserted - Viola - the box starts burning - This is a sure to work method - everytime.
Click to expand...
Click to collapse
Dear, i tried this method as well...but no luck. please advice..., if possible please share the link for usb burning tool and the firmware for MXQ PRO+ model. Will try fresh. Would highly appreciate ur help...
Had the same problem with mecool km9.
Tried all with no luck, then i tried to disconnect the box, close then restart usb burning tool, load the img file, unchecked erase flash and erase bootloader, hold the reset button with toothpic, then connect the box, hit refresh, and after that, start the flashing process.
So, if you tried to uncheck erase... like i did, you should try to disconnect the box, as it doesn't seem to register the unchecking without that.
:good:
You can see how many failed i had before disconnecting/reconnecting the box !
I have an at&t LG G3 D850
It was stuck with a McAfee lock and kill switch after letting someone borrow it.
I finally found a guide that let me get into download mode.
That guide wanted me to use LGUP but it would not recognize my phone it just kept saying unknown even though the phone shows in my device manager.
So now I am trying LG Flash Tool. But it seems to be stuck in the "ready" position.
I've heard that it doesn't work well with win10 but I am not sure. I only have this laptop and one with win8 on it. I was getting an error "milky way not connecting" but set the compatibility to win7 and that stopped.
Any idea why it is stuck in the ready position?
LilNerd1 said:
I have an at&t LG G3 D850
It was stuck with a McAfee lock and kill switch after letting someone borrow it.
I finally found a guide that let me get into download mode.
That guide wanted me to use LGUP but it would not recognize my phone it just kept saying unknown even though the phone shows in my device manager.
So now I am trying LG Flash Tool. But it seems to be stuck in the "ready" position.
I've heard that it doesn't work well with win10 but I am not sure. I only have this laptop and one with win8 on it. I was getting an error "milky way not connecting" but set the compatibility to win7 and that stopped.
Any idea why it is stuck in the ready position?
Click to expand...
Click to collapse
Your using a USB 2.0 port correct? USB 3.0 won't work. And you've changed the LG/Android com port to com41 in device manager?
If so have you tried unplugging and replugging the phone? Remember each time you attempt to flash you need to reboot the device. (Make sure your in download mode)
About the mcafee thing. I do know it blocked download mode, since you said you found away around it. I don't think flashing will remove the mcafee lock. But it's still worth a try!
Sent from my iPhone using Tapatalk
hyelton said:
Your using a USB 2.0 port correct? USB 3.0 won't work. And you've changed the LG/Android com port to com41 in device manager?
If so have you tried unplugging and replugging the phone? Remember each time you attempt to flash you need to reboot the device. (Make sure your in download mode)
About the mcafee thing. I do know it blocked download mode, since you said you found away around it. I don't think flashing will remove the mcafee lock. But it's still worth a try!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, USB 2.0 and I have tried unplugging and replugging the phone. COM41. I just rebooted and tried again but it is still stuck at ready. I am in download mode.
I tried it about an hour ago and read to disconnect the USB and reconnect to "jump start" the flash tool. At the time when I disconnected it gave me a "waiting for connection" message. When I reconnected it was starting to work but my cat unplugged the USB and I haven't been able to get it to work since.
LilNerd1 said:
Yes, USB 2.0 and I have tried unplugging and replugging the phone. COM41. I just rebooted and tried again but it is still stuck at ready. I am in download mode.
I tried it about an hour ago and read to disconnect the USB and reconnect to "jump start" the flash tool. At the time when I disconnected it gave me a "waiting for connection" message. When I reconnected it was starting to work but my cat unplugged the USB and I haven't been able to get it to work since.
Click to expand...
Click to collapse
You'll just need to keep retrying. But yeah need to unplug and replug sometimes to get it to work. Have you rebooted your computer? Also what sort of USB cable are you using? The oem LG one?
If you've changed USB ports etc each time make sure you check device manager as it can change the com port back.
Sent from my iPhone using Tapatalk
hyelton said:
You'll just need to keep retrying. But yeah need to unplug and replug sometimes to get it to work. Have you rebooted your computer? Also what sort of USB cable are you using? The oem LG one?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Using the cable that came with the phone.
I will give restarting my computer a shot.
Hello! First post here, bit of a doozy. I have a OnePlus 6 and this weekend I decided I'd try out LineageOS 18. I installed it fine and it works (phone isn't bricked) but I've decided I want to go back to Oxygen OS now. However, I'm having a lot of trouble making this happen.
I've been following all the various guides, which involve using MSM Tool to flash the stock ROM back to the phone, but it always hangs up when I hit "Start" on MSM Tool. It'll get stuck on "Waiting for Device," or sometimes I get "Open Serial Device Failed" and I've also gotten "Sahara Communication Failed."
It seems like I can get everything else right though, so I'm not sure why it hangs here. The phone, when plugged in, shows up in Device Manager as "Qualcomm HS-USB QDLoader 9008 (COM3)" like it should, and it also shows up in MSM Tool under COM 3, so it should be good, but it just never works when I hit "Start."
Does anyone have any ideas on what to do? It's not the end of the world but I'm having issues with Lineage and it would be real nice to be back on stock Oxygen OS. Thanks.
I wonder if you're on a USB 3.0 port. If so, try a USB 2.0 port. Cheers.
Kidneybot said:
Sahara Communication Failed
Click to expand...
Click to collapse
This might happen when you are using a USB 3.0 port. Try changing to a USB 2.0 port one.
Kidneybot said:
Open Serial Device Failed
Click to expand...
Click to collapse
This happens when 2 devices like printers or something uses the same COM port, make sure there is no weird serial devices are plugged in at the same time, also make sure your drivers are installed correctly and functioning.
When you get the Sahara message, leave the message on the screen and hold the power and volume up buttons on your phone. It will briefly re-establish connection then start the download. This worked for me when I had the problem. Good luck.
I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
lukebukowiec said:
I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
Click to expand...
Click to collapse
Keep at it.
I spent two days unbricking a 7T when it happened. Take 2/3 tutorials and see that every condition is met. Don't forget to look for the proper Qualcomm pilots, you might need to update them manually. (If I didn't know any better I'd say that your problem here)
The drivers you're looking for are named QDLoader something.
I know it should work because I did it on the One plus 9 if my memory serves me right, you just need to follow through and make sure that you also have the right MSM tool.
Pay attention to small details like the phone might be crashing on the start you should restart accordingly, or maybe you're not pressing the right volume button (was it up + power? I don't remember) and see what your computer sees plugged in.
Use more than one USB cable just in case but seems unlikely.
I followed this procedure since the one you referenced the google docs link would never download for me: https://www.droidwin.com/unbrick-oneplus-9-pro-msm-download-tool/
I had to use the alternate method to get to EDL mode in that tutorial since the normal one did not work. I also had to uncheck the box that said something about SHA256 before it would say Waiting.
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!
Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/
Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.