Develop Bugs

[Q] HTC M8 unbrick help

hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,

yes
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.

Hi Konsolen,
Thanks for the reply. I connected the phone, and qualcom hs usb showed up and i have added some screenshot , but i dont exactly understand your last comments qualcom bootloader driver and so on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
[/IMG]

i added some picture, but where do i find the bootloader driver?
konsolen said:
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Click to expand...
Click to collapse

It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.

Gkhnnn said:
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
Click to expand...
Click to collapse
Does the M8's screen come on? Any charge LED (and what color)?
Very key detail (among others): what did you do to get the phone into this condition?

m8
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
i installed cm12 but i couldnt use my navigation as the ohone couldnt find any sattelites.
so i tried several firmwares and after changing to supercid i managed to update firmware and hboot. after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp but it freezed and after a forced restart i saw red triangles on each corner and has never seen anytging on scrreen since. always black.

Gkhnnn said:
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
Click to expand...
Click to collapse
Red LED? I asked what color before.
Gkhnnn said:
after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp
Click to expand...
Click to collapse
That is remarkably vague. What commands exactly?

m8
​
sorry, the color is orange.
i'm on phone now and can send the commands i have tried
but the codes never worked but i believe i managed to delete a wrong partition .
when onnecting Phone to pc, 14 disk partition shows up, only 4-5 of them has files inside.

konsolen said:
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Click to expand...
Click to collapse
Device is always in the device manager. If i remove the driver it shows up as qusb bulk with question-mark.
I tried to download several driver but i couldnt get the device in fastboot or download mode.
I look forward to your link
Thanks

m8
redpoint73 said:
Red LED? I asked what color before.
That is remarkably vague. What commands exactly?
Click to expand...
Click to collapse
TWRP after installing a rom giving me "unable to mount data" all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37
But i heard from somebody that these codes were for HTC M7 and not M8

What carrier or region (CID)?

m8
redpoint73 said:
What carrier or region (CID)?
Click to expand...
Click to collapse
Its a Verizon , i live in Europe, but i got the phone for free from company i worked in.
This is a pic i took for a weeks ago.
[/IMG]

Why not just try and flash the RUU?
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
That might at least get it working again, as you can do it via a microSD card

m8
i have now downloaded the standalone zip and copied that to sd card, renamed to 0P6BIMG.zip
as the screen doesnt show anything, i have powered on with vol down, i assume the hboot ask for vol up for continue to installing, now i wait but i dont thing anything happens
The exe RUU says "USB error, could not connect to the phone"

m8
When connecting the phone to pc, as said before 14 disk partition opens up, and here are the folder which contains the files showed
[/IMG]
[/IMG]
[/IMG]
[/IMG]

m8
When the phone connected to my pc , its shows in device-manager:
PORTS: Qualcomm HS-USB Diagnostics 9006 (COM12)

Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...

EddyOS said:
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
Click to expand...
Click to collapse
Screen not coming on, and device showing as Qualcomm on PC is a bad sign. Agree it might not be recoverable.
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
But extreme care needs to be taken before manually messing with partitions like the OP did. A single mis-typed character can be disastrous. And there are safer ways to have recovered from the fairly common internal storage issue (format with computer or in TWRP).

redpoint73 said:
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
Click to expand...
Click to collapse
That someone is the same one
And what I know ... that's a hard brick .. corrupted partition

Unable to use fastboot miui P beta

I just flashed the beta for Android p of rn5pro global. Everything works. But at the moment to go into fastboot, it goes but typing fastboot devices keep showing waiting for device. I unplugged it and try again fastboot devices using the redmi note 4 and mi 3 instantly. It only happen with the r5 any ideas ? I tried using the mi flash tool also it didn't recognize it.
What I want I to be available to use fastboot again. To flash the recovery and root it.

Place some images for the community to see how Android P is on our device.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And how exactly is that gonna help in any way??? sarcasm

Yesterday i've used fastboot just fine on pie

Make sure to install Redmi note 5 pro device driver

Jctatis said:
I just flashed the beta for Android p of rn5pro global. Everything works. But at the moment to go into fastboot, it goes but typing fastboot devices keep showing waiting for device. I unplugged it and try again fastboot devices using the redmi note 4 and mi 3 instantly. It only happen with the r5 any ideas ? I tried using the mi flash tool also it didn't recognize it.
What I want I to be available to use fastboot again. To flash the recovery and root it.
Click to expand...
Click to collapse
check for USB 2.0 instead of 3.0

lcdkhoa said:
check for USB 2.0 instead of 3.0
Click to expand...
Click to collapse
Tried this didn't work. I funny think is that phone on gr find. I when I type reboot fastboot it stop working. The phone appear after test point. I but when I go manually from os to fastboot the oh flash tool doesn't recognise it. I

