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

Root [How-To] Install SPRecovery on unrooted 2.1 OTA

1. Use the .sbf file provided in the OP to flash SPRecovery. You may have to read the sticky about RSD Lite to figure out how to do so. The link is in the OP.

2. Now you have two choices:

a. Install a ROM that is already rooted. You can find all those instructions in the respective ROM's threads.

b. Root your current 2.1 OTA. That requires knowledge of adb, and the file attached to the OP. If you have both of those, then you just follow the commands posted.

LOL ok...Who here lives in New Jersey and knows how to do this. I'll pay them to show me step by step how to do this stuff or better yet i'll pay to have it done.
 

Running RSDLite 4.5 on Windows 7 x64

When opening the SPRecovery_ESE81.sbf in RSDLite, it says: "Unknown Platform"

Filename: SPRecovery_ESE81.sbf
Creation Date: 04/14/2010 01:44:23
File size: 6345657
RAM DL Version: N / A
Bootloader Version: N / A
Platform: Unknown Platform
HAB Type: Signed Production

The flash will not continue beyond this point. I verified the md5 sum on the .sdf file.

Any suggestions?
 
Running RSDLite 4.5 on Windows 7 x64

When opening the SPRecovery_ESE81.sbf in RSDLite, it says: "Unknown Platform"

Filename: SPRecovery_ESE81.sbf
Creation Date: 04/14/2010 01:44:23
File size: 6345657
RAM DL Version: N / A
Bootloader Version: N / A
Platform: Unknown Platform
HAB Type: Signed Production

The flash will not continue beyond this point. I verified the md5 sum on the .sdf file.

Any suggestions?

Ok, I figured it out. Make sure you have the latest RSDLite #1 I had to run RSDLite as an Administrator for it to run correctly.
 
1. Use the .sbf file provided in the OP to flash SPRecovery. You may have to read the sticky about RSD Lite to figure out how to do so. The link is in the OP.

2. Now you have two choices:

a. Install a ROM that is already rooted. You can find all those instructions in the respective ROM's threads.

b. Root your current 2.1 OTA. That requires knowledge of adb, and the file attached to the OP. If you have both of those, then you just follow the commands posted.

What if we don't have knowledge of ADB?

I booted into recovery... mounted /system

