yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] blacklevel:
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:

# 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:

# 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.
[Galaxy Tab  Android Development] leonreijnders:
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
[Galaxy Tab  Android Development] blacklevel:
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?
[Galaxy Tab  Android Development] Cliffro:
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
[Galaxy Tab  Android Development] Squishie:
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!
[Galaxy Tab  Android Development] jammysunny:
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
[Galaxy Tab  Android Development] mbaroukh:
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
[Galaxy Tab  Android Development] blacklevel:
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.
[Galaxy Tab  Android Development] gklyne:
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

]]
[Galaxy Tab  Android Development] blacklevel:
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:

$ 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?
[Galaxy Tab  Android Development] the incredible:
Which is the more simple method for root of galaxy tab euro ?are there ?
[Galaxy Tab  Android Development] blacklevel:
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.
[Galaxy Tab  Android Development] JanovPelorat:
This thread should be a sticky. Worked like a charm.
[Galaxy Tab  Android Development] the incredible:
z4root is very simple method..thanks.
[Galaxy Tab  Android Development] cowgaR:
thanks to Germany...

I agree, this thread should be sticky. Finaly some sense in android devel section...
[Galaxy Tab  Android Development] gummo6869:
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.

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!
[Galaxy Tab  Android Development] blacklevel:
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?
[Galaxy Tab  Android Development] debosset:
Hi,

I did the z4root on my galaxy tab (euro) and it works great.

I'm now waiting until a recovery app on my tab :)
[Galaxy Tab  Android Development] gummo6869:
There is no error message!

Here is how it looks like after the mount command:

>adb shell

# mount -o remount, rw -t rfs /dev/block/st19 /system

mount -o remount, rw -t rfs /dev/block/st19 /system

# exit

exit

And here is the log from using SuperOneClick:

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...

269 KB/s (5392 bytes in 0.019s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...

ROOTED

Getting mount path...

/dev/block/stl9

OK

Remounting system with read-write access...

OK

Pushing su...

failed to copy 'C:\Users\Server\Desktop\SuperOneClickv1.5.5-ShortFuse\su' to '/system/bin/su': No space left on device

OK

chmod su...

Unable to chmod /system/bin/su: No such file or directory

OK

Pushing Superuser.apk...

failed to copy 'C:\Users\Server\Desktop\SuperOneClickv1.5.5-ShortFuse\Superuser.apk' to '/system/app/Superuser.apk': No space left on device

OK

Remounting system with read-only access...

OK

Running a SU test...

Test failed!

FAILED

Hope this can help!

Appreciated for your help~ btw, I m using Windows 7 64bits, don't know if it matters

I am still concern about a "NAND unlock" is needed for my Tab since my Tab is not an euro version.

I am in Canada which my Tab is locked on Bell Canada.
[Galaxy Tab  Android Development] blacklevel:
You have a typo there. The correct syntax is

mount -o remount,rw -t rfs /dev/block/st19 /system

Notice the missing blank in "remount,rw". That could explain why the remount fails. But in case you made the typo just here in your post, there are a few things you could check as well.

Normally the mount command does not echo itself once you submitted it. It should look like this:

# mount -o remount,rw -t rfs /dev/block/st19 /system
#

Maybe your provider has modified or removed the mount functionality in some way. Let's check that.

On my tab the mount command appears to be implemented as part of the "toolbox" application:

# ls -l /system/bin/mount
lrwxr-xr-x root shell 2010-12-28 11:13 mount -> toolbox
# ls -l /system/bin/toolbox
-rwxr-xr-x root shell 81452 2010-12-28 11:13 toolbox
#

The above commands show that "mount" is just a symbolic link to the "toolbox" application. That seems to work similar to busybox which also implements a number of system commands which are normally separate commands under a single roof.

Try to find the mount command on your tab and post the findings here.

This section of the SOC output makes me think that your tab needs a specific remounting procedure and that the typo in your post is just that.

That does not matter.
[Galaxy Tab  Android Development] gummo6869:
Sorry, it was a typo in the post. I was just copying and pasting from your guide, so it was correct with all the commands.

My tab is actually the same as yours, just the date & time is different:

# ls -l /system/bin/mount
lrwxr-xr-x root shell 2010-11-04 12:18 mount -> toolbox
# ls -l /system/bin/toolbox
-rwxr-xr-x root shell 81452 2010-11-04 12:18 toolbox
#

Do you think my tab require a NAND unlock?

It is because I downloaded BusyBox from Market and when I tried to install it, it said my device is rooted but installation failed coz I need NAND unlock.

Looks like my tab can do a "temp root" without r/w access...

I tried z4root, SuperOneClick and manaully by following your guide, all have the same results.
[Galaxy Tab  Android Development] gummo6869:
Checked the instructions for the z4root method, it mentioned:

The above highlighted sentences, probably is the problem which I cannot complete the BusyBox and su installation.....

Please.... does anyone know how to do an NAND unlock for the Galaxy Tab?

Greatly appreciated~
[Galaxy Tab  Android Development] RNGuy:
There shouldn't be any special steps required to root a bell Tab. I've got one and I had no problems. Try manually rooting.
[Galaxy Tab  Android Development] fcarmona:
$ su

su

Permission denied

$ su

su

#

when you try the fisrt time and get "Permission denied" it is because in your tab must agree to give root permision.
[Galaxy Tab  Android Development] hamba:
Thanks blacklevel for this. Had to resort to this method when all others failed. :)
[Galaxy Tab  Android Development] JeffR714:
I tried your manual root guide and everything went smooth till the su I keep getting permission denied I followed the guide to the tee had temp root and then when I went in cmd window

