Hi guys, hope you are all okay.
I've been having some issues with using adb shell commands with Adb tools windows, for a Galaxy S8 SM-G950U (T-Mobile Variant).
Everytime I try using an ADB shell command, my phone just starts acting crazy: Making me use 2 fingers to do stuff, it gets laggier, and basically unusable. This ends up with me having to do a factory reset (it doesn't even lets me make backups) so I can recover functionality.
Has anyone experienced this before? If so, How can I solve this to use any adb command without breaking up my phone?
Thank you guys so much for taking the time to read this case.
Have a great day y'all.
Germán.
Related
Alright, Im having an issue when using adb shell. Anytime i run an adb shell whether during normal operation, recovery, or bootloader the shell only allows me to run one command then refuses anything after. Even if i just su it will not respond to any other commands. It does not disconnect me or say device not found or return any type of error, just sits there waiting. Any help would be greatly appreciated.
also just realised if i try to run an adb backup it opens up the backup screen on my device and when i click backup my data it shows it is backing up but nothing gets pushed to my computer.
So no one has any ideas?
So that's it, my Nexus 4's front glass is broken to where I can only use half the screen. I want to unlock this thing and use ShareKM (Lets me use my mouse and keyboard from my computer on my phone) and Airdroid too I guess. The reason I need help is I can't type in my PIN to unlock the phone and even if I could, I doubt I'd be able to navigate to either ShareKM or Airdroid to start them up. Is there any adb command or otherwise to forward the pin to my phone through usb and then a command to start up the apps? I just wanna be able to use it and get some stuff off before I send it in to be repaired. Thanks in advance.
Not sure about unlocking the pin through adb, but you could use adb pull to copy the files that you need off the phone.
Maybe try this tool
This will only work if your phone is rooted and I hope you enabled usb debugging and unknown sources, otherwise I don't know what to do...
If you will have passed the lockscreen, you should be able to install ShareKM and Airdroid via ADB (if you have the .apk). But I don't know if it's possible to activate ShareKM without using the touchscreen.
But just to get your data off your phone, simply use
Code:
adb pull /sdcard/
then you have a backup of your music/photos/etc
Use adb while in recovery mode. Twrp supports that. Pull the sdcard like the above post suggests.
Sent from my Xiaomi Mi2s
So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.
Annoyingly, I can't for the life of me get adb on my laptop to list my S7 Edge as an authorised device, rather it lists it as unauthorized. I'm running Superman 1.8.1.
I'm not a noob at this type of thing and I've tried all the normal solutions. Including:-
Deleting the keys in /users/user/.android/ in Windows 7 and issuing an adb kill-server and adb start-server.
In developer options I've looked for the Revoke usb debugging authorization, something every solution suggests, but the option isn't there. Perhaps it's removed by Samsung or it's a Marshamallow thing.
I've checked /data/misc/adb for any keys but, whilst the folder is there, it's empty.
Changed the connection type from MTP and back again to no avail.
Tried a different USB port.
Nothing results in a key prompt on the phone, so I can't currently use adb. Any suggestions would be welcome.
I am on stock rom unrooted and the revoke usb debugging is definitely there. Maybe it's rom related why the option is not there. Also have connected adb to my windows 7 without issue.
Sent from My Galaxy S7 Edge
Cheers. It must have something to do with the Superman rom then. Does anyone else on Superman have the same issue?
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
badhat said:
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
Click to expand...
Click to collapse
I'm confused... What are you trying to do? I've never used that command...
acejavelin said:
I'm confused... What are you trying to do? I've never used that command...
Click to expand...
Click to collapse
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
badhat said:
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
Click to expand...
Click to collapse
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or not.
acejavelin said:
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or now.
Click to expand...
Click to collapse
OK, I tried using a different Android SDK (grabbed from https://dl.google.com/android/repository/platform-tools-latest-linux.zip) and now it's working. There must be something about the one my distribution packaged that is broken.
Code:
$ adb version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r11
$ LD_LIBRARY_PATH=$PWD ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/badhat/Downloads/adb/platform-tools/adb