adb usb
adb shell (got # sign)
adb push su /system/bin/su

and that last command hung!

Please help!
 
What if we don't have knowledge of ADB?

I booted into recovery... mounted /system

adb usb
adb shell (got # sign)
adb push su /system/bin/su

and that last command hung!

Please help!

Do you have the two files from the .zip file IN the same folder as adb? That's where 'push' will look for the file to copy onto your Droid.
 
Do you have the two files from the .zip file IN the same folder as adb? That's where 'push' will look for the file to copy onto your Droid.

Got it working for those who need to know

1. Install Android SDK
2. Follow instructions up to mount /system
3. adb usb

  • adb devices (to verify)
  • adb shell (to verify you get #)
  • if you don't get # don't bother going forward
4. adb push su /system/bin/su
5. adb push Superuser.apk /system/app/Superuser.apk
6. adb shell

  • /system/bin/chmod 6755 /system/bin/su
  • /system/bin/chmod 644 /system/app/Superuser.apk"
7. Reboot and you'll have root
8. Install tethering? Forget it... no netfilter...
 
That's right, by default the kernel does not support tethering.

You will need to flash one of the many custom kernels to take advantage of wireless/wired tethering.

I suggest using these:

P3Droid Kernels
 
step five: stay alive

enjoy rooted stock ESE81, with no need to screw up your shit or install a hacked together copy of ota...

LMAO @step 5........

I will definitely be trying this out. Alot quicker and less of a headache then going all the way back to 2.0.1
 
Thanks for the instructions below to get su and superuser on there. FYI - if you just add /system/bin/ before the chmod commands in the OP it will work and wont give you the "not found" issue.


Got it working for those who need to know

1. Install Android SDK
2. Follow instructions up to mount /system
3. adb usb

  • adb devices (to verify)
  • adb shell (to verify you get #)
  • if you don't get # don't bother going forward
4. adb push su /system/bin/su
5. adb push Superuser.apk /system/app/Superuser.apk
6. adb shell

  • /system/bin/chmod 6755 /system/bin/su
  • /system/bin/chmod 644 /system/app/Superuser.apk"
7. Reboot and you'll have root
8. Install tethering? Forget it... no netfilter...
 
Works like a charm! Thanks for this post. This definitely needs to be a sticky.

Now I am on to finding some good custom ROMs :-)
 
I'm trying this right now. Turns out I had to force SDK to update/install thru http. I didnt actually have adb installed. Now I should be getting somewhere. I was getting the chmod errors too.
 
Yes, or, use Barnacle, [currently] available on the Market. It does a very good job of wireless tethering without having a specialized kernel.

Btw, Fab, wonderful thread. Thanks!!!!

That's right, by default the kernel does not support tethering.

You will need to flash one of the many custom kernels to take advantage of wireless/wired tethering.

I suggest using these:

P3Droid Kernels
 
Got it working for those who need to know

1. Install Android SDK
2. Follow instructions up to mount /system
3. adb usb

  • adb devices (to verify)
  • adb shell (to verify you get #)
  • if you don't get # don't bother going forward
4. adb push su /system/bin/su
5. adb push Superuser.apk /system/app/Superuser.apk
6. adb shell

  • /system/bin/chmod 6755 /system/bin/su
  • /system/bin/chmod 644 /system/app/Superuser.apk"
7. Reboot and you'll have root
8. Install tethering? Forget it... no netfilter...

Yes this worked for me too. Thanks. Also, I had to update the program that uses adb. Mighta been the drivers. I saw those update right at the end.
 
This looks really great! Got a quick question though.

Please note that this WILL reflash the boot image to stock ESE81! This is required to keep recovery from being overwrote on reboot. A few bits in the boot image were changed to break the checksum hash that the recovery update checks.

I'm not clear on this -- does it mean my droid will be reflashed to stock config and I'll lose any apps and data too? Or does it just put my stock ESE81 to a stock ESE81 with sprecovery ability and leave the apps/data alone?
 
wow! this was super easy. my brother just got a droid with the 2.1 update and asked if we could hack it. this was easier than rooting my phone was back in the day.
 
i've used this to root my droid, but now my headphone jack is busted and i gotta replace, how can i unroot my droid after using this process?

thanks
 
All of those asking for the root exploit for the 2.1 OTA, or those unsatisfied with 2.1 and wanting to go back can now use this method posted by Droidmod. It is essentially an .sbf file that will install SPRecovery on the OTA update, and eliminates the need to downgrade back to 2.0.1 to get SPRecovery.

Once you have SPRecovery, you can just flash any new ROM that has superuser permissions. The link is here:

2.1 SP Recovery SBF - DroidMod

The post is as follows:



You'll need to follow the instructions for RSD Lite from the following thread, just replace the .sbf file with the one from Droidmod:

http://androidforums.com/all-things-root-droid/47349-now-you-can-live-without-fear-bricking.html

-----------------------------------

Additionally, once you have SPRecovery, you can just root your OTA 2.1 (no need to flash another ROM), though this requires you to be competent with adb.

These are the instructions, thanks to samedroidsex.



Props to the DM team! This is a sick release. And all you unrooted 2.1'ers out there, enjoy SPRecovery.

Thanks for the previous tip, in regards to renaming my ESE81 to update. When I download and install Smoked Glass 6.0.1 by Adamz, I loose my super user permissions. So here I am trying to add super user permissions to Smoked Glass 6.0.1 by Adamz. How do I go about this process?

I have a superuser permission file, but I don't know if its the right one for an ESE53 ROM. I've installed the SDK on my computer and also need to know if that is where the commands (from cmd prompt) will be entered to manually install the super user file, while my phone is in SPRecovery mode.

Speaking of that I've downloaded ClockworkMod and no longer have SPRecovery mode. Does this matter?

Currently running Bugless Beast V0.9 over ESE81.
 
from what i heard the version of adamz smoked glass thats on rom manager is a bad file. i would guess that's why you lost superuser permissions.
 
Back
Top Bottom