STUCK using msm tool for oneplus 6t at 9% " firehosecheckrsp failed " errno258
STUCK using msm tool for oneplus 6t at 9% " firehosecheckrsp failed " errno258
pls help
I CAN ONLY ENTER FASTBOOT MODE
DEVICE STATE 'LOCKED''
@sAmboy13
Once you are in fastboot mode at the screen that reads "START" use your volume rockers to navigate up or down and go to screen that reads "POWER" and use your power button to then select that and your device should turn off and you can then connect your device how the directions say and your PC should see your phone and in device manager your OnePlus 6t will be labeled Qualcomm USB driver or something like that.
User who commented after my post here is correct. And any time your using crappy windows best believe the Qualcomm USB drivers are not going to install smoothly. I had to uninstall mine and reinstall to get them to work.
I believe firehose has something to do with the connection between your device and the computer, like a connection. I know on Motorola devices firehose means your PC is attempting to communicate with your device...
(Edit)
The thread for that tool specifies to hold the volume up button for 5 seconds before connecting however I found I needed to hold both volume up and volume down to get the tool to work. Make sure to go to fastboot and then turn the phone off before this as it won't work if you've already tried connecting using the volume up method while off. Gotta start fresh. Hope this helps.
FirehoseCheckRSP
Hello. How to solve this problem?
Use one of the Fastboot roms there pretty much foolproof.
I am facing the same issue in my OP6T
> Device issue (Stuck at Boot Logo)
> Fastboot Accessible
> Recovery Inaccessible (stuck at boot logo)
> Device Detected Successfully in EDL Mode
> Bootloader Locked
While flashing stock rom using msm tool
It stuck at:
Firehorse Check Rsp Failed Err 258
I also tried flashing through fastboot mode but Bootloader is locked, so failed
Help please
I haven't seen a solution posted yet about this issue anywhere, but if anyone comes across this, I was able to solve this using a different usb cable and port. I was hitting this error midway when using a usb-c to usb-c cable on my laptop's thunderbolt port, and it worked when I used the original usb-a to usb-c connected to my laptop's USB 3 A port.
Same here. Worked with usb-a to usb-c, but not with usb-c to usb-c. Thank you!
Related
So I was given another HTC sensation recently but this time it's bricked and I don't know how to fix it.
I have a working HTC sensation phone to test that the driver work on win 8.1
The problem
When turning on the phone it goes to a black screen with HTC logo in the middle and 4 small triangles with exclamation point in each corner, from here I have to take out the battery to turn off the phone.
Holding Power+volume down brings up this screen as well so I can't get into bootloader/hboot using pwr+volume down, same thing with plugging in phone to usb
What I've been told
phone is s-off (I assume this means it has a some sort of custom recovery)
bricked when pulling out cable during RUU while trying to return to stock
What I've done/know
windows 8.1
plugged to USB 2.0 port
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
disabled driver signing security
install Android Universal Naked Driver in Win8 test mode
install Minimal ADB and fastboot utility
adb devices doesn't list any device
other adb command give "error: device not found"
fastboot command produces "waiting for device"
same with fastboot getvar cid
Thank you for any assistance you can give
stillsober said:
So I was given another HTC sensation recently but this time it's bricked and I don't know how to fix it.
I have a working HTC sensation phone to test that the driver work on win 8.1
The problem
When turning on the phone it goes to a black screen with HTC logo in the middle and 4 small triangles with exclamation point in each corner, from here I have to take out the battery to turn off the phone.
Holding Power+volume down brings up this screen as well so I can't get into bootloader/hboot using pwr+volume down, same thing with plugging in phone to usb
What I've been told
phone is s-off (I assume this means it has a some sort of custom recovery)
bricked when pulling out cable during RUU while trying to return to stock
What I've done/know
windows 8.1
plugged to USB 2.0 port
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
disabled driver signing security
install Android Universal Naked Driver in Win8 test mode
install Minimal ADB and fastboot utility
adb devices doesn't list any device
other adb command give "error: device not found"
fastboot command produces "waiting for device"
same with fastboot getvar cid
Thank you for any assistance you can give
Click to expand...
Click to collapse
you have to make the device being recognized from win 8.1
there a lot of guides here in xda on how to set up adb/fastboot on windows 8
then use again the ruu
I have 2 HTC sensations, one working one bricked.
the working one is recognised on the pc, fastboot etc working
the bricked one isn't
USB device not recognised when plugging in phone, in device manager in Android HTC device properties
Quote:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
I am trying to unlock Redmi note 6 pro but facing issue in fastboot. whenever I try 'fastboot devices' command, on 1st query it shows ID but on 2nd time query it shows '????????". when this happen, on phone screen messege appears as " press any key to shutdowd". pls check the attached image and tell me the solution. Have tried uninstall/reinstall driver, updated phone through phone's updater but nothing helps. phone always kicks out from fastboot mode. due to this problem mi unlock tool never detect my phone.
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
jwoegerbauer said:
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
Click to expand...
Click to collapse
Have done already these steps. will try changing PC tomorrow..
please read title and help
restore it with msm tool
how to connect the phone screen is black
If the screen is black it may already be in EDL mode. Plug it into a computer and check device manager for something like "Qualcomm HS-USB QDLoader." If that's there, you just need to get the MSM Tool for your model and make sure you have the right drivers.
If you can't get it into EDL mode, you will have to file a warranty claim with OnePlus, no other choice. Mess around with the buttons and see if you can get it to reboot or try the EDL key combo (hold volume up and down and while holding plug in the USB cable that's plugged into the computer). You don't have a chance of repairing it yourself if you can't get into EDL, end of story.
pc recognizing this Qualcomm HS-USB QDLoader in device manager but in msm tool it is showing n/a.and also in device manager it is showing triangle error on device.i am using official driver provided by msm tool poster.
Need some help unbricking (solved)
I bricked my OP9 doing some stuff today. It will not turn on, access bootloader, or anything. When I plug it into my computer, it makes a connecting sound, waits 10 seconds, then disconnect sound, then repeats the process. I tried using MSM...
forum.xda-developers.com
It's can help you
Well you're not the only one I guess. That happened to me as well. So perhaps, Alhamdulillah I can help you out
The screen still remains black that means your phone is in the EDL and you'll need to get it out of it and then get back to EDL again to use msm.
Anyway, hold the power + volume up + down all simultaneously for a while. It'll take you to the Fastboot mode. Don't worry, it definitely will take you to the Fastboot mode.
Then you can do the rest of the flashing as you wish
Hello I have a moto edge I had havoc on there and TWRP but I don't even really know what happened but I ended up bricking well not really bricked I can get in yo fastboot but the computer doesn't recognize the device I've switched cords computers tried every driver I can find I even went as far as to make my own edl cable to try to get it to edl more which one of the times playing with the edl cable i got it to say unknown device but haven't been able to since then if i boot to recovery it boot loops and same with just trying to boot I'm at a loss of what to try to do test points? To force edl? Please help
no need for EDL mode if you can still access fastboot. you can just install the drivers.
in fastboot mode format cache partition, that will fix TWRP boot-loop.
How to do that tho ?it doesn't recognize my device at all but it recognizes any other device I plug in
in device manager find the device with yellow triangle exclamation mark
Yeah no it's not there and when I can get it to make the noise it's from my home made edl Cable it says device descriptor error or something like that I'll look to see what it comes up as but I've installed drivers of uninstalled all the drivers I've got Qualcomm drivers I've got Motorola drivers I've got I've done all that or else I would have had it solved already I don't know what's going on with it and that's why I was asking about the edl test points because the computer won't read it whatsoever now it won't even get into fastboot but it won't get into edl neither I'm lost
try in linux lsusb (no virtual machine)
I had tried on Ubuntu with no luck it doesn't do anything at all now unless I edl Cable it and it says unknown USB device device descriptor request failed
does not sound like Ubuntu error message.
No that error is from windows I do not have access to my Ubuntu atm
Only heard about it when I recently tried to unlock the bootloader of my device.
I'm trying to boot into it but my phone only shows fastboot and recovery mode.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
Bootrom is unbrickable tiny bootloader that is reachable usually with test point on PCB board or by pressing both volume keys while connecting usb to PC.
same for preloader mode, that is yet another bootloader but in emmc storage, and therefore flashable/brickable. preloader is reached without any keys pressed, just by plugin usb cable.
Note that device must powered off completely. When you see the charging icon on phone screen, it's already powered on (in charging mode). It works best with battery disconnected.
Both modes require VCOM drivers you should install quickly when device is connected and visible in windows device manager for a certain time.