Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.
_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem
Related
please delete thread
deleted
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.
ADB Can't find the device :/
deleted
Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta
raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"
Still wont work
deleted
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"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"
}
Click to expand...
Click to collapse
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??
It worked thank you
deleted
Hi,
I have been trying to connect my Nexus 6 to my work pc but I just can't get the MTP file copying mode to work properly. I have used the latest Google USB driver and actually it's not so bad. With USB Debugging turned ON, I see "Android Deivce > Android ADB Interface" properly installed in device manager. I even see my phone's serial no. when I type "adb devices" in command prompt. BUT the bloody MTP mode just refuses to work. It keeps showing up in Device Manager as "Other devices" > MTP, with a question mark next to it.
{
"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"
}
When I switch USB debug off, there's no Android ADB Interface, and the unknown MTP entry in "other devices" transforms to "Nexus 6", again with a question mark next to it.
I have tried to manually install the proper driver but for starters, if I just select the folder where the .inf files are located Windows don't seem to anything inside it and when I force it to use that file ("Show All Devices > Have Disk") it only shows ADB and Bootloader drivers:
So what am I suppose to choose there in order for MTP to work as it should?
Have you tried other pc or laptop??
Yes, the phone shows up correctly in all modes on my home pc.
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
DebianDog said:
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I did that to no success but in the end, I just tried a different USB2.0 port and it worked, all drivers installed correctly. Now the weird thing is I can read from the internal memory of the phone, I can delete stuff from it, but when I try to copy something to it it says: "Error copying. The device has either stopped responding or has been disconnected" so I can't yet copy to it. This is driving me crazy right now...
I have this issue this morning. Right click and Update Drivers > Browse For Drivers > Let me pick > Portable Devices > Standard MTP Device > MTP Device.
Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.
driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).
Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"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"
}
I guess i have to go on a win7 machine then?
Thanks.
I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy
Hi guys, i have a problem with my device. Htc Desire 500.
I apologize for my english .. I try to make the bootloader to my device , but when I have to write in cmd : fastboot flash unlocktoken Unlock_code.bin .
In my device not I get anything to finally unlock the device .
You know what I can do ?
Attached I send you pictures of my device
{
"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"
}
MrR4nma said:
Hi guys, i have a problem with my device. Htc Desire 500.
I apologize for my english .. I try to make the bootloader to my device , but when I have to write in cmd : fastboot flash unlocktoken Unlock_code.bin .
In my device not I get anything to finally unlock the device .
You know what I can do ?
Attached I send you pictures of my device
Click to expand...
Click to collapse
Type fastboot devices and see if a device name tag gets listed. If not, it means you haven't installed the usb drivers correctly.
Are you on Windows 8 or 10?
To install ADB and Fastboot drivers on Windows 8 and 10, a forum member posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
You can also try WinDroid, it works with Desire 500
http://forum.xda-developers.com/showthread.php?t=2499926
razvangrig said:
Type fastboot devices and see if a device name tag gets listed. If not, it means you haven't installed the usb drivers correctly.
Are you on Windows 8 or 10?
A forum member posted the following solution (not tested) to install Adb and Fastboot drivers on Windows 8 or 10:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Add this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
7. Unplug usb cable and plug again.
8. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
You can also try WinDroid, it works with Desire 500
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Can i use disable driver signature enforcement in windows 8.1 to use adb for this device?Without modifying registry only allow unsigned driver.
{
"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"
}
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
43t34 said:
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
abrfilho said:
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
Click to expand...
Click to collapse
If that doesn't work, try using the Moto specific version of fastboot, called mfastboot.
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Just saw these replies, but this was the option I used to fix it. Tried an older PC downstairs and it worked.
My only issue now is: I have no 4G/LTE at all. Verizon SIM through StraightTalk. I went into APN settings, but everything is greyed out and can’t be edited, or added. When I go into my network settings and set my Preferred Network Type to “LTE only,” I lose all bars and signal. Is this just a Verizon thing or would it work with ATT SIM? Before I got the phone, I did extensive research to make sure it’d fully work on Verizon/StraightTalk, so I’m clueless right now.
A guy named Frank, with StraightTalk live chat, told me that my device isn’t 4G compatible....like, at all. Wth...? They didn’t seem like they knew what I was talking about, though.
ensure motorola drivers are installed and try different USB 2.0 ports.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Worked for me! Thanks for the great help!