edi194 said:
Yesterday i've used fastboot just fine on pie
Click to expand...
Click to collapse
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working

SunilSuni said:
Make sure to install Redmi note 5 pro device driver
Click to expand...
Click to collapse
The drivers been always there. It just stooped working after updating to this rom. I mean the phone works I'm replying from it. Gonna try from another laptop a clean install on drivers

Jctatis said:
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
I've used fastboot mode with Pie on MIUI (both Xiaomi.eu and Global Beta) and it was fine like always, install XDA's minimal ADB&Fastboot, always used It for all of my devices

Jctatis said:
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
No, that's not possible, probably the new bootloader has a lot of bugs and that's the reason why you pc can't detect the phone, you have 3 options: reinstall everything in your PC (I mean drivers, MiFlash, etc etc [Windows is Windows you know..] and try with differents cables, ports etc), try with differents PC's or stay in Pie until Xiaomi fixes the bugs.

onliner said:
No, that's not possible, probably the new bootloader has a lot of bugs and that's the reason why you pc can't detect the phone, you have 3 options: reinstall everything in your PC (I mean drivers, MiFlash, etc etc [Windows is Windows you know..] and try with differents cables, ports etc), try with differents PC's or stay in Pie until Xiaomi fixes the bugs.
Click to expand...
Click to collapse
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no recognize neither with the flash mi tool. when is in the "miAs$istant it show adb driver on the device manager" but when is in fastboot it doesn't even sound or show drivers.
tried different cables.
i guess the only option now is wait for and update that may fix the fastboot. or maybe my fastboot is blocked dunno... anyway thanks for the time and the asistantance :good:

