When I connect the phone (SCH-I545, verizon) to the PC, I see two choices shown under the pulldown menu: Connect as Media Device (MTP), or Camera (PTP). And the MTP choice is checked automatically.
I believe my phone has the latest OTA update. And I have turned on the Developer Option, check the "USB Debugging".
Did I miss anything? Please help.
newshook said:
When I connect the phone (SCH-I545, verizon) to the PC, I see two choices shown under the pulldown menu: Connect as Media Device (MTP), or Camera (PTP). And the MTP choice is checked automatically.
I believe my phone has the latest OTA update. And I have turned on the Developer Option, check the "USB Debugging".
Did I miss anything? Please help.
Click to expand...
Click to collapse
Are the drivers installed?
When you plugged in your phone, did the permission prompt for ADB appear?
What devices show up in the Windows device manager? (Windows/Break, then device manager.) You should see a "Samsung Android ADB Interface" appear if all is correct.
Yes, the drivers are installed. I first installed the samsung usb driver, I installed the kies package given I don't see the USB debugging permission message. Just tried the same thing in ubuntu, same result.
I must have missed something.... Just don't know what it is ....
The phone's developer option is on and debugging is checked,
On PC side the driver is installed. In fact, when I tested this in ubuntu, I ran "adb devices", it saw the phone ....
k1mu said:
Are the drivers installed?
When you plugged in your phone, did the permission prompt for ADB appear?
What devices show up in the Windows device manager? (Windows/Break, then device manager.) You should see a "Samsung Android ADB Interface" appear if all is correct.
Click to expand...
Click to collapse
Got it!
The message showed up after I toggled between those two choices. It was done in ubuntu. Thanks very much.
k1mu said:
Are the drivers installed?
When you plugged in your phone, did the permission prompt for ADB appear?
What devices show up in the Windows device manager? (Windows/Break, then device manager.) You should see a "Samsung Android ADB Interface" appear if all is correct.
Click to expand...
Click to collapse
This device is not supported. HELP!
Hi!
I have done everything mentioned above, but I get an error during the install. Have attached a print screen from the install.
Please help me.
Without working SIM atm because operator lock code recieved from my mobile operator doesn't work.
Best regards
Oscar.
Deleted
Sent From My Verizon S4
92oscbra said:
Hi!
I have done everything mentioned above, but I get an error during the install. Have attached a print screen from the install.
Please help me.
Without working SIM atm because operator lock code recieved from my mobile operator doesn't work.
Best regards
Oscar.
Click to expand...
Click to collapse
The "this device is not supported" message means that your phone (m0? What's that?) is patched by the vendor to fix the flaw that Saferoot uses to root it.
You'll have to find another tool to root your phone.
Thank you!
k1mu said:
The "this device is not supported" message means that your phone (m0? What's that?) is patched by the vendor to fix the flaw that Saferoot uses to root it.
You'll have to find another tool to root your phone.
Click to expand...
Click to collapse
Okei! Thank you for your help. It is a Galaxy SIII.
Just managed to update to Android 4.3 Jellybean at the same time as I changed mobile network operator. Mobile was locked and the NCK code from operator didn't work. Probably need the MCK (Defreeze) code to unlock which operator doesn't have access to. So no mobile phone for me atm.
I used VRoot and used a change-to-SuperSu guide and it worked. Couldn't find anyway to remove the network lock though..
Couldn't post the links on how I rooted and changed to SuperSu since I'm a n00b at this site.
And sorry for maybe posting this in wrong thread!
Best regards
Oscar
Related
Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Did you try closing HTC Sync Manager?
Make sure and exit completely, right click and exit in the system tray
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
TheEmpyre said:
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
Click to expand...
Click to collapse
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
jonathan413 said:
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
Click to expand...
Click to collapse
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
an0ther said:
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
Click to expand...
Click to collapse
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
TheEmpyre said:
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
Click to expand...
Click to collapse
there is no other drivers showing up other than HTC's. and ive reinstalled it at least three times. everything is working except ADB recognizing the phone.
jonathan413 said:
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
Click to expand...
Click to collapse
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
an0ther said:
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Click to expand...
Click to collapse
thats already checked. just unistalled all duplicate drivers and started fresh. now there is 3 drivers not installing. CDC serial, Android phone, and CDC serial again. not sure why that one installs twice but it failed anyway..those 3 will not install for the life of me.
TheEmpyre said:
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
Click to expand...
Click to collapse
in the toolkit it says "device not found"..when i run ADB devices it says "list of devices" but shows nothing. Now when i run the command it says in missing some .DLL extension file
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
TheEmpyre said:
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
Click to expand...
Click to collapse
ok i followed your instructions and yes all the drivers installed correctly, thank you. BUT now i run the toolkit and now it says "error: device offline".
an0ther said:
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
Click to expand...
Click to collapse
not sure. i dont keep ADB on my computer. I download it only when I need to. But i followed the instructions from the other user but now i get this message. "error: device offline".
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
TheEmpyre said:
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
Click to expand...
Click to collapse
ok so i ran the toolkit for the 3rd or 4th time and it rebooted in fastboot to obtain my token to unlock. but when i enter the token into htcdev website it keeps saying its wrong length. i checked over and over and its the right length and im copying what i see from the htc dev website instructions but three times i get wrong token length.
ok i got the code to work..now onto the next step.if i have problems ill be back here.
ISSUE RESOLVED. See post #17 for solution.
Hi, I have a Redmi Note 4 Qualcomm variant with MIUI Global 8.5 | Stable 8.5.4.0 (NCFMIED) ROM. I want to unlock the bootloader but MI Unlock Tool (v2.3.803.10) cannot recognize the phone in fastboot mode. I've gotten the permission to unlock.
I've tried v2.2 of the tool and encountered same problem. Tried multiple drivers, plugging phone in/out. Running "fastboot devices" command shows the device is connected. Tried installing Mi Driver that came with the tool but its setup says it's installed while the unlock tool says it isn't.
Suggestions appreciated. Thanks.
Note: I'm running Win 10 x64 Creator's Update (15063).
Hexerus said:
Hi guys, I have Redmi Note 4 Qualcomm Global variant with MIUI Global 8.5 | Stable 8.5.4.0 (NCFMIED). I want to unlock the bootloader but MI Unlock Tool (v2.3.803.10) cannot recognize the phone (connected in fastboot mode). I have gotten the permission to unlock. I'm running Win 10 x64 Creator's Update build 15063.
I've tried v2.2 of the tool and encountered same problem. Tried multiple drivers, plugging phone in/out. Running "fastboot devices" command shows the device is connected. Tried installing Mi Driver that come with the tool, its setup says it's installed but the unlock tool says it isn't. Really confused right now.
Any suggestion appreciated.
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?
No you didn't
Stevica Smederevac said:
Did you enable usb debugging in developer options?
No you didn't
Click to expand...
Click to collapse
Yes I did Enabled both OEM unlocking and USB debugging. For a person to unlock phone / flash ROM, expect him to at least know this.
Hexerus said:
Yes I did Enabled both OEM unlocking and USB debugging. For a person to unlock phone / flash ROM, expect him to at least know this.
Click to expand...
Click to collapse
I don't expect anything, sometimes you have to start from the beginning. . With that attitude,i have nothing more to say.
Stevica Smederevac said:
I don't expect anything, sometimes you have to start from the beginning. . With that attitude,i have nothing more to say.
Click to expand...
Click to collapse
I'm really sorry if it offended you. Didn't mean to be rude. It's late night and I'm really tired trying again and again with different changes. Googling didn't end up with satisfactory solutions so posted in a few forums. Apparently everyone is past this stage and into 50% and account binding errors. I don't know why I'm stuck here. Even MiFlash detects the phone but not Mi Unlock.
Again I'm sorry for that comment. I should have written it in OP.
Disable driver enforcement in windows 10 and then try again from start.
Hexerus said:
I'm really sorry if it offended you. Didn't mean to be rude. It's late night and I'm really tired trying again and again with different changes. Googling didn't end up with satisfactory solutions so posted in a few forums. Apparently everyone is past this stage and into 50% and account binding errors. I don't know why I'm stuck here. Even MiFlash detects the phone but not Mi Unlock.
Again I'm sorry for that comment. I should have written it in OP.
Click to expand...
Click to collapse
So many things are now installed that it would be a good idea to uninstall as much as possible including drivers.
After that install one version of unlock tool and try again.
Pretty confusing that only unlock tool can't recognize the device.
I think you already tried but I'll suggest anyway, try with different USB ports. Maybe you are plugged in usb hub or 3.0 and for some reason unlock tool is not working.
Reboot into bootloader and then type "fastboot devices" in the adb cmd. If it doesn't recognize any fastboot devices then you need fastboot driver. Use universal adb driver for that. Hope it helps.
EDIT: Sorry didn't notice that OP already tried this. I think maybe at this point you should try using a different computer, or log in from a different account on your pc.
small2cats482 said:
Reboot into bootloader and then type "fastboot devices" in the adb cmd. If it doesn't recognize any fastboot devices then you need fastboot driver. Use universal adb driver for that. Hope it helps.
Click to expand...
Click to collapse
But he said it does in fastboot but only not in unlock tool.
Try installing Mi pc suite..! If you have already. Then try reinstalling it.. Then check if your phone gets detected there.
himesh_d said:
Disable driver enforcement in windows 10 and then try again from start.
Click to expand...
Click to collapse
Did that. No luck. Although, I'm wondering why I didn't get this red "Can't verify the publisher" message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
It's assumed to be the reason for disabling driver signature enforcement according to many tutorials around the web. It is supposed to come when MiFlash is being installed but I didn't get it while installing MiFlashSetup_eng.msi (latest MiFlash tool).
Stevica Smederevac said:
So many things are now installed that it would be a good idea to uninstall as much as possible including drivers.
After that install one version of unlock tool and try again.
Pretty confusing that only unlock tool can't recognize the device.
I think you already tried but I'll suggest anyway, try with different USB ports. Maybe you are plugged in usb hub or 3.0 and for some reason unlock tool is not working.
Click to expand...
Click to collapse
Yes, exactly. I first installed Universal ADB drivers that gets installed in Program Files/Clockwork something folder. Then I downloaded ADB driver installer from here: http://adbdriver.com/. They have a GUI tool that apparently show whether drivers are correctly installed or not when you plug in your phone, and prompts to install if not. It showed a green dot, so I didn't install it. Then, since it wasn't working (the tool), I tried ADB 1.4.3 from here (XDA). Same result. I also tried Xiaomi's own driver that come with Unlock tool with its own setup. That is also not working, unfortunately. Every time, adb.exe and fastboot.exe recognizes phone in their respective modes, but not the tool.
I've tried uninstalling and reinstalling drivers through Device Manager, as there seems to be no folder in C: and no entry in Programs and Features for any driver. I think I have to try another PC. Not sure if a virtual machine would do (I can setup a Win7 VM just for the sake). Finding another PC would require waiting
And yes, tried different ports.
zerohunk said:
Try installing Mi pc suite..! If you have already. Then try reinstalling it.. Then check if your phone gets detected there.
Click to expand...
Click to collapse
Regarding MI PC suite, I installed it a few weeks ago and it wasn't detecting the phone, even with the ADB drivers installed and USB debugging and everything turned on. I googled it and found out that Xiaomi hasn't updated it to support devices running Marshmallow or later. It only works with Lollipop and prior devices. So yeah I will try but I think the result will be same i.e. phone won't get detected.
Hexerus said:
Yes, exactly. I first installed Universal ADB drivers that gets installed in Program Files/Clockwork something folder. Then I downloaded ADB driver installer from here: http://adbdriver.com/. They have a GUI tool that apparently show whether drivers are correctly installed or not when you plug in your phone, and prompts to install if not. It showed a green dot, so I didn't install it. Then, since it wasn't working (the tool), I tried ADB 1.4.3 from here (XDA). Same result. I also tried Xiaomi's own driver that come with Unlock tool with its own setup. That is also not working, unfortunately. Every time, adb.exe and fastboot.exe recognizes phone in their respective modes, but not the tool.
I've tried uninstalling and reinstalling drivers through Device Manager, as there seems to be no folder in C: and no entry in Programs and Features for any driver. I think I have to try another PC. Not sure if a virtual machine would do (I can setup a Win7 VM just for the sake). Finding another PC would require waiting
And yes, tried different ports.
Click to expand...
Click to collapse
I also ha windows 10 and minimal adb and fastboot tool. I didn't require any other drivers. My phone is recognized in every situation
Hexerus said:
Regarding MI PC suite, I installed it a few weeks ago and it wasn't detecting the phone, even with the ADB drivers installed and USB debugging and everything turned on. I googled it and found out that Xiaomi hasn't updated it to support devices running Marshmallow or later. It only works with Lollipop and prior devices. So yeah I will try but I think the result will be same i.e. phone won't get detected.
Click to expand...
Click to collapse
My Rn4 was on android nougat stable ROM when i installed mi pc suite and it did get detected.. I do remember while installing it asked me if i wanted to install drivers.. Click on yes! I think that will do it for you!
zerohunk said:
My Rn4 was on android nougat stable ROM when i installed mi pc suite and it did get detected.. I do remember while installing it asked me if i wanted to install drivers.. Click on yes! I think that will do it for you!
Click to expand...
Click to collapse
Mine says "Connect your device via USB" as soon as a plug phone. I too have nougat stable version. Which PC suite version do you have? I have 3.2.1.3111. It didn't prompt for any driver installation. Do you enable USB debugging while connecting to PC suite? Tried MTP and PTP modes, still the same.
Edit 1: Sometimes getting the "You need to update your device to use Mi PC suite..." a few moments after the previous error.
I finally went past this step. Here's my short guide to resolve the issue:
Note: I'm using Mi Unlock tool version 2.3.803.10 on Windows 10 x64 build 15063. This is the tool's latest version as of 28 August, 2017.
1. Extract the zipped archive of MI Unlock tool to a new folder in the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, making the path of the tool's executable: "C:\unlock\miflash_unlock.exe".
2. Run MiUsbDriver.exe from the folder as administrator and, even if it already says "Driver installed", click "Install" to make sure. Click "Retesting" to see if it says the same. Close the program.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
If it's not then:
(a) Close the properties window.
(b) Right click android bootloader interface and click "Update driver".
(c) Click "Browse my computer for driver..." -> "Let me pick from a list ...".
(d) Uncheck "Show compatible hardware".
(e) Select "Xiaomi Technology, Inc." from the left side and "Android Bootloader Interface" from the right and click next.
After it's installed, check the properties -> driver tab of "Android Bootloader Interface" to make sure driver provider, date and version is what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Here, MI Usb Driver should say "Already installed". If it doesn't, it won't work. In that case, you can check/re-do steps 1-5 to see if it helps. No idea beyond that.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, so the path of the tool's executable became "C:\unlock\miflash_unlock.exe"
2. Run MiUsbDriver.exe from the folder with as administrator and click "Install". Make sure it says "Driver installed" after that. If it already says that, hit install again just to make sure. Click "Retesting" to see if it remains the same. Close the program after.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
IF it's not, then close the properties window, right click android bootloader interface and click "Update driver". Click "Browse my computer for driver..." then "Let me pick from a list ...". Uncheck "Show compatible hardware", click "Xiaomi Technology, Inc." from the left side, then "Android Bootloader Interface" from the right and click next. After it's installed, check the properties to make sure it says what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Make sure MI Usb Driver says "Already installed". This is really important. Otherwise IT WON'T WORK. If it doesn't say that check previous steps and make sure your didn't miss any. Beyond that I have no idea.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
You are a LIFESAVER... Having spent more than 12 hours searching the internet..... Thanks again.
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
Hey Bro!!!!! I had made an account on XDA just & just to write this THANKFUL comment. Hell Lot of THANKS Buddy!!
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, so the path of the tool's executable became "C:\unlock\miflash_unlock.exe"
2. Run MiUsbDriver.exe from the folder with as administrator and click "Install". Make sure it says "Driver installed" after that. If it already says that, hit install again just to make sure. Click "Retesting" to see if it remains the same. Close the program after.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
IF it's not, then close the properties window, right click android bootloader interface and click "Update driver". Click "Browse my computer for driver..." then "Let me pick from a list ...". Uncheck "Show compatible hardware", click "Xiaomi Technology, Inc." from the left side, then "Android Bootloader Interface" from the right and click next. After it's installed, check the properties to make sure it says what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Make sure MI Usb Driver says "Already installed". This is really important. Otherwise IT WON'T WORK. If it doesn't say that check previous steps and make sure your didn't miss any. Beyond that I have no idea.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
Thank you, you solve my problem I try almost everything and the problem continues, your guide solve my issue with the USB drivers, good work
Found a password locked device : VIVO Y69. MTK6750. i tried to unlock it using Tools such as MRT, Miracle box and others but was Unsuccessful. the problem is that , my PC/Laptop was unable to detect it.... yes, i have already installed all the necessary MTK drivers, such as DA USB, Vcom , Preloader and so on .....
well, when i connect the device to the USB ports, it shows the "Charged only" sign to the battery icon on the device without making a sound or detecting it , not in the Device Manager.
i think the owner puts the device to "Charged only option"...
Any idea to make it detect, i mean like the Test Point or something.
Thank you all..
K4bini.
As long as Android's USB service isn't configured as ADB and/or MTP phone won't get detected.
0
jwoegerbauer said:
As long as Android's USB service isn't configured as ADB and/or MTP phone won't get detected.
Click to expand...
Click to collapse
Wow, i see..... so any idea to go around to configured to ADB/MTP? ..... no right?.. ok....
Seppppx said:
You found that phone?
If it's not yours you should find the owner instead of trying to unlock the phone.
Just imagine if this happened to you.
If you are doing the right thing, try to see if the owner put some of his information to the emergency information of the device.
When the phone is on the lockscreen
1. Swipe up.
2. Click "EMERGENCY" on the bottom.
3. Double tap "EMERGENCY INFORMATION"
And you should see if the owner put anything in there.
This processes might be different depending on the custom OEM skin.
Click to expand...
Click to collapse
there's no emergency information on the device, and yes , the process of accessing emergency information varies on devices... besides, i search and research the internet, and no one have experienced what i had. i will try and figured out myself and post a story on xda once successful.
So I have been trying to root my Moto G Power 2021 all day. I have been following the guide to using Magisk the non-twrp way, and I keep hitting the same snag over and over again. So far, I have successfully unlocked the bootloader, downloaded and installed the latest Magisk apk (Magisk25.2.apk) form the github page, and downloaded and installed the official Rescue and Smart Assistance (LMSA) on my computer. The problem that I am having is that whenever I plug my phone into my computer while I have RSA open, it asks me to authorize the computer to use it, but nothing opens on my phone to give me that option.
Before I am asked, yes I have Developer tools unlocked, the OEM is unlocked already (As I said above), and I have made sure that USB Debugging was allowed.
Please, tell me where I'm going wrong with this if anywhere?
The only other information I can think to add is that my phone IS running Android 11, but I'm unsure if that matters as I have seen other guides that explain how to root on Android 11.
Thanks in advance for any information that can be given!
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.cust...can-i-download-the-usb-drivers-for-my-device?
sdembiske said:
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Click to expand...
Click to collapse
Yes I did. I also tried uninstalling and reinstalling it when you linked it in case I didn't have it installed correctly, and that still did not work.
The below image is what I keep getting when I attempt to connect to RSA with my phone, and nothing at all like that shows up on my phone to verify.
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Thanks! I'll give that a shot and update when I've got a chance. I don't believe it's the USB cable since it's the cable that came with the phone, so I'll try the antivirus/firewall software side of things first.
Small edit:
I forgot to actually answer your question before. No, I hadn't already authorized this computer, as this is actually a pretty new computer (Only a few months old at this point). The USB debugging shows up at the top of my phone yes, but RSA won't do anything unless I authorize it, which gives me conflicting impressions that the phone seems to think it's verified the computer, but the computer and program don't see the verification.
sdembiske said:
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Click to expand...
Click to collapse
Thank you! That worked! I was able to get it sorted out, AND following the root guide, I was able to get my phone rooted too! Thank you very much again!
@Cloud557 How did you unlock bootloader? I have cricket moto g power 2021 but I checked with Motorola and apparently this model cannot be unlocked? Thanks