I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
motoxuser said:
I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
Click to expand...
Click to collapse
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
jayboyyyy said:
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
Click to expand...
Click to collapse
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
motoxuser said:
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
Click to expand...
Click to collapse
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
mjphillips1981 said:
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
Click to expand...
Click to collapse
great! I'll do that - actually, I just sent you a PM - i'm trying to work my way through the mac tool now and got stuck. appreciate it!
Related
Please for the love of god help me. I've tried everything.
I have a developer edition. I have the newest drivers, the newest phone updates. Everything. It is recognized by ADB when I'm on the home screen, but when I am in fastboot mode itself it will not recognize the device. I can't unlock the BL because of this. It's VERY frustrating and I'm about 12 hours from selling this device and buying an HTC M8.
I have Windows 7 64 bit. I'm on the newest moto drivers, the newest FW for the X. I've uninstalled and re-installed and restarted my machine countless times. With no luck. With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Navigate to where fastboot.exe is installed, and run "fastboot devices".
And make sure phone is in bootloader mode.
Does it list serial number?
I ran into the same issue last night, I just got a moto x DE for my wife, and a new laptop since last March when I unlocked my moto x DE. "adb devices" returned nothing, and I had a fresh install of the SDK and the moto drivers. Both old and new laptop on Win 7 64-bit. I googled trying to find a solution, but didn't find anything that worked. Grabbed my old laptop, hooked up to it, and it worked fine.
One suggestion I saw and didn't try was to remove/reload the moto drivers. Since I got it working and got her phone unlocked with my old laptop, I didn't pursue further.
Nitemare15 said:
....With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Click to expand...
Click to collapse
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
This is what worked for me. Posting here for posterity and potential helpfulness.
yghrv said:
I hit the issue earlier and fixed it with the steps. hope will help you too.
1. connect your phone with computer
2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\
3. run Motorola Driver Installer.exe, choose clean and Reinstall.
Click to expand...
Click to collapse
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Even that wouldn't help him if he was trying to use adb while in the bootloader.
KidJoe said:
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
Click to expand...
Click to collapse
Thanks for clarifying. I only end up dealing with rooting something once a year or so and always forget the "ins-outs-and-what-have-yous". Once I was reminded of fastboot vs. adb all was well!
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Thank you very much, that did the trick for me !
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
jdwilder23 said:
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
Click to expand...
Click to collapse
I'm sorry but you'll have to elaborate on your problem. Are you having trouble using adb in cmd? As in no devices list when you type adb devices but they do when you type fastboot devices ? You may need to check what you downloaded/installed and make sure that the folder that it downloaded to--that you've cd'ed into to use adb/fastboot--does contain adb.exe. I suggest this installer straight from Google. Also, adb will only display/connect devices when it's not in fastboot mode.
idk
I'm having problems with getting my token code to unlock my boot loader thru HTC but I downloaded the right software and it does recognise the device as adb but when I go into cmd prompt and type fastboot oem get_token_identifier it's not recognized and doesn't do anything. So I'm stuck on getting my token for htc
I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??
What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.
Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)
Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.
It finally worked, thanks a lot brother :laugh:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
1xcalibur1 said:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
Click to expand...
Click to collapse
First, you need your bootloader to be unlocked. It's pretty easy if you have that done already.
You'll need ADB and Fastboot. It can be tricky to get the right drivers. The driver used when your phone is connected in normal mode is not the same when connected in fastboot mode, in my experience anyway. You'll want the 15sec ADB driver and you'll need to update the driver when it is in fastboot mode.
Next, get the correct twrp img and put it in the ADB folder(you'll need a different one based on flashing a pie rom or a q rom). You may want to rename it so it's easier to type in fastboot.
To enter fastboot mode, hold volume up and plug in the usb cable. The LED should light up blue.
Open a command prompt and navigate to wherever you've installed ADB(mine is on C:\ so it's really easy).
Type "fastboot devices" to double check if the driver is installed and your phone is connected in fastboot mode.
------It should show something like: BH9090808E fastboot
Then type "fastboot flash recovery twrp.img" - or whatever you've named the file. It will take less than a few seconds.
Then type "fastboot reboot" and let your phone reboot.
Done
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
1xcalibur1 said:
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
Click to expand...
Click to collapse
My apologies. It's been so long since I've started from scratch, I must've gotten the drivers mixed up. The 15sec ADB is for the phone connected in normal mode.
I'm pretty sure this one is the fastboot one:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If not, I'm sorry because that's all I have.
I nailed it eventually!
For anyone that comes across this thread,
this video will solve all your problems with adb drivers:
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!