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)
Related
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
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?
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
I accidentality flashed a wrong oreo Chinese firmware on my international mate (nxt-L29), with that I'm stuck with booth bootloader and FRP lock ("enable OEM unlock" option in developer mode sitting is greyed).
in attempt to resolve this problem I'm asked to put USB ports setting on Manufacture mode in ProjectMenu witch i can't access via *#*#2846579#*#* code on phone.
it shows nothing.
help please....
is there any other method to enable Manufacture mode in usb setting like adb command ?????
note:
when i was in the upgrade mode (phone off, press the tow volume button up and down then connect the micro usb cable) i noticed the device respond to ADB commands and it's detected but unauthorized.
is there a way to make adb works.
tarekcod said:
note:
when i was in the upgrade mode (phone off, press the tow volume button up and down then connect the micro usb cable) i noticed the device respond to ADB commands and it's detected but unauthorized.
is there a way to make adb works.
Click to expand...
Click to collapse
you need to activate usb debugging first in the setting then it will give authorized
ceriqdesign said:
you need to activate usb debugging first in the setting then it will give authorized
Click to expand...
Click to collapse
I'm talking about the upgrade mode here.
tarekcod said:
I'm talking about the upgrade mode here.
Click to expand...
Click to collapse
Haha..#2nd post you said about adb unauthorized..so i respond to the question..
I lost root after updating the OS. So I want to root the phone. When the phone is in the system, it is OK to connect to my computer, and ADB is also OK. But when I boot into fastboot mode, it just can't connect to the computer no matter the computer is mine or my friend's. I have installed the driver....
USB debugging turned on?
I can help you with that, tell me if you still have the same problem.
Usb debugging makes no difference in fastboot mode. Adb doesn't do anything in fastboot mode. Fastboot works with fastboot mode. If you don't know this simple fact, you will likely screw up your phone trying to root it. I suggest you do some reading.
Just switch to you routed slot and root the update from there. Then switch back.