How to Root

Status
Not open for further replies.
ROOT Confused

I am new to this and computer ******ED I downloaded everything and did like it ask me too. I get to the extract all files part and thats as far as I can get if anyone can help I would greatly appeciate it.

Thanks
 
DI01 not working.

This one touch root is not working on my Fascinate. I've got the di01 update seams to be giving people trouble. Going to try the manual root ina few if I cant get this working. Ive tried with both sets of drivers, re downloaded the file a couple times, have my sd card mounted and got it on debug. Ive tried ona 32bit vista, 64bit win 7.
 
thanx dirrk and any others for this info.
i just rooted simply buy using the 1 click method.
only problem i had,was files not extracting.
when i clicked the uninstall,it extracted.
downloaded titanium backup,and barnicle wireless wifi.
all works great.know to find out how to remove bing.back to searching.

again thanx for the info.donation has been sent.
 
Device not found

When attempting to perform the One-click root I ran into an issue where the command prompt would identify the device and run through the process but there would be no 3 to 5 minute pause and I would get about 6 outputs of device not found.

I was using the .zip on the first page of this thread.

I tried it on three different computers running win 7, vista, and XP. They all had the same result.

I then noticed that Dirrk has a link to the .zip file in his signature block but with a slightly different name. I downloaded and ran that one and it worked perfectly.

I noticed that others described similar issues to what I had so I am guessing that there is an issue with the version on the front page.
 
a little help :)

This is my first rooting as well, I believe that I have rooted succesfuly however trying to rename my bloatware is not working.

I have tried 2 separate apps: "android mate" and normal "explorer". with explorer I am able to rename the apps but it doesn't stick (I'll rename [delete/move tried all] the app but as soon as i refresh the list or leave the directory and come back the app refreshes itself.).

Any suggestions would be greatly appreciated.
 
Coming up with a error: Cant find device, but drivers were installed correctly and it restarts my phone like it should but no root. Anyone have any advice?
 

Credits:

  • Sebastian Krahmer at C skills for developing the code necessary to exploit the root. Please see fit to donate via Paypal to 7-4-3-C@web.de.
  • The rootzwiki community for hosting the Samsung drivers
  • Android Central Member Dirrk for rooting this phone using Sebastians global android exploit and for making an autoroot version.


1. Download and Install Samsung Drivers

64bit:
http://www.wikifilez.com/root%20files/epic4g/usb_drivers_GalaxyS_x64.zip
or
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe

2. Go to Settings > Applications > Developement > Enable Debugging then plug in your phone

CAP201009102354.jpg

CAP201009102356.jpg


3. Download the attached files
FascinateRoot_v2.zip
Extract the all of the files (click on show files when done)
Run START_ROOT from the extracted folder do not touch your phone from here on out.


If you have any troubles running this 1 click root method then please follow these guidelines.
1. Check to make sure you installed the Samsung Drivers
2. Make sure your phone is connected using the original cable that came with the phone
3. Verify that debugging is enabled.
4. Try to run it again
5. If you are receiving errors then your phones drivers were not installed
6. If you are having a different please post here so we can help you.

Finally if you need more immediate help then check on irc.freenode.net #samsung-fascinate

How To Remove Root

adb shell
su (its going to ask you for permission on your phone so hit allow)
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
rm /system/bin/su
rm /system/bin/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit

Latest Update
09/25/2010 @6:20 EST Updated Files and FYI this still works with the latest update so make it easy and update first
Confirmed Wireless Tethering Wireless Tether 2.05-pre9

Rooted my first time ever, on my first Android phone ever, last night at home on my Win7 64b box and it worked like a champ as advertised above. Tried it earlier at work on XP SP3 but problems with pushing files/drivers. Didn't troubleshoot it too hard cuz I figured I would have better luck at home.

Dam but don't it feel GOOD to be a GANGSTER! Thanks Dirrrrrrk!!!:D
 


How To Remove Root

adb shell
su (its going to ask you for permission on your phone so hit allow)
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
rm /system/bin/su
rm /system/bin/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit

Hi. I've followed this thread to root my phone about two months back. I recently unrooted my phone following the steps above because I had a Verizon update that kept giving me a "can't mount /dev/block/mccblk0p1" error. (I prob should have asked about that before unrooting my phone)

Now I'm trying to root my phone again and after it says "Successfully exploited, installing permanent root files and deleting temp files", it gives me six "error: device not found" lines, followed by "Restarting your phone now." and another "error: device not found." My phone freezes after that.

Any ideas about why this is happening? Any help would be much appreciated. Thanks.
 
Now I'm trying to root my phone again and after it says "Successfully exploited, installing permanent root files and deleting temp files", it gives me six "error: device not found" lines, followed by "Restarting your phone now." and another "error: device not found." My phone freezes after that.

Any ideas about why this is happening? Any help would be much appreciated. Thanks.

I've had something similar happen a few times too. For some reason, after the initial reboot, Windows wouldn't see the phone - it wouldn't show up in the device manager and the root script couldn't finish the last few steps.

