SBF to root and to unroot

[Tallica]

OK...so, I'm thinking about going over to the dark side (I hear they have great cookies). I've read the guide in the beginning of the thread on using RSD Lite to install SPRecovery.

I have a Droid running stock 2.2 (did the manual update a few days ago), and have a few (noob) questions :icon_eek:

Can I install SPRecovery on top of 2.2, and if so which SPRecovery file do I use (a link would be greatly appreciated)?

If I can, after booting into SPRecovery, and making a backup, do I just flash the FRG01B sbf file from Pete's website to get 2.2 rooted?

If not, what would be recommended the recommended path to get 2.2 root on my droid?

Or, do I just have no idea what I'm doing?

Thanks!

Directly above your post is your exact issue, christim expained it good, Some people have issues flashing SPR over 2.2. that it's why it's recomended to go back to 2.0.1.

Once SPR is in place you can flash ANY rooted Rom for the Droid, doesn't have to be The FRG01B file.

The link to the SPR.sbf is in the OP do steps 1,4,2 then 3 in the OP
Then you can install any Rom through SPR.

 

[christim]

I just updated those steps too....to include the all important "back up" step!
All files mentioned reside in the first post of this thread.

 

[furbearingmammal]

OK...so, I'm thinking about going over to the dark side (I hear they have great cookies). I've read the guide in the beginning of the thread on using RSD Lite to install SPRecovery.

I have a Droid running stock 2.2 (did the manual update a few days ago), and have a few (noob) questions :icon_eek:

Can I install SPRecovery on top of 2.2, and if so which SPRecovery file do I use (a link would be greatly appreciated)?

If I can, after booting into SPRecovery, and making a backup, do I just flash the FRG01B sbf file from Pete's website to get 2.2 rooted?

If not, what would be recommended the recommended path to get 2.2 root on my droid?

Or, do I just have no idea what I'm doing?

Thanks!

What everyone else is saying about the step right above your post. Also, once you've rooted, my thread (linked in my signature) on post-root advice might help.

 

[jizoeyw]

im back to the beginning but no OTA

I am currently back to 2.0.1. I however am not getting any OTA updates for 2.1. Is there anyway I can get the OTA other than checking for updates? I guess I am just trying to get back to 2.1 the official way, any suggestions?

 

[jstafford1]

I am currently back to 2.0.1. I however am not getting any OTA updates for 2.1. Is there anyway I can get the OTA other than checking for updates? I guess I am just trying to get back to 2.1 the official way, any suggestions?

Since 2.2 is currently rolling out there will be no 2.1 update for you. If you don't get 2.2 by tomorrow might have to manually install it.

 

[grgguy]

A big thank you to who ever wrote this ....I thought I had killed my favorite toy but by following the instuctions its as good as new .

 

[jstafford1]

I have good news for everyone. There's going to be some new goodness coming to this guide in the next couple days. Keep your eyes on it.

 

[christim]

A big thank you to who ever wrote this ....I thought I had killed my favorite toy but by following the instuctions its as good as new .

Glad it worked out for you!

Some recent info leads me to think the following:

The sbf file for SPRecovery on ese81 comes with the ese81 kernel.

Coming from a stock 2.2 phone and trying to root, it makes sense to me that if you apply that SPRecovery sbf file you will have a kernel that doesn't play nice with Android 2.2

So: if you first put your update.zip rom file onto the root of your SDcard and then apply SPRecovery via RSD Lite and then reboot into SPRecovery and allow/apply update.zip you will have your rooted 2.2 rom on your phone.

alternatively, you can boot into SPRecovery once it is installed and use the mount option to get the update.zip file onto the root of your card, then allow/apply update.zip method and be good to go.

It's all in the order of how you do things. Makes sense to me, but I have not tested this.

 

[furbearingmammal]

SPRecovery comes with a 2.1 kernel. That would explain a LOT. Why didn't I think of that? I'm not tearing SBF files apart of messing too much with my Droid, of course. I wonder why Motorola hasn't offered some of you guys jobs yet.

 

