Related
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help
I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?
keval3492 said:
I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?
Click to expand...
Click to collapse
I recommend to follow this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
When your device isn't recognized by your pc you need to check if any firewall, antivirus or the driver signature verification prevents your device from being recognized. Also make sure that you reboot your pc after the installation of the Motorola drivers.
Thanks man !! But in thread which you send is not help me untill I unlock my phone.
keval3492 said:
Thanks man !! But in thread which you send is not help me untill I unlock my phone.
Click to expand...
Click to collapse
Sure, in the first step: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a otherwise please explain where you stuck when it's not the drivers?
In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???
keval3492 said:
In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???
Click to expand...
Click to collapse
Type "fastboot devices" when connected to the PC. If it shows your serial number of your phone then ok. If not, problems I mentioned before should be checked at your end.
I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .
keval3492 said:
I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .
Click to expand...
Click to collapse
Have you checked firewall and antivirus to be disabled?
You can also provide the whole console output here to get better overview of your errors :good:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
Oh, nice to know...
Unless you did not provide an console output its hard to help. Additional you need to make sure that "fastboot devices" displays the serial number, if it doesn't, you need to check firewall, driver signature verification, antivirus etc etc on the PC of your friend.
It's a common problem and the things to check by your end are the same and everything I've seen and read it's cause of the mentioned problems. Maybe your friend has something wrong configured or whatever.
keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.
Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/
Whenever I go to my friend's house and use his laptop to unlock my bootloader I will give you screen shot of display which causes problem for me to unlock my bootloader,thanks sir!!!!! And how to know that any anti virus ,firewall and other things you mentioned is stop me to install moto drivers?
Ayan Uchiha Choudhury said:
Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/
Click to expand...
Click to collapse
Yes this is the basic for any unlocking bootloader process which I already done , switch on OEM unlocking,usb debugging,file transfer etc.thanks for it.
echo92 said:
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.
Click to expand...
Click to collapse
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.
keval3492 said:
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.
Click to expand...
Click to collapse
Tutorials for disabling driver enforcement can be found through a Google search (e.g. here's a link : https://www.drivethelife.com/window...e-enforcement-on-windows-10-8-7-xp-vista.html ) Of course, ask your friend before attempting this, as this allows you and anyone else to install and run unsigned drivers (including the fastboot drivers).
Okk thanks bro
So it is a safe driver(moto device manager)? Because if my friend ask me !!
keval3492 said:
So it is a safe driver(moto device manager)? Because if my friend ask me !!
Click to expand...
Click to collapse
You download it directly from motorola website? Why it should not be safe
Yes I downloaded from Motorola website ,it is also safe ,so why any PC not installed moto driver directly!!!!and gives fastboot _ Athens 16 mp s
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established
Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button
Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.
@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..
I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.
Moto e4 magisk manger trying to instal magisk hide props config says install failed
happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself
Safety net says the response is invalid does that affect ny device being rooted
happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?
Possible problems - phone defaults to USB for charging, not for file transfer.
Title. I've followed directions word-for-word. However, starting the device in fast boot & plugging it into the PC will not cause the device to appear. I Mi Unlock also can not detect it.
How am I messing this up? What can I do to fix it? Do I have a bum phone & need to return/replace?
Logged into Mi account
Mi account sync on
Find my device on
Developer options enabled
Enable USB debugging enabled
OEM unlocking enabled
SIM card in, wifi off, mobile date on
Mi Unlock status activated
All of the above done
Initiate fastboot
Start Mi Unlocker & sign in
Plug fastbooted phone in
Phone not detected by Mi Unlock
Not appearing in Windows Explorer
Use CMD to search for devices, none found
CMD -> adb devices returns nothing
i've a similar problem, for me the problem was the usb 3.0 port, with a fresh start of win10 i can see the phone connected in fastboot mode, when i open mi unlock the phone disappear and after is impossible to be recognized until a restart of win10. The only way for see the phone detected by MI unlocker was to use and usb 2.0 hub connected in the usb 3 port. Use a usb 2.0 port if you've or try with another computer.
TitanRaven said:
Possible problems - phone defaults to USB for charging, not for file transfer.
Title. I've followed directions word-for-word. However, starting the device in fast boot & plugging it into the PC will not cause the device to appear. I Mi Unlock also can not detect it.
How am I messing this up? What can I do to fix it? Do I have a bum phone & need to return/replace?
Logged into Mi account
Mi account sync on
Find my device on
Developer options enabled
Enable USB debugging enabled
OEM unlocking enabled
SIM card in, wifi off, mobile date on
Mi Unlock status activated
All of the above done
Initiate fastboot
Start Mi Unlocker & sign in
Plug fastbooted phone in
Phone not detected by Mi Unlock
Not appearing in Windows Explorer
Use CMD to search for devices, none found
CMD -> adb devices returns nothing
Click to expand...
Click to collapse
I used Windows 7 and it worked perfectly first time. I think (as always) it's a windows problem.
AndrewChan99 said:
I used Windows 7 and it worked perfectly first time. I think (as always) it's a windows problem.
Click to expand...
Click to collapse
Can I use Windows 7 disk image on a Windows 10 to fix it? I don't have access to any Windows 7 computers ATM.
What worked for me is transferring the folder of mi unlocker to the root of C: and reinstalling adb drivers
PowerGirl said:
Possible problems - phone defaults to USB for charging, not for file transfer.
Title. I've followed directions word-for-word. However, starting the device in fast boot & plugging it into the PC will not cause the device to appear. I Mi Unlock also can not detect it.
How am I messing this up? What can I do to fix it? Do I have a bum phone & need to return/replace?
Logged into Mi account
Mi account sync on
Find my device on
Developer options enabled
Enable USB debugging enabled
OEM unlocking enabled
SIM card in, wifi off, mobile date on
Mi Unlock status activated
All of the above done
Initiate fastboot
Start Mi Unlocker & sign in
Plug fastbooted phone in
Phone not detected by Mi Unlock
Not appearing in Windows Explorer
Use CMD to search for devices, none found
CMD -> adb devices returns nothing
Click to expand...
Click to collapse
In the Mi Unlocker app, in the top right corner there's the settings button, go there and look for the "Install drivers" button. That worked for me.
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
sujan smash said:
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
zgfg said:
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
Click to expand...
Click to collapse
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
sujan smash said:
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
Click to expand...
Click to collapse
Everything looks correctly set but you could still try another PC and USB cable
zgfg said:
Everything looks correctly set but you could still try another PC and USB cable
Click to expand...
Click to collapse
Well i did that too, tried it on my laptop too no luck there also,
As ive mentioned in the first thread ,
It is detecting redmi note 10 in fastboot mode on the same pc with same cable and everything, but not redmi k20, so its not abt PC drivers its something to do with my phone
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
zgfg said:
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
Click to expand...
Click to collapse
Yep it sucks, Thanks Anyways