Database Users

[Q] Galaxy S4 USB OTG Ethernet?

Hi all,
Can anyone with a USB to Ethernet adapter please test if this works with the Galaxy S4 using an OTG USB cable? I have read it works with the Nexus 7 but would love to know if it works with the Galaxy S4. Would be quite handy to hook up the galaxy directly to my 100mb internet.
Thank you.

S4 tested with two USB Ethernet modules. unsuccessfully
delucz said:
Hi all,
Can anyone with a USB to Ethernet adapter please test if this works with the Galaxy S4 using an OTG USB cable? I have read it works with the Nexus 7 but would love to know if it works with the Galaxy S4. Would be quite handy to hook up the galaxy directly to my 100mb internet.
Thank you.
Click to expand...
Click to collapse
I tried with some generic USB - 10/100 Ethernet (its working with Android 4.0.1 in Point of View TV Stick) and Delock Gigabit USB (not testetd with Android previously) but not working with S4. I check OTG cable connecting USB flash drive and it works with S4, same with USB mouse and USB keyboard. This Ethernet 10/100 USB module after connecting to S4 lights up so its powered but S4 does not looks like recognize it. i have to small knowledge or S4 hasn.t some drivers.

RMPL said:
I tried with some generic USB - 10/100 Ethernet (its working with Android 4.0.1 in Point of View TV Stick) and Delock Gigabit USB (not testetd with Android previously) but not working with S4. I check OTG cable connecting USB flash drive and it works with S4, same with USB mouse and USB keyboard. This Ethernet 10/100 USB module after connecting to S4 lights up so its powered but S4 does not looks like recognize it. i have to small knowledge or S4 hasn.t some drivers.
Click to expand...
Click to collapse
Thanks for trying! A few people have tried with no luck unfortunately. Hopefully someone can create a loadable module that contains ethernet drivers for the S4!
Cheers

RMPL said:
I tried with some generic USB - 10/100 Ethernet (its working with Android 4.0.1 in Point of View TV Stick) and Delock Gigabit USB (not testetd with Android previously) but not working with S4. I check OTG cable connecting USB flash drive and it works with S4, same with USB mouse and USB keyboard. This Ethernet 10/100 USB module after connecting to S4 lights up so its powered but S4 does not looks like recognize it. i have to small knowledge or S4 hasn.t some drivers.
Click to expand...
Click to collapse
Have you tried this with a powered USB hub?

Just tested - negative result.
NZtechfreak said:
Have you tried this with a powered USB hub?
Click to expand...
Click to collapse
S4 connected via OTG to extrenally powered USB HUB. Ethernet USB adapter connected to Hub. Nothing happens on S4.
To verify connect USB Flash drive to USB hub and its sucessfully detected and browsed on S4 (so hub itself working).
Tested USB Ethernets:
USB Ethernet 10/100 "JP1081B"
USB Ethernet 10/100/1000 "Delock 61730"

RMPL said:
S4 connected via OTG to extrenally powered USB HUB. Ethernet USB adapter connected to Hub. Nothing happens on S4.
To verify connect USB Flash drive to USB hub and its sucessfully detected and browsed on S4 (so hub itself working).
Tested USB Ethernets:
USB Ethernet 10/100 "JP1081B"
USB Ethernet 10/100/1000 "Delock 61730"
Click to expand...
Click to collapse
I thought that would likely be the result, but always worth checking non-working USB OTG stuff with a powered hub.
I have a couple of different ethernet adapters, driverless ones that are confirmed working with the few Android devices (tablets) that have been reported to work with ethernet connections, will post results when I get them (I expect them not to work).

NZtechfreak said:
I thought that would likely be the result, but always worth checking non-working USB OTG stuff with a powered hub.
I have a couple of different ethernet adapters, driverless ones that are confirmed working with the few Android devices (tablets) that have been reported to work with ethernet connections, will post results when I get them (I expect them not to work).
Click to expand...
Click to collapse
Fingers crossed but I have my doubts too unfortunately.

Any updates to this interesting thread?
I too would like to get this going with my new Samsung S4, mine is via Sprint, if that matters.
I have tried to OTG cable w/ a USB and StickMount Pro, that works.
BTW, my S4 is rooted via the CF Auto Root method.

has anyone actually found a driver for this?

Possible???
Is this in any way possible?? I am planning to buy one adapter for my s4. Is it worth buying??

I would be interested. The device recognizes it but does not work with this program Ethernet Google Play.
Forgive my language I'm using Google Translator Spanish to English.
I saw a post to introduce myself.
Thank you