adb shell

$su

Permission denied

and this continued can you please help me
[Galaxy Tab  Android Development] blacklevel:
Since manual rooting takes a few minutes, the problem could be that the Tab display timed out so that you may not have noticed the superuser.apk popping up and asking for permission.
[Galaxy Tab  Android Development] JeffR714:
Do you know how stupid I feel? I'm used to your regular devices when you hit adb shell everything's done in the command window I wasn't even looking at the tab..Thank you Oh and everything worked out perfect I owe you one!!

Jeff
[Galaxy Tab  Android Development] blacklevel:
Don't worry about it. I guess this happened to many folks when trying this for the first time, including myself. :)

Maybe I should put this gotcha into the howto.
[Galaxy Tab  Android Development] Temar:
Thanks, worked like a charm.

I just have one question: Why do you chmod busybox to 4755?

4755 sets the set-user-id bit and therefore busybox will always be executed as root. This looks like a huge security risk, because you do not get any notification from the su application when busybox is executed. Shouldn't the mask be 0755 or is there any special reason for setting the set-user-id bit on busybox?
[Galaxy Tab  Android Development] earthman5678:
/system folder is 100% full in recent firmware

I had the CF-Root KA kernal flashed on stock KA firmware but FUS is complaining about busybox. When I tried to reinstall busybox from market, I can't and it always complaining about nandlock or fail remount.

I digged deeper then I found the recent released firmware has 100% utilized space in /system folder. This cause any file copy to the folder impossible even if the remount with rw is done. The remount actually succeeded and it was the diskfull that prevent any file being copy into the system folder unless you first remove some files in it. I don't know if this is sammy in action trying to discourage rooting.

Cheers.

P/S: Click thanks if you find this discovery useful.
[Galaxy Tab  Android Development] Manicova:
i going to say......................................................................................................................................................................................................................................................don't work for me T_T

Update

XD

Thanks! there are 3 version of su in the S.O.C.root for me the second one work instead of the first. big thanks!
[Galaxy Tab  Android Development] RichAP:
Works for SGT

Just wanted to say thanks!

This worked for me on a Sprint Galaxy Tab running EA24 using su-v3.
[Galaxy Tab  Android Development] romy4321:
good day to all!!

i try to root my tab with gingerbread using this method but when am in

> adb shell

$ cd /data/local/tmp

$ chmod 777 rageagainstthecage

$ ./rageagainstthecage

the result

Failed to set prot mask <Inapropriate ioctl for device>

please advice and thanks in advance
[Galaxy Tab  Android Development] blacklevel:
It appears that the rageagainstthecage exploit fails on your Gingerbread rom. I can't say for sure because I have not yet tried to root Gingerbread myself.

However, you could try and use the "GingerBreak" exploit instead of the "rageagainstthecage" method. The required binaries are here:

http://xdaforums.com/attachment.php?attachmentid=591335&d=1304969547

You need to push and chmod 2 files from the ZIP and execute the "GingerBreak" binary instead of "rageagainstthecage". Otherwise the manual rooting process is the same:

> adb push misc_version /data/local/tmp
> adb push GingerBreak /data/local/tmp
$ chmod 777 /data/local/tmp/misc_version
$ chmod 777 /data/local/tmp/GingerBreak
$ /data/local/tmp/GingerBreak

If you try this it please post here if it worked.
[Galaxy Tab  Android Development] romy4321:
thanks for the reply

i try and the result (i type it manually from the console)

