Hello everyone,
I start by saying that so far I have owned and unlocked at least 5 Xiaomi devices, so a little experience I think I have accumulated.
Today I wanted to unlock the bootloader of my Mi Note 10. I arm myself with patience, download everything i need (miunlock, miflash for the drivers).
Usb debugging activated
OEM release activated
I add Account on Mi unlock
I start miunlock
I put the smartphone in fastboot
The pc does not detect it --- Nothing, no sound and miunlock stuck on "connect device".
I open Adb (always present on the PC), I restart the device, I connect to the PC, it is recognized
Adb Devices --- ok, it is recognized
adb reboot bootloader --- ok it is restarted in fastboot
fastboot device --- Nothing! no sound of reconnection and remains stuck on Waiting Device (I open the device manager of Win 10 and if I disconnect / reattach it does not even go the typical update of the connected devices)
I doubt whether the cable ... I try 4 cables but nothing
I doubt whether the USB port ... I try them all but nothing
I doubt both the pc ... I try to landline, but nothing, same problem
I doubt whether Win 10 ... I brush up on the old pc with win 7, but nothing
I doubt whether I am the problem ... I resume the Redmi Note 7, the same procedure and in a moment everything went.
In short, it seems that from fastboot no signal arrives to the pc, I can't understand if I skipped some new passage or if it is a problem of the device, so I ask you if you have any suggestions to meet me.
I thank you in advance for the attention and help you will offer !!!
Disable driver signature in win 10 and install drivers from mi unlock tool zip.
Hudinited said:
Disable driver signature in win 10 and install drivers from mi unlock tool zip.
Click to expand...
Click to collapse
I do it, but nothing... Today i tried also with win xp but nothing, no new device in device manager
Related
Similar questions to this have been asked before but got no replies so, in desparation, am asking again.
Bought my phone second hand. On starting, it shows the Vodafone logo so assume it's branded.
About Phone -> Software Information shows:
Android Version: 2.3.5HTC Sense version: 3.0Software number: 2.10.161.5
HBOOT shows:
*** UNLOCKED ***SAGA PUT SHIP S-ON RHHBOOT-2.00.0002
Now for the problem:
I'm trying to set S-OFF and root the phone but my PC, running Windows 10, is unable to communicate with the phone when it's in Recovery mode.
The entry for My HTC under Android USB Devices in Device Manager disappears once I start the phone in Recovery mode and connect it to my PC via a USB cable.
At this point Device manager on my PC shows under USB Controllers an entry for an unknown USB Device (Device failed enumeration) and the Hardware Ids show as USB\UNKNOWN.
I'd really appreciate someone familiar with this area throwing some light on what could be going on here and perhaps giving me some pointers on how to resolve this.
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Layer_DE said:
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Click to expand...
Click to collapse
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
bacoms said:
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
Click to expand...
Click to collapse
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Layer_DE said:
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Click to expand...
Click to collapse
If I can drum up any enthusiasm to continue, I'll try and borrow a PC running Windows 7 and try again.
Hello,
Had the phone for 2 years, and I was using a Google Pixel UI. I had some problem with phone auto rebooting while not in use. So I decided to install MUI, but I forgot its only in Chinese without google play.
So I have tried to install the TWRP recovery, but the fastboot is not recognized by the computer.
I have tried Xiaomi Poco X3, and fastboot its working fine on it. So its not issue with the cable.
I have installed some drivers, but it didnt help. I have tried most of the options, so not sure what I'm missing. Will try tomorrow, a different PC at work. MiFlash also cant see it.
Thanks for any help.
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Any leads on the above problem guys?
Disable driver signature enforcement and download mi flash tool. It will prompt you to install all the drivers. Install them and check if it works. For me this was the solution. Another solution is to download the latest drivers from android at https://dl.google.com/android/repository/platform-tools-latest-windows.zip for windows and install it manually by using device manager. This fixes are of course only for windows
On my PC, I didn't try other devices in fast boot mode but I know that my redmi note 7 pro wasn't displaying even after installing those Google/phone drivers.
It eventually worked when I opened Device Manager and saw that my phone was showing as Unknown Device; I clicked on the option to update the driver from a folder on my PC, so I selected the folder containing the android_winusb.inf file and it worked
sumitsky33 said:
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Click to expand...
Click to collapse
If you get solutions then please tell us
Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?
Try installing usb drivers or the phone will never be detected.
VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting
Install windows on partition 30Gb, change cable
yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
tarek._.n said:
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
Click to expand...
Click to collapse
Update : I used another pc, an amd laptop and used the tool all in one made by @mauronofrio and it worked perfectly, saving me from hours of trying things, so thank you for that!
I usually avoid this drama by disabling driver signature before installing OnePlus drivers on windows 11. Always works.
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?