trying to root android tablet

I am trying to root my android tablet so that I can modify some of the
internal settings, etc. I found an example of a debian user that did it
here: https://forum.suprbay.org/showthread.php?tid=135675

So, I downloaded superoneclick, made a directory under home, unzipped it
there, and changed the permissions to run adblinux there so that I could
execute the program.

I have not tried to do a full on install of Android-SDK. If I need to,
can someone give me a link for the right one to install?

I connected my android tablet (it is an off brand tablet called a
SkyworthS7, with Android 4.0 Ice Cream Sandwich on it) via the micro
USB. I made sure that USB Debugging was turned on. Then I ran the
following command:


~/AndroidTool/ADB> ./adblinux devices
List of devices attached

~/AndroidTool/ADB>

So you see, nothing is detected. The example I followed said that if
nothing is detected, “it may be permissions causing you issues, and you
might need to reconfigure udevd.”

So, any help? I don’t really know what to do just to get this first step

  • to get my tablet detected.

I did, by the way, also try and connect my Samsung phone the same way,
and it also was not detected.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

Hi
Have you seen this thread?
https://forums.opensuse.org/english/get-technical-help-here/applications/482255-trying-install-android-sdk.html

I would guess you need a udev rule, when you plug the device in and run the dmesg command, do you see it connected?

On 04/19/2013 12:29 PM, golson765 wrote:
> I am trying to root my android tablet so that I can modify some of the
> internal settings, etc. I found an example of a debian user that did it
> here: https://forum.suprbay.org/showthread.php?tid=135675
>
> So, I downloaded superoneclick, made a directory under home, unzipped it
> there, and changed the permissions to run adblinux there so that I could
> execute the program.
>
> I have not tried to do a full on install of Android-SDK. If I need to,
> can someone give me a link for the right one to install?
>
> I connected my android tablet (it is an off brand tablet called a
> SkyworthS7, with Android 4.0 Ice Cream Sandwich on it) via the micro
> USB. I made sure that USB Debugging was turned on. Then I ran the
> following command:
>
>


> ~/AndroidTool/ADB> ./adblinux devices
> List of devices attached
>
> ~/AndroidTool/ADB>
> 

>
> So you see, nothing is detected. The example I followed said that if
> nothing is detected, “it may be permissions causing you issues, and you
> might need to reconfigure udevd.”
>
> So, any help? I don’t really know what to do just to get this first step
> - to get my tablet detected.
>
> I did, by the way, also try and connect my Samsung phone the same way,
> and it also was not detected.
>
Just a quick follow up - I WAS able to get that command to detect my
Samsung phone. The first time I had tried it without USB Debugging
enabled on my Samsung phone, but this time it was enabled, so the
Samsung phone was detected.

However, the tablet is still not detected, and I suspect that being an
off brand, there are no udev device rules set up for it. If that is the
case, how would I figure out the hex device code to add a rule to
“51-android.rules” in the /lib/udev/rules.d directory?


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

On 04/19/2013 12:46 PM, malcolmlewis wrote:
> Hi
> Have you seen this thread?
> http://tinyurl.com/c4fleol
>
> I would guess you need a udev rule, when you plug the device in and run
> the dmesg command, do you see it connected?
>
>

Yes, I have been looking at that now, and it is helpful. I was able to
figure out that the Vendor ID was (probably) 2207. It is an Indonesian
manufacturer (and I found an Indonesian tech blogger that did basically
what I am trying to do, but was using Ubuntu). The problem there is it
is entirely in Indonesian - google translate helped get me the info I
needed there.

So, using the Vendor ID 2207, I added the following rule to
/lib/udev/rules.d/51-android.rules-


# Smartfren (Skyworth)
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0660", GROUP="users"

The blogger had put it in mode 0666, but all my other android devices in
that file were listed in 0660, so I set it like them.

Then I reloaded the udev rules with the following:


systemctl restart udev.service

Then I looked at dmesg like you suggested, and here is what it shows:


[52630.146686] usb 2-5: new high-speed USB device number 26 using ehci_hcd
[52630.261228] usb 2-5: config 1 interface 1 altsetting 0 bulk endpoint
0x85 has invalid maxpacket 64
[52630.261727] usb 2-5: New USB device found, idVendor=2207, idProduct=0010
[52630.261739] usb 2-5: New USB device strings: Mfr=2, Product=3,
SerialNumber=4
[52630.261747] usb 2-5: Product: S7
[52630.261753] usb 2-5: Manufacturer: unknown
[52630.261758] usb 2-5: SerialNumber: 0123456789ABCDEF
[52630.262608] scsi31 : usb-storage 2-5:1.0
[52631.261271] scsi 31:0:0:0: Direct-Access     Linux    File-CD
Gadget   0000 PQ: 0 ANSI: 2
[52631.262717] sd 31:0:0:0: Attached scsi generic sg5 type 0
[52631.264011] scsi 31:0:0:1: Direct-Access     Linux    File-CD
Gadget   0000 PQ: 0 ANSI: 2
[52631.265794] sd 31:0:0:1: Attached scsi generic sg6 type 0
[52631.270819] sd 31:0:0:0: [sde] Attached SCSI removable disk
[52631.275552] sd 31:0:0:1: [sdf] Attached SCSI removable disk


