For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Veid71 said:
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Click to expand...
Click to collapse
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Click to expand...
Click to collapse
I'm not sure either but i can't imagine it'll hurt to try a reboot command or to swap slots
How can this even work? ADB only works when the phone is in fastboot mode, which automatically means that Android isn't even running surely? Hence you can't run apps.
Sent from my Pixel XL using XDA-Developers Legacy app
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
NO
With two phones and adb over network you can send a command to another phone using Tasker (maybe other apps too, only ever used it while looking for an answer to your same question). I know I at least sent reboot from one phone to another... But I think fastboot won't work like this, only (simple) adb shell commands - I'm pretty sure I gave up on it once I realized that I think it is not possible to change boot slots using this method....
Other than that, FlashFire can be used I a rooted phone to change boot slot - wipe dalvik and reboot to other boot slot. I don't know a way on a non rooted phone - anyone know a way without using pc and fastboot?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
For fastboot and adb in recovery, you'll need the phone connected to to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely, but you won't be able to see the phone's screen.
For adb in normal boot, you can either use "adb over network" (LAN) (if WAN, you'll need to bypass firewall if any) or connect your phone to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely. You can see the phone's screen using tools such as AirDroid or TeamViewer.
Related
Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!
You have the Motorola v4.9 USB charging drivers installed?
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.
bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.
Ah, Mac, I'm of no use to you then.
Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
Whenever I try to flash TWRP to my phone it says "error: more than one device or emulator". Can someone help?
tyboxer13 said:
Whenever I try to flash TWRP to my phone it says "error: more than one device or emulator". Can someone help?
Click to expand...
Click to collapse
I'd guess it is some problem with the adb server. Close all cmd and open a new one. Navigate to your adb/fastboot folder and enter the following:
adb kill-server
adb start-server
adb usb
adb devices
If it starts up again and all is fine it should show your device after the last command.
Btw. why is everybody using an all in one toolkit instead of learning to work with adb fastboot properly and doing it the old fashioned way: reading all that's needed to know and start off step by step.
Sent from my HTC One_M8 using XDA Free mobile app
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
djr83 said:
I recently updated to Android 5.0.1 on my M8 GPe and it seems to work just fine. Today I wanted to flash a custom recovery but I couldn't get any connection between the phone and the computer. When I enter fastboot I don't get "fastboot usb" as I usually do.
Do I need new drivers or something? I have both Windows 7 and OS X 10.10 so a solution for either is ok.
Click to expand...
Click to collapse
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Heisenberg420 said:
I was also unable to get fastboot working.
For custom recovery I used adb shell and used the dd cmd, worked fine
Click to expand...
Click to collapse
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
djr83 said:
I don't think I get any connection with adb either? But I'll try that. What command should I use to flash the recovery image in adb?
Edit: adb devices shows an empty list.
Click to expand...
Click to collapse
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Heisenberg420 said:
Connect via USB
To see if you have a connection type
Adb devices
U should see a device
Then follow these directions
http://www.teamw.in/project/twrp2/225
You should copy and paste the dd cmd directly into terminal, if you typo that one u may brick ur device
Click to expand...
Click to collapse
Exactly, I'm not getting any devices.
djr83 said:
Exactly, I'm not getting any devices.
Click to expand...
Click to collapse
Have u enabled USB debugging in developer options?
Heisenberg420 said:
Have u enabled USB debugging in developer options?
Click to expand...
Click to collapse
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Edit: Tried another USB port on the computer and it's working now.
djr83 said:
Yes. And nothing has changed on the computer since before I updated to 5.0.1.
Click to expand...
Click to collapse
I'd say its the drivers. Try to reinstall
You can try adb over WiFi without the drivers, download an adb wireless app from the market, enable it, get the IP address of your phone in the app, then connect through adb
Adb connect <IP[emoji14]ORT HERE>
then try adb devices
On a fresh device, I used KingRoot and obtained Flashify to try to flash on the TWRP for my device with the intention of putting on Cyanogenmod. Plain and simple, the result was this: anytime I try to enter Download Mode or Recovery Mode, I get flashing red and blue lights.
I've tried rooting with KingRoot additional times, but it always seems to go away on reboot. To make it worse, I can't even get rid of KingRoot.
Anyone got ideas? And please don't link any "D855 ONLY" threads, because I've looked through those.
i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.
G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.
inasar said:
i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.
Click to expand...
Click to collapse
From what mode can I flash it? I thought you had to be in download or fastboot mode to execute ADB shell commands.
Jahanzaibawan said:
G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.
Click to expand...
Click to collapse
It's the correct recovery file for the model. I can't get to fastboot mode.
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I've got ADB set up on my Windows PC back at home already, so I may have to wait until I get home from traveling (next Friday). All I have available to me right now is my Chromebook with Linux.
Thank you for the steps, though. I'll try that as soon as I get home. Might even try to borrow someone else's computer to give it a whirl.
inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I get "/system/bin/sh: adb: not found" when I do this. Can't seem to figure out what that means.
Do you have adb setup on your pc?
inasar said:
Do you have adb setup on your pc?
Click to expand...
Click to collapse
Yes, and when I use the adb devices command, my phone shows up.
Ok can try the same but skip the point where you type adb shell
btothemose said:
Yes, and when I use the adb devices command, my phone shows up.
Click to expand...
Click to collapse
Did you try it again. I think it should work. If it didn't then there is a very helpful post by thecubed over here which you can follow and it will work.
The thread is here. Just go through the first post which has a tutorial and steps you need to take:
http://forum.xda-developers.com/lg-...lg-g3-twrp-d852-d852g-f400-t2900614?nocache=1