[Q] Unlocking the bootloader problem - Xiaomi Mi Mix 2S Questions & Answers

When the Mi Mix 2S is in fastboot and the Unlock program on the computer says to connect the phone to the computer, when I do the phone screen displays the text Press any key to shutdown.
I've tried different USB type-c cables, different USB ports, tried re-installing the Fastboot drivers and what's worse is fastboot mode stays when the Unlock software is not running. I can plug in the phone to the computer while phone's in fastboot mode and it stays in fastboot mode.
Is the Unlock software supposed to say how long to wait before trying to unlock the bootloader?
Here is the updated bootloader unlock announcement from Xiaomi MIUI forums http://en.miui.com/thread-246705-1-1.html

Related

[Q] Unlocking Bootloader Using SDK and ADB

I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium

Fastboot won't list device XZs Dual SIM

Hi,
I have the Android SDK installed and have also enabled USB debugging and allowing unlocking of bootloader option in developer options. When my phone is on and I connect it via USB cable, and then run adb devices command, I can see it shows the device. However, when I switch off and enter fastboot mode (volume up + plug usb cable) and then run fastboot devices command, it displays nothing. Can someone please help?

unlock bootloader huawei mate 9

i got the bootloader unlock key from huawei and saved it in case i will need it, i want to unlock it now so i downloaded the latest android platform tools. i tried unlocking it using fastboot but fastboot devices didnt return anything (i used adb reboot bootloader to enter the fastboot mode) when the phone was in the fastboot mode (it said phone locked frp unlocked) i tried fastboot oem unlock [key] but it didnt find any device so i typed fastboot devices but it didnt return anything. i searched for almost an hour in xda and the internet and couldn't find anything helpful so i created an account and posted the question here (it didnt allow me to post on the root forum)
Have you put your phone in fastboot mode first. (Turn off phone and while holding down the volume down button plug in the usb cable to your pc) or download the Multi Tool application from https://pro-teammt.ru/huawei-multi-tool-eng/ and use the unlock bootloader with own key. Note that unlocking the bootloader will factory wipe your phone so make a backup first.
rex91 said:
Have you put your phone in fastboot mode first. (Turn off phone and while holding down the volume down button plug in the usb cable to your pc) or download the Multi Tool application from [link that xda didnt allow me to add] and use the unlock bootloader with own key. Note that unlocking the bootloader will factory wipe your phone so make a backup first.
Click to expand...
Click to collapse
i tried it but it has the same problem, it sends the phone into the fastboot mode and then it cant find it, i connected the phone with usb cable and enabled all necessary options from the developer options in the settings
When you connect your phone to your pc and go into device manager is your device recognised. If not then either it might be a driver issue (reinstall all Huawei drivers), a usb cable problem (try another cable) or a usb port problem (try another usb port)

Device not recognized in fastboot on Mac and not recognized at all on PC

I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?

Asus ZenFone Max Pro M2 fastboot mode says 'press power key to shutdown' after plugging in.

I was trying to unlock my phone's (Asus ZenFone Max Pro M2) bootloader using Unlock Batch using the guide here. When I booted into fastboot everything was fine but when I connected using USB and ran fastboot devices using my laptop, the phone's screen turned into a black screen saying 'press power key to shutdown' and fastboot identified the device as '????????'.
I have the usb drivers installed (both universal and asus's official) and have even tried uninstalling and reinstalling but still no progress. If the phone is booted, adb is able to detect the device normally.
RikSantra1119 said:
I was trying to unlock my phone's (Asus ZenFone Max Pro M2) bootloader using Unlock Batch using the guide here. When I booted into fastboot everything was fine but when I connected using USB and ran fastboot devices using my laptop, the phone's screen turned into a black screen saying 'press power key to shutdown' and fastboot identified the device as '????????'.
I have the usb drivers installed (both universal and asus's official) and have even tried uninstalling and reinstalling but still no progress. If the phone is booted, adb is able to detect the device normally.
Click to expand...
Click to collapse
I have the same problem..

Categories

Resources