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] fastboot boot <recoverimgename>.img

I am having trouble getting consistent results with the "fastboot boot <recoverimgname>.img" command.
I am working with both an Amazon Fire 5th generation tablet, a Nexus 4 and HTC One X.
I followed the directions and youtube video posted by awesomeslayerg and rootjunkysdl for rooting the Amazon Fire, and was successfully able to do so (CyanogenMod version 12.1-20151115-UNOFICCIAL-ford, Android 5.1.1).
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
I was also able to put Android version 6.0 on the Nexus 4 by following these directions:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
The one thing I'm struggling with is the fastboot command "fastboot boot <recoverimgename>.img".
On both devices, I'm able to get the devices in communication with the PC (ie "fastboot devices" returns the appropriate information about the devices).
I then run the "fastboot boot <recoverimgename>.img" command:
For Fire: "fastboot boot TWRP_Fire_2.8.7.0.img" (obtained from http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery)
For Nexus 4: "fastboot boot twrp-2.8.7.0-mako.img" (obtained at https://dl.twrp.me/mako/)
In both cases the recovery file is in the same directory from which I am running adb/fastboot.
The issue with both is that sometimes they'll reboot into the respective recovery, and sometimes they won't.
When they won't, the Nexus 4 hangs at the Google splash screen. The Amazon Fire boots to the system.
I can't figure out why they don't consistently boot to the recovery.
I've tried getting into fastboot mode via "adb reboot bootloader", by shutting the devices off and booting into fastboot manually (volume button + power switch), by rebooting to recovery then to fastboot, etc.
Also tried waiting a long time after getting the correct response to "fastboot devices" to make sure things had settled down.
Nothing seems to have given a consistent response.
I'd like to be sure that I can boot into a recovery on the PC when I need to (from fastboot on the device). At the moment it seems to be luck whether I can or not, but I assume there must be some cause that I can solve.
Anyone else experience this problem? Have ideas how to solve? Or can point me to a forum which is addressing this?
Thanks.

fastboot boot <recoverimgename>.img Inconsistency
I've just looked through the entire forum discussion on rooting the Amazon Fire 5th gen tablet, and not found an answer to this problem.
I've already rooted the Fire (Ford) and gotten Cyanogenmod 12.1-20151115-UNOFFICIAL-ford running on it, so this device is OK.
But I have continue to have erratic results booting to a recovery on the PC using fastboot: C
I can get the tablet connected to the PC in fastboot mode, fastboot devices gives me the right answer, my driver is Android Composite ADB Interface, and everything seems OK.
But most of the time when I enter the "fastboot boot TWRP_Fire_2.8.7.0.img" command the Fire reboots to system, and occasionally to Amazon's recovery version. Only occasionally to TWRP, and I don't know why.
How can I consistently boot into the TWRP_Fire_2.8.7.0.img recovery on the PC that I used when I rooted the thing in the first place?
Any ideas?

Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!

Thanks much. I'll try the guide. I've managed to get it all to work (ie "fastboot boot TRWP_Fire_2.8.7.0.img") on another PC, so it must be the setup on the 1st PC. I'm really struggling with the drivers.
I'd post questions in the other threads, but don't have the status yet...
I also see that Amazon's new update has throw a monkey wrench into fiddling with the Fire. I'll keep working at it.
Darth said:
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Click to expand...
Click to collapse

Go to your device sections and contribute some meaningful posts to threads that interest you, and you'll be able to post in the other threads in no time. :good:

wrong boot img flashed. Now phone stuck in bootloop and won't be detected by PC

Hi guys,
Before i start, just be informed that i have tried google all possible solutions and tried them but to no avail. I know its a long shot but perhaps someone may be able to help however small the chances are.
My phone is a Xiaomi Redmi Note 3 Snapdragon variant and is rooted.
What happened was, i tried installing TWRP (kenzo version) on my phone and so following the "instructions" in the downloaded file.
I used Flashify to flash the boot.img and then redmi_note_3_Twrp.img then the phone prompted me to reboot.
Now my phone is stuck in bootloop. The only thing i can do is to boot into Fastboot. So i tried accessing fastboot via ADB hoping to be able to some how flash the original boot.img back.
The problem i have now is that i am unable to access the phone at all even though i can go into fastboot. It wont be detected by my PC. I tried Minimal ADB and Fastboot and PdaNet.
Is there any other way for me to detect my phone and run some form of command to get it started again? Any help at all is appreciated. The phone is fairly new and i'm regretting trying to get the latest ROM for it.
I'm hoping i'll have some luck in a helpful community such as this.
Thanks guys.

Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either

Marticco said:
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Click to expand...
Click to collapse
Fret not my friend. For i have found the solution and managed to unbrick my phone. Thank the good guys at MIUI for this.
Head over to the MIUI forum and search unbrick under the Redmi Note 3 forums. I can't post the link here unfortunately
You can also thank me after you unbrick your phone.
This only applies if you are uaing the Redmi Note 3 Pro

yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device

Marticco said:
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Click to expand...
Click to collapse
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?

willetan said:
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
Click to expand...
Click to collapse
yes it is unlocked,
i think? When i entered fastboot mode. One of my apps says bootloader enabled and when i typed 'fastboot devices' in the Minimal ADB and Fastboot its shows:
0123456789ABCDEF devices
whereas if I type 'adb devices' i just shows:
List of devices attached
The main problem is the driver, i cant get adb to find my device. I have tried the universal usb drivers like Kouch but no success. My device is listed in the Unspecified section in my computer

Sony Xperia 5 II XQ-AS62 root

Happy new year! I was hoping to bring in the new year with root, but strangely with this version when ever I boot into "bootloader" from the recovery menu, the device screen is blank, and adb does not detect anything.
Would someone be gracious enough to provide a step by step root for this particular US variant? I can send you a gift card if you get me running with just root!
Thank You!

It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!

BurnsMotorCycle said:
It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!
Click to expand...
Click to collapse
On other thread you mentioned that `fastboot devices` gives nothing. I suspect that you are missing drivers for your device so try installing drivers first. Try these: Xperia 5 II driver - Sony Developer World ?

I saw that link before, but my device was not specifically listed. I'll try it anyway and hope that it works.

I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"

BurnsMotorCycle said:
I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"
Click to expand...
Click to collapse
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?

PPGX5II said:
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?
Click to expand...
Click to collapse
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21

BurnsMotorCycle said:
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21
Click to expand...
Click to collapse
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.

PPGX5II said:
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.
Click to expand...
Click to collapse
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.

BurnsMotorCycle said:
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.
Click to expand...
Click to collapse
Thanks! But I just wanted to help you out. I won't be taking any gift cards in return!
If you want you can donate it to some of these developers so that they can work on supporting more!
Cheers and Happy New Year!

It Worked! I appreciate your help, but I mostly just followed the link you provided from
Miustone. Thank you to him and you both! That Thread should definitely be pinned in the
"Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe" section too!
Ill donate to Miustone, and have a happy new year!
EDIT: Darn looks like Miustone only takes paypal, which I don't have (I have crypto). Thanks again for the help everyone!

Quick Question, how do you tell which region firmware is on your phone?

Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details

PPGX5II said:
Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details
Click to expand...
Click to collapse
you are so kindful!

Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?

klausstoertebeker said:
Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?
Click to expand...
Click to collapse
No because you can't

I also have Sony Xperia 5 II XQ-AS62 and I've found myself in a similar situation as burnsmotorcycle but I think it's because I have TWRP installed. More specifically, I see my device when I run "adb devices", I get nothing when I run "fastboot devices", and I get TWRP when I run "adb reboot recovery".
Does anyone know how I can uninstall TWRP? Please note, my device still has the bootloader unlocked, fastboot commands are unresponsive now that TWRP is present, and ADB and Magisk seems to be the only tools available to me right now.

ADB not seeing phone when in recovery

Hey everybody. I'm back from a long hiatus from rooting phones. I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Win10, pretty sure drivers are up to date, adb up to date.
Computer and adb both see the phone when it's powered on normally, but I have to choose usb mode every time I plug it in. I suspect the adb not seeing it in recovery mode may have something to do with this, but I'm just guessing. I'm not sure how to overcome this. I know plenty of people have rooted this phone, so I don't get it.
Would be happy for any input on this issue. Idk where to go from here, and it's really frustrating, bc I'm excited to switch to this phone.
TIA

Have you tried checking Windows update when the phone is plugged in and in recovery mode? Do you have the Google fastboot drivers? Qualcomm drivers? OnePlus drivers? Are you using CMD or PowerShell for adb?

Zamkat said:
I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Click to expand...
Click to collapse
yes, why should you? adb not available in recovery mode, expected behaviour.
Zamkat said:
I know plenty of people have rooted this phone, so I don't get it.
Click to expand...
Click to collapse
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.

alecxs said:
yes, why should you? adb not available in recovery mode, expected behaviour.
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
Click to expand...
Click to collapse
It's been so long since I did this...I don't remember much about the procedure. I was just following the instructions. It said to turn it off, and then hold down and power to boot into fastboot mode. Then to connect it and type the reboot bootloader cmd.
I am using powershell.
These instructions aren't very good, I realize now. -_-
I guess I don't have the fastboot drivers...I'll try to get those and make another attempt. Thanks, I'll get back to you.

the driver is included in the same android_winusb.inf where the ADB driver is. you just need to disable windows driver signature enforcement before trying to install.
once you see device in 'fastboot devices' proceed with bootloader unlocking.
T-Mobile get Unlock Code to Submit to OnePlus for unlock token
This took me way too long to figure out so Hopefully this will make it quicker for someone: OnePlus Help Page Dr. Mario said: fastboot oem get_unlock_code (Found ten pages in at...
forum.xda-developers.com

Okay, well, this will make things difficult. Am I missing something here...???

Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.

not sure what you are trying, but to run fastboot commands either navigate with cd into platform-tools directory from cmd.exe or in powershell type the path to file like this:
Code:
.\fastboot devices

Zamkat said:
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
Click to expand...
Click to collapse
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.

I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting. It is also not mentioned anywhere in this device forum.

Zamkat said:
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
Click to expand...
Click to collapse
Please go back to post #6. as we can see you're in folder "platform-tools" (left side of the cursor in your PowerShell window). This folder contains the files "adb.exe" and "fastboot.exe" and some more.
As a normal Windows user you would try to start these .exe files with a double click. Don't try it because it won't start anything. These .exe files are not executables, they are binaries. To run them you need to enter "adb" or "fastboot". That's all.

You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide

According to the instructions, I need to use the Sdk manager to install the fastboot drivers.
In order to get that, I apparently need the command line tools.
In order to get those enabled/installed in sdk, I need the Sdk manager...??? I'm so confused.

BillGoss said:
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
Click to expand...
Click to collapse
Holy ****, thank you.
Okay, I am in Fastboot mode, and I'm getting ready to install Twrp, but...it says my Device State is locked. Does that mean my bootloader is not unlocked? Because it is supposed to be.

alecxs said:
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting.
Click to expand...
Click to collapse
The Platform Tools are part of the Android SDK. But Google offers them also as a single download, excluded from the Android SDK:
It's not wrong to install the whole SDK. But it's too much if only 2 binaries are being used.

how did you unlock the bootloader without fastboot?

alecxs said:
how did you unlock the bootloader without fastboot?
Click to expand...
Click to collapse
I'm an idiot. I need to do that still.

Device isn't being seen by adb in fastboot. Any suggestions?

Fyi, you shouldn't have posted the question in this forum but in the q&a forum https://forum.xda-developers.com/f/oneplus-8t-questions-answers.11583/

@BillGoss thread is moved soon, thx for reporting.
@Zamkat no device is seen by adb in fastboot.