[Motorola Droid X2] mostKnownUnknown:
That's fine by me. I've tried a few things but nothing has really panned out where I think a team of people is needed to investigate. You can only do so much when this is your first android phone, a primary phone and when you have real life to deal with :).

I think the item that most people can do is still Project Cheesecake. I'm still finding development updates and sending them to the2dcour (no unlock was found yet). It's not hard to do in terms of technical ability. It just takes a good amount of time. Also, we just need to be a bit lucky with a Moto dev posting the right update on the could servers while we're searching it.

Whoa. Hold up there. Don't go flashing over the bootloader just yet. We at least need to come up with a very good reason before we brick someone's phone. For now, let's mobilize our efforts into something concrete and then we may need a test phone.

I'm trying to take your guys money. But every time I see that "Failed to boot." error, part of my hopes get dashed. I'm still working closely with the2dcour on Project Cheesecake but that is more about luck in finding the unlock. I wonder what TeamWin has in store.

I don't have anything to really push with a team just yet. I'm just trying a few things followed up by SBF after SBF after SBF. Once I have a solid approach to go down then I'll really enlist the various communities to help.

Recalling grad school classes for a bit... When you digitally sign something, the signature is composed with something you know (private key) and a representation of the data (hash). Because of the hash, the signature is unique to that data (for the most part) and you can't just copy the signature from one piece of data to another. However, when I think about approach #5, do we know if there are any flaws in the way the bootloader checks for the signature? If there is, then the bootloader can't truly tell if signature is from Moto. The exploit may be as simple as building program on the PC (windows, mac, linux, etc.) which allows us to sign the partition image as if we were Moto. Then we just distribute the program to those who want to make kernels or custom recoveries. That's my thought about "copying" a signature.

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

As a side note:

I'm still going to look at the ways of defeating the locked bootloader in my spare time (I work and take grad classes). In the mean time (now that everyone seems to be empowered in making the DX2 awesome), there are still two areas that the community can focus on with a locked bootloader:

1. Get a pure-ASOP ROM to boot

With the 2nd-init development, there shouldn't be any reason to unlock the true performance potential of the phone with a clean blur-less ROM (hell, the DX1 folks have CM7 running on 2nd-init off of the Froyo kernel). I think most people want to see CM7 and I don't believe it is too hard to leverage the work of the Atrix CM7 team. Now, I'm NOT saying we should go and try to port their version of CM7 since a) they are only at pre-beta stage and b) they built their version after they unlocked the bootloader so they have a few kernel changes. Since they did all the startup legwork, we SHOULD ask around the Atrix CM7 team to find out what changes from the main CM7 code to get it to boot (I'm thinking mount points and device drivers). We should assemble our own CM7 team and work off of the CM7 code main. Then if we fix any issues that seem to be common to both devices, we could work with the Atrix team to help fix it for both devices (more eyes on it, the better).

2. Get kexec to work

I think most people what an unlocked bootloader for the overclocking ability which requires a modified kernel. There was an effort on the Atrix side to get kexec to work. kexec is the ability to initiate a 2nd kernel while the first kernel is running and essentially take over where the first kernel left off (kinda like 2nd-init). The project stopped soon after the bootloader unlock was found. There is enough work there to really explore deeply. I think if can get this to work, we might forget all about the locked bootloader and might actually think Moto and VZW are not the devil (although I doubt it :)).

Those are the two recommendations for the community to do. I don't know what's the best way to get developers to help us work on both items. Maybe we could reallocate some of the bootloader bounty to get create bounties on both items. Anyway, I think those are the two wishes of the community right now and if we could get people motivated to work them, our phone could be in a happier place. Then maybe those "the phone is dead" and "the unhealthy state of our phone" threads go away because I'm so sick of those posts right now.

References:

Project Cheesecake - http://xdaforums.com/showthread.php?t=1226664

Digital Signature on Wikipedia - http://en.wikipedia.org/wiki/Digital_signature

Official CM7 for Atrix Thread - http://xdaforums.com/showthread.php?t=1257574

atrix-dev-team on Google Project - http://code.google.com/p/atrix-dev-team/

kexec on Wikipedia - http://en.wikipedia.org/wiki/Kexec

EternityProject Kexec method for Motorola Olympus (Atrix 4G) - http://xdaforums.com/showthread.php?t=1079097