I just bought a new smartfren Skyworth S7 tablet, and I am trying to
connect to it through the usb cable. All the websites say I need to
install ADB (Android Debug Bridge).
The only problem is, there is only information out there on connecting
to it through Windows. I can do that if I want to by booting into
windows on my laptop, and I probably will just to understand the process
a little better, but I really want to be able to connect to it through
my opensuse system.
When I connect by opensuse, and then I run fdisk -l, I get the following:
linux-o3ef:/home/george # fdisk -l Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x5a684d71 Device Boot Start End Blocks Id System /dev/sda1 2048 52430847 26214400 1c Hidden W95 FAT32 (LBA) /dev/sda2 52430848 158926847 53248000 7 HPFS/NTFS/exFAT /dev/sda3 158926848 175704063 8388608 82 Linux swap / Solaris /dev/sda4 * 175704064 1465147391 644721664 5 Extended /dev/sda5 175706112 217649151 20971520 83 Linux /dev/sda6 217651200 259594239 20971520 83 Linux /dev/sda7 259596288 976773119 358588416 83 Linux /dev/sda8 976775168 1465147391 244186112 83 Linux Disk /dev/sdb: 1765 MB, 1765801984 bytes 55 heads, 62 sectors/track, 1011 cylinders, total 3448832 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System Disk /dev/sdc: 31.5 GB, 31499223040 bytes 255 heads, 63 sectors/track, 3829 cylinders, total 61521920 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 8192 61521919 30756864 c W95 FAT32 (LBA)
Using KDE, I mounted the device that came up, which turned out to be
/dev/sdb. It had the label “ROCKCHIPS”. I didn’t know what else to do
with it. Kparted reads it as an unpartitioned space, but as you can see
below, there is clearly some sort of partition that suse is recognizing.
On KDE it is listed as a “Linux File-CD Gadget”.
linux-o3ef:/home/george # cd /media linux-o3ef:/media # ls ROCKCHIPS linux-o3ef:/media # cd ROCKCHIPS/ linux-o3ef:/media/ROCKCHIPS # ls ..adobe-digital-editions Books Download .mmsyscache myrecord Ringtones Alarms .cr3 eBooks Movies Notifications TouchPalv5 Android DCIM kindle Music Pictures .youversion ..android_secure Digital Editions LOST.DIR myalbum Podcasts linux-o3ef:/media/ROCKCHIPS # blkid /dev/sdb /dev/sdb: LABEL="ROCKCHIPS" UUID="80F4-1401" TYPE="vfat"
So, any ideas on what to do next? I need to root the device and connect
to it because I think there are some problems on the device that can
only be sorted out by rooting it (that is what the android people call
accessing your android device by root). My thinking is that surely there
is a way to do this from a linux OS like opensuse, instead of having to
rely on Windows.
Box #1: 12.2 | KDE 4.9.2 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it