How to Root

Status
Not open for further replies.
1 click root and manual root not working here.

1 click root fails because i have the DI01 update. manual root causes phone to go extremely slow and then fail completely
 
After rooting via one-click DI01 update is failing

1 click root and manual root not working here.

1 click root fails because i have the DI01 update. manual root causes phone to go extremely slow and then fail completely


Same here - after rooting D101 is not installing. Any fixes?

I just got this phone - should I return within the 30 days as I don't want to keep having this headache everytime an update comes through.:confused:
 
Thanks Dirrk!! This is my first Android phone, the Samsung Fascinate, and this was easier than manually doing it. I installed the WiFi Tethering and my son is able to get on-line on his iPod touch wherever we are.
 
Utterly painless.

Wireless tether working. LagFix brought it from 850 to 2206. Took more time to find the apps than to run 'em.

Much appreciated! Be sure to let us know when we get some ROMs for this baby. :)
 
stock d101 rooted

Just received my phone today, came preloaded with DI01 update.. 1 click method worked.. however, on first try was getting the Device not found error, even though at first the device was recongnized.

Restarted CPU and phone, reran 1 click root, made sure to unlock phone immediately when rebooted..

working flawlessly

Thanks to all who put the effort and time into this
 
Okay..
this is really werid and i really need help.
I using 1 click root and everything goes well.
but to the last part it say"
After it wasy Succesfully exploited. instaling permanet root file..

error: device not found.......
and phone frezze. then i have to take the battery out and put it back on...

i try clean cache/ and factory reset..

what did i do wrong???

please help me
 
unroot the fascinate?

From studying all the past posts it sounds like I have arrived late in the game now that the rooting method is essentially one click. Sounds like the batch file eliminates entering adb commands. I really am new too all this and I would like to try unrooting now that my Fascinate is rooted. Adb is completely foreign to me, so anything I say might sound like knowledge but is actually nothing more than mimicry. I open the cmd on my computer and began to enter the following:

adb shell
su (its going to ask you for permission on your phone so hit allow)
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
exit

However, my steps end as follows:

C:\Users\Owner>adb shell
$ su (i accept permission on my phone)
su
# rm /system/app/Superuser.apk
rm /system/app/Superuser.apk
rm failed for /system/app/Superuser.apk, Read-only file system
#

I then assumed to type exit after the last # even though it looked like the unroot failed, like so...

...
# exit

and it returns:
exit
$

I close the cmd and unplug my phone its still rooted and fine
I found some info on how to ADB and do i need to enter this,

adb shell
su
sysrw

in order to mount the sytem as read write, before i enter this
rm /system/app/Superuser.apk

Like i said i successfully rooted, but i would like to unroot just so i feel complete and then root again. Thanks to Dirrk for about a simple a method as possible.
 
what's up everyone this is a newbie here I need help badly.. I have a samsung fascinate and I did the 1 click root method my phone restarts but when it restarts there's nothing new its the same. I even try rebooting but this thing does not does the trick it tells me that basicallythe file does not exist when I try to upload from the sd card. I even installed titanium backup but that does not work so I know for sure I'm not rooted.... I did everything correct im pretty sure... any help would be greatly appreciated thank you everyone!!!
 
Has anyone tried unrooting using the method posted at the bottom of, how to root? It looks simple, however, i cant manage it because i get the read out of my device being a Read-only file system. I tried to make it read/write by doing this:

db shell
su
sysrw

Yet again i cant because:

sysrw: not found

If anyone can give me some tips i will be thankful. Also is returning to stock different from unrooting? All i want is to take my phone back to how it was right before i rooted it, just so i know that i can in the future.
 
Hey Guys this might be a dumb question and already answered but ive looked everywhere and can not find it. Ive got the root and lag fix going great thanks dirrk, but i really would like to try some of the kernels you have not sure what i need to do to install them. Thanks for your help!
 
Hey Guys this might be a dumb question and already answered but ive looked everywhere and can not find it. Ive got the root and lag fix going great thanks dirrk, but i really would like to try some of the kernels you have not sure what i need to do to install them. Thanks for your help!

Uninstall the lagfix you have and then read the threads in the main rom/hacks page about installing ClockworkMod Recovery. Once you have installed clockwork then boot into clockwork recovery and install one of my kernels.
 
1 click root and manual root not working here.

1 click root fails because i have the DI01 update. manual root causes phone to go extremely slow and then fail completely

1 click root is failing because you are clearly doing something wrong. The update has NOTHING to do with it. You should restart your phone before trying to do the root.
 
