Unroot Captivate and Vibrant

[djunio]

Since there are no cutom ROM's or recoveries, all you have to do is remove the files that enables root.

adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
One ROM and recoveries come out, I will update this with OEM firmware.

http://forum.xda-developers.com/show...68&postcount=4

Or open terminal emulator and type:

su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

[xgoochx]

I apologize a head of time for my ignorance. But how do you do this? I have rooted my Captivate but want to unroot it. Any way someone can post a nOOb version explaining this? Do i need to click start then run then cmd? Thanks in advance.

[ggrant3876]

The first example you need to use adb, in the lower example you just type the commands into your terminal. You should be able to get a terminal emulator free in the android market. If you are rooted when you type the first su hit enter and you should het #.

Or open terminal emulator and type:

su (enter)
rm -r /system/app/Superuser.apk (enter)
rm -r /system/xbin/busybox (enter)
rm -r /system/bin/su (enter)

[extorian]

Given that the system firmware isn't actually changed when rooting, I wonder if OTA updates will still work as normal without the need to unroot.

[djunio]

It should.......

[extorian]

I noticed in the update script it has this:

symlink("../xbin/su", "/system/bin/su");

Doesn't that mean there's a dead symlink called /system/bin/su that needs removing too?

[djunio]

Um not sure if u can remove it. I think that's the stock su that all Androids ship with.

I c what your saying now, that's part of the new system. If its removed u won't have root.

[extorian]

Yeah but that's what I mean... if you're unrooting, don't you need to delete that shortcut too.

Edit: shortcut = symlink.... speaking in Windoze now

[djunio]

I'll check the stock rom later, there's an su file that ships with Android that has to stay. I think that one stays.

[extorian]

As best as I can tell, that file is created as a symlink as part of the update.zip package when rooting. So it's either already overwritten the stock one, or it's left over... at least that's what seems to be the case.