This howto is for those people who are unable to root their Galaxy Tab using any of the automated procedures and do not suffer from CLPS (command-line-phobia-syndrome).
My story: After upgrading my EURO (GSM) Galaxy Tab to JM6 my persistent efforts to root the device using either the z4root or SuperOnClick methods have all been unsuccessful. z4root (v1.3.0) kept crashing at different stages, apparently depending on which and how many background apps were running. With SuperOneClick I never managed to get beyond the "changing permissions" stage.
Since both methods are basically wrappers of the rageagainstthecage application, I tried to perform the rooting procedure manually. Guess what, that worked without any problem and it is pretty easy to do.
The basic steps of the rooting process are:
1) use rageagainstthecage to get a temporary root shell
2) use the temporary root shell to copy three files to the read-only system partition the device
While I find the outlined procedure straightforward, you may not. Anyhow, try this at your own risk.
==== Prerequisites ====
I used Ubuntu 10.10 for this, but it should work on any other distro and on Windows just as well. Whatever OS you use, you need a working adb connection to your Galaxy Tab. Odin or Kies are of no use here.
You need the following binaries
* su
* busybox
* Superuser.apk
* rageagainstthecage
To get the all required files, simply download "SuperOneClickv1.5.5-ShortFuse.zip". That's what I used.
Get it here: http://forum.xda-developers.com/showthread.php?t=803682
Extract the contents of the ZIP, open a command-prompt on your computer and change to the directory where the extracted files are located.
Some advice if shell commands are not your regular cup of tea.
The following instructions show the shell commands. Some are executed on the host computer. Others are executed on the Galaxy Tab. You can differentiate between the two easily: All commands which start with "> " need to be executed in a shell on the host computer. Commands which are prefixed with "$ " are executed on the Galaxy Tab. In both case the ">" and the "$" must not be typed. If you copy+paste from this howto, make sure only to copy the commands and leave out the prompt.
==== Step 1: getting a temporary root shell ====
Copy the rageagainstthecage exploit to a temporary directory.
Code:
> adb push rageagainstthecage /data/local/tmp
263 KB/s (5392 bytes in 0.020s)
Change the file permissions and execute the exploit.
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 rageagainstthecage
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
(other output truncated)
Your shell session will be terminated which will throw you back to the regular command prompt of your host computer.
==== Step 2: restart adb server ====
Now stop and restart the adb server process.
Code:
> adb kill-server
> adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now reconnect to the Galaxy Tab again. Notice the '#' prompt. This means you have a temporary root shell now. We use this to execute some privileged commands which make the rooting permanent.
==== Step 3: making it permanent ====
First, make the system partition writeable. We need this to be able to copy su, busybox and Superuser.apk to the required locations. Then exit the android shell again.
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
The final steps are to change the file permissions for su and busybox and then remount the system partition as read-only again.
Code:
> adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
# exit
That should be all. Try a reboot and some apps which require root, like Titanium Backup. The Superuser.apk should popup a dialog requesting permission.
Hope this helps. Happy rooting.
[update]
This process worked for JMA and JMD as well.
"adb install" Superuser.apk instead of "adb push"
[/update]
It will help me !
Merci ;-)
Fantastic! This is just what I was looking for, thank you! I feel dumb now, because I started a thread of my own right as you posted this. You must just type faster than me
I ran a quick test, and it all looks good. One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Anyway, thanks again, this did exactly what I needed it to. Well done, I appreciate it.
DavidThompson256 said:
One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Click to expand...
Click to collapse
Thanks for pointing that out! Actually both the filesystem type and blockdevice name were totally wrong. Apparently the mount command ignores both parameters - at least when they are wrong.
I just verified this as self-punishment for not paying attention:
Code:
# mount
(...)
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
/system is mounted read-only to /dev/block/stl9. This is the normal state of things.
Now I remount this without the fstype parameter and using a wrong blockdevice name:
Code:
# mount -o remount,rw /dev/block/xyz /system
# mount
(...)
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
Surprise, this actually remounts /system in read-write mode. This is why my original howto worked despite using the wrong parameters.
Thanks again. I corrected the HOWTO.
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
leonreijnders said:
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
Click to expand...
Click to collapse
That is strange. The result of the rooting process is just adding three files to the system partition. I find it hard to believe that this could lead to the problem you describe. However, while experimenting with z4root I had the the effect that there were many rageagainstthecage processes running in the background and the Galaxy Tab slowed down considerably. Perhaps there is something similar going on.
Have you tried rebooting after completing the rooting process?
Try shutting down the Tab completely.After rebooting get a shell on the Tab with "adb shell" and execute "ps". That shows the process list. If that looks normal, I would try a factory reset of the device. Which ROM version are you running?
BlackLevel: Thank you soooooooooo much... I don't get how to hit the Thanks Meter thing, but here is the old fashioned way. I used a MacBook to accomplish your perfect, step by step rooting of an AT&T Galaxy Tab i987. It helps that I'm more comfortable at the command line than with most GUI systems.
I could put this into a bash script, but that could be dangerous. People really need to look at whats happening with 'adb' and have some idea of what adb is for. I did renamed your 'adbmac' to 'adb', then I could cut and paste from your instructions except for adding ./ before the adb... ie. ./adb shell
Again, wonderful work at pulling this all together in one place.
Jeff
This guide worked perfectly! I love a nice quiet clean root and it doesn't get any better than this. You my friend deserve a cookie!
Hi Guys,
I flashed to JMA, rooted it with One Click Root, and everxthing seemdet to be okay, but activating OCLF failed....is there anybody with the same problem?
Jan
Thanks a lot !. It's clean and doesn't need a kies ...
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
And thanks again ...
Mike
mbaroukh said:
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
Click to expand...
Click to collapse
The reason is that "/sbin/adbd" (the adb daemon) is running as the shell user. It would need to run as root user instead. This requires changes to the initial ram disk where adbd the relevant settings are stored.
Dealing with "insufficient permissions for device"
Thanks, this worked for me.
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
gklyne said:
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
Click to expand...
Click to collapse
Thanks for the feedback. On my Ubuntu 10.10 adb runs under my regular user-id (1000) and I do not have to use sudo or run the local adb server as root. That might be due to the way the udev rules are set up. Mine are rather unrestrictive and look like this:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
How do yours look like?
Which is the more simple method for root of galaxy tab euro ?are there ?
the incredible said:
Which is the more simple method for root of galaxy tab euro ?are there ?
Click to expand...
Click to collapse
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.
This thread should be a sticky. Worked like a charm.
z4root is very simple method..thanks.
thanks to Germany...
I agree, this thread should be sticky. Finaly some sense in android devel section...
Thank you very much for your guide!
I followed all the instructions in your guide, everything seems fine until I try to push the busybox and su to my Galaxy Tab.
blacklevel said:
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
[/update]
Click to expand...
Click to collapse
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too
(No space left on device) is impossible, my tab is brand new sealed when i got it.
I have been trying the z4root and SuperOneClick procedure to root this tab but are all unsuccessful.
I am not sure if it is because of my tab needed a "NAND unlock" (I cannot find any guide about the NAND unlock) because I received this message when I tried to install busybox from the market.
Please help! My tab is carrier locked to Bell Canada, I really wanna to unlock it and root it~
Thanks!
gummo6869 said:
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too,
Click to expand...
Click to collapse
The `no space left on device` message indicates that the /system partition is still read-only. That means the mount command in step 3 was unsuccessful. Did you get any error message when you executed it?
After permroot with VISIONary r14 I am getting an I/O Error on /etc/hosts and /system/etc/hosts. This is sad as my purpose in permrooting is to have a custom hosts file.
This is the sequence of events as I recall it:
1) Performed a temproot using VISIONary r14
2) ADB pushed my hosts file to /data/data/hosts
3) Set up my hosts file as the one to be consulted (as root)
Code:
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -o remount,ro /dev/block/mmcblk0p25 /system
4) Installed AdFree (granted rights, hosts file downloaded to /data/data/hosts; did not check symlink creation)
5) Removed AdFree and pushed my own hosts file again (as I need some entries for local network)
6) Performed a permroot
At this point I noticed some ads had appeared on a web page I normally have ad-free. So I thought that to be odd. I also did find /etc/hosts again. Not to worry, I will just do step 3 above again now that permroot is done (successfully). At least, that's what I thought. Remounting the filesystem is not a problem. The filesystem is indeed mounted as writable when I check cat /proc/mounts. But then I get the error:
Code:
# rm /etc/hosts
rm /etc/hosts
[B]rm failed for /etc/hosts, I/O error[/B]
This is the same for /system/etc/hosts.
The result is that my custom hosts file is not used
All commands are run through ADB shell, not a terminal emulator on the phone.
Please let me know if you have any suggestions.
e2fsck_recvy is not an option on a device mounted as /system. I suppose I could run it from some recovery mode...no knowledge about that.
HTC Desire HD
Android 2.2
Software version 1.32.405.6
PS: this thread is not to discuss the philosophical position one may have on blocking advertising and the like.
you cant do this with temp root..... without s-off the nand protection will stop you writing to /system even when logged in as su
This error occurs with permroot, not temproot.
But if I understand you correcty my only option is to go for a custom ROM. This may be a little too much hassle just to turn off the ads.
Update: performed S-OFF as described here: [TOOL][VIDEO] One click Radio S-OFF, SimUnlock (Easy Root & S-OFF Guide). Unfortunately still get /system/etc/hosts: I/O error.
Vic_E said:
4) Installed AdFree (granted rights, hosts file downloaded to /data/data/hosts; did not check symlink creation)
Click to expand...
Click to collapse
I've been thinking about making this more explicit, the symlink box isn't just to create a symlink, it's also to use the symlink, regardless if you made a symlink manually or not.
I'd suggest ticking this, at least then adfree should work, although it's weird that you can't even cat the /system/etc/hosts file.
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 2.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2014-06-29 14:30 su -> /system/xbin/su
Analysis: File: su is a symbolic link pointing to another file: /system/xbin/su
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 348160 2014-06-29 14:30 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
Wrong forum, US variants have their own fora. Your thread belongs here, I've asked mods to move it. Sit tight until they do.
Karetus said:
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Click to expand...
Click to collapse
You need to download the su zip and flash it in recovery.
Lokke9191 said:
You need to download the su zip and flash it in recovery.
Click to expand...
Click to collapse
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
KJ said:
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
Click to expand...
Click to collapse
Would you happen to have a link available? Or will any version do the trick?
Karetus said:
Would you happen to have a link available? Or will any version do the trick?
Click to expand...
Click to collapse
You should not use any version. Use the one I attached.
So I rooted my phone used it for a bit then for some reason it messed up so I bought root checker pro and it said Root access not properly configured or granted.
Superuser Application Status
NOT installed: Superuser by ChainsDD, SuperSU by Chainfire, or Superuser by Koush
System Files Status
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-01-23 18:48 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User and Group ID Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
ADB Shell User Status
ADB setting for shell access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
Results provided for your SGH-I747M - Android 4.3 device by Root Checker Pro version 1.4.2 from joeykrim in the Android Market - my device is an android Galaxy s3 version is 4.3 and I'm not running a Rom and I used towel root please help I can't find the solution anywhere
Hi there,
Please wait until mods will move this thread to the device specific forum.
Stand by
The simplest way to get root in my opinion is to flash Philz Touch recovery for the d2lte using Odin. Then flash super su from recovery, boot phone, let supersu and disble knox, reboot phone, done.
I have an Alcatel ideal 4060a and it's does the exact same thing an says the same when I do my root checker. What do I do to get my root back?
If you have an older kernel, made on or before May 2014, then you can use towel root to gain root.
Hello been awhile, I have a Aspen a785. Rooted. Used China site few years back. Installed kingroot. Tab was new then. Only place to unlock it at the time.
I run Linux machines. No windows at all available. . I've tried to get su working have pro key. Problem is kingroot has controls of root. Disabled I can't get su working properly, fx has no root access. Super won't install. King active , su installs but doesn't control root, it Thinks it does, it can blok access but only if king is active . king is in #/system/app
Is there a source file I can manually install or modify to change permissions?
I did find a file permissions.text or something that showed eu.chainfire??? As none
And com.kingroot.??? As ,3003,1028,####,####,###.
Is there a web source for info on these files?
Is there a Linux method software available for su install and rooting?
update! need help
Iv dug a bit more
No file install-recovery-2.sh
File install-recovery.sh shows
#!/system/xbin/sh
/system/xbin/Ku.sud -d &
/system/etc/install-recovery-2.sh
Mount -0 remount -rw /system
/system/bin/toolbox chcon ubject_r:system_file:s0 /system/app/kinguser.apk
chcon ubject_r:system_file:s0 /system/app/kinguser.apk
/system/bin/toolbox chcon ubject_r:system_file:s0 /system/xbin/su
chcon ubject_r:system_file:s0 /system/xbin/su
/system/etc/kds --global-daemon 1
#end
Would changing /kinguser.apk too ( EU.chain fire.supersu-2.apk) solve issue with root control at boot up? Then delete all references to king?
Unable to edit install-recovery.sh seams r protected