Database Info

[Q] Stuck at the Fastboot protocol support

I trying to unlock my XOOM WIFI from COSTCO, when I ran the command
adb reboot bootloader
The XOOM reboots show the message STARTING FaSTboot protocol support and stuck in there, I have to VOL UP & Power to reset it.
What I am doing wrong.?
I do not want to do the ONE CLICK to avoid wiping the machine completely.
Do I need to wipe it the first time?

you need to have fastboot in your machine, then you can run:
fastboot oem unlock
it will ask you to use volume up/down keys to confirm "twice" the terms of service and will unlock it for you.
please not that unlocking it will void your warranty right away, so unless you are a developer or have a very good reason to do so, I would not recommend it.

You are doing it right.
adb reboot bootloader
is supposed to bring you to "Starting Fastboot protoco"l screen. Just continue and enter the commands as the instructions entail. If this is the first time you are rooting the device though you will end up wiping everything fyi.

ubuntu and fastboot....waiting for device
I am running Ubuntu 10.10. When I do adb reboot bootloader....when I run any fastboot command it says <Waiting for Device>…do I need to install USB drivers and how would I do that on Ubuntu.
Any help would be greatly appreciated...

Type in adb devices.
Does it list your device there?
Most likely it's a driver issue when it says "waiting for device."
I know nothing about ubuntu though so i wont be any help getting those drivers installed.

Yes it does before I get into the bootloader. After I get into the bootloader I get nothing.
Sent from my PC36100 using XDA Premium App

adb not reconized
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx

wmchristian said:
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
Click to expand...
Click to collapse
Make sure you are running the commands from the directory on your computer that the adb file is in. For example, make sure you do a CD "\Program Files\Android\android-sdk\tools" if that is where adb and all the necessary files are.

thx for reply
Thought I did ill try again this weekend to over clock my xoom never was good at dos.

[Q] Softbricked after 4.3.3

Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.

haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app

Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.

Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.

habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?

So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.

habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.

I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk

Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.

haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.

haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.

[Q] moto g xt1031 isnt listed in adb devices

i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.

lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What is the phone booted into when you're entering the adb command? The phone is booted into Android or in recovery? If you're in bootloader you'll need to use fastboot commands. Such as fastboot devices

lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What os are you using on your PC? I had similar problems on Linux mint until I firgured out I had to add a line of code with the adb install
Sent from my Moto G using XDA Free mobile app

It doesnt show up when its booted into android, recovery or bootloader. I am running windows 7 home premium. Ive tried many different driver installers and nothing has worked.

ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55

lolkidz said:
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
Click to expand...
Click to collapse
I would suggest uninstalling whatever drivers you have installed. Disconnect your phone, uninstall drivers, restart, install drivers and connect your device then try again. When the phone is connected as mtp, adb, fastboot, it will install drivers for each type.
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050

i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.

lolkidz said:
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
Click to expand...
Click to collapse
Where did you DL the adb thing at? You could have a faulty adb download or just didn't install your correct api in the adb suite
Sent from my Moto G using XDA Free mobile app

Moto G XT1040 - bricked?

I unlocked my Moto G XT1040 bootloader and tried to load stock Kit Kat (because my wife didn't like Lollipop) using ADB.exe, but something went wrong. Now it boots to the "bootloader unlocked" warning screen and won't continue to boot after that. I can't run ADB commands against it because it's saying that no device was found. I assume that's because I need to turn on USB debugging, but I can't boot into the OS to do that.
I heard you could restore stock firmware using Odin, but I can't seem to find the stock XT1040 tar files that are needed to do that, and I don't know if Odin will be able to communicate with the phone, since ADB isn't recognizing any connected devices (the phone does say "USB connected" and in device manager it's recognized properly as a Motorola android device). I even tried using a different computer, but still can't send any commands to the phone.
Is it bricked beyond repair? It's fine if we have to stay with Lollipop - I'd just like to get it operational again.
Cheers

Hi
Try to flash it with fastboot... Opening your bootloader screen will put you in that mode on your phone...
Let us know

satanas17 said:
Hi
Try to flash it with fastboot... Opening your bootloader screen will put you in that mode on your phone...
Let us know
Click to expand...
Click to collapse
Thank you! I'm a newbie so I assumed that if ADB said no devices were recognized, then certainly fastboot commands wouldn't work.
I actually ended up using mfastboot to restore the stock firmware and everything is working great. Thanks so much!

micheken said:
Thank you! I'm a newbie so I assumed that if ADB said no devices were recognized, then certainly fastboot commands wouldn't work.
I actually ended up using mfastboot to restore the stock firmware and everything is working great. Thanks so much!
Click to expand...
Click to collapse
You're welcome, happy endings are always a pleasure...
Mark your topic as solved and hit the thanks button if you want...

ADB will not recognize my 2015 moto e 4G LTE

I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?

BillyMumphry said:
I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?
Click to expand...
Click to collapse
Ha ha! As soon as I submitted this, I got a notification of a software update to Marshmallow!
The irony...lets hope this irons out the wrinkles.

SOLVED!!!
Well, the OTA update to Android 6 didn't solve my problem, it was my relentless sifting through post after post on XDA and just all over the Internet in general. For anyone else facing this problem here is how mine was solved:
My attempts at unlocking the bootloader were these: I installed everything that I could find on the internet. I installed Android Studio, SDK, all kinds of different drivers, minimal ADB and Fastboot, but nothing seemed to really work. When I plugged my phone into the computer neither ADB nor Fastboot would recognize the device.
USB debugging was ON, OEM was enabled, and for some reason I had MTP set. So after hours of sifting through bug reports generated by a terminal emulator APP, and going over post after post I finally found something useful.
Before I tried it though I wanted to start fresh. So I uninstalled everything from my PC and only download 2 things. Minimal ADB and Fastboot, (found here: http://forum.xda-developers.com/showthread.php?t=2317790, and the official Motorola Device Manager (found here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481.
But the thing that really did it was something I read here on XDA . It was this: switch MTP to PTP! And it was just that simple. Everything else was set the same, USB DEBUGGING ON, OEM ENABLED, and PTP SELECTED. I didn't even boot the device into Fastboot to begin as is instructed, I just started with my phone on and plugged in to my PC as I was just finishing transferring some photos. So I opened ADB/Fastboot, typed in "$ fastboot oem get_unlock_data" and bingo!
Here are the instructions I followed on how to unlock the bootloader: http://freeandroidroot.com/how-to-unlock-bootloader-and-root-motorola-moto-e/
So thank-you XDA forum, you are an invaluable and inexhaustible resource! :thumbup::thumbup::thumbup:
~This thread can now be closed~