Hello,
Im using a S3 Neo like this Section implies.
My problem is, that i can transfer files of the cellphone to my computer with debian 8 jessie, but i cant transfer files of my pc to the s3 neo
PHP:
[email protected]:/lib# adb devices -l
List of devices attached
[email protected]:/lib# mtp-detect
[HIDE]
android-tools-adb of the debian repo doenst help and mtp-detect, detects nothing.
dolphin explorer can open the cellphone and there are 2(1) cellphones shown in the contextmenu of kde.
back in the days with windows it was plug&play to transfer files between it
im curious about that debian shows up two devices, too.
i followed the ubuntu wiki with jmtpfs too and the debian wiki itself, nothing worked.
Desktop
[email protected]:/lib# uname -a
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) x86_64 GNU/Linux
Samsung S3 Neo not rooted/jailbreaked, just stock and never touched anything.
edit my text is too long, i outsourced the mtp-detect echo
docs.google.com/document/d/1cKqfjY4oyU4ckZeYweg6AhjJ2o-h7ssiOegvuBgJt1M/edit?usp=sharing
Related
Ok,
So Ive been scouring the net to find out if there is anyway I can get my device to be recognized. So far I've tried:
Windows 7 Ultimate 64bit, phone goes into storage mode and loads the drivers. although the drivers are not signed so windows refuses to load them, nice microsoft.
Ubuntu 10.04 64bit, ok i've installed usb_modeswitch and setup a bunch of udev rules (attached) and I can get the device to be detected but not recognized ie if I execute
Code:
adb devices
I get
Code:
List of devices attached
???????????? device
if I try
Code:
adb shell
I get dropped right into the user shell on the device. *Nice* score one for linux, but this doesn't do me much good because if I try to bring up the dalvik monitor it refuses to recognize the device grrr bad linux
I've attached my udev rules and a listing from when I tried to start the dalvik monitor, if anybody has some idea how I can get either windows to load the provided drivers or ubuntu to recognize the device I would be eternally greatfull
Thanks
Tired and wear from trudging around the net all day
Ben
So I found a guide on how to mount my n7 under linux.
the only proble is that I have to enter the command "sudo mtpfs -o allow_other /media/Nexus7" everytime I plug it in.
Is there a way to automate this?
The guide can be found here.
http://www.nexus7tablethelp.com/2012/07/connect-nexus-7-to-linux-via-mtp-using.html
What linux disto are you running? If you're using Ubuntu w/ Unity, this is much easier: ubuntuforums.org/showthread.php?t=1895820.
For what it's worth, I manage my Nexus 7 through gMTP (available in software center) on Ubuntu 12.04. It's not the fastest thing in the world, and sometimes it acts like it's locked up when it's still thinking, but it's never let me down.
Thanks guys!
I developed a little tool which can be used to connect and disconnect adb sessions to Android devices via wifi.
Maby some of you will find it handy
The tool is targeted at Ubuntu 12.04 or above but it should run on other distributions too.
The following libraries will be needed to run this program:
Code:
libgtkmm-3.0-dev
libglibmm-2.4-dev
libsigc++-2.0-dev
libappindicator3-dev
libsqlite3-dev
libnotify-dev
The code is available here
The License is GPL3.
32-Bit version and debian packages will follow soon.
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
gus_zernial said:
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
Click to expand...
Click to collapse
Why are you wanting to use ADB or SDK?
Make sure you have Samsung drivers installed.
My pc recognizes my G935F right away.
gus_zernial said:
I have a Kubuntu 15.10 linux PC and a S7 Edge Exynos SM-G935FD phone running Android 6.01. The phone is rooted using Chainfire auto-root. Linux and adb don't recognize the phone ... when the phone is connected to the linux PC using a USB cable, the phone doesn't show up in lsusb list of devices or in the adb devices command (either when the phone is in recovery mode or in normal mode). Here's what I've done:
-Enabled Developer Options, USB Debugging and USB Configuration MTP on the phone
-Installed the latest Android SDK including Android 6.0 Support and all available updates on the linux box.
-Created /etc/udev/rules.d/51-android.rules on the line below on the linux box
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
permissions on that file are -rw-r--r-- 1 root root 71 May 4 14:07 /etc/udev/rules.d/51-android.rules
-rebooted the linux box and the phone a million times, and killed/restarted the adb server a million and a half times
I do see messages in the syslog on the linux box in attachment hereto - not sure what they mean. I'd very much appreciate recommendations how to diagnose and/or fix. Thx, Gus
Click to expand...
Click to collapse
"POWWWWER...SPEEEEED !"
Sent from my Echoe Powered Stig driven G935F
> Why are you wanting to use ADB or SDK?
For the same reason thousands of other developers do
> Make sure you have Samsung drivers installed.
Linux does not require special USB drivers for ADB
> My pc recognizes my G935F right away.
Is your PC running Linux?
And no, don't ask me why I use Linux instead of Windows, as most Android developers do.
Gus
here is also trouble shooting information
~~~~~~~~~~~~~~~~~~~~~~~
https://store.askey.com/adt-3.html
~~~~~~~~~~~~~~~~~~~~~~~
android 13
for google tv and android tv
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android 13 for TV | Android Developers
developer.android.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
android 12
for google tv and android tv
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
https://developer.android.com/tv/release/12#install-manual
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
android x86
android (tv / tablet / pc) version. i
this runs on laptops and in virtual machines. its stock un bloated
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android-x86
Android-x86: Free software download for windows, linux.
www.fosshub.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------
and now linux options for android tv boxes
-----------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GitHub - 833M0L3/H96MaxX3: Install Linux on H96 Max X3 / Amlogic S905X3 TV Box. Cheap alternative to Raspberry Pi's for making a headless home server.
Install Linux on H96 Max X3 / Amlogic S905X3 TV Box. Cheap alternative to Raspberry Pi's for making a headless home server. - GitHub - 833M0L3/H96MaxX3: Install Linux on H96 Max X3 / Amlogic S9...
github.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linux images for android tv boxes (currently avalaible: archlinux, kali linux) - FreakTab
This topic if for people who want to run linux on thier android tv boxes (by linux i mean kali linux and arch linux) kali linux and arch linux images can be found here: https://disk.yandex.com/d/q3R5VgmiDDLq6w Steps to run linux. 1. Flash the image you downloaded from the link above to an...
forum.freaktab.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Armbian for Amlogic S805 and S802/S812
forum.armbian.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
this is my fav
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kali ARM Statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hack the world
and for reading this as an added bonus... free premium youtube version for android devices ... no ads , download video and/or audio, plays with screen off, no ads any where, picture in picture, back ground play, and no ads
Alright I'm no expert on Android tv boxes but is it possible to flash this without unlocking the bootloader?
Like I've got a tivo 4k box that is android 9 and tivo isn't releasing updates anymore as far as I can tell. So could I flash android tv 12 or 13 on it without OEM unlock and without bootloader unlock?
With out unlocking the bootloader. Linux is going to be the best option. You can run many different linux distributions on these tv boxes. Look into kali linux for arm or ubuntu for arm. Possibly debian.
with kali live boot and a usb or flash drive. It restores a pc with black screen of death and allows access to revoer files or take over the device.
Things to note... chmod -v 7777 written before anything changes its permissions same with chmod +rwxXst or last resort chmod +rwx. Adding -v shows if it worked or not -c or -v does that.
Fsck before the path of a directory such as /dev/sda will try to repair the file system on the device listed (dev is short for device and sda is usb plug device #1)
If you put the file system with the files needed on a sd or flash drive or partition. You can mkfs.ext2 -d // /dev/ and what ever device name added to copy root directorys while making a replacement file system
dd if= insert a disk image name or a directory then type of= and insert location to flash the image to.
dd if=/dev/zero of=/dev/ and device path .. will zero a device for re write
Now if you want to edit parts of the file system then create a mount point on the same path but make a new file with mkdir -v -p /type out where you want to go. Then you can mount with files to implant or replace at the location with mount -L and the devices label/name then the paths location or /dev/sd last letter for your device and then location.
Oh and you can also mount with mount -loop and you will basically have your mount over the original one.
If you need to edit logs. type nano and the name of the file. To save what you write hold ctrl and press x then y then let go ctrl and hit enter
spart0n said:
Alright I'm no expert on Android tv boxes but is it possible to flash this without unlocking the bootloader?
Like I've got a tivo 4k box that is android 9 and tivo isn't releasing updates anymore as far as I can tell. So could I flash android tv 12 or 13 on it without OEM unlock and without bootloader unlock?
Click to expand...
Click to collapse
Android devices boot and pass permission as they pass through security. Problem is partiton 1 and partiton 3 are both partition 1 with partition 2 overlaying it. ...
This is what the gods of android use this is a tool box with magisk and pals programs https://apt.izzysoft.de/fdroid/repo/com.sanmer.mrepo_111.apk
Also with a rooted device and an adroid program called termux. You can actually manipulate other androids in lots of ways. Expecially with kali nethunter on a rooted device.. or emulated rooted device like Ld player
Termux has changed the game when it comes to altering androids.
Termux
The main termux site and help pages.
termux.dev
This on a rooted phone is a trojan horse for androids
Kali NetHunter | Kali Linux Documentation
Kali on your Android phone
www.kali.org
This is where the linux on tv boxes information is
Single Armbian image for RK + AML + AW (aarch64 ARMv8)
The start system in Coreelec is not compatible with LibreELECE Armbian etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, whic...
forum.armbian.com
Personally.. using a linux os on a sd card to wipe android tv box is easier than finding one in a billion rom you need.
They say the rock chip is impossible to brick. It has rockmode or what ever.. i ****ing bricked one last year