Root failed rooting

[timmyP_]

Hi, I followed this tutorial exactly: How to Root - Android Forums

1) i downloaded/installed the drivers

2) i unpackaged the rootkit onto the sdcard

3) i executed start_root.bat

4) the script(s) ran and the phone rebooted.

now, when i connect the phone to the computer (any computer) via usb, it isn't recognized. this is the main problem. i also downloaded rom manager, and it says i do not have root.

any help would be most appreciated.



when i run start_root from the tutorial now:

******************************************************************************
* *
* 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

*
* 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 . . .

nothing is being recognized...

 

[timmyP_]

also when i am connected to the computer via usb, it says there is no sdcard inserted (when there clearly is). it seems something went terribly wrong with the tutorial i used.

 

[saps]

also when i am connected to the computer via usb, it says there is no sdcard inserted (when there clearly is). it seems something went terribly wrong with the tutorial i used.

Are you/can you mount[ing] the sdcard?
If you can mount is the superuser.apk anywhere on the sdcard?
If not manually move it over and install it that way

 

[timmyP_]

Are you/can you mount[ing] the sdcard?
If you can mount is the superuser.apk anywhere on the sdcard?
If not manually move it over and install it that way

I can indeed mount the sdcard.

If by mount the superuser.apk do you mean save it on the sdcard? It's already on there.

How do I install it is my question?

 

[timmyP_]

OK, I just ran and installed superuser.apk...

Then I go to settings and tap su binary v original, and this message appears:

"new version of su binary available" press ok to attempt to install it automatically."

i click ok, then this msg appears:

"an error occurred and su was not updated. a zip file (su-2,3,1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.


how do i reboot into recovery mode and then flash my su binary??

 

[saps]

I can indeed mount the sdcard.

If by mount the superuser.apk do you mean save it on the sdcard? It's already on there.

How do I install it is my question?

OK, I just ran and installed superuser.apk...

Then I go to settings and tap su binary v original, and this message appears:

"new version of su binary available" press ok to attempt to install it automatically."

i click ok, then this msg appears:

"an error occurred and su was not updated. a zip file (su-2,3,1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.


how do i reboot into recovery mode and then flash my su binary??

Well it sounds like you got SU and it sounds like you got it out of the zip and as an apk. Do you also have busybox on there, you need them both? Also did you get the Samsung drivers too?

Recovery is accessed by holding down volume button while you push the power on

 

[timmyP_]

I have all the files in the root kit from How to Root - Android Forums

that tutorial

yes i have the samsung drivers installed

and yes, it has busybox, su, superuser.apk, and rage.bin

however im not sure how to implement all of these

also adb is not recognizing any devices

 

[timmyP_]

bump --- anyone?

 

[Smitty9803]

I had this same problem when I rooted mine a few days ago. I just can't remember how I fixed it so it would be recognized. Let me go back through the instructions and see if I can figure it out.

Did you download the right drivers? There are two sets...one for 32 bit and one for 64 bit.


ADDED: From what I can remember, I just uninstalled everything, reinstalled, and tried again. Also rebooted the phone before switching to "debugging" mode and pluging it into the computer. I don't think I did anything else beyond that and it magically worked. I may have downloaded the wrong drivers the first time but i'm not sure.

 

[timmyP_]

Ah so there is a glimpse of hope! haha

yes I assure you they are the correct drivers.

 

[Smitty9803]

When you installed the drivers...did you change where they were installed to or did you just install them into the Program Files folder (default)?

 

[nitsuj17]

When you installed the drivers...did you change where they were installed to or did you just install them into the Program Files folder (default)?

yeah if you have a 32 bit system its should be programfiles->samsung

 

[Smitty9803]

yeah if you have a 32 bit system its should be programfiles->samsung

I think this is why I had problems rooting mine...when I downloaded the drivers the first time, i installed them in a different folder. Once I uninstalled and re-downloaded, I downloaded them to the default folder (program files > samsung) and voila!

 

[timmyP_]

No the drivers are in program files.

I have already uninstalled everything. It simply will not detect any devices... I am so upset.

 

[saps]

No the drivers are in program files.

I have already uninstalled everything. It simply will not detect any devices... I am so upset.

This just happened to one of our phone guides D13 [PC was not seeing his SF] and he solved his problem by re-booting his PC. You might try the same, won't hurt and you know how 90% of windows issues are solved with a reboot.

 

[timmyP_]

I will try to reboot now and repeat the process.

Everyone please keep their fingers crossed.

 

[timmyP_]

Rebooted, and it was recognized!!!!!!!! What a simple yet crucial mistake of not rebooting, lol... thank you.

Used this tutorial and did it manually this time: http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Fascinate)

Thanks to everyone for the help

 

[saps]

Good Stuff tim. Yeah its always the simplest things

 

[Smitty9803]

Nice, glad you got it working man.

I may have rebooted mine as well when I had this problem but I can't remember...I need to start writing down each step I take when modding since I forget everything. lol

 

[D13]

Lol, I know how frustrating it can be

 

[timmyP_]

Just finished The ClockworkRecovery mod... now moving onto Cyanogen Mod...

then I dunno what to do from there lol..

 

[saps]

Just finished The ClockworkRecovery mod... now moving onto Cyanogen Mod...

then I dunno what to do from there lol..

De bloat or overclock

 

[nitsuj17]

Just finished The ClockworkRecovery mod... now moving onto Cyanogen Mod...

then I dunno what to do from there lol..

when you say moving on to cyanogen mod, im assuming you mean to follow steps to root or something, because cm is not yet available as a rom for galaxy s phones. It will at some point (and what a day THAT will be!!!) but they need 2.2 source or release first.

 

[timmyP_]

Im assuming de bloat means to take off all the bullshit on the phone, i have done that (THANKS ROOOOT)

now what though. what is the deal with lag fix, voodoo kernel bs??

 

[saps]

Im assuming de bloat means to take off all the bullshit on the phone, i have done that (THANKS ROOOOT)

now what though. what is the deal with lag fix, voodoo kernel bs??

next is likely either voodoo or OC. Lag fix/voodoo is where you will replace the stock RFS filesystem [slow] with EXT4 [faster reads and writes]. OC of course is where you take the stock 1Ghz and bump it up a bit. The nice thing is almost all the OC kernels are undervolted as well so despite the extra speed you should gain a bit of extra battery life too