MTP isn't working on my PC. I tried on other PCs around here, and they're working.
I was using a custom rom before that, it was CAF for android 11. ( [ROM][11.0][STABLE] CAF Android 11 for RN8/8T [LA.UM.9.x][VANILLA/GAPPS] | XDA Developers Forums (xda-developers.com) )
But I'm suspecting it's windows fault. Recently, there had been an update, and when it was updating it ran into problem, but I eventually fixed, but the result was that installed programs and configurations were all reset.
I tried installing ADB, or some USB drivers I've searched for, but none of them worked. I've also tried updating the driver throug Devices Manager, but windows said it couldn't install it.
I'm trying to install another rom, but I have to solve this issue first.
[EDIT]
I formated windows and it's now showing up here. I have no idea what caused this, but the windows update probably messed up drivers or something.
LucasGMF said:
MTP isn't working on my PC. I tried on other PCs around here, and they're working.
I was using a custom rom before that, it was CAF for android 11. ( [ROM][11.0][STABLE] CAF Android 11 for RN8/8T [LA.UM.9.x][VANILLA/GAPPS] | XDA Developers Forums (xda-developers.com) )
But I'm suspecting it's windows fault. Recently, there had been an update, and when it was updating it ran into problem, but I eventually fixed, but the result was that installed programs and configurations were all reset.
I tried installing ADB, or some USB drivers I've searched for, but none of them worked. I've also tried updating the driver throug Devices Manager, but windows said it couldn't install it.
I'm trying to install another rom, but I have to solve this issue first.
Click to expand...
Click to collapse
but you should disable drive signature befor all
milatave said:
but you should disable drive signature befor all
Click to expand...
Click to collapse
Is this something from the computer, right? It's weird, because I never had to change this stuff before. Before the update, windows was recognizing my phone normaly, but after, it didn't. But thanks for the reply, though. Things are working normaly after I formated.
LucasGMF said:
Is this something from the computer, right? It's weird, because I never had to change this stuff before. Before the update, windows was recognizing my phone normaly, but after, it didn't. But thanks for the reply, though. Things are working normaly after I formated.
Click to expand...
Click to collapse
yes, mybe that update was a security patch for windows, usually adb and mtp not work correctly if drive signature is enable
Related
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs
I had previously rooted my OP3, but accidentally updated it with the OTA open beta update, losing twrp recovery. I'm finding it incredibly difficult to flash twrp again to reroot.
The bootloader is still unlocked, and USB debugging is on with OEM unlocked, but I keep getting FAILED messages when I attempt to flash. "fastboot devices" shows the device (as a series of numbers).
I've tried using the OnePlus3&[email protected]_radaideh, but when attempting to flash it shows the below and then fails:
error: no devices/emulators found
I couldn't get it to work on my computer at home (win10) and read about problems with the OP3 drivers being unsigned (even with driver enforcement off). I'm also struggling on win7 - for some reason, the driver is listed in the Device Manager under the hardware group TP-LINK Android Phone and I can't get it to work using the OnePlus Android Bootloader Interface (under OnePlus, Inc.) or the Android Bootloader Interface (under Google, Inc.).
Could anyone suggest anything I should try?
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
emuandco said:
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
Click to expand...
Click to collapse
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
justmast said:
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
Click to expand...
Click to collapse
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
emuandco said:
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
Click to expand...
Click to collapse
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
justmast said:
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
Click to expand...
Click to collapse
Yep I was here aswell. Boot into driver signature mode and install the proper drivers. If you connect your device you can change the drivers. I don't have a PC next to me so I can't give you exact steps. The unbrick tool has the proper drivers, just follow the first few steps of that instruction to get it to show up as Qualcomm or something else as long as it isn't Kedacom.
Hey, after updating from CB1 to Oxygen OS 9.0.2 i can't access the device (OP3) via fastboot anymore. I have installed all needed drivers and adb is working as it should.
What is strange is, that my device is always shown just as "Android " with a "!" next to it.
Device has been updated via official full update (Downloaded w oxygen downloader - full update)
I have already tried to reinstall the device in the device manager
I have completely reinstalled all ADB/USB drivers
USB debugging is enabled
Has anymone having the same issues? Under CB1, everything was fine...
Have you tried different USB ports? Even other PC's?
I had the same issue, but managed to get it working on another laptop.
bartovitc said:
Have you tried different USB ports? Even other PC's?
I had the same issue, but managed to get it working on another laptop.
Click to expand...
Click to collapse
It was working on a linux based system started from a usb stick in the end, but using the same computer. After long time of research I found out, that it is a problem caused by windows 10, not wanting to install the right drivers. Aparently you only have few options to fix this. But as it works with a usb linux system, I have a "fix" now
NeroTheDawn said:
It was working on a linux based system started from a usb stick in the end, but using the same computer. After long time of research I found out, that it is a problem caused by windows 10, not wanting to install the right drivers. Aparently you only have few options to fix this. But as it works with a usb linux system, I have a "fix" now
Click to expand...
Click to collapse
Sounds like ADB/Fastboot drivers aren't installing properly. You have looked up the right way to install those drivers on Windows 10 haven't you? by disabling driver signing enforcement:
https://ph.answers.acer.com/app/ans...windows-10:-disable-signed-driver-enforcement
ADB/Fastboot works for me and a lot of other people.
It's not a OP3 problem.
Good luck.
It's not a OP3 problem.
Good luck.
Click to expand...
Click to collapse
Check my last reply. I know that its not a OnePlus specific problem, but when I faced this problem the first time, it was right after the Update to pie - which was a coincidence.
Thanks for the advice with the driver signing enforcement, I will try that!
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Phat Phreddy said:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
Click to expand...
Click to collapse
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
mlcattini said:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Click to expand...
Click to collapse
But I said its working on ADB..
RollDload said:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
Click to expand...
Click to collapse
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Phat Phreddy said:
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Click to expand...
Click to collapse
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Phat Phreddy said:
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Click to expand...
Click to collapse
then it was definitely a problem in the driver.