Related
Hello guys!
I've got a bit of a problem here, because now my mobile refuses to connect with activesync and therefore making it impossible to flash it.
I read the readme in the cid bypass folder, and didn't quite understand it, but as keen as I was on getting a new rom I did it all wrong.
I actually copied the cid bypass folder to my sd-card and ran haret.exe from the phone. A friendly penguin appeared along with some green text, and it rebooted and went black. I waited for a while, but had no patience so I rebooted it again. But after this it has been impossible to connect it with activesync! I've tried hard reset and different computers but nothing works!
I'm hoping someone on this forum can help me!
best regards
Try this.
turn your phone off and press the camera button in then plug it into the USB port
you should get a multi color screen. If you do then you can flash.
But go here http://forum.xda-developers.com/showthread.php?t=330909
Go to where it says EDIT and follow what it says.
Oh and when a dos box opens up and ask you things just press the return key each time.
good luck
hey man, I tried reflashing the original rom to my vox, with the manualstyle sd card flash. So now it's flashed with the original rom, but still activesync doesn't work! anybody have an idea on how to make this right?
somebody tried running haret.exe from their phone, then flashing the Uspl with ruu flasher and then flash the new cooked rom?
My phone is not able to connect for flashing while in black state (after running harET), is it stupid of me to reboot it and start it by holding camera button while plugging it in to the computer? and then flash it with the ruu?
somebody please help me?
go into settings then connections then more till you see USB to PC
in there un-tick the box which says enable advaned network.
zipuz said:
somebody tried running haret.exe from their phone, then flashing the Uspl with ruu flasher and then flash the new cooked rom?
My phone is not able to connect for flashing while in black state (after running harET), is it stupid of me to reboot it and start it by holding camera button while plugging it in to the computer? and then flash it with the ruu?
somebody please help me?
Click to expand...
Click to collapse
I am confused..is it working or not? one post you say it is but you cant sink..then you say its not.????
and dont use the flash off the mem stick..use windows..
ok, sorry for making confusing posts! I'm just excited about getting it to work.
So here's the situation:
From stock phone used with exchange (turned off the exchange part before doing anything)
1. I ran haret.exe from my phone, and it rebooted into a "black state" after which I rebooted it again
2. I tried to connect it to my computer using activesync, to be able to flash, but it wouldn't connect. Activesync doesn't respond to my phone.
3. I flashed the shipped rom to my phone from my sd-card in good hope that it would reset the whole process, but it still won't connect to activesync.
So here's my problem; I want to flash a cooked rom to my phone, but I'm unable to connect it to my computer via activesync, what to do?
deuse said:
go into settings then connections then more till you see USB to PC
in there un-tick the box which says enable advaned network.
Click to expand...
Click to collapse
tried with both ticked and unticked, still nothing
Turn off your phone then keep the camera button pressed in at the same time plug it into the usb port
your should show diff colors on the screen..if so follow what it says in this link.
http://forum.xda-developers.com/showthread.php?t=330909
and do it from the pc not your mobile...
it's restored, but no activesync still
Is the cable you are using ok? or is it a new one you just got.
does windows see it when you plug it in? if so un-install active sync then reinstall it.
I'm having the same issue with Windows Mobile 6.5 ROM, activesync simply doesn't work ;/
ivanek666 said:
I'm having the same issue with Windows Mobile 6.5 ROM, activesync simply doesn't work ;/
Click to expand...
Click to collapse
Have you been into settings and un-ticked the box in USB to PC?
Also if you are trying to sync to office you must create a new partnership
google is your best friend.
I have no problems with sync in XP/Vista?windows 7 and office 2007
I am using FMs 1.1 WM 1.1
deuse said:
Is the cable you are using ok? or is it a new one you just got.
does windows see it when you plug it in? if so un-install active sync then reinstall it.
Click to expand...
Click to collapse
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
zipuz said:
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
Click to expand...
Click to collapse
Do the Hard reset .Then connect it to your machine.I hope this time it will work smoothly.
zipuz said:
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
Click to expand...
Click to collapse
Try this
open sync then at the top chose files then click on DELETE MOBILE DEVICE
see what happens..but post back if you fix it to help other people
yogusmilu said:
Do the Hard reset .Then connect it to your machine.I hope this time it will work smoothly.
Click to expand...
Click to collapse
I failed to mention that I've tried the hard reset as well, no luck.
I thought about the same thing Deuse, but there's no mobile device registered, so I'm not able to delete it.
It seems that you have tried every possible method! Anyway, my suggestion is install activesync in some other PC (friend's) and connect your phone there. See if it registers the phone. If it does then it is problem with the PC and not with phone. In that case, connect phone to PC and open controlpanel>System (icon)>Hardware tab>Device Manager Button in your PC. Unfold Network adapters and see if your phone is detected properly or it is detected with an "!" mark in "Unknown/Other device". If so, delete the device and disconnect phone. Reboot PC, reboot phone connect again and let the PC reinstall your device and see if it recognises your phone.
One more way (I think you might have tried this)- Uninstall Activesync and reinstall and connect phone.
By the way if your phone is not recognised in some other PC then it seems trouble with the phone.
Thanks.
Looks like your cable is faulty. Try activesync connection through bluetooth (for testing, ofcourse you cant flash from bt ).
parthabhatta said:
It seems that you have tried every possible method! Anyway, my suggestion is install activesync in some other PC (friend's) and connect your phone there. See if it registers the phone. If it does then it is problem with the PC and not with phone. In that case, connect phone to PC and open controlpanel>System (icon)>Hardware tab>Device Manager Button in your PC. Unfold Network adapters and see if your phone is detected properly or it is detected with an "!" mark in "Unknown/Other device". If so, delete the device and disconnect phone. Reboot PC, reboot phone connect again and let the PC reinstall your device and see if it recognises your phone.
One more way (I think you might have tried this)- Uninstall Activesync and reinstall and connect phone.
By the way if your phone is not recognised in some other PC then it seems trouble with the phone.
Thanks.
Click to expand...
Click to collapse
It's marked with an "!", will try it on my own pc next time I have it, worked there last time! if not, I'll have to live with
Hi all i am new to this site and hopefully somebody can help. I got a galaxy s3 and every time i try connect to my pc the mtp driver fails to load. I have tried 3 different pc's both on vista and windows 7. I also tried kies and i won't recognize the phoen either. Any help would be greatly appreciated.
same here
i am experiencing the same problem. i have even reinstalled windows 7 ultimate (64 bit) to try to remedy the problem. still not working. the only programs added to win7 at this point are kies, firefox and chrome
i also tried to connect to a linux mint 12 box and i get the message that it can't find the program required on the computer to open.
it is really frustrating. i am going to try the google found method of unplugging my phone (which i plug in with the provided cable from samsung), and then:
1. removing kies (again)
2. removing drivers (again)
3. rebooting
4. installing kies
5. reinstalling drivers
6. connect phone in USB debug mode (there is no longer a kies option in s3) and let it install the other drivers.
7. unplug phone and turn off usb debugging
8. reconnect phone and hope for the best.
i will advise on how this goes.
blah
well, still stuck. tried the above method twice, and still no progress. i have tried many different ports, and have completely removed all usb devices except for the galaxy s3. i have tried both the 100mA ports and the 500mA ports. neither one will install the SAMSUNG Mobile MTP Device.
i am now at my wits end, as i have a laptop with vista and am receiving the same message.
i am sooo frustrated at this point. i guess i will have to use the Kies Air until i can get this working, which really makes it difficult, as that is not my main pc with all my music/videos on it.
i wonder if there is an app that might connect rather than relying on samsung mtp?
I have just talked to tmobile and it is a know issue with this phone, they are working on an update to the phones software and told me it should be available shortly. Hope this helps
samsung s3 and mtp issues
Same here have spent 2 days and tried everything to then find this thread, why don't Samsung recognize the problem. I am with vodafone so hope they react quickly.
workaround
i bought a micro adapter and am just switching out my external sd's. it's a pain, but at least i have mah music and vids.
Problem solved!!!!!!!! After many tries i removed the sim card from the phone and tried connecting the phonewith out the sim card and found everything worked normal, all the drivers loaded and the pc recognized my phone. So went to tmobile got a new sim card and now everything works great. So if you are having this issue try connecting without the sim card and if it connects normal then you know what the problem is. Hope this helps!!!!!!!!!!
Solved another way
Had the same problem with my Verizon S3. Tried the usual uninstall/reinstall with no luck, then got on the Samsung tech support chat site with "Nadia". Here is what we did (and it took some trial and error). Turned on debugging mode, drivers automatically tried to reinstall and failed again, then I switched the USB port (from one that supports faster charging to one that supports USB 3.0), the drivers reinstalled again, and it worked. Here is the chat transcript:
info: Please wait for a Samsung Agent to respond.
info: You are now chatting with 'Nadia'. There will be a brief survey at the end of our chat to share feedback on my performance today.
info: Your Issue ID for this chat is LTK56401322851X
Nadia: Hi, thank you for contacting Samsung Technical Support. How may I help you today?
Visitor: I have tried to install the device software on my Windows 7 PC to support the Verizon Galaxy S3. I keep getting "SAMSUNG Mobile MTP Device Failed" errors. I have uninstalled the drivers and software, rebooted, and reinstalled three times with the same result. This is a Win 7 64 bit machine. Any ideas?
Nadia: I understand that you have an issue downloading a software on the device. Is that correct?
Visitor: No. I have the software. The problem is that it will not install on my computer properly. As a result, my PC cannot see the phone when it is connected to the USB port.
Nadia: Thank you for correcting me.
Nadia: Are you referring to SCH-I535?
Visitor: yes
Nadia: Thank you.
Nadia: May I know if the USB debugging mode is ON on the phone?
Nadia: Please check mark USB Debugging option under Applications >> Settings >> Applications >> Development on the device.
Visitor: no it is not
Nadia: Please check mark the USB debugging mode and try.
Visitor: I have turned it on. Is that what you want?
Nadia: Yes.
Visitor: The PC now is trying to re-install the drivers
Nadia: Let me know if the drivers are reinstalled succesfully.
Visitor: The USB composite device, mobile usb modem and ADB interface were successful. The Mobile MTP Device failed
Nadia: Please right click on MY Computer>>Select Properties>>Hardware>>Device Manager>>Click on Samsung USB drivers and click on Update.
Visitor: Windows says it is up to date.but the device status is "the device cannot start (code 10)"
Nadia: Okay. Please perfrom the below step while the debugging option is on and try to connect.
Nadia: Please follow the steps mentioned below to perform a soft reset on your Phone.
1. Turn off the handset.
2. Remove the battery and wait for 30 seconds.
3. Reinsert the battery and turn ON the device.
Visitor: ok
Nadia: Please perform the above steps and let me know the status.
Visitor: Just removed the battery I have short fingernails and it is difficult to get the back cover off.
Nadia: I am sorry to hear that.
Visitor: just restarted it
Nadia: Okay.
Visitor: shall I reconnect it now?
Nadia: Yes. Please connect it and let me know the status.
Visitor: It's trying to reinstall the MTP driver.
Nadia: May I know if the installation is successful?
Visitor: Computer is still thinking
Visitor: Failed. Windows says the device cannot start
Nadia: May I know if you are using the USB cable which came along with the device?
Visitor: yes
Nadia: Okay.
Nadia: Please give me a moment while I go through the inquiry.
Visitor: ok
Nadia: Please try to connect to another USB port of the PC and check?
Visitor: ok
Nadia: Thank you.
Visitor: That worked!
congrats! did you have your sd card installed or out when this worked?
Well I had many conversations with Brian in the Kies support team for Samsung, end result - don't know how to fix this, will add you to an ever growing list of people who are unable to get this to work, we will contact you once we think we have a fix. So if you are running XP SP3 and you can't get mtp to load I am afraid you are knackered.......
I hope someone finds a fix or samsung sends an update out soon...This is driving me crazy...
i tried to get it to sync with a couple of linux boxes as well, to no avail...
Success! Well, here is how I got it to FINALLY install the MTP driver.
Navigated to:
Settings >>> Data and Backup >>> Factory Data Reset
When it asked me to set up my google account i chose "Not Now"
After also cancelling the dropbox creation/signin, I then plugged the phone in and...
Boom!
Driver installed successfully.
Now to enter my google account info and see if the driver can start...
So, this method works. after the driver installed successfully, I set up google, as well as all of my other previously downloaded applications. Connecting the phone now works, the driver has no issues.
btw, I am running win7 64 bit (ultimate) and now am happily transferring files the easy way!
Just waiting for my 64GB micro card to arrive, then life will be back to normal...
Thanks to XDA for all of the tips I received!:victory:
crimsonllama said:
So, this method works. after the driver installed successfully, I set up google, as well as all of my other previously downloaded applications. Connecting the phone now works, the driver has no issues.
btw, I am running win7 64 bit (ultimate) and now am happily transferring files the easy way!
Just waiting for my 64GB micro card to arrive, then life will be back to normal...
Thanks to XDA for all of the tips I received!:victory:
Click to expand...
Click to collapse
Installed first time on a windows 7 machine, no changing anything - installed the driver straight away and kies runs. So my problem is linked to xp.
Possible Fix...
I finally managed to get my MTP problem fixed for my galaxy s3.
First I plugged my phone to my PC and when my USB notification popped up on the top of my phone screen. Pull down your notifications and you will see "Connected as a media device Touch for other USB options" I did this and selected "Camera (PTP)" I then reconnected to the PC.
This allowed me to acces my phone and SD card in explorer but did not connect to Kies. So change back to MTP mode (media)
I then went into Device Manager and right clicked on MTP Device that had a yellow ! mark next to it, and went to properties > Driver tab > Uninstall.
!!***NOTE When you select uninstall make sure you select the tick box underneath which says something like " also delete the driver software" ****!!
Once uninstalled, open Kies which should be 'waiting' for you to plug in your device, do so now with unistalled drivers and it should find the device and ask you to upgrade your firmware straight away, do so and start syncing away
**NOTE: I did a factory reset on my phone before this, so if the above does not work for you, factory reset your phone and repeat the above steps***
If this starts to work please let me and other people know, so we can spread the word, because this is becoming a common problem.
Drove Me Nuts -- Until This Post
crimsonllama said:
Success! Well, here is how I got it to FINALLY install the MTP driver.
Navigated to:
Settings >>> Data and Backup >>> Factory Data Reset
When it asked me to set up my google account i chose "Not Now"
After also cancelling the dropbox creation/signin, I then plugged the phone in and...
Boom!
Driver installed successfully.
Now to enter my google account info and see if the driver can start...
Click to expand...
Click to collapse
I finally have my S3 working perfectly now. It's all due to the above post, most importantly this line "When it asked me to set up my google account i chose "Not Now"." I had been trying everything I could find, on just about every site I could find. So, I came here to run through everyone's ideas. That was the key for me. I did the factory reset again...This time after boot, I said no, skip and later to everything. Plugged in the data cord and to my surprise within seconds it was done. I looked in C: There was a new section called "Portable Devices" with a folder containing the two storage areas -- card -- phone -- I've since put in all my info. ran in de-bugging and switched back -n- forth between MTP and PTP .... So far so good....I hope this helps add to the mystery, and I was not to talkative...thnx Div
94q45t said:
1. Turn off the handset.
2. Remove the battery and wait for 30 seconds.
3. Reinsert the battery and turn ON the device.
Click to expand...
Click to collapse
For me this was the fix.... relay worked :good:
Galaxy S3 + W7 Ultimate x64
Before I've tried to reboot phone,PC but not worked....after battery remove....worked...
Working
Awesome guys thanks. Got a friends working doing a combo of mentioned fixes...
WHAT DID NOT WORK:
1. Uninstalling Windows Drivers
2. Virtualised a Win 7 x32 bit as there was mention this was a 64 bit problem (I am using Win 7 Pro x64)
3. Changed the USB Connection Settings via the Notification pull down
4. Restarting phone
5. With and without SIM
6. Different USB Port
WHAT WORKED:
On Windows 7 Pro x64:
1. Uninstalled MTP Device Driver in windows with "uninstall driver" checked
On Phone:
2. Factory Reset Device
3. On first boot: Skip Samsung Account Setup
4. On first boot: Skip Google Account Setup
5. On first boot: Basically skipped everything to get to Home Screen
6. Plugged in phone, connected immediately in File Manager and Kies
This all seems to kick the phone into action and it worked on all computers that it previously did not (It worked on nothing previously)
We setup all the accounts, installed all the apps and it the phone still connects to the computer.
Samsung, wicked phone, but this is not good!
Thanks again to all. Good luck.
what fixed for me
i was running resurection remix rom had driver fail changed to fox hound rom now usb connects everytime.lol
My 920T has stopped connecting to windows, however it can connect to ODIN and Smart Switch Emergency Software Recovery. It will not connect to Smart Switch regularly. I have tried 2 USB cords, my Windows 10 PC, and my work Windows 7 PC. I reinstalled the S6 drivers on both. I then performed a factory reset using the Smart Switch Emergency Software Recovery and the problem still persists. I am thinking this is likely an odd hardware issue, however the phone still connecting to ODIN and Emergency Software Recovery makes it seem like a software issue. Any thoughts?
Edit: USB debugging is enabled as well.
USB-Debugging enabled in developer options?
- Renolz
renolz said:
USB-Debugging enabled in developer options?
- Renolz
Click to expand...
Click to collapse
I forgot to mention. Yes it is.
Try download Shortcut master lite from playstore, run secret code explorer in it, then code 0808, and set AP and MTP+ADB to see phone as disk in windows, this helped me, hope it will help you.
brenner650 said:
Try download Shortcut master lite from playstore, run secret code explorer in it, then code 0808, and set AP and MTP+ADB to see phone as disk in windows, this helped me, hope it will help you.
Click to expand...
Click to collapse
did it work?
Hi all, a couple nights ago I flashed Lineage 15.1-20180806 to my OPO and everything went smooth. This morning I tried to connect it to my pc to transfer some pics and to my surprise the PC doesn't recognize it.
It looks like the PC is "trying" to establish a connection because the led in the phone blinks really fast for some small periods of time. The phone isn't charging when connected to the PC either.
What I have already tried:
- I already enable USB debugging in developer options
- Set MTP as default usb configuration
- Tried 2 different cables and different usb ports in PC.
I will try again in another computer when I get home but, honestly, this doesn't seem to be a problem with my PC or the cable as those were the ones I used when I flashed the rom and I also used the same cable when I transferred files to the same PC in the past. The phone was running Lineage OS 13 before the flash I think.
Any idea what else can I try to get it to work? I'm afraid I will be attached to this rom forever since I won't have a way to flash another ROM right?
EDIT:
If I go into recovery mode (TWRP) and plug the usb cable the PC recognizes it and I can transfer my files. So I'm 100% sure this is on Lineage OS. Again, when I get home I will see if ADB works while in TWRP but still would like to know if any of you guys has had this issue solved.
Thanks!
do you have anything important on your oneplus one
kallum7 said:
do you have anything important on your oneplus one
Click to expand...
Click to collapse
Nothing so far. It will become a back up phone soon.
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
kallum7 said:
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
Click to expand...
Click to collapse
Thank you, will give it a try and report back later.
adrek09 said:
Thank you, will give it a try and report back later.
Click to expand...
Click to collapse
okay
Is Lineage OS 15.1 supporting VoLTE by any way.
Had the same issue... and had this issue always coming back, currently with LOS18 (some devices worked, others didnt - couldnt see a pattern).
I tried all the triggers like setting File Transfer, disabling USB Debugging - nothing worked...
...until I rebooted my device (a YT703L).
In the end, it should be either (not sure which one actually)
File Transfer - always on (in DevSettings Default USB) or
USB Debugging off (also Dev Settings)
AND reboot.
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