I am trying to use the msm tool to unroot my OnePlus 8t tmobile variant. Using the MSM tool I have run into a few different problems.
1. Drivers. When my phone is in edl mode plugged in to my computer, device manager recognizes it as usb_bulk. I tried using the provided .cab file to update windows Qualcomm drivers but windows could not ever find the files when updating. I found on another forum a automatic installer.
2. Although it now says Qualcomm 9008 windows says that driver digital signature is not recognized or corrupted. However the MSM tool does finally show COM 5 and when I plug in my device is stuck at waiting for device.
I'm pretty stuck right now and any information to help me out would be appreciated.
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
mreese14 said:
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
Click to expand...
Click to collapse
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
gforceriders said:
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
Click to expand...
Click to collapse
Worked for me, thank you!
Related
I have problem with my OPO.
I try to install TWRP 2.8.6.0 but after that my phone doesn't boot. Nothing work. I hold power button for 2 minutes and nothing.
I do everything like in this guide but it doesn't work. http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I connect my bricked phone and Windows see it "other devices- unknown device"
I done cmd commands, update driver, select Qualcomm 2012/widnows8/qcmdm/ QDLoader 9008 and after that I have error " Windows found driver software for your device but encountered an error while attempting to install it. This device cennot start(Code 10)"
And it is my problem. I stopped at point 2b in the Guide becouse I can't install drivers.
here is video of that. https://drive.google.com/open?id=0B9...G8tbnNES2VZWG8
Please fast help, becouse I really need this phone next weekend.
Please, can someone help me?
Rebeluch said:
Please, can someone help me?
Click to expand...
Click to collapse
when i bricked my oneplus one, i had similar issues. I had to reinstall windows in order to make it work.
hellcat50 said:
when i bricked my oneplus one, i had similar issues. I had to reinstall windows in order to make it work.
Click to expand...
Click to collapse
Do you pluged phone into USB port and computer can't see it?
Do you reinstalled system to Windows XP?
Rebeluch said:
Do you pluged phone into USB port and computer can't see it?
Do you reinstalled system to Windows XP?
Click to expand...
Click to collapse
I used windows 8.1
reinstalled windows 8.1 on a new partition
It's now a long time ago so i can't quite remember what problem exactly i had, but I know that it didn't worked and i reinstalled windows and it worked.
Actually one month after I bought my oneplus one i bricked it
have u tried disable windows driver signature enforcement? becoz after windows 7, driver that doesnt have digital signature are not installed unless u disable the enforcement
MrxSiN said:
have u tried disable windows driver signature enforcement? becoz after windows 7, driver that doesnt have digital signature are not installed unless u disable the enforcement
Click to expand...
Click to collapse
Yes, I do this in Advanced restart options and click F7. And windows still can't see phone.
Hello,
My new P11 tablet is stuck in fastboot mode after I flashed it using Lenovo Rescue and Smart Assistant tool to the latest version.
I tried to do it several times but it is still the same. The flashing completes successfully and it boots in fastboot mode after that.
Any ideas how to fix this?
Thanks in advance!
VVV1981 said:
Hello,
My new P11 tablet is stuck in fastboot mode after I flashed it using Lenovo Rescue and Smart Assistant tool to the latest version.
I tried to do it several times but it is still the same. The flashing completes successfully and it boots in fastboot mode after that.
Any ideas how to fix this?
Thanks in advance!
Click to expand...
Click to collapse
I managed to fix it using QFIL. I had to install QPST and run QFIL from "C:\Program Files (x86)\Qualcomm\QPST\bin". The download fails the first time, but it works the second.
The same as in this video -
Hi,
I have the same issue and I tried QFIL however the device is not detected. Could you explain more in details how you managed to fix this?
Thanks in advance
Edit: Never mind, considering I just received it yesterday and this is clearly a bug with Lenovo's app, and that before this happened I couldn't get the tablet to be detected by fastboot (only adb), I'll return this one to Amazon. I've successfully unlocked the bootloader on my other one so it seems something was wrong with this particular one.
Hi there. They have left me a tablet with the same problem but I can't get QFIL to detect it for me. I can't install Qualcomm drivers for it.
Thanks and sorry for my English.
arturito109 said:
Hi there. They have left me a tablet with the same problem but I can't get QFIL to detect it for me. I can't install Qualcomm drivers for it.
Thanks and sorry for my English.
Click to expand...
Click to collapse
same here
VVV1981 said:
I managed to fix it using QFIL. I had to install QPST and run QFIL from "C:\Program Files (x86)\Qualcomm\QPST\bin". The download fails the first time, but it works the second.
The same as in this video -
Click to expand...
Click to collapse
thankyou so much!! It's work at the first time (I choose metabuild, rom ver TB-J606F_S120184_210520_ROW - My laptop is dell Latitude E5530 - Win 7 SP1 64bit)
raiso said:
thankyou so much!! It's work at the first time (I choose metabuild, rom ver TB-J606F_S120184_210520_ROW - My laptop is dell Latitude E5530 - Win 7 SP1 64bit)
Click to expand...
Click to collapse
im always fail, any help, what version of qpst you use ?
$ fastboot set_active a
did the trick for me!!
I tried following the "Global/US OnePlus 9 Unbricking Guide" but I get stuck at the drivers part and while I can see that my phone is connected as a device to my PC I cant seem to install the drivers or get access to root folders (which I assume is connected). Ive tried using software to download the drivers for me and I've tried following the notes that came with the qualcom drivers file. The only thing I can do is boot my phone into fast boot but every option from there just leads to "phone corrupt... cant boot" error message
casualBricker said:
I tried following the "Global/US OnePlus 9 Unbricking Guide" but I get stuck at the drivers part and while I can see that my phone is connected as a device to my PC I cant seem to install the drivers or get access to root folders (which I assume is connected). Ive tried using software to download the drivers for me and I've tried following the notes that came with the qualcom drivers file. The only thing I can do is boot my phone into fast boot but every option from there just leads to "phone corrupt... cant boot" error message
Click to expand...
Click to collapse
use msm download tool to unbrick your phone
just follow the instructions its works i used it 3 times for my 9
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com