• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Working EASY Root

mackeydesigns said:
I've been on this part for several minutes now (maybe going on 10+) with no movement back to the folder. What should I do?
Click to expand...

Most likely your phone froze. Restart your phone and start with that step again. No need to start over, just do this again: ./rageagainstthecage-arm5.bin

Zegapain said:
So here is the beginning of my confusion. I unziped "android-sdk-windows" to my "c:" drive and then I took the FOUR FILES within the "fascinateRoot.rar" folder and put them in "c:\sdk\tools\

When I go to do the command prompts it tells me "adb is not recognized as an internal or external command, operable program or batch file".

I am getting so frustrated with this. I mean, I feel so r3tarded right now. I've home-brewed a PSP before surely this can't much more difficult. This is my very first Android phone coming from a shitty LG VX10000. I would love nothing more then to install LauncherPro and get rid of all this bloatware on my Fascinate. :(
Click to expand...

You can install LauncherPro right now. It does not require root in any way. You're getting the "adb is not recognized" error because you have to be in C:\sdk\tools to run any adb commands (unless you do some other complicated steps to let you run 'adb' commands anywhere in command prompt). So, navigate to C:\sdk\tools, then run all of the commands. If you already extracted the fascinateRoot.zip files to C:\sdk\tools, you should be ready to go. Just navigate to C:\sdk\tools and copy/paste the commands exactly as they are in the guide. No need to modify them at all.

I know that's a wordy explanation so let me know if that doesn't clear it up for you.
 
eleazar said:
Most likely your phone froze. Restart your phone and start with that step again. No need to start over, just do this again: ./rageagainstthecage-arm5.bin



You can install LauncherPro right now. It does not require root in any way. You're getting the "adb is not recognized" error because you have to be in C:\sdk\tools to run any adb commands (unless you do some other complicated steps to let you run 'adb' commands anywhere in command prompt). So, navigate to C:\sdk\tools, then run all of the commands. If you already extracted the fascinateRoot.zip files to C:\sdk\tools, you should be ready to go. Just navigate to C:\sdk\tools and copy/paste the commands exactly as they are in the guide. No need to modify them at all.

I know that's a wordy explanation so let me know if that doesn't clear it up for you.
Click to expand...

There is just something simple I'm not doing right. I'm not sure if I have all the different folders/files where they need to be exactly. For example I first double click on "My Computer", then I double click on my C: drive then within that I see the "sdk" folder. When I double click the sdk folder within that I see the "android-sdk-windows" and the "tools" folders.

But then again there is a "tools" folder via C:\sdk\android-sdk-windows\tools. Should the Four fascinateROOT files be within that "tools" folder or the other "tools" folder?

I at least know in order for these command prompts to work properly the specified folders and files need to be in the right places. Are folder/files in the wrong places?
 
Zegapain said:
There is just something simple I'm not doing right. I'm not sure if I have all the different folders/files where they need to be exactly. For example I first double click on "My Computer", then I double click on my C: drive then within that I see the "sdk" folder. When I double click the sdk folder within that I see the "android-sdk-windows" and the "tools" folders.

But then again there is a "tools" folder via C:\sdk\android-sdk-windows\tools. Should the Four fascinateROOT files be within that "tools" folder or the other "tools" folder?

I at least know in order for these command prompts to work properly the specified folders and files need to be in the right places. Are folder/files in the wrong places?
Click to expand...

If you want easy access to the ADB commands, to save typing full paths, and you don't have your Environment Variables set - it won't hurt to put the fascinateRoot files in that directory.

However, this isn't *necessary*.
 
Okay so I think I put the files and folders in the right places. I then proceeded to the command prompt and entered everything exactly within summerfish's post.

Here is a screengrab of my log. http://img718.imageshack.us/img718/1583/commandlogroot.png

I believe everything went fine. Am I supposed to reset my phone now or was it supposed to reset during the rooting process because my phone didn't automatically reset or anything.
 
Zegapain said:
Okay so I think I put the files and folders in the right places. I then proceeded to the command prompt and entered everything exactly within summerfish's post.

Here is a screengrab of my log. http://img718.imageshack.us/img718/1583/commandlogroot.png

I believe everything went fine. Am I supposed to reset my phone now or was it supposed to reset during the rooting process because my phone didn't automatically reset or anything.
Click to expand...

It all looks right. The # means that at least at some point in the process you had superuser permissions.

You should reboot the phone to get Superuser.apk loaded, then you should be able to grant superuser permissions to things like Titanium Backup and One Click Lag Fix.
 
burningembers said:
It all looks right. The # means that at least at some point in the process you had superuser permissions.

You should reboot the phone to get Superuser.apk loaded, then you should be able to grant superuser permissions to things like Titanium Backup and One Click Lag Fix.
Click to expand...

Hmm, I now see superuser in my apps folder but when I select it a blank screen just appears.
 
Zegapain said:
I thought I had to input the command "adb reboot recovery" and then select something that says "reinstall packages"?
Click to expand...

I'm not aware of this...but I'm not an expert.

I seem to be able to grant superuser permissions to root-only applications just fine, and they work - and I never did anything like that.

Someone else may need to comment.
 
burningembers said:
I'm not aware of this...but I'm not an expert.

I seem to be able to grant superuser permissions to root-only applications just fine, and they work - and I never did anything like that.

Someone else may need to comment.
Click to expand...

It's okay. I don't think it matters now. So now that I'm rooted I can finally erase all the bloatware and install a google search widget?
 
theicemonkey said:
Thanks so much for the help (and for not getting frustrated with me!). If anyone else did the method listed on the Phandroid homepage and then had trouble, follow the following steps FIRST, before trying the above method:

Code: 
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/bin/joeykrim-root.sh
rm /system/bin/jk-su
rm /system/bin/playlogo
rm /etc/passwd
rm /etc/group
mv /system/bin/playlogo-orig /system/bin/playlogo
mount -t rfs -o remount,ro /dev/block/stl9 /system

Please Note: The above steps are joeykrim's (of SDX) uninstallation method for his root guide

Once I did this and rebooted, I was able to successfully complete this version and achieve permanent root.
Click to expand...

wait, so is this actually how to unroot the phone?

or is it to get to a safe place after botching part of the process?

people are saying it's a permanent root, but is this referring to the fact that it'll stick, or that there's no way of undoing it?
 
I may have missed this but I want to root my phone but only IF there is a factory ROM so I can return the phone if I ever have to. I want to get all the bing bloatware off the device. Also I really like the idea of the Car Cradle is there a way to change the default map setting to google if I root the phone?
 
jspidah said:
wait, so is this actually how to unroot the phone?

or is it to get to a safe place after botching part of the process?

people are saying it's a permanent root, but is this referring to the fact that it'll stick, or that there's no way of undoing it?
Click to expand...

I believe permanent is referring to it "sticking" after reboot. That un-installation guide might work if you used his guide (joeykrim), but if you used the guide in this thread, I do not believe that will work.

Viper1117 said:
I may have missed this but I want to root my phone but only IF there is a factory ROM so I can return the phone if I ever have to. I want to get all the bing bloatware off the device. Also I really like the idea of the Car Cradle is there a way to change the default map setting to google if I root the phone?
Click to expand...

I don't know of any factory ROM's being released yet. My only other Android experience is with the Incredible and they had RUU files to flash back to stock. I assume something similar exists for Samsung phones but I don't know what it is.

I'm not sure about your 2nd question relating to the Car Cradle app. Hopefully someone else can answer it for you.

nunyabizness said:
nm :)
Click to expand...

