ADB not working on win7, win10 or OSX - Android Q&A, Help & Troubleshooting

hey there,
I am currently trying to do a factory reset / wipe my data from my Sony Xperia Z3.
The screen is unresponsive and blacked out after I dropped the device, the phone itself however is still working.
windows:
I had managed to copy data from my SD card a few weeks ago on win7 - however after I updated my PC to win10, the device does not show up any more for some reason. On my girlfriends PC (running win7), the device is shown, but does not contain any file structure (no files & folders displayed). When I run "adb devices", I get the "attached is a list of devices" like response, but without my phone being shown.
OSX:
I am now trying to do the factory reset via ADB on my macbook (since I could not get it to work on win7/win10).
I have installed Android SDK including ADB. However, when I type "adb devices" in the terminal, I get the response "-bash: adb: command not found". I should get something like "attached is a list of devices" though.
I am a novice to OSX, so maybe I am doing something wrong, but I don't know what. I included a screenshot of my installation.
If someone could help me getting access to my device through ADB, that would be great.
Thanks a lot!

Related

Eclipse can't find my device

"No compatible targets were found. Do you wish to a add new Android Virtual Device?"
I didn't really program anything yet, I'm just trying to set everything up so I can start learning how to program for an android device, but I can't seem to get past this problem.
I'm using windows 7 and a sony Xperia J.
I rebooted both already, and re-installed the drivers (assuming I installed the correct drivers, but I'm pretty sure I did)
I've been trying to solve this problem for 4 hours already... any help would be greatly appreciated
I think you have a problem with the ADB driver.
Why don't you wanna use a virtual device?
because I have to get the app on my phone in the end no matter how I test it, and to get it on I need adb anyway..
So I'd rather deal with this problem now
Ok, I prefer to use the emulator because I want to have all on the same screen.
2 more things:
- on your device, have you checked in Settings -> Developer options, the option "USB debugging"? Without it, the computer sees only the media device.
- go with a command prompt in the folder "...\android-sdk\platform-tools" and run "adb devices". This command will display all the devices connected.
Good luck!

[RESOLVED] Screen Broken - Data Recovery?

I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.

[Q] Hairybean Bootloader, forgot the ROM

So I installed "Hairybean 2.3 (4.2.1) Bootloader & Recovery.zip" onto my TF201 Transformer Prime but like a complete noob I left the ""Hairybean 2.3.zip" ROM itself off the internal storage. Now the tablet won't boot to get the ROM copied over. Even better, the microSD port on the tablet was previously hosed by my brother hammering in a card practically sideways.
How in the world do I get the ROM accessible to the tablet, or get the hairybean bootloader removed? How bad off am I?
xandroid_prime said:
So I installed "Hairybean 2.3 (4.2.1) Bootloader & Recovery.zip" onto my TF201 Transformer Prime but like a complete noob I left the ""Hairybean 2.3.zip" ROM itself off the internal storage. Now the tablet won't boot to get the ROM copied over. Even better, the microSD port on the tablet was previously hosed by my brother hammering in a card practically sideways.
How in the world do I get the ROM accessible to the tablet, or get the hairybean bootloader removed? How bad off am I?
Click to expand...
Click to collapse
While you are in TWRP you have access to ADB.
Make sure you have the drivers installed (look in device manager if there is an exclamation there or if you have a device)
Then you would need adb on your pc and put the rom.zip in the same folder as it and do adb push romname.zip /sdcard/
You should then be able to access the rom from the internal when it has finished copying.
There is an ASUS Android Devices\Android ADB Device listed under Device Manager, but when I try adb push "Hairybean 2.3.zip" /sdcard/ I get an "error: device not found".
I'd actually tried this earlier and forgot to mention it in the original post, add it to my big list of boneheadedness. What obvious bit am I missing here?
xandroid_prime said:
There is an ASUS Android Devices\Android ADB Device listed under Device Manager, but when I try adb push "Hairybean 2.3.zip" /sdcard/ I get an "error: device not found".
I'd actually tried this earlier and forgot to mention it in the original post, add it to my big list of boneheadedness. What obvious bit am I missing here?
Click to expand...
Click to collapse
type adb devices and tell me what output you get.
Sorry, yet another thing I should have listed. adb devices comes back with "list of devices attached" then a blank line. So I'm definitely doing something wrong.
Here is the adb and fastboot I use and also a link to the drivers.
http://www.androidfilehost.com/?fid=22962010882834442
OK downloaded both, when I pointed windows at this driverset the tablet now shows as "ASUS Android Composite ADB Interface". Extracted the ADB-Fastboot file and ran adb devices again, same result (no device listed).
Now what am I doing wrong? I feel like every single step I take I run into another catch-22.
xandroid_prime said:
OK downloaded both, when I pointed windows at this driverset the tablet now shows as "ASUS Android Composite ADB Interface". Extracted the ADB-Fastboot file and ran adb devices again, same result (no device listed).
Now what am I doing wrong? I feel like every single step I take I run into another catch-22.
Click to expand...
Click to collapse
Try restarting the PC.. If still broke try a different USB port. Preferably one on the back.
Multiple reboots and trying every USB port on my rig proved fruitless.
So I punted and moved this process over to a win7 laptop (was working on a Win8 desktop, if it matters) that had never been connected to the tablet, started fresh.
adb devices sees the device!
adb push "Hairybean 2.3.zip" /sdcard/ successfully completed copying the file over!
Starting the install now. Thank you so very much for the assist, I'd hit so many roadblocks I was about to surrender!
xandroid_prime said:
Multiple reboots and trying every USB port on my rig proved fruitless.
So I punted and moved this process over to a win7 laptop (was working on a Win8 desktop, if it matters) that had never been connected to the tablet, started fresh.
adb devices sees the device!
adb push "Hairybean 2.3.zip" /sdcard/ successfully completed copying the file over!
Starting the install now. Thank you so very much for the assist, I'd hit so many roadblocks I was about to surrender!
Click to expand...
Click to collapse
No problem mate. Glad you got it sorted :good:

[Q] ADB shell for recording Android 4.4.3 device screen not working

Okay so I was planning on making some YouTube videos of games and apps I like, and that in mind I got a Nexus 5. So I downloaded Android SDK and extracted all the files, installed the right driver for my Nexus 5 etc. At
At first it was hard to get it to work and I had to do lots of stuff I never knew I could, but then I finally got it to work. I manged to get it to work. Then I decided to try it on another account on my computer (not admin). That didn't work, so I went back to the admin account and now that doesnt work either.
When I try "adb shell" in command prompt it will display a message such like this: "error: device not found". Yet I get a usb debugging conformation on my phone.
What should I do?

Palm PVG100 won't show up in "adb devices"

I am trying to get an APK off a Palm PVG100 phone. On my Windows 8.1 PC, "adb" works just fine when I connect a Moto G Power. I am able to see the Moto immediately with "adb devices" and run other adb commands, including copying APKs from the Moto.
However, I have tried connecting two different Palm PVG100 phones with the same USB cable, and they never show up in "adb devices".
I have enabled USB debugging on the PVG100 and clicked to authorize the computer. And, I am able to see files in MTP mode and transfer pictures from the PVG100 in PTP mode using that cable, but no matter how many times I "adb kill-server" and "adb start-server", the list from "adb devices" is always empty when either PVG100 is attached.
I see that other folks have been able to use adb on the PVG100, see for example the thread at https://forum.xda-developers.com/t/release-palm-debloat-fixes-script-2020-03-11.4052477/
Can anyone suggest what I need to do differently? Thanks!
For the benefit of future searchers: a clean install of the latest ADB on a Windows 10 machine using the convenient tool at https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
did the trick, and I was able to see the PVG100 over adb.

Categories

Resources