Database Info

MOTOACTV "waiting for device" fastboot

Hi all
Ive been tinkering for about 8 hours today with my Motoactv trying to root it. Ive been trying to root based on the Thread
http://forum.xda-developers.com/showthread.php?t=1534073
here on XDA. Ive also read every thread I could find on the internet regarding this to no avail.
I am attempting to flash rebootrecovery using fastboot and its keeps hanging on "waiting for device".
My Motoactv is recognized in Device Manager as MOT ADB Device. I place the device into fastboot and run the fastboot flash recovery recovery.img command. I have also tried fastboot flash recovery rebootrecovery_ma.zip
I cannot figure out why my comp isnt communicating with my device. I was able to see that some people have added the vendor ID to the fastboot flash command but it seems MOTO has hidden the ID pretty well.
Does anyone have any suggestions with this issue?
EDIT*
Well if there are any other idiots like me out there I will answer my own question for them. I figured it out about 10 minutes after creating this thread. rebootrecovery_ma.zip should be flashed via RSD Lite while in Fastboot on the Device. It will then reboot into recovery and you can flash AnyRoot_MA.zip through recovery.

Hi glamaina,
Looks like am the other idiot..without choosing the Fasboot option by pressing the power button, i double clicked the Recovery.bat and the message got is "waiting" in the command prompt.
Read you post still didnt figure it out..took a while after slowly grasping ..oh man..what a dumb guy i am.

Waiting for device
glamaina said:
Hi all
Ive been tinkering for about 8 hours today with my Motoactv trying to root it. Ive been trying to root based on the Thread
http://forum.xda-developers.com/showthread.php?t=1534073
here on XDA. Ive also read every thread I could find on the internet regarding this to no avail.
I am attempting to flash rebootrecovery using fastboot and its keeps hanging on "waiting for device".
My Motoactv is recognized in Device Manager as MOT ADB Device. I place the device into fastboot and run the fastboot flash recovery recovery.img command. I have also tried fastboot flash recovery rebootrecovery_ma.zip
I cannot figure out why my comp isnt communicating with my device. I was able to see that some people have added the vendor ID to the fastboot flash command but it seems MOTO has hidden the ID pretty well.
Does anyone have any suggestions with this issue?
EDIT*
Well if there are any other idiots like me out there I will answer my own question for them. I figured it out about 10 minutes after creating this thread. rebootrecovery_ma.zip should be flashed via RSD Lite while in Fastboot on the Device. It will then reboot into recovery and you can flash AnyRoot_MA.zip through recovery.
Click to expand...
Click to collapse
I have a moto electrify and the motoactv 16. I did a clean with MotoActv Easy modder and now none of the flash tools work. I want to go back to the original system as I am a bike rider. I get a waiting on device everytime now with MotoActv easy Modder or MotoActv Root Tool. Any suggestion or help would be great and evern worth compensation. Extremely frustrating, and not sure I am getting the drivers correct or the register is creating a problem.. thanks Larry l a nichol @kan s a s .n et

lanichol said:
I have a moto electrify and the motoactv 16. I did a clean with MotoActv Easy modder and now none of the flash tools work. I want to go back to the original system as I am a bike rider. I get a waiting on device everytime now with MotoActv easy Modder or MotoActv Root Tool. Any suggestion or help would be great and evern worth compensation. Extremely frustrating, and not sure I am getting the drivers correct or the register is creating a problem.. thanks Larry l a nichol @kan s a s .n et
Click to expand...
Click to collapse
Yes, still have the problem and willing to pay someone to help. lanich"0"l @ ka ns as.nET. thanks.

[Completed] [Q] Fastboot doesn't recognize moto g 4g on linux

I have a Moto G 4g. ADB recognizes the cell and I can restart it in fastboot mode, but when I check in the terminal with:
Code:
fastboot devices
Nothing appears, and if I go on with
Code:
fastboot oem get_unlock_data
It gets stuck at
Code:
< waiting for device >
I tried as a user and as root on an Archlinux machine with android-udev rules as shown in the Archlinux wiki (sorry, i can't put the link). AP Fastboot fast boot menu shows that the cell is locked.

Hi,
You can try a different cable, or USB port on the pc...or even a different pc. Until fastboot devices detects your device, there's nothing you can do.
Reinstall drivers...and you are on the bootloader mode right?
If none of that helps, you can ask in your device section for help....
http://forum.xda-developers.com/moto-g/help
Good luck!

Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.

trichocereus said:
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
Click to expand...
Click to collapse
Please start one in your section. Xda Assist is here to help navigate the site, not for support.
Thanks!

I cannot do fastboot commands. Please help, I've been doing this all day!

My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!

xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!

You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb

[Completed] Ares 8 and Rooting

Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:

domilu said:
Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:
Click to expand...
Click to collapse
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal

Vatsal said:
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal
Click to expand...
Click to collapse
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.

domilu said:
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.
Click to expand...
Click to collapse
Hello,
You may try the link I posted above.
Also, if you have any issues with them, please post in the respective threads. The experts there maybe able to assist you.
Good luck!
-Vatsal

Shield K1 Tablet isn't recognized by fastboot

Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.

You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.

bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.

dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.

Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt

I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others

dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!

For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:

0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.