I am not exactly sure what to do with this. Is there a place to get it
to recognize the Manufacturer? My Samsung phone has a known manufacturer
(naturally).

In any case, I did go ahead and install theadb that came with the
android-sdk package instead of the superoneclick version. I ran it, and
same thing, no devices listed. However, it finds my samsung phone
without a problem.

When I run lsusb, it has this:


Bus 001 Device 002: ID 0ac8:c40a Z-Star Microelectronics Corp.
Bus 002 Device 026: ID 2207:0010
Bus 004 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems)
NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


So you see my tablet is detected there on the 2nd line but no other
information given, and nothing about it being in debug mode. This is
also not like the Samsung phone, which does give the full vendor
information and states that the device is in debug mode.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

An issue I’ve seen a lot is that the machine “thinks” it has to deal with a modem, therefore activates usb_modeswitching. Here’s how to stop that behaviour:
In /etc/usb_modeswitch.conf, change this line

DisableSwitching=0

to

DisableSwitching=1

Then reconnect the device and see if you can reach it.

On 04/19/2013 04:16 PM, Knurpht wrote:
> An issue I’ve seen a lot is that the machine “thinks” it has to deal
> with a modem, therefore activates usb_modeswitching. Here’s how to stop
> that behaviour:
> In /etc/usb_modeswitch.conf, change this line
>
> Code:
> --------------------
> DisableSwitching=0
> --------------------
>
> to
>
> Code:
> --------------------
> DisableSwitching=1
> --------------------
>
>
> Then reconnect the device and see if you can reach it.
>
>
Thanks for the suggestion! Unfortunately, no change.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

> android

ok…so, i also have an Android tablet and i have about 300 questions…

(maybe only 25, to start–including how to SAFELY root it, but i’m
not too keen on following the instructions of someone i do not know
their linux/android/whatever expertise and whose daddy bought them a
'Droid and if they brick it their mommy will buy’em a new one when
she runs out to buy the ‘computer expert’ some more bubble gum)

unfortunately i have not yet found a suitable forum to ask my Qs, and
now wonder: Is this the place??


dd

On Fri 19 Apr 2013 10:35:44 AM CDT, dd wrote:

> android

ok…so, i also have an Android tablet and i have about 300 questions…

(maybe only 25, to start–including how to SAFELY root it, but i’m
not too keen on following the instructions of someone i do not know
their linux/android/whatever expertise and whose daddy bought them a
'Droid and if they brick it their mommy will buy’em a new one when
she runs out to buy the ‘computer expert’ some more bubble gum)

unfortunately i have not yet found a suitable forum to ask my Qs, and
now wonder: Is this the place??

Hi
If your trying to install the openSUSE arm version, don’t see why not :wink:

The first thing I would suggest is how to recover from a ‘bricked’
state for your device. Usually it’s finding a restore image that is
suitable, I bricked my MK802 device took me a few goes to find the
right image on the net, but once I had it on an SD card and resurrected
a windows machine to run the software it was fine…


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop
up 16:32, 3 users, load average: 0.02, 0.04, 0.05
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Arrandale

This is an interesting thread indeed.

Has someone who makes Forum decisions considered adding a Specific Forum for OPENSUSE-ARM ?

Seems it won’t be long that this will be a active as Virtual Machines and 64 bit.

Unfortunately, I wouldn’t even know who/where to make that suggestion.

On 2013-04-19 16:46, cmcgrath5035 wrote:
> Unfortunately, I wouldn’t even know who/where to make that suggestion.

There is a forum here that has “suggestions” in the name :wink:


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Couple things to note, from what you posted you should be able to work with your tablet through adb but this is entirely different from being able to root your tablet. Most rooting tools do need adb or fastboot to work though and this is why you need the udev rules.
Do you know if superone click even supports your tablet or if there is even a proven root technique that works with it?

Anyway, you can download adb and fastboot herehttp://tinyurl.com/dxgvbtb and install it in your home and then run the command

adb devices

and see if your tablet shows up.

Hi
My udev rules use libmtp…;


cat /usr/lib/udev/rules.d/51-android.rules


# Android devices - UDEV Rule


# For ASUS Transformer TF101
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4e0f", SYMLINK+="libmtp-%k", MODE="0666", GROUP="users"
# For MK802
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="0003", SYMLINK+="libmtp-%k", MODE="0666", GROUP="users"

