Related
I am afraid I have made a very big n00b mistake.
Let me just say to prior to this goof up, I was well informed of the rooted SG4G world and had successfully flashed CWM and was running on various custom kernels and tweaks. I am currently abroad and had to revert back to my unlocked SG4G as my phone abroad, so my knowledge of the rooting world became somewhat diminished. Now here lies the problem. Earlier this morning, my phone had a random reboot. I decided to try and flash another kernel that I had saved on my phone via SGS Kerenel flasher(which I have used successfully used before). However, I think i may have reverted to the stock kernel that did not run well with all the tweaks I had previously installed. Now when I boot up, I get stuck on the SG4G screen (only for T-Mobile screen). I rebooted into recovery mode but it appears as if I have lost CWM, therefore I can not do a nandroid back up.
My question is: How can I restore my phone and make a nandroid backup without CWM?
I already took matters into my own hands and tried flashing CWM via Haeimdall through the kernel that is suggested in "The Definitive Noobs guide to Flashing and or fixing the SG4G" but Heimdall does not seem to recognize my device. It does say "Device detected" when I enter download mode but it is not giving me the option to click "Start."
Help will be much appreciated since I am relying on my phone while I am abroad and need to fix this ASAP.
Much appreciated and again,
Sorry for the n00b mistake
Take note of the 'kernel' in SGS Kernel Flasher. Not ROM flasher.
Follow the guide in the second link of my signature.
Thank you for the prompt response lumin,
I have followed your guide to the bone but I am unfortunately stuck on a certain step. When I reboot my phone into "Download mode" and connect the USB cable, nothing happens. The command prompt just says "Ready for Flash" and does not proceed to the "Installing Drivers" step.
Any thoughts on this?
I hope this does not mean my phone has become a paperweight and that my computer no longer recognizes the phone via USB .
Edit: According to Heimdall the Device status says "Connected" but according to the the command prompt it says "Device not connected" and "Ready for Flash"
Also, when I first plug in my phone, Windows 7 tells me the "USB device is not recognized"
Hope this doesn't mean we've hit a dead end...
Did you read the notes about removing other drivers that may have been installed on your computer for your phone?
lumin30 said:
Did you read the notes about removing other drivers that may have been installed on your computer for your phone?
Click to expand...
Click to collapse
Yes I did. I installed usbdeview before I began the process and deleted anything Android/Samsung related.
Windows doesn't seem to recognize my phone but Heimdall does say the "Device Status" is connected.
Any other thoughts?
When I first connect to my pc (holding buttons to get in download mode, gb bootloaders) I get same msg. But, once I press the volume button and enter download (Andy & shovel screen), the computer(Odin) sees it and that not recognized pop up goes away. Are you sure you got a proper/good cable?
Eurik said:
Yes I did. I installed usbdeview before I began the process and deleted anything Android/Samsung related.
Windows doesn't seem to recognize my phone but Heimdall does say the "Device Status" is connected.
Any other thoughts?
Click to expand...
Click to collapse
If Heimdall see's it, it's soft bricked and fixable by flashing the right stuff. Still getting into download mode, it can be fixed.
getochkn said:
If Heimdall see's it, it's soft bricked and fixable by flashing the right stuff. Still getting into download mode, it can be fixed.
Click to expand...
Click to collapse
That is great news.
But how exactly do I flash "the right stuff?"
I noticed that when I plugged my SG4G to attempt the "Installing Drivers" step via CMD, my laptop installed the drivers automatically and said "the device is ready to use." Does this constitute as "Installed Drivers" step completed and I can proceed to flashing KJ6 Heimdall via one click?
Thanks,
Eurik
champ1919 said:
When I first connect to my pc (holding buttons to get in download mode, gb bootloaders) I get same msg. But, once I press the volume button and enter download (Andy & shovel screen), the computer(Odin) sees it and that not recognized pop up goes away. Are you sure you got a proper/good cable?
Click to expand...
Click to collapse
I am using a data cable that I believe is from an old "V-cast" phone. I am not using a Samsung Galaxy USB cable but I have not had a problem with transferring files to and from my phone from my laptop so I assume it is not the cable... unless I am mistaken?
Use your cable that came with the phone. Just because the cable will transfer files doesnt mean it will work with heimdall.
You keep mentioning installing drivers through cmd line. While it does show the cmd line in the background - Zadig should open giving you a GUI to install/replace the drivers.
Is Zadig opening when you run the One-Click? Also, do you still have Samsung drivers installed on your computer? Go to My Computer > Uninstall Programs and look.
lumin30 said:
You keep mentioning installing drivers through cmd line. While it does show the cmd line in the background - Zadig should open giving you a GUI to install/replace the drivers.
Is Zadig opening when you run the One-Click? Also, do you still have Samsung drivers installed on your computer? Go to My Computer > Uninstall Programs and look.
Click to expand...
Click to collapse
Hello lumin and thank you again for your prompt responses,
I checked again to see if there were any drivers installed and you were in fact correct. The KIES program slipped by my findings. I uninstalled it and again uninstalled anything Samsung/Android related via usbdeview.
I thought this might do the trick but Zadig is not popping up when I plug my USB cable in my "Download ready" Samsung. The CMD does read "Ready for flash" and Heimdall says its connected. Should I just go ahead and run Heimdall? WIll Zadig pop up after I click the "flash" button. If I am not mistaken, your tutorial says it should automatically pop up, which in my case, it is not.
Also, eollie did mention I need a the Samsung Galaxy S USB cable that came with my phone. I am not currently using that. Could the cable be the culprit to my issue?
I really appreciate everybody's help to my problem.
Thank you all,
Eurik
If it says connected in Heimdall and flash is enabled - then yes - flash. It does not have to be a Samsung cable. The cable will either work or not work. And it sounds like yours is working.
lumin30 said:
If it says connected in Heimdall and flash is enabled - then yes - flash. It does not have to be a Samsung cable. The cable will either work or not work. And it sounds like yours is working.
Click to expand...
Click to collapse
Alright lumin,
One more step complete, one more problem.
I got to the step where Zadig shows up. The drivers even installed and I got a message saying my "Device is ready to use."
Now the new problem.
When I select "List all devices" I do not see the option to select "Samsung USB Composite Device."
4 devices are listed and the include: HP webcam-101 (Interface 0). HP webcam-101 (Composite Parent), Gadget serial, and Gadget serial Control (interface 0).
No Samsung USB Composite device though.....
Eurik said:
Alright lumin,
One more step complete, one more problem.
I got to the step where Zadig shows up. The drivers even installed and I got a message saying my "Device is ready to use."
Now the new problem.
When I select "List all devices" I do not see the option to select "Samsung USB Composite Device."
4 devices are listed and the include: HP webcam-101 (Interface 0). HP webcam-101 (Composite Parent), Gadget serial, and Gadget serial Control (interface 0).
No Samsung USB Composite device though.....
Click to expand...
Click to collapse
Did you go to advanced or whatever the item is and choose list all devices?
getochkn said:
Did you go to advanced or whatever the item is and choose list all devices?
Click to expand...
Click to collapse
Sure did.
Mentioned in my post that I selected "List all devices."
Any other thoughts?
Use Gadget Serial. Others have reported the same situation and successful used Gadget Serial. And/or try a fresh USB port.
lumin30 said:
Use Gadget Serial. Others have reported the same situation and successful used Gadget Serial. And/or try a fresh USB port.
Click to expand...
Click to collapse
Christ all mighty it worked.
Lumin I cannot thank you enough for taking the time to walk me through this. I can now use my phone again abroad and go back to business.
A millions thanks lumin.
Sincerely,
Eurik.
Eurik said:
Christ all mighty it worked.
Lumin I cannot thank you enough for taking the time to walk me through this. I can now use my phone again abroad and go back to business.
A millions thanks lumin.
Sincerely,
Eurik.
Click to expand...
Click to collapse
Now you can help others. If you will - add [Solved] to the thread title.
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Have you enabled USB debugging in Developer Options in settings?
Sent from my XT1032 using Tapatalk
Of course I did ^^
battlemaxi said:
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Click to expand...
Click to collapse
For my XT1031, I had to use the Motorola USB drivers for ADB to work, and Kush's Universal ADB drivers for Fastboot to work.
And if you are using Windows 8/8.1, then you have to disable to forced signature verification in order to install the Universal ADB drivers.
Also, for ADB to work in Windows, I had to set the phone's USB computer connection to Camera (PTP), instead of Media Device.
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
battlemaxi said:
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
Click to expand...
Click to collapse
Dude, you need to follow the instructions step by step and provide more info about what's going on.
1. Is your "Enable ADB debugging" enabled? You said yes.. does your phone show "Android debugging enabled" icon when you plug it into your computer? If not, you don't have it enabled !
2. If you see the notification, go to Device Manager (hope you are using Windows, or I can't really help you), then can you find your device there? If the USB drivers are installed correctly, then you should see "Android Device" then a "Motorola ADB Interface" inside it. If not, you will see a yellow exclamation with something like "Motorola device"..
3. Did you change your phone's USB computer connection to Camera (PTP)??
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
liveroy said:
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
Click to expand...
Click to collapse
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
robin0800 said:
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
Just follow those instructions to the letter and any thing you don't understand or get an error message report back here
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Hmmm... so.. what do you see when you type "adb devices" ?
Also, in your Device Manager, is the Motorola ADB interface properly installed? (no issues)?
And yes, to unlock the bootloader you just need Fastboot... when you boot to Fastboot and type "fastboot devices" do you see anything?
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
battlemaxi said:
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
Click to expand...
Click to collapse
Well, are you sure you fastboot works?
If so, it's very weird why adb won't...
And yeah, ADB is very useful... if not lifesaving...
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Can you see adb in the computer device manager program
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
liveroy said:
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
Click to expand...
Click to collapse
Even if you revoke, you should see the device listed if you run "adb devices"...
neozen21 said:
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
Click to expand...
Click to collapse
Nope
I guess I have the newest Version, cause I downloaded it from Motorola.com
Yes everything is working no yellow thingys what so eher..
If I use the 'ADB devices' command the ID of my device shows up but as already mentioned it's offline.
Gesendet von meinem XT1032 mit Tapatalk
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
For me, it was a wiring problem. I hadn't got the original wire plugged, but a second one bought in ebay. Then I used the original one, and problem solved. I hope it is your problem.
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Try using the Universal Naked Drivers instead.
http://forum.xda-developers.com/showthread.php?t=2139767
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Have you tried a different USB port on your PC? I know when I first started customizing my tablet I had problems using the front ports on my PC. It wouldn't recognize my tablet in fastboot, but when I plugged into one of the back ports directly on the motherboard it worked great.
Ehh
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Solved
Tajmoti said:
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Click to expand...
Click to collapse
@Tajmoti can you add solved to the thread name...
lj50036 said:
@Tajmoti can you add solved to the thread name...
Click to expand...
Click to collapse
I dont know how LOL
Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!
From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!
I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.
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