Nah, getting into the bootloader doesn't do anything; it just interrupts the boot cycle. Now, if you get STUCK in the bootloader then ALL software on the phone (not the SD card) is gone and you're pretty boomed.
I'm currently on 2.3.340 using fission and looking to try out Tranq. Before I venture into that, I want to make sure I know which SBFs I should be using in case of a brick.
If i wanted to completely clean everything out back to stock, do I need to flash the full 2.3.320 then the system only 2.3.340? Or can I just flash the system only 2.3.340 with a wipe data/cache a few times?
When reading through all these threads, I information for both, so I'm not quite sure.
-- Since ROMs only replace system stuff (well, MOST ROMs, some are now replacing boot logos, and putting files on other parts of the phone)... flashing the /system only .sbf should clean you up.
--FULL .sbf to 2.3.320, THEN flashing up to 2.3.340 via the 4 patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
The FULL 2.3.320 .sbf also changes your bootloader/kernel/baseband back to 2.3.320, so you need to re-update them back to 2.3.340.
--Maderstcok has an update that .sbf's to 2.3.320, then 2.3.340 all in one update. Still fairly untested, but might be an all in one solution for ya. Search for it on the boards if you decide to try it, you'll find it.
--might find some interesting stuff, including misc. DroidX and Android stuff at my site: http://www.sephtin.com
firstname.lastname@example.org or try to walk me through what i have to do step by step.... thanks
You installed the wrong version of the ROM on your phone in the first place. Now you need the right SBF. You've tried two wrong versions. Do you remember what system version you had before you tried to install the ROM?
also 2.2.1...baseband version BP_C_01.09.07P
kernal 126.96.36.199-g5562e1w30471@il93lnxdroid08 # 1
thats everything I know ... hope to hear you know how i can restore this after my mistake for trying to rush....