Now I run the command udevadm trigger to reload…

So if I run adb devices, I see;


adb devices
List of devices attached 
037c704343016257    device
20080411    device

Then I need to only have one device connected to shell to it…


Connect to the TF101;
adb shell
shell@android:/ $

Connect to the MK802;
adb shell
root@android:/ # 

On 04/19/2013 08:35 PM, malcolmlewis wrote:
>

> On Fri 19 Apr 2013 10:35:44 AM CDT, dd wrote:
>
>> android
> ok…so, i also have an Android tablet and i have about 300 questions…
>
> (maybe only 25, to start–including how to SAFELY root it, but i’m
> not too keen on following the instructions of someone i do not know
> their linux/android/whatever expertise and whose daddy bought them a
> 'Droid and if they brick it their mommy will buy’em a new one when
> she runs out to buy the ‘computer expert’ some more bubble gum)
>
> unfortunately i have not yet found a suitable forum to ask my Qs, and
> now wonder: Is this the place??
>
>
>

> Hi
> If your trying to install the openSUSE arm version, don’t see why not :wink:
>
> The first thing I would suggest is how to recover from a ‘bricked’
> state for your device. Usually it’s finding a restore image that is
> suitable, I bricked my MK802 device took me a few goes to find the
> right image on the net, but once I had it on an SD card and resurrected
> a windows machine to run the software it was fine…
>

This is going to be more challenging than I thought, to find a restore
image and then know how to restore the device while on a windows machine.

So far I haven’t tried it because I am afraid of bricking it and I
haven’t even looked into how to connect to my device in windows.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

