Expanding on the ideas of others

[motorhead1991]

You guys have said for years that at some point, a collaborative effort should be made among the crazies that work on disassembly.

Well, given my experience on Android, I know that people work better when they can see another's work.

With that said, I'll attempt to be the catalyst for said effort. Let me formally introduce you to the OpenEEC-Project

I believe github is a good place to start this, since Atlassian's bitbucket can be confusing (but private repos are free there). So how about it, guys? Who's in?

(I'll put SAD up tonight, when I get the chance. Guess who gets to learn "git for windows")

[decipha]

i dont understand what your trying to achieve?

[motorhead1991]

i dont understand what your trying to achieve?

The same as any other collaborative project: to share knowledge, skill and experience. We all have a goal in common, why not work together to get there? Both Pym and tvr have open sourced their disassemblers, Lawrence's always was... This way, its all in one place, and a single person is not burdened with keeping everything current.

[decipha]

ah i see

[motorhead1991]

Do you happen to have a last name or Email address for Andy? I'd love to give proper authorship

[ranga83]

Why not just put all the files in the disassembly post?

[motorhead1991]

Why not just put all the files in the disassembly post?

I already have the source, I just wanted to make sure Andy's name was on it.

[motorhead1991]

Finally touched base with tvrfan, and he was very open to the idea. So far, the project is slow to take off, but it's going.

EEC-IV-disassembler

The title was Andy's idea, not mine.

I also created a Telegram chat. Its awful quiet in there
Telegram

[motorhead1991]

And here we have SAD running on Android. This is why I encouraged the OpenEEC project. If you look at the github, I'll have the code updated shortly.

Screenshot_ConnectBot_20180423-211219.png

[decipha]

i still dont undrstand the point, it would be a pain to do disassembly on an andriod or mobile device. I typically have 4 to 5 listings open at once to follow jumps and calls and to see whats doing what in order to make any useable sense out of the code. That would be extremely difficult on an andriod device.

[motorhead1991]

i still dont undrstand the point, it would be a pain to do disassembly on an andriod or mobile device. I typically have 4 to 5 listings open at once to follow jumps and calls and to see whats doing what in order to make any useable sense out of the code. That would be extremely difficult on an andriod device.

Because I don't sit at a computer all the time.

I'm working on an app that can open the files so you can view them in a text editor. To the trained eye, you'd be able to spot the common sub's and label them accordingly.

I do see your point though.

[Pym]

No interest to move SAD806x too to android (I have already created some software on it and I can say it will be horrible to use),
but as we had already discussed on it, publishing sources on GitHub will permit the project to continue living or at least to give a base for another one.
My shitty code is getting worse and worse, each time I add new things, so even if the job is not finished for me, it is the moment to keep trace of sources.
I will provide them to you soon.

[motorhead1991]

No interest to move SAD806x too to android (I have already created some software on it and I can say it will be horrible to use),
but as we had already discussed on it, publishing sources on GitHub will permit the project to continue living or at least to give a base for another one.
My shitty code is getting worse and worse, each time I add new things, so even if the job is not finished for me, it is the moment to keep trace of sources.
I will provide them to you soon.

806x would be way overcomplicated on Android . SAD was easy.