after $ /data/local/tmp/GingerBreak

[**] Gingerbread/Honeycomb--android 2.[2.3]' 3.0 softbreak

[**] <C> 2010-2011 The android Exploid Crew. All right reserved

[**]

[**]

[**]

[**] Exploit make take a while

[+] Plain Gingerbread mode!

[+] Found system :0xafd17f01 strcmp: 0xafd3759

[+] Found PT_DYNAMIC of size 232 <29 entries>

[+] Found GOT : 0x0001a450

[+] Using device/devices/platform/s3c-sdhc1.0/mmc_host_mmc0

[*] vold: 0068 GOT start : 0x00019450 GOT end : 0x0001a490

and i wait up to 15 mins, only - mark blinking on the console and nothing more
[Galaxy Tab  Android Development] blacklevel:
Thanks for posting this. Sorry it doesn't work.

It appears that the exploit is more device-sensitive than rageagainstthecage. The GingerBreak I linked above are supposed to work with Desire HD. They may have been modified to work on DHD devices. You could try the original binary from the original author. This can be found here:

http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html

Be careful, though, and make an external backup of any data important to you. The author writes that there is a chance that your sd-card might be formatted. This might happen because the exploit attacks vold (the volume manager).
[Galaxy Tab  Android Development] romy4321:
thanks for your help and advice

i will try these and thanks again
[Galaxy Tab  Android Development] blacklevel:
Did it work?
[Galaxy Tab  Android Development] eahiv:
Thanks

Worked great! With latest SuperOneClick archive I had to use psneuter instead of rageagainstthecage but otherwise spot on (USA VZN SGH-1800).
[Desire Q&A, Help & Troubleshooting] alinuxos:
I've tried to root it in many ways.

My only reason of rooting is installing Georgian glyphs,

as I would like to have georgian alphabet support.

It's a very big issue for us:

code.google.com/p/android/issues/detail?id=5925

code.google.com/p/android/issues/detail?id=8394&q=georgian&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars

#########################

unrevoked.com

with unrevoked 3.21 and even 3.22 version. no way.

it tells me: Internal error: couldn't find misc.

Afterwords I've tried r6-desire-root-alt, no success in this front too:

ladbook:r6-desire-root-alt alinux$ ./step1-mac.sh
Desire Root Step 1

Erasing cache and rebooting in RUU mode...

Password:
erasing 'cache'... OKAY
... OKAY

About to start flash...
< waiting for device >
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)

Rebooting to bootloader...

rebooting into bootloader... OKAY

Step 1 complete - now use the bootloader menu to enter recovery mode.

To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option.
ladbook:r6-desire-root-alt alinux$

My phone details:

BRAVO PVT1 SHIP S-ON

HBOOT-0.93.0001

MICROP-031d

TOUCH PANEL-SYNT0101

RADIO-5.09.05.30_2

with OTA updated Froyo 2.2

Any help is very appreciated! Thank you in advance!
[Desire Q&A, Help & Troubleshooting] EddyOS:
unrEVOked works with no issues on that HBOOT - sounds like you've not made sure the right drivers are installed
[Desire Q&A, Help & Troubleshooting] alinuxos:
First of all thank you for your reply.

Primary I've done it in MacOSX.

Afterwards I repeated it on Win 7, I was following this guide:

http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

for driver installation.

But, same result.

Is there way to make a TOTAL HARD reset, and maybe redo rooting with the latest unrevoked?
[Desire Q&A, Help & Troubleshooting] RaymondErasmus:
Download the Slax iso and the create a bootable cd, then download unrevoked 3.2.1(for linux) and save it onto the flash.

Boot from slax cd, copy files from flash to desktop, install and follow the onscreen instructions with unrevoked.

:D
[Desire Q&A, Help & Troubleshooting] EddyOS:
I had no issues in Windows 7 x64 Ultimate using unrEVOked so can't really comment, sorry
[Desire Q&A, Help & Troubleshooting] alinuxos:
Hello,

I've tried it with Linux too now...

I have a Ubuntu partition. With "sudo ./reflash" in the same way like win or mac gives me:

Internal error: couldn't find misc.

:mad::mad::mad::mad::mad:
[Desire Q&A, Help & Troubleshooting] gonjeshk:
i have the same problem. after i installed this rom RUU_Bravo_Froyo_HTC_ARA_2.32.415.3_Radio_32.49.00. 32U_5.11.05.27_release with bootloader 0.93.0001 i cannot root. any solution yet? thanks in advance
[Desire Q&A, Help & Troubleshooting] alinuxos:
People! I've done a downgrade from 0.93.0001 to HBOOT-0.83.0001