On 04/20/2013 07:46 AM, anika200 wrote:
> golson765;2548983 Wrote:
>> On 04/19/2013 12:46 PM, malcolmlewis wrote:
>>> Hi
>>> Have you seen this thread?
>>> ‘Trying to install Android SDK…’ (http://tinyurl.com/c4fleol)
>>>
>>> I would guess you need a udev rule, when you plug the device in and
>> run
>>> the dmesg command, do you see it connected?
>>>
>>>
>> Yes, I have been looking at that now, and it is helpful. I was able to
>> figure out that the Vendor ID was (probably) 2207. It is an Indonesian
>> manufacturer (and I found an Indonesian tech blogger that did basically
>> what I am trying to do, but was using Ubuntu). The problem there is it
>> is entirely in Indonesian - google translate helped get me the info I
>> needed there.
>>
>> So, using the Vendor ID 2207, I added the following rule to
>> /lib/udev/rules.d/51-android.rules-
>>
> Code:
> --------------------
> > >
> > # Smartfren (Skyworth)
> > SUBSYSTEM==“usb”, ATTR{idVendor}==“2207”, MODE=“0660”, GROUP=“users”
> >
> --------------------
>> The blogger had put it in mode 0666, but all my other android devices
>> in
>> that file were listed in 0660, so I set it like them.
>>
>> Then I reloaded the udev rules with the following:
>>
> Code:
> --------------------
> > >
> > systemctl restart udev.service
> >
> --------------------
>> Then I looked at dmesg like you suggested, and here is what it shows:
>>
> Code:
> --------------------
> Couple things to note, from what you posted you should be able to work
> with your tablet through adb but this is entirely different from being
> able to root your tablet. Most rooting tools do need adb or fastboot to
> work though and this is why you need the udev rules.
> Do you know if superone click even supports your tablet or if there is
> even a proven root technique that works with it?
>
> Anyway, you can download adb and fastboot here’
> http://tinyurl.com/dxgvbtb’ (http://http://tinyurl.com/dxgvbtb) and
> install it in your home and then run the command
> Code:
> --------------------
> adb devices
> --------------------
> and see if your tablet shows up.
>
>
Ok, thanks. I downloaded fastboot and will look into how to make that
connect. Since connecting is my first step towards rooting the device,
that is what I need to focus on, I think.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

On 04/20/2013 08:26 AM, malcolmlewis wrote:
> Hi
> My udev rules use libmtp…;
>
> Code:
> --------------------
>
> cat /usr/lib/udev/rules.d/51-android.rules
>
>
> # Android devices - UDEV Rule
>
>
> # For ASUS Transformer TF101
> SUBSYSTEM==“usb”, ATTRS{idVendor}==“0b05”, ATTRS{idProduct}==“4e0f”, SYMLINK+=“libmtp-%k”, MODE=“0666”, GROUP=“users”
> # For MK802
> SUBSYSTEM==“usb”, ATTRS{idVendor}==“18d1”, ATTRS{idProduct}==“0003”, SYMLINK+=“libmtp-%k”, MODE=“0666”, GROUP=“users”
>
> --------------------
>
>
> Now I run the command udevadm trigger to reload…
>
> So if I run adb devices, I see;
>
> Code:
> --------------------
>
> adb devices
> List of devices attached
> 037c704343016257 device
> 20080411 device
>
> --------------------
>
>
>
> Then I need to only have one device connected to shell to it…
>
> Code:
> --------------------
>
> Connect to the TF101;
> adb shell
> shell@android:/ $
>
> Connect to the MK802;
> adb shell
> root@android:/ #
>
> --------------------
>
>
Ok, I am reading up on mtp. Does the use of the SYMLINKargument in your
udev rules mean that yours will automatically use libmtp?

What is the difference between using libmtp and what I am doing, and how
can I tell? Will using libmtp likely allow me to connect to my device,
which I am unable to do right now except through USB mass storage?


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

On Sun 21 Apr 2013 04:38:50 AM CDT, golson765 wrote:

On 04/20/2013 08:26 AM, malcolmlewis wrote:
> Hi
> My udev rules use libmtp…;
>
> Code:
> --------------------
>
> cat /usr/lib/udev/rules.d/51-android.rules
>
>
> # Android devices - UDEV Rule
>
>
> # For ASUS Transformer TF101
> SUBSYSTEM==“usb”, ATTRS{idVendor}==“0b05”,
> ATTRS{idProduct}==“4e0f”, SYMLINK+=“libmtp-%k”, MODE=“0666”,
> GROUP=“users” # For MK802 SUBSYSTEM==“usb”, ATTRS{idVendor}==“18d1”,
> ATTRS{idProduct}==“0003”, SYMLINK+=“libmtp-%k”, MODE=“0666”,
> GROUP=“users” --------------------
>
>
> Now I run the command udevadm trigger to reload…
>
> So if I run adb devices, I see;
>
> Code:
> --------------------
>
> adb devices
> List of devices attached
> 037c704343016257 device
> 20080411 device
>
> --------------------
>
>
>
> Then I need to only have one device connected to shell to it…
>
> Code:
> --------------------
>
> Connect to the TF101;
> adb shell
> shell@android:/ $
>
> Connect to the MK802;
> adb shell
> root@android:/ #
>
> --------------------
>
>
Ok, I am reading up on mtp. Does the use of the SYMLINKargument in your
udev rules mean that yours will automatically use libmtp?

What is the difference between using libmtp and what I am doing, and how
can I tell? Will using libmtp likely allow me to connect to my device,
which I am unable to do right now except through USB mass storage?

Hi
Yes it will use libmtp, it should help connecting… Now is there an
option on your device to enable usb debugging in the settings?


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop
up 1 day 13:00, 3 users, load average: 0.96, 1.19, 0.92
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Arrandale

I highly recommend doing some background research.

The main place to ask your questions or search about rooting and deploying alternative images are at xda-developers.com

If you want to know which openSUSE (or other) image is appropriate for your tablet, it starts with the specific ARM model and version.

The problems you’re having getting ADB to recognise your tablet are not unusual, I’ve found success is problematic, unreliable and can change quickly. For Device:Manufacturer code you should search based on your tablet name. If your tablet is off-brand, it’s even less likely you’ll be successful.

HTH,
TSU

On 04/21/2013 11:46 PM, tsu2 wrote:
> I highly recommend doing some background research.
>
> The main place to ask your questions or search about rooting and
> deploying alternative images are at xda-developers.com
>
> If you want to know which openSUSE (or other) image is appropriate for
> your tablet, it starts with the specific ARM model and version.
>
> The problems you’re having getting ADB to recognise your tablet are not
> unusual, I’ve found success is problematic, unreliable and can change
> quickly. For Device:Manufacturer code you should search based on your
> tablet name. If your tablet is off-brand, it’s even less likely you’ll
> be successful.
>
> HTH,
> TSU
>
>
Thanks to everyone for your input. I think that in lieu of all the other
work I am doing right now, I am going to have to put this project on the
back burner. I hate to do that,but I have to concentrate on more
important things for the time being.

When I have time to get back to it one day, I will. This forum has given
me the ideas I need for being able to get it going again in the right
direction when the time comes.


G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

Rooting android phone is not as difficult as you think. Firstly i am also afraid of rooting my android but then i found a very helpful article that make my work easy. You can also give this a try and it works with most of android devices. How to root android phone or tablet.

On Fri, 15 Nov 2013 09:36:01 GMT, johnlane1212
<johnlane1212@no-mx.forums.opensuse.org> wrote:

>
>Rooting android phone is not as difficult as you think. Firstly i am
>also afraid of rooting my android but then i found a very helpful
>article that make my work easy. You can also give this a try and it
>works with most of android devices. ‘How to root android phone or
>tablet’ (http://tinyurl.com/l8lqtsv).

And the fact that it is so easy and well documented does not make you at
least a little bit uneasy about android security?

?-)