What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[HACKS] Root Droid 1 - regardless of OS version

So when you boot into the os you don't have root and when you reboot into recovery it is the stock recovery?

But after you flash the sbf you are able to get into sprecovery?

Sent from my Droid using Tapatalk

"Things you're going to need:

  1. A Windows based computer. Personally, XP would be preferred, but if it is something newer you'll probably be OK. Windows 7 has the most trouble, followed by Vista. That said, many people have no problem at all with either OS, and at this point we've got solutions to most of the issues that come up. If you're running Windows 7 you may want to go ahead and read the Frequently Encountered Issues section now (before you start the process) so if you hit any of those issues you'll already know there is a solution for it. If you don't have a Windows computer but do have a Linux box, you should be able to substitute sbf_flash for RSD Lite and use the exact same process. Follow the sbf_flash instructions on the author's page.
    13977d1282620419-root-droid-1-regardless-os-version-vs.gif
  2. RSD Lite 4.6. That's a "7 zip" file. If you have WinRAR it will unzip it no problem. If you don't have WinRAR, or anything else that will unzip a 7-zip file, WinRAR is a good choice. If that link ever dies you should have no problem finding RSD Lite 4.6 all over the place. Just so you know you're getting the exact some file and not a slightly different version or an adulterated copy, the file inside the zip is named RSDLite4.6.msi and the MD5 hash for the file is eb315e028f38b4b3244778782485cd6d.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  3. Either the 32-bit or 64-bit Motorola drivers as appropriate for your machine. [Here are some older versions in case the links may be useful (32-bit or 64-bit).]
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  4. My "recovery only" SPRecovery SBF for the Droid 1. (Link)
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  5. My "complete root" update file. (Link)
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  6. Your phone and the micro-USB cable to connect your phone to your computer."
"Detailed Procedure:

  1. Attach your phone to your computer.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  2. Unzip the SBF file that you downloaded in Step 4 of "things you're going to need" above. This will produce the file MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  3. Do not unzip the MotoCache1_Complete_Root_v1.1-update.zip file that you downloaded in Step 5 of "things you're going to need". You need to copy this file to the root of your phone's SD card and then rename it to update.zip. Note: If on your computer you see the file listed as "MotoCache1_Complete_Root_v1.1-update" (no .zip on the end) then when you copy it to the phone you should name it just "update" (no ".zip"). There are several ways to do this (ADB, mount the phone's file system, etc.). Use which ever you're comfortable with. If you don't know how to do this there are tons of posts on it.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  4. Power down your phone normally.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  5. Once the phone is off, slide open the keyboard and press on the "up" direction of the directional keypad rocker (the direction toward the screen -- which could really be to the right depending on how you're holding the phone) [pic]. While holding the dpad in the up direction, simultaneously press and hold the power button of the phone. When you see the backlight of the screen come on you can release the power button and the bootloader screen should appear (it will say "Bootloader" in the upper left corner). You can release the dpad. At the bottom of the text on the screen it should say "Transfer Mode: USB" if your cable is properly connected.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  6. Start RSD Lite on your computer. If you're on a version of Windows newer than XP, remember to run RSD Lite as administrator by right clicking its menu choice and choosing "Run as Administrator". If you don't have such an option, you may be able to right click on the shortcut, choose "properties", and check "Run this program as Administrator" [pic].
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  7. Hopefully the phone will be listed in the grid in the bottom half of the RSD Lite window. Give it a minute or two if it doesn't show up right away. Sometimes it takes Windows a minute (or 2 or 3) to let go of the phone and pick it back up again after rebooting into the bootloader. If after a couple minutes your phone still isn't listed in the "Model" column of the bottom section, in RSD Lite, click Config, Device Id Options, and choose "First-Come-First-ServeDeviceId Mode" and press "OK". RSD Lite may say you need to restart RSD -- if so, do so.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  8. Assuming that you now can see your phone listed, click the "..." button to the right of the "Filename:" box. Find the SBF file you unzipped earlier and choose it. After choosing the file the right hand File details pane will fill in.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  9. OK, this step is where you are going to press "Start" in RSD Lite, but don't do that yet. Before you press Start, read step 10. Step 10 has some timing sensitive tasks. If your phone has functioning FRS (discussed earlier), and you do step 10 wrong, you will have to start back over with this step as the FRS will undo the flash you just did with RSD. Once you've read Step 10 and know what you'll be doing next, go ahead and press Start.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  10. After clicking Start, the flashing process goes through several distinct steps. This particular SBF file is very small so it finishes pretty quickly. At some point there will be a bit of a delay with RSD Lite showing a status of "Phone[0000]: Waiting for re-enumeration". After that is when the actual flashing happens. When the flashing has completed, RSD Lite is going to issue a "reboot-bootloader" command to your phone. Unfortunately the Droid does not appear to implement the reboot-bootloader command correctly and does a normal reboot instead. If you don't "catch the boot" by holding up on the dpad key the OS will boot (and if you have functioning FRS the custom recovery you just flashed on will be put back to stock). Just before sending the reboot instruction to your phone the status in RSD Lite will change to "Phone[0000]: Phone is being rebooted". On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot within a second or two. You want to be already holding the dpad key up when the phone actually reboots. If you followed the instructions for Step 9 you have pre-read this step and knew to be ready for this. If not, your phone is probably already rebooted into the OS. If you failed to catch the boot, and the OS booted, let the phone finish booting, then power it off, hold the dpad up and power it back on. After that, continue through the steps like nothing happened. If your recovery got flashed back to stock we'll know it soon enough.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  11. You should now be looking at the bootloader on the phone, and RSD Lite should still be saying "Phone[0000]: Phone is being rebooted". If too much time has passed RSD Lite may be saying "Please manually boot the phone". The "Progress" value on the screen will keep incrementing, and at some point before, or at, 100% the result should change to "PASS".
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  12. Power the phone off again. With the keyboard open, press and hold the "X" key on the physical keyboard and keep it held while you power the phone on. Once the phone comes on you can release the power button, but keep the "X" button held until you see the the Motorola logo.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  13. When recovery starts, if you are presented with a screen with a gold colored android in the center that says "Patched by SirPsychoS (0.99.3b) on the second line of text (like this), you're in SPRecovery. If however you are presented with a screen with no text, and a graphic of a triangle with an exclamation point in it and an arrow pointing to a phone (looks like this), you're in stock recovery. If it's the latter, either you failed to catch the boot and your phone has functioning FRS (and it put your recovery back to stock) or something else odd happened (not likely). In any event, if you're in stock recovery you can't proceed so your only choice is to go back to Step 9 and try again. If you're in SPRecovery, congratulations -- move to the next step.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  14. In the SPRecovery menu, use the volume up/down keys to highlight "install" and use the camera button to choose it.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  15. Now highlight "Allow update.zip Installation" and choose it. [It will appear to do nothing -- that's normal. If you're unsure if you clicked it or not, choose it twice, it won't hurt.]
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  16. Finally, highlight "Install /sdcard/update.zip (deprecated)" and choose it.
    13977d1282620429-root-droid-1-regardless-os-version-vs.gif
  17. The install should run to conclusion pretty quickly. When it's done it should look like this. If it does, congratulations, you're done. You're rooted with busybox, SPRecovery, and your FRS is now disabled so you won't revert back to stock recovery the next time you boot the OS. Enjoy!"
Yeah, I followed these directions to the letter and everything worked fine. But for some reason, it's not rooted.
 
i asked before, not sure if someone had answered ...

concerning future OS updates coming from motorola/google (i.e., android 2.3), will i have to find the update.zip and install it manually or will the OTA update appear as it would when i was not rooted ?

Most likely it will nag you but sprecovery will block the install. Unless you allow it which will remove root and possibly reintroduce FRS.

thanks, so the best route is to grab the update.zip as soon as it's available ...

that is, if it gets released for the original droid ...
 
If there's a push and you're not running a ROM that blocks OTA updates it will drop onto your phone. However, consider the fact that you don't HAVE to wait for it to drop onto your phone... And manual downloads and installs have proven far more reliable than OTA installs.

However, the update will break root, so your best bet is to wait until someone has a rooted OTA ROM and download+install that.
 
@gmorgan

You didn't really answer my question. I know which guide you are using.

When you catch the boot it says PASS and then you unplug and reboot while holding x you get sprecovery?



Sent from my Droid using Tapatalk
 
this is what i did to root my droid works great
but my keyboard has a bubble and im gunna trade it in before my warentee expires to get a new droid

how do i unroot and go back to stock?
 
ok so i got this working but how can i then grant superuser permissions to a certain program? my market doesnt work and i figured out how to fix it, but i need to give my terminal emulator superuser permissions so i can run a command to remove a file. when i click on my Superuser Permissions icon i see that SetCPU is allowed but i can't seem to add anything.
 
When you open the program a window will come up asking if you want to allow root access. Check the remember box then allow.
Done.

Sent from my Droid using DroidForums App
 
No box pops up asking to allow superuser access when i start terminal emulator

When you open TE, type in "su" (no quotes) and press enter, it should change from a $ sign to a # sign. Is that what happens? If so, it recognizes you as su.

I believe TE is like running a command prompt on your PC - It will run even if you're not an admin; it just won't give you access to certain commands as a non-admin.
 
Last edited:
Actually, as you noticed, just opening Terminal does not ask for superuser. Entering the command jeffe65 pointed out should then give you the popup box asking for superuser, make sure the "remember" box is checked, then you will see your prompt change from a "$" to a "#".

good luck
 
Ah, a bootloop. Do what guidot says, but a caveat -- Bugless Beast v.5 is a BEAST to install for inexperienced ROM users. Make ABSOLUTELY SURE you are following the directions in his thread to get it to work right.

In SPR, wipe system data 3x, then wipe the data cache 3x separately. You'll have to set the phone back up, but it's the only way to jump from ROM to ROM with any kind of assurance it'll work. Some people say you don't have to if you're jumping from AOSP ROM to AOSP ROM, but the last thing you really want is to have to SBF your phone back to stock and start over because something screwed up. It's happened. :)

I just rooted my friends phone the droid, I have a nexus one so im experienced with rooting, i just did what you said and i'm still getting boot loop, i flashed the latest 205 nightly @ cyan and i'm getting the loop...what can I do?
 
Back
Top