I've used this downgrade tool:

http://www.brutzelstube.de/wp-content/uploads/2010/09/downgrade23a.zip

My stuff at the moment:

2.1-update1 firmware.

32.41.00.32U_4.08.00.09 radio.

1.21.405.2 software version.

build number: 1.21.405.2

Should I root now?
[Desire Q&A, Help & Troubleshooting] gonjeshk:
i have tested this too but it did not work for me. what did u exactly do?
[Desire Q&A, Help & Troubleshooting] alinuxos:
boot in linux.

use terminal for:

unzip donwgrade23a.zip

move into:

desire_downgrade

and launch with sudo:

sudo ./donwgrade.sh

and wait ;)
[Desire Q&A, Help & Troubleshooting] gonjeshk:
i did exactly that but i get error messages:

./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Your phone is now ready to be downgraded - rebooting to bootloader.

Starting in 10 seconds (ctrl-c to quit)

./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

what can i do now?
[Desire Q&A, Help & Troubleshooting] falsinho:
Worked like a charm! Thanks. :)
[Desire Q&A, Help & Troubleshooting] EddyOS:
That is this thread:

http://xdaforums.com/showthread.php?t=768256

It also works in Windows
[Desire Q&A, Help & Troubleshooting] alinuxos:
It's ubuntu dependencies, you should have libstdc++ installed.

try sudo apt-get install libstdc

or if not,... try to find a right package with command apt-cache search libstdc
[Desire Q&A, Help & Troubleshooting] RaymondErasmus:
Go for it ... i see no reason why you shouldnt be able to root and then let us know how it went.

Its strange that some people running HBOOT 0.93 have issues rooting, were any of your phones branded? I read somewhere that vodafone or something with this hboot gives issues when trying to root
[Desire Q&A, Help & Troubleshooting] ste1164:
I have HBOOT 0.93.0001 and I could root fine.
[Desire Q&A, Help & Troubleshooting] gonjeshk:
now i get this error message with using ubuntu live cd:

no device found and in phone bootloader tells me the version would be older....

maybe it depends on the new rom i am havin now?
[Desire Q&A, Help & Troubleshooting] xavierjohn22:
I have 0.93.0001 and rooted fine with unrevoked3
[Desire Q&A, Help & Troubleshooting] prodygee:
That hboot 0.93000001, was released as an OTA. This also updated my Desire to that new hboot version. Maybe a try to prevent rooting?

My desire was rooted before but I unrooted it because it needs sending to htc. It's suffering from random reboots when it gets hot. It reboots, then vibrates 7 times. Google it, a lot of people have this problem.

I'm hoping I'll be able to root again when I get it back, because I just neeeeeed to run MIUI..

Ah the above comment comforts me :) I'll just try unrevoked again.
[Desire Q&A, Help & Troubleshooting] olvatito:
i tried Unrevoked and all downgrade tools , but always have problem some where , but main problem that after the phone reboot it's always can not find the phone and give me error , i recheck the adb many times and used Linux and windows 7 64 bit .

please help
[Desire Q&A, Help & Troubleshooting] temiatwork:
EddyOS, with your Desire's config, you manage to re-root it? I had mine upgraded a few days ago but the same error shows as the OP stated.

HTC Desire - ROM: 2.29.405.2 WWE| Radio: 32.49.00.32U_5.11.05.27 | HBOOT: 0.93
[Desire Q&A, Help & Troubleshooting] EddyOS:
I re-rooted last week and now running eMIUI - had no issues rooting as always
[Desire Q&A, Help & Troubleshooting] docnasef:
Sorry guyz

Obviously I am a newbie here and this q might seem very naive

My phone specs:

Android Version 2.2

Baseband Version 32.49.00.32U_5.11.05.27

Kernel Version 2.6.32.15-gd96f2c0

htc-kernel@and18-2 #1

Build Number 2.32.415.3 CL283905 release-keys

Software Number 2.32.415.3

Browser Version WebKit 3.1

BRAVO PVT3 SHIP S-ON

HBOOT 0.93.0001

MICROP -051d

Can this phone be rooted? using the unrevoked method?

I read that there are a few problems...

Could someone please walk me through the process..

Thanks all!!!
[Desire Q&A, Help & Troubleshooting] MasDroid:
It should work fine for you. It works fine on HBOOT 0.93.0001, the issue is if you have a PVT4 Desire, which you do not. Use unrEVOked 3.22 (in my sig below).