Thank you All. Following is how I got LAN Ethernet to work on my Galaxy S4. Some of these steps are very risky and may wipe out all your phone data or make your phone unusable. So I am not recommending you to try it. I am only sharing what I did in my phone to make it work with OTG Ethernet. Also the procedures are very device and version specific. Even same model phones with different Build version and Android version may give different results.
My Devices:
Samsung Galaxy S4 Model Number: SGH-I337M
Android version: 5.0.1 (Lollipop) SDK 21
CPU Architecture: ARMv7
Build Fingerprint: jfltevl/jfltecan
BobJGear OTG Ethernet
ASIX AX88772A Chipset
Following is the Summary of the key steps and troubleshooting. You can search online to find the APKs and Installers or to know more details.
Install Droid Info App to get details of the phone CPU
Install Kingo ROOT App on the Phone and Root the Galaxy S4
Install Odin3 v3.13.1 on Windows 10 PC
Use Odin3 to install “Team Win Recovery Project” (TWRP) on the phone. TWRP was necessary to install XPOSED Framework. The specific version of TWRK that I could install is TWRP 3.1.1.0. I installed it using the file with following file name:
“twrp-3.1.1-0-jfltecan.img.tar”.
The other newer version of TWRP did not work. It kept going back to default recovery menu. Also uncheck “Auto Reboot” in the Odin Options and manually reboot phone to Recovery mode after installing TWRP from Odin.
If you get following message when trying to start TWRP in Recovery mode, Just wait few minutes and TWRP will start.
RECOVERY IS NOT SEANDROID ENFORING
SET WARRANT BIT RECOVERY
During TWRP initial setup Swipe to “allow modification” to System partition
Install XPOSED Installer using apk with following file name. This is an App used to install XPOSED Framework.
"Xposed-Installer-3.0-Alpha-4-2016.10.16.apk"
After installing it, it showed warning that it is not compatible with my phone and android version. Leave the XPOSED Installer installed. Use alternate method to install XPOSED Framework using TWRP.
Install XPOSED Framework using TWRP. I installed the XPOSED Framework version 87.1. That is the only version that worked. I used zip file with following file name
“xposed-v87.1-samsung-5.0.x-sdk21-by-dkcldark-arm.zip”
The other versions of XPOSED Framework was giving following errors.
The installed firmware is not deodexed!
This version of Xposed requires deodexed firmware!
After installing XPOSED Framework, open XPOSED Installer and install Hack Connectivity Service
Install Terminal Emulator.
Sometimes after reboot, the Terminal Emulator shows blank screen. Wait for a minute or so and it should show the usual prompt where you can enter the commands.
Install SuperSU Free v2.79
I installed Ethernet Droid apk, but it did not work.
I installed Busybox but it was not necessary to be used
Usual Steps
Once everything is installed, following are the usual steps to connect to Ethernet.
Connect the Ethernet OTG to Smartphone.
Disable Wifi
Enable Wifi Hack in “Hack Connectivity Service”
Start Terminal Emulator and run following commands. This needs to be done every time we switch from Wifi to Ethernet.
Code:
su
netcfg eth0 dhcp
ip rule add from all lookup main pref 99
ndc resolver setnetdns eth0 "" 8.8.8.8 8.8.4.4
exit
If I don't use the above "ip rule" command, I can only ping to router using Superuser and Internet does not work.
Also previously it was not recognizing website names while pinging. the "ndc resolver" command resolved that issue.
Once above commands are executed, I can use LAN Internet on my Galaxy S4.
Update on Nov 19, 2019:
For the Usual Steps, the Terminal Emulator Commands after "su" line can be saved in a file in the local storage of the phone with name such as "lan.sh" then following commands can be used to execute the file.
su
cd sdcard
sh lan.sh
Video Demonstration
The demonstration of my final results is in my following video. It also has an example of Simultaneous Charging while using OTG Adapter.
https://youtu.be/RtLV6qpMm6o

Root from 2016 MacBook Pro?

Hey all,
Has anyone been able to successfully root from a MacBook Pro 2016 with USB Type C ports? Having problem getting adb to list my Shield. This is on:
2016 Macbook Pro w/ macOS Sierra 10.12.3
WAWPI USB 3.0 A Male to A Male Cable
Apple USB-C to USB Adapter
Android Debug Bridge version 1.0.36 (Revision 84e3321d5db3-android)
System Information -> USB shows Shield but adb devices does not. I was able to connect with adb connect <IP> but not USB. I've seen various threads pointing to a possible issue with Mac USB Type C/Thunderbolt 3 ports.
Any help would be appreciated.
EDIT: adb command works with about mentioned cable and adapter. The real issue is fastboot. It constantly freezes/crashes macOS. I think my Mac was in a funky state preventing adb command from listing devices. Unfortunately, this still prevents me from performing a complete root from this macbook. I was able to complete root with another macbook with USB ports. So does anyone have a fix or workaround for fastboot other than running a VM or bootcamp?
EDIT2: In case anyone is following this thread... There's an open bug for this and a fix is in QA. New release coming.

Thanks for this post.. I was confused about what the issue was.