Jctatis said:
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no re... :good:
Click to expand...
Click to collapse
Just do as I say :
Open device manager,you will find that a driver Android is missing (which wasn't the case previously on fastboot) .Install the drivers from the link in this video description: https://youtu.be/eQSAD8tNOaA
Do the fastbooty thing....
Thank me later

You can make a bootable USB with Ubuntu and boot it from the USB without installing. Then install adb and try and see if it works. That way you can confirm if it is the phone or your windows that is causing issues.

You went to fastboot from recovery? It doesn't work. I had the same problem - full shutdown and then boot with power and volume down.
Wysłane z mojego Redmi Note 5 przy użyciu Tapatalka

Guys I have problem with adb fastboot after flash this leaked firmware.
I am stucked with this release.
CMD failed the flash of TWRP for the package size and it recognize my RN5 random.
Another users have this issue with latest release.

Jctatis said:
Is there a possibility of the fastboot been or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
For me it stopped working on xiaomi.eu firmware, reflashing to global beta worked

Jctatis said:
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no recognize neither with the flash mi tool. when is in the "miAs$istant it show adb driver on the device manager" but when is in fastboot it doesn't even sound or show drivers.
tried different cables.
i guess the only option now is wait for and update that may fix the fastboot. or maybe my fastboot is blocked dunno... anyway thanks for the time and the asistantance :good:
Click to expand...
Click to collapse
USB debugging option enabled? If yes, then fastboot commands won't work. Try to disable it and then execute commands. It should work. I'm in the same boat as you when fastboot suddenly stopped working. Only thing I did is to enable USB debugging. So I disabled and all fine. I'm on 9.3.25 Miui Pie btw. Try it. It may or may not work..but that's how it works on my device. Wierd af

Thank for all the replies I gonna try all the options I didn't try Joe new ones you guys mention, the ubuntu one guess is os or a virtual machine

Same problem after latest update of Miui Pie , test tomorrow with my old PC , I have the doubt if the problem is my new Notebook Asus TUF FX504 GM , USB 3.0 break the fastboot.
I have used same driver of the old PC and same method.
Fastboot work but same flash error "the package size bla bla bla......"and disconnect fastboot connection random.

HD1907 won't connect to PC (TRIED EVERYTHING)

Phone will only connect to adb in bootloader mode and shows as (unauthorized) despite USB debugging enabled. Tried revoking all but did not fix.
Won't prompt for file transfer or USB debugging. Nothing even shows up in device manager when phone is booted into Android.
Tried 4 cables and 4 computers. Tried changing default usb mode.
Bootloader is unlocked.
I used to transfer files all the time but not it randomly does not connect.

You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers

HueyT said:
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
Click to expand...
Click to collapse
I never get the popup. It is as if the phone is connected to the wall when I plug it into my computer. EXCEPT when I am in booted into recovery and it says it is unauthorized.
adb devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not detected in fastboot mode at all.
The only option I see is to try factory reset via recovery.
I see this in recovery

Now I literally can't get anything to show in device manager or adb/fastboot.
I have tried every driver and guide under the sun. Disabled driver signature enforcement. Ran the convert MSM and the regular 1907 MSM, didn't fix.
No matter how many times I install the OP drivers or Google nothing even shows in device manager even when "Show hidden devices" is checked. This picture I am in the system with USB debug and OEM unlock enabled set to file transfer (Although it never prompted me for anything, in fact USBDeview doesn't show anything when I plug in the phone):

So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

HueyT said:
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)

Jonnyswboy said:
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Click to expand...
Click to collapse
U need Qualcomm USB 9008 drivers

HueyT said:
U need Qualcomm USB 9008 drivers
Click to expand...
Click to collapse
I successfully ran the MSM several times.

After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files

HueyT said:
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
Click to expand...
Click to collapse
After above patched MSMtool I cannot connect to PC via fastboot. I just bought a Pixel 6, but thanks for the help.

Question Bricked phone, looking for help!

I will literally pay someone to help me out here at this point.
I have been trying to unbrick my device for the past 2 days now, I have no access to Fastboot or the Recovery mode, just EDL mode. I have been trying to use MSM to unbrick the device. I have tried every version of MSM (EU, Global and India), my version of the phone is EU, I have tried multiple different variants of the Qualcomm driver, none have worked. I'm at the situation where its telling me "Param Preload, Device not match image". I have tried turning off Sha256 Check and turning on lite firehouse, none have worked. I have looked everywhere but can't seem to find any solution for me
I bricked it by flashing something onto the phone, where it required you to flash certain files, Wipe the phone and then flash more files, but I forgot to wipe the device before flashing the rest of the files, and it hasn't turned on since, I am starting to wonder if there is any way at all at fixing this or is it gone for good. i do not want to spend another $900 for this phone, and repair service is my last option, I am going to see if anyone can help me this on e last time before I file for repair service, as I do not want to pay the repair service
I would really appreciate if anyone could even give me a clue on what to do here as I am out of options, thank you very much for reading anyways even if you weren't able to help
I have also put this on XDA in hopes someone there could help me too!

HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !

epcwong said:
HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !
Click to expand...
Click to collapse
If I tick Sha256 then it gets stuck at some "Sahara communications" or something like that, I can't remember I'm not home rn. Any other options?

It seems that you've installed too much different drivers on your computer. Uninstall all android drivers and only install the OnePlus_USB_Drivers_Setup.exe and QDLoader HS-USB Driver_64bit_Setup.exe. Then give it another try !

Another option is that because the EDL mode only holds for may be 5 to 10 seconds, you have to get the msm tool ready with the Sha256 check turn on but "don't use the lite firehouse" also with "start" turn all standby. Once you've got all the above ready, then put your phone into EDL mode and plug into the computer immediately (in a very uick action), and try it again !

Try the option first before revised the drivers ! If I remember right the "Sahara communications" is caused due to the EDL mode is off when your plug into the computer too late. The timing is very important that's why it showed communication error. Try again !

Launch the MSM tool (use the Win7 one) Choose "Others"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ensure you select the EU from the top "Target" dropdown:
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.

djsubterrain said:
Launch the MSM tool (use the Win7 one) Choose "Others"
View attachment 5677693
Ensure you select the EU from the top "Target" dropdown:
View attachment 5677699
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.
Click to expand...
Click to collapse
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?

Aphriz said:
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?
Click to expand...
Click to collapse
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that

djsubterrain said:
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that
Click to expand...
Click to collapse
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great

Aphriz said:
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great
Click to expand...
Click to collapse
It sounds like you're doing something wrong when connecting device /entering EDL mode at the correct time. or you haven't got Proper drivers installed,. Keep trying different configurations bro you'll get it eventually. If you haven't restarted PC since installing drivers give that a go. That stopped errors for me.

Easy way to catch EDL mode on your phone is to have your phone completely shut off and not connected. Get MSM set up how it should be and go ahead and hit start. It will begin looking for your phone. Connect your phone to the USB that is connected to your computer while holding down both volume buttons.
No fuss or trying to time anything. It will start your phone and catch the EDL mode.
Won't solve your problem, but it's an easy way to catch EDL every time.

Deleted

After all the comments from the above members, your phone should work with the msm tool. If still not, which means you didn't catch the right timing when connect the phone to the computer. Last option, leave your phone for 3 to 4 days until the phone battery is completely drained off. Then try to re-connect your phone again with the msm tool. Once your phone is connected, it should start the firmware download automatically. Give it a go !

I would also check to see if the drivers work if you disabled driver signing in Windows, there were some issues previously with the certification:
After that, try installing the driver again, just in case that's what is stopping them working.
Check it with another cable also, I've honestly had a problem with one USB cable and not another, it's rather fickle but once you confirm what setup works, just use that in future.
Try on another computer/laptop also if you have one but install those drivers before you even start. You should do that with any USB device, install the drivers first THEN attach it.

Pixel experience ( Usb Not recognizing in recovery mode )

Pixel Exp USB not working
So i want to install pixel experience on my one plus 7T and I did all the steps until i reached the side loading but the issue is when ever I enter pixel experience recovery mode my computer doesn’t recognize my phone and there is a triangle on it in device manager but in bootloader or when booted the connection works fine.
- i have installed google drivers
- usb is working fine

Install Qualcomm driver
https://gsmusbdriver.com/install-qualcomm-usb-driver

I'm currently having this same issue with the Qualcomm Drivers installed. Any other suggestions?

Azu1e said:
I'm currently having this same issue with the Qualcomm Drivers installed. Any other suggestions?
Click to expand...
Click to collapse
Try reinstalling USB and Qualcomm drivers with Windows in Test Mode. Sharing a screenshot of you Device Manager could help us help you also.

Did you find a solution? I am facing the same issue.

- Check the USB cable being used
- Try another USB port on the computer
- LIke other user mentioned boot your windows into recovery then start the windows with disabled driver signature verification mode then install the drivers (For me Oneplus drivers itself worked fine) this will just make sure that ur computer recognizes your android rest is left to what you have fiddled on the ROM. worst case just download the stock ROM with MSM tool and reset your entire phone and continue the experiments.

Robinlong said:
Try reinstalling USB and Qualcomm drivers with Windows in Test Mode. Sharing a screenshot of you Device Manager could help us help you also.
Click to expand...
Click to collapse
Hello havent had time to mess with my phone. Bellow I have attached a copy of how my device manager looks like when in the pixel experience recovery mode. When trying to update the drivers these are the options that I get. Regardless of what I click on for the model option none of them seem to work. I am kind of stuck here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Azu1e said:
When trying to update the drivers
Click to expand...
Click to collapse
Make sure Windows is in Test Mode or Disable Integrity Check. Then, try reinstalling the Oneplus USB drivers from here first and lastly Qualcomm drivers from here or from here.
I think that in Recovery Mode the Device should look like this:

Robinlong said:
Make sure Windows is in Test Mode or Disable Integrity Check. Then, try reinstalling the Oneplus USB drivers from here first and lastly Qualcomm drivers from here or from here.
I think that in Recovery Mode the Device should look like this:
View attachment 5918033
Click to expand...
Click to collapse
I tried this again using the three links provided. I made sure to reset my computer by disabling the Integrity and being in test mode. Still no luck. I have no idea where I went wrong. I've followed all the instructions from the forums and made sure to read every step carefully before attempting. As and alternative I tried to run TWRP and install the rom from a usb plugged into my phone. Even this has been failing with both Pixel experience and Lineage OS. At the moment I have flashed back to 10.0.13 Global OnePlus 7t with the pixel experience recovery image. Any further help or advice is much appreciated.

Azu1e said:
I tried this again using the three links provided. I made sure to reset my computer by disabling the Integrity and being in test mode. Still no luck. I have no idea where I went wrong. I've followed all the instructions from the forums and made sure to read every step carefully before attempting. As and alternative I tried to run TWRP and install the rom from a usb plugged into my phone. Even this has been failing with both Pixel experience and Lineage OS. At the moment I have flashed back to 10.0.13 Global OnePlus 7t with the pixel experience recovery image. Any further help or advice is much appreciated.
View attachment 5918571
Click to expand...
Click to collapse
Could using windows 11 be causing a problem?

Any suggestions I have tried installing the drivers on Windows 10 and 11. I have tried using different computers but still no luck.

Azu1e said:
Any suggestions I have tried installing the drivers on Windows 10 and 11. I have tried using different computers but still no luck.
Click to expand...
Click to collapse
Can you define "no luck"? What error or problem are you having?
If you are still getting the yellow exclamation in Device Manager, you could try clicking "Update Driver" and browsing to the folder where you unzipped the drivers.
Also there are many solutions you could try from this thread.

I've tried following the instructions on that thread and have been unable to update the drivers from the disk. The only inf file available to me is the autorun file in the OnePlus_USB_Drivers_Setup folder. All of these issues are when running the phone in the pixel experience recovery mode.
View attachment 9rkonok9bdv81.webp