MOTOACTV "waiting for device" fastboot - General Questions and Answers

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.

Related

[q] depressed and need help

DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
DflMaster said:
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
Click to expand...
Click to collapse
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
pushkardua said:
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
Click to expand...
Click to collapse
I dont know! I can Erase and Flash .img files into the phone ~ by using CMD and the SDK but i dont seem to be able to flash a system.img the one i have is 3gb and says error allocating memory. I dont see my device on adb ~ and fastboot shows ? Fastboot as device. I went and installed Ubuntu into a Virtual drive to try to push files into phone so i could access download mode or recovery. No luck there i couldnt find the phone under devices either.
When i use CMD on the PC and flash recovery recovery.img or any other image command the phone displays the work being done. So i think i am connected to Fastboot.

Need help to fix boot loop

Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
I'm done
xswish said:
Hello, first post on this forum, so yeah ^^ I am also kinda new to this. I have a gs3 which is rooted and all, but that is old, and methods has changed...
So i tried to root my shield tablet and it got stuck in a boot loop. I can not get it into the bootloader using adb tools, or fastboot, or atleast i knot know how to. I have ran the: adb reboot bootloader, without success. I have also tried the: adb devices command and i dont see my device there. I have installed mini adb drivers.
This happend when using this tool(windroid): http://forum.xda-developers.com/showthread.php?t=2499926
So im thinking that if there is a way to get out of this, that would be great. I really hope i have not bricked it... all i wanted to to was to get root so that i could connect a ps3 controller... :/
I tried to use the windroid program but the recovery did not install. so i did it manually following this tut http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
im am not complaining or anything, purly looking for help.
So, after trying i got it up and running. i did not flash any supersu.zip files, just installed it from the market. wen it asked me to reboot the device ended up like this. I am aware of the disclaimers and stuff. If i go to device manager on my computer i can se: SHIELD Tablet, with a yellow triangle. I also searched youtube and this forum to look for posts, but found none that could help.
image: https://www.dropbox.com/s/16y1icl89etg9q9/2015-04-18%2015.36.46.jpg?dl=0[/IMG]
**Update** I found out how to get into the bootloader manually, so ill continue trying...
Click to expand...
Click to collapse
So, i fixed the problem by browsing back in the forums, did not know you could get into the bootoader by sing hw keys... lol
I fixed it by following this post: http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462

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

[HELP] Bricked Oneplus 6 - Qualcomm CrashDump - already tried everything

Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Did you try msm download tool? If not, nead that thread and good luck
whizeguy said:
Did you try msm download tool? If not, nead that thread and good luck
Click to expand...
Click to collapse
Hi!
Thanks for your reply, but I think you do not read my entire post
As I said, i've already tried at least 8 different versions of msmDownloadTool.
If you have any other suggestion, I'll appreciate.
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
EarthquakeXS said:
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
Click to expand...
Click to collapse
Yes, I am unable to enter into Fastboot Mode.
When I try, the logo saying "fastboot" appears, but after 4 seconds, the systems stucks on CrashDump error screen again.
That way my PC cannot find my phone with ADB or FASTBOOT commands.
The only tool that works is msmDownloadTool, but even with a success run with that tool, my system does not start and stills under CrashDump error.
I was thinking if exists some version of msmDownloadTool that justs restore the fastboot and unlock bootloader with brute force.
Thats my last hope
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
sanaulla jauhar said:
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
Click to expand...
Click to collapse
Hi!
Can you please provide some link to this tool?
Thanks for your help!
mikesmarcos said:
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Click to expand...
Click to collapse
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Hi dude are u here ? i will help u
Try this
Rhach1d237 said:
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Click to expand...
Click to collapse
Source is a videotutorial. google oneplus 6 hardbrick and click the video of Max Lee
(it worked for me)
the download takes an awful lot of time
first get your phone into qualcomm download mode by holding down volume up + power button and plug your device in your PC.
(first unzip the hardbrick zip folder) then the oneplus 6 folder and than the .exe file and click 'start' if it detects your phone.
That is flashing every chip and Hydrogen OS 5.whatever.3 but that is not important. Your phone should boot and than you can install Oxygen OS with android 10(thats the other zip folder) using the local upgrade feature.
(make sure to enable google play services after upgrade from hydrogen OS)
Hope it will work for you too if you haven't tried it already.

Question Rog Phone 5 Brick

Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'
Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't
Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working

Categories

Resources