How to Root

Status
Not open for further replies.
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?

Make sure USB debugging is turned on and run adb to see what's going on:

In a command prompt, navigate to the folder holding all the root files and type: "adb shell" (no quotes).

Next, type "su" to see if su is installed. Check your phone to see if a message pops up asking for you to allow superuser.

If that doesn't work, type "cd data/local/tmp" That'll put you in the directory were the root script initially copied files to.

Now, type "ls" to get a file listing. Do you see files like com.sh, su, busybox and Superuser.apk?

Let me know the results of that...
 
Hello. I am a noob to the fascinate root but I rooted my Droid1 and loved it. I am now attempting to root my fascinate and here is the issue I'm having:

I D/L'd the 64 bit driver for Samsung and then tried to d/l the FascinateRoov_v2.zip file and it won't d/l. It just sends me to a new page. I am assuming that the file is gone. If someone has already posted the new d/l in one of the 59 pages of replies, I am sorry. I am simply too tired to go through all of them tonight. Thank you and have a good night.

EDIT: NVM. I just d/l'd to my phone and transferred it over. It's weird that the PC wouldn't d/l the file and my phone would. 1pt for fascinate!
 
Last edited:
Hello. I am a noob to the fascinate root but I rooted my Droid1 and loved it. I am now attempting to root my fascinate and here is the issue I'm having:

I D/L'd the 64 bit driver for Samsung and then tried to d/l the FascinateRoov_v2.zip file and it won't d/l. It just sends me to a new page. I am assuming that the file is gone. If someone has already posted the new d/l in one of the 59 pages of replies, I am sorry. I am simply too tired to go through all of them tonight. Thank you and have a good night.

I just clicked on the link in Dirrk's first post and it re-downloaded the .zip for me. So try again.;) And check your downloads it might be there.
 
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
===================

Hi,

I tried the Z4root approach (see this link Z4Root Is One Click Root App For Samsung Galaxy S / Android Phones) along with adb shell and this has worked for me!

Many thanks for the assistance.


DJ
 
does not work

I dont know then, both links in Dirrk's post worked for me on my win7 64 bit laptop. I now have 3 .zips in my downloads. So maybe you guys aren't putting it in the right spot. But it's stilling working for me.

Sent from my Super-Clean Fascinate
 
help please

******************************************************************************
* *
* 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
I500a26405f6 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
654 KB/s (1867568 bytes in 2.786s)
88 KB/s (26264 bytes in 0.290s)
918 KB/s (196521 bytes in 0.208s)
20 KB/s (5392 bytes in 0.250s)
4 KB/s (281 bytes in 0.055s)
* 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: 19:20:26.98

*
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
*
* Restarting your phone now.
*
error: device not found
* Complete
*
******************************************************************************
Press any key to continue . . .
 
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.

Ok.. so i used this. now i have superuser on my phone.. however when i open it it shows no apps.. also i dont see busy box in my app list. is this how it should be? I am new to this. where do i go from here if i want to install voodoo?
 
Yes this is normal, if you haven't installed any apps that use root, you won't see anything in the superuser list. And as far as Voodoo I would just wait until the newer Voodoo gets released after the new update. The newer ver. is supposed to be less buggy.

Sent from my Super-Clean Fascinate
 
Hello. I am a noob to the fascinate root but I rooted my Droid1 and loved it. I am now attempting to root my fascinate and here is the issue I'm having:

I D/L'd the 64 bit driver for Samsung and then tried to d/l the FascinateRoov_v2.zip file and it won't d/l. It just sends me to a new page. I am assuming that the file is gone. If someone has already posted the new d/l in one of the 59 pages of replies, I am sorry. I am simply too tired to go through all of them tonight. Thank you and have a good night.

EDIT: NVM. I just d/l'd to my phone and transferred it over. It's weird that the PC wouldn't d/l the file and my phone would. 1pt for fascinate!
didn't work for me with firefox running adblock. Works with IE8.
 
I know its off topic but did Dirrk really go to iPhone? Or is that just all hearsay...

ROFL

I have just been hogged down with work and school that I have had 0 time to work on coding. Plus any time i have had in the last week I have spent playing cod. Christmas time is a busy time for my job and there are only two weeks until finals. But I promise I will never go to an iphone even if I do have to sell them next year. Plus the only reason I rooted my phone and made a kernel for it was to make it work perfectly for me. Since it is working and I have had 0 problems in almost 2 months of using it I dont really see room for much improvement until 2.2 comes out.
 
ROFL

I have just been hogged down with work and school that I have had 0 time to work on coding. Plus any time i have had in the last week I have spent playing cod. Christmas time is a busy time for my job and there are only two weeks until finals. But I promise I will never go to an iphone even if I do have to sell them next year. Plus the only reason I rooted my phone and made a kernel for it was to make it work perfectly for me. Since it is working and I have had 0 problems in almost 2 months of using it I dont really see room for much improvement until 2.2 comes out.

Totally understand man, it's that time of year. Just haven't seen you around and saps was being funny on xda.

Sent from my Super-Clean Fascinate
 
first off, i'm a total noob at this rooting stuff, but i did follow instructions and this is the screen i get:

93703023.jpg


immediately after the "Start time: 18:02:56.98" line appears, the phone shuts off to reset, and i'm assuming that why the "error: device not found" is showing up.

the whole process finishes, from top to bottom in maybe 10-15 sec and if i press a key at the end, it just closes the cmd prompt window.

can anyone help? many thanks in advance
 
first off, i'm a total noob at this rooting stuff, but i did follow instructions and this is the screen i get:

93703023.jpg


immediately after the "Start time: 18:02:56.98" line appears, the phone shuts off to reset, and i'm assuming that why the "error: device not found" is showing up.

the whole process finishes, from top to bottom in maybe 10-15 sec and if i press a key at the end, it just closes the cmd prompt window.

can anyone help? many thanks in advance

Follow the instructions in post 572 on page 58 of this thread. Your computer isn't recognizing your phone after it reboots in time for the script to finish the last few steps. You just have to manually execute a few commands.
 
  • Like
Reactions: schroeder
When i enter the first command, this is what i'm getting:

manualcodeerror.jpg


And just so that i'm clear on this, i'm NOT supposed to mount, just have debugging enabled, right?
 
it's cool, i just rooted the old fashion way, manually. barnacle works, so i guess i'm good. Thanks for the help, chris3d!
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,464
Messages
6,968,371
Members
3,163,552
Latest member
dumpsterrentals68