[HowTo] Root, Deodex, and Theme Droid Froyo 2.2 FRG22D

[Pir8Bob]

I have rooted successfully, but I had some trouble deodexing. When I open command prompt to the right directory and type "adb shell" a message appears that says "adb is not recognized as an internal or external command."

If you are using linux or a mac, you might have to run the command "./adb shell" instead.

 

[dfranks]

I have an OG droid with FRG83D and when I try to use the script on my mac i get this report in the terminal:

Modified for Droid 1 by Pir8Bob

Checking for needed files.
-->Superuser.apk
---->Downloading...
---->Success
-->su
---->Downloading...
---->Success
-->busybox
---->Downloading...
---->Success
-->rageagainstthecage-arm5.bin
---->Downloading...
---->Success

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled.
Do not enable USB Mass Storage when connected.

Checking for devices...

./doroot.sh: line 175: ./adb: No such file or directory
./doroot.sh: line 176: ./adb: No such file or directory

Transfering payload.
-->rageagainstthecage-arm5.bin
./doroot.sh: line 197: ./adb: No such file or directory
./doroot.sh: line 204: ./adb: No such file or directory
./doroot.sh: line 115: ./adb: No such file or directory

It appears you have an ADB session with root. Skipping exploit.

Remounting system as RW
./doroot.sh: line 265: ./adb: No such file or directory

Copying files to system.
-->Superuser.apk
./doroot.sh: line 275: ./adb: No such file or directory
-->Copying su
./doroot.sh: line 285: ./adb: No such file or directory
-->Copying busybox
./doroot.sh: line 295: ./adb: No such file or directory

Setting permissions
-->su
./doroot.sh: line 308: ./adb: No such file or directory
-->busybox
./doroot.sh: line 323: ./adb: No such file or directory
Creating cp link
./doroot.sh: line 333: ./adb: No such file or directory

Disabling recovery-from-boot.p
./doroot.sh: line 344: ./adb: No such file or directory

Remounting system as RO
./doroot.sh: line 359: ./adb: No such file or directory

Clean up: deleting temp files
-->rageagainstthecage-arm5.bin
./doroot.sh: line 386: ./adb: No such file or directory



Congratulations, you should now be rooted.

I'm going to reboot your phone in about 5 seconds. (ctrl+c to cancel)
./doroot.sh: line 757: ./adb: No such file or directory



when i'm done i unplugg and i still dont have root.

 

[Pir8Bob]

I have an OG droid with FRG83D and when I try to use the script on my mac i get this report in the terminal:

Modified for Droid 1 by Pir8Bob

Checking for needed files.
-->Superuser.apk
---->Downloading...
---->Success
-->su
---->Downloading...
---->Success
-->busybox
---->Downloading...
---->Success
-->rageagainstthecage-arm5.bin
---->Downloading...
---->Success

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled.
Do not enable USB Mass Storage when connected.

Checking for devices...

./doroot.sh: line 175: ./adb: No such file or directory
./doroot.sh: line 176: ./adb: No such file or directory

...

when i'm done i unplugg and i still dont have root.

That's because you didn't follow the directions. You didn't put doroot.sh in your android_sdk/tools directory.

Notice the numerous "./doroot.sh: line ###: ./adb: No such file or directory" lines? That means that doroot.sh can't find adb.

I advise that you rethink rooting your phone if you didn't notice this standard bash error.

 

[dfranks]

I have an OG droid with FRG83D and when I try to use the script on my mac i get this report in the terminal:

Modified for Droid 1 by Pir8Bob

Checking for needed files.
-->Superuser.apk
---->Downloading...
---->Success
-->su
---->Downloading...
---->Success
-->busybox
---->Downloading...
---->Success
-->rageagainstthecage-arm5.bin
---->Downloading...
---->Success

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled.
Do not enable USB Mass Storage when connected.

Checking for devices...

./doroot.sh: line 175: ./adb: No such file or directory
./doroot.sh: line 176: ./adb: No such file or directory

...

when i'm done i unplugg and i still dont have root.

That's because you didn't follow the directions. You didn't put doroot.sh in your android_sdk/tools directory.

Notice the numerous "./doroot.sh: line ###: ./adb: No such file or directory" lines? That means that doroot.sh can't find adb.

I advise that you rethink rooting your phone if you didn't notice this standard bash error.

Sorry i'm not very good with scripts but i'm well aware of what rooting is and can do. This is my 4th time rooting my phone but my 1st since 2.2. I'm not sure what you mean by i didn't put it in the correct folder. doroot.sh is located in my Users/*****/Downloads/android-sdk-mac_86/tools. Not trying to be annoying and i appreciate the help, I just want to understand what I did wrong.

 

[Pir8Bob]

Sorry i'm not very good with scripts but i'm well aware of what rooting is and can do. This is my 4th time rooting my phone but my 1st since 2.2. I'm not sure what you mean by i didn't put it in the correct folder. doroot.sh is located in my Users/*****/Downloads/android-sdk-mac_86/tools. Not trying to be annoying and i appreciate the help, I just want to understand what I did wrong.

Ok, I would open up your terminal and cd into the tools directory. "ls -l" and make sure that adb is there and that it's executable. Also make sure that doroot.sh is there and also executable (just for safety's sake). You can also make sure that adb is running alright by executing the command "./adb devices" straight from the terminal. If you have trouble running that commands, then you might want play it safe and get the whole sdk over again.

 

[dfranks]

Sorry i'm not very good with scripts but i'm well aware of what rooting is and can do. This is my 4th time rooting my phone but my 1st since 2.2. I'm not sure what you mean by i didn't put it in the correct folder. doroot.sh is located in my Users/*****/Downloads/android-sdk-mac_86/tools. Not trying to be annoying and i appreciate the help, I just want to understand what I did wrong.

Ok, I would open up your terminal and cd into the tools directory. "ls -l" and make sure that adb is there and that it's executable. Also make sure that doroot.sh is there and also executable (just for safety's sake). You can also make sure that adb is running alright by executing the command "./adb devices" straight from the terminal. If you have trouble running that commands, then you might want play it safe and get the whole sdk over again.

Thanks SOOOOO much. I did as you instructed and reinstalled the SDK and it worked perfectly. Thanks for all the help, your a life saver. I couldn't stand not being rooted for so long.

 

[Pir8Bob]

Glad I could help. And more than anything, I'm glad you got successfully rooted.