Hey! I need help, please. I'm trying to unlock bootloader of the Moto C XT1756, it has a MT6735. So, I tried in Windows and in Linux (linux with 2 pc). And the problem is next.
I installed ADB and Fastboot (I tried minimal, 15 seconds, platfoorm tools, all). So, ADB detects the device, I can use any adb command like the "adb reboot bootloader". It reboot in fastboot mode and if I use "fastboot devices" it is detected. But when i'm trying to use "fastboot oem get_unlock_data" it says me "failed, unknown command." It happen also with any oem command. I don't know how to proceed. If someone can help me, i'll be grateful. Thanks for read
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Oh. So, I'll test your ADB-FASTBOOT installer, really thanks!
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.
jwoegerbauer said:
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Click to expand...
Click to collapse
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.
I see you didn't get it.
Manufacturers implement ADB and/or Fastboot with version what corresponds to their ideas.
Hence in your case some ADB and/or Fastboot commands may work or not.
Oh. So, this phone can't be unlocked?
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
jwoegerbauer said:
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
Click to expand...
Click to collapse
I didn't get the second sentence. "Use Motorola's "Android USB Driver". Btw, I used "mfastboot.exe devices" and it recognizes my phone, then "mfastboot.exe oem get_unlock_data" and it keeps saying "failed: unknown command."
Update: I tried three different wires. Three different PC (Including Linux-PC) and the error is the same. I can't understand it. It have an option "Unlock OEM" in Developer Settings (so, I think that the manufacturer allows unlock) I can't do nothing.
Related
[Q] Stuck in "Starting Fastboot Protocol Support" when trying to flash stock images
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
philski421 said:
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
Click to expand...
Click to collapse
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
bwcorvus said:
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
Click to expand...
Click to collapse
thats where I have no clue what hell is going on, if I type in flash blah blah it says waiting for device
i have the same issue, I'm I reboot via adb and then my xoom reboots and says starting fasboot protocol support and just sits there. Any help or idea why?
answered my own question. This is because my device has not been unlocked yet.
I had to do the fastboot oem unlock found here.
http://forum.xda-developers.com/showthread.php?t=967065
Only thing I can suggest is to check to make sure you have your drivers installed and ready for fastboot. I think one of the commands you can throw at it is fastboot devices which should do the samething as adb devices but use for fastboot (but can't remember, been awhile since I've had to do anything with fastboot). If that is an acceptible command then you should see your device listed, if not then your computer isn't seeing the device which is why it's saying waiting for device.
You might also want to try throwing the fastboot oem unlock command again and see what happens (it's possible that you've never actually unlocked the xoom).
This is only a few suggestions I can give you for now as I'm not at home to try throwing some of those commands myself to confirm they're valid commands or not, sorry.
drivers are installed that's how I did the original unlock. and I'm sure I hit accept. I went through the whole process of losing everything when doing so. no dice on being able to flash . and the weird thing is this. when I type in adb reboot bootloader it reboots to the fast boot protocol screen but when I type in the info to flash the recovery I get the error of can't load
I'm having the same problem, I simply can't boot into FASTBOOT. I've got the latest USB drivers, I've updated ADB, but it just won't work. It just sits there telling me "Starting fastboot protocol support".
Very frustrating, nothing I do seems to fix it - I've even done a factory reset.
Edit: Now it won't even respond to "fastboot oem unlock", it just sits there saying "<waiting for device>" even though the device shows fine when I do "adb devices" and the device also shows in Windows. (Is this simply because the device is already unlocked)
Are you sure USB debugging is enabled?
Sent from my GT-I9000 using XDA Premium App
Yep, it is
Edit: By the way, if I do "fastboot devices" nothing is listed. If I do "adb devices" it lists the XOOM just fine.
Edit again: Just noticed that the OP also used the "rootmyxoom" process, which is exactly what I used and I'm having the same issues he's having... hmm.
Hi guys,
Looking for a genuis here...I've spent the last few days trying to work this puzzle out:
Installing GrapheneOS onto Pixel 3 phone using Windows 10, using command line tools only. Android Studio is not installed on the PC.
Here's what I've done so far...downloaded:
The Pixel image - GrapheneOS stable channel for Pixel 3
ADB & fastboot
First we downloaded fastboot (ADB, Android SDK platform-tools for Windows): https://developer.android.com/studio/releases/platform-tools - had an issue with the fastboot flashing unlock command...it doesnt unlock the device, instead says <waiting for any device>
Then we deleted the SDK platform tool and installed Minimal ADB & Fastboot and the same darn issue happened - the fastboot flashing unlock command doesnt unlock the device... command prompt says <waiting for any device>
The device is carrier unlocked, OEM unlocking enabled, USB debugging enabled, File transfer (MTP) mode on.
The following commands work with the SDK platform-tools & minimal ADB & Fastboot: adb devices, adb reboot bootloader
The block is the command: fastboot flashing unlock as we keep getting <waiting for device>.
Tried to fix this myself, here's what has been tried so far (not necessarily in this order):
Checked Fastboot version... fastboot --version works for both downloads so it's recognising it! Wahoo.
Used command prompt & powershell - when it gets to the fastboot flashing unlock command the response is always <waiting for device>
Checked the PATH (in control panel / advanced setting) and made sure environmental variable goes to the right folder
Downloaded Google USB Driver - nothing changed, we already had up-to-date drivers
Tried to change the fastboot script, click to open the fastboot file, when I click "open" the command prompt pops up, red error message flashes then the command prompt window closes in the blink of an eye. I then turned off Windows secuirty setting for app, same thing still happens.
Tried all USB ports with USB-C cable - same error <waiting for device>
Tried all USB ports with anotehr USB-C cable - same error <waiting for device>
Please help!
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
jwoegerbauer said:
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
Click to expand...
Click to collapse
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Redsquirrel77 said:
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Click to expand...
Click to collapse
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
jwoegerbauer said:
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
Click to expand...
Click to collapse
Thanks so much, I think we are getting closer to success!
Qualcomm USB driver downloaded and successfully installed.
Update since the Qualcomm USB driver download:
adb reboot bootloader command works - phone goes into fastboot mode
fastboot devices - no response (new command line)
fastboot - -version shows version and installation
fastboot flashing unlock response is still <waiting for any device>
Used command adb shell getprop ro.boot.cid and response is 00000000
Response should be 11111111 if it's a Google phone...is this my issue? Or does it help explain why fastboot isn't working?
Fastboot operates on device's bootloader only if unlocking bootloader isn't denied. Makes sense,, doesn't it?
Me and all my friends always test this by running
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported" <- on some devices: adb shell "getprop sys.oem_unlock_allowed"
If returned value is 1 - or true, then it's supported otherwise it's not.
Hi,
I don't know if it will help but try this.
PROBLEM
I tried all manner of ADB drivers and fastboot drivers for the last 4 hours just so that I am able to oem unlock this OnePlus device.
I have all OnePlus drivers installed. I have the ADB drivers installed from here. With all these I was able to run adb commands on the phone when it was on including commanding the phone to enter into EDL mode, commanding the phone to reboot into bootloader (fastboot mode). However in once in Fastboot mode, I could not communicate with phone and all I got was "waiting for device".
SOLUTION THAT WORKED FOR ME
It could be a computer brand model. Turns out the problem was not Windows. The problem was not Oneplus. The problem was my Lenovo Thinkpad which apparently requires its own Lenovo USB drivers.
If at all you're on Lenovo machine and you're stuck on "waiting for device" in Fastboot mode despite trying everything, then try installing Lenovo USB Drivers. I would recommend installing the generic ADB drivers first from here. Then installing the Lenovo drivers that are specific to you machine from here. Mine is Thinkpad.
I really hope this helps if not you, then someone else just about to pull their hair out.
Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.
One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.
tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue
Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers
2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..
I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.
Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol
I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!
I'm trying to unlock the bootloader. When I first connect the phone, I can do 'adb devices' on my pc and it returns:
List of devices attached
1818FDH.... device
I then boot into fastboot mode...
dnewell said:
I'm trying to unlock the bootloader. When I first connect the phone, I can do 'adb devices' on my pc and it returns:
List of devices attached
1818FDH.... device
I then boot into fastboot
Click to expand...
Click to collapse
It's your platform tools/adb/fastboot folder up to date? I'd not update it.
xunholyx said:
It's your platform tools/adb/fastboot folder up to date? I'd not update it.
Click to expand...
Click to collapse
It is....version r33.0.3
dnewell said:
It is....version r33.0.3
Click to expand...
Click to collapse
What does cmd and device manager say when you type "fastboot devices"?
dnewell said:
It is....version r33.0.3
Click to expand...
Click to collapse
OK 2 questions
1 In Developer options is OEM unlocking grayed out?
2 Is your sims in the phone? Because when I did mine I didn't pit the sims in and OEM unlocking was grayed out, So I put it in and it came up. Just something to check out. But I'm not sure that's what your looking for.
No, OEM unlocking is enabled. USB debugging is enabled. also. Sim is installed. When I do 'fastboot devices' in the CMD window, it just comes back with the prompt. Not sure what you are asking about device manager. It shows pixel 7 pro under 'Other devices'. That doesn't change when I do 'fastboot flashing unlock', even though the response in the cmd window is 'waiting for any device'.
dnewell said:
No, OEM unlocking is enabled. USB debugging is enabled. also. Sim is installed. When I do 'fastboot devices' in the CMD window, it just comes back with the prompt. Not sure what you are asking about device manager. It shows pixel 7 pro under 'Other devices'. That doesn't change when I do 'fastboot flashing unlock', even though the response in the cmd window is 'waiting for any device'.
Click to expand...
Click to collapse
When you enter fastboot it should list the device as "android bootloader interface" in device manager. Make sure that you have the P7P device drivers installed from here download and install the driver's. If it's showing "waiting for any device" then it is not connected
When I was in normal mode on the phone, it found MTP USB Device driver in the Google USB driver directory. However, trying to install it says I already have it. When I went to fastboot mode, I had it search my computer for available drivers, and it found Android Composite ADB driver. Should I install that?
dnewell said:
When I was in normal mode on the phone, it found MTP USB Device driver in the Google USB driver directory. However, trying to install it says I already have it. When I went to fastboot mode, I had it search my computer for available drivers, and it found Android Composite ADB driver. Should I install that?
Click to expand...
Click to collapse
Install it and run the "fastboot devices" command. If it shows "android bootloader interface" in device manager your good.
If not you need to manually update using "browse computer" and point it directly to where you downloaded and unzipped the P7P drivers
That worked! I was not trying to install the driver while in fastboot mode, that was the problem! Thank you very much for the help!
dnewell said:
That worked! I was not trying to install the driver while in fastboot mode, that was the problem! Thank you very much for the help!
Click to expand...
Click to collapse
Awesome, glad I could help and it worked for you!