this is awsome my droid 2 is comming tomorrow.. my original droid screen died at the beginning of this week
I'm must be losing my computer touch, but I tried and I'm really lost. I can't get past this step:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
When I type adb my cmd prompt says the command is not recognized. I must doing something wrong. I have downloaded the sdk tool and extracted, I already have the motorola drives and I got the droid2root extracted. I really need a simpler step by step walkthrough.
@Jedidroid - I think you are having the same problem I did following the instructions. I stayed in the folder of my adb and added to the push. Example - When you followed cd c:/Droid2Root I skipped that step and then changed the next line to adb push c:/Droid2Root/Superuser.apk and so on for the pushes.
So i just did this if i pick the app it doesnt open up asking your superuser requests and i cannot choose uninstall on the bloatware apps however i downloaded a file manger and i can edit root files any one have any ideas?
What Is ADB And How To Install It? [Android]
go there and follow the steps to install adb into the path in the enironment variables
and only apps that require root will ask for superuser requests, not all apps.
When I do the 'adb devices' step, it returns "list of devices attached" and shows nothing connected. Seems I am missing something.
EDIT: SB Debugging enabled and PC Mode selected on connection