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.
Related
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.
matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.
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?
I have installed all drivers and did all the obvious tricks like driver signature, installing adb drivers and extracting xioami tool to C drive. The issue is whenever i use 'cmd' in phone's fastboot mode, then i can see the phone alongside its serial number but whenever i open xiaomi unlock tool, then it dissapears and doesnt show up neither in the tool nor in cmd box.
Can anyone help?
Open xiaomi tool then plug the phone on fastboot mode after
Gonime said:
Open xiaomi tool then plug the phone on fastboot mode after
Click to expand...
Click to collapse
I had also tried to plug my phone after opening mi unlock tool. N see it doesn't work. Neither my phone shows in cmd nor in mi tool even my pc doesn't recognize anything after plugging cable.
But as I close mi tool again it starts showing in cmd
Is there aren't different versions of xiaomi tools ? maybe with a newer or older version ?
other usb port?
other pc ?
Have you made all the things in dev mode on your phone ?
EDIT : maybe it can help
I installed ADB and fastboot drivers correctly and xiaomi drivers. It detects when i use my phone turned on but when i go to fastboot i get (waiting for device) and it doesnt get detected with mi unlock tool. what do i need to do? My nexus 5 gets detected with fastboot but not my note 7
dlsygaco said:
I installed ADB and fastboot drivers correctly and xiaomi drivers. It detects when i use my phone turned on but when i go to fastboot i get (waiting for device) and it doesnt get detected with mi unlock tool. what do i need to do? My nexus 5 gets detected with fastboot but not my note 7
Click to expand...
Click to collapse
Check you have disabled driver signature verification in windows.Most if not all xiaomi drivers are uncertified.Just google it for your windows version and will give you the options.Solved it for me.
Finsnevis said:
Check you have disabled driver signature verification in windows.Most if not all xiaomi drivers are uncertified.Just google it for your windows version and will give you the options.Solved it for me.
Click to expand...
Click to collapse
How do i check it? I did the permanent thing in cmd with bcedit test signing on etc
dlsygaco said:
How do i check it? I did the permanent thing in cmd with bcedit test signing on etc
Click to expand...
Click to collapse
Normally on windows 7 you will get test mode after disabling driver signature verification as in screenshot.For mi unlock remember your pc needs to be connected to wifi and your phone must have a data connection or it will not work.
Finsnevis said:
Normally on windows 7 you will get test mode after disabling driver signature verification as in screenshot.For mi unlock remember your pc needs to be connected to wifi and your phone must have a data connection or it will not work.
Click to expand...
Click to collapse
Mine has test mode on the side. My pc is connected to a wifi and my phone can go data. But i thought u had to turn it off after veifying? Like go to fastboot mode
dlsygaco said:
Mine has test mode on the side. My pc is connected to a wifi and my phone can go data. But i thought u had to turn it off after veifying? Like go to fastboot mode
Click to expand...
Click to collapse
Nothing really you can do in adb until bootloader is unlocked.You probably know you need oem unlock and you need to connect to mi cloud when unlocking and there is another setting in dev options to sign in to account.Xiaomi now require pc connected to wifi and phone connected to data so both can communicate through mi cloud to unlock.Phone must be connected to data not wifi.
Whenever I go to fastboot the computer recognizes the phone but as soon as I open Mi Unlock Tool or MiFlash Tool, the device disconnects and a message appears on the corner of the screen saying to press the volume buttons to turn off the device, nor the Mi Unlock nor MiFlash detects the device, could anyone help me?
I tried to install the qualcomm usb drives, tried different versions of Mi Unlock/PC Suite and nothing works
Hexvessel1992 said:
Whenever I go to fastboot the computer recognizes the phone but as soon as I open Mi Unlock Tool or MiFlash Tool, the device disconnects and a message appears on the corner of the screen saying to press the volume buttons to turn off the device, nor the Mi Unlock nor MiFlash detects the device, could anyone help me?
I tried to install the qualcomm usb drives, tried different versions of Mi Unlock/PC Suite and nothing works
Click to expand...
Click to collapse
I have the same issue. Driver installed with miflash_unlock. When i start the Fastboot the driver isnt found.
Have you tried opening Mi Flash as admin on Windows?
worked with me buying a USB hub, I don't know if it's a problem with the motherboard usb drivers, but with the hub the mi flash and unlock tool
detect the device now, you can buy one of these cheap hub with 4 usb ports