Database Info

[Q] ADB error device not found OSX

Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.

Forgive me for asking the obvious, but do you have USB Debugging enabled?

distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.

Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?

distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try

Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.

distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac

kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).

Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.

distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.

Fastboot devices gave me this output:
serial# fastboot

kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.

distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.

kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.

distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe

kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).

Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck

no ADB connection anymore

ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "ADB devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!

yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
shouldnt it be adb devices instead of dab ?

I wanna try this ABD but there no link?!!

Shouldn't this ABC post be somewhere else?

you guys should quit cluttering this thread and help him figure this whole KFC thing out....

sheetmetalninja said:
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
Click to expand...
Click to collapse
You're right.
But I also don't know anything about BAD or FASTBOOB or anything like that. I don't like reading. :[

yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.

Check the drivers, you may need to update them
Sent from my Desire HD using XDA App

taney said:
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Click to expand...
Click to collapse
how 2 do that? i mean what do you mean with devmgmt.msc(device management...?)
1) usb cable is good, the original one. also tried different usb cables, it doesn't matter.
2) usb port is also ok, other devices running out of the box (f.e. dvd drive oder dslr)
3) adb driver already updated via "Android SDK and AVD Manager".
i installed Android SDK tools, SDK Platform tools, sdk platform (--> is there sth. missing?)

Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again

Romanbb said:
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Click to expand...
Click to collapse
no sorry...won't work..
getting the same:
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
also tried without fastboot rebooting.

there are news guys:
just got an windows 7 personal computer for a couple of days.
installing the sdk and usb driver just worked fine.
why it doesn't work for mac?
already installed all new...

You may also check the cable you're using to connect the phone to your Mac. I was getting the same problem when trying to use the cable from my car charger - the phone was not even visible on the system list of USB devices. Using the cable that came with the phone did the trick.
(although if you used the same cable with Windows and it worked, my hint won't be of much help)

Do you got HTC sync installed on your PC?

TheStigx said:
Do you got HTC sync installed on your PC?
Click to expand...
Click to collapse
please remember - i'm using a MAC!
so finally i tested my device with several computers at the university.
i just found out, that the problem may been caused of my installed mac osx lion - but don't ask me why!
on the mac of my prof (also osx lion with latest updates) it worked out of the box...
--> so i'm gonna making backups now and will format my hard disk and reinstall lion again.
i'll give u feedback again ;-)

Have you closed the htc-sync application? solved the connection-error for me...

Maeffjus said:
Have you closed the htc-sync application? solved the connection-error for me...
Click to expand...
Click to collapse
again guys:
I'm using a MAC!
is there any official sync app for mac i don't know about??

ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.

yasinis said:
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
Click to expand...
Click to collapse
ok, just found out where the problem was caused. it was EasyTether!
this will help:
Code:
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

[Q] No matter what ADB reports "List of devices attached" EMPTY

Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.

studioleland said:
Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.
Click to expand...
Click to collapse
The HTC Sync app on your laptop should be removed. You only needed it to install the drivers, then per the Firewater instructions, Sync should be uninstalled. I don't know if that's what's causing your problems, but try it.

per the Firewater instructions, Sync should be uninstalled
Click to expand...
Click to collapse
I did try that as well. Do I need to remove and restart? I will try that.

studioleland said:
I did try that as well. Do I need to remove and restart? I will try that.
Click to expand...
Click to collapse
Possibly? I'm not a mac guy so I don't know, sorry.

sfreemanoh said:
Possibly? I'm not a mac guy so I don't know, sorry.
Click to expand...
Click to collapse
WOW! Got it! This will no doubt save some people. From stackoverflow:
If you have installed the application EasyTether, this can interfere with ADB.
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
Click to expand...
Click to collapse
Boom! It worked.

studioleland said:
WOW! Got it! This will no doubt save some people. From stackoverflow:
Boom! It worked.
Click to expand...
Click to collapse
Ahh, yeah... That was mentioned in the firewater instructions.
"All other phone software removed or disabled (Samsung Kies, PDANet, etc.)"

studioleland said:
WOW! Got it! This will no doubt save some people. From stackoverflow:
Boom! It worked.
Click to expand...
Click to collapse
hey what did you do to fix it ? i spent hours trying to unlock this thing and now my phone is with a guy that owns a computer store trying to do it for me . please help me out

ANTHONY81L said:
hey what did you do to fix it ? i spent hours trying to unlock this thing and now my phone is with a guy that owns a computer store trying to do it for me . please help me out
Click to expand...
Click to collapse
Happy to be of help if I can. What step are you stuck on. Can you post a list of steps taken already?

studioleland said:
Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.
Click to expand...
Click to collapse
How did you do it..mine also says "list of devices attached "..

Step 1 : stop adb by typing code
adb kill-server
Step 2: remove the usb cable from the computer and phone
Step 3: disable usb debugging on your phone
Step 4: Enable usb debugging on your phone
Step 5: Connect usb to your phone and computer
Step 6: kill adb server by typing the code
adb kill-server
Step 7: ???
Step 8: Profit

Question ADB TCPIP mode w/o cable

I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. The Tasker trick is waaay too complicated, and I couldn't make it work on my Pixel 7 Pro.
When root is available, things look simple: run "setprop persist.adb.tcp.port 5555" or modify /system/build.prop to include a line to that effect. Assume that I go to the trouble of rooting my phone, and make the requisite change in /system/build.prop, will I be able to un-root afterward while keeping the change I made intact?
Edit: here's a wild thought: maybe I can actually tinker with the official Android factory image, hence add the requisite line to /system/build.prop in vitro, as it were, repackage the whole thing as a modified image, and then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?

Aqua1ung said:
I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. (...)
Click to expand...
Click to collapse
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

ze7zez said:
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.

Aqua1ung said:
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.
Click to expand...
Click to collapse
Are your tools up to date? What is the output of:
Code:
adb version

Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb

Aqua1ung said:
Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Click to expand...
Click to collapse
Update your tools, you should be on 33:
Code:
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as /usr/lib/android-sdk/platform-tools/adb

I have a script for that, I forgot to include it...
Edit: can't attach it for some reason, anyways, here's a link to my git: update_platform_tools

Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service

Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
Do you have your phone and PC connected via wifi to the same router?

ze7zez said:
Do you have your phone and PC connected via wifi to the same router?
Click to expand...
Click to collapse
Same router, yes, though my PC is on a wired connection.

Aqua1ung said:
Same router, yes, though my PC is on a wired connection.
Click to expand...
Click to collapse
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.

ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
I was about to see if I could do that, lol, my box is wired as well

ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?

Aqua1ung said:
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?
Click to expand...
Click to collapse
As for things you can do with root, I have nothing to offer, in fact, I am totally against it. It just causes unnecessary problems with the device.
However, you *may* be able to modify the stock rom with an Android ROM Kitchen, emphasis on the "may".

Aqua1ung said:
(...) then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?
Click to expand...
Click to collapse
So what's would the point of OTA file signatures if anyone could modify the original ROM with dangerous changes?

Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
It worked fine for me after killing adb ($ adb kill-server)

Tasker and LADB app are working on my P7P perfectly, no cable required, no root - more info here.