SBF to root and to unroot

[teddyearp]

christim (or other RS): sorry if this suggestion has already been posted...

Since we have the full FRG22D system OTA file available now, and it flashes using sprecovery, clockwork, and obviously stock recovery, as well as replacing anything that's not the stock recovery, can't the "unroot" instructions be simplified (with better organization and verbiage obviously) to just "download this file, rename to update.zip if using spr/stock, wipe data/cache, flash away"?

Just thought it might be a simpler way for a lot of people to unroot and get back to "pure" stock now that FRG22D should be officially pushed out to everyone. It wipes /system, so it gets rid of root, and it puts stock recovery back on.

Obviously, using the .sbf will still be needed if recovery isn't attainable, but the way I see it, the less we have to rely on rsdlite and all of the "rsdlite can't see my phone" issues, the better, and easier for RS members!

+++1 for this ^^^^^. I have been trying to push this type of method for un-rooting for quite a while now (see the thread linked in my sig) since there are SO many potential pitfalls to using RSD Lite.

 

[jntdroid]

+++1 for this ^^^^^. I have been trying to push this type of method for un-rooting for quite a while now (see the thread linked in my sig) since there are SO many potential pitfalls to using RSD Lite.

Just seems like it could make life a little easier in some situations... I see this thread quoted ALL the time by RS and non-RS members when someone needs to unroot and start "fresh", and it seems like the .sbf method might be overkill - again, in some situations - and ends up creating more questions. It's an awesome tutorial, don't get me wrong, just trying to simplify...

 

[furbearingmammal]

There are reasons to want to SBF back to stock -- for example when sending a phone in for replacement or prior to sale -- but for most people the master OTA is perfect.

 

[Abe21599]

+++1 for this ^^^^^. I have been trying to push this type of method for un-rooting for quite a while now (see the thread linked in my sig) since there are SO many potential pitfalls to using RSD Lite.

Just seems like it could make life a little easier in some situations... I see this thread quoted ALL the time by RS and non-RS members when someone needs to unroot and start "fresh", and it seems like the .sbf method might be overkill - again, in some situations - and ends up creating more questions. It's an awesome tutorial, don't get me wrong, just trying to simplify...

so that FRG22D is practically an update that flashes back to stock 2.2 using recovery? ill make a suggestion to the other members.

 

[jntdroid]

There are reasons to want to SBF back to stock -- for example when sending a phone in for replacement or prior to sale -- but for most people the master OTA is perfect.

If that file replaces recovery, puts the newest bootloader on, and wipes /system when it basically overwrites it, how would that be different than using the .sbf?

 

[jntdroid]

+++1 for this ^^^^^. I have been trying to push this type of method for un-rooting for quite a while now (see the thread linked in my sig) since there are SO many potential pitfalls to using RSD Lite.

Just seems like it could make life a little easier in some situations... I see this thread quoted ALL the time by RS and non-RS members when someone needs to unroot and start "fresh", and it seems like the .sbf method might be overkill - again, in some situations - and ends up creating more questions. It's an awesome tutorial, don't get me wrong, just trying to simplify...

so that FRG22D is practically an update that flashes back to stock 2.2 using recovery? ill make a suggestion to the other members.

Yes - I've only tested on Clockwork 2.5.0.1, but it worked just as it did on stock as well as sprecovery.

 

[christim]

There are reasons to want to SBF back to stock -- for example when sending a phone in for replacement or prior to sale -- but for most people the master OTA is perfect.

If that file replaces recovery, puts the newest bootloader on, and wipes /system when it basically overwrites it, how would that be different than using the .sbf?

The end result is the same, a stock phone, but you don't need rsd lite. You could download it with your phone, rename it to update.zip and move if from /sdcard/download to /sdcard/update.zip, reboot into SPR or CW then install it and be back at stock. Good for Mac users, good for those not near a PC. Might not even be a bad idea to just keep it on your phone in case something goes on the fritz so you can still use it as a phone to dial someone.

This thread was started a while ago. The info works, but it is getting dated and there are some newer methods out and about. The topic of the thread we see, and it covers that topic. In a crunch sbf files will save your phone. It might not be an immediate solution but if it is the only one then you just gotta get to a windows PC with RSD Lite on it.

I spent yesterday working on a new root thread. It's locked away out of site at the moment but should be ready "soon" (day or so).

The FRG22D sbf file would be a good candidate to replace the 'back to stock' sbf step as that avoids having to do OTAs or manual upgrades to get back to Android 2.2. A couple days ago I removed the ESE81 instruction part due it having the 2.1 kernel included which plays havok when you are on a 2.2 operating system. That option box points to MotoCache1's thread with the updated sbf file he made that is kernel-less.

 

[christim]

ok, I know, double post. By a mod.

jntdroid, teddyearp and anyone else who might have suggested it...

First post, box option 6, the update.zip method has been updated to use FRG22D

Thanks for the suggestions guys and if someone has CW specific instructions I'll add an OR, in there for using that recovery tool to apply the update.zip

 

