Sorry for another "Root" thread...

[j32driver]

I need some help. The 1 click root method in the "How to Root" sticky doesn't work on my phone. START_ROOT begins and then the program fails and terminates about 3 seconds after it starts. So... I'm trying to do this manually... the problem is I'm a complete newb.

Here is what I've done:
I started with the method from here: Fascinate

The problem is the files are contained in a folder labeled Droid2 root. So... I took the files from the "How to Root" sticky and created my own folder to root from. In this folder, I have: rage, su, superuser, and busybox.

Using the command prompt, from inside AndroidSDK\tools I can adb device and it will list my fascinate. The next step has me cd to my folder that has my root files in it. After I cd and try to adb push the files to the phone, the adb command is no longer recognized.

Ideas for a newb?

 

[namebrandon]

I need some help. The 1 click root method in the "How to Root" sticky doesn't work on my phone. START_ROOT begins and then the program fails and terminates about 3 seconds after it starts. So... I'm trying to do this manually... the problem is I'm a complete newb.

Here is what I've done:
I started with the method from here: Fascinate

The problem is the files are contained in a folder labeled Droid2 root. So... I took the files from the "How to Root" sticky and created my own folder to root from. In this folder, I have: rage, su, superuser, and busybox.

Using the command prompt, from inside AndroidSDK\tools I can adb device and it will list my fascinate. The next step has me cd to my folder that has my root files in it. After I cd and try to adb push the files to the phone, the adb command is no longer recognized.

Ideas for a newb?

I'm not going to go into the explanation about why this is happening unless you want me to, but the quick and easy fix is to just copy your four files to your \tools directory and do everything from that same directory.

Then just skip any line that says.. "cd c:/fascinateRoot"

 

[j32driver]

Cool... thanks Brandon. I'll do it that way.

If you are bored and just want to type, I'd love to learn whats happening though.

 

[namebrandon]

Sure.. the adb executable (file/program) resides in your tools directory. In order to run this program, you need to run it from that specific directory.

The other option is to update your PATH environment variable to include your tools directory.

What that does, is when you run any command, it checks the directories listed in your PATH variable for the program you just tried to run. If it finds it, it runs the program.

Since you didn't add your \tools directory to your PATH variable, and since you've changed to a different directory (cd = change directory) that no longer contains the adb executable, it gives you the "command not found" (or similar) error message.

Not your fault, you probably didn't follow the official Android SDK install instructions, which is reasonable, since you just needed adb.exe for this process, and not the entire SDK.

You can Google 'windows path environment variable' for more details.

 

[j32driver]

Thanks Brandon. That actually helps a ton. I was wondering what "Path" was all about. That's a pretty good head start. I'm determined to become fluent in Android... just haven't had any time to study and play.

 

[j32driver]

Wow... getting ROOT is just kicking my butt. I know this shouldn't be this freakin hard.

Ok... moved the files to my tools folder. Got to the part where you run rage and then wait. It spawned children, posted up the paypal donate info, told me to wait, then I got something along the lines of adb will need to be restarted on the desktop client and it presented me with a $_ and didn't do anything else. I waited for more than 10 minutes and nothing.

I tried to navigate back to the tools directory but couldn't figure it out. So I closed the command prompt, restarted it and then started over. Except now, when I push rage to the phone, the command prompt doesn't respond. I ultimately wound up locking up the phone and needing a battery pull to get it back.

What the hell is my problem. Why won't this phone take root? I'm starting to feel like a complete idiot.

 

[namebrandon]

Hrm.. I don't have time to walk you through it now, but have you tried this method?

http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html

It should do the same thing, it's just automated a bit. If you still need help, just post again and I'll look at it in the morning.

Hang in there, we'll get you going.

 

[j32driver]

Brandon,

Thanks for the continued help. The "1 click" root method in the sticky doesn't work on my phone. I started with that method, tried it several times and it fails everytime. After I press a key to get the process started, it starts to load files and about 3 seconds later my command prompt dissappears and the process seems to just evaporate.

I used ASTRO to look at the SD card after all my problems last night, and the /data folder appears completely empty. I don't know if thats a clue or not. So far it looks like I've failed to push anything to the phone.

Here is my hardware setup:
32bit XP laptop
Fascinate running Launcherpro Plus
I removed PDAnet (free) because I thought it might be interfering since it also requires debugging mode in order to work.

I've got a win7 32bit laptop that belongs to the wife, I think I'm going to try the process from that computer to narrow down whether its a phone problem or a computer problem.

 

[namebrandon]

Ok, lemme follow that link you're using step by step and see if I can replicate the problem you're having.

 

[namebrandon]

okie dokie.. Good news, I did get your problem, and I know how to fix it. It's not your fault, it's the instructions.

lets kinda start this over.. (we're going to reboot your phone first, so don't be in the middle of anything)

Open a command prompt and cd to your tools folder, and enter the following commands.

adb reboot [enter] (this will reboot your phone)
adb kill-server [enter] (wait for the phone to fully reboot before proceeding to the third step)
adb shell [enter]

when you get the $ prompt, do the following

cd /data/local/tmp [enter]
rm -r rage*.bin [enter]
exit [enter]

now, assuming your rage.bin/su/busybox etc are all in the tools directory, do..

adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin [enter]
adb shell [enter]
cd /data/local/tmp [enter]
chmod 4755 rageagainstthecage-arm5.bin [enter]
./rageagainstthecage-arm5.bin [enter]

Now this should work properly, and you should see it drop you back to your dos prompt within ~30 seconds or so. You can follow the directions from this point forward.

If, for whatever reason, this freezes your phone, let me know. There might be an issue with this rage.bin exploit and the new DI01 upate.

We'll just skip this mess and set you up with CWM recovery. It'll be easier.

 

[j32driver]

Thanks Brandon. Gonna be a couple hours before I can tackle this. I'll let you know how it goes.

 

[j32driver]

SUCCESS!!!

Worked like a charm. Wireless Tether for Root installed with no problems. I must be good.

Next steps:
Backup
Bing hard search button fix
Bloatware removal.

Thanks again for all your help Brandon!

 

[namebrandon]

No problem-o.. Nice work!