[AlBundy]

Just to make sure I have this correct, the update.zip file referred to below, would be the JRummy file from the FroYo Circus thread, if I want to wind up with rooted 2.2 coming from stock 2.2.

So: if you first put your update.zip rom file onto the root of your SDcard and then apply SPRecovery via RSD Lite and then reboot into SPRecovery and allow/apply update.zip you will have your rooted 2.2 rom on your phone.

Also, would I need to do a data wipe before flashing; I'd prefer to keep my data if I can.

Thanks

 

[christim]

Just to make sure I have this correct, the update.zip file referred to below, would be the JRummy file from the FroYo Circus thread, if I want to wind up with rooted 2.2 coming from stock 2.2.

So: if you first put your update.zip rom file onto the root of your SDcard and then apply SPRecovery via RSD Lite and then reboot into SPRecovery and allow/apply update.zip you will have your rooted 2.2 rom on your phone.

Also, would I need to do a data wipe before flashing; I'd prefer to keep my data if I can.

Thanks

Going from a 2.2 kernel to a 2.2 kernel you probably are ok.

1. install sprecovery
2. do an advanced nandroid backup (takes less than 3 minutes)
3. flash your circus thread rom. or any rom you want via update.zip method
4. if all is well, stop here and make a backup. you are done.
5. if it blows up in your face do a restore of the backup you made
6. wipe cache and data
7. install your update.zip
8. once it is all set up do another backup

The trick is to put the update.zip in the root of your card first, before flashing the sprecovery via rsd lite. Then you can just boot into SPRecovery and install the rom.

 

[Tanknspank]

How to flash an sbf from linux.

1) Download the sbf_flash file, and make sure it and the .sbf you are trying to flash are in the same directory.

2) power off the phone.

3) connect the phone to the computer while holding up on the d-pad.

4) now you need to cd to the directory of the sbf_flash and .sbf files. Open a terminal and cd to the folder.

for example, if the files are in the download folder of ubuntu, it would be cd /home/owner/downloads

5) Now it is time to flash the phone. First we need to chmod the sbf_flash, then we can flash it.

chmod +x sbf_flash

6) Now we flash the .sbf. Of course the filename.sbf is the actual name of the .sbf you are using.

./sbf_flash filename.sbf

You should get output in the terminal that looks like this:

SBF FLASH 0.01 (mbm)

=== hack.sbf ===
00: RDL03 0x80500000-0x8054CFFF FE66 AP
01: CG35 0xC0680000-0xC08E37FF ABCB AP
02: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP

Droid found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
Droid (ramloader) found.
>> sending erase
>> uploading CG35
Uploading: 100% OK
>> uploading CG47
Uploading: 100% OK
>> verifying CG35
-- OK
>> verifying CG47
-- OK
>> rebooting

Sbf_flash

I will work on testing this method myself, but this was posted by [mbm] from DroidMod so it most likely works

 

[christim]

Hey christim, i was thinking, maybe you should add how to flash sbf's from a linux platform.

If you test it and get it working, we'll get it out there. A bootable Linux CD, or USB stick, with the right tools might be a mac solution as well as a Linux solution.

 

[Tanknspank]

Hey christim, i was thinking, maybe you should add how to flash sbf's from a linux platform.

If you test it and get it working, we'll get it out there. A bootable Linux CD, or USB stick, with the right tools might be a mac solution as well as a Linux solution.

I think I've figured it out now. I will update the post with the correct guide and files, and tell you when. I need to backup my current setup on my phone, and then I will test it. I need to download an sbf to test it with though, and my connection sucks, so don't count on it anytime soon.

 

[Tanknspank]

K updated. And we don't need to upload the file christim. [mbm] wants it to be linked to the original link so he can keep track of everything. I will be testing this soon.

Oh, and the ESE81update.zip is actually twice the size it needed to be. I checked into it and it has another ESE81update.zip inside of it, thus making it huge. Just saying