Hey guys, I have an old Pixel device and i can recall its email/password. I was trying to follow this post (https://forum.xda-developers.com/pixel/help/frp-bypass-pixel-usb-debugging-off-t3520192/page34) but the very first step which is sideloading isn't working for me.
When i connect this device to my mac book and issue command
Code:
adb devices
, I get no device in the adb list. However, when i issue the same command to my another Pixel XL device (which has usb debugging enabled), it works fine.
So my first question is that how can i get adb sideload working when i can't even see this device on console.
The bootload is locked and I am not sure what update i had on this device. Probably android 7 (can't recall)
Related
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
CoatedMoose said:
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
Click to expand...
Click to collapse
Did u try to do a adb remount then try adb devices
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
CoatedMoose said:
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
Click to expand...
Click to collapse
Did u download motohelper drivers so your adb will recognize the device
if the xoom is in fastboot adb wont recognize it hold power and volume up to reboot and try again
The xoom is recognized already. I am able to send the adb reboot bootloader command. When the xoom is trying to load into fastboot, it is not visible, which makes it impossible to enter the oem unlock command.
I gave up on the device, I was having issues with geolocation as well which didn't exist on another device. I returned the device and am waiting to receive the 3g version from the US.
I have the same problem. Does anyone know how to get around this?
Sent from my Xoom using XDA Premium App
If when you can run the adb reboot bootloader command and don't get fastboot to work, then as yet I have not found a solution. Instead I just returned it and ordered the 3g version from verizon and had it shipped. The commands worked fine. If you cannot use the adb command to reboot, then check the instructions for installing adb and fastboot and/or post the error messages you are getting.
On a side note, where did you get your xoom (country/store etc). I wonder if it is a problem with a certain batch, or all the Canadian ones etc. I my wifi only version from bestbuy in Canada.
I'm having the same problem right now on my xoom.
I was preordered on Amazon and delivered to New York 3 weeks ago...
no solution as for now..
returning isn't an option for me, since I live in Poland :/
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
I'm not sure if you're using Windows or not but I didn't had any issues when I used fastboot. Just need to make sure you have the drivers installed, and when you do adb reboot bootloader check the device list to make sure it still shows your device listed in there and not as a question mark. If you don't see your device listed in the Device List or does show but with a question mark, double check to make sure you have the drivers installed or else fastboot will not work.
And don't bother trying to use adb when you're in the bootloader since adb will not work.
*** edited: just noticed now that you are using ubuntu 10.10 (I need to stop over reading stuff). Can't remember how the drivers aspect works in Linux since it's been forever since I've used a Linux flavor but you will still want to make sure you have the correct drivers installed or make the changes that niematunikogo did and see if that worked.
niematunikogo said:
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
rrainz said:
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
Click to expand...
Click to collapse
before typing all the commands, first type "sudo su". adb and fastboot both need to be executed as root (adb actually works without root in case you already edited the USB rules before)
I had same problem but just returning device was not what I intended to do
niematunikogo said:
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
This worked for my Ubuntu, thanks!
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)
I recently bought a 2018 Samsung Galaxy Tab A (SM-T387t) to replace my fallen Nexus 7 as an in-dash car tablet. Unfortunately, the problem I’ve run into is that because it is a t-mobile branded device, the bootloader is locked unlike its WIFI counterpart, so I can’t flash anything on it.
I’ve found multiple questions just like this on the forum but no concrete answer. Has anyone been able to complete this?
1st thing of all things is to enable USB debug in Android -> Settings -> Developer options and re-start phone afterwards, if not done yet
2nd is to install ADB & Fastboot ( see link in my signature below ) & Samsung's Android USB driver suitable for your phone, if not done yet
3rd is to trying to establish both an ADB USB-connection and a Fastboot USB-connection between Windows PC and your phone to check whether these are working, if not done yet
Code:
adb devices
fastboot devices
If all is working well so far then you can try to unlock phone's bootloader and to root phone's Android.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.