From studying all the past posts it sounds like I have arrived late in the game now that the rooting method is essentially one click. Sounds like the batch file eliminates entering adb commands. I really am new too all this and I would like to try unrooting now that my Fascinate is rooted. Adb is completely foreign to me, so anything I say might sound like knowledge but is actually nothing more than mimicry. I open the cmd on my computer and began to enter the following:

adb shell
su (its going to ask you for permission on your phone so hit allow)
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
exit

However, my steps end as follows:

C:\Users\Owner>adb shell
$ su (i accept permission on my phone)
su
# rm /system/app/Superuser.apk
rm /system/app/Superuser.apk
rm failed for /system/app/Superuser.apk, Read-only file system
#

I then assumed to type exit after the last # even though it looked like the unroot failed, like so...

...
# exit

and it returns:
exit
$

I close the cmd and unplug my phone its still rooted and fine
I found some info on how to ADB and do i need to enter this,

adb shell
su
sysrw

in order to mount the sytem as read write, before i enter this
rm /system/app/Superuser.apk

Like i said i successfully rooted, but i would like to unroot just so i feel complete and then root again. Thanks to Dirrk for about a simple a method as possible.

sysrw will not work because you googled something that was rom specific. ie that command is not a real command its a script someone added into thier rom. you need to type this

adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/bin/su
rm /system/bin/busybox
rm /system/app/Superuser.apk
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit

I have updated the OP, I am sorry for any confusion
 
Hey guys,

I am having a problem. I have debug enabled and i run start.bat. Everything goes fine. When the phone reboots, I have to log back into everything as if I did a master reset or just bought the phone. Any ideas?


******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I5000018ff18 device

*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone

* Then rerun this application

*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
2359 KB/s (1867568 bytes in 0.772s)
2137 KB/s (26264 bytes in 0.012s)
2231 KB/s (196521 bytes in 0.086s)
1316 KB/s (5392 bytes in 0.004s)
21 KB/s (281 bytes in 0.013s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 16:25:53.59

*
error: device not found
 
Thanks Dirrk that did the trick i think im unrooted. i followed these steps:

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

and there were no such directories found for these steps:
rm /system/bin/su
rm /system/bin/busybox

are these steps redundant or are they there just to be sure everything is removed?

Which brings me to my next problem my phone appears to be unrooted no superuser app or in adb su is not found, but i cant re-root when i run the batch file. I am getting the same error Breakthecycle2 has: no device found at that same step. Is this because i didn't unroot correctly? I am currently reinstalling the samsung drivers to see if that works. I could also find my device in cmd by entering adb devices when the rooting wasn't working.
 
Thanks Dirrk that did the trick i think im unrooted. i followed these steps:

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

and there were no such directories found for these steps:
rm /system/bin/su
rm /system/bin/busybox

are these steps redundant or are they there just to be sure everything is removed?

Which brings me to my next problem my phone appears to be unrooted no superuser app or in adb su is not found, but i cant re-root when i run the batch file. I am getting the same error Breakthecycle2 has: no device found at that same step. Is this because i didn't unroot correctly? I am currently reinstalling the samsung drivers to see if that works. I could also find my device in cmd by entering adb devices when the rooting wasn't working.

They are to make sure everything was removed. I didnt remember where I had put them for the 1 click root. I usually do it manually when I root other peoples phones because its quicker. And depending on what is on my mind I will either use /xbin or /bin for the install, they are both included in $PATH so if they are in both or just in one. They will need to be removed to unroot.

To answer your other questions, there are two solutions. I have not updated this in a while so I am sorry for that I just have been working on getting the kernels and everything set up for our phone. The easiest solution for you would be to manually do it since you obviously are not "horrible with following directions" like some. Manual method

Assuming your device still has su/Superuser.apk/busybox on the sdcard and rage.bin in /data/local/tmp if they are not then plz push them there.
adb shell
chmod 0755 /data/local/tmp/rage.bin
/data/local/tmp/rage.bin
Wait
try adb shell again ur looking for the # instead of the $ this time
if it still says $ wait a little longer and try again if not restart your phone just run the rage.bin again
once you have the # in shell then type these commands
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/su > /system/xbin/su ( u see i chose xbin lol idk why this time )
cat /sdcard/busybox > /systme/xbin/busybox
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
chmod 4755 /system/xbin/busybox
chmod 4755 /system/xbin/su
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit

Your other option is go into the .bat file and where u see PMSLEEP ## change it to: pause

Just make sure you give it ample time and if you want you can even have another cmd open and type adb shell to ensure the device is ready.
 
  • Like
Reactions: MunkinDrunky
I get how to go the 1 click root method. Should I wait until 2.2 comes out or risk doing it now? People run tons of different things, I assume they're all themes? How would I know which one would suit my needs? And can someone tell me what a kernel is?
 
Status
Not open for further replies.