[Droid Eris Android Development] bftb0:
Uh ... um ...

jcase's "One Click" doesn't touch the bootloader. You could re-perform this method after doing something else (e.g. jcase's "One Click"), but that really doesn't make much sense: flashing a PB00IMG.ZIP ROM wipes out everything on the phone, so it (almost) makes what you did previously irrelevant with the exception of backups that can be later restored.

Now that you have 1.49.2000 S-OFF on your phone, there shouldn't be a need to ever touch the bootloader again - unless you want to become an expert at Eris flashing techniques, or you are planning on cleaning up the Eris for a sale or return. Even in that case, though - because you have a S-OFF bootloader on the phone - the fastest way to roll back the bootloader is by flashing the replacement S-ON bootloader into place by using fastboot with the S-OFF bootloader on the phone. (That's the single most dangerous thing you can do to the Eris, BTW).

You might want to consider updating your radio though - flashing the Root PB00IMG.ZIP ROM via HBOOT as you just did installs a fairly old radio, and virtually none of the Eris dev ROMs flash the radio - so you will be sort of "stuck" with the old radio unless you update it.

Note also that there is a tricky way of installing the Root ROM (w/ 1.49.2000 S-OFF bootloader) PB00IMG.ZIP file in a way that only installs the bootloader, so that anything else on the phone is not touched (e.g. recovery, radio, or OS) - you can search for the "toastcfh Battery Pull Trick" for that. There is also floating around somewhere a flashable package named "erisengspl.zip" which is claimed to have the same result - only flashing the S-OFF bootloader and leaving everything else untouched. SEE WARNING BELOW!

One more thing - again, I am reading between the lines - but something you might want to be aware of when reading threads on this board:

Various people use the word "rooting" to mean nothing more than:

[SIZE=+2]"Rooting means gaining some form of privileged execution on the phone."[/SIZE]

That "privilege" could be anywhere - using the bootloader, the recovery boot, or the regular OS boot. It doesn't mean anything specific about what is installed elsewhere on the phone; for instance:

- Engineering bootloader (1.49.2000 S-OFF) + Stock recovery + Stock OS = Rooted

- Stock bootloader + Custom recovery + Stock OS = Rooted

- Stock bootloader + Stock recovery + Rooted OS = Rooted

The most flexible combination (in terms of disaster recovery and available tools), though, is:

- Engineering bootloader (1.49.2000 S-OFF) + Custom recovery + Rooted OS = Root

As an example, jcase's "One Click" only installs the Amon_RA custom recovery IIRC - you then have the (privileged) ability to modify other stuff on the phone - for instance by flashing a "ROM" to install a rooted OS.

There. That's enough to chew on for a while.

bftb0

[ Edit 2011-01-18 ]

[SIZE=+2] WARNING: "erisengspl.zip" EXTREME HAZARD[/SIZE]

[SIZE=+1]

XDA user blindmanpb reported bricking of his phone when "erisengspl.zip" was flashed on a phone with a 1.46.0000 S-ON bootloader present.[/SIZE]

Previously, my own personal testing showed that it does not work with the 1.47.0000 S-ON bootloader (but did not cause a bricking)

[SIZE=+2]DO NOT USE "erisengspl.zip" ON ANYTHING OTHER THAN THE 1.49.0000 S-ON BOOTLOADER[/SIZE]