[furbearingmammal]

There are reasons to want to SBF back to stock -- for example when sending a phone in for replacement or prior to sale -- but for most people the master OTA is perfect.

If that file replaces recovery, puts the newest bootloader on, and wipes /system when it basically overwrites it, how would that be different than using the .sbf?

Simple. Personal data. Some people might not want pictures or texts/e-mails/music/incriminating evidence left on their phone.

 

[jntdroid]

There are reasons to want to SBF back to stock -- for example when sending a phone in for replacement or prior to sale -- but for most people the master OTA is perfect.

If that file replaces recovery, puts the newest bootloader on, and wipes /system when it basically overwrites it, how would that be different than using the .sbf?

Simple. Personal data. Some people might not want pictures or texts/e-mails/music/incriminating evidence left on their phone.

Oh... well, true, I guess I was just working under the assumption that flashing that .zip would be coupled with doing a data/cache wipe - but obviously that shouldn't be assumed.

 

[teddyearp]

Yes, everything personal is cleared by doing a factory data reset (wipe data/cache) and there have been these similar ways/files to unroot the phone via the recovery system. This method here to root and unroot was really a compiliation of this:

http://www.droidforums.net/forum/hacking-help/37717-unroot-unbrick-using-sbf-post-ikithme.html

(but it lacked the big fat warning about using RSD Lite) and the method using the SPRecovery_ESE81.sbf file created by [mbm]that used to be on DroidMod.org.

RSD Lite (as my limited knowledge understands it) is service software that is usually only used by techs and as such I have found it to be a bit extreme to see it thrown it at eveyone who want to revert their phone to 'stock' and/or every other little problem that usually can be fixed via recovery, nandroid, wiping, and/or adb shell. But when I have posted such concerns in the RS, I have been drowned out by the majority who has been linking to this thread. I am glad that someone else has been able to point this out and be heard. Thank you jntdroid.

Now that we have the most excellent way to root thanks to the extreme work of MotoCache1, and the simplicity to unroot via the full FRG22D update.zip file, if it were me I would take and put this thread in the historical archives. But that's just me. Mind you, I don't purport to be all knowing or someone who knows all things there are to know about the Droid 1 phone. I just keeps reading the tons of threads and do alot of my learning from the trials and errors of others who don't.

OK, I'll get off my soap box now.

 

[jntdroid]

ok, I know, double post. By a mod.

jntdroid, teddyearp and anyone else who might have suggested it...

First post, box option 6, the update.zip method has been updated to use FRG22D

Thanks for the suggestions guys and if someone has CW specific instructions I'll add an OR, in there for using that recovery tool to apply the update.zip

christim - feel free to pull the clockwork info from here if you think it's good enough: http://www.droidforums.net/forum/re...ck-2-2-without-sbf-rsd-lite-droid-1-only.html

 

[mtz_gto]

Just wanted to say thank you for your tutorial.
It helped me put my old Droid back to stock for a warranty replacement
from big red.

~J


Notes: used sbf file with Moto RSD lite on Windows 7 with no problems.

 

[christim]

RSD Lite (as my limited knowledge understands it) is service software that is usually only used by techs and as such I have found it to be a bit extreme to see it thrown it at eveyone who want to revert their phone to 'stock' and/or every other little problem that usually can be fixed via recovery, nandroid, wiping, and/or adb shell.

OK, I'll get off my soap box now.

Soap boxes are a cool thing.

ikithme's guide is indeed where this all started.

I wouldn't call it extreme. 2 posts above yours it was very useful to mtz_tgo. It works and that is what counts. What makes it great is exactly what you posted. It solves all of those above problems. Someone, somehow, has done something they shouldn't have and now their phone doesn't work. We've all seen the posts where we try and fix the current problem and hours or days go by. Time and time again it has been the fasted way to get someone's phone fixed. Some of us want and need to know what makes the light go on. Others just want to flip the switch, see the light, and go do something else more important to them. Neither mentality is right or wrong, it just is what it is.

That doesn't mean RSD Lite is always offered as the first and only solution but if there is a lot of confusion on the part of the op or things are really messed up it just gets the job done quickly.

Out of the 6 options on the first post:

1 - installs rsd lite...no risk to anything there, just installs it on your computer. If you want it you need instructions and links. I'd say those aren't outdated yet.

2 - links to motocache1's thread (one of your two suggested options)

3 - do a backup....nothing outdated with that suggestion

4 - install a rom with what you installed in option 2 - also not outdated.

5 - flash to stock via rsd lite and the stock 2.01 sbf file. Question is...is there a complete stock 2.2 sbf file this can be replaced with. Anways, still relevant instructions if someone can't get into recovery.

box option 06: update.zip with frg22d (2nd of your two suggested options)

 

[furbearingmammal]

Christim --

http://androidoverdrive.com/pete/OEM/VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE.sbf

That's the FRG01B SBF. That's as current as they come that I'm aware of.