Android phone to root shield?

I dont have a laptop to move near my Shield Tv to use adb. Could all the same be done on my Android phone using Terminal Emulator, or does that over-complicate rooting the Shield Tv?

No help yet....?
Well first you'd have to have adb/fastboot and you'd have to have driver's to connect to device.
I fly racing drones and have seen a clean flight app for configuring flight controller changes. That involves connecting your quad flight controller to your Android device with a USB cable. Typically you would use a PC with drivers very similar an operation to running fastboot to root your phone. I think it comes down to which device is running command prompt can connect with its drivers to the Target device
You should post in other forums like in adb development forum or Nexus up forum.

I suppose I could try it for the yucks... But, since your the One asking? Why don't you just download a Terminal Editor (From the PlayStore), which should allow you to use (e.g. emulate), ADB at the least of it. Not sure if it'll be of much help to you at the Fastboot Level though.
TBQH: I'm not sure this is the best plan of attack. As you would almost have to be very meticulous here, as to not accidentally flash your Phablet with the Shield TV Firmware, or vise-versa.
*EDIT*
Just outta ****s, and giggles I decided to just try it out to see how far One could get with it. As it turns out, you can at least get into the Fastboot System like this. However since I don't have anything like Fastboot, or ADB as a callable executable (From Emulated Android Terminal), I can't issue any Fastboot commands durr.
It could be interesting to look Into if there isn't an Android OS version of Fastboot that could be ran from the Terminal. But, my guess is there wouldn't be. As 99.9% of Devices out there don't require you to be patched into a USB Host just to get into Fastboot / Update / Recovery Mode. And for the times when you do need a PC there is bespoke Software like Kies, or Odin out there to make that task simpler.
*EDIT II*
A quick shufti on ATE, and Fastboot brought up this Gem.
http://www.nairaland.com/2351005/how-set-up-run-fastboot
Of course the usual caveats about being Rooted, (The Device from which you plan to root from. e.g. your Phablet), apply.

I've tried this with my Nexus 6p. 7.1.1 Pure Nexus ROM. ElementalX​ Kernel. Rooted. I used the included USB C to USB A cable and was never able to get the Shield to show up under adb devices.
I ended up just splicing two broken micro USB cables. You just cut and match the colors. I didn't even seal the wires. No solder, no electrical tape. No heat shrink. Just made sure none of the splices were touching and it worked just fine on my laptop connected to the shield TV 2017. These were USB 2.0 cables. But make sure they're data cables and you shouldn't have any issues.
I personally tried many versions of adb for Android and could never get the Shield to show up. So I just gave up and make the USB A male to male cable and did it the right way.
Sent from my Pixel+XL using Tapatalk

MTP and ADB on switch

Hi all,
so i have got android installed on my switch but cannot seem to get the usb to work at all for ADB and MTP.
the switch does not show anything when it is connected by usb and it does not appear in device manager or adb on the host machine.
i have enabled developer mode and debug over USB.
i have tried to connect to ADB via the network but this lead to the authentication failing
does anyone have any ideas of what could be the issue?

I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't

Laurin Neff said:
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Click to expand...
Click to collapse
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.

Roy8765 said:
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Click to expand...
Click to collapse
Just flash magisk, it's what I did and now I have root.

Question for Surfer or any other Android guru.

Is adb not able to connect over even see these Joying FYT Airmont units with Oreo on it?
The head unit has a switch to allow debug over usb but when I connect a usb to my laptop I don't get the dialogue screen on the head unit asking if I want to connect to this device and the laptop cannot see the unit at all.
I figured maybe it needed device specific drivers in Windows so figuring Joying hasn't made any I found universal usb drivers for it. Nothing.
I got an app called Naptime or something that's supposed to be able to put the unit in full doze. It's designed to work on rooted devices but also says that can be worked around by using adb to give certain permissions. I can't do that if I can't even connect adb to the damn thing.

Also, is rooting these using that Magisk method result in the same type of full root the normal way on other devices? It isn't limited compared to the normal way is it?

You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory

surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
Click to expand...
Click to collapse
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.

rigattoni said:
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
Click to expand...
Click to collapse
These commands require root

surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
Click to expand...
Click to collapse
Maybe I'm doing something wrong then. The developer options are enabled and I have it set for unlocked bootloader but my laptop can't see it whether I'm connected through the OTG usb port or the standard one and the HU doesn't give the popup dialogue asking if I want to allow the connection like my tablet and phone did. Maybe they changed something with these particular units with the new UI?
I did notice on another thread someone that had a FYT Joying Airmont with 8.1 and they said something about the 3 dot menu on the top right for "USB Connection" that brings up two options both in Chinese an his only worked on the lower option. I did try that too but still nothing. IDK. Maybe I had something else set wrong when I tried that lower option that made it not work in all my effort yesterday to get adb to see it and connect.