Can I use a Nexus 7 to root a cellphone?
Is there a way to put ADB on the Nexus 7 and use a MicroUSB to MicroUSB cable to root a cellphone?
Night be possible, real question is, is it smart to do so? Stability wise I wouldn't do it, but that's me
Sent from my HTC One using Tapatalk
That's a good question I was wondering the same thing. I have a full keyboard with my nexus 7.I don't know if that would make a difference or not. Good luck!!!
Sent from my Nexus 7 using xda app-developers app
pseudoremora said:
adb shell and Terminal Emulator are not the same thing. One is an shell environment (adb shell) and the other is a tool to access that environment (Terminal Emulator).
adb shell is native to the phone and allows for Linux shell access. Terminal emulator will allow you to run adb shell ON the phone directly to access that shell environment.
Secondly, yes you are correct, in that you can use the Command Prompt (CMD) to access adb shell. Also, your phone must be in debugging mode as you stated.
To get a list of commands -- you type: adb, while in the androidsdk\tools folder and it'll display the default set of commands available to you.
Click to expand...
Click to collapse
From this post that I found in a random, non-related thread, it sounds like ADB is already part of the Android OS. So it's possible that all I need to do is install a Terminal Emulator on a tablet, connect the tablet to an Android phone via cable and run an "adb devices" to see if it's connecting.
I'll try to do this sometime this week and see if it works.
CZ Eddie said:
Can I use a Nexus 7 to root a cellphone?
Is there a way to put ADB on the Nexus 7 and use a MicroUSB to MicroUSB cable to root a cellphone?
Click to expand...
Click to collapse
Just tried with OTG cable in Nexus 7 with MicroUSB cable in my GSII and I couldn't get it to work. It didn't give a notification on the phone about Debugging being connected but it did start charging the phone.
Related
Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
UND3RTAK3R said:
Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
Click to expand...
Click to collapse
1) install HTC sync to get the Evo drivers
2) install Android SDK
3) add the tools folder with adb.exe in it to your windows Path or always navigate the command line to that folder.
should work
So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.
If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.
Can someone guide me in the direction I need so I can do this adb reboot?
chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.
I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.
I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.
I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.
If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk
I don't see any other threads, so is it just me struggling to install working ADB drivers?
The zip file I found in another thread made out like it was installed, but apparently not...
Any tips?
Windows 7/8? The drivers that I posted in the dev thread should work.
If you're on Windows 8 though, you'll have to reboot in that insecure driver installation mode thing.
Sent from my HTCONE using Tapatalk
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
AndyCr15 said:
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
Click to expand...
Click to collapse
You try "ADB Composite Device" or something along those lines? When you run that one it should be good.
When you download the zip, you should just extract the whole thing. Then after that I find the driver manually instead of having it search the folders. Are you selecting the android_winusb.inf for the driver?
I'm on the same OS for my main desktop and I do a lot of my work with the N1 on there using those drivers. Are you using normal command prompt in the platform-tools folder? I don't use anything other than command prompt for adb, so I'm not sure about those picking it up.
Sorry if that isn't any help, but I'm not sure what would stop it from picking it up after you use those drivers.
the other threads zip file works fine with my win 64. Are you going through a usb hub? That can mess it up
Sent from my N1 using XDA Premium 4 mobile app
No, no hub. Yep, doing all as I should. I'll try a different cable and different port though.
Linux
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
mybrotherischad said:
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
Click to expand...
Click to collapse
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
ChodTheWacko said:
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
Click to expand...
Click to collapse
Running natively. No luck doing it as root.
Hello folks,
I have a Nexus 7 2013 with Lollipop and I cannot manage to make it be recognized by Windows. I have tried Windows 7 and Windows XP in different computers. The nexus 7 is shown as “USB device not recognized”. I have tried to uninstall previous drivers, install the Google Drivers, Universal drivers and nothing. I have also tried the Nexus Root Toolkit. The Nexus 7 is being charged while connected to the computers. So, I assume it’s not a problem with the USB cable. I’ve tried more than one USB cable too. I’ve tried with USB debugging enabled and disabled, MTP enable and disabled with no success.
Does anyone have a suggestion of something I should try?
Thank you!
Are you positive it isn't a problem with the storage itself? If you are rooted, download Terminal Emulator from the Play Store, open it, and run the two commands below:
Code:
su
Code:
restorecon -FR /data/media/0
If you are on stock lollipop, it is unlikely that this is the problem, and is unlikely this will fix it, but it is always a possibility and might be worth a try. Let me know how you make out.
(The reason I am skeptical, is because usually when these commands need to be run, the device is recognized, but you can't see any of the files)
Hi, SwoRNLeaDejZ
My Nexus 7 is not rooted. I could not run the command you gave me. I am using stock Lollipop. I think it's not a problem with the storage.
Anyway, thank you for replying!
SwoRNLeaDejZ said:
Are you positive it isn't a problem with the storage itself? If you are rooted, download Terminal Emulator from the Play Store, open it, and run the two commands below:
Code:
su
Code:
restorecon -FR /data/media/0
If you are on stock lollipop, it is unlikely that this is the problem, and is unlikely this will fix it, but it is always a possibility and might be worth a try. Let me know how you make out.
(The reason I am skeptical, is because usually when these commands need to be run, the device is recognized, but you can't see any of the files)
Click to expand...
Click to collapse
Double check the stock USB cable or at least try another high quality one, I was having a similar issue with my phone and it was a bad cable (same situation, would charge bit not connect)
Agree on cable. Some will still charge, but not work for anything else
lolcopter and mhester50,
I have tried several cables including the one I use for my Samsung Note 2.
I don’t believe it is a problem with the cable.
Could it be that the USB port of the Nexus 7 is damaged for data transfer although it allows charging?
So I've recently bought a 3XL and, coming from a Mate 9 (awful replacement for my 6P when Huawei couldn't repair it after the mobo died) which was rooted and flashed with a treble ROM to get to as stock as possible I've vowed I won't root my 3XL (primarily because I have a banking app that seems to detect Magisk regardless of what I do about it).
I am wanting to grant some permissions to Tasker by adb however anything I seem to do will not give me the prompt on my phone to authorise the device fingerprints and allow me to run adb commands.
I have Ubuntu 18.10 and the latest version of android-tools. I have searched Google and XDA and followed all the usual troubleshooting methods: different cables, USB ports, toggling debugging under developer options changing the USB configuration.
I'm really hoping someone can offer some suggestion.
TIA!
beejkitsune said:
So I've recently bought a 3XL and, coming from a Mate 9 (awful replacement for my 6P when Huawei couldn't repair it after the mobo died) which was rooted and flashed with a treble ROM to get to as stock as possible I've vowed I won't root my 3XL (primarily because I have a banking app that seems to detect Magisk regardless of what I do about it).
I am wanting to grant some permissions to Tasker by adb however anything I seem to do will not give me the prompt on my phone to authorise the device fingerprints and allow me to run adb commands.
I have Ubuntu 18.10 and the latest version of android-tools. I have searched Google and XDA and followed all the usual troubleshooting methods: different cables, USB ports, toggling debugging under developer options changing the USB configuration.
I'm really hoping someone can offer some suggestion.
TIA!
Click to expand...
Click to collapse
Fastboot boot TWRP for Pixel 3 XL, it doesn't have to be installed. Then, on your Ubuntu installation, open a terminal in your Home folder
Code:
cd .android
adb push adbkey.pub /data/misc/adb/adb_keys
Alternately, you can navigate to the .android directory in your Home folder and open the terminal, but the push command is the same
Reboot the device and you should now have authorization.