All you need to do is manually execute the last few commands that the script couldn't. So, reboot your phone normally, connect it to your computer, open a Command prompt (start>run>cmd). Navigate to wherever you unzipped the root files and type the following, one at a time:

adb shell sh /data/local/tmp/com.sh

adb shell rm /data/local/tmp/su

adb shell rm /data/local/tmp/Superuser.apk

adb shell rm /data/local/tmp/busybox

adb shell rm /data/local/tmp/rage.bin

adb shell rm /data/local/tmp/com.sh

The first one runs a shell script to set file permissions, the others just remove the root files from the temporary spot they were being stored.

Then just reboot your phone. Try that and let me know if it works.
 
Hi, have just installed what I thought was root, which comes up with some cleanup error messages at the end of the script (essentially permission denied), so I'm not sure it has fully worked.

I'm having issues copying files into /system/lib (via adb push), saying permission denied and when I run adb shell, I am unable to chmod any of the files - again permission denied.

I see there are some additional switches on the adb CLI to start in root mode (adb root) tried this errors with:

"adbd cannot run as root in production builds"

Please point me in the right direct as to what needs to be done to enable full root access.

I'm running on the Windows XP SP3, USB connected in debug etc with the 32 bit mode drivers.

DJ
 
Please point me in the right direct as to what needs to be done to enable full root access.

Sounds like you're not getting superuser permission through adb. Adb shell into your phone and type su at the prompt. You should get a message on the phone asking to authorize superuser permissions, click allow and make sure the "remember" checkbox is checked. Now you should be able to copy whatever you need to copy.
 
Then just reboot your phone. Try that and let me know if it works.

Thanks Chris3D! My phone is rooted once again.

I originally unrooted my phone to try to get my Verizon update working. The package is "SCH-I500_DH12_to_DI01." I can't find any information about that package and it downloaded overnight. I'm not entirely sure what the update is but when I try to install it, it reboots and says "can't mount /dev/block/mccblk0p1." Would you have any ideas as to what is causing this? Thanks again.
 
Thanks Chris3D! My phone is rooted once again.

I originally unrooted my phone to try to get my Verizon update working. The package is "SCH-I500_DH12_to_DI01." I can't find any information about that package and it downloaded overnight. When I try to install it, it reboots and says "can't mount /dev/block/mccblk0p1." Would you have any ideas as to what is causing this? Thanks again.

It sounds like your getting the same thing i had when i went into recovery mode. It didn't really effect my phone in any way, so i didn't think to much on it. But the DI01 sounds like something from JT's Super Clean Rom. As long as your phone isn't FC'ing alot or has any other really big problems, i wouldn't trip on it that much. :)

After installing the StupidFast Kernel (stable) ver. and Dark Gloss Mod theme, i haven't seen that "E: Can't Mount dev/block/mmcblk0p1 (invaild argument)" anymore. I don't know if that was what the problem was or not.

But as far as updates from Verizon, i know it's not Froyo so there's no point that i see to unroot yet. And if I've heard correctly you wont have to unroot your phone to get a version of Froyo anyway. Some developer will more than likely make a flashable version that's debloated/debinged already.
 
Thanks Chris3D! My phone is rooted once again.

I originally unrooted my phone to try to get my Verizon update working. The package is "SCH-I500_DH12_to_DI01." I can't find any information about that package and it downloaded overnight. I'm not entirely sure what the update is but when I try to install it, it reboots and says "can't mount /dev/block/mccblk0p1." Would you have any ideas as to what is causing this? Thanks again.

Could that be the 2.1 update 1 from Verizon, I think dated September 22nd? Did you ever install that through the phone? If so, it won't install if you've installed the Clockwork Recovery, so maybe that's your issue. If it is, there's an unsigned version that will install through Clockwork. If you need it, I'll post it.
 
Could that be the 2.1 update 1 from Verizon, I think dated September 22nd? Did you ever install that through the phone? If so, it won't install if you've installed the Clockwork Recovery, so maybe that's your issue. If it is, there's an unsigned version that will install through Clockwork. If you need it, I'll post it.

I am currently running 2.1 update 1. I think the update is the one mentioned in this thread http://forum.androidcentral.com/verizon-fascinate/44602-update-coming-but-not-2-2-a.html.

Anyhow, I think I will skip this update and wait for Froyo to come out for the phone.

Thanks Chris3D and Fappy Jones!
 
Sounds like you're not getting superuser permission through adb. Adb shell into your phone and type su at the prompt. You should get a message on the phone asking to authorize superuser permissions, click allow and make sure the "remember" checkbox is checked. Now you should be able to copy whatever you need to copy.

Hi, I took a closer look at the installation and the root installation has failed, (see below) the cleanup operation fails after running 'rage.bin'.

Recommendations?

*
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
mount: Operation not permitted
/data/local/tmp/com.sh: cannot create /system/xbin/su: permission denied
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: permission denied
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: permission deni
ed
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
 
Status
Not open for further replies.