A little something I learned from decades of experience, and being a open source RCE and engineering talent way before OSS existed: When you create a scene around a project and abuse accumulated information, people who could productively contribute tend to not take interest in collaboration..
On most projects like this for embedded devices, information the devs accumulate tends to be used in popularity contest rather than put in public domain making the project more attractive to someone who just wants to assist for results..
One thing I found through my own efforts being a new 5620 owner, is that you don't need modified cables for most things. 'Master ROM' has a handler for USB bus that handles writing, this includes second stage boot loader range which is what this team is trying to create(first stage can't be written unless there is a accessible hardware interface). For android kernel you can't fit memory setup in the allowed space and have to jump to a loader.
The only reason I'm looking into the 5620 is to fix my own issues with baseband data, my options are get the information from here or spend weeks or months reversing millions of bytes of mode handling code, some of which will require expensive hardware to dump because of kies range limitations..
EDIT: One thing I always found annoying with embedded device scenes is how everyone is trying to exploit everyone else and nothing ever really gets done..getting information that would otherwise be trivial is like pulling teeth as a result..