Thanks to CRPercodani and UBRocked for originally putting this thread together. And thanks to Rootyourdroid.info even though the site is gone it provided a wealth of information.
What you need to know first:
Benefits of Rooting
Okay, so you know “how” to Root your phone… but why do it? What exactly can you get out of a Droid that has been rooted?
Well, aside from being cool and geeky, there are a few real benefits. Think of you Droid as a supercar. If you drive it only in subdivision streets, you aren’t really pushing it to its capabilities. However, if you take it to a track or maybe the Autobahn, you can open her up and unleash its power. Obtaining root is like taking your car to the Autobahn, except nerdier!
Enough of the analogies! Show me what I can do.
Most people want to root their phones for one reason: loading custom ROMs. A ROM, when it is applied to smartphone operating systems, is a fully customized image that alters the function and form of the device. For instance, a ROM could be a port of the HTC SenseUI found on Android phones like the Eris and the Hero. A person with root could potentially take this port, if made available, and put it on their Droid. At this time, there are no real custom ROMs for the Droid, though advancements are being made every week.
Another benefit of obtaining Root is the use of Root-only applications. Some applications require Superuser permissions in order to operate. You can think of “Superuser” as a limitless administrative role for the Android OS. It is given full control over what can be done on the software level. Superuser requires Root, and thus, so do certain apps. You can download Terminal apps which allow you to enter Android OS code to communicate with the system, Drocap2 which can take screengrabs anywhere on the phone, Adfree which disables advertisements on the web and in other apps, etc… There are many very cool programs being created specific to Root users!
One of the richest abilities given to Root users is scripting and customization. Given a mix of apps, the SDK, and scripts, Root users can change the way their phone feels and operates. Things like skinning every aspect of the OS, upgrading features that aren’t yet released, and creating all new functionality altogether could not be possible without Root. There is so much capability at such an early phase (remember, the Droid was first rooted only a few weeks ago), it’s an awesome time to be a part of the Root community. There will be groundbreaking discoveries and releases that will completely change the way you think about your Droid.
Rooting your phone is a fun, educational, and useful way of getting the most out of your device. But as always, there are risks involved every step of the way. Just be smart and careful, and don’t get ahead of yourself. I created this site as a guide for the average Joe, but even a plain-English guide can seem daunting for the more advanced operations. You need to keep in mind that by Rooting your Droid, you are most definitely going against the Verizon TOS and will be breaking your warranty. Though there are ways to revert back to a completely Root-free device, I can’t assure you this will not get you into trouble in the future.
Avoid Bricking
If you simply take your time and do things right, you can eliminate much- -if not all- -of that risk!
Obviously, the goal around here isn’t to pile as many non-working Droid’s into landfills as possible. We want you to successfully enhance the ability of your phone! So here are a few tips to help keep you from the dreaded brick…
Bricking a droid is actually quite hard to accomplish because almost anything can be recovered with an sbf file.
Follow directions carefully, making sure to read through them before beginning.
Go slow and take your time on every detail.
Research the action you are about to perform; if you don’t know much about it, become educated.
Trust your instinct. If you are unsure about something, perhaps you shouldn’t try.
Follow instructions fully. If you forget a step or quit before you’re done, there may be problems.
So happy rooting! And remember, as always, we are not responsible for your mistakes.
Preliminary Skills:
USB Debugging
USB Debugging is a common procedure used in Rooting and hacking the Droid. Simply said, it allows the Android Debugging Bridge to work its magic by allowing a seamless handshake between Droid and PC. We use this mode for copying data between the Droid and PC, installing apps, reviewing phone data, and for development purposes. It is very easy to setup, requiring only a system setting to be enabled.
Begin by connecting your Droid to a PC via USB. Go into the Droid settings and select Applications.
Select Development.
Ensure “USB debugging” is checked. You will be asked if you want to enable debugging, select yes.
And that is all there is to it. You now have a direct connection with ADB and your PC. We will do this to our phones most every time we need to transfer files via ADB.
Sometimes, people will have incompatible preloaded drivers on their computers. This may result in a “Device Not Found” error when following some guides. To remedy this, please refer to the USB Debugging Drivers guide.
Mounting The SD card to transfer files
Since your MicroSD card is buried underneath your battery, it is silly to remove it and use a card reader every time you want to copy files over to it. Fortunately, the Droid allows you to easily mount the MicroSD card as a mass storage device, similar to a USB Thumbdrive. Though we may also use ADB to copy files from our PC to our MicroSD card, this requires no Command Prompt or code use.
Mounting the MicroSD Card:
Connect your Droid to a PC via USB. You will be notified that there is a USB connection. Drag down the notification shade and select “USB connected.”
You will now see an option to mount your phone; do so at this time by selecting “Mount.”
This will turn your Droid into a mass storage device. Your computer should automatically recognize it and an autorun popup should appear on your desktop.
Browse the files so that you see the contents of your SD card. You are now ready to upload files onto the MicroSD card. Turning Off MicroSD Mounting:
Slide down the notification shade and select “Turn off USB storage.”
An option will popup allowing you to “Turn Off”–select this now.
If you haven’t closed the SD Card folder on your computer, the window should close automatically once you turn off USB storage.
ADB, command line bridge between the Android SDK and the Droid
The Droid is a highly hackable device, and much of this is due to the rich developer support directly from Google. As many of you know, the Droid runs the Android operating system which has been developed and pushed by Google. Not only do they provide the end-user OS you use on the phone, but they have created a full-featured SDK for private developers.
An SDK, or Software Developer’s Kit, is a collection of scripts, code, programs, and knowledge bases that assist people in creating Android apps and working inside the OS. It is a completely free package and is absolutely essential for higher level mods. You can read more about the SDK and download it from here: Android SDK | Android Developers
There is also an in-depth installation guide. It does not matter where on your computer the SDK folder is located and installed to. Follow the install guide before proceeding.
Inside of the SDK is the cornerstone of most Android mods: Android Debug Bridge. It is located within the tools folder (android-sdk-windows/tools) and can be accessed through Windows Command Prompt. This small application is a bridge between your computer and the Android OS on your phone. It allows you to push, pull, copy, and delete files as well as advanced scripts that perform specific tasks directly on your phone. You can think of it as an interface which extends your computer’s keyboard and files to your Droid.
In most of the upcoming Root Your Droid guides, you will see me reference the use of ADB, command prompt, Superuser permissions, and Linux code. This will all center around the SDK and Android Debug Bridge. But before you can use it, it’s important to learn what it is you’re doing.
How to access ADB through your Windows computer:
The first thing to know is how you access ADB to be able to use it. If you notice, double clicking on adb.exe in the tools folder does not open or run anything. In order to run ADB, we must do it through the Command Prompt.
To do this, go to your Start Menu and select “Run…”.
A Run dialogue will pop up; type “cmd” and hit OK.
This will open a new window called Windows Command Prompt.
This program is similar to DOS in that it allows you to input text-based commands in order to perform tasks. From here, we need to navigate to the tools folder inside of the Android SDK folder (where adb.exe is located). To do this, we need to know the exact file path of the tools folder. Open up the tools folder and at the top of the Windows Explorer window is the address, or file path, of the folder.
For instance, my tools folder is on the Desktop of my XP machine. Thus, the full file path of the folder is:
Cocuments and SettingsuserDesktopandroid-sdk-windowstools
Where “user” is the username of your computer. Copy your file path for use in the Command Prompt.
Back to the Command Prompt, we now need to point to the file path we copied. To do this, we need to type: “cd” for change directory, then add a space. This will preceed the file path of the folder. Right click inside Command Prompt and select Paste. You cannot use a keyboard shortcut to paste into Command Prompt, this will simply type out the keystrokes you used. Once we have typed in “cd ” and then pasted the file path, your Command Prompt should look like this:
Press enter and you will notice that where “c:” use to be is now replaced with the full file path of the tools folder.
If Command Prompt alerts you that “The system cannot find the path specified”, you probably have not pasted the correct or full path of the folder.
Tip: Windows Vista and 7 users may go into their tools folder, highlight the full address and simply replace it with “cmd”. Press enter and Command Prompt will open and will be pointed at the folder.
Once you have pointed Command Prompt to your tools folder, you may test to see if you have everything in order by typing “adb” and hitting enter.
If all went well, Command Prompt should display a long list off available commands and descriptions. Here is an explanation for the most commonly used ADB commands:
adb push – Copies a file from the computer onto the Droid.
adb pull – Copies a file from the Droid to the computer.
There are many more commands as you can see from the list Command Prompt gave you. These are simply the most common commands used in these guides. The guides will go more in depth as you go along. To use these commands, you must ensure your directory in Command Prompt is pointed to your tools folder.
You must be made aware that when accessing your Rooted phone through ADB, that you may be prompted to accept a Superuser Permission. To avoid seeing this in the future, simply select “Always” when this pops up. If you do not accept the permission, it will fail ADB.
Basic commands used within ADB
While working with a Rooted Droid and ADB, you will notice that there is an extensive use of code. Much of this code may be unfamiliar to you, but it shouldn’t be scary.
When you see lines such as:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
sync
You may feel like you are in over your head. But it’s a lot simpler than it looks!What you see above is called Unix commands. These commands are recognized by the base Linux kernel which controls the Android OS. Linux is an open source computer operating system; Google uses it to create Android. So these Unix commands are similar to the Windows Command Prompt commands we learned about in the Android Debug Bridge guide except they are used for different systems.
When using Unix commands in future guides, it is important to read through them carefully and copy them exactly. Though a mistake will most likely return an error message and cause no harm, it is possible to miss a character and do some damage. Caution and deliberation is key! Here are a few common Unix commands used for Droid modding purposes. These certainly aren’t all of them, and all commands will be described within individual guides.
su – (Substitute User) Used to change to “root user” to perform Superuser Permission commands.
mount – Readies a file system for use; allows the user to perform commands to a directory.
cd – (Change Directory) Changes to the proceeding directory.
chmod – (Change Mode) Changes the mode of files and directories; commonly used to change permissions.
mkdir – (Make Directory) Makes a new directory for files.
mv – (Move) Moves a file or directory from one place to another.
sync – Synchronizes all data which has been scheduled for writing.
As I’ve stated, there are many more commands which may be used while sending commands to your phone. Don’t fret; they will be described fully as you go along.
One important consideration to make is that after EACH line of Unix commands, you must hit enter to run the command before going on to the next line. You may not copy and paste multiple lines into Command Prompt at once.
I bet you’d never guessed you would be learning a new programming language while working on your Droid! Though you are far from mastering the Unix system, I hope this has familiarized you with some of the necessary commands needed for advanced root-related functions.
PC Drivers needed for the Droid
Some people are having problems with getting their Droids to connect to ADB after enabling USB Debugging. The reason for this problem may be incompatible USB drivers. To manually install the correct Droid USB Debugging drivers, please go to this link: Motorola USB Drivers
Simply download the Windows drivers that pertain to your system (32 or 64 bit), extract the installer, and install the drivers. Then, reconnect the Droid via USB and enable USB Debugging.
This will solve some of the “Device Not Found” problems people are having.
Installing apps not found in the market
Sometimes we want to install an app that has not been downloaded from the market. When we download an app from a developer or website directly, this is called an “Unsigned App”. Sometimes while hacking, we need to use an app that isn’t in the market. For this reason, we need to enable the installation from unknown sources.
Begin by connecting your Droid to a PC via USB. Go into the Droid settings and select Applications.
Ensure “Unknown Sources” is checked. You will be asked if you want to enable debugging, select yes.
You have now allowed your Droid to install apps not downloaded from the market.
Now onto the good stuff.....
How to Root 2.1 from Windows without losing app data
This method is meant for use with 2.1. It will work with other versions of android but the kernel will have to be changed to a kernel that is for that version of android.
Windows Instructions:
1.) Download 2.1 SP Recovery sbf to your C: root directory (C:\)
2.) Download md5sum
3.) Place md5sum in c:\windows\system32
5.) Download in install RSDLite 4.6 for this file you may need an un-zip tool like WIN RAR
6.) Download and install the correct motorola drivers for your windows machine (32 for XP, 32 or 64 for Vista depending on Vista version) Current Motorola Drivers
4.) Run command prompt (Start->Run then type "cmd" and hit enter)
5.) Change directories to your C:\ root directory (cd c:\)
6.) Type in "md5sum SPRecovery_ESE81.sbf"
7.) Make sure the sum of the image is EXACTLY 9b6a336cd8f067d4487935468c758d89
7.) Connect phone via USB and reboot, while rebooting hold UP on the dpad
8.) Run RSD Lite 4.6
Windows 7 64 Bit Users See Hidden Instructions
1.) Navigate to the install folder which is usually C:\Program Files\Motorola\RSD Lite
2.) Right click on SDL.exe
3.) Click run as administrator
9.) Select the SPRecovery 2.1 SBF file
10.) Click Start and wait for RSD Lite to flash the SPRecovery image onto phone and then wait on phone to reboot.
11.) Download this update.zip
12.) Mount your droid and place the update.zip in the root of your sd card.
13.) Power off your droid
14.) Power on your droid while holding X
15.) Now you are in SPRecovery. Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
16.) Press allow update.zip Installation
17.) Press Install /sdcard/update.zip (deprecated)
18.) Once that is complete use the power button to get back to the main menu.
19.) Press reboot system now
20.) Go to the Market and Download Titanium Backup
21.) Open titanium backup. This will bring up a superuser request. Press Allow
22.) Titanium backup will now give you an error. Press ok then press Problems?
23.) Press Yes, do it.
24.) This will kick you out of titanium backup. Click on the notification you got from titanium.
25.) Now that you are back in titanium press menu then batch.
26.) Now press Backup all user apps
27.) Press Run the batch operation
You can now install custom roms without fear of loosing your app data.
How to Root from Linux
Under Construction
How to perform a nandroid backup
How to perform a nandroid backup with SPRecovery
1.) Boot into recovery by holding X while powering on the phone
2.) Click backup/restore
3.) Press Simple Nandroid backup
4.) Once the nandroid is complete press power to get back to the main menu
5.) Reboot
That’s it
How to perform a nandroid backup with Clockworkmod Recovery
1.) Boot into recovery by holding X while powering on the phone
2.) Click nandroid
3.) Press Backup
4.) Once the nandroid is complete press power to get back to the main menu
5.) Reboot
That’s it
How to Flash a custom rom
There are two ways roms are distributed and one is not common anymore at all. For now this is just covering the most commonly used form which is update.zip. Instructions for roms distributed as nandroid backups will come later.
How to Flash a custom rom with SPRecovery
1.) Download the rom
2.) Place the file in the root of your sdcard.(Not in any folder just on the sd card.)
3.) Rename the rom to update.zip. Be sure that you are only naming it update.zip. Windows often does not show file extensions and you will end up with files named update.zip.zip. Renaming files with Astro File Manager once they are on your sd card is a good solution to this.
4.) Power off your droid
5.) Boot into recovery by holding X while powering on the phone
6.) Perform a nandroid backup (always sound practice although this is not required)
7.) Wipe data/factory reset (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)
8.) Wipe Cache Partition (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)
9.) Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
10.) Press allow update.zip Installation
11.) Press Install /sdcard/update.zip (deprecated)
12.) When the install is complete use the power button to go back to the main menu
13.) Reboot
How to Flash a custom rom with Clockworkmod Recovery
1.) Download the rom
2.) Put the file anywhere on your sdcard.
3.) Power off your droid
4.) Boot into recovery by holding X while powering on the phone
5.) Perform a nandroid backup (always sound practice although this is not required)
6.) Wipe data/factory reset (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)(This also wipes your cache partition so no reason to do that as well.)
7.) Press install zip from sdcard
8.) Press Choose zip from sd card
9.) Navigate to the file and click on it.
10.) When the install is complete press the power button to get back to the main menu
11.) Reboot
How to Flash a kernel
How to Flash a custom kernel with SPRecovery
1.) Download the kernel
2.) Place the file in the root of your sdcard.(Not in any folder just on the sd card.)
3.) Rename the kernel to update.zip. Be sure that you are only naming it update.zip. Windows often does not show file extensions and you will end up with files named update.zip.zip. Renaming files with Astro File Manager once they are on your sd card is a good solution to this.
4.) Power off your droid
5.) Boot into recovery by holding X while powering on the phone
6.) Perform a nandroid backup (always sound practice although this is not required. Its actually not necessary at all if you have a kernel that you know works well somewhere on your sdcard.)
7.) Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
8.) Press allow update.zip Installation
9.) Press Install /sdcard/update.zip (deprecated)
10.) When the install is complete use the power button to go back to the main menu
11.) Reboot
How to Flash a custom kernel with Clockworkmod Recovery
1.) Download the kernel
2.) Put the file anywhere on your sdcard.
3.) Power off your droid
4.) Boot into recovery by holding X while powering on the phone
5.) Perform a nandroid backup (always sound practice although this is not required. Its actually not necessary at all if you have a kernel that you know works well somewhere on your sdcard.)
6.) Press install zip from sdcard
7.) Press Choose zip from sd card
10.) Navigate to the file and click on it.
11.) When the install is complete press the power button to get back to the main menu
12.) Reboot
How to change recoveries
Changing Recoveries with Rom Manager
1.) Go into Rom Manager
2.) To Flash the current Clockworkmod Recovery press flash Clockworkmod Recovery
3.) You will be asked to confirm phone model which should be Motorola Droid (CDMA) if it is not then do no proceed.
4.) To Flash SPRecovery scroll to the bottom and press Flash Alternate Recovery
5.) To Flash a Clockworkmod other than the current one scroll to the bottom and press All Clockworkmod Recoveries
6.) Select the Clockworkmod Recovery that you wish to flash and press ok.
Changing Recoveries with Terminal
The current clockworkmod recovery can be downloaded Here
SPRecovery .99.3b can be found Here
Which ever recovery you are using should be in the root of your sd card.
You will also need Terminal Emulator from the market. I use the one by the dev Jack Palevich
To make this clearing I am going to put what you should actually type red.
I will be using SPRecovery as the example here but the process is the same for Clockworkmod just change the filename from recovery-0.99.3b.img to recovery-clockwork-2.5.0.1-sholes.img or whatever the name of the current clockworkmod recovery file is.
1.) Start Terminal Emulator
2.) type su then press enter
3.) type cd sdcard then press enter
4.) type flash_image recovery recovery-0.99.3b.img then press enter
5.) you are done but I would suggest typing reboot recovery then press enter so you can be sure it worked.
Changing Recoveries with ADB
The current clockworkmod recovery can be downloaded Here
SPRecovery .99.3b can be found Here
Which ever recovery you are using should be in the root of your sd card.
You will need the Android SDK so you have Android Debug Bridge
SDK can be found Here
To make this clearing I am going to put what you should actually type red.
I will be using SPRecovery as the example here but the process is the same for Clockworkmod just change the filename from recovery-0.99.3b.img to recovery-clockwork-2.5.0.1-sholes.img or whatever the name of the current clockworkmod recovery file is.
1.) Start command prompt if you are in windows or terminal emulator if you are in Linux
2.) cd to the adb tools director
3.) type adb shell then press enter
4.) type su then press enter
5.) type cd sdcard then press enter
6.) type flash_image recovery recovery-0.99.3b.img then press enter
7.) you are done but I would suggest typing reboot recovery then press enter so you can be sure it worked.
How to revert back to Stock 2.0, 2.0.1, 2.1, or 2.2
*I just want everyone to know that I didn't write this guide, just the first paragraph. You can thank ikithme for the guide.
Now that a .sbf file has been released for our Droid's we can always recover them using RSD Lite. it is pretty easy to use this. Of course if you physically break your phone it won't help, but if you screw anything up software wise you are covered.
If you unplug your phone while doing this it will break it beyond repair, Verizon will not be able to fix it. DO NOT ATTEMPT THIS UNLESS YOU ABSOLUTELY NEED TO USE IT!
Make sure you download the correct drivers for your system either 32bit or 64bit
Instructions:
1. Download all of the files above including the 32-bit OR 64-bit Motorola USB Drivers.
2. Install RSDLite AND the 32-bit or 64-bit Motorola USB Drivers (Depends on your system most will need 32-bit some will need 64-bit)
3. Connect your phone to USB and turn it off then turn it back on, while your phone is booting hold up on the DPAD. (Some users have said it is easier to hold the volume down button and camera button instead.)
4. Run RSD Lite 4.6 as Administrator (For all you Vista and 7 folks out there. If you are using XP you may not need to run as Administrator)
5. Click the ... next to the filename box and browse to where you saved the .sbf file and double click the .sbf file.
6. Hit start and below it should give you completion progress and all of that.
7. Once your phone is done being flashed (It may take a while so don't unplug it) it will reboot and you will be back at stock no root.
8. Done
Credits:
dordodim for the sbf file. ikithme for guide.
Motorola for the awesome phone, usb drivers and RSDLite.
Basebands
Install these the same way you would any rom or kernel.
Original Baseband Credit to Billgalbreath for the zip C_01.3E.01P
Second Baseband Credit to tehsteve for the zip C_01.3E.03P
Third Baseband Credit to P3Droid for the zip C_01.41.00R
Fourth Baseband Credit to P3Droid for the zip (Note flashing this baseband requires C_01.41.00R is already on your phone. C_01.43.01P
Installing Flash_image
Flash_image can be downloaded Here make sure it is in the root of your sd card.
Note that most roms will already have flash_image in place.
For this you will need to use either adb or terminal emulator. For terminal emulator I recommend the one on the market by Jack Palevich.
What you should actually type will be in red. Make sure it is typed exactly with all spaces included or it will not work.
Directions for Terminal
1.) Type su then press enter
2.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
3.) Type dd if=/sdcard/flash_image of=/system/bin/flash_image then press enter
4.) Type chmod 755 /system/bin/flash_image then press enter
5.) Type sync then press enter
Directions for ADB
1.) Open command prompt and cd to your adb tools directory
2.) Type adb shell then press enter
3.) Type su then press enter
4.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
5.) Type dd if=/sdcard/flash_image of=/system/bin/flash_image then press enter
6.) Type chmod 755 /system/bin/flash_image then press enter
7.) Type sync then press enter
Installing Busybox
This guide is for use with ADB. You can download Busybox Here place this in your adb tools folder.
Note that most roms will already have this installed.
What should actually be typed in adb will be in red.
1.) cd to your adb tools directory
2.) Type adb push busybox /data/local/busybox then press enter
3.) Type adb shell then press enter
4.) Type su then press enter
5.) Type cd /data/local then press enter
6.) Type chmod 755 busybox then press enter
7.) Type ./busybox then press enter
8.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
9.) Type /data/local/busybox cp /data/local/busybox /system/xbin then press enter
10.) Type cd /system/xbin then press enter
11.) Type busybox --install . then press enter
12.) Type mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system then press enter
13.) Type sync then press enter
14.) Type reboot then press enter
Not stickied b/c the powers that be are consolidating all the {old} stickies into single informational stickies with links to the {old} stickied posts.
Location: The land of palm trees, sunny skies, and sandy beaches
Posts: 5,053
Device(s): HTC Droid Incredible
Carrier: Not Provided
Thanks: 776
Thanked 1,546 Times in 770 Posts
OMJ, you should make another root guide for this subforum and post all the important root threads such as this one in it. Kelmar and I are doing the same for some of the forums as this will help alot in terms of being able to have all the relevant info right infront of users.
I never had that in there. The reason for that is because there are so many different ways to do themes that its best to follow the instructions of the themer
Device(s): Retired OG Droid
Injury Retired Droid X
Current LTE Galaxy Nexus, VZW
Carrier: Not Provided
Thanks: 56
Thanked 59 Times in 43 Posts
Quote:
Originally Posted by OMJ
I never had that in there. The reason for that is because there are so many different ways to do themes that its best to follow the instructions of the themer
Ohh ok. I thought i've seen it here before. Gracias amigo
Ok OMJ bit of a noob here and considering Rooting. I haven't done any kind of programing since windows 3.1 and have what might be a bit of a silly question. what's the dif between a ROM and a Kernal, and do you need both? From my antiquated recolection to extrapolating conclusions here, the Kernal is your bios (clock speed, etc) and the ROM would be your OS (for lack of better term)?
__________________
"You can take my DROID from my cold dead hand..... no probably not even then with the Kung Fu death grip I'll have on it."
Ok OMJ bit of a noob here and considering Rooting. I haven't done any kind of programing since windows 3.1 and have what might be a bit of a silly question. what's the dif between a ROM and a Kernal, and do you need both? From my antiquated recolection to extrapolating conclusions here, the Kernal is your bios (clock speed, etc) and the ROM would be your OS (for lack of better term)?
Your assessment of rom and kernel is pretty close. You dont need both or either but most roms do come with custom kernels.
Quote:
Originally Posted by TharOosta
Quesion:If I decide to root. Can I download paid apps for free like a jailbroken iPhone?
nope...Paying for apps supports the developers and brings more developers to android. The more apps that get paid for the better the market will get.
If you are looking for pirated apps you came to the wrong place. Android forums supports the dev community and not piracy.
The Following 2 Users Say Thank You to OMJ For This Useful Post:
I have the dumbest question your probably ever going to hear. I do not have a computer, my Droid is my computer, it seems pretty obvious to me that I cannot do this without one. Am I correct in that conclusion? Thanks.
I have the dumbest question your probably ever going to hear. I do not have a computer, my Droid is my computer, it seems pretty obvious to me that I cannot do this without one. Am I correct in that conclusion? Thanks.
Well if you are on frg22d then all the current root methods require a computer.
The Following User Says Thank You to OMJ For This Useful Post:
Well if you are on frg22d then all the current root methods require a computer.
Yes -- if you were on FRG01B you could have upgraded to FRG22D rooted without a computer, but if you're already on FRG22D you need to at least flash a custom recovery to be able to install the root tools even if you dont want to flash a ROM.
Yes -- if you were on FRG01B you could have upgraded to FRG22D rooted without a computer, but if you're already on FRG22D you need to at least flash a custom recovery to be able to install the root tools even if you dont want to flash a ROM.
It's funny cause I was FRG01B when I started reading this thread. I did a factory reset and came out the other end at FRG22D.
Your assessment of rom and kernel is pretty close. You dont need both or either but most roms do come with custom kernels.
OK good because I love my droid as is, Nice and vanilla, but I hate bloatwear and was thinking about bringing up my CPU clock (nothing fancy I was thinking about 800 would do well for me). Where would there be a function for that or would i need an app to do that (I think I read about one in another forum)?
OK good because I love my droid as is, Nice and vanilla, but I hate bloatwear and was thinking about bringing up my CPU clock (nothing fancy I was thinking about 800 would do well for me). Where would there be a function for that or would i need an app to do that (I think I read about one in another forum)?
you just need the app setcpu. The stock kernel can actually OC to 800mhz.
The Following User Says Thank You to OMJ For This Useful Post:
OMFG so i did 2.2 sbf to unroot and my RSD took forever then said FAIL!!! said that is was not flashed and then my phone said completed...booted back up and perfect! So people if you try this and it says fail, then you still may have a chance.
So on the last last line of reverting back to stock you said you will be at 2.0.1 but that's just if you chose that one. If you do 2.2 that's what you should be back at right? Also will I begin to receive OTAs again in the future?
So on the last last line of reverting back to stock you said you will be at 2.0.1 but that's just if you chose that one. If you do 2.2 that's what you should be back at right? Also will I begin to receive OTAs again in the future?
thats correct on both accounts. The 2.0.1 thing is just a left over from the original guide. I will edit it out now.
If anyone has anything that they think should be added to this let me know now. I only have my droid until monday or tuesday so after that I wont be able test things out for myself which will make it much harder to update this thread.
I followed the following directs on how to revert your Droid:
Instructions:
1. Download all of the files above including the 32-bit OR 64-bit Motorola USB Drivers.
2. Install RSDLite AND the 32-bit or 64-bit Motorola USB Drivers (Depends on your system most will need 32-bit some will need 64-bit)
3. Connect your phone to USB and turn it off then turn it back on, while your phone is booting hold up on the DPAD. (Some users have said it is easier to hold the volume down button and camera button instead.)
4. Run RSD Lite 4.6 as Administrator (For all you Vista and 7 folks out there. If you are using XP you may not need to run as Administrator)
5. Click the ... next to the filename box and browse to where you saved the .sbf file and double click the .sbf file.
6. Hit start and below it should give you completion progress and all of that.
7. Once your phone is done being flashed (It may take a while so don't unplug it) it will reboot and you will be back at stock no root.
8. Done
At first I wasn't able to run RSD as administrator. I had to go into properties and check the box for it (no menu item when right-clicked). However, once I select the .sbf file I cannot hit start. It is faded out. I'm lost as to how continue. Please help or direct me to something that can.
I downloaded the 2.1 .sbf and now the program works. It's flashing now. I'll post the results after.
The flashing was a success. I then loaded the newest OTA update to the phone. Now I cannot root my phone using Easy Root or Universal Androot. Is this due to the newest update?
Last edited by oG-ShAdY; September 15th, 2010 at 02:47 AM.
I followed the following directs on how to revert your Droid:
Instructions:
1. Download all of the files above including the 32-bit OR 64-bit Motorola USB Drivers.
2. Install RSDLite AND the 32-bit or 64-bit Motorola USB Drivers (Depends on your system most will need 32-bit some will need 64-bit)
3. Connect your phone to USB and turn it off then turn it back on, while your phone is booting hold up on the DPAD. (Some users have said it is easier to hold the volume down button and camera button instead.)
4. Run RSD Lite 4.6 as Administrator (For all you Vista and 7 folks out there. If you are using XP you may not need to run as Administrator)
5. Click the ... next to the filename box and browse to where you saved the .sbf file and double click the .sbf file.
6. Hit start and below it should give you completion progress and all of that.
7. Once your phone is done being flashed (It may take a while so don't unplug it) it will reboot and you will be back at stock no root.
8. Done
At first I wasn't able to run RSD as administrator. I had to go into properties and check the box for it (no menu item when right-clicked). However, once I select the .sbf file I cannot hit start. It is faded out. I'm lost as to how continue. Please help or direct me to something that can.
I downloaded the 2.1 .sbf and now the program works. It's flashing now. I'll post the results after.
The flashing was a success. I then loaded the newest OTA update to the phone. Now I cannot root my phone using Easy Root or Universal Androot. Is this due to the newest update?
@OMJ
First thanks for all your help, I'm rooted now and LOVEING IT. I mean seriously, just rooting increased my quadrant score and cleaned up a lot of lag in my Launcherpro. Now I just have one question, how do I remove the bloatwear!!?? I looked in the settings>applications, no dice. I saw that someone said you can delete them with TiBU but I didn't see it (or maybe it's an option only for paid version). Help!!
BTW says you don't have a Droid anymore, What did you get and why!?
@OMJ
First thanks for all your help, I'm rooted now and LOVEING IT. I mean seriously, just rooting increased my quadrant score and cleaned up a lot of lag in my Launcherpro. Now I just have one question, how do I remove the bloatwear!!?? I looked in the settings>applications, no dice. I saw that someone said you can delete them with TiBU but I didn't see it (or maybe it's an option only for paid version). Help!!
BTW says you don't have a Droid anymore, What did you get and why!?
Titanium is the easiest way to remove apps. Its what I use. In titanium press on the Backup/Restore tab. The just select any app that you want to remove and there is on option to uninstall.
I got a DX. I got it cause I like the bigger screen and a physical keyboard is not important to me. I also just wanted something new and work was willing to buy me a DX if I gave my Droid to a coworker. So I was able to get a new phone for free without extending my contract. I wanna get another Droid 1 but I am not willing to spend much on a phone that I wont be using as a phone.
The Following User Says Thank You to OMJ For This Useful Post:
Ok well at first, sorry for the long post. I was happy with my vanilla droid OC'd at around 700 (my Duke nukem is soooo awsome now). But after the favorable responces to my phanboy post, I figured I'd wet my feet on something easier first before I took the plunge. I have Rom Manager, TiBu, and SetCPU and I noticed in ROM manager it had a section "download ROM." Thought to myself "hay this might be a way to do it without my comp," and dove in. Since it had good RRS scores I figured I'd get LiquidFroyo and just do the stock one. Did (several) nandroid backups (thank the gods that be that I learned to listen to the wise ones here) and hit download. Took a while but it eventually said download complete and came up with "perform backup" and "Wipe data and install." Well being the anal individual I am (job requirement, backups of backups and data out the yang) I hit perform backup. I know everyone says wipe data (a few times according to issanne) but I figured that was after the backup. Next thing I know it says installing Liquid and I got stuck in a boot loop. Recovered and I'm back to my vannila just fine but now I can't find the new rom? What happened?
NM - I got it. I reflashed CwMod as I saw someone post in the app section of the forum. I just tried to DL LiQFroYo again and it went straight to the "perform backup" and "Wipe data and install" (I guess RM kept the ROM I DL'd all though where I haven't a clue). Hit the wipe and viola!! I have LiQFroYo!!! So incase any other noobs want an uncomplicated version.
1. BU in RM - name something (stable or something like that).
2. BU apps not in market in TiBu. (lost a few here but nothing important)
2.2 BU Launcher Pro if you have it. Saves a lot of time and skull sweat remembering where things are at.
3. DL rom in RM, when prompted hit "Wipe data and install"
4. WAIT!!!!! Your apps will come back after a while. (took about 20 min for all of mine install and all.)
5. If you have Launcher Pro (I love it and refuse to use anything else.) restore your settings. You might have to repaste a few widgits but that's no big deal.
6. ENJOY ROM'ing!!!!!!!!!!
this is worse than crack!!! I'm already thinking of another rom and maybe a kernel or two.
Last edited by corbinator; October 1st, 2010 at 02:30 PM.
Reason: update
Thanks to CRPercodani and UBRocked for originally putting this thread together. And thanks to Rootyourdroid.info even though the site is gone it provided a wealth of information.
What you need to know first:
Benefits of Rooting
Okay, so you know how to Root your phone but why do it? What exactly can you get out of a Droid that has been rooted?
Well, aside from being cool and geeky, there are a few real benefits. Think of you Droid as a supercar. If you drive it only in subdivision streets, you arent really pushing it to its capabilities. However, if you take it to a track or maybe the Autobahn, you can open her up and unleash its power. Obtaining root is like taking your car to the Autobahn, except nerdier!
Enough of the analogies! Show me what I can do.
Most people want to root their phones for one reason: loading custom ROMs. A ROM, when it is applied to smartphone operating systems, is a fully customized image that alters the function and form of the device. For instance, a ROM could be a port of the HTC SenseUI found on Android phones like the Eris and the Hero. A person with root could potentially take this port, if made available, and put it on their Droid. At this time, there are no real custom ROMs for the Droid, though advancements are being made every week.
Another benefit of obtaining Root is the use of Root-only applications. Some applications require Superuser permissions in order to operate. You can think of Superuser as a limitless administrative role for the Android OS. It is given full control over what can be done on the software level. Superuser requires Root, and thus, so do certain apps. You can download Terminal apps which allow you to enter Android OS code to communicate with the system, Drocap2 which can take screengrabs anywhere on the phone, Adfree which disables advertisements on the web and in other apps, etc There are many very cool programs being created specific to Root users!
One of the richest abilities given to Root users is scripting and customization. Given a mix of apps, the SDK, and scripts, Root users can change the way their phone feels and operates. Things like skinning every aspect of the OS, upgrading features that arent yet released, and creating all new functionality altogether could not be possible without Root. There is so much capability at such an early phase (remember, the Droid was first rooted only a few weeks ago), its an awesome time to be a part of the Root community. There will be groundbreaking discoveries and releases that will completely change the way you think about your Droid.
Rooting your phone is a fun, educational, and useful way of getting the most out of your device. But as always, there are risks involved every step of the way. Just be smart and careful, and dont get ahead of yourself. I created this site as a guide for the average Joe, but even a plain-English guide can seem daunting for the more advanced operations. You need to keep in mind that by Rooting your Droid, you are most definitely going against the Verizon TOS and will be breaking your warranty. Though there are ways to revert back to a completely Root-free device, I cant assure you this will not get you into trouble in the future.
Avoid Bricking
If you simply take your time and do things right, you can eliminate much- -if not all- -of that risk!
Obviously, the goal around here isnt to pile as many non-working Droids into landfills as possible. We want you to successfully enhance the ability of your phone! So here are a few tips to help keep you from the dreaded brick
Bricking a droid is actually quite hard to accomplish because almost anything can be recovered with an sbf file.
Follow directions carefully, making sure to read through them before beginning.
Go slow and take your time on every detail.
Research the action you are about to perform; if you dont know much about it, become educated.
Trust your instinct. If you are unsure about something, perhaps you shouldnt try.
Follow instructions fully. If you forget a step or quit before youre done, there may be problems.
So happy rooting! And remember, as always, we are not responsible for your mistakes.
Preliminary Skills:
USB Debugging
USB Debugging is a common procedure used in Rooting and hacking the Droid. Simply said, it allows the Android Debugging Bridge to work its magic by allowing a seamless handshake between Droid and PC. We use this mode for copying data between the Droid and PC, installing apps, reviewing phone data, and for development purposes. It is very easy to setup, requiring only a system setting to be enabled.
Begin by connecting your Droid to a PC via USB. Go into the Droid settings and select Applications.
Select Development.
Ensure USB debugging is checked. You will be asked if you want to enable debugging, select yes.
And that is all there is to it. You now have a direct connection with ADB and your PC. We will do this to our phones most every time we need to transfer files via ADB.
Sometimes, people will have incompatible preloaded drivers on their computers. This may result in a Device Not Found error when following some guides. To remedy this, please refer to the USB Debugging Drivers guide.
Mounting The SD card to transfer files
Since your MicroSD card is buried underneath your battery, it is silly to remove it and use a card reader every time you want to copy files over to it. Fortunately, the Droid allows you to easily mount the MicroSD card as a mass storage device, similar to a USB Thumbdrive. Though we may also use ADB to copy files from our PC to our MicroSD card, this requires no Command Prompt or code use.
Mounting the MicroSD Card:
Connect your Droid to a PC via USB. You will be notified that there is a USB connection. Drag down the notification shade and select USB connected.
You will now see an option to mount your phone; do so at this time by selecting Mount.
This will turn your Droid into a mass storage device. Your computer should automatically recognize it and an autorun popup should appear on your desktop.
Browse the files so that you see the contents of your SD card. You are now ready to upload files onto the MicroSD card. Turning Off MicroSD Mounting:
Slide down the notification shade and select Turn off USB storage.
An option will popup allowing you to Turn Offselect this now.
If you havent closed the SD Card folder on your computer, the window should close automatically once you turn off USB storage.
ADB, command line bridge between the Android SDK and the Droid
The Droid is a highly hackable device, and much of this is due to the rich developer support directly from Google. As many of you know, the Droid runs the Android operating system which has been developed and pushed by Google. Not only do they provide the end-user OS you use on the phone, but they have created a full-featured SDK for private developers.
An SDK, or Software Developers Kit, is a collection of scripts, code, programs, and knowledge bases that assist people in creating Android apps and working inside the OS. It is a completely free package and is absolutely essential for higher level mods. You can read more about the SDK and download it from here: Android SDK | Android Developers
There is also an in-depth installation guide. It does not matter where on your computer the SDK folder is located and installed to. Follow the install guide before proceeding.
Inside of the SDK is the cornerstone of most Android mods: Android Debug Bridge. It is located within the tools folder (android-sdk-windows/tools) and can be accessed through Windows Command Prompt. This small application is a bridge between your computer and the Android OS on your phone. It allows you to push, pull, copy, and delete files as well as advanced scripts that perform specific tasks directly on your phone. You can think of it as an interface which extends your computers keyboard and files to your Droid.
In most of the upcoming Root Your Droid guides, you will see me reference the use of ADB, command prompt, Superuser permissions, and Linux code. This will all center around the SDK and Android Debug Bridge. But before you can use it, its important to learn what it is youre doing.
How to access ADB through your Windows computer:
The first thing to know is how you access ADB to be able to use it. If you notice, double clicking on adb.exe in the tools folder does not open or run anything. In order to run ADB, we must do it through the Command Prompt.
To do this, go to your Start Menu and select Run .
A Run dialogue will pop up; type cmd and hit OK.
This will open a new window called Windows Command Prompt.
This program is similar to DOS in that it allows you to input text-based commands in order to perform tasks. From here, we need to navigate to the tools folder inside of the Android SDK folder (where adb.exe is located). To do this, we need to know the exact file path of the tools folder. Open up the tools folder and at the top of the Windows Explorer window is the address, or file path, of the folder.
For instance, my tools folder is on the Desktop of my XP machine. Thus, the full file path of the folder is:
Cocuments and SettingsuserDesktopandroid-sdk-windowstools
Where user is the username of your computer. Copy your file path for use in the Command Prompt.
Back to the Command Prompt, we now need to point to the file path we copied. To do this, we need to type: cd for change directory, then add a space. This will preceed the file path of the folder. Right click inside Command Prompt and select Paste. You cannot use a keyboard shortcut to paste into Command Prompt, this will simply type out the keystrokes you used. Once we have typed in cd and then pasted the file path, your Command Prompt should look like this:
Press enter and you will notice that where c: use to be is now replaced with the full file path of the tools folder.
If Command Prompt alerts you that The system cannot find the path specified, you probably have not pasted the correct or full path of the folder.
Tip: Windows Vista and 7 users may go into their tools folder, highlight the full address and simply replace it with cmd. Press enter and Command Prompt will open and will be pointed at the folder.
Once you have pointed Command Prompt to your tools folder, you may test to see if you have everything in order by typing adb and hitting enter.
If all went well, Command Prompt should display a long list off available commands and descriptions. Here is an explanation for the most commonly used ADB commands:
adb push Copies a file from the computer onto the Droid.
adb pull Copies a file from the Droid to the computer.
There are many more commands as you can see from the list Command Prompt gave you. These are simply the most common commands used in these guides. The guides will go more in depth as you go along. To use these commands, you must ensure your directory in Command Prompt is pointed to your tools folder.
You must be made aware that when accessing your Rooted phone through ADB, that you may be prompted to accept a Superuser Permission. To avoid seeing this in the future, simply select Always when this pops up. If you do not accept the permission, it will fail ADB.
Basic commands used within ADB
While working with a Rooted Droid and ADB, you will notice that there is an extensive use of code. Much of this code may be unfamiliar to you, but it shouldnt be scary.
When you see lines such as:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
sync
You may feel like you are in over your head. But its a lot simpler than it looks!What you see above is called Unix commands. These commands are recognized by the base Linux kernel which controls the Android OS. Linux is an open source computer operating system; Google uses it to create Android. So these Unix commands are similar to the Windows Command Prompt commands we learned about in the Android Debug Bridge guide except they are used for different systems.
When using Unix commands in future guides, it is important to read through them carefully and copy them exactly. Though a mistake will most likely return an error message and cause no harm, it is possible to miss a character and do some damage. Caution and deliberation is key! Here are a few common Unix commands used for Droid modding purposes. These certainly arent all of them, and all commands will be described within individual guides.
su (Substitute User) Used to change to root user to perform Superuser Permission commands.
mount Readies a file system for use; allows the user to perform commands to a directory.
cd (Change Directory) Changes to the proceeding directory.
chmod (Change Mode) Changes the mode of files and directories; commonly used to change permissions.
mkdir (Make Directory) Makes a new directory for files.
mv (Move) Moves a file or directory from one place to another.
sync Synchronizes all data which has been scheduled for writing.
As Ive stated, there are many more commands which may be used while sending commands to your phone. Dont fret; they will be described fully as you go along.
One important consideration to make is that after EACH line of Unix commands, you must hit enter to run the command before going on to the next line. You may not copy and paste multiple lines into Command Prompt at once.
I bet youd never guessed you would be learning a new programming language while working on your Droid! Though you are far from mastering the Unix system, I hope this has familiarized you with some of the necessary commands needed for advanced root-related functions.
PC Drivers needed for the Droid
Some people are having problems with getting their Droids to connect to ADB after enabling USB Debugging. The reason for this problem may be incompatible USB drivers. To manually install the correct Droid USB Debugging drivers, please go to this link: Motorola USB Drivers
Simply download the Windows drivers that pertain to your system (32 or 64 bit), extract the installer, and install the drivers. Then, reconnect the Droid via USB and enable USB Debugging.
This will solve some of the Device Not Found problems people are having.
Installing apps not found in the market
Sometimes we want to install an app that has not been downloaded from the market. When we download an app from a developer or website directly, this is called an Unsigned App. Sometimes while hacking, we need to use an app that isnt in the market. For this reason, we need to enable the installation from unknown sources.
Begin by connecting your Droid to a PC via USB. Go into the Droid settings and select Applications.
Ensure Unknown Sources is checked. You will be asked if you want to enable debugging, select yes.
You have now allowed your Droid to install apps not downloaded from the market.
Now onto the good stuff.....
How to Root 2.1 from Windows without losing app data
This method is meant for use with 2.1. It will work with other versions of android but the kernel will have to be changed to a kernel that is for that version of android.
Windows Instructions:
1.) Download 2.1 SP Recovery sbf to your C: root directory (C:\)
2.) Download md5sum
3.) Place md5sum in c:\windows\system32
5.) Download in install RSDLite 4.6 for this file you may need an un-zip tool like WIN RAR
6.) Download and install the correct motorola drivers for your windows machine (32 for XP, 32 or 64 for Vista depending on Vista version) Current Motorola Drivers
4.) Run command prompt (Start->Run then type "cmd" and hit enter)
5.) Change directories to your C:\ root directory (cd c:\)
6.) Type in "md5sum SPRecovery_ESE81.sbf"
7.) Make sure the sum of the image is EXACTLY 9b6a336cd8f067d4487935468c758d89
7.) Connect phone via USB and reboot, while rebooting hold UP on the dpad
8.) Run RSD Lite 4.6
Windows 7 64 Bit Users See Hidden Instructions
1.) Navigate to the install folder which is usually C:\Program Files\Motorola\RSD Lite
2.) Right click on SDL.exe
3.) Click run as administrator
9.) Select the SPRecovery 2.1 SBF file
10.) Click Start and wait for RSD Lite to flash the SPRecovery image onto phone and then wait on phone to reboot.
11.) Download this update.zip
12.) Mount your droid and place the update.zip in the root of your sd card.
13.) Power off your droid
14.) Power on your droid while holding X
15.) Now you are in SPRecovery. Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
16.) Press allow update.zip Installation
17.) Press Install /sdcard/update.zip (deprecated)
18.) Once that is complete use the power button to get back to the main menu.
19.) Press reboot system now
20.) Go to the Market and Download Titanium Backup
21.) Open titanium backup. This will bring up a superuser request. Press Allow
22.) Titanium backup will now give you an error. Press ok then press Problems?
23.) Press Yes, do it.
24.) This will kick you out of titanium backup. Click on the notification you got from titanium.
25.) Now that you are back in titanium press menu then batch.
26.) Now press Backup all user apps
27.) Press Run the batch operation
You can now install custom roms without fear of loosing your app data.
How to Root from Linux
Under Construction
How to perform a nandroid backup
How to perform a nandroid backup with SPRecovery
1.) Boot into recovery by holding X while powering on the phone
2.) Click backup/restore
3.) Press Simple Nandroid backup
4.) Once the nandroid is complete press power to get back to the main menu
5.) Reboot
Thats it
How to perform a nandroid backup with Clockworkmod Recovery
1.) Boot into recovery by holding X while powering on the phone
2.) Click nandroid
3.) Press Backup
4.) Once the nandroid is complete press power to get back to the main menu
5.) Reboot
Thats it
How to Flash a custom rom
There are two ways roms are distributed and one is not common anymore at all. For now this is just covering the most commonly used form which is update.zip. Instructions for roms distributed as nandroid backups will come later.
How to Flash a custom rom with SPRecovery
1.) Download the rom
2.) Place the file in the root of your sdcard.(Not in any folder just on the sd card.)
3.) Rename the rom to update.zip. Be sure that you are only naming it update.zip. Windows often does not show file extensions and you will end up with files named update.zip.zip. Renaming files with Astro File Manager once they are on your sd card is a good solution to this.
4.) Power off your droid
5.) Boot into recovery by holding X while powering on the phone
6.) Perform a nandroid backup (always sound practice although this is not required)
7.) Wipe data/factory reset (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)
8.) Wipe Cache Partition (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)
9.) Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
10.) Press allow update.zip Installation
11.) Press Install /sdcard/update.zip (deprecated)
12.) When the install is complete use the power button to go back to the main menu
13.) Reboot
How to Flash a custom rom with Clockworkmod Recovery
1.) Download the rom
2.) Put the file anywhere on your sdcard.
3.) Power off your droid
4.) Boot into recovery by holding X while powering on the phone
5.) Perform a nandroid backup (always sound practice although this is not required)
6.) Wipe data/factory reset (Again not required all the time but unless you are sure it will work without wiping its smart to do so.)(This also wipes your cache partition so no reason to do that as well.)
7.) Press install zip from sdcard
8.) Press Choose zip from sd card
9.) Navigate to the file and click on it.
10.) When the install is complete press the power button to get back to the main menu
11.) Reboot
How to Flash a kernel
How to Flash a custom kernel with SPRecovery
1.) Download the kernel
2.) Place the file in the root of your sdcard.(Not in any folder just on the sd card.)
3.) Rename the kernel to update.zip. Be sure that you are only naming it update.zip. Windows often does not show file extensions and you will end up with files named update.zip.zip. Renaming files with Astro File Manager once they are on your sd card is a good solution to this.
4.) Power off your droid
5.) Boot into recovery by holding X while powering on the phone
6.) Perform a nandroid backup (always sound practice although this is not required. Its actually not necessary at all if you have a kernel that you know works well somewhere on your sdcard.)
7.) Click on install (Note you can use the volume rocker to navigate and the camera button to select.)
8.) Press allow update.zip Installation
9.) Press Install /sdcard/update.zip (deprecated)
10.) When the install is complete use the power button to go back to the main menu
11.) Reboot
How to Flash a custom kernel with Clockworkmod Recovery
1.) Download the kernel
2.) Put the file anywhere on your sdcard.
3.) Power off your droid
4.) Boot into recovery by holding X while powering on the phone
5.) Perform a nandroid backup (always sound practice although this is not required. Its actually not necessary at all if you have a kernel that you know works well somewhere on your sdcard.)
6.) Press install zip from sdcard
7.) Press Choose zip from sd card
10.) Navigate to the file and click on it.
11.) When the install is complete press the power button to get back to the main menu
12.) Reboot
How to change recoveries
Changing Recoveries with Rom Manager
1.) Go into Rom Manager
2.) To Flash the current Clockworkmod Recovery press flash Clockworkmod Recovery
3.) You will be asked to confirm phone model which should be Motorola Droid (CDMA) if it is not then do no proceed.
4.) To Flash SPRecovery scroll to the bottom and press Flash Alternate Recovery
5.) To Flash a Clockworkmod other than the current one scroll to the bottom and press All Clockworkmod Recoveries
6.) Select the Clockworkmod Recovery that you wish to flash and press ok.
Changing Recoveries with Terminal
The current clockworkmod recovery can be downloaded Here
SPRecovery .99.3b can be found Here
Which ever recovery you are using should be in the root of your sd card.
You will also need Terminal Emulator from the market. I use the one by the dev Jack Palevich
To make this clearing I am going to put what you should actually type red.
I will be using SPRecovery as the example here but the process is the same for Clockworkmod just change the filename from recovery-0.99.3b.img to recovery-clockwork-2.5.0.1-sholes.img or whatever the name of the current clockworkmod recovery file is.
1.) Start Terminal Emulator
2.) type su then press enter
3.) type cd sdcard then press enter
4.) type flash_image recovery recovery-0.99.3b.img then press enter
5.) you are done but I would suggest typing reboot recovery then press enter so you can be sure it worked.
Changing Recoveries with ADB
The current clockworkmod recovery can be downloaded Here
SPRecovery .99.3b can be found Here
Which ever recovery you are using should be in the root of your sd card.
You will need the Android SDK so you have Android Debug Bridge
SDK can be found Here
To make this clearing I am going to put what you should actually type red.
I will be using SPRecovery as the example here but the process is the same for Clockworkmod just change the filename from recovery-0.99.3b.img to recovery-clockwork-2.5.0.1-sholes.img or whatever the name of the current clockworkmod recovery file is.
1.) Start command prompt if you are in windows or terminal emulator if you are in Linux
2.) cd to the adb tools director
3.) type adb shell then press enter
4.) type su then press enter
5.) type cd sdcard then press enter
6.) type flash_image recovery recovery-0.99.3b.img then press enter
7.) you are done but I would suggest typing reboot recovery then press enter so you can be sure it worked.
How to revert back to Stock 2.0, 2.0.1, 2.1, or 2.2
*I just want everyone to know that I didn't write this guide, just the first paragraph. You can thank ikithme for the guide.
Now that a .sbf file has been released for our Droid's we can always recover them using RSD Lite. it is pretty easy to use this. Of course if you physically break your phone it won't help, but if you screw anything up software wise you are covered.
If you unplug your phone while doing this it will break it beyond repair, Verizon will not be able to fix it. DO NOT ATTEMPT THIS UNLESS YOU ABSOLUTELY NEED TO USE IT!
Make sure you download the correct drivers for your system either 32bit or 64bit
Instructions:
1. Download all of the files above including the 32-bit OR 64-bit Motorola USB Drivers.
2. Install RSDLite AND the 32-bit or 64-bit Motorola USB Drivers (Depends on your system most will need 32-bit some will need 64-bit)
3. Connect your phone to USB and turn it off then turn it back on, while your phone is booting hold up on the DPAD. (Some users have said it is easier to hold the volume down button and camera button instead.)
4. Run RSD Lite 4.6 as Administrator (For all you Vista and 7 folks out there. If you are using XP you may not need to run as Administrator)
5. Click the ... next to the filename box and browse to where you saved the .sbf file and double click the .sbf file.
6. Hit start and below it should give you completion progress and all of that.
7. Once your phone is done being flashed (It may take a while so don't unplug it) it will reboot and you will be back at stock no root.
8. Done
Credits:
dordodim for the sbf file. ikithme for guide.
Motorola for the awesome phone, usb drivers and RSDLite.
Basebands
Install these the same way you would any rom or kernel.
Original Baseband Credit to Billgalbreath for the zip C_01.3E.01P
Second Baseband Credit to tehsteve for the zip C_01.3E.03P
Third Baseband Credit to P3Droid for the zip C_01.41.00R
Fourth Baseband Credit to P3Droid for the zip (Note flashing this baseband requires C_01.41.00R is already on your phone. C_01.43.01P
Installing Flash_image
Flash_image can be downloaded Here make sure it is in the root of your sd card.
Note that most roms will already have flash_image in place.
For this you will need to use either adb or terminal emulator. For terminal emulator I recommend the one on the market by Jack Palevich.
What you should actually type will be in red. Make sure it is typed exactly with all spaces included or it will not work.
Directions for Terminal
1.) Type su then press enter
2.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
3.) Type dd if=/sdcard/flash_image of=/system/bin/flash_image then press enter
4.) Type chmod 755 /system/bin/flash_image then press enter
5.) Type sync then press enter
Directions for ADB
1.) Open command prompt and cd to your adb tools directory
2.) Type adb shell then press enter
3.) Type su then press enter
4.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
5.) Type dd if=/sdcard/flash_image of=/system/bin/flash_image then press enter
6.) Type chmod 755 /system/bin/flash_image then press enter
7.) Type sync then press enter
Installing Busybox
This guide is for use with ADB. You can download Busybox Here place this in your adb tools folder.
Note that most roms will already have this installed.
What should actually be typed in adb will be in red.
1.) cd to your adb tools directory
2.) Type adb push busybox /data/local/busybox then press enter
3.) Type adb shell then press enter
4.) Type su then press enter
5.) Type cd /data/local then press enter
6.) Type chmod 755 busybox then press enter
7.) Type ./busybox then press enter
8.) Type mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system then press enter
9.) Type /data/local/busybox cp /data/local/busybox /system/xbin then press enter
10.) Type cd /system/xbin then press enter
11.) Type busybox --install . then press enter
12.) Type mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system then press enter
13.) Type sync then press enter
14.) Type reboot then press enter
how about a section about how to and where the OTA updates are stored on the phone and how to capture, save, export one BEFORE you do the update.
__________________
/** SGS3 (rooted & stock ROM) **/
/** Asus Prime TF201 (rooted & mildly OC'd) BRICKED BY THE ASUS OTA JB UPATE!**/
/** OG Droid (rooted & OC'd & all hacked up) **/
I am looking to root my D1 again and still have RSD Lite on my computer and the ese81.sbf file from back in july. I have the latest version of 2.2.1. so can I use that sbf file or is there a current version?
hey guys, what a great post, thank you to OP. it's really nice to see that people are willing to take so much time out just to help others.
i am trying to revert from android 2.2.2 back to 2.2.1. the update causes alot of lag on my phone, and has screwed up a few of my games/apps, and my main goal is to revert the update. i have an LG Optimus S (LS670) and it's my first android phone. so, i got to step 3 before realizing that this is the motorola droid forum. how depressing. so i figured it can't hurt to ask, just to make sure..... is this guide indeed only for motorola? i'm obviously somewhat new to doing extra add-ons and such to my phone. i always thought i was relatively cell-savvy until i started trying to research android and saw all these forums about rooting, and XDA and all that good stuff. i have been looking all over the net on how to revert for weeks. it seems as though it's harder to find instructions because my phone is unrooted. i didn't see any posts concerning reverting, such as this one, in the LG Optimus S forum. everytime i find something that looks like it might help me, it either a. seems to be for anything but the LS670, or b. scares me away. i know you guys aren't about people posting about their phones in the wrong forum, but i didn't know where else to go, and out of all the sites/posts i've seen regarding reverting, this is the most legit sounding one yet, and i've seen a buttload. if anyone is willing to give me any kind of help i'd really appreciate it.. even if you could just steer me in the right direction i'd be forever indebted to you thanks in advance guys. and just know that there's tons of people like myself out there that could only wish to have half of the knowledge about technology/cell phones in general that some of you have. it never ceases to amaze me that people even know how to perform these tasks. thanks again
Device(s): The Droid Bionic......
OG Droid - rooted,
Nexus 7
Carrier: Not Provided
Thanks: 20
Thanked 81 Times in 76 Posts
Quote:
Originally Posted by jenboben388
hey guys, what a great post, thank you to OP. it's really nice to see that people are willing to take so much time out just to help others.
i am trying to revert from android 2.2.2 back to 2.2.1. the update causes alot of lag on my phone, and has screwed up a few of my games/apps, and my main goal is to revert the update. i have an LG Optimus S (LS670) and it's my first android phone. so, i got to step 3 before realizing that this is the motorola droid forum. how depressing. so i figured it can't hurt to ask, just to make sure..... is this guide indeed only for motorola? i'm obviously somewhat new to doing extra add-ons and such to my phone. i always thought i was relatively cell-savvy until i started trying to research android and saw all these forums about rooting, and XDA and all that good stuff. i have been looking all over the net on how to revert for weeks. it seems as though it's harder to find instructions because my phone is unrooted. i didn't see any posts concerning reverting, such as this one, in the LG Optimus S forum. everytime i find something that looks like it might help me, it either a. seems to be for anything but the LS670, or b. scares me away. i know you guys aren't about people posting about their phones in the wrong forum, but i didn't know where else to go, and out of all the sites/posts i've seen regarding reverting, this is the most legit sounding one yet, and i've seen a buttload. if anyone is willing to give me any kind of help i'd really appreciate it.. even if you could just steer me in the right direction i'd be forever indebted to you thanks in advance guys. and just know that there's tons of people like myself out there that could only wish to have half of the knowledge about technology/cell phones in general that some of you have. it never ceases to amaze me that people even know how to perform these tasks. thanks again
-Jen
Sorry no one got to your post sooner. I hope this is not to late a response, but this is the Droid 1 forum.
The forum you need to post your question in is the one I linked below. It is the LG Optimus S All-Things-Root-Forum and the people there should be able to help you better.
I don't know why it's not working. I press start and NOTHING HAPPENS! Why? Can someone explain me? I even made a thread stating what happened to my cellphone!
Ok i flashed the file. It worked but now i rebooted and i'm in the ! TRIANGLE area. Nothing else. Did i miss something? Am i suppose to make it go into OS?
Last edited by pcnuttie; October 13th, 2011 at 01:33 PM.
I can not get anywhere with this device. Not sure of the correct drivers, adk, adt plugin? I have read this whole forum but i am unsure of what kernel versions to pick as well as my 2.3.3 os version im a newbie can someone please help?
If i were to unroot back to 2.2.2, would I lose all of my data (texts, pictures, app data, etc.)? If so, what would be the easiest way to keep them safe while still unrooting? Thanks!
If i were to unroot back to 2.2.2, would I lose all of my data (texts, pictures, app data, etc.)? If so, what would be the easiest way to keep them safe while still unrooting? Thanks!
Texts and app data yes. Your pics should be on your sdcard so no worries there. MyBackupPro will save texts, call logs, and app data, but if you're unrooted, I don't know if it will restore them all, definitely not app data. Besides, I wouldn't backup/restore app data ever anyways. Usually causes too many problems.
The Guide to All Things Root Related
ocuments and SettingsuserDesktopandroid-sdk-windowstools
Help
Recovered and I'm back to my vannila just fine but now I can't find the new rom? What happened?
question about these instructions/reverting...
thanks in advance guys. and just know that there's tons of people like myself out there that could only wish to have half of the knowledge about technology/cell phones in general that some of you have. it never ceases to amaze me that people even know how to perform these tasks. thanks again 