Great to see that you're making the switch! :)
 
This is what I get for entering this...

adb push c:/sdk/tools/rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
'c:/sdk/tools/rageagainstthecage-arm5.bin' is not recognized as an internal or external command,
operable program or batch file.


I can't think of a misstep up to this point. It did take me awhile to install the USB device driver; it kept asking me for the disk that came with the phone. Finally got past that... it's now recognized.

The installing of the 'adb', SDK, and whatnot, etc... made me lose some hair.

Any idea why it's telling me 'No'?
 
Ok, found the misstep. 'tools' was not directly under the 'sdk' folder. I just copy/pasted 'tools' into 'sdk'.
Now, I noticed you've changed the 3rd command to ---> adb push C:\fascinateRoot\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin

I've got rageagainstthecage-arm5.bin in c:\fascinateRoot. I also copied busybox, su, and Superuser.apk to c:\fascinateRoot It couldn't hurt, could it?

However, I keep getting "Permission denied" even when I open cmd.exe with ctrl-shift-enter. I've even rebooted into "Test Mode".

Please help.
 
makemehavefun said:
Ok, found the misstep. 'tools' was not directly under the 'sdk' folder. I just copy/pasted 'tools' into 'sdk'.
Now, I noticed you've changed the 3rd command to ---> adb push C:\fascinateRoot\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin

I've got rageagainstthecage-arm5.bin in c:\fascinateRoot. I also copied busybox, su, and Superuser.apk to c:\fascinateRoot It couldn't hurt, could it?

However, I keep getting "Permission denied" even when I open cmd.exe with ctrl-shift-enter. I've even rebooted into "Test Mode".

Please help.
Click to expand...

So you're getting the Permission denied error when you try to push the rageagainstthecage-arm5.bin file? Can you post a screenshot of your command prompt history? (similar to what I have in my first post). I'm not sure what you're referring to with "Test Mode" or running cmd.exe with ctrl-shift-enter(you shouldn't need to run cmd.exe as administrator).
 
I seem to have somehow removed my boot animation - not sure if it was in the process of rooting, doing the lag fix, or removing some bloatware via RootExplorer. It's not a big deal I guess, but it kinda freaks me out to see my phone boot up to a black screen! Is there an easy way to get it back?
 
nunyabizness said:
I seem to have somehow removed my boot animation - not sure if it was in the process of rooting, doing the lag fix, or removing some bloatware via RootExplorer. It's not a big deal I guess, but it kinda freaks me out to see my phone boot up to a black screen! Is there an easy way to get it back?
Click to expand...

eeks, that's never fun. Unfortunately I don't know how to get it back but if you realize you need a file from my 'unmodified' filesystem, just let me know and I'll send it over.

How about those Bucks yesterday? :D
 
There is still no way to do a nandroid even after root, correct? Is it because there is no recovery yet for the Fascinate?

What have you guys done with root, besides add Google voice search to the search soft key?
 
Correct, there is no nandroid yet and it because we don't have a recovery yet (ie. Clockworkmod).

I personally use Titanium Backup religiously. The absolute best backup program in my opinion. It backs up your apps and can restore all of them with just a few taps. I bought it after using it the first time. I was able to restore all of my apps like I had never switched phones.

Anyway, I'd recommend checking out the http://androidforums.com/fascinate-all-things-root/173085-confirmed-working-root-apps.html thread for more root only apps. I'll add some descriptions to the apps so people can see if they would be useful for them.
 
eleazar said:
eeks, that's never fun. Unfortunately I don't know how to get it back but if you realize you need a file from my 'unmodified' filesystem, just let me know and I'll send it over.

How about those Bucks yesterday? :D
Click to expand...

Eh, it's alright, like I said, it's just psychological. Way to get around it: don't look at my phone while it's rebooting! :p Plus this was my first time rooting, and since everything else appears to be working as it should, I figure unless anyone knows the exact (and hopefully uncomplicated! LOL) steps to repair it, I'm not even going to risk screwing something up just to fix a splash screen that I'd only see every 4-5 days anyway. :)

Yeah, how about 'em! :D Two down, 10 to go!
 
eleazar said:
So you're getting the Permission denied error when you try to push the rageagainstthecage-arm5.bin file? Can you post a screenshot of your command prompt history? (similar to what I have in my first post). I'm not sure what you're referring to with "Test Mode" or running cmd.exe with ctrl-shift-enter(you shouldn't need to run cmd.exe as administrator).
Click to expand...
Sorry, was afk all day. Yeah, Permission repeatedly denied and now I'm pretty sure it was because I didn't edit/add-on the Path variable under "System Properties > Advanced Tab > Environment Variables". Does that sound right?

Anyhow, I'm having Verizon send me a replacement cuz the AMOLED display itself is slightly off center by about a half millimeter at the top left... just enough to make the entire display look noticeably tilted NE/SW. They'll be sending it overnight so it'll arrive Tuesday.

Obviously, without being able to unroot it back to a clean factory reset state, I'm going to hold off until then. I think I'll be good after I set the Path variable as I've gotten past/resolved the SDK/ADB install and USB driver update issues. Hopefully, I won't have to ask for your help again, lol *fingers crossed*
 
You must log in or register to reply here.
Back
Top Bottom