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.
Related
Good morning, please is possible that after monthes of birth for this phone aren't these drivers? please, anyone has the way for doing this? thanks
myabc said:
Good morning, please is possible that after monthes of birth for this phone aren't these drivers? please, anyone has the way for doing this? thanks
Click to expand...
Click to collapse
It's no Moto G-problem, it's Windows 8.1. This worked for me. But you have to connect your phone to an USB 2.0-port.
Firetribe said:
It's no Moto G-problem, it's Windows 8.1. This worked for me. But you have to connect your phone to an USB 2.0-port.
Click to expand...
Click to collapse
i have not intel driver installed and i don't understand from where i have to start.
i ask you please:
1. is this guide even for me that i haven't intel device motherboard?
2. from where i must start? (there is not indication for step numbers in that guide
thanks
This worked for me!
myabc said:
Good morning, please is possible that after monthes of birth for this phone aren't these drivers? please, anyone has the way for doing this? thanks
Click to expand...
Click to collapse
This worked for me!
After you install this, it'll have two programs listed in control panel. Motorolla Mobile Drivers Installation & Motorolla Device Manager.
You can safely remove motorolla device manager and have the drivers
If @deej_roamer's advice didn't already do the job:
It doesn't matter which mainboard you have, what matters is the manufacturer of your USB-Port. If in device manager you have the mentioned Intel(R) USB 3.0 eXtensible Host Controller, then you have to change drivers to get fastboot working. At least, that was the case for me.
You can start in the guide with this passage:
Code:
Install your default device drivers (For HTC, Install the HTC Sync Manager, For Sony, Use the ones you got in flashtool, etc)
If you are using Windows 8.1, use this for HTC drivers.
deej_roamer said:
This worked for me!
After you install this, it'll have two programs listed in control panel. Motorolla Mobile Drivers Installation & Motorolla Device Manager.
You can safely remove motorolla device manager and have the drivers
Click to expand...
Click to collapse
thanks... finally works for me, too
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Jjleininger said:
Bricked my OPO somehow flashing cosmic OS. I get the load screen and thats it. no recovery and no fastboot. I've found a million tutorials on how to fix a hard brick, but all of them show the opo in device manager as qualcomm. I've downloaded some drivers but not sure what to do from here to get that to read qualcomm so i can start the unbrick process. any help or suggestions?
Click to expand...
Click to collapse
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Mr.Ak said:
Forget all the other guides...
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Just use this one and the drivers included.
It will easily restore back to cm11s(stock KK),after that you can flash MM(Cos13.1x) if you want through fastboot.
The key-point is you need to find one of Xp systems around you and then use that because win8/10 somehow makes driver signature a headache and takes more time to set-up.
Click to expand...
Click to collapse
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Jjleininger said:
I'll check this out this evening. I'm playing hell trying to get drivers working. All the write ups I see show the opo saying qualusb in device manager upon connection and no matter what I do I can't get mine to. I've got an old laptop running win7 maybe I'll give that a shot. This would be done and over if it showed as qualusb in "ports" instead of adb interface in "usb".
Thanks for the info.
Click to expand...
Click to collapse
Remove all other drivers.
Again,XP is advisable,I don't think it takes long to dual boot XP alongside.
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Jjleininger said:
Downgraded to Windows 7, now the phone shows up as Qualcomm, but still can't get the program to recognize. Bootable xp drive failed, will try disc when I get home.
Click to expand...
Click to collapse
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Mr.Ak said:
Sorry for late reply.It should be "Qhs_bulk" or "qualcomm_diagnostics9006" not just "Qualcomm".
Just try refreshing through Ebus button and make sure you're using original 1+ cable and try changing ports likewise.
I'd still say try with XP,use rufus to make a bootable usb and if you're good to go.After you setup the drivers(from thread link I gave you or from the zip itself), make sure you run the program as an administrator.
Click to expand...
Click to collapse
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Jjleininger said:
I've got it so it says qualcomm hs-usb qdloader 9008. I'll continue refreshing and swapping ports. I've used Rufus and four whatever reason it's giving me bsod when booting via USB. I'll give a disc a try.
Click to expand...
Click to collapse
Your motherboard supports usb booting?
Mr.Ak said:
Your motherboard supports usb booting?
Click to expand...
Click to collapse
Yessir, just went from windows 10 to 7 via USB boot.
Jjleininger said:
Yessir, just went from windows 10 to 7 via USB boot.
Click to expand...
Click to collapse
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Mr.Ak said:
You can use other software than rufus for XP but that'll make the process too slow,atleast while installing XP.
But a CD always does the work perfectly for XP!
Click to expand...
Click to collapse
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Jjleininger said:
I tried a straight jump from win 10 to xp with a disc and the installation option was grayed out, maybe with 7 it'll give me that option back. I'll burn a new one this evening and give it a go.
Click to expand...
Click to collapse
Dual boot?
I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.
praik96 said:
I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.
Click to expand...
Click to collapse
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?
I'm using windows 8.1 64bit version.
Mr.Ak said:
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?
Click to expand...
Click to collapse
When i press power button + vol. up for 10sec the windows recognizes the device but shows it as Unknown Device and then the Driver Update is not being done. What should i do?
praik96 said:
What should i do?
Click to expand...
Click to collapse
Did you even read my question?
Sent from my A0001 using Tapatalk
faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot
Kartike said:
faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot
Click to expand...
Click to collapse
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk
Mr.Ak said:
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm using windows 8.1, earlier i mentioned it in the title.
praik96 said:
I'm using windows 8.1, earlier i mentioned it in the title.
Click to expand...
Click to collapse
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk
Mr.Ak said:
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?
praik96 said:
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?
Click to expand...
Click to collapse
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
You should download One Plus USB drivers.
If you prefer you should use One Plus Toolkit.
Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.
praik96 said:
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.
Click to expand...
Click to collapse
Youtube
Sent from my A0001 using Tapatalk
Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Tip1: Use correct usb cable.
I thought the error was is usb drivers but it seems that the error was in usb cable. I lost my oneplus usb cable quite a while ago and was using third party usb cable for data transfer and charging. Tried to connect the bricked OPO with that cable only.
Just ought to try connected with different cable here used Amazon Basics micro usb cable and VOILA!!! The drivers were automatically installed by windows this time.It worked on current windows 8.1. Dont know it was luck or really dumb choice of USB cable.
But thank you very much for helping me out.
Whenever I connect my phone to usb an error is displayed on screen. Please see the screenshot. I have a dual boot pc with ubuntu 17.04 and windows xp. The error occurs on both os. In xp the driver is not installed and an error is displayed stating the specified service doesnot exist. I have tried changing cables and ports but still the same. My phone is unlocked exynos version with android 7 installed.
sixline said:
Whenever I connect my phone to usb an error is displayed on screen. Please see the screenshot. I have a dual boot pc with ubuntu 17.04 and windows xp. The error occurs on both os. In xp the driver is not installed and an error is displayed stating the specified service doesnot exist. I have tried changing cables and ports but still the same. My phone is unlocked exynos version with android 7 installed.
Click to expand...
Click to collapse
Install Windows 7 or newer
*Detection* said:
Install Windows 7 or newer
Click to expand...
Click to collapse
Dear, this is also happening on linux which is my primary os. I dont want to install windows 7. Please avoid such answer to anybody as this is not a solution.
sixline said:
Dear, this is also happening on linux which is my primary os. I dont want to install windows 7. Please avoid such answer to anybody as this is not a solution.
Click to expand...
Click to collapse
It's happening because there is no driver, install 7 or newer, and don't call me dear
*Detection* said:
It's happening because there is no driver, install 7 or newer, and don't call me dear
Click to expand...
Click to collapse
Ok Mr. Detection but you fail to understand that its also not working on linux which is my primary os.
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