So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Make sure that the drivers are installed properly from the SDK. Installing the SDK is not enough. Look in device manager and look for a yellow symbol with exclamation mark next to any Android device. Right click and get to select driver and point to "Google usb driver" that you extracted from the SDK then select either bootloader or ADB driver depending on what mode your phone is in when doing the above. It should then work. Sorry if that is not clear I am doing it from memory and I am not at my computer. Good luck!
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Try "fastboot devices" instead that will tell you of it's correct or not too
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Did you enable ADB debugging in Developer Options yet?
That must be done when plugging phone into your computer while the phone is booted up.
Related
hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.
Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/
Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse
Pixel XL (Verizon) Not Being Recognized via "ADB Devices" command on Windows 7.
So I got my 128gb pixel xl from Verizon today. It's still 7.1.0 (Build NDE63P) so I want to unlock the bootloader asap. I was able to get the phone booted up and mostly set up without taking the OTA update (I pulled sim card before booting the phone for the first time, and I skipped the wifi setup).
I intended to follow the instructions here to use dePixel8 to unlock the bootloader. I got USB debugging enabled on my phone, and ABD/Fastboot installed on my computer (Windows 7 laptop). The problem is the phone doesn't come up in the list when I use the "adb devices" command from the command prompt within the SDK folder. Looking at the device manager, it appears my laptop is automatically installing the "Google Nexus ADB Interface" driver for the phone, is this not the correct driver? I downloaded the USB drivers from here and tried pointing the Device Manager at them to force a driver update, but the device manager tells me the drivers are already up to date.
Can someone please explain to me how to get my computer (Windows 7) to recognize my phone via ADB so I can push dePixel8 and unlock the bootloader? I feel like I'm so close to being able to unlock the bootloader, but my phone not being recognized via ADB is driving me freaking crazy.
Thanks!
EDITED TO ADD: If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
TonikJDK said:
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Thanks for the prompt reply. I'm currently uninstalling Android Studio and SDK I downloaded, and will install the one you linked.
I think this is still a problem related to the driver Windows 7 is automatically installing for my phone. If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)
Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Just a quick bump for this thread. I could use some suggestions/guidance.
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Beetle84 said:
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Click to expand...
Click to collapse
Thank you very much for the helpful info. I am looking through this now. I am curious as to whether or not there is a Linux equivalent to the Motorola USB drivers. I only see Windows/MacOSX.
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Just a quick bump for the day.
PrettyDumbITGuy said:
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Click to expand...
Click to collapse
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Beetle84 said:
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Click to expand...
Click to collapse
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Beetle84 said:
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Click to expand...
Click to collapse
I disabled driver verification with the following command "bcdedit /set testsigning off" and then connection my phone. The Win10 machine still does not detect the phone as a usable device. I receive a warning box with the following error "USB device not recognized. The last USB device you connected to this computer malfunctioned and Windows does not recognize it. "
PrettyDumbITGuy said:
.
Click to expand...
Click to collapse
PrettyDumbITGuy said:
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
Click to expand...
Click to collapse
Did you install android tools and android udev on Manjaro
BTK19 said:
Did you install android tools and android udev on Manjaro
Click to expand...
Click to collapse
Yes, I did. The problem I run into on Linux is much the same as the problem that I run into on WIndows. The computer simply does not recognize the phone as a device and the Android SDK tools do not detect the phone. I almost wonder if maybe something is wrong with the phone? Perhaps I purchased a defective device? I know that normally when you plug in your phone to a machine you receive a prompt on the phone asking you whether or not this is a "trusted device" but I receive no such prompt on my Moto G Fast. I'm almost wondering if I should just return the phone and get something else. Perhaps a Moto G8 power or maybe one of the new Nord line of One+ phones.
This may be redundant. But I suggest you try another cord. More often than not I find myself weeding through charge only cords till I find a data cord. Also try using a USB 2.0 port, preferably attached (rear of the computer) as opposed to any front ports or hub.
PrettyDumbITGuy said:
Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Click to expand...
Click to collapse
Unlocking my G Fast was Sooo easy, i asked Boost to unlock phone, no charge! then i 5apped UICC UNLOCK btn under About Phone, done & done.