I am trying to unlock my device and keep having the problem of it not being recognized in fastboot.
I have the latest drivers from the android SDK (4.0), and have trying reinstalling them. It appears to mount fine, and all of the adb commands work. However, when I try fastboot devices, it returns nothing. fastboot oem unlock only gives a "waiting for device".
Any ideas?
Thanks
Device needs to be in the fastboot screen of the bootloader...
Sent from my Nexus One using XDA App
While I feel really stupid for somehow missing that fact in dozens of threads, it doesn't seem to fix the problem. I now have it in fastboot and at the top is says "FASTBOOT USB". Windows recognizes the device when its plugged in, but still no luck with devices.
Nevermind, I figured it out. It downloaded fastboot from another source. I am guessing that I was somehow missing a file. Thanks though.
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
Any way you could try it on a Windows 7 machine?
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Here's an easy way to install Fastboot/ADB.
Once that is installed you'll have to change your commands to fit the file path of the fastboot files.
For example:
Code:
fastboot flash logo C:\Users\OP\Desktop\logo.bin
[/COLOR]
savagebunny said:
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Click to expand...
Click to collapse
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
This minimal version of fastboot is a lot smaller and worked for me.
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
DragonRyderX said:
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
Click to expand...
Click to collapse
A windows 7 machine is unnecessary. I used windows 8.1 pro x64 to perform the whole upgrade process without a hitch. If mofo functions correctly, that means the fastboot drivers are installed correctly. If you start up minimal adb/fastboot, plug in your phone while it's in fastboot mode and type "fastboot devices," what do you get?
EDIT: Duh. You already said that it says returns nothing. Well in that case there has to be some sort of problem with the USB connection or the minimal adb/fastboot installation. Maybe try running the minimal adb/fastboot shortcut as administrator. I don't remember having to do that on mine, but who knows?
St33ve- see OP, nothing listed for adb or fastboot devices commands in their respective modes.
Have you tried a different USB cable?
Yonnor said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, about 7 different ones. 4 that I am sure have worked before, and no physical damage to them.
You said Mofo is able to see your device though, so that's kind of throwing me through a loop. You could try a fresh install of the Minimal ADB, and double check your drivers?
That's a sign of drivers not being installed!
Try opening up device manager n see if the driver is not installed.... If u see a device with an exclamatory mark n "quark" somewhere in it... The drivers aren't installed...
When the phone is in fastboot mode, the phone is listed as quark fastboot, but no exclamation mark. I reflashed computerfreaks image (KK) without an issue, but still isn't recognized in fastboot or Adb. I really want to flash me some Lollipop! I have crack flashed with every phone I own. I'm going thru withdrawals here LOL.
i am having the exact same issues. I've reinstalled drivers, switched usb cords and have had no success.
I'm not certain what actual fixed mine because I tried so many things but I got mine to recognize my phone. I think what did it was revoking the USB debugging authorizations and deleting the adb files on my computer under username/.Android. Then reauthorizing my phone. That and I believe I may have had duplicate drivers interfering with each other. Hope this helps
Hallelujah, I have lollipop!!!
I do not know exactly what the issue was but after factory resetting windows 8.1, and manually loading each driver for adb and fastboot, it works (again). I wish there was a Thank All Button. THANKS ALL!!!
I was on my phone and an app closed. Then it closed again when I tried to re-open it. Third time's the charm, it closed again and then google services stopped. Then my phone shut off. I wouldn't turn on, so I had to do the power button+volume down to get into the bootloader menu. I tried to boot up and was stuck with a bootloop. I downloaded a factory image and the latest android sdk.
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
melgibson666 said:
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
Click to expand...
Click to collapse
My idea is that the bootloader is locked.
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
NLBeev said:
My idea is that the bootloader is locked.
Click to expand...
Click to collapse
It is not.
danarama said:
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
melgibson666 said:
It is not.
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
Click to expand...
Click to collapse
Please screenshot the error.
melgibson666 said:
. . .Bootloader unlocked
. . .reinstalled the drivers to be sure,
. . .used the original USB cable. . .
. . .tried 3 different USB ports . . .
. . .fastboot detected the device.
Still not working.
Click to expand...
Click to collapse
The quotes from you posts gave me the impression that the hardware is OK.
Probably the drivers on your PC are also OK.
I assume the command 'fastboot devices' responded a device ID.
Other issues could be:
- the dosbox and fastboot commands on the PC are not started as administrator;
- the driver on the pc is an adb-driver and not an adb combined driver;
- the version of fastboot is obsolete;
- images flashed before were corrupt;
Possible actions:
Make sure the fastboot and also adb files including the dll's are up to date.
Check if the command 'adb devices' works.
Try to adb sideload a (stock) rom.
Hello guys,
I have 3 identical phones i-mobile IQ2. They are shared among our family.
Mine (fortunately) is runnng fine. The 2 others not so. That's the reason why I want to flash a different ROM.
I have 2 Computers, One with Windows, the other Linux. Both are equipped with adb/fastboot.
What did I do?
1) enabled developer options in the settings.
2) enabled USB debugging and OEM unlock in developer options.
3) Connect the phone via USB
4) Terminal command "adb devices" shows correct serial number of the phone
5) and here it starts. After typing "adb reboot bootloader", the phone shows the white i-mobile screen which is shown when you enter fastboot mode. But....
6) "fastboot devices" results in the terminal message "waiting for any devices"
And that's it. Nothing happens. Retried with 2 phones and always the same. The funny thing is that on my identical phone, there is not a problem and typing "fastboot devices" results in a proper recognition of my phone.
So.... is there anything that I could have done wrong or that I forgot? How can I unlock my bootloader in a different way? As far as I know, adb commands are usually the last resort.
I would appreciate every help. Thanks
You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU
I had the same problem on my gm4g nd i solved installing the correct driver just like nhmanas said. Good luck.
nhmanas said:
You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU
Click to expand...
Click to collapse
Ok, I will try and get back to you again. Thanks for now.
In the past I have unlocked the boot loaders for Pixel, Pixel 2 and Pixel 3 always on first try and I know how to do it. But my new Pixel 5, US unlocked version, arrived today, will not boot loader unlock. I have dev options enabled, USB debugging on, and allow OEM unlock set on. I'm using a Mac so my fastboot commands are ./fastboot___. With the Pixel 5 in fastboot mode, ./fastboot devices gives a correct response, the device responds with its serial number. But then with ./fastboot flashing unlock nothing happens. Just sits there. When I give the command the terminal cursor moves down to the next line but there is no response from the device. I've turned off, rebooted, repeated multiple times, same result. I tried the old ./fastboot oem unlock and that does not work either (as expected).
Has anyone else encountered this? Advice?
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Michael1200 said:
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Click to expand...
Click to collapse
Thanks, Michael. I am using the latest SDK with current platform-tools, and don't have another computer. Tried several different cables, no luck. However, I've decided to forgo unlocking the BL and just set it up locked. I no longer use root nor custom ROMs and future TWRP is very unlikely so I'm going to stay boot loader locked for the first time in many years. Will see how it goes. I really have not needed/used it since OS10.
Thanks again.