Hi,
I'm having some difficulties connecting to the wireless network (eduroam) at my university. Sometimes I can connect easily, others the device keeps trying to get the ip address and them says unsuccessful... Is there any way to see the log from the wifi connection?
adb logcat will probably work in this case. Or if you don't have adb setup, you can also install a terminal emulator on the device, temp root using z4 and then run logcat locally.
agentdr8 said:
adb logcat will probably work in this case. Or if you don't have adb setup, you can also install a terminal emulator on the device, temp root using z4 and then run logcat locally.
Click to expand...
Click to collapse
Or, for people with a certain allergy against terminals and shells: Install Quick System Info Pro and take it from there.
Alogcat does the job too.
i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way
Find one of the old guides to rooting, with instructions on getting it recognized by adb. Mostly need to edit a config file, iirc.
Sent from my Kindle Fire using xda premium
oxlong27 said:
i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules
jcase said:
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules
Click to expand...
Click to collapse
What exactly do I add to the udev rules in my 51. Android rules? Any way someone can type it exact so I can copy and paste? I never ran into issues like this usually rooting my devices on Linux is smooth as butter. Thanks jcase
Could u elaborate a little I'm a little new to linux
Sent from my ADR6425LVW using xda premium
Hi all,
After unlocking/recovery/rooting via Heisenberg's guide, I then tried to connect to my Amazon FireTV via Terminal Emulator, but when I try any adb command from it, it says:
/system/bin/sh: adb: not found
What am I missing or forgetting to do? Thanks.
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
zephiK said:
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
Click to expand...
Click to collapse
I've been using the same ADB commands in Terminal Emulator on my Android phones for years...
Anyone?
Anyone? Would really like to be able to connect to all my Android devices...
Can anyone help me with this? I can't find anything online and surprised no one else is asking about the issue...
Same issue was posted here on reddit FYI: https://www.reddit.com/r/AndroidQue.../adb_tool_no_longer_available_on_marshmallow/
How can we connect to other Android devices via Android 6.0 devices if this no longer works?
Hi guys,
I can't connect my s7 edge to my mac.
I've already downloaded Android file transfer but when I plug the phone to the computer, I have message.
In my mac, telling me that "connexion impossible" and same in my S7.
Any ideas ?
Envoyé de mon SM-G935F en utilisant Tapatalk
Try restarting Your phone. Sometimes it helps. I have a macbook pro too and it sometimes catches connection and sometimes nothing happens. Maybe try installing windows through Bootcamp? Or just copy files over using SDCard. Or try using a different USB port. Or remove Android file manager and install it again. If none of these work download samsung kies. I think they have a version for MacOSX.
I've already tried these I worked with my S5 then suddenly stopped working. Don't getting it's so weird. Will try to use kies
Envoyé de mon SM-G935F en utilisant Tapatalk
Mate, did you realise, you are trying to get Samsung & Apple to talk to each other... They only talk in legal courts..
Kidding...
I had the same thing. I removed AFT, then went into the Preferences file (Library>Preferences) and deleted Android File Transfer plist files and also downloaded the Kies DMG to get the Uninstaller app. Ran that (evrn though not installed but previously had been) then made sure no Preference files for Kies existed. Rebooted my Mac (normally don't have to like you do with windows). Booted back up and I installed Android File Transfer and it works again. Just remember that AFT does not play well with any Kies files existing on your Mac.
Sent from my SAMSUNG-SM-G935A using Tapatalk
@p2kin good point ? @burrzoo kies is not installed on my mac but if you're telling me there is troubleshoot when AFT and kies are installed. Then I think I know where the problem is coming from. I've installed SideSync the problem might be there. I'm gonna remove SideSync and see what happens
Envoyé de mon SM-G935F en utilisant Tapatalk
Aaaannnnd it worked
Thanks @buurzoo for helping me.
So for anyone that will or has trouble with android file transfer, remove kies or SideSync
Envoyé de mon SM-G935F en utilisant Tapatalk
Anyone get ADB working? I'm getting a no permissions (udev rules) on my linux machine. I'm guessing we need to add the device into udev
EDIT: Solution for Ubuntu/Linux here: https://forum.xda-developers.com/showpost.php?p=73619079&postcount=20
hmm it works on my Mac though..
did you use Sudo?
stewa2jm said:
did you use Sudo?
Click to expand...
Click to collapse
Yeah, it's not working.. I tried adding the dev in my android.rules file and still nothing. I'm going to play with it more now
Sent from my PH-1 using Tapatalk
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
stewa2jm said:
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
Click to expand...
Click to collapse
I'm always on the latest version since I do a lot of Android development. I don't get why it's not working.. I've had to add devices in udev so many times, never did it give me an issue before. I'll see if I can figure it out though
Sent from my PH-1 using Tapatalk
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
IM0001 said:
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
Click to expand...
Click to collapse
Really? Lol I did mention it works on my Mac, so yeah.. It's turned on.. I've even tried turning it off and then on again. [emoji1] [emoji1] [emoji1] [emoji1]
stewa2jm said:
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
Click to expand...
Click to collapse
Will do!
Sent from my PH-1 using Tapatalk
any idea whats causing adb to not work?
drocny87 said:
I found a work-a-round to transfer your files from one phone to the Essential.
create a folder on your desktop and copy and paste all files you want transferred to the PH1. Once you have completed that just copy and paste those files from that folder to the phone.
Click to expand...
Click to collapse
wow, an extremely obvious solution to a problem no one asked about and has nothing to do with this thread!!
I've got ADB to connect somewhat. Instead of cd\sdk\platform-tools just run cd\sdk. ADB devices shows my phone, but once I ADB reboot bootloader, it will boot into the bootloader, but that's it.
I can't get it to work at all windows 10
Sent from my PH-1 using Tapatalk
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
skw5115 said:
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
Click to expand...
Click to collapse
What is your usb setting? Charging, file transfer?
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
I tried on both already
Sent from my PH-1 using Tapatalk
I got ADB working on linux. You need to add this to your 51-android.rules
#Essential
SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="plugdev"
I still can't get fastboot to work yet though. To get it to work I need to run: sudo $(which fastboot) devices
I'm going to play around with it more to see if I can get it to work just using fastboot devices
ADB is working on Windows 10, but as mentioned above, fastboot isn't recognized. Can't unlock the effing bootloader without that dammit.
---------- Post added at 08:20 PM ---------- Previous post was at 08:14 PM ----------
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
File transfer
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
skw5115 said:
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
Click to expand...
Click to collapse
Same here, just manually installed Google USB Driver and installed it as "Fastboot Interface" and it worked.
Ok I got adb and fastboot both working on Ubuntu/Linux now. Instead of adding the line I posted in my previous post just run this:
sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
Then
sudo service udev restart
Then ubplug your device if it's plugged in via USB and then plug it back in. adb works as well as fastboot