I'm trying to unlock the bootloader on my XT1622.
I can transfer files etc and backup when connected to PC and in Windows
I have installed the drivers and fastboot and adb and opened a cmd window in Admin mode in the directory where fastboot.exe and adb.exe are installed.
I have restarted the phone in fastboot mode (power up plus Vol Down) and connected by USB cable to my PC but when I type adb devices I get no information coming back.
Does anyone have any idea, please, where I may be going wrong?
Anyone able to help, please?
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
actomox said:
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
Click to expand...
Click to collapse
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Still no show
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
pastorbob62 said:
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Click to expand...
Click to collapse
actomox said:
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
Click to expand...
Click to collapse
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Still no joy
negusp said:
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Click to expand...
Click to collapse
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
actomox said:
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
Click to expand...
Click to collapse
Did an RSA key dialogue ever pop up when you plugged it into your PC?
If fastboot shows no devices when your phone is in fastboot mode (voldown+power hold), then something is seriously off. Have you tried multiple USB cables?
On your wife's PC did you make sure to install adb/fastboot and drivers: https://forum.xda-developers.com/showthread.php?t=2588979
And make sure to run the cmd shell as administrator/root? (right click cmd, click run as admin)
Will double check everything
Will double check all of those pointers over the weekend and report back. Thanks
Success at last
Went onto my wife's computer and deleted all that I could find relating to SDK and Motorola. Re-installed adb tools and the Motorola drivers and now adb devices return the details of the connected phone. Onto the next stage of unlocking the bootloader and then rooting. Thanks for the help.
Related
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
need use QPST (http://forum.xda-developers.com/showthread.php?t=2588608&page=5)
but this way not completed until the end of
I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?
epicfailol said:
I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?
Click to expand...
Click to collapse
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.
GSLEON3 said:
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.
Click to expand...
Click to collapse
I used getvar, and it worked fine (but most the of parameters don't), boot and idme don't work because it's locked, and oem unlock doesn't exist. But what your saying is that I shouldn't even be able to do any of this?
i look at the picture and the kindle is not hdx.
i've searching for fastboot cable on ebay but didn't found, the cable only work for kindle HD
so for there is no fix for bricked kindle fire hdx
You can turn HDX into fastboot mode by "adb reboot bootloader" if device is alive.
But you can not flash anything anyway - error "flash not allowed for locked hw".
Fastboot cable perfect fit to HDX too. But it turn device in Qloader for QPST.
epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
Try "fastboot -i 0x1949 yourcommandhere"
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!
I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!
Did you type 'su' after opening ADB/command prompt?
No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!
Use "fastboot devices" "fastboot oem unlock".
I want to install the AOSP on the x compact.
I unlocked the bootloader but when I type
Code:
adb devices
no devices is recognized. I installed the fastboot tool too. I booted into fastmode with holding the volume up button when connecting but no device is recognized. I also factory reset the phone without luck to run the
Code:
fastboot
Maybe you need to allow your computer when it's asked on the phone.
evilorb said:
Maybe you need to allow your computer when it's asked on the phone.
Click to expand...
Click to collapse
what you mean when is phone is fast boot there has no display controls
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
evilorb said:
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
Click to expand...
Click to collapse
I authorized the phone but still not able to run fastboot commands when I go into fastboot mode with the blue led
But now you see your phone in terminal when you type "adb devices" ?
evilorb said:
But now you see your phone in terminal when you type "adb devices" ?
Click to expand...
Click to collapse
in the normal system mode then I can see it but not in the fastboot mode
Adb won't work in fastboot mode. Try "fastboot devices" when in fastboot mode.
When phone is turned off and connected via usb (vol+) to pc then type:
fastboot devices
When phone is turned on and connected via usb to pc (usb debugging on) then type:
adb devices
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)