I purchased a new Macbook Pro (Late 2016) which only has Thunderbolt (USB-C) ports and no standard USB ports.
I downloaded the Android SDK and setup ADB/Fastboot commands on the new mac, just like I did on my previous macs. However, I could not get the computer to recognize my phone with the USB-C to USB-C cable that came with my Google Pixel. I also tried using the USB-C to USB-C cable that came with my Nexus 6P, but that didn't solve the problem either.
So I went and bought a Thunderbolt to standard USB adapter and plugged it into the USB to USB-C cable that came with my Pixel and Voila! the computer recognizes the phone perfectly now with ADB and Fastboot commands.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's super annoying that we need an additional adapter for this (thanks, Apple). But I wanted to share this so others can save themselves the time of pulling their hair out trying to figure out why their new mac won't recognize their Android phone.
I also have a late 2016 Macbook Pro and have noticed weird behavior using ADB and Fastboot. For me, my usb c cable that came with my nexus 6p seems to work fine for adb when I choose 'File transfers' from the "Use USB for" menu in the notification drawer. Using the latest version of fastboot (installed via brew), seems to cause my macbook to freeze, regardless of whether i have and android device attached to the computer.
michaelmab88 said:
I also have a late 2016 Macbook Pro and have noticed weird behavior using ADB and Fastboot. For me, my usb c cable that came with my nexus 6p seems to work fine for adb when I choose 'File transfers' from the "Use USB for" menu in the notification drawer. Using the latest version of fastboot (installed via brew), seems to cause my macbook to freeze, regardless of whether i have and android device attached to the computer.
View attachment 3964773
Click to expand...
Click to collapse
Same here, ADB works fine with my Nexus 5x and Nexus 6p, but I can't get fastboot to work... tried different adapters and cables and also other terminal software on the Macbook, but nothing helped. Any news anyone?
thal said:
Same here, ADB works fine with my Nexus 5x and Nexus 6p, but I can't get fastboot to work... tried different adapters and cables and also other terminal software on the Macbook, but nothing helped. Any news anyone?
Click to expand...
Click to collapse
Bump. Any updates on this? I am also having problems with fastboot with my nexus 6p. I enter the command and nothing happens. It just goes to the next line and hangs there.
Filed bug with Google
There is a filed bug on: code.google.com with id 231129
Please upvote that bug, its a show stopper for many Android / iOS devs (like me)
ta1onn said:
There is a filed bug on: code.google.com with id 231129
Click to expand...
Click to collapse
cputoaster said:
Please upvote that bug, its a show stopper for many Android / iOS devs (like me)
Click to expand...
Click to collapse
It looks like they're working on it, here's the patch comments: android-review.googlesource.com with id 328620
ta1onn said:
It looks like they're working on it, here's the patch comments: android-review.googlesource.com with id 328620
Click to expand...
Click to collapse
Any update on this fix? My Windows partition no longer recognizes my Pixel anymore either. I'm getting extremely frustrated.
Workaround: Install VirtualBox
sn0warmy said:
Any update on this fix? My Windows partition no longer recognizes my Pixel anymore either. I'm getting extremely frustrated.
Click to expand...
Click to collapse
It's really annoying that you have to do this, but the workaround is to use Ubuntu/Linux on a virtual machine. It worked on my Nexus 5X + MacBook Pro 2016.
Here's the steps to do it:
Install VirtualBox
Install Ubuntu or other Linux distro
Install fastboot/adb with `sudo apt-get install adb fastboot`
Attach Nexus 5x to VirtualBox
Done!
Shameless advertising:
https://jameswarp.com/2017/fix-fastboot-macbook-pro-2016/
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
So I've been trying for quite awhile to bring my player back. I was trying to develop my kernel with it and it just plummeted to it's death eventually. I found a DD dump somewhere of another device and flashed it, which I guess might not have been exactly the right file and now here we stand.
The device doesn't turn on, I don't get any "SAMSUNG" boot logo - nothing. It comes up in windows as
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now from the research I've done, that should be the "lucky unbrickable" state. The device does nothing, but still shows up in windows. I've tried unbrickable on windows 7, windows 7 via a ubuntu VM, and went as far as to setup a dedicated desktop with ubuntu natively and a windows XP VM. I can only get my player to react on the native linux desktop, but it enters download mode really strangely -
YouTube video of it being "resurrected"-
http://youtu.be/WDclUEyoHFE?hd=1
And after that I lose USB (although the device stays on and powered up as long as I leave it connected). I tried connecting the device to my XP VM which is what everything says to do, and I get "No USB devices connected" in virtualbox. Dmesg gives me "unable to enumerate USB device on port 1, device descriptor read/8, error -71" as soon as download mode initiates.
Every time I've done this whole process before, it's worked wonderfully and you can continue on and flash your bootloaders, then reflash everything else. I've tried this whole process over and over and over and haven't had any success. I also tried a USB jig and it didn't do a single thing.
Can anyone provide ANY insight? I'm really open to anything right now, otherwise it's out for JTAGing. I'm about at whits end with it and I'm out of ideas.
THANKS!
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
lolo9393 said:
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
Click to expand...
Click to collapse
My windows 7 computer connects fine to my galaxy s3. I just root/recovery/rom/kernel'd it a few days ago from that computer, so everything seems to be working as it should.
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
ti-pich said:
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
Click to expand...
Click to collapse
Yeah, I actually just did that. I even went as far as trying the current and past 3 versions of heimdall and it doesn't detect any devices.
Sent from my galaxy nexus using xda app-developers app
oneclickunbrick
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Evoium said:
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Click to expand...
Click to collapse
Thanks, I'll try that when I get home. It looks like a precursor program to the unbrickable mod but I'm willing to try anything at this point!
Sent from my Galaxy SIII
has it worked for you ?
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
PairOfSocks said:
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
Click to expand...
Click to collapse
Yep, tried that a few times. I was using heimdall before so the drivers should be kosher for it.
It's almost like once it enters download mode the hardware isn't cooperating. I've also gone as far as trying every previous version of UnBrickable thinking one might work better, but I've gotten the same result with all the versions. Download mode shows up and then it drops all connectivity.
I have a ZEKI 10" TBQC1063B tablet. It apparently an updated version in that it now comes with Google Play Store app installed from the factory. It has Android 4.1.1.
I started to try to Root the device, but was unsuccessful.
In my quest to debug Rooting, I started trying playing with ADB directly. I quickly discovered I could not get to 'first base' with ADB.
Yes, I have USB DEBUGGING enabled, and when my tablet is plugged into my PC, the tablet shows that icon of the Android face in the status line in the lower right screen.
I started to try different drivers (reading that such might be the cause of ADB not working), even though all of the appear to be working OK when I check in Device Manager. One of the attempts I made at drivers led me to those offered as part of PDAnet. While using PDAnet's drivers didn't seem to help, I did stumble upon a CLUE. The CLUE is that while installing the PDAnet drivers, PDAnet did successfully install its own app onto my tablet. I think that such requires ADB to work, no? Could someone confirm such (or not)?
I tried a PC program called AdbDriverInstaller. When I first tried it, it reported a Device Status error of "Driver Incorrectly". So, I uninstalled that driver (I belive at that point it was the PDAnet one), and installed a new driver from a collection called UniversalAdbDriverSetup6. Now, that looked better. AdbDriverInstaller now shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking better?
My problem is that ADB DEVICES still shows no devices:
Does anyone know of anything else to try? This is about the limit of my expertise.
Try!
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Kunal.Kene.1797 said:
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Click to expand...
Click to collapse
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
WaltA said:
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
Click to expand...
Click to collapse
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Also, this is a good tool..makes adb system wide as well HERE
Also, not sure when Android implemented this, you might see a box up asking for you to grant the PC permission to use ADB, grant it
WaltA said:
Click to expand...
Click to collapse
lacoursiere18 said:
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Click to expand...
Click to collapse
I unplugged and plugged my tablet in a few times (over a course of several days while I tried to debug this on my own). Both my PC and my tablet have been powered on/off and rebooted over that time too.
I believe I showed I ready tried those commands, with no success.
TBQC1063B Zeki tablet
Zeki TBQC1063B
Any roms available? This one seems to be stuck. I can get to the boot list, but haven't found a new rom for it. Or even the factory rom.
Hi, as the title says, I'm trying to unlock the bootloader of my V30 (H930, firmware 20r), and each time I try to unlock it, it hangs on the first step of the unlock process:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've gone through the 'WTF' post here, and I've done all the troubleshooting apart from trying Windows 7/another PC, and trying another USB-C cable (only have the one). It's 2nd hand, so I have no idea if it was previously Android 9/10, if that complicates things?
Any help would be great, TIA.
Irradium said:
I've done all the troubleshooting apart from trying Windows 7/another PC, and trying another USB-C cable
Click to expand...
Click to collapse
You admit you haven't tried all the Troubleshooting Tips. That's your answer and you know it.
For some people it works on the THIRD different computer they tried, or the THIRD different USB cable.
___
Any reason why you started a completely different thread, when your question is about the WTF INSTRUCTIONS? I'm going to repost your question and the answer there, where it belongs.
ChazzMatt said:
You admit you haven't tried all the Troubleshooting Tips. That's your answer and you know it.
For some people it works on the THIRD different computer they tried, or the THIRD different USB cable.
___
Any reason why you started a completely different thread, when your question is about the WTF INSTRUCTIONS? I'm going to repost your question and the answer there, where it belongs.
Click to expand...
Click to collapse
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
When you put it that way, yeah, good idea to repost it.
Irradium said:
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
Click to expand...
Click to collapse
If you have tried the different ADB installations, you've installed all the different Windows, Google, LG drivers mentioned in the Troubleshooting Tips, and you're on the right firmware, then the only answer is to try a different computer or a different cable. I can give example after example...
One guy had a very expensive Windows 10 GAMING computer, but it worked with his brother's very cheap Windows 10 laptop computer. He couldn't believe it.
Also, while Windows 10 will work, Intel Windows 7 with USB 2.0 ports seems to work best. Or you can order a cheap USB 2.0 hub off eBay and plug it into your computer.
Except for the right firmware (Tip #1), all the other Troubleshooting Tips deal with ADB communicating with your phone. There's 11 tips whose sole purpose is to makeh ADB communicate with with your phone to send this unlock code.
---------- Post added at 08:51 PM ---------- Previous post was at 07:55 PM ----------
See here:
NeonHD said:
Hi, just want to say that for anyone who is stuck on the Sending 'unlock' part, I HIGHLY RECOMMEND switching to another computer. I was stuck on that part and I did everything from reinstalling the drivers to using another adb package and still to no avail. Then—as it was suggested and performed by many—I finally decided to switch to another computer (my PC tablet running windows 10) and guess what?? It works!!!
I was expecting to get the same error, but nope I FINALLY unlocked my V30!!
This is my testimony to you all so hopefully more people will do this before giving up.
Click to expand...
Click to collapse
Irradium said:
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
Click to expand...
Click to collapse
As ChazzMatt wrote, different cables, different USB ports, different computers.
The only thing I'd add is to run fastboot devices after entering fastboot mode, before flashing unlock.bin. If it doesn't list your phone's ID at that point, you know the connection isn't working.
Not gonna lie, I was skeptical at first too whether changing computers would actually fix anything, but it did. Perhaps ADB drivers work better on Intel than AMD devices.
NeonHD said:
Not gonna lie, I was skeptical at first too whether changing computers would actually fix anything, but it did. Perhaps ADB drivers work better on Intel than AMD devices.
Click to expand...
Click to collapse
Funnily enough, my main machine (Ryzen 1600) got as far as starting the flash, whereas my work laptop (Intel ??) didn't even list the device...
Irradium said:
Funnily enough, my main machine (Ryzen 1600) got as far as starting the flash, whereas my work laptop (Intel ??) didn't even list the device...
Click to expand...
Click to collapse
Doesn't work with AMD Ryzen whatsoever.
If you search in the WTF thread for "Ryzen" you'll see all the failures. To be honest, I'd never heard that name before V30 WTF thread. I stopped using AMD years ago because I kept being disappointed about performance vs Intel on budget laptops and desktops for family and friends.
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
There does seem to be a known problem with the Mi Unlock tool not being able to communicate properly with the system drivers. There are some tips for getting it working on this thread:
https://forum.xda-developers.com/t/...ol-cannot-detect-phone.3663139/#post-73566526
If that post doesn't solve the problem then try reading through the later posts in that thread.
Sorry for the late reply, I did the suggestion and it worked! Thank you for the help.
My goal was to flash the indonsian rom of the device onto and I had a bit of a problem last night I ended up sending it into a bootloop because the connection wasn't stable from the computer to the phone, I just woke up today and tried it again on a different computer and a brand new cable and the connection wasn't cutting out at all. I put it in fastboot and succesfulyl flashed it. I can't thank you enough for the help.
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
The Spike Man said:
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
Click to expand...
Click to collapse
No need, your experience may be shared by others in which case it will be useful to have somewhere to talk about it
The Spike Man said:
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
View attachment 5681651
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
Click to expand...
Click to collapse
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
aariss said:
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
Click to expand...
Click to collapse
It is mediatek.