Of Interest: Rooting your Samsung Captivate [2.3.5]

I somehow bricked my phone today - it freaked me out (more than a little bit), so I ended up taking it to the AT&T service shop, where they restored it to working order, free of charge.

I then bricked it again. (This is where facepalms are appropriate...)

I then miraculously unbricked it.

In the same vein as my previous rooting (I rooted the phone within twenty-four hours of first receiving it), I set out to figure out how to do this. I also want to install a custom ROM, but that comes later.

Enter copious amounts of trawling the internet (and also being scared of breaking something while the phone is in "DOWNLOAD MODE: DO NOT TURN OFF TARGET!").

I stumbled upon this treasure and have since been happily plugging away at getting everything done:

[ http://androidforums.com/captivate-all-things-root/483646-guide-root-official-2-3-5-guide.html ].

There is something to be said about tenacity and perseverance and just how much smarter some people are than I.

I'm somewhat interested in upgrading phones, but this wondrous piece of technology will do for now.

Be advised...

[ http://m512.tk ] is no longer under my control. If you or someone you have shared this site with typically access CCWK through that address, I apologize for the inconvenience and ask that you use [ http://ccwk.co.cc ] for the time being.

I'm working on getting another free domain name, though.

EDIT: [ http://x512.tk ] is the new address.

MC

Stuff I like: TmarTn's Youtube Channel

[ http://www.youtube.com/user/TmarTn ] is someone I just discovered - I'm quite late to this party (and I haven't been posting during the time I've been working on everything for school. That being said, TmarTn is an excellent tutor when it comes to Call of Duty: Modern Warfare 3's multiplayer.

I'll admit that I'm absolutely terribad when it comes to the FPS sorts of games - the advice I got from friends is to watch pro gameplay (a la Major League Gaming's MW3 Gamebattles); I don't get much out of search and destroy, though.

I'm looking for ways to up my game. Do y'all have any tricks to share?

Python is haaaard.

Well, not really.

[ Python ] is a language I decided I'd sit down and learn for a project I've taken upon myself to write.

So far I'm two mostly-working modules in and it's not terribly difficult to understand what I'm doing.

A relevant citation is what python returns when the user types import this:



The Zen of Python, by Tim Peters


Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!


I've tried to keep what I'm doing to be just that: easy to explain and read and understand. I have not, however, made it easy to write or optimize (mainly because I'm not the most competent programmer out there).

The language encourages ease-of-learning and ease-of-use, something which I think is important enough to shirk Java and C as a whole.