Android TV Launcher Pushed to Google Play

Over the past decade, the tech universe has seen two drastic and widely contrasting changes with … more

Cyngn, OnePlus, Micromax – The Legal Battle

Recently, a battle has been waging in India over the rights to distribute the commercial … more

Lean Mean Battery Power Saving App Review

We talk a lot about battery topics here at XDA TV. We talk about everything from Power Banks to USB … more

Android 5.1 Possibly Coming February 2015

Google released Android 5.0 just over a month ago, and since then Lollipop has been trying to … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Closed

Rooted

OP Dirrk

9th September 2010, 11:31 PM   |  #1  
OP Member
Thanks Meter: 2
 
69 posts
Join Date:Joined: Sep 2007
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it 7-4-3-C@web.de

I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below


Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root%20file...alaxyS_x64.zip

32bit:
http://www.wikifilez.com/root%20file...Phones_x86.exe

1 Click Root Method
http://forum.androidcentral.com/fasc...-how-root.html

Manual Method

cd C:\android-sdk\tools

adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox

adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin

wait....
when it brings you back to your original shell in windows then follow these commands

adb shell (you should see # this time instead of $ this is exactly what we want)

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

cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox

exit

adb install C:\fascinate\Superuser.apk

This is permanent.

I just updated the files here with the latest su / superuser.apk / busybox

Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/show...38#post8086738
Attached Files
File Type: rar fascinate.rar - [Click for QR Code] (995.8 KB, 5203 views)
Last edited by Dirrk; 14th September 2010 at 04:36 PM. Reason: Making it a easier to follow
The Following User Says Thank You to Dirrk For This Useful Post: [ View ]
10th September 2010, 12:17 AM   |  #2  
Senior Member
Flag New Mexico
Thanks Meter: 53
 
418 posts
Join Date:Joined: Mar 2006
Quote:
Originally Posted by Dirrk

All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light

adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox

adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin

wait....
when it brings you back to your original shell or windows cmd promt

adb shell

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

cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox

exit

adb install Superuser.apk

Please let me know if I posted something wrong.

does it stick after reboot?
10th September 2010, 12:19 AM   |  #3  
Senior Member
Thanks Meter: 12
 
261 posts
Join Date:Joined: Jan 2010
Its supposed to be a temporary root so i doubt it will.
10th September 2010, 12:22 AM   |  #4  
Account currently disabled
Flag Michigan City, IN
Thanks Meter: 1,485
 
1,603 posts
Join Date:Joined: Jul 2010
Donate to Me
More
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.

Sent from my SPH-D700 using XDA App
10th September 2010, 12:34 AM   |  #5  
Senior Member
Flag Chicago, IL
Thanks Meter: 34
 
448 posts
Join Date:Joined: Sep 2010
see below.
Last edited by namebrandon; 10th September 2010 at 01:06 AM.
10th September 2010, 01:02 AM   |  #6  
Senior Member
Flag Chicago, IL
Thanks Meter: 34
 
448 posts
Join Date:Joined: Sep 2010
confirmed root.

Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.

You also have a typo near the end "scard" instead of "sdcard".
10th September 2010, 01:47 AM   |  #7  
OP Member
Thanks Meter: 2
 
69 posts
Join Date:Joined: Sep 2007
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.

And yes this is permanent
10th September 2010, 01:52 AM   |  #8  
Senior Member
Flag Chicago, IL
Thanks Meter: 34
 
448 posts
Join Date:Joined: Sep 2010
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.

Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
10th September 2010, 02:41 AM   |  #9  
cliffr39's Avatar
Member
Thanks Meter: 5
 
49 posts
Join Date:Joined: Mar 2006
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent

side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
10th September 2010, 03:00 AM   |  #10  
OP Member
Thanks Meter: 2
 
69 posts
Join Date:Joined: Sep 2007
Quote:
Originally Posted by cliffr39

I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent

side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.

It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones

Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes