Advanced Rooting Question/Discussion "rage.bin"

[Stupendous Man]

First, please don't comment on this post unless you are a developer, highly knowledgeable, or have information regarding the issues i've described.

I'm requesting information about the "rage.bin" that is part of the rooting process used on the Fascinate. I've successfully rooted my fascinate manually, using the files supplied here but the only part of the process that is a mystery is the rage.bin.

I understand that it is a program that Exploits some part of the OS that gains you root access.

I have a few important questions:

1. What does rage.bin actually exploit (Specifically)

2. Does Rage.bin make changes to any files on the phone?
a. if so what files?


ADVISEMENT NOTE:
I was under the impression that the exploit only gains you root access temporarily, then while temporarily root you add su, busybox and the superuser.apk and voila. If this is NOT the case then the "Un rooting" instructions (which is stated as just deleting those 3 files) would NOT unroot a phone.
Can someone clear this up?

Main Issue at the Moment:
My main goal is to solve/debug a minor problem i'm having with my fascinate. Since the root the only thing that doesn't seem to play nice is the "TwLauncher" app (The default Launcher). It seems to take longer to load (when it doesn't force close on me) Not that I like it that much, I'm a launcher pro user, but solving any instability issues in the rooting process will make for less paperweights.


Phone/File version information:
Phone Firmware ver: 2.1-update1
Phone Baseband ver: s:i500.04 V.DH12
Phone Kernel ver: 2.6.29
Phone Build num: SCH-I500.DH12

Superuser/Root File Versions:
Superuser.apk ver: 2.3.6.1 (Database v5)
Su binary ver: 2.3.1-ef
BusyBox ver: Unknown at this time? Downloaded from This forum Fascinate_v02.zip

 

[namebrandon]

It has to do with fork-bombing the adb daemon, causing adbd's setuid to fail. The author's name is Sebastian Krahmer if you want to look for his site. He did publish the source for an older version of rage.bin, if you're really interested.

It makes zero changes to the phone. I highly doubt your TwLaunder FC's are due to rage.bin, since no one else appears to see them. I would try mounting /dbdata and wiping it, then rebooting, that will probably resolve your issue.

Also of interest, you do not need rage.bin to root your phone. You could simply flash CWM recovery, and when you access the shell you'll always get superuser access due to a modified adb daemon. Similarly with the Voodoo kernel, you'll get superuser shell access at boot, since privilege elevation in this instance is compiled into the kernel.

 

[Stupendous Man]

Hey thanks for the input, I'll check out his site.

I'll take a look at the /dbdata section.

no one probably sees this issue because honestly the default twlauncher on the fascinate sucks and no one uses it LOL. But I kinda liked a few of the Samsung widgets that came on the phone so I had twlauncher on my home screen in case I wanted to use it.

Since the only 2 things i've done to the phone to cause the problem is
1. run rage.bin
2. copy three files (su, busybox, and superuser.apk)

If Rage truly only bombs the adb's daemon running on the phone then i've narrowed it down to one of the three files i've added.


If I find out more I'll post

 

[Stupendous Man]

I un-rooted my phone and the problem with TwLauncher still existed. After determining that the rooting procedure makes no modifications to the phone I found that the only change since I installed Launcher pro was a Hard reset of the phone.

If you have Launcher Pro set as the "Default Action" when the home button is pressed, after a hard reset you may incur instability when trying to launch the TwLauncher via a shortcut. (as I did)

Solution:
1. Settings->Applications->Manage Apps->Launcher Pro
2. Select Clear Defaults
3. Hit home button
4. Select TwLauncher from Prompt
5. Hit home button
6. Check Box Use this as default
7. Select Launcher Pro.

Done.

 

[happynorain]

It has to do with fork-bombing the adb daemon, causing adbd's setuid to fail. The author's name is Sebastian Krahmer if you want to look for his site. He did publish the source for an older version of rage.bin, if you're really interested.

It makes zero changes to the phone. I highly doubt your TwLaunder FC's are due to rage.bin, since no one else appears to see them. I would try mounting /dbdata and wiping it, then rebooting, that will probably resolve your issue.

Also of interest, you do not need rage.bin to root your phone. You could simply flash CWM recovery, and when you access the shell you'll always get superuser access due to a modified adb daemon. Similarly with the Voodoo kernel, you'll get superuser shell access at boot, since privilege elevation in this instance is compiled into the kernel.

Where is the source of rage.bin?